#1 2022-12-29 06:29:43

RIP_eng57

Member

Registered: 2022-12-24

Posts: 5

Getting boot errors after new install Beryllium

I just installed Beryllium. And I'm getting a couple of errors repeatedly.

mdadm: No arrays found in config file or automatically
cryptsetup: WARNING: mmcblk1p2_crypt: couldn't determine device type, assuming default plain

After doing some research it appears the first one is common and it can be ignored if you dont use "RAID" and also the file /etc/mdadm/mdadm.conf can be edited by adding

ARRAY <ignore> devices=/dev/xxx

which will get rid of the error, which slows down boot by about a min mind you.

Ive never used 'RAID", but I want to be sure before I go removing/editing. I checked the logs with "journalctl | grep raid" and it gave me

I guess its a kernel module loading or raid algorithm....Idk? So how can i safely get rid of this error or can you point me in the right direction please where i can try to figure it out?

Also with the 2nd error I'm thinking its probably not cool to post 2 different errors/questions in same post now that i think about it. so Ill wait for a veteran member to lmk.  I don't think I left anything out besides maybe

 uname -a
Linux charger 5.10.0-20-amd64 #1 SMP Debian 5.10.158-2 (2022-12-13) x86_64 GNU/Linux

hhh

Gaucho

From: High in the Custerdome

Registered: 2015-09-17

Posts: 16,140

Website

Re: Getting boot errors after new install Beryllium

If you get a boot error (I assume these are boot errors) and it says it's a "warning" and not a "Fail" and the system still boots, it's probably safe to ignore the warning.

It's a Linux kernel error for your specific hardware, probably. If the workaround to suppress the warning slows your boot down, ditch the workaround unless you really hate seeing the warning, Or install Plymouth so you don't see it (though that will slow your boot time down as well).

Does the system boot? If it ain't broke, don't fix it.

---

I don't care what you do at home. Would you care to explain?

johnraff

nullglob

From: Nagoya, Japan

Registered: 2015-09-09

Posts: 12,654

Website

Re: Getting boot errors after new install Beryllium

If you get a boot error (I assume these are boot errors) and it says it's a "warning" and not a "Fail" and the system still boots, it's probably safe to ignore the warning.

Cryptic warnings are not uncommon, but anyway if you're not using RAID you can safely remove mdadm:

sudo apt remove mdadm

---

...elevator in the Brain Hotel, broken down but just as well...
( a boring Japan blog (currently paused), now on Bluesky, there's also some GitStuff )

Introduction to the Bunsenlabs Boron Desktop