Raid 5 degraded...:(

Dannermax · 3. November 2013

Hey.

I dont know what i did, but i was trying to install ubuntu as a 2.nd os, and i tried to mount the raid with mdadm through webmin. I didn't know what i did, because when i restarted it told me that 1 disk had failed and that the raid had been degraded..arghh!!

I installed OMV again, and the degraded state is the same:

Code

root@openmediavault:~# cat /proc/mdstat
Personalities : [linear] [multipath] [raid0] [raid1] [raid6] [raid5] [raid4] [raid10]
md127 : active raid5 sdb[1] sdd[3] sdc[2]
      8790795264 blocks super 1.2 level 5, 512k chunk, algorithm 2 [4/3] [_UUU]

and:

Code

root@openmediavault:~# fdisk -l


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


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


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


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


Disk /dev/sdc: 3000.6 GB, 3000592982016 bytes
255 heads, 63 sectors/track, 364801 cylinders
Units = cylinders of 16065 * 512 = 8225280 bytes
Sector size (logical/physical): 512 bytes / 4096 bytes
I/O size (minimum/optimal): 4096 bytes / 4096 bytes
Disk identifier: 0x00000000


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


Disk /dev/sdd: 3000.6 GB, 3000592982016 bytes
255 heads, 63 sectors/track, 364801 cylinders
Units = cylinders of 16065 * 512 = 8225280 bytes
Sector size (logical/physical): 512 bytes / 4096 bytes
I/O size (minimum/optimal): 4096 bytes / 4096 bytes
Disk identifier: 0x00000000


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


Disk /dev/sde: 80.0 GB, 80026361856 bytes
255 heads, 63 sectors/track, 9729 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: 0x000ad6af


   Device Boot      Start         End      Blocks   Id  System
/dev/sde1   *           1          32      248832   83  Linux
Partition 1 does not end on cylinder boundary.
/dev/sde2              32        9730    77899777    5  Extended
/dev/sde5              32        9730    77899776   8e  Linux LVM


Disk /dev/md127: 9001.8 GB, 9001774350336 bytes
2 heads, 4 sectors/track, -2097268480 cylinders
Units = cylinders of 8 * 512 = 4096 bytes
Sector size (logical/physical): 512 bytes / 4096 bytes
I/O size (minimum/optimal): 524288 bytes / 1572864 bytes
Disk identifier: 0x00000000


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


Disk /dev/sdf: 2063 MB, 2063597568 bytes
64 heads, 62 sectors/track, 1015 cylinders
Units = cylinders of 3968 * 512 = 2031616 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 512 bytes / 512 bytes
Disk identifier: 0x000757b8


   Device Boot      Start         End      Blocks   Id  System
/dev/sdf1   *           1         947     1876992   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=(233, 204, 35) logical=(946, 37, 10)
Partition 1 does not end on cylinder boundary.
/dev/sdf2             948        1016      135169    5  Extended
Partition 2 has different physical/logical beginnings (non-Linux?):
     phys=(233, 237, 3) logical=(947, 6, 11)
Partition 2 has different physical/logical endings:
     phys=(250, 193, 7) logical=(1015, 14, 28)
Partition 2 does not end on cylinder boundary.
/dev/sdf5             948        1016      135168   82  Linux swap / Solaris


Disk /dev/dm-0: 75.6 GB, 75606523904 bytes
255 heads, 63 sectors/track, 9191 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/dm-0 doesn't contain a valid partition table


Disk /dev/dm-1: 4160 MB, 4160749568 bytes
255 heads, 63 sectors/track, 505 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/dm-1 doesn't contain a valid partition table
root@openmediavault:~#

Alles anzeigen

In the OMV web interface, the state of the array is clean, degraded, and the array info is as such:

Version : 1.2
Creation Time : Fri Mar 22 15:53:45 2013
Raid Level : raid5
Array Size : 8790795264 (8383.56 GiB 9001.77 GB)
Used Dev Size : 2930265088 (2794.52 GiB 3000.59 GB)
Raid Devices : 4
Total Devices : 3
Persistence : Superblock is persistent

Update Time : Sun Nov 3 13:20:46 2013
State : clean, degraded
Active Devices : 3
Working Devices : 3
Failed Devices : 0
Spare Devices : 0

Layout : left-symmetric
Chunk Size : 512K

Name : openmediavault:nas (local to host openmediavault)
UUID : 25ebd78d:be752afc:2a3c1956:5c326984
Events : 468

Number Major Minor RaidDevice State
0 0 0 0 removed
1 8 16 1 active sync /dev/sdb
2 8 32 2 active sync /dev/sdc
3 8 48 3 active sync /dev/sdd

Im feel very stupid, because i tampered with something i shouldent have...And i cant select any devices under raid - recover... What to do?

endstille · 3. November 2013

Hey Dannermanx,

i might be wrong, but i recognized, that your sda seems to be missing and currently has no working partition table:
"Disk /dev/sda doesn't contain a valid partition table"
"Number Major Minor RaidDevice State
0 0 0 0 removed
1 8 16 1 active sync /dev/sdb
2 8 32 2 active sync /dev/sdc
3 8 48 3 active sync /dev/sdd"

Have you tried, hitting "recover" in the web interface and then selecting sda and proceed?
i think once you installed ubuntu, it altered this harddisk and this is your problem now.
Maybe you can also try to wipe it through web interface and then recover your raid.
Just be sure NOT to mix these two operations... i was stupid enough to do it, once everything was new and so i killed about 1/3 of all my files (yeah 1/3 of each file, rendering most stuff broken...)

Basically i would advice not to rush anything

BR Marc

Dannermax · 3. November 2013

Hey marc.

Ehen i hit recover, there is nothing to select.. That is what makes this so wierd.

This is what i can see when hitting recover:

http://img41.imageshack.us/img41/4413/vnpo.jpg

Nothing to select... What can i do?
Ill try not to rush it.. But it is so uncomftable knowing that my data might be lost...

tekkb · 3. November 2013

You might want to wait for Ryeco to take a look at this and let him tell you what to do.

davidh2k · 3. November 2013

On your own risk: I think you need to wipe sda first...

Greetings
David

ryecoaaron · 3. November 2013

David is right. Try wiping it first and then using the recover. If that doesn't work, we should be able to fix it from the command line. As long as it is just one drive, your data should be safe.

Dannermax · 4. November 2013

The sda is not a part of my raid 5 array, its an 80gb harddrive i use for the OS.. And if wiping that dosent work, i should wipe sde right?

Screenshot of the physical disks:
http://img546.imageshack.us/img546/9684/0z1b.jpg

davidh2k · 4. November 2013

Don't wipe sda in that case!

Let Ryecoaarn take a look again before you continue...

Greetings
David

Dannermax · 4. November 2013

Ok. Standing by...

ryecoaaron · 4. November 2013

It switched. In your original fdisk -l output, /dev/sda was the drive. The physical devices doesn't show which drive needs to be wiped. Can you show me a pic of the raid tab?

Dannermax · 4. November 2013

Ofourse. Is this what you need:

It is okay if the system om the 80gb gets wiped aswell...

ryecoaaron · 4. November 2013

You want to wipe /dev/sdb. I don't think the web interface will let you wipe the OS drive or a mounted drive. Haven't tried lately

Dannermax · 4. November 2013

I installed ubuntu on the 80gb drive, messed up the raid mounting, and installed OMV on a USB stick (kingston) I was afraid that if i deleted the 80gb drive, my raid would be even more messed up...

So no problem in, wiping the 80gb first.. Install OMV on it, and then wipe the sdb and rebuild?
Im afraid it will take forever rebuilding the drive, when the os is on a thumbdrive.. Im not that dumb actually..

ryecoaaron · 4. November 2013

I would do this:

Wipe the 80 gb
Wipe /dev/sdb (so that it doesn't change again)
throw away thumbdrive
unplug all but the 80 gb drive
install omv
plug other drives back in
fix raid

Dannermax · 4. November 2013

Got it!! Thanks man.. last question and ill shut up.. Would it need to be a secure wipe with the raid harddrive or can i just do quick? (cant find information about this on google...)

I really apprechiate your help!!!

ryecoaaron · 4. November 2013

Quick wipe is good enough.

Dannermax · 4. November 2013

Gracias!

Dannermax · 4. November 2013

hey, me again. I reinstalled OMV on the 80gb drive.

Now under the RAID tab there is no raids to recover.. and the failed harddrive does ot show up under physical drives.. do i need to, somehow get the missing harddrive to reappear in order to fix the raid?

ryecoaaron · 4. November 2013

We will switch to the command line Post the output of:

cat /proc/mdstat
fdisk -l

Dannermax · 4. November 2013

Whoops.. I discovered that 1 of the harddrives wasnt plugged in, properly... Thanks for the patience My system is now recovering the RAID5.. cross fingers it wont take 80 days.

Jetzt mitmachen!