NETGEAR is aware of a growing number of phone and online scams. To learn how to stay safe click here.
Forum Discussion
Solved
ReadyNAS Duo v1 not completely booting up after replacing failed disk
Background
I have a ReadyNAS Duo V1 with a failing disk. System emails indicated :
Disk 2 did not pass SMART self-assessment test. Please replace this disk as soon as possible.
Growing SMA...
Finally done more detailed tests on the second disk I acquired and find faults. The cause seems to be a faulty disk. I have done a factory reset with the first 2TB disk I purchased and it's working fine, and faster than before, but obviously not in a RAID configuration.
Clearly I was too patien. My investment in testing tools will be put to good use whenever I buy new hard drives.
Many thanks to all contributors.
Thanks for the quick response.
No reason for using beta, I thought I was on latest when I kicked this process off, but clearly not. Unless this situation does not resolve itself I shall wait until the sync completes before updating. If you have knowledge there was a related bug in the beta release, corrected for the final release, I shall reconsider.
I do not have a backup. I accept it is a terrible lapse and I am in the process of correcting (such as acquiring a back up device) but since I know I can access my data if this fails, I consider the risk of data loss low.
I am unable to log onto the admin account using https://ip.address.of.nas/admin. I've used several devices to attempt to log in. The device has not been moved nor the network reconfigured since I was last able to log on.
4.1.15 is no longer beta, it was recently released as production.
Thanks for the response. I assumed from mdgm's post that was the case.
In the context of not wanting to interrupt the current sync process, because it's been going since 2nd August and I am relying on patience to resolve it, I would prefer to do the latest firmware upgrade after the sync completes.
However, if someone has information that either 4.1.14 or 4.1.15 production release specifically addressed long sync times, I shall reconsider the timing of the upgrade.
The reason I mentioned it is that betas are betas. They may inherently possibly have issues that one wouldn't see in a production release as betas haven't gone through the complete QA process. I was speaking generally rather than referring to an issue with the beta build you are running.
We don't recommend sticking on beta firmware after betas are over.
Fully agree, I would not normally stay on a beta and truly thought I was on the latest version.
Is there any record of sync taking an inordinate amount of time, regardless of the firmware release? I found one post on the subject, any knowledge you have access to that I do not?
I may give it a few more days and then interrupt. I will then backup, upgrade firmware, try again and if no success, factory reset.
bryn_hird wrote:
...if someone has information that either 4.1.14 or 4.1.15 production release specifically addressed long sync times...
I don't think so (and I'm thinking that is quite unlikely given the v1 already is using hardware acceleration).
Certainly the release notes don't mention it:
http://kb.netgear.com/app/answers/detail/a_id/25786/~/raidiator-version-4.1.14-(sparc)
http://kb.netgear.com/app/answers/detail/a_id/30914/~/raidiator-version-4.1.15-(sparc)
Many thanks for providing those links.
NETGEAR Academy
Boost your skills with the Netgear Academy - Get trained, certified and stay ahead with the latest Netgear technology!
Join Us!
