[SOLVED]'Trust My Array' Procedure failed, array won't start, what now?

[javier911]

I decided to use that procedure on my 5.0.5 unraid box, unfortunately I misunderstood some of it, such as I didn't realize that the "recent 5.x" warning applied to 5.0.5, and I screwed up my array.  Probably by refreshing the webpage like it said to not do, but again I just didn't understand, I thought that only applied to 4.7.  I know I should have just let it rebuild the disk but the failed disk passed tests and I didn't want my array to be down or super slow for days.

 

I later found this thread:

http://lime-technology.com/forum/index.php?topic=19385

...and I'm in the same situation as the one poster there where my drives all became unassigned and "blue" status.

 

So I manually assigned them all again, making sure my parity drive is the same which is easy because it's the largest drive.  Then I try to check the "Parity is already valid" and start the array but it never starts.  In the log it seems to be doing the same stuff over and over to attempt to start the array.

Oct 14 04:32:43 unraid1 kernel: mdcmd (16): import 15 0,0
Oct 14 04:32:43 unraid1 kernel: mdcmd (17): import 16 0,0
Oct 14 04:32:43 unraid1 kernel: mdcmd (18): import 17 0,0
Oct 14 04:32:43 unraid1 kernel: mdcmd (19): import 18 0,0
Oct 14 04:32:43 unraid1 kernel: mdcmd (20): import 19 0,0
Oct 14 04:32:43 unraid1 kernel: mdcmd (21): import 20 0,0
Oct 14 04:32:43 unraid1 kernel: mdcmd (22): import 21 0,0
Oct 14 04:32:43 unraid1 kernel: mdcmd (23): import 22 0,0
Oct 14 04:32:43 unraid1 kernel: mdcmd (24): import 23 0,0
Oct 14 04:32:43 unraid1 emhttp_event: driver_loaded
Oct 14 04:33:12 unraid1 emhttp: shcmd (4650): rmmod md-mod |& logger
Oct 14 04:33:12 unraid1 emhttp: shcmd (4651): modprobe md-mod super=/boot/config/super.dat slots=24 |& logger
Oct 14 04:33:12 unraid1 kernel: md: unRAID driver removed
Oct 14 04:33:12 unraid1 emhttp: shcmd (4652): udevadm settle
Oct 14 04:33:12 unraid1 kernel: md: unRAID driver 2.2.0 installed
Oct 14 04:33:12 unraid1 kernel: read_file: error 2 opening /boot/config/super.dat
Oct 14 04:33:12 unraid1 kernel: md: could not read superblock from /boot/config/super.dat
Oct 14 04:33:12 unraid1 kernel: md: initializing superblock
Oct 14 04:33:12 unraid1 emhttp: Device inventory:
Oct 14 04:33:12 unraid1 emhttp: Hitachi_HDS5C3020ALA632_ML0220F311UPBD (sdb) 1953514584
Oct 14 04:33:12 unraid1 emhttp: WDC_WD20EARS-00MVWB0_WD-WCAZA6010408 (sdc) 1953514584
Oct 14 04:33:12 unraid1 emhttp: WDC_WD20EARS-00J99B0_WD-WCAWZ0950511 (sdd) 1953514584
Oct 14 04:33:12 unraid1 emhttp: WDC_WD20EARS-00J99B0_WD-WCAWZ0929154 (sde) 1953514584
Oct 14 04:33:12 unraid1 emhttp: WDC_WD20EARS-00J2GB0_WD-WCAYY0152863 (sdf) 1953514584
Oct 14 04:33:12 unraid1 emhttp: ST2000DM001-1CH164_Z1E24FA6 (sdg) 1953514584
Oct 14 04:33:12 unraid1 emhttp: ST2000DM001-1CH164_Z1E24FLV (sdh) 1953514584
Oct 14 04:33:12 unraid1 emhttp: WDC_WD20EARS-00MVWB0_WD-WCAZA1284898 (sdi) 1953514584
Oct 14 04:33:12 unraid1 emhttp: WDC_WD20EARX-00PASB0_WD-WMAZA9865830 (sdj) 1953514584
Oct 14 04:33:12 unraid1 emhttp: HGST_HDS5C4040ALE630_PL1331LAGHYSWH (sdk) 3907018584
Oct 14 04:33:12 unraid1 kernel: mdcmd (1): import 0 8,160 3907018532 HGST_HDS5C4040ALE630_PL1331LAGHYSWH
Oct 14 04:33:12 unraid1 kernel: md: import disk0: [8,160] (sdk) HGST_HDS5C4040ALE630_PL1331LAGHYSWH size: 3907018532
Oct 14 04:33:12 unraid1 kernel: md: disk0 new disk
Oct 14 04:33:12 unraid1 kernel: mdcmd (2): import 1 8,32 1953514552 WDC_WD20EARS-00MVWB0_WD-WCAZA6010408
Oct 14 04:33:12 unraid1 kernel: md: import disk1: [8,32] (sdc) WDC_WD20EARS-00MVWB0_WD-WCAZA6010408 size: 1953514552
Oct 14 04:33:12 unraid1 kernel: md: disk1 new disk
Oct 14 04:33:12 unraid1 kernel: mdcmd (3): import 2 8,48 1953514552 WDC_WD20EARS-00J99B0_WD-WCAWZ0950511
Oct 14 04:33:12 unraid1 kernel: md: import disk2: [8,48] (sdd) WDC_WD20EARS-00J99B0_WD-WCAWZ0950511 size: 1953514552
Oct 14 04:33:12 unraid1 kernel: md: disk2 new disk
Oct 14 04:33:12 unraid1 kernel: mdcmd (4): import 3 8,64 1953514552 WDC_WD20EARS-00J99B0_WD-WCAWZ0929154
Oct 14 04:33:12 unraid1 kernel: md: import disk3: [8,64] (sde) WDC_WD20EARS-00J99B0_WD-WCAWZ0929154 size: 1953514552
Oct 14 04:33:12 unraid1 kernel: md: disk3 new disk
Oct 14 04:33:12 unraid1 kernel: mdcmd (5): import 4 8,80 1953514552 WDC_WD20EARS-00J2GB0_WD-WCAYY0152863
Oct 14 04:33:12 unraid1 kernel: md: import disk4: [8,80] (sdf) WDC_WD20EARS-00J2GB0_WD-WCAYY0152863 size: 1953514552
Oct 14 04:33:12 unraid1 kernel: md: disk4 new disk
Oct 14 04:33:12 unraid1 kernel: mdcmd (6): import 5 8,128 1953514552 WDC_WD20EARS-00MVWB0_WD-WCAZA1284898
Oct 14 04:33:12 unraid1 kernel: md: import disk5: [8,128] (sdi) WDC_WD20EARS-00MVWB0_WD-WCAZA1284898 size: 1953514552
Oct 14 04:33:12 unraid1 kernel: md: disk5 new disk
Oct 14 04:33:12 unraid1 kernel: mdcmd (7): import 6 8,144 1953514552 WDC_WD20EARX-00PASB0_WD-WMAZA9865830
Oct 14 04:33:12 unraid1 kernel: md: import disk6: [8,144] (sdj) WDC_WD20EARX-00PASB0_WD-WMAZA9865830 size: 1953514552
Oct 14 04:33:12 unraid1 kernel: md: disk6 new disk
Oct 14 04:33:12 unraid1 kernel: mdcmd (: import 7 8,96 1953514552 ST2000DM001-1CH164_Z1E24FA6
Oct 14 04:33:12 unraid1 kernel: md: import disk7: [8,96] (sdg) ST2000DM001-1CH164_Z1E24FA6 size: 1953514552
Oct 14 04:33:12 unraid1 kernel: md: disk7 new disk
Oct 14 04:33:12 unraid1 kernel: mdcmd (9): import 8 8,112 1953514552 ST2000DM001-1CH164_Z1E24FLV
Oct 14 04:33:12 unraid1 kernel: md: import disk8: [8,112] (sdh) ST2000DM001-1CH164_Z1E24FLV size: 1953514552
Oct 14 04:33:12 unraid1 kernel: md: disk8 new disk
Oct 14 04:33:12 unraid1 kernel: mdcmd (10): import 9 8,16 1953514552 Hitachi_HDS5C3020ALA632_ML0220F311UPBD
Oct 14 04:33:12 unraid1 kernel: md: import disk9: [8,16] (sdb) Hitachi_HDS5C3020ALA632_ML0220F311UPBD size: 1953514552
Oct 14 04:33:12 unraid1 kernel: md: disk9 new disk
Oct 14 04:33:12 unraid1 kernel: mdcmd (11): import 10 0,0
Oct 14 04:33:12 unraid1 kernel: mdcmd (12): import 11 0,0
Oct 14 04:33:12 unraid1 kernel: mdcmd (13): import 12 0,0
Oct 14 04:33:12 unraid1 kernel: mdcmd (14): import 13 0,0
Oct 14 04:33:12 unraid1 kernel: mdcmd (15): import 14 0,0
Oct 14 04:33:12 unraid1 kernel: mdcmd (16): import 15 0,0
Oct 14 04:33:12 unraid1 kernel: mdcmd (17): import 16 0,0
Oct 14 04:33:12 unraid1 kernel: mdcmd (18): import 17 0,0
Oct 14 04:33:12 unraid1 kernel: mdcmd (19): import 18 0,0
Oct 14 04:33:12 unraid1 kernel: mdcmd (20): import 19 0,0
Oct 14 04:33:12 unraid1 kernel: mdcmd (21): import 20 0,0
Oct 14 04:33:12 unraid1 kernel: mdcmd (22): import 21 0,0
Oct 14 04:33:12 unraid1 kernel: mdcmd (23): import 22 0,0
Oct 14 04:33:12 unraid1 kernel: mdcmd (24): import 23 0,0
Oct 14 04:33:12 unraid1 emhttp: shcmd (4653): /usr/local/sbin/emhttp_event driver_loaded
Oct 14 04:33:12 unraid1 emhttp_event: driver_loaded

I see that section repeated over and over every minute or so.

 

When I ran initconfig it gives that message about renaming super.dat to super.bak.  I cannot find any file named super.bak but I did find a file named super.old.  Do I have to restore that or something?

 

Anyway yes I'm lost now, so basically 2 questions.

 

1) Did I lose all my data??!!?

 

2) How do I resolve this?

 

Thanks

 

[JorgeB]

Your data should be fine, and you can use the V6 procedure for 5.0.5.

 

Go to tools -> New config, reassign all disks, check "parity is already valid" and start array.

[javier911]

Your data should be fine, and you can use the V6 procedure for 5.0.5.

 

Go to tools -> New config, reassign all disks, check "parity is already valid" and start array.

That worked, thank you very much.  I was pretty sure the data would be intact but not totally sure, now I can sleep .

[JorgeB]

You should run a non correcting parity check to make sure the failed disk is really OK, if there are sync errors but no disk errors then run a correcting check.

[RobJ]

And consider upgrading to v6!