On Friday 14 August 2015 17:01:11 Jeremi Piotrowski wrote:
> On Fri, 14 Aug 2015, Peter Humphrey wrote:
> > > I have now followed Rich's procedure to build the VM, and it does boot -
> > > once!
> > >
> > > After that, on every boot it complains "failed to read the system array"
> > > and
> Any idea what you did between the first boot and the second one? An
> internet search shows that this can happen if the btrfs module doesnt get
> modprobed correctly.
Nothing. Just rebooted. It's repeatable. Well, it was for a while but now I
get the repair shell every time.
> > > So I ran dracut again with add_dracutmodules+=”btrfs” and
> > > add_drivers+=”btrfs” but that didn't help. Specifying
> > > device=/dev/sda4,device=/dev/sdb4 on the kernel command line didn't help
> > > either.
>
> Forget the device thing added to the kernel cmdline, that doesn't work.
Yes, I only tried it as a long shot.
> Can you verify that all pieces of btrfs are present in the initramfs?
> `lsinitrd initramfs.img | grep btrfs` should tell you if that's the case.
> Is btrfs built into the kernel or a module?
Built-in, naturally.
> > Actually, it turns out that the device scan isn't needed: just an exit or
> > control-d is enough.
>
> Check that the kernel cmdline is correct. You need to check the one that
> you provide and the one that is hardcoded into the dracut image. What does
> dracut.log say?
# cat /boot/grub/grub.cfg
root (hd0,1)
timeout 10
Menuentry 'Gentoo Linux 4.0.5, no X {
linux /boot/kernel-x86_64-4.0.5-gentoo root=/dev/sda4 softlevel=nox
net.ifnames-0
initrd /boot/initramfs-4.0.5-gentoo.img
}
# grep initrd /var/log/dracut.log
I: *** Creating initrd image file '/boot/initramfs-4.0.5-gentoo.img' done ***
--->8
# ls -l /boot
--->8
-rw------- 1 root root 6.7M Aug 14 23:22 initramfs-4.0.5-gentoo.img
-rw-r--r-- 1 root root 3.9M Aug 14 23:12 kernel-x86_64-4.0.5-gentoo
--->8
# grep btr /etc/fstab
LABEL=GENTOO / btrfs defaults 0 0
All that seems right to me. The label came from mkfs.btrfs -m raid1 -d raid1
--label=GENTOO /dev/sda4 /dev/sdb4
Adding rootdelay=30 made no difference either. In fact I didn't see such a
pause.
--
Rgds
Peter
