NETGEAR is aware of a growing number of phone and online scams. To learn how to stay safe click here.
Forum Discussion
Solved
Solid red alert LED, no network link, flashing red disk light
It has the latest ReadyNAS firmware. One disk started complaining about SMART errors but continued to function (while likely reducing performance). I bought a replacement drive but the drive was ba...
My bad. The ethernet cable was loose. When I fixed that I got a link light and found the unit at its usual IP address. (I was expecting the worst so I didn't check the basic stuff like "is it plugged in?")
And I am being really stupid because the model of disk I bought nearly matches the netgear compatibility list except that it is SAS.
Sorry to waste your time!
If you are using XRAID or a RAID mode with redundancy, I sugggest powering down the NAS and removing the failed drive. At this point it's not helping you.
If the system boots, the array will be degraded, so you should update your backup right away (and if you don't have a backup, you should back up everything you can).
If the system doesn't boot, or if the array doesn't mount then you should contact paid support (my.netgear.com)
Thanks. I have XRAID (which means I have redundancy, right?). And, no, it does not boot. It sounds like that near-failed drive went into an absolutely failed state and the flashing red fault LED on the drive is telling me that.
Is it normal for the unit to not boot when one drive is failed? Intuitively, it sems to me like it ought to boot in a read-only mode so it can clearly tell you what state it is in. (I did not find documentation in the manual about the meaning of the fault LED on each drive. Obviously it shows a "fault" but what kind of fault and what are the next steps when the LED is flashing.)
I can see how even booting in read-only mode wears the remaining drives so if it refuses to boot it preserves those drives longer. But that also makes it impossible to back up the data which sounds like a really good idea when a drive fails.
So I have turned it off awaiting the replacement, replacement drive (it's "replacement, replacement" because I bought a replacement drive weeks ago but it turned out to be faulty).
Hi nmgeek
As StevenB said, you should remove the near-failed drive. That drives is of little use to you now. I very bad disk can certainly cause the kind of problems you report. That disk is likely to spew tons of PCI errors and sector errors. The raid is out of sync as the re-sync never completed so it will cause a problem with trying to boot as the NAS will try and (and fail) to assemble the RAID upon boot.
Best thing is to not use the faulty disk at all. With X-RAID and 4 disks you have 1 disk redundancy so given that the 3 other disks are OK, then you are fine. Boot the NAS with the 3 good disks only.
As a piece of advise, it is a very bad idea to try and re-insert a known bad disk. It triggers a re-sync of the RAID and a sync is the most strenuous process for the disks. A failing disk is almost certain to suffer a quick death during that attempted re-sync.
nmgeek wrote:
And, no, it does not boot.
Are you saying that it won't boot with the failed drive removed?
If so, try installing RAIDar and see if can discover the NAS. https://kb.netgear.com/20684/ReadyNAS-Downloads
nmgeek wrote:
Thanks. I have XRAID (which means I have redundancy, right?).
Correct. That doesn't mean your data is safe, as there are failure modes where redundancy won't help.
nmgeek wrote:
Is it normal for the unit to not boot when one drive is failed? Intuitively, it sems to me like it ought to boot in a read-only mode so it can clearly tell you what state it is in.
It won't boot read-only unless it sees something wrong with the file system (which runs on top of RAID). That's because the goal of RAID is to allow you to continue to access (and update) your data even if you are replacing a disk.
However, a failed drive can still prevent the system from booting - it depends on exactly how it failed. Also, the system normally boots from disk 1 - so it is fairly common for the system boot to fail when disk 1 fails.
Thanks for your very detailed, knowlegable response, StephenB
I actually never tried booting it with the failed drive removed.
Today, the replacement replacement drive arrived. I installed it and powered the unit up.
The failed drive was number 3.
After about 1.5 hours of being powered up the state of the system is now:
- No drive fault lights: all four drives have their blue power lights
- The system error LED is flashing short-on, short-on, then long-off
- Power light lit
- No link light
- No response pinging it's static IP address (expected since the link light is not on)
Next step? RAIDar? (which means I have to comandeer someone's Windows PC since RAIDar only runs on Windows?)
> The system error LED is flashing short-on, short-on, then long-off
Correction: it's short-on, long-on.
NETGEAR Academy
Boost your skills with the Netgear Academy - Get trained, certified and stay ahead with the latest Netgear technology!
Join Us!
