-
Notifications
You must be signed in to change notification settings - Fork 18
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
grub-probe adds trailing slash (if root is on the root dataset). #15
Comments
You should really have create a separate dataset for the root and not put them in the root dataset. But it should work any way (possibly removing that slash). But only testing will tell (I've never seen this type of setup before so you'll be the first to confirm :).
Oh, yes!! I've basically rewritten the initrd scripts, supporting a ton of more PS. This is really a support question, not a bug/issue. If you could be so kind to close this and continue this on the mailing list, I'd be most grateful. |
Okidoki - I'd have done that earlier if it had been clearer that said "mailing list" is actually a Google Group not requiring subscription to YAML :) |
Reopened as requested [https://groups.google.com/a/zfsonlinux.org/d/msg/zfs-discuss/hHzJ3GwmKE8/fMHg6G8I3jsJ] and relabeled. I am not able to confirm nor infirm that no trailing slash is added when the OS root is NOT in the root dataset, so I put that condition in parentheses. |
But the label is ok. I'll look into this when I have more time. |
Reading the upgrade-from-0.6.2 readme that comes with one of the updated packages for Debian (but not on Ubuntu???!) I see that nowadays grub.cfg should have kernel cmdline entries that read something like
{{{
bootfs=rpool/ROOT/debian-1 boot=zfs ro
}}}
(or
bootfs=Patux boot=zfs ro
in my case).However, even with the latest grub-pc, grub-pc-bin, grub-common and grub2-common from the ZoL Debian repo, I get a grub.cfg with entries that still have
{{{
root=ZFS=Patux/ ro boot=zfs $bootfs
}}}
with $bootfs defined as
zfs-bootfs ($root) bootfs
Is this equivalent?
That's both under Debian (Testing) and under Ubuntu 14.04, btw. When I first rebooted my Ubuntu rig after today's upgrades, I was dumped at the busybox prompt because of a pool import failure. The bootstrap actually tried to import rpool (which I don't have) ... but it had already imported the correct pool. Is that due to the grub.cfg entry, or an issue with the new zfs-initramfs 0.6.3-2~trusty version? (Or maybe I should ask if the zfs-initramfs in the Debian repo is actually more recent/correct than the version for Ubuntu? ;) )
The text was updated successfully, but these errors were encountered: