NETGEAR is aware of a growing number of phone and online scams. To learn how to stay safe click here.
Forum Discussion
Swapped drives now Not-Redundant
My ReadyNAS NV+ v2 was full of 1TB disks and I've been replacing them over time with 3TB disks. The last swap out seemed to work fine except now the web interface shows X-RAID2 (Not-Redundant) which makes me think that next time I try to swap out a disk or a disk fails I'll lose everything on the entire array. Why did it build a non redundant array? I have these disks in the unit
Disk 1 SAMSUNG HD103SJ 931 GB (28 °C, Write-cache On). Status: OK
Disk 2 WDC WD30EZRS-00J99B0 2794 GB (28 °C, Write-cache On). Status: OK
Disk 3 Seagate ST31000528AS 931 GB (30 °C, Write-cache On). Status: OK
Disk 4 WDC WD30EZRS-00J99B0 2794 GB (30 °C, Write-cache On). Status: OK
Is there any way to make it rebuild the array properly without going through all the effort of restoring a backup?
Also, it now says I have 4.6TB available which is an odd number. If the whole thing is non redundant I would expect 8TB (3+3+1+1). So maybe its actually misreporting the redundancy level?
Disk 1 SAMSUNG HD103SJ 931 GB (28 °C, Write-cache On). Status: OK
Disk 2 WDC WD30EZRS-00J99B0 2794 GB (28 °C, Write-cache On). Status: OK
Disk 3 Seagate ST31000528AS 931 GB (30 °C, Write-cache On). Status: OK
Disk 4 WDC WD30EZRS-00J99B0 2794 GB (30 °C, Write-cache On). Status: OK
Is there any way to make it rebuild the array properly without going through all the effort of restoring a backup?
Also, it now says I have 4.6TB available which is an odd number. If the whole thing is non redundant I would expect 8TB (3+3+1+1). So maybe its actually misreporting the redundancy level?
10 Replies
Replies have been turned off for this discussion
- Your enclosure.log says your volume is not redundant but it shows all disks as O.K.
Looking at mdstat.log it shows The 4x1TB RAID-5 layer (md2) as redundant but not the 2x1TB RAID-1 layer (md3).
For some reason /dev/sdb (probably the WD30EZRS in slot 2), the disk you most recently added is not synced in as part of the OS partition (on md0) properly. This may be the problem.
Would suggest you contact NetGear tech support for advice. - Thanks for your help. The barrier to entry for Netgear tech support is too high so I'll just try swapping out a 1TB disk next time I get a 3TB in and see where that leaves me. Maybe it'll resync itself back into correctly working.
- Removing the 3TB disk last added while the NAS is on, waiting 30 seconds or so, checking to see that you can still access your data and if you can still access your data then readding the disk will likely resolve the problem. A resync will occur and your volume should then be redundant again.
- Basically sometimes a resync doesn't work. It appears in this case that there was a problem syncing the last added 3TB drive into the array.
mdgm wrote: Removing the 3TB disk last added while the NAS is on, waiting 30 seconds or so, checking to see that you can still access your data and if you can still access your data then readding the disk will likely resolve the problem. A resync will occur and your volume should then be redundant again.
This totally worked. Thanks again for your help.- Great!
Edit: as Papabear points out current volume capacity is fully expanded. - For an array with 2x1TB and 2x3TB drives, the 4.6TB space (net after overhead) is about right. My NVX in that configuration has 4.5TB. (3x1TB first layer, 1x2TB second layer less overhead, the second 3TB drive provides the redundancy).
- Oops. Good point
- Same problem as OP here .. status says not redundant but space available suggests otherwise.
Disk 1
WDC WD10EAVS-00D7B1 931 GB (32 °C / 89 °F, Write-cache On). Status: OK
Disk 2
ST31500541AS 1397 GB (33 °C / 91 °F, Write-cache On). Status: OK
Disk 3
ST31500541AS 1397 GB (32 °C / 89 °F, Write-cache On). Status: OK
Disk 4
ST2000DL004 HD204UI 1863 GB (30 °C / 86 °F, Write-cache On). Status: OK
..I've had a ticket with Netgear support now for 3 days. They got me to try OS reinstall and now I've left it in debug mode for them to connect and poke about for the past 2 days but still no news.
How do I tell which drive has caused the array issue? If it's a 2Gb I can pull it, use to backup and then start again as I'm only using 1.8Tb of the array. I've already tried pulling a drive and re-sync but no joy, unless I pulled the wrong drive of course.
Volumes
/c
X-RAID2 (Not-Redundant)
1.8 TB Free Of 3.6 TB
Thanks!
Adam - Forgot to add logs:
enclosure.logtemp!!1!!status=ok::descr=30.0C/86.0F::expected=0-65C/32-149F
fan!!1!!status=ok::descr=1350RPM::type=SYS
ups!!1!!status=not_present::descr=Not present
volume!!1!!status=warn::descr=Volume C: RAID Level X2, Not redundant. A disk failure will render this volume dead.; 1875 GB (50%) of 3687 GB used
disk!!1!!status=ok::descr=Channel 1: WDC WD10EAVS-00D7B1 931 GB, 30C/86F
disk!!2!!status=ok::descr=Channel 2: ST31500541AS 1397 GB, 32C/89F
disk!!3!!status=ok::descr=Channel 3: ST31500541AS 1397 GB, 31C/87F
disk!!4!!status=ok::descr=Channel 4: ST2000DL004 HD204UI 1863 GB, 27C/80F
model!!0!!mode=home::descr=ReadyNAS NV+ v2::arch=arm1::jbod=1
mdstat.logPersonalities : [linear] [raid0] [raid1] [raid10] [raid6] [raid5] [raid4]
md3 : active raid5 sdb4[0] sdd4[3] sdc4[1]
976749568 blocks super 1.2 level 5, 64k chunk, algorithm 2 [3/3] [UUU]
md2 : active raid5 sda3[0] sdc3[3] sdb3[2]
2916122112 blocks super 1.2 level 5, 64k chunk, algorithm 2 [4/3] [UUU_]
md1 : active raid1 sdd2[4] sdc2[2] sdb2[1]
524276 blocks super 1.2 [4/3] [UUU_]
md0 : active raid1 sdd1[4] sdc1[3] sdb1[2]
4193268 blocks super 1.2 [4/3] [UUU_]
unused devices: <none>
NETGEAR Academy
Boost your skills with the Netgear Academy - Get trained, certified and stay ahead with the latest Netgear technology!
Join Us!
