Recover software raid after system crash

nacht · 27. November 2012

So here is my situation...
i had a perfectly good media server running on these 2 drives. sharing music and Movies throughout the house. when my 1.5 year old puppy thought it would be helpful to knock the plug out of the wall on my NAS (how the hell she got back behind where it was plugged is beyond me, but she did). so system would not boot up again and gave me all kinds of errors ( i still have the flash stick that install was on). So in an effort to get this going again I got a new stick and installed a newer version of OMV (Old one was 0.2.7 i think now i am on 0.3.6) and once installed i added back in the 2 drives (info below) now it sees my raid and it saw the filesystem so i tired to mount it and it gave me a "can not mount duplicate mount point error" so i logged out swapped the drives position on the controller card and reloaded. this time during boot up it gave me a "can not mount" kind of error on UUID : 4e4fdb41:ff056f4a:4479a0bb:3518d220 and asked me to run some kind of fsck maintenance on it so i typed in the fsck command with -a and and it warned me that the file system was mounted and it would wreck it... so i aborted, rebooted again and this time skipped the maintenance. When i loaded up this time it showed the disk as mounted. So i unmounted it and then it disappeared completely.

So I am at a loss as to what to do i want to most importantly save my data if its still there and ideally recover this raid as is and keep using it.

at this point i don't remember which was plugged into ide1 and which was in ide2 (each were on its own channel) i don't remember what file system i used i do remember the name of the 2 folders (maybe they were called mount points) one was audio the other was video. but any help would be very appreciated.

Code

Version : 1.2
  Creation Time : Sun May  6 16:19:06 2012
     Raid Level : raid0
     Array Size : 625139712 (596.18 GiB 640.14 GB)
   Raid Devices : 2
  Total Devices : 2
    Persistence : Superblock is persistent


    Update Time : Sun May  6 16:19:06 2012
          State : clean
 Active Devices : 2
Working Devices : 2
 Failed Devices : 0
  Spare Devices : 0


     Chunk Size : 512K


           Name : openmediavault:WDBlue  (local to host openmediavault)
           UUID : 4e4fdb41:ff056f4a:4479a0bb:3518d220
         Events : 0


    Number   Major   Minor   RaidDevice State
       0       8       16        0      active sync   /dev/sdb
       1       8        0        1      active sync   /dev/sda

Alles anzeigen

nacht · 19. Dezember 2012

sorry to have to bump this, i am about to go into some cancer treatment and would love to get at the Videos on this drive any help on how to get this mounted would be great.

thanks in advance!

ryecoaaron · 19. Dezember 2012

I would unplug the two raid drives and reinstall version 0.4 on another hard drive (not a flash stick). Then plug the raid drives back in. It will find them and you can mount them. Moving drives to different positions won't change anything because they are recognized by their UUID wherever they are.

nacht · 28. Dezember 2012

ok so i did this and still not able to mount. they still show up in raid management as clean. but under filesystem they are completely gone any suggestions would be great.

http://linux-tips.org/article/…as-duplicate-uuid-problem

i found this article and wondered if there was a way to get at it from a command line and find/force it to mount?

ryecoaaron · 28. Dezember 2012

What is the output from the following commands run as root from command line:

fdisk -l
cat /proc/mdstat
blkid
mount

nacht · 28. Dezember 2012

fdisk -l

Code

Disk /dev/sda: 320.1 GB, 320072933376 bytes
255 heads, 63 sectors/track, 38913 cylinders
Units = cylinders of 16065 * 512 = 8225280 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 512 bytes / 512 bytes
Disk identifier: 0x00000000


Disk /dev/sda doesn't contain a valid partition table


Disk /dev/sdb: 320.1 GB, 320072933376 bytes
255 heads, 63 sectors/track, 38913 cylinders
Units = cylinders of 16065 * 512 = 8225280 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 512 bytes / 512 bytes
Disk identifier: 0x00000000


Disk /dev/sdb doesn't contain a valid partition table


Disk /dev/sdc: 4009 MB, 4009754624 bytes
124 heads, 62 sectors/track, 1018 cylinders
Units = cylinders of 7688 * 512 = 3936256 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 512 bytes / 512 bytes
Disk identifier: 0x0001a3d3


   Device Boot      Start         End      Blocks   Id  System
/dev/sdc1   *           1         963     3700736   83  Linux
Partition 1 has different physical/logical beginnings (non-Linux?):
     phys=(0, 32, 33) logical=(0, 33, 3)
Partition 1 has different physical/logical endings:
     phys=(460, 216, 12) logical=(962, 123, 38)
Partition 1 does not end on cylinder boundary.
/dev/sdc2             964        1019      211969    5  Extended
Partition 2 has different physical/logical beginnings (non-Linux?):
     phys=(460, 248, 43) logical=(963, 32, 39)
Partition 2 has different physical/logical endings:
     phys=(487, 92, 53) logical=(1018, 50, 20)
Partition 2 does not end on cylinder boundary.
/dev/sdc5             964        1019      211968   82  Linux swap / Solaris


Disk /dev/md127: 640.1 GB, 640143065088 bytes
2 heads, 4 sectors/track, 156284928 cylinders
Units = cylinders of 8 * 512 = 4096 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 524288 bytes / 1048576 bytes
Disk identifier: 0x00000000


Disk /dev/md127 doesn't contain a valid partition table

Alles anzeigen

cat /proc/mdstat

Code

Personalities : [linear] [multipath] [raid0] [raid1] [raid6] [raid5] [raid4] [raid10] 
md127 : active raid0 sdb[0] sda[1]
      625139712 blocks super 1.2 512k chunks

blkid

Code

/dev/sda: UUID="4e4fdb41-ff05-6f4a-4479-a0bb3518d220" LABEL="openmediavault:WDBlue" TYPE="linux_raid_member" 
/dev/sdb: UUID="4e4fdb41-ff05-6f4a-4479-a0bb3518d220" LABEL="openmediavault:WDBlue" TYPE="linux_raid_member" 
/dev/sdc1: UUID="0611a596-1078-4881-9297-183271013b69" TYPE="ext4" 
/dev/sdc5: UUID="32c924d7-7bd1-4094-8755-f6c779f7a0f1" TYPE="swap"

mount

Code

/dev/sdc1 on / type ext4 (rw,errors=remount-ro)
tmpfs on /lib/init/rw type tmpfs (rw,nosuid,mode=0755)
proc on /proc type proc (rw,noexec,nosuid,nodev)
sysfs on /sys type sysfs (rw,noexec,nosuid,nodev)
udev on /dev type tmpfs (rw,mode=0755)
tmpfs on /dev/shm type tmpfs (rw,nosuid,nodev)
devpts on /dev/pts type devpts (rw,noexec,nosuid,gid=5,mode=620)
tmpfs on /tmp type tmpfs (rw)

ryecoaaron · 28. Dezember 2012

Try this as root:

mount /dev/md127 /media/4e4fdb41-ff05-6f4a-4479-a0bb3518d220

If it complains the directory doesn't exist, add this command before trying the previous command again:

mkdir /media/4e4fdb41-ff05-6f4a-4479-a0bb3518d220

nacht · 28. Dezember 2012

mkdir /media/4e4fdb41-ff05-6f4a-4479-a0bb3518d220

Code

mount: you must specify the filesystem type

ryecoaaron · 28. Dezember 2012

I just looked at your output again and your raid array (/dev/md127) doesn't have a uuid. So, the uuid I told you to use was for the drives not the array.

You can try this command but I don't think it will work:

mount -t ext4 /dev/md127 /media/4e4fdb41-ff05-6f4a-4479-a0bb3518d220

I would also try booting an Ubuntu cd to see if it sees the array.

nacht · 29. Dezember 2012

mount -t ext4 /dev/md127 /media/4e4fdb41-ff05-6f4a-4479-a0bb3518d220

Code

mount: mount point /media/4e4fdb41-ff05-6f4a-4479-a0bb3518d220 does not exist

i am trying a ubuntu CD now

nacht · 29. Dezember 2012

Ok i booted Ubuntu 10.04 from disk and was able to see the "Array" but would not let me mount it

error was

Code

Unable to mount Location
Can't mount file

ryecoaaron · 29. Dezember 2012

I was hoping it would automount in ubuntu.

What does cat /proc/mdstat tell you under Ubuntu?

nacht · 30. Dezember 2012

cat /proc/mdstat

Code

Personalities:
unused devices: <none>

SerErris · 2. Januar 2013

If this is the whole output of your /proc/mdstat then the kernel have no raid modules loaded (no personalties listed).

That is the reason why you do not see anything here.

Jetzt mitmachen!