NETGEAR is aware of a growing number of phone and online scams. To learn how to stay safe click here.
Forum Discussion
Numb3r6
Feb 28, 2019Apprentice
ReadyNAS Duo v1 odd behaviour
After the events last week, I thought stability had returned but it seems not....
Last week involved a failing>failed disk. I replaced it with new like for like, resync completed and all was normal...
StephenB
Mar 01, 2019Guru - Experienced User
The rapidly rising lp stat counts could indicate that the Duo is having some issues with the first disk. "lp stat" is monitored by the Duo itself - it's not a SMART stat, and I've never seen a clear explanation of what it is.
It would be wise to update your backup.
Clearly you are seeing a formatting bug on the resync page (looks like RAIDar?). As far as the times go, the estimates are often way off, especially on the older legacy NAS.
Numb3r6
Mar 01, 2019Apprentice
Thanks for your reply StephenB. It's now down to just over 11 hours pending. If it gets to the end of this sync without a total failure, I'll reboot, check logs and content accessibility - and if all is well, replace Disk1 also (which I know will kick off another resync, but that didn't take too long last week) I hope it doesn't get to the end of this resync and then immediately kick off again, as that seems to be what happened early this morning. Weird thing is that since I replaced Disk2 last week, it's been running perfectly normally, not a hint of more troubles until last night.
That info from NAS Utils (RAID Status) which currently shows "Resync 55%complete, Time to finish etc" interests me. I am wondering if the 55 (which seems to be incrementing) relates to Disk1 and 37 (static) relates to Disk2 perhaps, and if that is some indication of Disk1 being problematic. I'm perhaps clutching at straws given the lack of other clues.
What I don't get is that all other aspects of health that I can see suggest all is good. The only clue is the Lp stat count. As you can see from my pics, everything else shows as green. I'd almost be happier if Disk1 showed a yellow on Frontview, which would at least reinforce something not being right.
Based on another thread here, the suggestion is that Lp stat increase means I/O requests are taking longer than expected. I guess that would stack up if there was a clear fault developing, but as I said all the other indicators such as reallocation, uncorrectables and ATA errors show nothing bad in the SMART summary.
Out of interest do you know of any specific log area I could check to see if there is something fundamentally amiss with the NAS itself that could cause this? Paranoia is setting in here. I can understand the possibility of Disk1 following in the footsteps of Disk2 as they were the same age, and perhaps the recent hammering has pushed it to the edge, I don't know.
- StephenBMar 01, 2019Guru - Experienced User
Numb3r6 wrote:
That info from NAS Utils (RAID Status) which currently shows "Resync 55%complete, Time to finish etc" interests me. I am wondering if the 55 (which seems to be incrementing) relates to Disk1 and 37 (static) relates to Disk2 perhaps, and if that is some indication of Disk1 being problematic. I'm perhaps clutching at straws given the lack of other clues.
No. % is the html code for %. So it's a minor formatting bug, meaning to say "Resync 55% complete"
Numb3r6 wrote:
Out of interest do you know of any specific log area I could check to see if there is something fundamentally amiss with the NAS itself that could cause this?
Maybe look in system.log and kernel.log for disk errors.
Overall, it is an old NAS. You should plan on replacing it at some point, perhaps with an RN212 or an RN422. Then repurpose the Duo as a backup NAS.
- Numb3r6Mar 02, 2019Apprentice
Thanks StephenB, the resync finally finished yesterday evening. I recall from ages ago that time estimates can be wildly out, as you said earlier. I'm now assuming that the sync that started just after 2200 on Thursday, which informed of expected completion by about 0800 Friday, was just not accurate, and the resync actually finished last night. Still no idea what prompted it as I can find nothing untoward in the SMART info or logs at all, bar what looks like a minor glitch with timeserver sync.
I may well have a look at the chassis models you suggest. Would I be right in assuming if I bought diskless I could start off just by inserting a current healthy drive from my Duo, make sure that is ok, then add a second new drive to sync up - or do the newer chassis have a different architecture requiring blank drives and data population by loading up from another source perhaps? Right now there's no pressing need to go beyond 2TB and I don't want to incur too much in the way of extra cost just now.- StephenBMar 02, 2019Guru - Experienced User
Numb3r6 wrote:
I may well have a look at the chassis models you suggest. Would I be right in assuming if I bought diskless I could start off just by inserting a current healthy drive from my Duo, make sure that is ok, then add a second new drive to sync up - or do the newer chassis have a different architecture requiring blank drives and data population by loading up from another source perhaps?The disks do need to be reformatted in the new system.
It is possible to remove one disk from the duo, and do a factory install in the new NAS. You'd create the users, shares, etc. Then copy the data from the duo using rsync backup jobs. If you use the private "home" folders it's easiest to copy them from a PC using drag and drop. After that you can remove the second disk and rebuild the array.
But there is risk here, since the duo's array will be degraded when you remove the first disk. So you really should make a backup anyway.
Personally I'd get new disks for the new NAS, and set up the duo as a backup.
Related Content
NETGEAR Academy
Boost your skills with the Netgear Academy - Get trained, certified and stay ahead with the latest Netgear technology!
Join Us!