October 10, 201213 yr Hi there. So I'm struggling with a few things at once - basically my problems have gotten worse while trying to fix things. 1) my flash drive keeps mounting read-only, but the system has been working fine. 2) I ordered a new flash drive and more ram and it all showed up today. 3) ram installed ok 4) my new flash drive won't boot (another post in the hardware forum). 5) now i'm booting on my old flash drive (that has been working) My problem now is that unRaid seems to have completely lost my drive configuration. When I boot up it says "No disks assigned". What caused this and how can I get my array back up and running???? When I try to reassign the drives they show up blue as a "New Disk". There is WAAAAYYY to much data on these drives for me to consider them as "new disks". Could someone help me out? whiteatom :'(
October 10, 201213 yr Author I don't have a screen shot of my drive config (stupid i know), but I do have a syslog from last week.. can I get the intended drive assignment from that?? Doing some more digging.. it appears that the problem might be that my flash drive mounted as sdg instead of sdc as it did in the past - is this a possible cause? whiteatom
October 10, 201213 yr My instructions do not get you back to operational without building parity again! So others with more knowledge then myself will likely have a better method. If you install all your drives as data drives with no parity drive you can start your array and see what you have available. Just make sure not to FORMAT anything. You should see just one unformatted drive in the list - your parity drive. Now you know which drive is your parity that you will be rebuilding so the drive order of the rest of the drives doesn't matter. Make the unformatted drive your parity drive and the rest assigned as data drives and start the array to rebuild parity. You are back in operation once parity is built but to confirm parity was built correctly you need to then run a parity check. I followed this method when I virtualized my unRAID server but as I said at the top there is likely a better way that will preserve your parity.
October 10, 201213 yr Author I found this... Is disk0 the parity? Sep 24 17:40:36 knox kernel: mdcmd (1): import 0 8,32 1953514552 ST2000DL003-9VT166_5YD2XNYW Sep 24 17:40:36 knox kernel: md: import disk0: [8,32] (sdc) ST2000DL003-9VT166_5YD2XNYW size: 1953514552 Sep 24 17:40:37 knox kernel: mdcmd (2): import 1 8,128 976762552 WDC_WD10EACS-00D6B0_WD-WCAU40518710 Sep 24 17:40:37 knox kernel: md: import disk1: [8,128] (sdi) WDC_WD10EACS-00D6B0_WD-WCAU40518710 size: 976762552 Sep 24 17:40:37 knox kernel: mdcmd (3): import 2 8,144 1953514552 ST2000DL003-9VT166_6YD24F2R Sep 24 17:40:37 knox kernel: md: import disk2: [8,144] (sdj) ST2000DL003-9VT166_6YD24F2R size: 1953514552 Sep 24 17:40:37 knox kernel: mdcmd (4): import 3 8,112 976762552 WDC_WD10EADS-00L5B1_WD-WCAU4A147383 Sep 24 17:40:37 knox kernel: md: import disk3: [8,112] (sdh) WDC_WD10EADS-00L5B1_WD-WCAU4A147383 size: 976762552 Sep 24 17:40:37 knox kernel: mdcmd (5): import 4 8,0 1953514552 WDC_WD20EARS-00MVWB0_WD-WCAZA2530406 Sep 24 17:40:37 knox kernel: md: import disk4: [8,0] (sda) WDC_WD20EARS-00MVWB0_WD-WCAZA2530406 size: 1953514552 Sep 24 17:40:37 knox kernel: mdcmd (6): import 5 8,80 1953514552 Hitachi_HDS5C3020ALA632_ML0220F313PSBD Sep 24 17:40:37 knox kernel: md: import disk5: [8,80] (sdf) Hitachi_HDS5C3020ALA632_ML0220F313PSBD size: 1953514552 Sep 24 17:40:37 knox kernel: mdcmd (7): import 6 8,64 1953514552 ST2000DL003-9VT166_5YD2SLX4 Sep 24 17:40:37 knox kernel: md: import disk6: [8,64] (sde) ST2000DL003-9VT166_5YD2SLX4 size: 1953514552 Sep 24 17:40:37 knox kernel: mdcmd (: import 7 8,48 1953514552 ST2000DL003-9VT166_6YD24DBJ Sep 24 17:40:37 knox kernel: md: import disk7: [8,48] (sdd) ST2000DL003-9VT166_6YD24DBJ size: 1953514552
October 10, 201213 yr I found this... Is disk0 the parity? Sep 24 17:40:36 knox kernel: mdcmd (1): import 0 8,32 1953514552 ST2000DL003-9VT166_5YD2XNYW Sep 24 17:40:36 knox kernel: md: import disk0: [8,32] (sdc) ST2000DL003-9VT166_5YD2XNYW size: 1953514552 Sep 24 17:40:37 knox kernel: mdcmd (2): import 1 8,128 976762552 WDC_WD10EACS-00D6B0_WD-WCAU40518710 Sep 24 17:40:37 knox kernel: md: import disk1: [8,128] (sdi) WDC_WD10EACS-00D6B0_WD-WCAU40518710 size: 976762552 Sep 24 17:40:37 knox kernel: mdcmd (3): import 2 8,144 1953514552 ST2000DL003-9VT166_6YD24F2R Sep 24 17:40:37 knox kernel: md: import disk2: [8,144] (sdj) ST2000DL003-9VT166_6YD24F2R size: 1953514552 Sep 24 17:40:37 knox kernel: mdcmd (4): import 3 8,112 976762552 WDC_WD10EADS-00L5B1_WD-WCAU4A147383 Sep 24 17:40:37 knox kernel: md: import disk3: [8,112] (sdh) WDC_WD10EADS-00L5B1_WD-WCAU4A147383 size: 976762552 Sep 24 17:40:37 knox kernel: mdcmd (5): import 4 8,0 1953514552 WDC_WD20EARS-00MVWB0_WD-WCAZA2530406 Sep 24 17:40:37 knox kernel: md: import disk4: [8,0] (sda) WDC_WD20EARS-00MVWB0_WD-WCAZA2530406 size: 1953514552 Sep 24 17:40:37 knox kernel: mdcmd (6): import 5 8,80 1953514552 Hitachi_HDS5C3020ALA632_ML0220F313PSBD Sep 24 17:40:37 knox kernel: md: import disk5: [8,80] (sdf) Hitachi_HDS5C3020ALA632_ML0220F313PSBD size: 1953514552 Sep 24 17:40:37 knox kernel: mdcmd (7): import 6 8,64 1953514552 ST2000DL003-9VT166_5YD2SLX4 Sep 24 17:40:37 knox kernel: md: import disk6: [8,64] (sde) ST2000DL003-9VT166_5YD2SLX4 size: 1953514552 Sep 24 17:40:37 knox kernel: mdcmd (: import 7 8,48 1953514552 ST2000DL003-9VT166_6YD24DBJ Sep 24 17:40:37 knox kernel: md: import disk7: [8,48] (sdd) ST2000DL003-9VT166_6YD24DBJ size: 1953514552 I would think so. I seem to remember seeing my parity as disk0 in the logs - but someone else will need to confirm. Sorry I'm not comfortable telling you a flat YES. Or you could use your new flash drive to boot from (once you get that working anyway) and assign it as a data drive. It should show up in the GUI as unformatted. One thing you could do once you get all this sorted out is label your drives (something I'm guilty of NOT doing myself ).
October 10, 201213 yr Author The one drive I have labelled is my cache drive. With identify I was able to find that disk0 is the cache drive.... so I reassigned according to that list and just started the array. It seemed happy with the drive assignment. The parity check is in progress now. I'll let you know how it goes. Thanks for the tips. I wonder what caused the config to be lost? would it be that my USB stick mounted with a different letter? I thought that wasn't a problem anymore.... whiteatom
October 10, 201213 yr With your flash mounting as read only I could see flash problems cause a loss of configuration data. Maybe the write that caused it to be read only was to your drive configuration? Beyond that I'm afraid I don't know.
October 10, 201213 yr The one drive I have labelled is my cache drive. With identify I was able to find that disk0 is the cache drive.... so I reassigned according to that list and just started the array. It seemed happy with the drive assignment. The parity check is in progress now. I'll let you know how it goes. Thanks for the tips. I wonder what caused the config to be lost? would it be that my USB stick mounted with a different letter? I thought that wasn't a problem anymore.... whiteatom The drive letters never made a difference. The sdX assignments are ephemeral and may change from boot to boot.
October 11, 201213 yr Author So.. I'm at 90% now and so far 0 errors.. so I think if I had screwed things up I would have found at least 1 error by now. Thank you for helping me down from my little panic. I think all is well now. whiteatom
October 13, 201213 yr Author Everything is back to normal on my new flash drive.. Thanks for the help
Archived
This topic is now archived and is closed to further replies.