NETGEAR is aware of a growing number of phone and online scams. To learn how to stay safe click here.
Forum Discussion
ReadyNAS NV+ stall during File System check at 19%
My ReadyNAS NV+ is stalling during the File System check at 19%. It is visible in RAIDar, and all four disks register as healthy, until the 19% point is reached, at which point RAIDar cannot find t...
arefem wrote:
My ReadyNAS NV+ is stalling during the File System check at 19%.
Have you tried skipping the check with the boot menu?
If your NV+ says "ReadyNAS NV+" on the front panel, then the instructions are on pages 23-24 here:
If it says "ReadyNAS NV+ v2" on the front panel, then the instructions are on pages 24-25 here:
Hi Stephen,
Thanks for the quick response. It is an NV+. I hadn't tried skipping the check with the boot menu. In fact I didn't know you could do that. That was a definite step forward. RAIDar now runs fully, and my PC sees the NAS and I can access the files. I can see that the firmware version is 4.1.16. I am not sure what I should do next to restore the NAS to its previous condition. My instinct is to connect one of the backup disks to see if the scheduled backup runs. The NAS has four 1TB disks. However, presumably one or more of the NAS disks has some kind of issue which needs to be resolved. I don't know if it is relevant, but during the boot process a message came up on the screen saying that 'Disk 2 was syncing'. None of the other disks were mentioned.
A secondary issue I have is that when I click on the Setup button I get a security message from the browser that it does not support TLS 1.2 protocol. I have tried with several browsers, but none allow Setup to load, so I am not sure how to get round that.
Cheers
Rennie
arefem wrote:
I hadn't tried skipping the check with the boot menu. In fact I didn't know you could do that. That was a definite step forward. RAIDar now runs fully, and my PC sees the NAS and I can access the files. I can see that the firmware version is 4.1.16
Great. BTW, 4.1.16 is the most recent (and final) firmware for your NAS.
arefem wrote:
I don't know if it is relevant, but during the boot process a message came up on the screen saying that 'Disk 2 was syncing'.
It is relevant - resyncing means the disk contents were reconstructed (using RAID parity) from the other disks. This will happen when you replace a disk, but there are also situations where the array gets out of sync. In this case, some writes to disk 2 probably never completed - perhaps due to a system crash or power loss. Whatever the cause, the system detected it, and automatically rebuilt it.
There could still be some file system issues (caused by whatever triggered the resync), so there could still be some lost or corrupted files. If the resync has completed, you could try restarting the NAS normally and see if that completes. But I do suggest getting an up-to-date backup first.
arefem wrote:
My instinct is to connect one of the backup disks to see if the scheduled backup runs.
That makes sense, and in parallel you can work to get back access to frontview.
arefem wrote:
A secondary issue I have is that when I click on the Setup button I get a security message from the browser that it does not support TLS 1.2 protocol. I have tried with several browsers, but none allow Setup to load, so I am not sure how to get round that.
To clarify, the issue is that the NAS doesn't support TLS 1.2 - most browsers deprecated TLS 1.0 a few months back.
If you use a version of Windows that still has Internet Explorer installed, you can still connect with that - manually browsing to https://nas-ip-address/admin (substituting the real IP address of course). Edge in IE mode should also connect ( https://pureinfotech.com/enable-ie-mode-microsoft-edge-chromium/ has a useful guide).
Another option (useful for either Macs or Windows PCs) is to download an older version of FireFox (version 94.0.2 will work). Make sure you don't let the browser update during the install, and right after the install completes, disable auto-update. If you are comfortable with ssh, there is a configuration file in the NAS that you can change to let you reach frontview with ordinary (unencrypted) HTTP. Or you can make sure you keep the older browser around, and only use it to access the NAS.
More information on this is here:
Hi Stephen,
I've left a backup disk plugged in to hopefully run a scheduled backup overnight. I'm not too optimistic, because for some reason, after being connected for a time the NAS seems to become unreachable.
I've installed FireFox version 94.0.2 ready to try with Frontview tomorrow or at the weekend. I've no experience of SSH, but I have a brother who works in IT support, so I'm hoping he can help (unfortunately he is on holiday until the week after next).
Cheers,
Rennie
Hi,
I have not been able to spend time on this in the last few weeks, but I'm able to pick it up again now. The latest position is that it now does not get past the disk 2 sync on bootup. I was unable to run a backup, so unless there is something else worth trying, I am thinking that the only option left is to try replacing disc 2 and see if it rebuilds. If that is the best way to proceed, should I do the swap with the NAS powered off?
I was briefly able to access Frontview, and I can't remember the exact wording, but it indicated that disk 3 was beginning to exhibit errors so should be replaced soon. So I am assuming that the best case scenario is that I have to replace two disks, but there is also a risk that disk 3 has now failed, and all I can do then is a clean build.Cheers
Rennie
NETGEAR Academy
Boost your skills with the Netgear Academy - Get trained, certified and stay ahead with the latest Netgear technology!
Join Us!
