Saturday, January 2, 2010, at 2:00 PM

Just rescued my (software) RAID5.

Yesterday, after rebooting my home server, I noticed I couldn't access any of its data, which sits on a normally fine software RAID5 device. When trying to mount the device, I always got the following error: "mount: /dev/md0 already mounted or /mnt/share busy".

I tried rebooting: fail.

I messed a bit with my /etc/fstab config file: fail.

Suspecting the mdadm config file could be the culprit, I uninstalled, then reinstalled mdadm, to make sure it regenerates its config file: fail again.

After some long (and panicking) minutes, I found this savior's post:
http://matthew-garman.blogspot.com/2009/12/device-already-mounted-or-mountpoint.html.

Just a quick note though: make sure to remove ("comment out") the necessary entry in your /etc/fstab config file, then reboot, before attempting to run e2fsck. If not, the device may be "busy", probably trying to be mounted, and the scan won't launch. Then, after all is repaired, restore your original fstab file content, and remount your device. VoilĂ !

No comments:

Post a Comment