-
Notifications
You must be signed in to change notification settings - Fork 1.7k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
bootup: "couldn't find a valid label" #2057
Comments
Addendum: there does seem to be an issue with grub, in how it handles mirrored pools. I split rpool, which gave me a pool on only ata-WDC_WD3200BPVT-22JJ5T0_WD-WX81AA1M9437-part6, ran update-grub; grub-install and reboot. The pool is now resilvering after I added back ata-WDC_WD3200BPVT-22JJ5T0_WD-WX81AA1M9437-part8 to it, I will report back if rebooting with it gives a new issue. I have no reason to expect it will ... ... as long as I don't (have to) rebuild grub.cfg ! |
Compar:
with
The former is an extract from grub.cfg generated when update-grub is run with a mirrored pool, the latter with a pool without redundancy. Note how the former grub.cfg sets the root to the /boot partition, while the latter sets it to the zfs partition, referenced through its guid (took me a while to figure out that one :) ) |
@RJVB This is not an issue with ZoL. Please move this to https://github.com/zfsonlinux/grub. |
Closing, it was migrated to zfsonlinux/grub#13. |
I modified one of my LinuxMintDebian-on-zfs set-ups yesterday. Its pool had an external mirror and because I didn't want the moral obligation to keep an external disk connected (it's a netbook), I decided to split its linux partition in 2and rebuild the pool using like so. The ext3 /boot partition was on sda7 where I left it:
I know that this kind of mirroring isn't the most protective (but it ought to protect more against bit-rot than no mirror at all) and I notice now that gparted finally did not give me 2 perfectly identical partitions (6 & 8), but that's not the point here (or so I hope).
I've been doing quite a bit of linux-on-zfs setting up lately, so I was confident that the most time-consuming in this operation would be the 2 send/receive operations to and fro an external disk.
Instead, I've been spending hours rebuilding the initramfs, grub.cfg and rebooting, and I cannot seem to get rid of that boot error
"could not find a valid label"
After a pause, the boot continues, and until I renamed my pool from Patux to the default, rpool, I had to import and mount it by hand for the boot to complete.
Initially, I saw messages about sda6 and sda7 not being found in device.map (which I don't have), I think during update-grub. This was after 1:30 in the morning, so sadly I didn't think to save them. This morning, I almost thought the cycle looked good, but a reboot still showed that dreaded warning and I decided to raise this issue.
This time I kept a log:
grub.cfg looks like this:
So what is that label that's not being found as the first thing during the boot process after I selected the desired grub entry? Why is it that I could boot with my pool name of choice (and still can on my other set-up, rebuilt no later than last Monday, with a copy of this netbook's pool?)
Could it be the fact that there's a newline in the -class os $menuentry_id_option?
Is there anything else I'd have to upload to diagnose this issue?
The text was updated successfully, but these errors were encountered: