Jump to content

Failed Drives


Recommended Posts

Posted
On 12/23/2021 at 4:12 PM, JorgeB said:

Test completed without errors, so disk is OK for now.

Right! And my question is, is this disk advisable to be used for the long term?

 

Posted
3 hours ago, AlexKoh said:

is this disk advisable to be used for the long term?

Difficult to say, it could last days or years, but that basically goes for any disk, just keep monitoring it.

  • 2 months later...
Posted

Just to update and summarize.

 

Realised that my mother board's sata port is throwing random errors. Hence decided to swap it this year with ASUS work station pro motherboard. So far disk did not throw any errors and hope that it stays this way.

 

And as suggested will continue to monitor SMART stats

  • 8 months later...
Posted (edited)
On 4/10/2021 at 11:58 AM, Mason736 said:

So I woke up this morning, and two of the ST8000VN04 drives had dropped from the array with read errors.  They are both brand new drives from Seagate.  
 

I'm convinced is the issue with the ERC and low voltage spin up, so I followed the above instructions.  We will see if they, or any of the other VN04 drives drop out of the array again.

 

Did you ever figure this out? After enabling spin down, two of my drives died - a ST8000VN04 dropped and also a WD 10TB Red completely died. 

 

The ST8000VN04 doesn't have any SMART errors, and I was able to add it back to the array, but on array shutdown, I got a sector error in the logs (but nothingin SMART). Very weird.

 

Nov  5 20:02:07 nasserv kernel: XFS (md1): Unmounting Filesystem
Nov  5 20:02:07 nasserv kernel: md: disk22 read error, sector=3907717616
Nov  5 20:02:07 nasserv kernel: sd 1:0:6:0: Power-on or device reset occurred
Nov  5 20:02:07 nasserv kernel: md: disk22 write error, sector=3907717616
Nov  5 20:02:07 nasserv kernel: md: disk22 read error, sector=0
Nov  5 20:02:07 nasserv kernel: md: disk22 write error, sector=0

 

UPDATE... Looks like there maybe a compatiblity issue with the ST8000VN04 and Unraid?

 

 

Edited by coolspot
  • 7 months later...
Posted

Are SSDs allowed?

I would advice against buying Patriot P220 1024GB. They are reported to have flaky controllers.

I bought two of them in january, now (5 months later):

- one of them dropped from the array a month ago and did so until i erased with "secure erase" tool (bad controller?)

- the other started to have reallocated sectors just today

 

Will change to samsung 870 evo.

Posted (edited)

I meant: allowed to report ssds in this thread, since i didnt want to start an own topic for failed ssds. I  only saw failed hdds reported here, so...

 

Also, i had them in a btrfs raid 1 pool. As i understood, btrfs takes care of ("soft"?) trimming and i didn't change anything on the default pool settings.

Edited by x3n0n
Posted
On 11/5/2022 at 8:27 PM, coolspot said:

 

Did you ever figure this out? After enabling spin down, two of my drives died - a ST8000VN04 dropped and also a WD 10TB Red completely died. 

 

The ST8000VN04 doesn't have any SMART errors, and I was able to add it back to the array, but on array shutdown, I got a sector error in the logs (but nothingin SMART). Very weird.

 

Nov  5 20:02:07 nasserv kernel: XFS (md1): Unmounting Filesystem
Nov  5 20:02:07 nasserv kernel: md: disk22 read error, sector=3907717616
Nov  5 20:02:07 nasserv kernel: sd 1:0:6:0: Power-on or device reset occurred
Nov  5 20:02:07 nasserv kernel: md: disk22 write error, sector=3907717616
Nov  5 20:02:07 nasserv kernel: md: disk22 read error, sector=0
Nov  5 20:02:07 nasserv kernel: md: disk22 write error, sector=0

 

UPDATE... Looks like there maybe a compatiblity issue with the ST8000VN04 and Unraid?

 

 

Does anyone have an update to know if the compatibility issue has been fixed with subsequent releases of Unraid?  I’d love to go back to being able to spin down my array without dropping HDDs from the array.

  • Like 1
  • 8 months later...
Posted

 

ST18000NT001-3LU101 Seagate Ironwolf Pro NAS.

Installed for a year, ready as a spare and precleared. Added to the Array for a couple of days and had pre-allocation and uncorrectable errors.

Will be an RMA warranty.

 

Join the conversation

You can post now and register later. If you have an account, sign in now to post with your account.
Note: Your post will require moderator approval before it will be visible.

Guest
Reply to this topic...

×   Pasted as rich text.   Restore formatting

  Only 75 emoji are allowed.

×   Your link has been automatically embedded.   Display as a link instead

×   Your previous content has been restored.   Clear editor

×   You cannot paste images directly. Upload or insert images from URL.

×
×
  • Create New...