July 16, 201114 yr Hi, Replacing failed drive, followed Joe L. script/process, but after putting in new drive (SATA not IDE), unRaid wants to immediately start the array. I've tried stopping it several times, but it seems to "hang" with the 1st SATA data drive and is taking forever to unmount it? Is that unusual? How can I boot up w/o starting the array (linux command ?) so that I can add the replacement Sata drive to the system. Thanks Dave
July 17, 201114 yr Hi, Replacing failed drive, followed Joe L. script/process, but after putting in new drive (SATA not IDE), unRaid wants to immediately start the array. I've tried stopping it several times, but it seems to "hang" with the 1st SATA data drive and is taking forever to unmount it? Is that unusual? How can I boot up w/o starting the array (linux command ?) so that I can add the replacement Sata drive to the system. Thanks Dave If you have any add-ons, you best disable them if you do not know what you are doing. then, follow the normal troubleshooting instructions when requesting help... post a syslog. Tell us what version of unRAID, etc.
July 17, 201114 yr Author Thanks Joe, I did set-up your unMenu and within that minidlna (though that can be eliminated at this point). I tried to get a syslog before I tried to shut the system down, but it would not allow me access to the "flash" drive and/or unMenu. I did get an extract for 7/14/11 (oops posted before complete) which I posted at http://lime-technology.com/forum/index.php?topic=13952.0. I just looked and the "system" claims it is unmounting the 1st Sata drive (1 TB Seagate - sdb), but it has been doing this for the past 2 1/2 hours, so.... My guess is that its locked, all the rest of the drives are unmounted but not this one. Until it is unmounted, I don't think I can add the replacement drive to the array and begin to rebuild the "lost" files. I don't believe that I've seen this before, where the array wants to start, but won't shut down. Couple that with a drive that has died, which I think should (if removed) prevent the system from booting and I am worried that my data could be lost. I welcome any suggestions that you might have as the "Master Guru" ! One thought was to "disconnect" another drive, to force the array to see a problem and not start, then I could add the new drive (to replace the failed unit) , then reboot after re powering the other drive. Do you think this would work? Otherwise, is there a command that will specifically prevent the unRaid "bat" file from loading/starting the array? Dave
July 17, 201114 yr Author Hi Joe, I'm trying to get a Syslog to post, but am not able to access the "flash" directly from my windows shares and/or through a command line interface. The array has been "attempting" to unmount/dismount my 1st Sata drive for over 5 hours w/no change, so am not sure what to do next. Is there a linux command to allow me to update/retrieve the syslog so that I can post it for you/others? Thanks, Dave Screen copy of current system following "stop" command: LIMEtechnology Server name: Tower Comments: Media server unRAID Server Pro Main | Users | Shares | Settings | Devices version: 4.7 Disk status Model / Serial No. Temperature Size Free Reads Writes Errors parity ST31500341AS_9VS37M0J * 1,465,138,552 - 135 183 0 disk1 ST31000528AS_9VP1XTQX * 976,762,552 Unmounting 83 16 0 disk2 Not installed - 488,386,552 - - - - disk3 Maxtor_6L300R0_L60VMZGG * 293,057,320 - 79 25 0 disk4 WDC_WD2500JB-00REA0_WD-WMANK1838271 * 244,198,552 - 80 27 0 disk5 WDC_WD2500JB-00REA0_WD-WMANK1917605 * 244,198,552 - 80 27 0 disk6 ST3500830A_9QG2T30C * 488,386,552 - 85 29 0 disk7 ST3500830A_9QG2ECSV * 488,386,552 - 86 29 0 Command area Stopping....
July 17, 201114 yr Hi Joe, I'm trying to get a Syslog to post, but am not able to access the "flash" directly from my windows shares and/or through a command line interface. The array has been "attempting" to unmount/dismount my 1st Sata drive for over 5 hours w/no change, so am not sure what to do next. Is there a linux command to allow me to update/retrieve the syslog so that I can post it for you/others? Thanks, Dave Screen copy of current system following "stop" command: LIMEtechnology Server name: Tower Comments: Media server unRAID Server Pro Main | Users | Shares | Settings | Devices version: 4.7 Disk status Model / Serial No. Temperature Size Free Reads Writes Errors parity ST31500341AS_9VS37M0J * 1,465,138,552 - 135 183 0 disk1 ST31000528AS_9VP1XTQX * 976,762,552 Unmounting 83 16 0 disk2 Not installed - 488,386,552 - - - - disk3 Maxtor_6L300R0_L60VMZGG * 293,057,320 - 79 25 0 disk4 WDC_WD2500JB-00REA0_WD-WMANK1838271 * 244,198,552 - 80 27 0 disk5 WDC_WD2500JB-00REA0_WD-WMANK1917605 * 244,198,552 - 80 27 0 disk6 ST3500830A_9QG2T30C * 488,386,552 - 85 29 0 disk7 ST3500830A_9QG2ECSV * 488,386,552 - 86 29 0 Command area Stopping.... yes, you'll find it in the wiki under "troubleshooting" http://lime-technology.com/wiki/index.php?title=Troubleshooting
July 17, 201114 yr Author Main | Users | Shares | Settings | Devices version: 4.7 Disk status Model / Serial No. Temperature Size Free Reads Writes Errors parity ST31500341AS_9VS37M0J * 1,465,138,552 - 135 183 0 disk1 ST31000528AS_9VP1XTQX * 976,762,552 Unmounting 83 16 0 disk2 Not installed - 488,386,552 - - - - disk3 Maxtor_6L300R0_L60VMZGG * 293,057,320 - 79 25 0 disk4 WDC_WD2500JB-00REA0_WD-WMANK1838271 * 244,198,552 - 80 27 0 disk5 WDC_WD2500JB-00REA0_WD-WMANK1917605 * 244,198,552 - 80 27 0 disk6 ST3500830A_9QG2T30C * 488,386,552 - 85 29 0 disk7 ST3500830A_9QG2ECSV * 488,386,552 - 86 29 0 Command area Stopping.... yes, you'll find it in the wiki under "troubleshooting" http://lime-technology.com/wiki/index.php?title=Troubleshooting Thanks Joe, I was just trying to get a copy of the Syslog per these instructions, I will attach both the one from Friday evening (7/15) and today (7/17) as zips. Thanks again, Dave syslog-2011-07-15.zip syslog_2011-07-17.zip
July 17, 201114 yr Author Hi Joe, Went back to unRaid and re-booted again, then stopped array, it finally unmounted disk1 and allowed me to "add/replace" disk 2 (new Sata 1TB) to replace the failed IDE (500GB) drive. It is now rebuilding the data and should complete sometime today ? (>1000 minutes). Once that is complete, should I perform another Parity Check? I would think that during the rebuild, that would be done, but am not sure since this is my first drive failure. After the above, I would like to install a larger Parity Drive and consolidate my data into fewer drives (if I've had 1 ide drive fail, they are probably all due at some point, so perhaps its time to move to newer drives). The current Parity Drive is 1.5 TB and I just got a 2.0 TB (could not use for data since larger than Parity). To replace Parity does it just go in the same slot as the current Parity, then do a Parity Check? Should I try to move the data from the other small drives (IDE's) first, then change the Parity Drive? What would you recommend? Thanks again, you are definitely the "Hero" ! Dave
July 17, 201114 yr Hi Joe, Went back to unRaid and re-booted again, then stopped array, it finally unmounted disk1 and allowed me to "add/replace" disk 2 (new Sata 1TB) to replace the failed IDE (500GB) drive. It is now rebuilding the data and should complete sometime today ? (>1000 minutes). Once that is complete, should I perform another Parity Check? I would think that during the rebuild, that would be done, but am not sure since this is my first drive failure. After the rebuild, perform a manual parity check with the option selected to NOT update parity. That way it will not be clobbered if the replacement disk has an un-readable sector. After the above, I would like to install a larger Parity Drive and consolidate my data into fewer drives (if I've had 1 ide drive fail, they are probably all due at some point, so perhaps its time to move to newer drives). The current Parity Drive is 1.5 TB and I just got a 2.0 TB (could not use for data since larger than Parity). To replace Parity does it just go in the same slot as the current Parity, then do a Parity Check? Should I try to move the data from the other small drives (IDE's) first, then change the Parity Drive? What would you recommend?When you replace the parity drive and re-start the array, it will re-build parity. This time though, when you so a subsequent parity check, it is ok to let it it update... Thanks again, you are definitely the "Hero" ! Dave Thanks.
July 17, 201114 yr Author After the rebuild, perform a manual parity check with the option selected to NOT update parity. That way it will not be clobbered if the replacement disk has an un-readable sector. ........... When you replace the parity drive and re-start the array, it will re-build parity. This time though, when you so a subsequent parity check, it is ok to let it it update... Thanks. Thank you Joe, I appreciate your insight and knowledge. Would you recommend consolidation (copying small drives to large drive) first or getting the new Parity Drive installed? Also if I install a new Parity (larger drive) does the old Parity drive need to be removed until after Parity is calculated or can it remain as another drive when the "new" Parity drive is installed? It is a process and I would like it to be safe! Dave
July 17, 201114 yr After the rebuild, perform a manual parity check with the option selected to NOT update parity. That way it will not be clobbered if the replacement disk has an un-readable sector. ........... When you replace the parity drive and re-start the array, it will re-build parity. This time though, when you so a subsequent parity check, it is ok to let it it update... Thanks. Thank you Joe, I appreciate your insight and knowledge. Would you recommend consolidation (copying small drives to large drive) first or getting the new Parity Drive installed? Also if I install a new Parity (larger drive) does the old Parity drive need to be removed until after Parity is calculated or can it remain as another drive when the "new" Parity drive is installed? It is a process and I would like it to be safe! Dave It can remain as installed, but then you'll need to leave it un-assigned until after the initial parity calc is done on the new parity drive.
July 18, 201114 yr Author After the rebuild, perform a manual parity check with the option selected to NOT update parity. That way it will not be clobbered if the replacement disk has an un-readable sector. Hi Joe, Everything went well and I was able to get to my Accounting data, so I think my unRaid Server is back together. I want to mark this as "Solved" but still have a couple of questions: 1 - How do you perform a "manual Parity Check w/No Parity Update"? I found your script for the monthly parity check, but in trying to invoke just the command line got lost in what to type. I think its there, but I don't see anything happening nor does the Lime-Tech Main or UnMenu main screen see anything. {This might be a good addition to the unMenu scripts with a manual override "button" to invoke.} 2 - My other problem is that I no longer can use Tower as my name (I've found something in the forum to rename the tower but it doesn't seem to work). I've set the unRaid server to a fixed IP address 10.0.0.50 and as long as I use that in the address bar I can get to the Tower. Shares come across as \\Tower\Movies, but not the LimeTech Main and your unMenu defaults to Tower:8080, so accessing any of the great commands that you have developed, requires me to rename the path to 10.0.0.50:8080\system_log (for example). Again my sincere thanks for all your help and that of Shawn (Whaler_99) for the recomendations. The forum is great! Warmly, Dave Surprise to me, apparently I did manage to invoke a Command Line Parity Check and eventually it started to show up in unMenu et al. Thanks, not exactly sure of how I did this, but wow! I can't tell if it's w/o updating, but since I used your Command, would suspect so! Dave
Archived
This topic is now archived and is closed to further replies.