NETGEAR is aware of a growing number of phone and online scams. To learn how to stay safe click here.
Forum Discussion
Drive replacement rebuild status
Hi, I started a vol expansion on my ReadyNAS Pro Bus, replacing drive 1 with a new 3TB drive (ST33000650NS on the HCL, my 2nd one). I'm on RAIDiator 4.2.27, configured as X-RAID2. The drive tested fine, and the last log entry 24 hours ago says:
But, there's no indication of a rebuild underway. Front panel status says "Vol C Unprotected" and the Status | Health page shows the old drive 1 Id, blinking yellow, and listed as "Dead".
My question is: has the rebuild silently failed somehow or is this normal and should I wait longer than 24 hrs for the rebuild to silently finish? Shouldn't the drive health page show the new drive with status "Resync", and isn't there supposed to be any indication of rebuild progress?
Thanks, Mark
Data volume will be rebuilt with disk 1.
But, there's no indication of a rebuild underway. Front panel status says "Vol C Unprotected" and the Status | Health page shows the old drive 1 Id, blinking yellow, and listed as "Dead".
My question is: has the rebuild silently failed somehow or is this normal and should I wait longer than 24 hrs for the rebuild to silently finish? Shouldn't the drive health page show the new drive with status "Resync", and isn't there supposed to be any indication of rebuild progress?
Thanks, Mark
2 Replies
Replies have been turned off for this discussion
- What other drives are in the nas currently?
What drives were in the nas when it was initially setup and was this the last time the unit was factory defaulted?
Do you have a backup?
If you don't have a backup, then make one now, then reboot the nas, perhaps a few times if the rebuild doesn't start.
If you have a backup you can either try removing the drive and reinserting it after the nas recognises a drive removal ;and/or reboot the nas.
I suspect a reboot is all that is required. - This is the 3rd drive replaced in +5 yrs, but it's been so long since last time, I couldn't remember exactly how resync status was supposed to be reflected. Turns out it just needed to be re-seated. I should have noticed I was missing the very last log message before it really started the resync:
RAID sync started on volume C.
With that, resync appears running fine.
Thanks
NETGEAR Academy
Boost your skills with the Netgear Academy - Get trained, certified and stay ahead with the latest Netgear technology!
Join Us!
