NETGEAR is aware of a growing number of phone and online scams. To learn how to stay safe click here.
Forum Discussion
Replacing failed disk in RN426
One day I rebooted my RN426, and one of my disks (disk4, Seagate 3TB) was not longer recognized, so the volume was marked as degraded. Rebooted again, and it came up, volume resynced, everything OK. ...
Interesting. I see now this array was moved across from an ARM box.
Not sure if some of the weirdness you saw with Resiliio Sync may be related to that. Did you uninstall all apps before moving your disks across to the RN426?
The disk dropping typically on restarts but not on shutdown-reboots is interesting. Though as you say 3 attempts is a small sample size.
If I recall correctly I had to wipe all the apps after moving the array across, since the old apps were ARM so they didn't work on this machine. I didn't notice much weirdness other than that, but you could be right that the continuing strange issues around app installs an uninstalls could be related.
One thing is that lsblk doesn't turn up the new disk either. And it doesn't matter which slot I put it in (4, 5, or 6). I guess I could pull all the disks and plop it in slot 1 to see if the machine sees it at all, but that's getting pretty invasive. Also not completely sure lsblk should be able to see unformatted and unmounted disks. Internally, is the machine partitioned into bays 1,2,3 and bays 4,5,6? Might explain it if 1 of the two controllers went bad, or a loose connector, or something like that. However, the disks do power on, so they're not totally disconnected.
Regarding reboots vs. shutdowns, it's definitely true that in a cold start the disks have spun up long before the OS even thinks about loading, but in a reboot it seems to be much faster. Perhaps something about the vibration of spin up causing one of the disks to bail, was always my theory anyway. I would assume that's a red herring, but since it's the same disk, I'm not so sure. Maybe points to loose connector somewhere internally, if it's the case that bays 4,5,6 are isolated from bays 1,2,3 it could make sense.
Have you checked the old SeaGate disk using SeaTools and the new WD disk using WD Data LifeGuard Diagnostics.
I believe we use a couple of controllers on our 6 bay units, but not sure how many drive bays would be on each. If the disks are fine then hardware failure or a loose connector or something like that would be a possibility.
Don't open the NAS case up. We don't support doing that. If you suspect a hardware problem it would be best to open a support case. First you should check the disks are healthy.
I had a similar problem with getting my Pro-6 to recognize a replacement disk a few years ago. It turns out that the linux disk driver had disabled the port when the original disk failed - likely a consequence of the way it failed. Powering down and then restarting worked in that case.
Did you try powering down the RN426 (perhaps removing the power cable for a couple minutes), and then restarting? That might kick-start the system into recognizing the disk. The theory on removing the power cable is that removing all power will clear out any live bios state.
NETGEAR Academy
Boost your skills with the Netgear Academy - Get trained, certified and stay ahead with the latest Netgear technology!
Join Us!
