hello everyone.

 

I am having a problem with one of my drive.

I have a spare drive to replace it. but before unplugging it I managed to run a smartcrl report.

 

one detail that might be of use. I had to reboot my unraid before I could run the report.

I would really appreciate if someone could comment on the results.

 

Thanks for your help

R

 

smartresults.txt

hello everyone.

 

I am having a problem with one of my drive.

I have a spare drive to replace it. but before unplugging it I managed to run a smartcrl report.

 

one detail that might be of use. I had to reboot my unraid before I could run the report.

I would really appreciate if someone could comment on the results.

 

Thanks for your help

R

Disks are disabled when a "write" to them fail.  The smart report only shows 1 sector pending re-allocation, apparently found when you asked the disk to perform a "long" test recently. I don't think that is related.

 

There is nothing else showing why the disk may have failed during the "write" operation.  Unless you saved the syslog before re-booting,  you'll not have any clues for analysis. 

 

Suspect loose power or data cables first, unless running on one of the beta versions of unRAID where disks can not spin up after being spun down on some disk controllers.  Other than that, it could be a defective disk, power supply, power supply splitter, drive tray, disk-controller, or cable.  We have no idea, since you did not supply any syslog for analysis, or describe your hardware.

 

See the sticky at the top of this forum: http://lime-technology.com/forum/index.php?topic=9880.0

 

Joe L.

 

thanks for taking the time to answer.

I am aware of the reasons that could lead to a disk_dsbl red ball. that's why I am not worried.

 

unfortunately I could not provide a smartctl prior rebooting because it would simply fail

and I was too stupid to think of saving my syslog ((

 

I am running 4.7

the hardware is pretty common for an unraid build

norco 4224

supermicro sil8f

2 mv8 with a few wd20ears for data, 1x2GB seagate for parity, and a 500GB seagate for cache.

nothing much running on my 4.7 except unmenu.

 

I was wondering whether I should RMA the disk or not.

I know the procedure to replace the disk (which I already did) and my array will be fine.

fortunately I had run a parity check a couple of days ago so my data can be considered as safe/valid (discussion on this type of statement have been ongoing )

 

I was sharing my report hoping it would raise an obvious reason to the failure so I could RMA the disk.

but from your answer I guess that I will have to be more patient on that.

I guess (if you or someone else does not advise me otherwise) that I will preclear it and add it to my array.

I will then watch it for futur failure.

 

thank you again for your time, it is highly appreciated.

 

Cheers,

R

 

 

 

 

After the pre-clear the Current_Pending_Sector raw value should be zero.

After the pre-clear the Current_Pending_Sector raw value should be zero.

 

dgaschk,

 

thanks.

I will keep that in mind.

 

R