NETGEAR is aware of a growing number of phone and online scams. To learn how to stay safe click here.
Forum Discussion
guy1074
Aug 13, 2016Aspirant
X-RAID (RAID 5) Recovery Problems - ReadyNAS NV+ (RND4210) #27270843
My ReadyNAS had 3x 2TB HDD's and was working fine. It was configured for X-RAID and my understanding is that with 3 hard drives it behaves as a RAID 5 configuration where any one of the three drives...
- Aug 14, 2016
Disk 2 (your SeaGate disk) is the dedicated parity disk.
However it looks like this problem may be simpler than I thought.Your OS partition is 100% full (this is probably why it was still stuck on booting even after replacing the failed disk)
# df -h
Filesystem Size Used Avail Use% Mounted on
/dev/hdc1 1.9G 2.0G 560k 100% /
# du -csh /var/log/frontview/error.log
1.4G /var/log/frontview/error.log
That log was last updated back in June and contains errors related to the http/s service. It's typically not a very important log so I just emptied it.
StephenB
Aug 13, 2016Guru - Experienced User
guy1074 wrote:
I'm not familiar with RAID 4 - if that is what my unit is using, what are my options from here?
RAID-4 has the same concept of RAID-5 (xor parity blocks), but the parity blocks are all placed on one disk instead of spread out over all of them. In the case of your NV+, the parity blocks are on an area of the disk that looks unformatted to standard linux tools.
Your options are
(a) pay a reputable data recovery service. Netgear offers one, Seagate does also. Western Digital doesn't (last I checked) but they do recommend some partners who do.
(b) attempt to recover the data yourself. There are some paid tools you could try - generally they are free downloads, so you can see what they might recover before you purchase.
If this is a science project/learning experience then you could go for (b). If the data is important, and you want to maximize your chance of success then go for (a).
mdgm-ntgr
Aug 14, 2016NETGEAR Employee Retired
Disk 2 (your SeaGate disk) is the dedicated parity disk.
However it looks like this problem may be simpler than I thought.
Your OS partition is 100% full (this is probably why it was still stuck on booting even after replacing the failed disk)
# df -h
Filesystem Size Used Avail Use% Mounted on
/dev/hdc1 1.9G 2.0G 560k 100% /
# du -csh /var/log/frontview/error.log
1.4G /var/log/frontview/error.log
That log was last updated back in June and contains errors related to the http/s service. It's typically not a very important log so I just emptied it.
Related Content
NETGEAR Academy

Boost your skills with the Netgear Academy - Get trained, certified and stay ahead with the latest Netgear technology!
Join Us!