NETGEAR is aware of a growing number of phone and online scams. To learn how to stay safe click here.
Forum Discussion
Easiest RAID configuration to recover data if ReadyNAS fails
Hello, I have a ReadyNAS 104 and am not able to buy another quickly if mine fails someday (the NAS, not the drives), because I live in Brazil and hardware of this type here is prohibitely expensive...
Yes, I know it still is at level 2. I think it doesn't need to go over to level 3. In fact I almost closed it, as the responses here on the forum were already sufficient to know what to do. The only thing that remained was some help with the error causes.
I did not know beforehand that what the web interface showed as a "rebuild" could be in fact more than one operation (and/or different ones). If I may, I would suggest that you either simplify the user interface feedback, telling that the "rebuild" process is complete only when there are no more operations left, or the exact opposite, that it shows which operation is running. That would avoid confusion. Independently, major operations like these should appear on the web interface logs. I know interfaces need constant improvement and this is not a complaint, only feedback.
Here is the entry (from status.log) for when I attached the last hdd. The nas hanged just after:
[14/10/19 23:02:40 ART] notice:disk:LOGMSG_ADD_DISK Disk Model:ST3000DM001-1CH166 Serial:Z1F2VRCC has been added to Channel '1' of the head unit.
And here is the entry for when I finally rebooted it and the rebuild process got to continue:
[14/10/23 11:50:51 ART] info:system:LOGMSG_READYNASD_ABORTED_NOINFO ReadyNASOS service or process was restarted.
The times are GMT -03:00 (ART). I live in Brazil, Rio, and we're currently in daylight savings time which would be GMT -02:00 but that's not being taken into account. That's another feedback, it would be good if the device had more time options and could recognize automatically or at least have an option to set daylight savings.
About the previous case, yes the password was wrong because I did a factory reset while troubleshooting and forgot to change it. However I promptly changed it back and that's when I've been put on hold for a long time. I was having to leave my pc on for days waiting for access, without responses. Even before the password thing this happened. But that's not what I complained about here, it was about the carelessness of the representatives that didn't even read the case. That's way more basic.
All in all, I'm glad the forum exists and that I have a channel (the amazon email thing was never answered) and someone (you) to which I can pass on constructive feedback. Unfortunately, I had to pass on some rant too, but I think we're on the right track.
I did not know beforehand that what the web interface showed as a "rebuild" could be in fact more than one operation (and/or different ones). If I may, I would suggest that you either simplify the user interface feedback, telling that the "rebuild" process is complete only when there are no more operations left, or the exact opposite, that it shows which operation is running. That would avoid confusion. Independently, major operations like these should appear on the web interface logs. I know interfaces need constant improvement and this is not a complaint, only feedback.
Here is the entry (from status.log) for when I attached the last hdd. The nas hanged just after:
[14/10/19 23:02:40 ART] notice:disk:LOGMSG_ADD_DISK Disk Model:ST3000DM001-1CH166 Serial:Z1F2VRCC has been added to Channel '1' of the head unit.
And here is the entry for when I finally rebooted it and the rebuild process got to continue:
[14/10/23 11:50:51 ART] info:system:LOGMSG_READYNASD_ABORTED_NOINFO ReadyNASOS service or process was restarted.
The times are GMT -03:00 (ART). I live in Brazil, Rio, and we're currently in daylight savings time which would be GMT -02:00 but that's not being taken into account. That's another feedback, it would be good if the device had more time options and could recognize automatically or at least have an option to set daylight savings.
About the previous case, yes the password was wrong because I did a factory reset while troubleshooting and forgot to change it. However I promptly changed it back and that's when I've been put on hold for a long time. I was having to leave my pc on for days waiting for access, without responses. Even before the password thing this happened. But that's not what I complained about here, it was about the carelessness of the representatives that didn't even read the case. That's way more basic.
All in all, I'm glad the forum exists and that I have a channel (the amazon email thing was never answered) and someone (you) to which I can pass on constructive feedback. Unfortunately, I had to pass on some rant too, but I think we're on the right track.
NETGEAR Academy
Boost your skills with the Netgear Academy - Get trained, certified and stay ahead with the latest Netgear technology!
Join Us!
