NETGEAR is aware of a growing number of phone and online scams. To learn how to stay safe click here.
Forum Discussion
ReadyNAS Ultra 2: how to recover data from RAID-1 disks?
Hello,
- I have a ReadyNas -> Netgear RNDU2120-100PES (check image below).
- It has a "blue light" - but the network port NIC seems totally dead. Not link at all. So my guess unit works w...
Fixed the thread title.
It's advisable to check disk health and the state of the RAID array before proceeding to run the commands you mentioned.
Hello mdgm,
- Can you update me on the commands i should run to check the "helath and state of RAID array" ?
- Also note - > i have one of the disks attached to a PC - should i attach both disk?
Best regards,
Johan
Hello Again,
- I know ran the commands:
# mdadm --assemble --scan
# vgscan
# vgchange -a y
# mount /dev/c/c /mntBut cant seem to mount the drive- error "unknown filesystem type 'linux_raid_member".
Note i have one of the two disks - connected to the PC.
Look at images below:
# mount -o ro -t ext4 /dev/c/c /mnt
Hello,
- Cant mount it > it says "is already mounted" ?
- Check attached image.
- Also tried to create a new folder /mnt/recovery - and mount it here instead of /mnt/sdb3 but no luck - seems something is preventing me from accessing this.
- Can you help me remotely? (ssh access)
Hello,
- Also this information is from dmesg:
[ 362.460636] md: md0 stopped.
[ 362.461213] md: bind<sdb1>
[ 362.469600] md: raid1 personality registered for level 1
[ 362.469881] md/raid1:md0: active with 1 out of 2 mirrors
[ 362.469904] md0: detected capacity change from 0 to 4293906432
[ 362.476292] md0: unknown partition table
[ 362.661170] md: bind<sdb2>
[ 362.662166] md/raid1:md1: active with 1 out of 2 mirrors
[ 362.662191] md1: detected capacity change from 0 to 536858624
[ 362.662521] md1: unknown partition table
[ 362.727698] md: bind<sdb3>
[ 362.818110] raid6: sse2x1 6145 MB/s
[ 362.886093] raid6: sse2x2 9477 MB/s
[ 362.954076] raid6: sse2x4 12507 MB/s
[ 362.954078] raid6: using algorithm sse2x4 (12507 MB/s)
[ 362.954080] raid6: using ssse3x2 recovery algorithm
[ 362.971233] async_tx: api initialized (async)
[ 362.971591] xor: automatically using best checksumming function:
[ 363.010060] avx : 25118.000 MB/sec
[ 363.329026] md: raid6 personality registered for level 6
[ 363.329028] md: raid5 personality registered for level 5
[ 363.329029] md: raid4 personality registered for level 4
[ 363.329260] md/raid:md2: device sdb3 operational as raid disk 0
[ 363.329411] md/raid:md2: allocated 0kB
[ 363.329423] md/raid:md2: raid level 5 active with 1 out of 2 devices, algorithm 2
[ 363.329424] RAID conf printout:
[ 363.329425] --- level:5 rd:2 wd:1
[ 363.329426] disk 0, o:1, dev:sdb3
[ 363.329452] md2: detected capacity change from 0 to 1995563728896
[ 363.329794] md2: unknown partition table
[ 586.406417] device-mapper: uevent: version 1.0.3
[ 586.406482] device-mapper: ioctl: 4.27.0-ioctl (2013-10-30) initialised: dm-devel@redhat.com
[ 6740.573943] EXT4-fs (md1): VFS: Can't find ext4 filesystem
NETGEAR Academy
Boost your skills with the Netgear Academy - Get trained, certified and stay ahead with the latest Netgear technology!
Join Us!
