NETGEAR is aware of a growing number of phone and online scams. To learn how to stay safe click here.
Forum Discussion
one disk failed in RAID 5, no data in shared folders, old three disks color changed to RED
Hi,
we have with RAID-5 configured.
one disk failed and it was replaced in poweroff mode.
3 old disks changed to RED color and new disk added is black. Pl. check in image attached.
Updated to latest available OS.
Logs
ue May 9 2017 18:51:21
System: Firmware was upgraded to 6.7.1.
Tue May 9 2017 18:51:21
System: ReadyNASOS background service started.
Tue May 9 2017 18:51:19
Volume: System volume root's usage is 82%. This condition should not occur in normal conditions. Contact technical support.
Tue May 9 2017 18:43:34
System: The system is rebooting.
Tue May 9 2017 18:13:33
System: ReadyNASOS background service started.
Tue May 9 2017 18:13:21
Volume: Less than 20% of volume media's capacity is free. Performance on volume media will degrade if additional capacity is consumed. NETGEAR recommends that you add capacity to avoid performance degradation.
Tue May 9 2017 18:13:19
System: ReadyNASOS service or process was restarted.
Tue May 9 2017 17:45:39
Disk: Disk Model:ST3000DM001-1CH166 Serial:W1F20Z9B was added to Channel 2 of the head unit.
Tue May 9 2017 17:10:00
System: Antivirus scanner definition file was updated to 57.23370.
Tue May 9 2017 17:04:34
Disk: Disk in channel 4 (Internal) changed state from RESYNC to ONLINE.
Tue May 9 2017 17:04:34
Disk: Disk in channel 3 (Internal) changed state from RESYNC to ONLINE.
Tue May 9 2017 17:03:59
System: ReadyNASOS background service started.
Tue May 9 2017 17:03:47
Volume: System volume root's usage is 84%. This condition should not occur in normal conditions. Contact technical support.
Tue May 9 2017 17:03:46
Volume: Less than 20% of volume media's capacity is free. Performance on volume media will degrade if additional capacity is consumed. NETGEAR recommends that you add capacity to avoid performance degradation.
Mon May 8 2017 19:36:52
System: The system is shutting down.
It also indicates data 0, free space 0.
Pl. let me know how to revive this NAS and get all data in place.
Regards
Pavan
10 Replies
Replies have been turned off for this discussion
I am thinking that your full OS volume likely contributed to this problem.
I suggest contacting paid support (my.netgear.com).
Note that if you are the original purchaser (new, not used) and purchased between 1 June 2014 and 31 May 2016, then you have lifetime free chat support. So take advantage of that if you have it.
Have you tried booting with just the three old drives? The proper way to replace a bad drive is with the power on, by the way. If booting with the three orignals works, then add the new one with the power on. If the NAS complains that it has data on it, you will have to re-format it from the Volume page before it will add it to the array. It is always a good idea to make sure your backup is up to date before adding a new drive because the re-sync process is drive intensive and if it causes a second, marginal drive to fail, your volume is lost.
Maybe you want to upvote this "idea": https://community.netgear.com/t5/Idea-Exchange-for-ReadyNAS/Change-the-incredibly-confusing-error-message-quot-remove/idi-p/1271658
Your root volume is fuller than normal.
If you want to have a look at the data volume as well, download the logs from the GUI, look at dmesg.log and search for the mentions of md127.
Yes, It have tried it but status is same.
syslog is of 1.2 gb
logs are not rolling.
Any idea if i perform following steps.
option one:
1. boot with one new drive
2. disable x-raid and powerdown.
3. boot with all four drives.
4. ?? ??
data will be available or not..
option two:
reduce size of syslog and reboot NAS.
clearing some space in / drive will resolve the problem.
Regards
Pavan
Have you just booted with three old disks?
- Playing around with disks is not a good idea. Trial and error (trying different combinations of disks) may further damage the RAID array. That's why it's better to try determine which drive is causing the issue.
jak0lantash wrote:
Playing around with disks is not a good idea. Trial and error (trying different combinations of disks) may further damage the RAID array. That's why it's better to try determine which drive is causing the issue.He already has been playing around with the drives. Looking more closely at the log segment, there is more to this story that has been told. Drives in channels 3 & 4 completed resync within less than a minute of each other? Why/How? Drive was added to channel 2 less than an hour later. No resync is shown as starting. OS was updated a little more than an hour later, which included a reboot, well before the resync could have completed, even if it had started. And it was done with an already too full OS partition.
The OP was playing with fire and got burned. Had the original story been the whole story (Replace one drive and the other three went red), then trying to boot with the original three was a good plan. But with everything that was done, who knows?
NETGEAR Academy
Boost your skills with the Netgear Academy - Get trained, certified and stay ahead with the latest Netgear technology!
Join Us!
