Cannot install native zfs root file system with zfs dailies 0.6.3-22~2d9d57~jessie on Debian Jessie #3047
Comments
|
|
root=ZFS=spool/ROOT/debian Even tried setting the following parameters in /etc/default/grub This issue can be reproduced as follows: VirtualBox Installation of Debian Jessie (tested in RAID 10) Install zfs dailies, |
? It shouldn't matter, both is/should be supported… You say 'mount /boot'. Where is that, on a separate partition or on a ZFS dataset? Previously, you've also said:
This is something outside ZFS… For some reason, it looks like your initrd is broken somehow… I have no idea what could have gone wrong! |
|
My default in /etc/fstab is to was just trying different things to get it to work. Just edited the boot options through the grub menu. None of the following worked: linux /vmlinuz-3.16.0-4-amd64 root=spool/ROOT/debian ro quiet linux /vmlinuz-3.16.0-4-amd64 root=spool/ROOT/debian ro quiet boot=zfs rpool=spool bootfs=spool/ROOT/debian linux /vmlinuz-3.16.0-4-amd64 root=zfs=spool/ROOT/debian ro quiet linux /vmlinuz-3.16.0-4-amd64 root=zfs=spool/ROOT/debian ro quiet boot=zfs rpool=spool bootfs=spool/ROOT/debian Yes /boot is on a separate partition RAID 10 configuration: sda1 - UEFI With the non-dailies, Also when I don't add "boot=zfs rpool=spool bootfs=spool/ROOT/debian" in the grub menu boot command line, the message is slightly different: modprobe: module unknow not found in modules.dep BusyBox v1.22.1 (Debian... /bin/sh: can't access tty; job control tuned off It is possible that zfsutils did not install properly: or The pool imported incorrectly: or Grub is not recognizing zfs as a filesystem: or something else...but whatever it is, for the moment building a native zfs root file system with the dailies install is not working. :( |
And this is also true for any other dataset/filesystem besides /.
|
|
This also happened to me, when installing the zfs dailies 0.6.3-25 yesterday. The install procedure is the same as described by azeemism.
This is what happens, when manually importing the root pool in busybox. Basic setup: mypool/ROOT/debian with mountpoint=legacy |
The pool SHOULD have been imported at that time (or maybe that's the problem, it can't figure out the pool and therefor not the root fs?)… Instead of running 'zpool import' at that time, try running 'zpool status' and see what it say. Also give me the output of "cat /proc/cmdline". |
|
after manually importing the pool: |
|
That's weird� The kernel command line looks just fine� But recovering for now, would be something like: I honestly have no idea what the problem might be :(. Could you just run to make sure that the module actually is 0.6.3-25? Doesn't need to be in the initrd... |
|
ZFS -> 0.6.3-25
|
|
( Your missing the zfs after the -t in your mount command )
|
|
Yeah the 'zfs' was missing here, but it doesn't change the situation on reboot. With manually mounting the pool, as described here, I can boot into the system. But on reboot I have to do it again. |
|
What works (boot without user interaction): So the previous setting with bootfs (-), mountpoint=legacy and using the fstab doesn't work for me. It looks like the boot parameter "boot=zfs rpool=skynet bootfs=skynet/ROOT/debian ro quiet" are ignored. |
|
|
I through the zpool option 'bootfs' is overridden by the boot parameter. That should by true, when multiple OS are present on one pool. Or do you always need at least one valid setting for the zpool option bootfs, which can be then overridden by a different boot parameter? |
|
|
Ok, I think I found something... I rewrote the initrds (the idea was to make it more modular and not so 'spagetti like' in The reason is that although I save all values I needed, they weren't used later (and was overwritten by faulty code to detect them). I'm going to do some testing of this today (and if someone wants to help, I'll be on the ZoL IRC channel). Should have something later. |
|
New versions for both wheezy and jessie daily ( |
|
OK, after updating the reboot is not working again. ~# zpool get bootfs skynet ~# zfs list -r skynet
After importing and mounting manually and exiting twice the system boots. But now even with bootfs property set, it doest't boot without user interaction. |
|
Have a look at Please give me the output of the following command line: From the looks of it, it's still using the old initrd scripts... |
|
The initrd was updated before reboot. root@skynet:/etc/initramfs-tools# ls -l /etc/initramfs-tools/*/zfs
ls: Zugriff auf /etc/initramfs-tools/*/zfs nicht möglich: Datei oder Verzeichnis nicht gefunden
root@skynet:/etc/initramfs-tools# ls -l /usr/share/initramfs-tools/*/zfs
-rw-r--r-- 1 root root 61 Feb 8 19:24 /usr/share/initramfs-tools/conf-hooks.d/zfs
-rwxr-xr-x 1 root root 2969 Feb 8 19:26 /usr/share/initramfs-tools/hooks/zfs
-rw-r--r-- 1 root root 17541 Feb 8 19:26 /usr/share/initramfs-tools/scripts/zfs |
|
Ok, then we're back to me having no clue :( |
|
Close as stale. If it's actual - feel free to reopen. |
Hi,
At first reboot, the screen freezes with the following message:
mount: mounting /sys on /root/sys failed: No such file or directory
mount: mounting /proc on /root/proc failed: No such file or directory
/init: line 335: can't open /root/dev/console: no such file
...
[end Kernel panic - not syncing: attempting to kill init! exitcode=0x00000200
After a cold boot the following message appears:
sh: argument expected <- repeated 4 times
Command: mount -o zfsutil -t zfs - /root
Message: filesystem '-' cannot be mounted, unable to open the dataset
mount: mounting - on /root failed: No such file or directory
Error: 1
Manually mount the root filesystem on /root and then exit.
BusyBox v1.22.1 (Debian ...
/bin/sh: can't access tty; job control turned off
/#
Install procedure outlined in #3046, apart from correcting root=ZFS=, unmounting /boot, /sys, /proc, exiting chroot, exprorting the pool, and rebooting. This may also be related to #3045 and perhaps even #3044 .
I have had no issue with this install process under the non-dailies zfs version (v0.6.3-766_gfde0d6d) even with /boot within the zpool. I was hoping to use the dailies version with the latest fixes, but that unfortunately doesn't look hopeful now.
Thanks for all that you do,
Azeem
The text was updated successfully, but these errors were encountered: