NETGEAR is aware of a growing number of phone and online scams. To learn how to stay safe click here.
Forum Discussion
Solved
Help. I think my ReadyNas Ultra6 is dying.
One day I did not find access to the storage. Looked at the NAS, it was not working, only blinking both LEDs. I turned it off, blew out the dust inside, and turned it back on. It was also blinking an...
I agree this sounds like a power supply issue. While the volume is in re-sync, you should do nothing. But I hope you have a recent backup, as it could fail during re-sync in a way that makes the volume inaccessible.
Once the re-sync is complete, you can try booting the NAS with no drives. It's not a great test, but can be useful in some cases. If it boots more normally (up to the point of saying "no disks", of course), then that's another hint it is the supply.
If you have a spare ATX12V power supply (or one you can "borrow" from a PC), you can connect it externally just to see if that fixes it before you invest in a replacement supply.
Do you know what firmware you are running?
Strange_alex wrote:
But since I have 6 disks in Raid5 mode, and everything is filled with 80%, this process is not fast,
The amount of data in the volume does not affect the resync time. Resync requires every sector of every disk to be either read or written, even if the volume is empty.
Strange_alex wrote:
One day I did not find access to the storage. Looked at the NAS, it was not working, only blinking both LEDs. I turned it off, blew out the dust inside, and turned it back on. It was also blinking and wouldn't turn on. Every 5-6 seconds the green and blue LEDs light up at the same time for a very short time, and if you look behind the back wall, there is an attempt to spin the blades of both fans (they twitch) at the same moment when the LEDs blink. After some time of such attempts, the booting process starts and even succeeds.
This sounds like something is failing - perhaps the power supply (which can be replaced). Do you have a backup of the data?
I'm tagging Sandshark , as he might have some suggestions on troubleshooting.
I agree this sounds like a power supply issue. While the volume is in re-sync, you should do nothing. But I hope you have a recent backup, as it could fail during re-sync in a way that makes the volume inaccessible.
Once the re-sync is complete, you can try booting the NAS with no drives. It's not a great test, but can be useful in some cases. If it boots more normally (up to the point of saying "no disks", of course), then that's another hint it is the supply.
If you have a spare ATX12V power supply (or one you can "borrow" from a PC), you can connect it externally just to see if that fixes it before you invest in a replacement supply.
Yesterday, I found a 20TB drive and started backing up just as I was syncing. Since I have a lot of shares, and I didn't want to copy several streams in parallel, the NAS stayed half a night without load and.... did not reboot. Although earlier, judging by the output of the 'last' command, it could reboot every few minutes. Just in case I stopped the tailscale daemon beforehand, which shouldn't affect it in any way, but the fact remains - no reboots yet.
Problems with the power supply are the main theory so far, I will look for a replacement. Might be worth taking it out and checking for blown capacitors. As soon as I copy the contents - I will try booting without disks as you advised.Any other tests to check the power supply? I find it a bit strange that it reboots without load, but under load it is stable.
Does the blinking lights mean anything? Is it just a side effect of the disks not getting enough power to start?I don't understand anything anymore. For several days while copying 20TB of data (intermittently) there was not a single reboot, everything is stable. In the end, as you advised, I stopped the NAS, pulled out all disks and turned it back on. Booting started instantly, without any blinking LEDs, of course with the inscription “finding disks”. Put all disks back in, and... everything booted up perfectly and instantly, without any problems and has been working for almost 24 hours now.
If anything, ReadyNASOS version is 6.9.6.
But what is strange is that in the listing of the 'last' command the time after reboot (in brackets) does not correlate with the real time of the event:reboot system boot 4.4.157.x86_64.1 Thu Nov 21 20:49 - 12:15 (4+15:26)
reboot system boot 4.4.157.x86_64.1 Wed Nov 20 07:44 - 10:27 (02:43)
reboot system boot 4.4.157.x86_64.1 Wed Nov 20 07:39 - 10:27 (02:48)
reboot system boot 4.4.157.x86_64.1 Wed Nov 20 07:36 - 10:27 (02:51)
reboot system boot 4.4.157.x86_64.1 Wed Nov 20 07:31 - 10:27 (02:56)
reboot system boot 4.4.157.x86_64.1 Wed Nov 20 07:27 - 10:27 (02:59)
reboot system boot 4.4.157.x86_64.1 Wed Nov 20 07:23 - 10:27 (03:03)
reboot system boot 4.4.157.x86_64.1 Wed Nov 20 07:16 - 10:27 (03:11)
reboot system boot 4.4.157.x86_64.1 Wed Nov 20 07:12 - 10:27 (03:15)
reboot system boot 4.4.157.x86_64.1 Wed Nov 20 07:08 - 10:27 (03:18)
reboot system boot 4.4.157.x86_64.1 Wed Nov 20 07:02 - 10:27 (03:25)
reboot system boot 4.4.157.x86_64.1 Wed Nov 20 06:58 - 10:27 (03:29)
reboot system boot 4.4.157.x86_64.1 Wed Nov 20 06:51 - 10:27 (03:36)
reboot system boot 4.4.157.x86_64.1 Wed Nov 20 06:44 - 10:27 (03:43)
reboot system boot 4.4.157.x86_64.1 Wed Nov 20 06:40 - 10:27 (03:47)
reboot system boot 4.4.157.x86_64.1 Wed Nov 20 06:36 - 10:27 (03:50)
reboot system boot 4.4.157.x86_64.1 Wed Nov 20 06:33 - 10:27 (03:54)
reboot system boot 4.4.157.x86_64.1 Wed Nov 20 06:19 - 10:27 (04:08)
reboot system boot 4.4.157.x86_64.1 Wed Nov 20 06:09 - 10:27 (04:18)
reboot system boot 4.4.157.x86_64.1 Wed Nov 20 05:59 - 10:27 (04:28)
reboot system boot 4.4.157.x86_64.1 Wed Nov 20 05:49 - 10:27 (04:38)
reboot system boot 4.4.157.x86_64.1 Wed Nov 20 05:38 - 10:27 (04:49)
reboot system boot 4.4.157.x86_64.1 Wed Nov 20 05:18 - 10:27 (05:09)
reboot system boot 4.4.157.x86_64.1 Wed Nov 20 04:55 - 10:27 (05:31)
reboot system boot 4.4.157.x86_64.1 Wed Nov 20 04:49 - 10:27 (05:38)
reboot system boot 4.4.157.x86_64.1 Wed Nov 20 04:46 - 10:27 (05:41)
reboot system boot 4.4.157.x86_64.1 Wed Nov 20 04:42 - 10:27 (05:45)
reboot system boot 4.4.157.x86_64.1 Wed Nov 20 04:38 - 10:27 (05:49)
reboot system boot 4.4.157.x86_64.1 Wed Nov 20 04:34 - 10:27 (05:52)
reboot system boot 4.4.157.x86_64.1 Wed Nov 20 04:31 - 10:27 (05:56)
reboot system boot 4.4.157.x86_64.1 Wed Nov 20 04:27 - 10:27 (05:59)
reboot system boot 4.4.157.x86_64.1 Wed Nov 20 04:14 - 10:27 (06:13)
reboot system boot 4.4.157.x86_64.1 Wed Nov 20 04:01 - 10:27 (06:25)
reboot system boot 4.4.157.x86_64.1 Wed Nov 20 03:08 - 10:27 (07:19)
reboot system boot 4.4.157.x86_64.1 Tue Nov 19 21:52 - 10:27 (12:35)
reboot system boot 4.4.157.x86_64.1 Sat Nov 16 14:01 - 10:27 (3+20:26)
reboot system boot 4.4.157.x86_64.1 Sat Nov 16 13:57 - 10:27 (3+20:29)
reboot system boot 4.4.157.x86_64.1 Sat Nov 16 13:54 - 10:27 (3+20:32)
reboot system boot 4.4.157.x86_64.1 Sat Nov 16 12:59 - 10:27 (3+21:27)
reboot system boot 4.4.157.x86_64.1 Sat Nov 16 12:56 - 10:27 (3+21:30)
reboot system boot 4.4.157.x86_64.1 Sat Nov 16 12:53 - 10:27 (3+21:34)
reboot system boot 4.4.157.x86_64.1 Sat Nov 16 00:37 - 10:27 (4+09:49)
reboot system boot 4.4.157.x86_64.1 Thu Apr 27 10:00 - 10:27 (573+00:26)
reboot system boot 4.4.157.x86_64.1 Tue Apr 25 05:45 - 10:27 (575+04:41)
reboot system boot 4.4.157.x86_64.1 Thu Aug 11 14:54 - 10:27 (831+19:33)
NETGEAR Academy
Boost your skills with the Netgear Academy - Get trained, certified and stay ahead with the latest Netgear technology!
Join Us!
