NETGEAR is aware of a growing number of phone and online scams. To learn how to stay safe click here.
Forum Discussion
Solved
OS6 now works on x86 Legacy WARNING: NO NTGR SUPPORT!
Update: It is now unofficially possible using NTGR images to update legacy hardware to os6.X See Post #3, for directions to install 6.2.1 on x86 Ultra and Pro Models. (ARM NOT SUPPORTED by this OS) ...
mdgm and I have decided that its time to lock this thread. So please do post any new OS6 on Legacy issues on their own threads.
So for any of you who have not been following along, I've been putting a brand new (excess inventory) ReadyNAS Pro through its paces with a fresh install of OS6 version 6.0.8.
About eight posts ago I ended with a list of eleven steps that I either had done or were planning on doing. The conclusion of that little experiment was simple. . . It turned out to be a BAD HARD DRIVE. Even though all the short/quick diagnostic tests I attempted said that the drive was okay the ReadyNAS knew otherwise. Once I resorted to a FULL Diagnostic / Surface Scan the problems eventually came to light. So I set that Hard Drive aside to send back to Western Digital for warranty replacement.
Fortunately I had a spare hard drive of the same brand and model that I could use in place of the newly discovered BAD drive. So, for the past week I have been pushing and pulling Terabytes and Terabytes worth of data to and from this ReadyNAS Pro using different protocols and methods trying to test every possible scenario before putting OS6 into a production environment. I also experimented with some really crazy drive swapping scenarios that I would NEVER attempt in a production environment. All in all, the vast majority of testing went pretty well, until. . . I get this E-Mail out of the blue from the NAS under test:
"Detected increasing ATA error count: [24636] on disk 5 [WDC WD2002FYPS-02W3B0, WD-WCAVY5956816] 2 times in the past 30 days. This condition often indicates an impending failure. Please be prepared to replace this disk to maintain data redundancy."
I'm like "What the Hell?" The distressing thing about the timing of this message is it took place about 20 minutes into a volume expansion experiment that I was performing. You see, all the testing that I was doing previously was with four 2TB Drives (Bays 2,3,4,5 populated. 1 and 6 empty). So I filled the volume with test data to ensure that I would get an alert stating that it was getting full. Once I was satisfied that the volume capacity alerts were working properly, I thought it would be a good time to do a Volume Expansion test. I inserted a fresh drive into Bay 6. Along with the message above I received another that said:
"Disk in channel '5' (Internal) changed state from ONLINE to FAILED."
So I removed the drive from Bay 5 and started a failure diagnosis on it. Here comes the weird part - After doing a FULL diagnostic on the drive with two different tools (to include a full SURFACE SCAN) both diagnostics reported zero errors or problems of any kind. Again I say: What the hell? So I wiped the first and last million sectors of the drive in preparation for reintroduction to the array.
Since performing a full diagnostic on a 2TB drive takes about 5 to 6 hours, the drive that I popped into Bay 6 had finished the integration process. Unfortunately, since the drive that was in Bay 5 failed during a Volume Expansion, the Array as a whole was still considered "Degraded". So, in an attempt to "fool" the ReadyNAS into forgetting about the drive that failed from Bay 5, I shut the unit down and moved the new drive that was in Bay 6 to Bay 5, and powered it back on, waited 15 or 20 minutes and reinserted the alleged "BAD" drive that was originally in Bay 5 into Bay 6. The insertion was detected and this is what I saw on the GUI:
Which leads me to three questions, which are:
1.) Why do you suppose the ReadyNAS thinks that this drive has issues when two different Hard Drive diagnostic programs say otherwise?
2.) Does OS6 have some sort Hard Drive Database that remembers every Hard Drive that has ever been in it?
3.) If number 2 above = YES, is there some way to clear that data so that the ReadyNAS reassess the condition of a particular drive from scratch sometime in the future?
As always. . . Thanks in advance,
About eight posts ago I ended with a list of eleven steps that I either had done or were planning on doing. The conclusion of that little experiment was simple. . . It turned out to be a BAD HARD DRIVE. Even though all the short/quick diagnostic tests I attempted said that the drive was okay the ReadyNAS knew otherwise. Once I resorted to a FULL Diagnostic / Surface Scan the problems eventually came to light. So I set that Hard Drive aside to send back to Western Digital for warranty replacement.
Fortunately I had a spare hard drive of the same brand and model that I could use in place of the newly discovered BAD drive. So, for the past week I have been pushing and pulling Terabytes and Terabytes worth of data to and from this ReadyNAS Pro using different protocols and methods trying to test every possible scenario before putting OS6 into a production environment. I also experimented with some really crazy drive swapping scenarios that I would NEVER attempt in a production environment. All in all, the vast majority of testing went pretty well, until. . . I get this E-Mail out of the blue from the NAS under test:
"Detected increasing ATA error count: [24636] on disk 5 [WDC WD2002FYPS-02W3B0, WD-WCAVY5956816] 2 times in the past 30 days. This condition often indicates an impending failure. Please be prepared to replace this disk to maintain data redundancy."
I'm like "What the Hell?" The distressing thing about the timing of this message is it took place about 20 minutes into a volume expansion experiment that I was performing. You see, all the testing that I was doing previously was with four 2TB Drives (Bays 2,3,4,5 populated. 1 and 6 empty). So I filled the volume with test data to ensure that I would get an alert stating that it was getting full. Once I was satisfied that the volume capacity alerts were working properly, I thought it would be a good time to do a Volume Expansion test. I inserted a fresh drive into Bay 6. Along with the message above I received another that said:
"Disk in channel '5' (Internal) changed state from ONLINE to FAILED."
So I removed the drive from Bay 5 and started a failure diagnosis on it. Here comes the weird part - After doing a FULL diagnostic on the drive with two different tools (to include a full SURFACE SCAN) both diagnostics reported zero errors or problems of any kind. Again I say: What the hell? So I wiped the first and last million sectors of the drive in preparation for reintroduction to the array.
Since performing a full diagnostic on a 2TB drive takes about 5 to 6 hours, the drive that I popped into Bay 6 had finished the integration process. Unfortunately, since the drive that was in Bay 5 failed during a Volume Expansion, the Array as a whole was still considered "Degraded". So, in an attempt to "fool" the ReadyNAS into forgetting about the drive that failed from Bay 5, I shut the unit down and moved the new drive that was in Bay 6 to Bay 5, and powered it back on, waited 15 or 20 minutes and reinserted the alleged "BAD" drive that was originally in Bay 5 into Bay 6. The insertion was detected and this is what I saw on the GUI:
Which leads me to three questions, which are:
1.) Why do you suppose the ReadyNAS thinks that this drive has issues when two different Hard Drive diagnostic programs say otherwise?
2.) Does OS6 have some sort Hard Drive Database that remembers every Hard Drive that has ever been in it?
3.) If number 2 above = YES, is there some way to clear that data so that the ReadyNAS reassess the condition of a particular drive from scratch sometime in the future?
As always. . . Thanks in advance,
NETGEAR Academy
Boost your skills with the Netgear Academy - Get trained, certified and stay ahead with the latest Netgear technology!
Join Us!
