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.
Okay. . . next stupid question:
In my ongoing quest to determine if OS6 is ready to house any actual data that I give a hoot about, I decided to do a little "Fault Tolerance" testing.
Here's the test platform:
A "new out of the box" ReadyNAS Pro with stock CPU, and Memory upgraded to 4GB's
4 X 2TB Western Digital WD2002FYPS RE4 Hard Drives populated in drive bays 1 through 4 (RAID 5 - X-RAID2)
RAID Array build process completed and stable, then rested for 12 hours
BIOS recently upgraded to v2.0 (Thanks mdgm!)
After confirmation that test data could be written to and read from the NAS, I pulled the drive out of bay 4 (hot) to pseudo-simulate a drive failure.
Waited 15 minutes, reconfirmed that test data could be written to and read from the NAS, then I replaced the drive in bay 4 with a different unformatted Western Digital WD2002FYPS RE4 Hard Drive. I checked the GUI which had the expected notifications of drive removals and insertions, but that's about it. I kind of expected the new drive to be added back into the array after the obligatory re-sync period. To the contrary, the new drive is just sitting there and the RAID5 array seems oblivious to the fact that a fresh drive is available for reintegration back into the array. I'm obviously missing something here. . .
Just for S's&G's I've rebooted, pulled and reinserted the blank drive a couple of times, skimmed the official OS6 documentation; I can't figure out how to reintegrate the new drive into the exsisting array.
This GUI currently shows this:
School me please! This should not be this counterintuitive. . . :nashammer:
In my ongoing quest to determine if OS6 is ready to house any actual data that I give a hoot about, I decided to do a little "Fault Tolerance" testing.
Here's the test platform:
A "new out of the box" ReadyNAS Pro with stock CPU, and Memory upgraded to 4GB's
4 X 2TB Western Digital WD2002FYPS RE4 Hard Drives populated in drive bays 1 through 4 (RAID 5 - X-RAID2)
RAID Array build process completed and stable, then rested for 12 hours
BIOS recently upgraded to v2.0 (Thanks mdgm!)
After confirmation that test data could be written to and read from the NAS, I pulled the drive out of bay 4 (hot) to pseudo-simulate a drive failure.
Waited 15 minutes, reconfirmed that test data could be written to and read from the NAS, then I replaced the drive in bay 4 with a different unformatted Western Digital WD2002FYPS RE4 Hard Drive. I checked the GUI which had the expected notifications of drive removals and insertions, but that's about it. I kind of expected the new drive to be added back into the array after the obligatory re-sync period. To the contrary, the new drive is just sitting there and the RAID5 array seems oblivious to the fact that a fresh drive is available for reintegration back into the array. I'm obviously missing something here. . .
Just for S's&G's I've rebooted, pulled and reinserted the blank drive a couple of times, skimmed the official OS6 documentation; I can't figure out how to reintegrate the new drive into the exsisting array.
This GUI currently shows this:
School me please! This should not be this counterintuitive. . . :nashammer:
NETGEAR Academy
Boost your skills with the Netgear Academy - Get trained, certified and stay ahead with the latest Netgear technology!
Join Us!
