On 9 January 2011 13:45, Paul Richards <[email protected]> wrote: > On 9 January 2011 12:37, Pascal Hambourg <[email protected]> wrote: >> Paul Richards a écrit : >>> >>> I figured out how to add crc32 to the initramfs, but unfortunately I >>> get the same error. It's unfortunate that the error message does not >>> tell me which symbol is missing, as perhaps including another modulre >>> in the initramfs would help. >> >> Did you look at the output of dmesg as the message suggested ? >> The initramfs should start a shell after failing to mount the root >> filesystem (be patient, this may take some time). >> In the installer/rescue shell, you could also check the module >> dependency with lsmod. >> > > I tried this procedure again but used a shotgun approach to picking > which extra modules to put into the initramfs. > > From the installer VT (at step 3 in my procedure above) I executed: > > lsmod | sed 's%[ \t].*$%%' >> /etc/initramfs-tools/modules > > This has probably led to a bloated ramfs, but the system now boots > with btrfs as the root filesystem. :) > > Thanks everyone for your help. >
A simpler solution appears to be installing 'btrfs-tools' during install. This package drags in some initramfs-tools magic[1] that causes the correct modules to be put into the initramfs. This is far more elegant than hacking /etc/initramfs-tools/modules 1: http://packages.debian.org/squeeze/amd64/btrfs-tools/filelist -- Paul Richards @pauldoo -- To UNSUBSCRIBE, email to [email protected] with a subject of "unsubscribe". Trouble? Contact [email protected] Archive: http://lists.debian.org/[email protected]
