NETGEAR is aware of a growing number of phone and online scams. To learn how to stay safe click here.
Forum Discussion
Need help with XRaid2 problem on ReadyNAS Pro running RAIDiator 4.2.31
It is of course my own fault for not having a backup but the following happened. I had a 6 bay ReadyNAS pro as above running RAIDiator 4.2.31 with six 4TB drives. Whilst the logs showed an increa...
jelockwood1 wrote:
I had a 6 bay ReadyNAS pro as above running RAIDiator 4.2.31 with six 4TB drives. Whilst the logs showed an increasing number of ATA errors the system was at that point working. Due to the increasing number of errors I decided to kill two birds with one stone and replace all the drives with 6TB drives by swapping one at a time and allowing re-syncing to occur. I had successfully swapped five of the drives and was doing the final drive and re-syncing again when the fifth drive completely died whilst it was syncing the sixth. This meant effectively two bad drives at the same time.
One complication is that 4.2.x systems can't be expanded over 16 TiB.
6x4TB RAID-5 would normally give you a 20 TB volume. If you created the volume by installing all 6 disks at once, I believe you'd get the full 20 TB size (since the all the disks are of equal size, so the volume doesn't actually expand). But the expansion to 6x6TB (30 TB volume) should have failed.
The usual mount procedure in tech support mode is
vgscan
vgchange -a y
mount /dev/c/c /cThough it might be safer to do the mount read-only
mount -o ro /dev/c/c /cSo you could reboot into tech support mode and try that.
If you can figure out what 4 TB disk was in slot 6, you could also try assembling with the four 6TB drives and the original drive 6.
The other pathway is to use RAID recovery software in a Windows PC. You'd need an enclosure (~$200 USD). R-Studio is one option for recovery software ( https://www.r-studio.com/ )
I am at this stage far less concerned with storage expansion and may indeed look at v6 later for that.
Steve, as I indicated vgscan is not finding a volume i.e. c and hence it is not possible to do vgchange or mounting. Also (not mentioned) likely for the same reason there is no /dev/c/c/ device
You might have been confused by my referring to the fact I have a second identical but working unit and it does list the c volume and have a /dev/c/c/
jelockwood1 wrote:
I am at this stage far less concerned with storage expansion
Understood. I raised the expansion issue in the first post, because the failed expansion might complicate recovery efforts.
You might have better luck with the 4 larger disks + the original disk 6. The volume would be out of sync no matter what you do, so that it is part of the puzzle.
Though honestly I think your best option is recovery software.
NETGEAR Academy
Boost your skills with the Netgear Academy - Get trained, certified and stay ahead with the latest Netgear technology!
Join Us!
