Thanks to visit codestin.com
Credit goes to github.com

Skip to content

eve persist on second disk fix: don't init P3 partition#5289

Merged
rene merged 1 commit into
lf-edge:masterfrom
andrewd-zededa:install-persist-second-disk
Oct 9, 2025
Merged

eve persist on second disk fix: don't init P3 partition#5289
rene merged 1 commit into
lf-edge:masterfrom
andrewd-zededa:install-persist-second-disk

Conversation

@andrewd-zededa

@andrewd-zededa andrewd-zededa commented Oct 6, 2025

Copy link
Copy Markdown
Contributor

Description

For eve installs where the persist filesystem is placed on a separate disk: storage-init will not detect a P3 PARTLABEL on the install disk so the IMGA variable will be set and P3 will be empty. Use the IMGB empty or IMGC not empty as a way to detect this is an uninitialized system. Allow storage-init to fall to line 252 #in case of no P3 we may have EVE persist on another disks where the zpool import will occur.

PR dependencies

None

How to test and validate this PR

  • install eve HV=k with install and persist on separate disks (grub.cfg: eve_install_disk=sda eve_persist_disk=sdb)
  • configure controller with debug.enable.ssh, ssh to eve node, enter pillar container, verify "zpool status" shows sdb used as device not sda9.

Changelog notes

Fix EVE install where persist is placed on a second disk.

PR Backports

  • 14.5-stable: TBD
  • 13.4-stable: No, as the feature is not available there.

Checklist

  • I've provided a proper description

  • I've added the proper documentation

  • I've tested my PR on amd64 device

  • I've tested my PR on arm64 device

  • I've written the test verification instructions

  • I've set the proper labels to this PR

  • I've checked the boxes above, or I've provided a good reason why I didn't
    check them.

Comment thread pkg/storage-init/storage-init.sh Outdated
@andrewd-zededa andrewd-zededa changed the title Restore previous condition for virt eve install disk init. eve persist on second disk fix: Restore previous condition for virt eve install disk init. Oct 6, 2025
@zedi-pramodh

Copy link
Copy Markdown

I tested the fix and it works.

@zedi-pramodh zedi-pramodh left a comment

Copy link
Copy Markdown

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

LGTM

@rene rene requested a review from rucoder October 7, 2025 08:30
@rucoder

rucoder commented Oct 7, 2025

Copy link
Copy Markdown
Contributor

@andrewd-zededa @zedi-pramodh did you test PLATFORM=evaluation? this change breaks it

@rucoder rucoder left a comment

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

on EVAL eve all partitions are initialized so this condition must be adjusted for both cases

@andrewd-zededa

Copy link
Copy Markdown
Contributor Author

@andrewd-zededa @zedi-pramodh did you test PLATFORM=evaluation? this change breaks it

Ok, my original private message was asking about this. I guess this needs to be reworked to handle both situations.

@andrewd-zededa andrewd-zededa force-pushed the install-persist-second-disk branch from f36a84a to 4b73364 Compare October 7, 2025 20:21
@andrewd-zededa

Copy link
Copy Markdown
Contributor Author

I've amended the commit to attempt to handle all three conditions:

  • cloud init of non eval eve
  • eval eve
  • skip for zfs persist (and document this condition).

I'm working through testing this latest change.

@andrewd-zededa andrewd-zededa changed the title eve persist on second disk fix: Restore previous condition for virt eve install disk init. eve persist on second disk fix: don't init P3 partition Oct 7, 2025
@OhmSpectator OhmSpectator requested a review from rucoder October 7, 2025 20:29
Comment thread pkg/storage-init/storage-init.sh Outdated
@rene

rene commented Oct 8, 2025

Copy link
Copy Markdown
Contributor

@andrewd-zededa , just found a minor thing, otherwise LGTM.... I'll wait for @rucoder's comment as well...

Its possible that P3 is not initialized if the EVE installer was
configured to use a zfs persist on 1 or more separate disks.
eg. eve_install_disk=sda eve_persist_disk=sdb.

Condition was originally amended for Eval EVE in this commit:
7b9076f.
Attempt to formalize the two conditions expected here and
document the possible zfs condition.

Signed-off-by: Andrew Durbin <[email protected]>
@andrewd-zededa andrewd-zededa force-pushed the install-persist-second-disk branch from 4b73364 to 8e13f5f Compare October 8, 2025 14:58
@andrewd-zededa

Copy link
Copy Markdown
Contributor Author

Thanks @rene, fixed the space. @rucoder can you take a look at this?

@andrewd-zededa

Copy link
Copy Markdown
Contributor Author

The evaluation build is red but its due to this:

The self-hosted runner lost communication with the server.

@andrewd-zededa

Copy link
Copy Markdown
Contributor Author

/rerun red

@rucoder rucoder left a comment

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

LGTM!

@zedi-pramodh

Copy link
Copy Markdown

Looks like I have permissions to merge, can I exercise my power :)

@rene rene merged commit 4decd9b into lf-edge:master Oct 9, 2025
60 of 69 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

4 participants