n8800 red light when bay is empty ?

[FMaz]

Hi there !
First post, so I'll try to be pertinent


I had few (6) "current pending sectors" on my brand new WD harddrive ( yes, the model is in the HDD compatibility list )

24 hours later, the current pending sector count dropped to 2.
And a couple of hours later, the RAID was degraded, and the drive marked as bad, with the N8800 beeping the the red light on for the bay #3.

I've removed the hard drive. The red light still on.


I've passed it to the Western digital disk utility. Bad block have been found, but reported as repaired.
So I wanted to put back the --now repaired ?-- disk in the bay #3. The the red light still on, and the Thecus doesn't want to detect the disk.

I've placed the disk in the bay #6, the disk is detected OK. The raid have rebuilted, is marked as Healty, and a bad block scan reported the disk as Healty too.

But the bay #3 is still have a red light.


What's the problem with this red light ? When a disk failed, the bay is permanently unusable ?



The thecus support told me to reboot, but I'm doing a SMART test on the disk, and I find the reboot option a pseudo-solution to a hot-swap problem.

[Pskone]

I can't help with the light, but do you have WDTLER enabled on your drives?

I've currently got a similar issue with a 1.5GB WD drive on a N7700, the NAS reports pending sectors and after that WDDiag finds bad sectors and fixes them and the NAS goes back to 0 pending, but after a few days it's up to 5 pending again. If I do a bad sector scan on the NAS the drive drops from the array even though WDTLER is set to 7s. I'm going to try reducing it to say 5 seconds, maybe the Thecus NAS's have a lower timeout?

If you find a solution to deal with bad sectors inside the NAS without the drive dropping can you post back here?

[FMaz]

If I find any kind of solution, of course I'll post it

... but actually, I don't even know what "WDTLER" is.

I also have 4x 1.5 TB western digital Green disk (those from the supported HDD list)