NETGEAR is aware of a growing number of phone and online scams. To learn how to stay safe click here.
Forum Discussion
Nv+ issues?
Hi All, I came home from work and saw that my NV+ was off? No UPS but the power did not go out. Not sure why it was off. I turned it on and the boot cycle has been going on saying "booting..." ...
I asked support about why I did not get a error telling me what drive failed, this was the response below.
-----------
The reason why you didn't get an error with this drive failing is because it was the base drive that failed. The base drive is the drive where the operating system is installed. If your parity drive or any other drive failed you would have got some kind of message related to it on the LCD or RAIDar, and would have still been able to access your data.
There is an email alerts feature in the ReadyNAS that you can have it email you problems with the drives and let you know if there is a possible failure.
If you want to be able to access the NAS like we did you can install the root SSH add-on. This will allow access to the ReadyNAS like what we had.
Thank you again for choosing NETGEAR ReadyNAS. Have a great day!
----------
Well I learn something new every day, I did not know the OS was installed on the drives in the array, I honestly assumed the OS would be installed on some flash memory or something like that inside the NAS.
So I really do not understand, maybe someone can explain to me how if the OS is installed on 1 drive in the array, and that drive fails and causes the whole array to lock up like mine did and not boot back up correctly until you remove that failed drive and then the OS is reinstalled on another drive or something. how is that redundant? I mean I guess you data is kept intact, but seems very flawed to me.
If you have the OS installed on 1 of the drives in the array, and currently I am doing a RAID expansion to all new drives, how does that work when eventually I am going to pull the OS drive out of the array?
Also I did not have the email alerts setup correctly, but not sure if I would have gotten a alert or not since the unit seemed to lockup, and I already have the root SSH addon installed, but not sure if I tried it or not, but seemed like the unit would not boot up enough of the way to even SSH to the it, it was just sitting at "Checking FS" forever.
Maybe someone can answer or just tell me what they think about the way the OS is installed like this?
-----------
The reason why you didn't get an error with this drive failing is because it was the base drive that failed. The base drive is the drive where the operating system is installed. If your parity drive or any other drive failed you would have got some kind of message related to it on the LCD or RAIDar, and would have still been able to access your data.
There is an email alerts feature in the ReadyNAS that you can have it email you problems with the drives and let you know if there is a possible failure.
If you want to be able to access the NAS like we did you can install the root SSH add-on. This will allow access to the ReadyNAS like what we had.
Thank you again for choosing NETGEAR ReadyNAS. Have a great day!
----------
Well I learn something new every day, I did not know the OS was installed on the drives in the array, I honestly assumed the OS would be installed on some flash memory or something like that inside the NAS.
So I really do not understand, maybe someone can explain to me how if the OS is installed on 1 drive in the array, and that drive fails and causes the whole array to lock up like mine did and not boot back up correctly until you remove that failed drive and then the OS is reinstalled on another drive or something. how is that redundant? I mean I guess you data is kept intact, but seems very flawed to me.
If you have the OS installed on 1 of the drives in the array, and currently I am doing a RAID expansion to all new drives, how does that work when eventually I am going to pull the OS drive out of the array?
Also I did not have the email alerts setup correctly, but not sure if I would have gotten a alert or not since the unit seemed to lockup, and I already have the root SSH addon installed, but not sure if I tried it or not, but seemed like the unit would not boot up enough of the way to even SSH to the it, it was just sitting at "Checking FS" forever.
Maybe someone can answer or just tell me what they think about the way the OS is installed like this?
NETGEAR Academy
Boost your skills with the Netgear Academy - Get trained, certified and stay ahead with the latest Netgear technology!
Join Us!
