As far as why I was in /mnt... I had to be somewhere.
No you don't, you login or ssh in as root and run the command, there is no need to change to any directory.
Have you the output of what I asked for please.
Lost all drives
-
-
The raid is in auto-read-only that's why you can't see a file system;
mdadm --stop /dev/md0
mdadm --readwrite /dev/md0
when that's completed;
omv-mkconf fstab
post the output of; when it's all completed
cat /proc/mdstat
cat /etc/fstab
-
mdadm: /dev/md0 does not appear to be active.
Interesting it usually complains that it's running, ok as it's stopped mdadm --run /dev/md0 then run --readwrite
-
This is odd, what's the output of cat /proc/mdstat
-
Ok that's why, reboot the machine and check cat /proc/mdstat if it shows the same as your post 20 active (auto-read-only) then run the --readwrite command. If it's the same as the above it will need to be assembled again
-
I did notice that as the system came back up it ran an fsck on the raid and corrected errors.
Sometimes a reboot just resolves what appears to be the obvious.
Now that its back can you give me a synopsis of what happened?
The power outage caused the problem and probably poorly seated connections, but because mdadm is software if something goes wrong it doesn't know what it is, unlike a hardware raid. So you have to execute a few commands to find the cause the main one here being cat /proc/mdstat, that gives you the state of the array, blkid tells you what drives are part of it, from there you can make a start in putting it back together.
The most common problem for raid errors are power loss, and a user assuming that mdadm is 'hot swap', which it isn't, a swapped out drive causes the array to go inactive because it wasn't removed from mdadm.
In the UK power cuts are rare but I know from US users a UPS is a recommended necessity.But at least it's running again
-
Anyway to get that B drive back in without wiping it first?
Ok I'm at a loss with that, is that a USB drive? -
No, same sata 8 gig drive as the others. It dropped out after the reboot
Ok, is it Storage -> Disks
blkid
mdadm --detail /dev/md0
-
2 0 0 2 removed
In the GUI select the raid and click on recover, a dialog comes up, if /dev/sdb is shown select it (check box) click OK, if not come back.
-
I've had this happen before and from the gui I can only get the missing drive back in if I wipe it first.
That's the correct way to do it, but we could try this first,
mdadm --stop /dev/md0
mdadm --add /dev/sdb /dev/md0
Jetzt mitmachen!
Sie haben noch kein Benutzerkonto auf unserer Seite? Registrieren Sie sich kostenlos und nehmen Sie an unserer Community teil!