You are not logged in.
Pages: 1
Hi all!
Had a bad day today:
I had to take down the server on the power. When booting up again, it booted to rescue mode, because of faulty raid.
Md2, was inactive. Ok, to re-add missing device and start array.
Md3, also inactive. "mdadm -D /dev/md3", says it is an raid 0 array!, with 4 working devices. But it should be an raid 5!
/etc/fstab contained another uuid than mdadm reported. Editet fstab.
I had an old /etc/mdadm/mdadm.conf, with more info than just only array names and uuid. changed to that and have the info: "level=raid5 num-devices=4" after "ARRAY /dev/md/3" .
Fdisk reported the partions containing md3 to have an Linux File system. Changed the type to raid.
Mdadm still reports the array to be raid 0!.
Now I do not know what to do.
Last edited by rbh (2020-10-09 07:30:56)
// Regards rbh
Offline
I tested running
mdadm --assemble --verbose --run --force /dev/md124 /dev/sda4 /dev/sdb4 /dev/sdc4 /dev/sdd4
The array started with disk a to c as raid5. Stopped it and added sdd4. Restarted pc. The partition was not mounted, had made an error in fstab. Now tre disks again, sda offline.
Well, it will be solved after refrreshing sleep..
// Regards rbh
Offline
After the server been started this morning, I after 20 min, checked raid, /dev/md3 had been started with 4 devices, active in raid 5.
mdadm reported:
~# mdadm --examine /dev/sd[a-d]4 | egrep 'Event|/dev/sd'
/dev/sda4:
Events : 6687
/dev/sdb4:
Events : 6686
/dev/sdc4:
Events : 6686
/dev/sdd4:
Events : 6686
Sda4 is back without more intervention...
// Regards rbh
Offline
Pages: 1