You are not logged in.
While I was rebooting my Arch server today I happened to watch it run through it's whole song / dance during boot up. I saw that one of the lines failed in bright 'red' as it starts up...it was hard to miss.
::Activating RAID arrays = FAIL
::Mounting Root Read-only = DONE
::Checking Filesystems = BUSY
/dev/md0: clean, 55117/45539328 files, 20630896/182142944 blocks
/dev/sda1: clean, 31/250480 files, 36958/1000038 blocks
::Mounting Local Filesystem = DONE
Now the system quickly boots up quickly and beyond seeing the error, no other system issues come up. If you were not paying attention, you wouldn't even know there was a problem. RAID shows everything is up and up. The two drives are synced and persistent. Anyone know why I am seeing this error?
./
Offline
Because I can see it too!!!!
Prediction...This year will be a very odd year!
Hard work does not kill people but why risk it: Charlie Mccarthy
A man is not complete until he is married..then..he is finished.
When ALL is lost, what can be found? Even bytes get lonely for a little bit! X-ray confirms Iam spineless!
Offline
Because I can see it too!!!!
How is that helpful.
./
Offline
Because I can see it too!!!!
LOL .
Well is your system up-to-date? Do you have missconfigured configs like rc.sysinit?
“Talent you can bloom. Instinct you can polish.” — Haikyuu!! (adapted)
“If everybody thought alike, no one would be thinking very much.” — Walter Lippmann (adapted)
“The important thing is to be able, at any moment, to sacrifice what we are for what we could become.” — Charles Dubois
Offline
Before starting a topic, try searching: [mdadm] Activating RAID arrays believes to [FAIL]
This "fail" was introduced when upgrading mdadm from 2.6.x to 3.1.1.
It is a harmless bug in the script. mdadm is trying to assemble arrays that already are assembled on bootup.
Offline