NETGEAR is aware of a growing number of phone and online scams. To learn how to stay safe click here.
Forum Discussion
RN316 Upgraded Firmware, EDA500 Volumes are messed up
I just upgraded my firmware. machine booted and then one of my EDA500s doesn't show up. The other is also messed up. Doesn't seem that netgear provides support anymore... I used to be able to b...
joe_schmo wrote:
And about the use of the --force... do you think that that would mess data up given that it seems accessible via reclaime? Or should I give that a shot on one while I'm reclaiming the other?
To some degree this depends on the consequences of data loss, and how much you are prepared to spend on recovery.
I am thinking that the disks in the array are somewhat out of sync. There might be some some data corruption, since an out-of-sync array means that writes have somehow been lost. So there is some risk with --force.
You could alternatively
- offload the data with ReclaiMe, and then recreate the array. That would be time consuming, and it would require a lot of storage.
- clone all the disks - requiring you to purchase five 10 TB drives. You could then attempt to manually assemble the array using the clones. Also a fair amount of work, but if successful would eliminate the need to recreate the array and reload all the data.
- find a data recovery service (or find a way a path to Netgear's recovery service).
So for one of the EDAs I am going to go the reclaim route. I have enough drives for that.
If I unplug the EDAs during reboot, the data on the NAS itself is fine. It only shows up messed up if EDA is connected during boot.
So on the connected EDA that I am trying to get back at the moment EDA2
md123 : active raid5 sdg3[0] sdk3[4] sdj3[3] sdi3[2] sdh3[1]
39046344448 blocks super 1.2 level 5, 64k chunk, algorithm 2 [5/5] [UUUUU]
[>....................] resync = 0.0% (8659028/9761586112) finish=6192.0min speed=26250K/sec
root@NAS:~# mdadm --stop /dev/md123
mdadm: Cannot get exclusive access to /dev/md123:Perhaps a running process, moun ted filesystem or active volume group?
root@NAS:~# umount /dev/md123
root@NAS:~# mdadm --stop /dev/md123
mdadm: stopped /dev/md123
root@NAS:~# mdadm --assemble /dev/md123
mdadm: /dev/md123 not identified in config file.
root@NAS:~# mdadm --assemble --scan
mdadm: /dev/md/eda3-0 has been started with 5 drives.
mdadm: Found some drive for an array that is already active: /dev/md/0
mdadm: giving up.
mdadm: Found some drive for an array that is already active: /dev/md/0
mdadm: giving up.
root@NAS:~# cat /proc/mdstat
Personalities : [raid0] [raid1] [raid10] [raid6] [raid5] [raid4]
md123 : active raid5 sdg3[0] sdk3[4] sdj3[3] sdi3[2] sdh3[1]
39046344448 blocks super 1.2 level 5, 64k chunk, algorithm 2 [5/5] [UUUUU]
[>....................] resync = 0.0% (8659028/9761586112) finish=6192.0min speed=26250K/sec
md124 : active raid5 sda6[0] sdd6[5] sdc6[4] sde6[6] sdb6[2] sdf6[1]
9766864640 blocks super 1.2 level 5, 64k chunk, algorithm 2 [6/6] [UUUUUU]
md125 : active raid5 sda5[5] sdf5[6] sde5[9] sdc5[7] sdd5[10] sdb5[8]
9766864320 blocks super 1.2 level 5, 64k chunk, algorithm 2 [6/6] [UUUUUU]
md126 : active raid5 sda4[6] sdf4[11] sde4[10] sdd4[8] sdc4[9] sdb4[7]
4883113920 blocks super 1.2 level 5, 64k chunk, algorithm 2 [6/6] [UUUUUU]
md127 : active raid5 sda3[6] sdf3[11] sde3[10] sdd3[9] sdc3[8] sdb3[7]
14627073280 blocks super 1.2 level 5, 64k chunk, algorithm 2 [6/6] [UUUUUU]
md0 : active raid1 sda1[17] sdj1[10](W)(S) sdk1[11](W)(S) sdb1[16] sdc1[18] sdd1[19] sde1[20] sdf1[21] sdi1[9](W)
4192192 blocks super 1.2 [7/7] [UUUUUUU]
md1 : active raid10 sda2[0] sdf2[5] sde2[4] sdd2[3] sdc2[2] sdb2[1]
1566720 blocks super 1.2 512K chunks 2 near-copies [6/6] [UUUUUU]
root@NAS:~# cat /proc/mdstat
Personalities : [raid0] [raid1] [raid10] [raid6] [raid5] [raid4]
md123 : active raid5 sdg3[0] sdk3[4] sdj3[3] sdi3[2] sdh3[1]
39046344448 blocks super 1.2 level 5, 64k chunk, algorithm 2 [5/5] [UUUUU]
[>....................] resync = 0.1% (10726372/9761586112) finish=6214.8min speed=26148K/sec
Somehow the system now things EDA2 is now called EDA3. Not sure if that is part of the problem or just a side effect.
So while I still hold out hope that I'll figure out how to make the NAS see the 2 EDAs again.
If I decide to wipe them and then start from scratch, how do I get ride of the 3 that show up here:
I can't see the attachment. Are the three you are talking about three from one EDA that should be one? If that's the case, they aren't really volumes that the OS recognizes, and deleting the ones that aren't "real" might cause a problem. On mine, I booted the NAS without the offending EDA and it then showed one "missing" volume, which I deleted. I then wiped all the partitions from the drives so the NAS could start with them from scratch.
Right now, I'm not deleting anything while I grab data off of them via reclaimme.
Then I will try recovering them through mdadm.
And if that finally doesn't work, I'll rebuild from backup/reclaim.Contacting ReadyNAS support via Email will the best option if you want to seek assistance with them. You can send an email to readynassupport@netgear.com. Data Recovery may apply but no support contract is available for ReadyNAS devices.
HTH
Marc_V wrote:Contacting ReadyNAS support via Email will the best option if you want to seek assistance with them. You can send an email to readynassupport@netgear.com. Data Recovery may apply but no support contract is available for ReadyNAS devices.
HTH
Hi Marc_V
When did that change? I remember back in 2018/19 I was able to spend $150 for a support case.
NETGEAR Academy
Boost your skills with the Netgear Academy - Get trained, certified and stay ahead with the latest Netgear technology!
Join Us!
