NETGEAR is aware of a growing number of phone and online scams. To learn how to stay safe click here.
Forum Discussion
No volume exists (another case)
Hallo there, I have a problem similar to what davidburchett52 describes. However, I douldn't figure out how that part of the problem was solved. My device is a ReadyNAS Ultra 4 Plus running OS 6...
Thanks for your replies, Sandshark and StephenB.
I just finished checking the three original disks using the Data Lifeguard Diagnostic for DOS.
The quick test returned no errors for three disks.
Extended media test also returned no errors for disk #2 which I had originally suspected, as in my previous post.
I concluded it must be a hardware error with the ReadyNAS.
So with all original disks removed, I inserted the two new disks in two slots in the NAS, including one in slot #2 which disk I had originally suspected.
The NAS wouldn't boot!
I tried the new two disks in several slot combinations, but still the NAS wouldn't boot, until I removed one disk and inserted the other in slot #1 and powered on, at this point the NAS performed a factory reset, initialised Raid-X, created a volume and completed the boot!
I'm still unable to access the web GUI, neither with my old password, nor the default admin:netgear1
So, with the NAS still running, I inserted the other new disk in slot #2, and to my surprise it was detected as indicated in the LCD display, and data synching is now taking place.
I will wait until it finishes, and reboot. (it's running too slow taking into consideration that it's a an empty volume)
Now,
What does a factory reset mean in this case, other than resetting networking configuration?
If I remove the new two disks, can I re-insert the old ones safely? Will the old array settings be correctly identified from themselves, or is part of it lost due to the reset?
Could it have been all caused by corrupted configuration or another glitch?
gharbeia wrote:
I'm still unable to access the web GUI, neither with my old password, nor the default admin:netgear1
The default for OS6 is admin:password, not netgear1.
gharbeia wrote:
(it's running too slow taking into consideration that it's a an empty volume)
The fullness of the volume isn't relevant. RAID creates a virtual disk, and the file system runs on top of that. All the blocks are being synced, including free space.
gharbeia wrote:
If I remove the new two disks, can I re-insert the old ones safely? Will the old array settings be correctly identified from themselves, or is part of it lost due to the reset?
The operating system is on the disks (along with the settings). A factory reset (or factory install) creates a new operating system on the disks, and an empty data volume. That's all it does.
So if you put back your original disks, your original problem will come back.
gharbeia wrote:
Could it have been all caused by corrupted configuration or another glitch?
Perhaps. It's hard to say what caused it. If you could get the log zip file to Netgear, they could give you more information on what happened.
But I don't think you've ruled out a failure with one of the original disks. The quick test in lifeguard is more of a confidence test than a diagnostic. Even the non-destructive media test has its limits - I've had disks that passed that test, but failed when I ran the destructive write-zeros test.
BTW, why did you choose lifeguard for dos instead of lifeguard for windows? Just curious.
Thanks for your explanations, StephenB.
I chose Lifeguard for DOS because we're a Linux household. I have no access to Windows machines. Preparing FreeDOS boot media is easy.
Marc_V was kind enough to offer to take a look at the logs, and I sent them to him in a private message. I hope we can learn something that can help us.Case update:
I returned the three original disks in their order to the NAS and powered it, but it wouldn't boot, which is expected. The LCD would bear "Booting", and stays there.
I powered down, remove disk #2, but still it wouldn't boot. which is a development from the initial situation!
I tried recycling power with other disks removed, once a time, but it still wouldn't boot with any combination.
I noticed somthing: the numbered leds don't seem to reflect the actually inserted disks. I get leds only 3 & 4 lit when in fact disks 1, 2 & 3 are inserted. I had noticed this before but wasn't sure whether it was that or the haze from neighbouring leds was illuminating the others.
I think it's time to check the chassis. Do you have a spare SATA drive, any size? If so, remove all drives and boot with just that spare. If you remove all partitions on it with Windows first, it'll make creating the volume on it easier. But if you don't, you can go in and format the drive with the NAS.
After the volume is created and you can access it via the GUI, power down and move it to the next bay, then power up. Repeat with all bays and make sure it boots and the volume is accessible. If it fails to boot in one or more bays, the chassis has a hardware failure. If that is the problem, you can put the drives only in the good bays (if there are enough), or move the drives over to another OS6 NAS. Since you moved to OS6, you can just put the drives in a current model chassis and have everything available. Since your Ultra is Intel based, an Intel based replacement will also allow you to continue to use any apps you installed.
NETGEAR Academy
Boost your skills with the Netgear Academy - Get trained, certified and stay ahead with the latest Netgear technology!
Join Us!
