NETGEAR is aware of a growing number of phone and online scams. To learn how to stay safe click here.
Forum Discussion
RN104 raid volume recovery
I understand this could be a duplicate post but I tried looking several other posts on Netgear community and could not find a solution so I am posting my problem here. I had a NAS (RN104) with 4T...
Welcome to the Community!
Did the expansion finished before this happened? it would be best if you can send us the full logs on a shared link. You can PM it to us.
Regards
Hello Marc,
Thanks for looking into this. Unfortunately logs are not available now. There was a requirement of shares availability and someone reset the whole NAS device and rebuild the OS on new drives.
However when I had discussed with the person who was working on it and I am completely sure that expansion was not completed. When the new drives were added, it started re-sync process which was interrupted and never completed. I recently discovered that someone disabled the x-raid also (hoping to create a new volume on new added drives) and since then it has this issues.
Right now I have those two drives with me which were in x-raid (raid1) configuration earlier. I am hoping that I could mount the md raid volume in Linux and access the data from there.
I can provide more outputs from that drive if that helps. Sorry I have only limited data to provide here.
Thanks,
Varun
So your previously RAID1 was expanded to RAID5 but did not complete right? since Flex-RAID was used and it was manually added. Then there was a reset if I understand correctly.If you have a Windows PC trying out ReCLAIMe to access the data would be suggested. If you are using Linux then you should be able to mount the RAID using CLI.
Here are some Community post that might help
https://ubuntuforums.org/showthread.php?t=2265348
https://unix.stackexchange.com/questions/300122/mount-a-single-hard-disk-that-was-part-of-raid-1
DDRescue might also be of use. Haven't use much of Linux to be honest but I'm sure other members will be able to help as well.
Hope this helps!
Regards
Marc_V wrote:
https://ubuntuforums.org/showthread.php?t=2265348
These won't work with an OS-6 NAS.
Something like this should work:
# apt-get update
# apt-get install mdadm btrfs-tools
# mdadm --assemble --scan
# cat /proc/mdstat
# mount -t btrfs -o ro /dev/md127 /mntThough if the system were shut down in the middle of converting RAID-1 to RAID-5 you likely will need data recovery (such as ReclaiMe).
Hi Stephen,
Thanks for the suuggestion. I think I got your point. The only problem I am stuck now is the md volumes are in "inactive" state right now. I am sure that I will be able to mount these with your command once these are active. See below output for reference.
----------------------------------------
root@localhost-live ~]# cat /proc/mdstat
Personalities :
md125 : inactive sdb1[0](S)
4190208 blocks super 1.2
md126 : inactive sdb3[0](S)
3902166840 blocks super 1.2
md127 : inactive sdb2[2](S)
523264 blocks super 1.2----------------------------------------
I tried stopping and then reassemble but get below error.
----------------------------------------
[root@localhost-live ~]# mdadm --stop md126
mdadm: stopped md126
[root@localhost-live ~]# cat /proc/mdstat
Personalities :
md125 : inactive sdb1[0](S)
4190208 blocks super 1.2
md127 : inactive sdb2[2](S)
523264 blocks super 1.2
unused devices: <none>
[root@localhost-live ~]# mdadm --assemble /dev/md126 /dev/sdb3 -v
mdadm: looking for devices for /dev/md126
mdadm: /dev/sdb3 is identified as a member of /dev/md126, slot 0.
mdadm: no uptodate device for slot 1 of /dev/md126
mdadm: no uptodate device for slot 2 of /dev/md126
mdadm: no uptodate device for slot 3 of /dev/md126
mdadm: added /dev/sdb3 to /dev/md126 as 0
mdadm: /dev/md126 assembled from 1 drive - not enough to start the array.----------------------------------------
It looks like from the output below that it require 4 devices to start the array. I tried force option also but still get the same error. Is it possible if we can tweak the md definition and fool it to consider one device only. Or may be some other way around to make it active.
----------------------------------------
[root@localhost-live ~]# mdadm --examine /dev/sdb3
/dev/sdb3:
Magic : a92b4efc
Version : 1.2
Feature Map : 0x44
Array UUID : 946f1daa:25266b75:83ccd4cc:c9f1d2b7
Name : 2fe57776:data-0
Creation Time : Sat Aug 20 15:07:12 2016
Raid Level : raid5
Raid Devices : 4Avail Dev Size : 7804333680 (3721.40 GiB 3995.82 GB)
Array Size : 11706500352 (11164.19 GiB 11987.46 GB)
Used Dev Size : 7804333568 (3721.40 GiB 3995.82 GB)
Data Offset : 262144 sectors
New Offset : 261760 sectors
Super Offset : 8 sectors
State : clean
Device UUID : d6338322:5447e981:449fb043:53008fefReshape pos'n : 66118464 (63.06 GiB 67.71 GB)
Delta Devices : 2 (2->4)Update Time : Sun Dec 22 01:36:17 2019
Checksum : 64f1ca9d - correct
Events : 373Layout : left-symmetric
Chunk Size : 64KDevice Role : Active device 0
Array State : AAAA ('A' == active, '.' == missing, 'R' == replacing)----------------------------------------
NETGEAR Academy
Boost your skills with the Netgear Academy - Get trained, certified and stay ahead with the latest Netgear technology!
Join Us!
