NETGEAR is aware of a growing number of phone and online scams. To learn how to stay safe click here.
Forum Discussion
Solved
RN314 problems after Readynas 6.10.7
After install of 6.10.7 (apparently trouble free) on a RN314 (4*6TD WD drves) that has been in use for years, the gui degrades to the point where no data appears in the admin page.
In the short time after boot where admin page can be read, it shows that we are in resync at about 34.xx% complete. Using ssh and cat /proc/mdstat it shows 5.9% complete and verrrry slowly increments over the past few days. Converting the minutes left to days shows more that a month to complete the resync!
The log, when available, shows increasing disk errors on one of the four drives.
Can I replace the faulty drive with a new one, or must I wait for the resync to complete?
If I can replace the drive, is the proper procedure to hot swap the drive, or should I shutdown, replace the drive and power up?
Given the lack of normal behaviour of the admin gui, I am cautious about attempting to either:
- upgrade to 6.10.8
- downgrade to 6.10.6
- reinstall 6.10.7
top shows no stopped or zombie processes, cpu time is approx 50% idle and 50% wait. No swap usage. The only significant accumulation goes to md126_raid5
I'd appreciate advice from anyone more knowledgeable than me as to what steps to take.
Thanks in advance.
Alf
alfb wrote:
So should I hot swap sdb (drive 2 as 1,2,3,4) or is it sbd (drive 2 as in 0,1,2,3) The output from mdstat infers drive numbers are 0,1,2,3
And are these numbers from left to right as looking from the front??
One caution is that the error in the screen shot is a read error - normally if mdadm is rebuilding a disk, it is writing to it. So there still is some uncertainty on exactly what is going on.
sdb is normally the second disk from the left (the disk in the first slot normally is sda).
If you aren't certain, you can also get the serial number with smartctl -x /dev/sdb (along with a lot of other information). Then you could power down the NAS, check the disk serial, and boot up the NAS read-only without it. If the volume is there, but degraded, then you could reboot again normally. Then do a hot-insert of the replacement.
Instructions on booting the NAS read-only are on pages 74-75 here:
17 Replies
Replies have been turned off for this discussion
alfb wrote:
Can I replace the faulty drive with a new one, or must I wait for the resync to complete?
If the drive that is resyncing is the faulty one, then you don't need to wait.
But if it is a different drive, then you do.
alfb wrote:
If I can replace the drive, is the proper procedure to hot swap the drive, or should I shutdown, replace the drive and power up?
I generally recommend a hot swap. The system then detects the removal and reinsertion, and doesn't need to figure out that a drive was replaced.
alfb wrote:
Given the lack of normal behaviour of the admin gui, I am cautious about attempting to either:
- upgrade to 6.10.8
- downgrade to 6.10.6
- reinstall 6.10.7
The failing disk could be the cause of the poor performance. I wouldn't do any of these things at present.
StephenB,
Thanks for your advice.
Re
If the drive that is resyncing is the faulty one, then you don't need to wait.
But if it is a different drive, then you do.
I am not sure which drive is resyncing. I will try to copy the output of /proc/mdstat to show you what I know. It shows md126 with the activity, but no indication that I can see of drive 1 or 2 or 3 or 4
Perhaps there is a different cli command?
Regards, Alf
NETGEAR Academy
Boost your skills with the Netgear Academy - Get trained, certified and stay ahead with the latest Netgear technology!
Join Us!
