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.
anwsmh wrote:
My long posts (with top and mdstat) appear to be rejected or filtered by the posting application.
There is an automatic spam filter that triggered. The mods check the quarantine periodically, but it can take a while. I can also release them, so you can send me a PM if it happens again.
anwsmh wrote:
So, short and sweet: mdstat tells me that the reshape is motoring along at 4kB/sec and will finish in 4 months (120 days roughly).
It'd be very helpful if you told us the manufacturer and model of the disk you inserted.
anwsmh wrote:
The new disk was added in "safe" mode
Why are you using safe mode? Normally you are only in that mode when something is wrong.
The new disc is a Western Digital PC grade WD10EZEX-21M2NA0.
I added it in what I thought was safe mode (but probably isn't. I got it in this mode by booting with only disc 1 inserted) because I have no access to the Web UI and I was foolish enough to think that adding a disc to a raid group was unlikely to cause problems; that working round a problem was unlikely to lead to other problems etc.
No mitigating circs.
anwsmh wrote:
The new disc is a Western Digital PC grade WD10EZEX-21M2NA0.
Ok, that is CMR, not SMR. FWIW, I recommend sticking with CMR NAS-purposed disks (or enterprise class). So I would have gone with either a Seagate Ironwolf (ST1000VN002) or a WDC Red Plus (WD10EFRX).
anwsmh wrote:
I added it in what I thought was safe mode (but probably isn't. I got it in this mode by booting with only disc 1 inserted) because I have no access to the Web UIIf one disk was inserted, the system would have booted up in the normal mode (from disk 1). You wouldn't have been able to access the volume, since you wouldn't have enough disks to mount the RAID array. I'm guessing you then powered down, inserted the other disks, and powered up?
The best way to do have proceeded with the disk replacement was to hot-swap the disk (with the NAS running), or to hot-insert it (if you are adding a disk to an empty bay). What you actually did should have worked (assuming you did power down to reinsert the missing disks), but IMO wasn't that safe.
I am puzzled on how you would have gotten access to the web ui with only one disk installed - though there isn't an clear understanding of what is causing the log-in loop with 6.10.5. It would have been better to overcome the log-in loop before replacing a disk. But of course that is past.
Do you have a backup of the data?
If not, are you getting access to the files from Windows File Explorer? (although it could be slow)?
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.Wow, that the set of drives is heterogeneous is an understatement. You have a lot of RAID groups because of the multiple drive sizes. Yes, the other RAIDs will sync one at a time as each finishes, but I rather think that may never come. And I don't think the variety of drive sizes is a factor here. But that it will take that long just to re-sync the 1TB group is an indication something is very wrong. Normally, the other groups wouldn't need a re-sync since the new drive isn't a part of them. I think that means that booting with just one drive had an effect, and that might be at least a part of the problem.
TOP shows the RAID process is taking 100% of the CPU, but the companion kworker processes don't seem to be doing much. I'm not sure why that is, but it's bad. Unless one of the original drives is SMR, my suspicion is one of the drives is bad. But removing a drive at this point is a really a bad idea, though, even if it is bad.
Since you didn't mention having a similar issue the last time you added or swapped a drive, I doubt one of the others is SMR. But if you know the brands and models (which are in disk_info.log in the log .zip file if you have a saved one), it would be good to check.
Getting Netgear assistance does seem your best bet. If they can slow down the sync even more, then there will be enough of the CPU for SMB or the GUI and backup process to run so you can get files off the NAS. You really need to do that, because the only way I think you'll ever fix the issue is to test all the drives, remove the one that is bad (I think there has to be one), and do a factory default.
BTW, if you use the CODE INSERTION tool (looks like </>) when you post text grabbed from SSH, it will be formatted in a non-proportional font so it's a lot easier to read.
NETGEAR Academy
Boost your skills with the Netgear Academy - Get trained, certified and stay ahead with the latest Netgear technology!
Join Us!
