-
Notifications
You must be signed in to change notification settings - Fork 55
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
Thrown into BusyBox on bootup when ZFS is root fs (0.6.5.6-1 Debian Jessie release) #200
Comments
Also seeing this with the new version. |
I'm currently looking at this. Try booting with Also, in the first shell you get, please run Btw, openzfs/zfs#4474 is NOT related. That happens way, way later in the whole startup procedure. You're getting a problem in the |
Better yet, change the @arcenik Does that work? |
@FransUrbo : that does not work, find_rootfs function still return nothing. |
@FransUrbo : the bootfs value for my zfs pool is "-" (which is the default value). Therefore the find_rootfs print nothing and return 1. So initramfs script should change the ZFS_BOOTFS only if find_rootfs return 0 value
|
@arcenik Ok, thanx. That makes sence. |
How's this:
|
@FransUrbo this last variant fixes this issue for me! |
@Fabian-Gruenbichler, perfect thanx! I'll include that in the next update. I'll hold of a little to make sure there isn't any more issues lingering and then I'll build new packages for both Wheezy and Jessie. Expect them in five-six hours (with any luck). |
@FransUrbo instead of checking the content printed by find_rootfs you should check it's return code.
|
@arcenik Even better, thanx! |
@arcenik Actually, that don't seem to work:
However, this works:
|
So how's this:
|
Or possibly even better:
|
This problem also exists a few lines above:
I'm suggesting:
|
Still shouldn't do it if the import isn't successful, which my last examples fix. |
@FransUrbo : I'm trying your last proposal but ${POOLS} is empty on my test system |
It usually is... It's only in a few rare conditions when people have a root pool and a data pool (etc) that that is used. And when you specify |
Do note that there's TWO different places where almost the same code is used, and I showed solutions to both of them. Be sure to apply the correct code to the correct place. |
Closing this as fixed in 0.6.5.6-2 which is on it's way up to the repo now. |
I'll issue new debs right away. |
You could try this : https://github.com/arcenik/debian-zfs-root ;-) |
I usually use that, but I don't have time to set anything up now. I might even have the original VMs around, but I don't have to find them either :). Sorry about the mess-up. |
0.6.5.6-3 just pushed to the repo. |
The version 0.6.5.6-3 is working with my install script. Debian with zfs root is booting without problem. |
This was not the case for 0.6.5.2-2 Debian Jessie release.
@FransUrbo, could this be related to the commit for openzfs/zfs#4474. Note under 0.6.5.2-2 I had no trouble also loading
/usr
,/var
,/var/log
etc. on separate ZFS datasets (openzfs/zfs#4474 (comment))On every startup/reboot I see the following:
Jessie appears to load normally after this point:
Note:
/boot
is on ext4 and both/boot
and/boot/efi
are on a different diskSTEPS to reproduce the issue:
see: http://zfsonlinux.org/debian.html
Install dependencies:
Then:
Prevent disk import as sdX, keep disk import as by-id:
Then remake initramfs:
Create rpool and other pools:
Move files to rpool:
Recreate zpool.cache that goes missing when altroot is used:
Setup /sysroot:
Comment out
/
in/etc/fstab
Under 0.6.5.2-2 there is not need to add
rpool/ROOT/debian-8 / zfs default 0 0
Whether the line above is added or not added to
/etc/fstab
the same issue occurs even when usingzfs set mountpoint=legacy rpool/ROOT/debian-8
.Update initramfs:
Update grub and exit chroot:
The text was updated successfully, but these errors were encountered: