January 25, 20197 yr Author *sigh* Came home to this... ...a stopped array. Again. wtf 20 hours ago, trurl said: It still thinks parity is valid. Not sure what happened as far as that incomplete parity check report. Did you miss my suggestion above? If you New Config without that new disk, then you can use your array again without waiting for it to clear. And since parity is valid (and you will tell it so) you won't even need to rebuild parity. Then you can see if you still have problems without the disk. Yes, I did miss that. What do you mean "new config"? Wipe it and start over? That's not really an option if that's what you mean. 16 hours ago, johnnie.black said: There have been various reports with slow rebuilds/clears and the ST8000DM004, likely you got a dud. Great. 13 hours ago, jonathanm said: It's backed up on another drive not connected to the array, right? ...that's what I'm trying to get setup...
January 25, 20197 yr Author And here's this if anyone wants to see it. All help greatly appreciated. tower-diagnostics-20190124-1726.zip
January 25, 20197 yr 40 minutes ago, rmp5s said: 13 hours ago, jonathanm said: It's backed up on another drive not connected to the array, right? ...that's what I'm trying to get setup... Can you clarify what you mean? If you don't have a current backup, I think you would be better served by using this new 8TB as a backup, not in your unraid tower. 42 minutes ago, rmp5s said: What do you mean "new config"? Wipe it and start over? New config adds all data drives as they are, and rebuilds parity based on the current content. It only wipes out the parity drive(s).
January 25, 20197 yr Community Expert 46 minutes ago, rmp5s said: What do you mean "new config"? Wipe it and start over? That's not really an option if that's what you mean. Of course not. Just forget about adding that disk for now and see if you can get to a stable array without it. Tools - New Config. Retain All, then unassign that problem disk. When you start the array the only thing it will do is rebuild parity using the other disks. None of the data disks will change. In fact, since it sounds like you don't have backups, you might even postpone the parity rebuild by unassigning parity also. Then you can copy anything important and irreplaceable, and once you have done that, assign the parity disk and let it rebuild. If it offers to FORMAT anything, DON'T. Come back for further advice.
January 25, 20197 yr Author 4 hours ago, jonathanm said: Can you clarify what you mean? If you don't have a current backup, I think you would be better served by using this new 8TB as a backup, not in your unraid tower. New config adds all data drives as they are, and rebuilds parity based on the current content. It only wipes out the parity drive(s). Yes yes. I know. I work in IT. I know "RAID isn't a backup". I know. But how it is is better than how it was. I need to move shit onto the array to free up space on drives so I can put said drives into the array. For instance, one of the 3TB drives was cleared and brought to the array. It was cleared ONTO the array. It's just a massive shuffling of data. I have offsite backup plans, but I have to get everything set up first. New config. Got it. Sounds perfect. 4 hours ago, trurl said: Of course not. Just forget about adding that disk for now and see if you can get to a stable array without it. Tools - New Config. Retain All, then unassign that problem disk. When you start the array the only thing it will do is rebuild parity using the other disks. None of the data disks will change. In fact, since it sounds like you don't have backups, you might even postpone the parity rebuild by unassigning parity also. Then you can copy anything important and irreplaceable, and once you have done that, assign the parity disk and let it rebuild. If it offers to FORMAT anything, DON'T. Come back for further advice. Beautiful. Will get it started tomorrow morning and post the results. Thank you all!
January 25, 20197 yr Community Expert Looks like the server rebooted on its own. Jan 24 16:27:11 Tower emhttpd: unclean shutdown detected
January 25, 20197 yr Author 10 hours ago, johnnie.black said: Looks like the server rebooted on its own. Jan 24 16:27:11 Tower emhttpd: unclean shutdown detected Hmm...interesting...wonder why. I'll have to keep an eye on it.
January 25, 20197 yr Author 17 hours ago, trurl said: Of course not. Just forget about adding that disk for now and see if you can get to a stable array without it. Tools - New Config. Retain All, then unassign that problem disk. When you start the array the only thing it will do is rebuild parity using the other disks. None of the data disks will change. In fact, since it sounds like you don't have backups, you might even postpone the parity rebuild by unassigning parity also. Then you can copy anything important and irreplaceable, and once you have done that, assign the parity disk and let it rebuild. If it offers to FORMAT anything, DON'T. Come back for further advice. Alright. New config'd, all retain'd, wonky disk unassign'd, parity being reparity'd. We'll see what happens! Thanks, my friend.
January 25, 20197 yr Community Expert 9 minutes ago, rmp5s said: The now unassigned 8TB drive has an option to format, btw. I wouldn't bother with it for now in case trying to access it causes problems again. If you want to use it Unassigned you can format it later, and if you want to put it in the array it will be cleared so format would be pointless.
January 25, 20197 yr Author 4 hours ago, trurl said: I wouldn't bother with it for now in case trying to access it causes problems again. If you want to use it Unassigned you can format it later, and if you want to put it in the array it will be cleared so format would be pointless. Got it. Thanks.
January 27, 20197 yr Author Damn thing rebooted again. fml It only had ~8hrs left on building the parity. What a pain in the ass. Can someone peruse this for weirdness? I need to figure out why this thing is rebooting or it's going to be completely useless. tower-diagnostics-20190126-1900.zip
January 27, 20197 yr Author I just bought another PSU. Perhaps that'll help. *shrug* At $25, it's worth it to find out. EDIT: I'm running unRAID on an HP ProLiant DL360e G8, btw. In the past, I've had issues with reboots and it was due to a junk PSU...so I thought I'd start there. Edited January 27, 20197 yr by rmp5s
January 28, 20197 yr Author Alright. So, parity FINALLY finished. Think I should try to "preclear" the 8TB again?
January 29, 20197 yr Community Expert 9 minutes ago, rmp5s said: Think I should try to "preclear" the 8TB again? You just need to clear it, preclear is done outside the array if you want to test the disk before adding it.
January 29, 20197 yr Author 12 minutes ago, johnnie.black said: You just need to clear it, preclear is done outside the array if you want to test the disk before adding it. Alright. I started the "preclear" thing again and it started at 88% of step 2, where it apparently left off before, but after letting it go for a little while, it didn't progress any so I cancelled it. I'm just going to add it. Hope it works this time! Thanks, Walker.
February 3, 20197 yr Author So, just to update everyone, the clearing FINALLY finished. It took OVER FIVE DAYS for it to clear, but it finally finished and has been formatted and added to the array. I've got another 8TB on the way that I'm going to use to replace one of the 3TB drives, but now that I have enough space, I don't really care how long it takes to clear. I can FINALLY get to work setting everything up! Thank you all for all the help. You're the best. Edited February 3, 20197 yr by rmp5s
February 3, 20197 yr Community Expert 4 hours ago, rmp5s said: It took OVER FIVE DAYS for it to clear That's way too long, but it's not the first time a user get's very low write performance with those Seagate disks, appears some are much slower than they should be.
February 3, 20197 yr Author 8 hours ago, johnnie.black said: That's way too long, but it's not the first time a user get's very low write performance with those Seagate disks, appears some are much slower than they should be. Well...I've got another on the way so we'll see if it's any better.
February 4, 20197 yr Author The array just stopped on its own. I don't know why. The thing didn't reboot, but it says "unclean shutdown detected". Logs attached. I restarted the array and now it's doing a parity check. Something isn't right... tower-diagnostics-20190203-1846.zip
February 4, 20197 yr 2 hours ago, rmp5s said: The array just stopped on its own. I don't know why. The thing didn't reboot, but it says "unclean shutdown detected". Logs attached. I restarted the array and now it's doing a parity check. Something isn't right... tower-diagnostics-20190203-1846.zip
February 4, 20197 yr Community Expert Locking this thread since the user started a new one for some reason.
Archived
This topic is now archived and is closed to further replies.