NETGEAR is aware of a growing number of phone and online scams. To learn how to stay safe click here.
Forum Discussion
anwsmh
Jun 11, 2021Aspirant
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...
- Jun 16, 2021
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.
anwsmh
Jun 11, 2021Aspirant
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.
StephenB
Jun 11, 2021Guru - Experienced User
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.
- anwsmhJun 11, 2021Aspirant
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)- StephenBJun 12, 2021Guru - Experienced User
anwsmh wrote:
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.Probably worth following up on later (and maybe use smartctl or the web ui to test the disks). But it doesn't like sound it is related to the sync speed issue.
But I think Sandshark's thought is worth pursuing. WD20EFAX, WD30EFAX, WD40EFAX, and WD60EFAX are SMR drives, and if you are using them you will see highly variable write times and very long sync times. There are some desktop drives (and shucked USB drives) that are also SMR (both Seagate and Western Digital).
- anwsmhJun 13, 2021Aspirant
Thanks for everyone's patience with this thread.
root@nas-E7-02-2C:~# cat /proc/mdstat
Personalities : [raid0] [raid1] [raid10] [raid6] [raid5] [raid4]
md123 : active raid1 sde7[1] sdc7[0]
175683264 blocks super 1.2 [2/2] [UU]
resync=DELAYEDmd1 : active raid10 sde2[4] sdd2[3] sdc2[2] sdb2[1] sda2[0]
1305600 blocks super 1.2 512K chunks 2 near-copies [5/5] [UUUUU]md124 : active raid5 sde6[3] sdd6[2] sdc6[1]
68307072 blocks super 1.2 level 5, 64k chunk, algorithm 2 [3/3] [UUU]
resync=DELAYEDmd125 : active raid5 sde5[4] sdd5[3] sda5[0] sdc5[2]
331833472 blocks super 1.2 level 5, 64k chunk, algorithm 2 [4/4] [UUUU]
resync=DELAYEDmd126 : active raid5 sde4[5] sdd4[4] sda4[0] sdc4[3]
39041280 blocks super 1.2 level 5, 64k chunk, algorithm 2 [4/4] [UUUU]
resync=DELAYEDmd127 : active raid5 sde3[6] sdd3[5] sda3[0] sdc3[4] sdb3[1]
161586624 blocks super 1.2 level 5, 64k chunk, algorithm 2 [5/5] [UUUUU]
[====>................] reshape = 24.7% (13305472/53862208) finish=165179.5min speed=4K/secmd0 : active raid1 sde1[8] sdd1[7] sda1[0](W) sdc1[6](W) sdb1[5]
4190208 blocks super 1.2 [5/5] [UUUUU]unused devices: <none>
root@nas-E7-02-2C:~#
I think this means that the reshape will finish (at 4KB/sec) in about 115 days. Maybe other resyncs will happen after.
The data on this NAS (on discs sda-d) is only personal but I don't want to have to wait 4 months to access it (I have no access to the shares the NAS exports).
The data on the new drive was junk (the drive as added in "safe mode" after only a format. It was not added to a volume group since the "New volume" in frontview was greyed out).
Are there any safe options for getting access to the data on the NAS ? Can I pull sde ?
Related Content
NETGEAR Academy
Boost your skills with the Netgear Academy - Get trained, certified and stay ahead with the latest Netgear technology!
Join Us!