Jump to content
We're Hiring! Full Stack Developer ×

HELP. One drive dead


pras1011

Recommended Posts

I put the disc back into unraid and it showed up. However unraid it warning of the reallocated sector count. All other hdds are zero but disk2 is 11728.

 

Are you sure that unraid wont disable a drive because of this?

 

My biggest concern is whether the data on disk2 was written to properly when I was writing to it (before the failure)?

Link to comment
Are you sure that unraid wont disable a drive because of this?

It was likely disabled because of this, it just doesn't explain why it wasn't detected after that.

 

My biggest concern is whether the data on disk2 was written to properly when I was writing to it (before the failure)?

In theory it should be all in the emulated disk, in practice it's possible that the file that was being written at the time the disk switched to being emulated has some corruption, but all the rest would be OK.

 

 

Link to comment
24 minutes ago, pras1011 said:

But at the time of the failure, the hdd was only being read due to the parity check and no writing was taking place.

Then you have nothing to worry about, I only mentioned that because you said:

19 hours ago, pras1011 said:

My biggest concern is whether the data on disk2 was written to properly when I was writing to it (before the failure)

I understood that as the disk failed while you were writing to it.

Link to comment

If a disk read fails, unRAID may read its data from the parity calculation instead, and then try to write it back to the disk. When that write fails, the disk is disabled.

 

It is usually possible to get the SMART from unRAID instead of putting the disk into another system. Note that it is almost always a bad idea to put an unRAID disk into another system and try to work on it there, since you will invalidate parity.

Link to comment
2 hours ago, pras1011 said:

Yes, in the syslog there were some reads and at the end there were some writes before the disk was disabled

That's normal, when there's a read error unRAID uses parity plus all other disks to compute the correct data and tries to write it back, if the write fails the disk is disabled.

Link to comment

It is very possible to boot unRaid on a Windows computer and run preclear. No need to define an array, and disks will not be corrupted in any way if you never define or start the array. Afterwards you can remove the precleared disk and reboot into Windows. If you have an old computer this may be a good option.

 

Preclear does two things. It clears the disk which is only needed to quickly add a new disk to a parity protected array. And it tests the disk pretty thoroughly by prereading the entire disk, then filling the disk with zeroes, and finally verifying the disk is zeroed. This action helps the SMART system in the drives to identify and mark bad and marginal sectors.

 

Note that unRaid's clear function only zeroes the disk. The preread and post validation reads are not done. Also, with unRaid, the disk is added to the array immediately. With preclear you look at the results and possible SMART attribute issues after the preclear and then decide whether to use the drive or perhaps return for an exchange if it has issues.

Link to comment
1 hour ago, pras1011 said:

I don’t have a spare computer but there must be a way to run preclear in a Windows environment?

No. But if you want to test the disk you can use the disk manufacturer's utility in Windows as already mentioned.

 

Since your intention is to rebuild an existing disk you don't need a clear disk. The only time unRAID requires a clear disk is when ADDING a disk to a NEW slot in an array that already has valid parity. This is so parity will remain valid.

 

I know I'm sort of repeating what has already been said, but sometimes different ways of saying things helps with understanding.

Link to comment

Archived

This topic is now archived and is closed to further replies.

×
×
  • Create New...