NETGEAR is aware of a growing number of phone and online scams. To learn how to stay safe click here.
Forum Discussion
MInDev
Mar 21, 2013Aspirant
ReadyNAS NV+ (v1) stuck on "Quota chk" [SOLVED]
Hello
I created another thread on the forum recently which is relevant to this issue (viewtopic.php?f=31&t=69834). Briefly, my ReadyNAS stopped responding suddenly a few weeks ago (Windows reported that mapped drives were unavailable, RAIDar couldn't see the device, and I couldn't connect to Frontview), so I held the power button down for 5 seconds, and after a delay it turned off.
When I turned it back on again, it went through a "Quota chk" which completed successfully, and it started up without problems. I was advised by Frontview, however, that the "ATA error count" on one (disk 1) of the two disks (both Seagate Barracuda LP ST31000520AS) in the unit (in X-RAID configuration) had increased.
I bought a replacement disk (a Western Digital WD10EFRX "Red NAS Hard Drive") in anticipation of replacing this drive, but put off swapping it for the failing unit immediately... I was going to wait until my ReadyNAS had finished it's next scheduled Full Backup - which I've set to run every 4 weeks, with incremental backups (to an external 1 GB USB hard disk) every evening.
Last night the same thing happened. The ReadyNAS vanished from the network. I held the power button down again and switched it off for the night. Today when I turned it back on, it started the "Quota chk" again, and it's been stuck at 33.9% for about 2 hours. I'm assuming the bad disk is responsible for the hold up, but perhaps I'm not being patient enough. The blue LED behind the power button pulses for about 5 seconds, then stops, then the ACT LED blinks once, and then the blue LED begins pulsing again. The two hard disk LEDs are green and unchanging.
So I'm seeking advice about how best to handle this. Should I (assuming it will work) hold the power button down again and turn the device off, then take out disk 1, insert the new disk, and switch it back on? Alternatively, should I power off the device, take out disk 1, turn it back on and let it boot (in "degraded" mode I believe?) and then hot-swap the new drive into the chassis?
Or something entirely different? Thank you very much in advance
I created another thread on the forum recently which is relevant to this issue (viewtopic.php?f=31&t=69834). Briefly, my ReadyNAS stopped responding suddenly a few weeks ago (Windows reported that mapped drives were unavailable, RAIDar couldn't see the device, and I couldn't connect to Frontview), so I held the power button down for 5 seconds, and after a delay it turned off.
When I turned it back on again, it went through a "Quota chk" which completed successfully, and it started up without problems. I was advised by Frontview, however, that the "ATA error count" on one (disk 1) of the two disks (both Seagate Barracuda LP ST31000520AS) in the unit (in X-RAID configuration) had increased.
I bought a replacement disk (a Western Digital WD10EFRX "Red NAS Hard Drive") in anticipation of replacing this drive, but put off swapping it for the failing unit immediately... I was going to wait until my ReadyNAS had finished it's next scheduled Full Backup - which I've set to run every 4 weeks, with incremental backups (to an external 1 GB USB hard disk) every evening.
Last night the same thing happened. The ReadyNAS vanished from the network. I held the power button down again and switched it off for the night. Today when I turned it back on, it started the "Quota chk" again, and it's been stuck at 33.9% for about 2 hours. I'm assuming the bad disk is responsible for the hold up, but perhaps I'm not being patient enough. The blue LED behind the power button pulses for about 5 seconds, then stops, then the ACT LED blinks once, and then the blue LED begins pulsing again. The two hard disk LEDs are green and unchanging.
So I'm seeking advice about how best to handle this. Should I (assuming it will work) hold the power button down again and turn the device off, then take out disk 1, insert the new disk, and switch it back on? Alternatively, should I power off the device, take out disk 1, turn it back on and let it boot (in "degraded" mode I believe?) and then hot-swap the new drive into the chassis?
Or something entirely different? Thank you very much in advance
1 Reply
Replies have been turned off for this discussion
- MInDevAspirantJust to conclude this. I went with "option 2". I waited 24 hours in case things improved - they hadn't when I returned to the ReadyNAS this afternoon, it was still showing "Quota chk: 33.9%".
So I held the power button down for 5 seconds, and shortly afterwards it switched itself off (the front panel remained illuminated with the "Quota chk" message however). I then turned off my UPS (which dimmed the front LCD panel), and unplugged everything from the device - power cable, Ethernet cable, USB external hard disk cable, and USB cable from the UPS.
I removed Drive 1 from the unit (had the stuck drive cage problem again), and took the opportunity to wipe the whole thing (ReadyNAS) down with some kitchen towel to remove dust - I blew a lot of accumulated dust out of it too.
Then I re-attached all of the cables, switched my UPS back on, and pressed the power button (the ReadyNAS now only containing Drive 2). Nothing happened. I panicked a bit at this point, and contemplated how blowing dust out of the box could have killed the power supply, but after about 10 minutes it suddenly spring in to life all on its own. Perhaps it was waiting for a specific signal from the UPS?
It ran the "Quota chk" again, but this time completed fairly quickly, and started up successfully. I had several message in the Frontview logs about what had happened - the ATA error count on Drive 1 had doubled again just before the failed Quota chk began - and about the now missing Drive 1.
Then I inserted my new replacement hard disk into the ReadyNAS (with the ReadyNAS turned on) in bay 1, and it was immediately identified. I had "resync started on Disk 1" messages in Frontview, and after about 6 hours (during which time the lights flickered several times, it was a nervous wait), I was told "RAID sync finished on volume C. The volume is now fully redundant.".
So, it's all ended fairly well.
Related Content
NETGEAR Academy
Boost your skills with the Netgear Academy - Get trained, certified and stay ahead with the latest Netgear technology!
Join Us!