Siduction Forum

Siduction Forum => Installation - Support => Topic started by: steve on 2018/01/31, 20:20:00

Title: Error booting system: no arrays found
Post by: steve on 2018/01/31, 20:20:00

Greetings,

Upon boot, I am getting this error:

"running scripts/local-block...mdadm no arrays found in config file or automatically'

What I tried:

• Searching the siduction wiki and did not find anything helpful for me
• Searched google and saw similar problems but I could not figure out what do do really
• I fsck my filesystem like: fsck -u /dev/mapper/vg01-lv_siduction with no errors
• chrooted into siduction from another system and tried to run update-initiramfs -u but got similar error about no arrays

Any tips or pointers to online solutions appreciated! Tks
My system:
Lenovo Thinkpad T440p, Siduction Lxqt, updated regularly per wiki instructions, and running well for months.

Title: Re: Error booting system: no arrays found
Post by: melmarker on 2018/01/31, 20:47:53

it isn't a bug, just the reality if you don't have a soft raid in your system - in that case 'apt purge mdadm' would help a lot.

Title: Re: Error booting system: no arrays found
Post by: steve on 2018/01/31, 21:01:14

Thanks for the reply.

I chrooted in and ran `apt purge mdadm` which completed without error.

When I exit and reboot, error changes slightly to

`Begin: running /scripts/local-block ... done`

this repeats until the system fails at the initramfs prompt. This is the place where the other failure would sette also.

Any pointer what to do at this point?

Thanks!

Title: Re: Error booting system: no arrays found
Post by: melmarker on 2018/01/31, 21:53:07

update your initramfs

Code: [Select]

% apt-file search  /scripts/local-block
cryptsetup: /usr/share/initramfs-tools/scripts/local-block/cryptroot
lvm2: /usr/share/initramfs-tools/scripts/local-block/lvm2
mdadm: /usr/share/initramfs-tools/scripts/local-block/mdadm

it might be a problem with initramfs-tools

Title: Re: Error booting system: no arrays found
Post by: steve on 2018/02/01, 21:20:50

Ok, thanks for reply.

Running this:

Quote

update-initramfs -u
update-initramfs: Generating /boot/initrd.img-4.15.0-towo.1-siduction-amd64

And rebooting from chroot gives similar error about 30 times:

Quote

Begin running /scripts/local-block ...done

And then it went on to suggest possible reasons for the error:

Check the command line:

Code: [Select]

cat /proc/cmdline
BOOT_IMAGE=/vmlinuz root=UUID=838239a...115a # I truncated UUID for here

Note: Previously, the root device pointed to dm-6 but I changed to UUID to test. Neither work and both give the same error.

Check for missing modules:

Code: [Select]

cat /proc/modules

Many show up but lvm does not. Should it?

Check /dev/:

Code: [Select]

ls -l /dev

Many show up including /dev/sda b c as expected, but there is no reference to dm-6

Not really sure about any of this, but it seems to me that since my root filesystem and kernel files reside in a LVM volume (as is my practise everywhere, including my Stretch install), is the problem that the initramfs environment can not see LVM volumes?

Thanks again for your help and this great distro.

-Steve.