Re: [Libreboot] ERROR: device '/dev/matrix/root' not found. Skipping fsck

[Daniel Tarrero]

oh, so it was that you miss to load the LVM module in the init.rd, isnt
it?
given it wasnt loaded on boot, neither your drive got mapped into
/dev/mapper/<whatever>, so it was not located :)

nice you solved it :)


On Fri, May 06, 2016 at 06:52:17PM +0200, Michael Bohn wrote:
> Problem is solved  I forgot the hook part "HOOKS="base udev autodetect
> modconf block keyboard keymap consolefont encrypt lvm2 filesystems fsck
> shutdown"
> 
> THX
> 
> 2016-05-06 17:39 GMT+02:00 Michael Bohn <address@hidden>:
> 
> >   I use UUID ( see fstab ) may be it's a lvm problem because  at the  at
> > the [rootfs ]#  I did not find  a folder like /dev/mapper  (only
> >  /dev/mcelog  /dev/mem /devmemory_bandwidth)
> >
> > 2016-05-06 17:36 GMT+02:00 Michael Bohn <address@hidden>:
> >
> >> I use UUID ( see fstab ) may be ist a lvm problem because  at the
> >>
> >>
> >>
> >>
> >> [rootfs ]# ls  /dev/*
> >> /dev/mcelog
> >>
> >>
> >>
> >> address@hidden ~ # lvdisplay
> >>   --- Logical volume ---
> >>   LV Path                /dev/matrix/swapvol
> >>   LV Name                swapvol
> >>   VG Name                matrix
> >>   LV UUID                9N3M0R-7v2I-9WLy-d7aN-5XiY-1rAw-WQ8YYt
> >>   LV Write Access        read/write
> >>   LV Creation host, time parabolaiso, 2016-05-02 00:52:34 +0000
> >>   LV Status              available
> >>   # open                 0
> >>   LV Size                8.00 GiB
> >>   Current LE             2048
> >>   Segments               1
> >>   Allocation             inherit
> >>   Read ahead sectors     auto
> >>   - currently set to     256
> >>   Block device           254:2
> >>
> >>   --- Logical volume ---
> >>   LV Path                /dev/matrix/root
> >>   LV Name                root
> >>   VG Name                matrix
> >>   LV UUID                FU487N-719J-rJGp-hH1p-sDC3-Xooz-ghzMyO
> >>   LV Write Access        read/write
> >>   LV Creation host, time parabolaiso, address@hidden ~ # lvdisplay
> >>   --- Logical volume ---
> >>   LV Path                /dev/matrix/swapvol
> >>   LV Name                swapvol
> >>   VG Name                matrix
> >>   LV UUID                9N3M0R-7v2I-9WLy-d7aN-5XiY-1rAw-WQ8YYt
> >>   LV Write Access        read/write
> >>   LV Creation host, time parabolaiso, 2016-05-02 00:52:34 +0000
> >>   LV Status              available
> >>   # open                 0
> >>   LV Size                8.00 GiB
> >>   Current LE             2048
> >>   Segments               1
> >>   Allocation             inherit
> >>   Read ahead sectors     auto
> >>   - currently set to     256
> >>   Block device           254:2
> >>
> >>
> >> grub> cryptomount -a
> >> grub> set root='lvm/matrix-root'
> >> grub> linux /boot/vmlinuz-linux-libre-lts root=/dev/matrix/root
> >> cryptdevice=/dev/sda1:root
> >> grub> initrd /boot/initramfs-linux-libre-lts.img
> >> grub> boot
> >>
> >> address@hidden ~ # cat /mnt/etc/fstab
> >> #
> >> # /etc/fstab: static file system information
> >> #
> >> # <file system> <dir> <type> <options> <dump> <pass>
> >> # /dev/mapper/matrix-root
> >> UUID=c059559b-682a-44ed-b81f-902dc39ec3fe /         ext4
> >> rw,relatime,data=ordered 0 1
> >>
> >> # /dev/mapper/matrix-swapvol
> >> UUID=e59285f7-a291-49f2-8b29-6385752ed228 none       swap       defaults
> >>   0 0
> >>
> >>
> >> 2016-05-06 17:14 GMT+02:00 Daniel Tarrero <address@hidden>:
> >>
> >>> have you used UUIDs or labels when "Configure the system"?
> >>> in the past, use of UUIDs in the place of labels has solved similar
> >>> problems (locating the drives).
> >>>
> >>> There seem to be some glitches with hardware ordering, and f.e. docking
> >>> and undocking the laptop causes the drives to change its label (making
> >>> boot loader unable to locate drive). With the use of UUIDs this dont
> >>> happen (UUIDs doesnt change regardless you move or change hardware).
> >>>
> >>> Let us know if that solves the problem.
> >>>
> >>> Regards,
> >>> D
> >>>
> >>>
> >>>
> >>> On Fri, May 06, 2016 at 04:34:10PM +0200, Michael Bohn wrote:
> >>> > Hy All,
> >>> > if I follow the howto "Installing Parabola GNU/Linux with full disk
> >>> > encryption" at
> >>> >  https://libreboot.org/docs/gnulinux/encrypted_parabola.html I 'm
> >>> unable to
> >>> > boot the system.
> >>> >
> >>> > Waiting 10 seconds for device /dev/matrix/root
> >>> > ERROR: device '/dev/matrix/root' not found. Skipping fsck
> >>> > ERROR: Unable to find root device '/dev/matrix/root'
> >>> >
> >>> >
> >>> > Did body knows  what's the reason for this error ?
> >>> >
> >>> >
> >>> > Michael
> >>>
> >>>
> >>
> >