June 1, 20179 yr I'm new to unraid. And just finished getting my first box set up. A couple of hours ago I got an interesting alert:"unraid Alert [UNRAID] - Disk 1 in error state (disk dsbl)" It is now disabled and its content emulated, and is showing the red X next to it. After, I was not able to get a SMART report from the drive until after rebooting. In the syslog (attached) it starts looking shaky at Jun 1 13:29:10 The SMART report for disk 1 (attached) isn't looking to hot either. Not being an advanced user, Im not sure if I should replace the drive or not. syslog.txt ST4000LM016-1N2170_W800FFWL-20170601-1601 - after reboot.txt unraid-diagnostics-20170601-1533.zip Edited June 1, 20179 yr by fted Added diagnostic zip (taken before reboot)
June 1, 20179 yr Community Expert Instead of attaching the syslog and/or SMART for any disk you should always go to Tools - Diagnostics before rebooting if possible and post the complete diagnostics zip. That disk doesn't look good. Do you have another you can use for rebuilding? I would like to know more about your other disks before continuing, so post your diagnostics as mentioned. Diagnostics contains syslog(s), SMART for all disks, and many other useful things. It is also a zip file so is much smaller than the plain text.
June 1, 20179 yr Author Understood, attached zip taken before reboot in first post. Well, the parity drive is a new WD RED. The first, and largest data drive (4TB) is the one that failed and comes from a Segate External drive. The second largest data drive (1TB) Comes from an external WD Elements drive. The third data drive is an old internal 2.5 Hitachi drive of 250 GB. So, i guess using only old drives, these failures are expected. Yes, I've got a newly bought WD RED ready to replace it.
June 1, 20179 yr Community Expert 44 minutes ago, fted said: The third data drive is an old internal 2.5 Hitachi drive of 250 GB. Doesn't mean it's about to fail, but wow, over a million LCC: 193 Load_Cycle_Count 0x0012 001 001 000 Old_age Always - 1199625
June 1, 20179 yr Community Expert 48 minutes ago, fted said: The third data drive is an old internal 2.5 Hitachi drive of 250 GB. I personally wouldn't waste a port on a drive that small, but since it is already part of the parity array leave it until you can replace it.
June 1, 20179 yr Author I have not done any testing or pre clearing on the new drive, and I was thinking its better to replace the old drive asap, while the array is at risk. What do you think? Yes, that small drive will have to go at some point On the other hand, nothing is running at the moment and I'm not in a hurry. Edited June 1, 20179 yr by fted
June 1, 20179 yr Community Expert IMO, unless you can power down the server while you test the spare better to replace it immediately without testing than to continue using the array at risk.
June 2, 20179 yr Author New drive up and running, thanks! Will investing the old drive, now that its out to see what I can learn from it.
June 2, 20179 yr Community Expert 197 Current_Pending_Sector 0x0012 092 064 000 Old_age Always - 672 198 Offline_Uncorrectable 0x0010 092 064 000 Old_age Offline - 672 It looks really bad, good for a paper weight and not much else.
June 19, 20179 yr Author Yeah, it Failed and could not complete some diagnostic tests. At least I discovered unraid and set up redundancy before it happened.
Archived
This topic is now archived and is closed to further replies.