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 boot fail into "Volume scan found and corrected errors"
This is a ReadyNAS Duo v1
-Bootup via Power Timer, as usual, no errors reported or emailed to me
-First use of NAS was to stream music to a mobile device. Done it many times, no issues. This time though the streamer was clearly struggling finally reporting it could not connect to device (i.e. the NAS)
-Visually checking it the blue LED was flashing at a steady rate but the unit was not finishing boot.
-No errors previously noted
-Held the power button down to force shutdown, which it did, and I removed power briefly
-Restarted, same
-Repeated this and eventually the blue LED went steady, but system still inaccessible
-Looking at the green LEDs, the top one (disk activity) was flashing rapidly and the 2 beneath it (disk 1 and 2) were steady.
-The IP address was then visible on the network, but could not connect to Frontview via a browser
-Left it a while longer and could access content via network, as well as using Frontview
-Checking Frontview logs etc, there's nothing worrying about disk health
-Only clue is in logs, just saying "Volume scan found and corrected errors"
Now I can access the file system I'm doing a (slightly overdue) backup to a standalone disk. It'll take a while....
With that in mind, I am puzzled as to what has happened. I'm pretty sure the timing coincided with my use of Stratospherix MusicStreamer.
So are there any known triggers that could provoke the symptoms I experienced, or is there anywhere else I can look at within the NAS for more detailed error info?
Storage is at 76% BTW
RAIDar shows no issues
thanks
Dave
I wouldn't be concerned about lp stat events.
A volume scan is a reasonable idea, though I'd suggest making a backup (or updating it if needed) first.
17 Replies
Did you check system.log and kernel.log for details on what the volume scan fixed? Also, did you look for any disk errors in those logs?
Thanks for reply StephenB. OK I'd been looking in the file system rather than using the Frontview option to download them. I hadn't realised that option would reveal more detail than is shown in the Frontview summary. That said I don't know what I would be looking for that relates to the event that took place. System has not been rebooted since yesterday, as I am offloading content to another drive. Mind you it has shown no signs of misbehaviour nor anything bad in the Frontview health summary since.
Whilst my system is far from new, I have replaced disks for higher capacity in its life, and regularly give it a blowthrough to shift dust. Mind you heat has never been an issue, and the only times I've had problems before (maybe twice, before I got a UPS) was unplanned power interruption which it recovered from anyway, with no signs afterwards.
It's hard to say if the file system corruption led to the streaming problem, or if the forced shutdown did.
The forced shutdown would trigger a volume scan on startup, and possibly a RAID resync. There could have been some lost (cached) writes, which would account for some filesystem corruption.
Generally - look in system.log and kernel.log for any evidence of system crashes or disk-related errors between the time you had the streaming problem and the time the system was fully recovered.
Also look in disk_usage.log at the fullness of the 2 GB OS partition (/dev/hdc1 if you are running XRAID). Normally the OS partition on the Suo is about 25% full.
disk_smart.log is a good place to look for information on disk health - you can also see the SMART+ stats in frontview (though they will come up blank if you use Chome).
NETGEAR Academy
Boost your skills with the Netgear Academy - Get trained, certified and stay ahead with the latest Netgear technology!
Join Us!
