Jump to content

UNRAID thumbdrive fried - drive order... saywhaaa?


Recommended Posts

So aw-hell, the thumb drive I was using fried when my server was moved while attached. The thumb drive got sammiched between a wall and the USB port. *pop-sizzle-toast* goes the thumb drive but the motherboard and parity/data drives appear to be fine. 

 

Requested another License, was approved and all good there. However I have a 12 bay driver server mostly full and no documentation as to the drive order (other than Parity, this drive I know as its my larger drive). So what is the safest way to determine drive order for all the data drives? And yeah, I'll label the holly hell out of them if I can ever determine the order. If...

 

Any help would be appreciated. If i can supply any additional information... just ask. I've been running UNRAID flawlessly since 2013 and honestly never much messed with it other than to swap a dying drive on occasion, so I'm about as green and Cali Sunshine. SUPER simple direction is always appreciated. Thank you. 

Link to comment
34 minutes ago, RackaStackaMackaLack said:

So what is the safest way to determine drive order for all the data drives?

If you have single parity data drive order is not important, parity will still be valid, it's not the same with dual parity, parity1 would still be valid but not parity2.

  • Like 1
Link to comment
2 hours ago, RackaStackaMackaLack said:

, I'll label the holly hell out of them if I can ever determine the order. If..

Better yet keep a current backup of Flash. Then not only will you have your drive assignments but also all the other configurations from the webUI. 

  • Like 1
Link to comment
2 hours ago, RackaStackaMackaLack said:

I've been running UNRAID flawlessly since 2013 and honestly never much messed with it other than to swap a dying drive on occasion,

Assuming you are running a recent version of Unraid you can download a zipped backup of Flash from Main - Boot Device - Flash - Flash Backup

 

If you are "set it and forget it " make sure you have Notifications setup to email you. 

  • Like 1
Link to comment

Tee-

14 hours ago, johnnie.black said:

If you have single parity data drive order is not important, parity will still be valid, it's not the same with dual parity, parity1 would still be valid but not parity2.

So I can simply add each drive back into the system (this time maybe in order) and when i start the array its all good? I do just have a single Parity btw. Will i be prompted to rebuild Parity or anything additionally that I should be aware of? Example "whatever you do just don't select the (whatever) option or you're going to waste all your data. That kind of added info is also much appreciated. 

 

11 hours ago, trurl said:

Assuming you are running a recent version of Unraid you can download a zipped backup of Flash from Main - Boot Device - Flash - Flash Backup

 

If you are "set it and forget it " make sure you have Notifications setup to email you. 

That's the thing, I was NOT running a recent version, its the same one i setup back in 2013. However now I am running a current version as I lost all the contents of the original thumb drive.

 

 

 

Link to comment
6 hours ago, RackaStackaMackaLack said:

So I can simply add each drive back into the system (this time maybe in order) and when i start the array its all good? I do just have a single Parity btw.

Yes.

 

6 hours ago, RackaStackaMackaLack said:

Will i be prompted to rebuild Parity or anything additionally that I should be aware of?

Check "parity is already valid" before starting the array, next to the start array button.

Link to comment
13 hours ago, johnnie.black said:

Yes.

 

Check "parity is already valid" before starting the array, next to the start array button.

"Parity is Valid" however received this:

 

Jun 25 12:11:14 Tower kernel: md: disk6 new disk
Jun 25 12:11:14 Tower kernel: mdcmd (8): import 7 sdf 64 2930266532 0 WDC_WD30EFRX-68N32N0_WD-WCC7K1CZYJTF
Jun 25 12:11:14 Tower kernel: md: import disk7: (sdf) WDC_WD30EFRX-68N32N0_WD-WCC7K1CZYJTF size: 2930266532
Jun 25 12:11:14 Tower kernel: md: disk7 new disk
Jun 25 12:11:14 Tower kernel: mdcmd (9): import 8 sdb 64 2930266532 0 WDC_WD30EZRZ-00Z5HB0_WD-WCC4N0XAPS4N
Jun 25 12:11:14 Tower kernel: md: import disk8: (sdb) WDC_WD30EZRZ-00Z5HB0_WD-WCC4N0XAPS4N size: 2930266532
Jun 25 12:11:14 Tower kernel: md: disk8 new disk
Jun 25 12:11:14 Tower kernel: mdcmd (10): import 9 sdj 64 2930266532 0 WDC_WD30EZRZ-00Z5HB0_WD-WCC4N3PLLKVK
Jun 25 12:11:14 Tower kernel: md: import disk9: (sdj) WDC_WD30EZRZ-00Z5HB0_WD-WCC4N3PLLKVK size: 2930266532
Jun 25 12:11:14 Tower kernel: md: disk9 new disk
Jun 25 12:11:14 Tower kernel: mdcmd (11): import 10 sdk 64 1953514552 0 ST2000DM001-1CH164_Z340CPVK
Jun 25 12:11:14 Tower kernel: md: import disk10: (sdk) ST2000DM001-1CH164_Z340CPVK size: 1953514552
Jun 25 12:11:14 Tower kernel: md: disk10 new disk
Jun 25 12:11:14 Tower kernel: mdcmd (12): import 11 sdl 64 976762552 0 ST1000DM003-1CH162_Z1D66X85
Jun 25 12:11:14 Tower kernel: md: import disk11: (sdl) ST1000DM003-1CH162_Z1D66X85 size: 976762552
Jun 25 12:11:14 Tower kernel: md: disk11 new disk
Jun 25 12:11:14 Tower kernel: mdcmd (13): import 12
Jun 25 12:11:14 Tower kernel: mdcmd (14): import 13
Jun 25 12:11:14 Tower kernel: mdcmd (15): import 14
Jun 25 12:11:14 Tower kernel: mdcmd (16): import 15
Jun 25 12:11:14 Tower kernel: mdcmd (17): import 16
Jun 25 12:11:14 Tower kernel: mdcmd (18): import 17
Jun 25 12:11:14 Tower kernel: mdcmd (19): import 18
Jun 25 12:11:14 Tower kernel: mdcmd (20): import 19
Jun 25 12:11:14 Tower kernel: mdcmd (21): import 20
Jun 25 12:11:14 Tower kernel: mdcmd (22): import 21
Jun 25 12:11:14 Tower kernel: mdcmd (23): import 22
Jun 25 12:11:14 Tower kernel: mdcmd (24): import 23
Jun 25 12:11:14 Tower kernel: mdcmd (25): import 24
Jun 25 12:11:14 Tower kernel: mdcmd (26): import 25
Jun 25 12:11:14 Tower kernel: mdcmd (27): import 26
Jun 25 12:11:14 Tower kernel: mdcmd (28): import 27
Jun 25 12:11:14 Tower kernel: mdcmd (29): import 28
Jun 25 12:11:14 Tower kernel: mdcmd (30): import 29
Jun 25 12:11:14 Tower emhttpd: import 30 cache device: no device
Jun 25 12:11:14 Tower emhttpd: import flash device: sda
Jun 25 12:12:54 Tower ntpd[1637]: kernel reports TIME_ERROR: 0x41: Clock Unsynchronized
Jun 25 12:14:24 Tower emhttpd: too many devices 

Link to comment

Join the conversation

You can post now and register later. If you have an account, sign in now to post with your account.
Note: Your post will require moderator approval before it will be visible.

Guest
Reply to this topic...

×   Pasted as rich text.   Restore formatting

  Only 75 emoji are allowed.

×   Your link has been automatically embedded.   Display as a link instead

×   Your previous content has been restored.   Clear editor

×   You cannot paste images directly. Upload or insert images from URL.

×
×
  • Create New...