NETGEAR is aware of a growing number of phone and online scams. To learn how to stay safe click here.
Forum Discussion
Solved
OS 6.10.5 CLI management commands (for managing RAID groups)
Are there any CLI commands for managing RAID groups in OS 6 ? I have just apparently serendipitously recovered from the Authentication Loop bug in the management interface (remove disks and boot w...
Thank you for your helpful remarks StephenB.
I am giving some attention to replacing the discs with more suitable models.
In the meantime, since it's manifest that I don't know what I am doing, I have bought Netgear support who will certainly do a better job getting me out this mess than me.
Thank you.
Thank you StephenB.
I expect I am trouble with this (tick all the boxes: no web interface - sadly, it's back in the Authentication loop; and just about zero conceptual knowlege of the ReadyNAS RAID implementation) but since a data reshape is sitting on 2.75% (from front panel) and top shows load averages of 6.01, 6.08, 6.07 with the md127_raid5 process sitting on 100%, I was looking for alternative ways of knowing what's happening etc.
Well, that's what you use the mdadm and btrfs commands for. To see the status of RAIDs, including sync status, use cat /proc/mdstat. Or if you want a continuous update, use watch cat /proc/mdstat. This is not unique to the ReadyNAS. MDADM is a standard part of Linux and BTRFS is a common addition. So just Googling for standard Linux commands will get you started.
Thank you Sandshark.
The cat /proc/mdstat shows that sync is happening but at a rate of 33kB/sec, so it looks like trying to do stuff (in this case, adding a disk) without adequate preparation will earn it's usual reward.
anwsmh wrote:
The cat /proc/mdstat shows that sync is happening but at a rate of 33kB/sec,You could query the smart stats for each disk using smartctl. Also, you can use journalctl to see if there are any errors going on that might be slowing the sync.
FWIW, I always test my new disks in a PC using vendor tools before adding them to the NAS. I run the full non-destructive test, and follow that up with the full erase/write zeros test.
I sometimes have had new drives pass the short smart tests, but fail one of those more extensive tests.
Hi StephenB,
Thank you for your encouragement and assistance (and the sound advice about preparation)
As far as I can tell, smarctl shows a handful of errors (<=9) on one device (not the addition) and nothing on the new disc ("No errors logged"). The device logging 9 errors does so at power on and the errors are related to various disk blocks (I think.Only two LBAs are repeated). All devices report healthy.
I am unfamiliar with journalctl (when I run journalctl --system -o short -r, what is mainly obvious is HTTP errors from frontview)
Yeah, that's incredibility slow. What type drive did you add? If it's one that's SMR, such as the WD EFAX series, then that's the likely problem, and you are in for more. But don't just stop anything at this point, even if that is it. But do use the top command to see if it looks like there are any processes being held or stacked up by the sync.
I have also seen instances where the NAS has turned off drive buffering during re-sync, which results in very slow syncs. It may supposed to only do that if there is no UPS, but I've seen it in other cases. Do you have an UPS attached?
What result do you get from cat /proc/sys/dev/raid/speed_limit_max and cat /proc/sys/dev/raid/speed_limit_min? What about hdparm -W /dev/sdX where you repeat where X is each of the drives in the RAID? If your RAID is across all 6 drives, that is probably either a-f or a-g minus one somewhere in that range that was the one you replaced.
Hi Sandshark,
Firstly, I am very grateful for your comments. Things are getting worse in that mdstat shows the speed has dropped to 13k.
The new drive (added to an existing heterogenous set of 4) is a WDC WD10EZEX-21M2NA0.
top shows
<pre>
PID USER PR NI VIRT RES SHR S %CPU %MEM TIME+ COMMAND
1456 root 20 0 0 0 0 R 100.0 0.0 1279:33 md127_raid5
3189 root 19 -1 2898228 41608 25448 S 1.3 2.0 20:14.24 readynasd
2043 root 20 0 28764 3040 2484 R 0.7 0.1 0:00.30 top
1 root 20 0 204356 7244 5392 S 0.0 0.4 0:06.64 systemd
2 root 20 0 0 0 0 S 0.0 0.0 0:00.04 kthreadd
3 root 20 0 0 0 0 S 0.0 0.0 0:01.09 ksoftirqd/0
5 root 0 -20 0 0 0 S 0.0 0.0 0:00.00 kworker/0:0H
7 root 20 0 0 0 0 S 0.0 0.0 0:39.56 rcu_sched
8 root 20 0 0 0 0 S 0.0 0.0 0:00.00 rcu_bh
9 root rt 0 0 0 0 S 0.0 0.0 0:01.20 migration/0
10 root rt 0 0 0 0 S 0.0 0.0 0:00.41 watchdog/0
11 root rt 0 0 0 0 S 0.0 0.0 0:00.51 watchdog/1
12 root rt 0 0 0 0 S 0.0 0.0 0:01.05 migration/1
13 root 20 0 0 0 0 S 0.0 0.0 0:01.05 ksoftirqd/1
15 root 0 -20 0 0 0 S 0.0 0.0 0:00.00 kworker/1:0H
16 root rt 0 0 0 0 S 0.0 0.0 0:01.21 watchdog/2
17 root rt 0 0 0 0 S 0.0 0.0 0:00.66 migration/2
18 root 20 0 0 0 0 S 0.0 0.0 0:01.17 ksoftirqd/2
20 root 0 -20 0 0 0 S 0.0 0.0 0:00.00 kworker/2:0H
21 root rt 0 0 0 0 S 0.0 0.0 0:00.64 watchdog/3
22 root rt 0 0 0 0 S 0.0 0.0 0:00.90 migration/3
root@nas-E7-02-2C:~# cat /proc/sys/dev/raid/speed_limit_max
200000
root@nas-E7-02-2C:~# cat /proc/sys/dev/raid/speed_limit_min
30000
</pre>
There is no UPS.
hdparm -W on the 5 members of the raid group (a - e) shows write caching on.
NETGEAR Academy
Boost your skills with the Netgear Academy - Get trained, certified and stay ahead with the latest Netgear technology!
Join Us!
