Is hard-disk really dead?

opt2bout,
I'm using 4.2.18 and am having problems, not 4.2.19.

I have a similar problem with a READYNAS 600 and Seagate ST31000333AS (1TB). I replaced an actually dead drive (not responsive to a windows-based SATA interface), and received email notification of the successful resync. RAIDar shows all green lights for the disks. However, RAIDiator shows flashing yellow and the Health is listed as dead. I tried upgrading from 4.2.17 to 4.2.19-T9 which did not fix this. I tried swapping the disk with the adjacent bay, and the Dead disk status in RAIDiator follows this disk.

Please let me know if you guys are find out anything new.

Think I may have had this issue too.

First disk to become 'Dead' had one smart error: Offline Uncorrectable 1. So I let it slide.
Second disk to fail seems to have no smart errors but I'm guessing a disk can have no errors and still fail.

When the first disk failed I replaced it with a new one. Afterwards I decided to add back in the failing disk to see what would happen. It resynced and expanded and has been working away solid for nearly 2 months...
Last week then the 2nd disk failed. I only got around to it today but I just rebooted the nas and it started a resync and hasn't reported a problem so far.
First disk to fail was in slot 3 which I moved to 6. 2nd disk is in slot 4 and hasn't been moved, so it doesn't seem to be a slot specific problem at least.

I think I ran a firmware update shortly before disks started failing. I could be wrong there though because I see no mention of a firmware update in the logs. Unless that sort of thing isn't logged?

Readynas Pro Pioneer Edition, Running X-Raid 2. Firmware: RAIDiator 4.2.15.
6xWestern Digital Caviar Green 2TB.
Disk 1 WDC WD20EADS-00R6B0 1863 GB , 36 C / 96 F , Write-cache ON OK
Disk 2 WDC WD20EADS-00R6B0 1863 GB , 37 C / 98 F , Write-cache ON OK
Disk 3 WDC WD20EARS-22MVWB0 1863 GB , 33 C / 91 F , Write-cache ON OK
Disk 4 WDC WD20EADS-00S2B0 1863 GB , 39 C / 102 F , Write-cache ON OK
Disk 5 WDC WD20EARS-00MVWB0 1863 GB , 35 C / 95 F , Write-cache ON OK
Disk 6 WDC WD20EADS-00R6B0 1863 GB , 35 C / 95 F , Write-cache ON OK

RhysAndrews wrote:
opt2bout, I'm using 4.2.18 and am having problems, not 4.2.19.

Yeah, I finally got a copy of 4.2.18 and updated the firmware. Less than 24 hours later--BAM! Volume is re-syncing on its own. In the next 24 hours I predict that the drive in Bay 1 will go "DEAD" without any SMART errors (it has been running 542 hours since back-revving to 4.2.17 and absolutely zero problems. Less than one day after updating to 4.2.18 and I am having erratic behavior.
I thought maybe the "green" drives may be at issue with the firmware. But then I recall, the first drive to "fail" (which is now in use on another server) wasn't a green drive.
But something in the newer firmware is triggering this. I will update this in a few days to see what happens. I sure liked having my Lion backups running though.

Be advised that 4.2.18 has been pulled from the website. I recommend you either revert to 4.2.17 or try 4.2.19 T4.

Yeah, 4.2.17 didn't have Lion Time Machine support. The security advisory on 4.2.18 doesn't affect us, the unit is just running for me...unless there was something else wrong with 4.2.18.??

4.2.19-T4 caused the Bay 1 drives to go DEAD after a few hours (< 24)...three drives later and we knew something was wrong--but not with the drives. Contacted support, but they couldn't help us with beta f/w, so we downgraded to 4.2.17 and the drives worked fine (now for 3 weeks @ 24/7). We moved to 4.2.18 to get Time Machine support. The drive has resync'd and we are waiting to monitor the status & report back to support.

Support told us to wait on 4.2.19 release before upgrading. They weren't aware of T9, but warned me they won't support beta f/w.

By the way...where is 4.2.19-T9 anyway? The thread in the forum still shows T4 and fudging the URL to be http://www.readynas.com/download/beta/r ... -4.2.19-T9 doesn't work.

EDIT: never mind, I noticed your thread changed to reflect the current T4. T4 is evil!! :(

I was wrong on T9, I'll blame the keyboard and have edited my previous post. If you are not using AFP, the security hole in 4.2.18 may not affect you.

If you encounter problems with 4.2.19 T4 that is apparently firmware, please post your observations in the Beta threads. That is where the Jedi are looking for feedback.

PapaBear wrote:
I was wrong on T9, I'll blame the keyboard and have edited my previous post. If you are not using AFP, the security hole in 4.2.18 may not affect you. If you encounter problems with 4.2.19 T4 that is apparently firmware, please post your observations in the Beta threads. That is where the Jedi are looking for feedback.

I did...

viewtopic.php?f=51&t=56010
viewtopic.php?f=24&t=55594