You are not logged in.
Pages: 1
This is more of a warning to people using RAID than anything else.
I had a RAID 1 array with 2 HDDs for my /home directory.
After a recent standard update (pacman -Syu) I found out that my system was failing to boot because it could not find /dev/md127 which was my RAID 1.
I quickly found out that I no longer had any /dev/md* and no /proc/mdstat.
Those were completely erased by the update.
Everything I read regarding recovering broken RAID arrays assumed that at least a /proc/mdstat was present, which it wasn't.
I could not attach the drives to a new RAID array, because the drives assumed they were part of a former RAID that I could no longer edit.
I managed to recover the data in my /home directory by mounting one of the drives as read-only using a loop device.
I then completely wiped the other HDD, copied the files to that disk and mounted it normally to /home, so I was saved.
I need the /home redundancy for my work files, so for now I'm using the other drive as a backup with periodic rsyncs.
For the time being I will be forgoing RAID 1 for backup until I understand what really happened.
Any ideas about what happened and what I could have done differently are much appreciated, including if RAID 1 is a good idea for people who want to have a backup.
Offline
Offline
Thank you! Will follow the issue on that post.
Offline
Pages: 1