ReadyNAS 104 lost x-raid volume! how can I recover the volume from my intact 3 disks ?

[TokyoPeter]

Hello,

I have a RN104 with 3 x WD 3TB Red drives. They were configured by X-RAID.

Model: RN104

Firmware: 6.4.1

About a month ago, the RN would hang, ping was working, but Frontview nor SSH would respond. The only way to get back in was by a pulling the power plug and restarting.

So I final go a hold of a new 3TB WD Red and put that into bay #1. I pulled the the RAID drives in bays 2, 3, 4.

Reinstalled the OS onto the new drive in Bay #1

Then pushed the drives in bay 2,3,4 back in.

Let the system sync the drives.

This is were I don't know what to do. I was expecting the RAID drives to mount. They didn't and the few commands I know of aren't helping.

Here's what I've tried.

root@prkt-ReadyNAS:/# fdisk -l

 

Disk /dev/mtdblock0: 1 MB, 1572864 bytes

255 heads, 63 sectors/track, 0 cylinders, total 3072 sectors

Units = sectors of 1 * 512 = 512 bytes

Sector size (logical/physical): 512 bytes / 512 bytes

I/O size (minimum/optimal): 512 bytes / 512 bytes

Disk identifier: 0x234ef2ce

 

Disk /dev/mtdblock0 doesn't contain a valid partition table

 

Disk /dev/mtdblock1: 0 MB, 524288 bytes

255 heads, 63 sectors/track, 0 cylinders, total 1024 sectors

Units = sectors of 1 * 512 = 512 bytes

Sector size (logical/physical): 512 bytes / 512 bytes

I/O size (minimum/optimal): 512 bytes / 512 bytes

Disk identifier: 0x30303032

 

Disk /dev/mtdblock1 doesn't contain a valid partition table

 

Disk /dev/mtdblock2: 6 MB, 6291456 bytes

255 heads, 63 sectors/track, 0 cylinders, total 12288 sectors

Units = sectors of 1 * 512 = 512 bytes

Sector size (logical/physical): 512 bytes / 512 bytes

I/O size (minimum/optimal): 512 bytes / 512 bytes

Disk identifier: 0xe0496006

 

Disk /dev/mtdblock2 doesn't contain a valid partition table

 

Disk /dev/mtdblock3: 4 MB, 4194304 bytes

255 heads, 63 sectors/track, 0 cylinders, total 8192 sectors

Units = sectors of 1 * 512 = 512 bytes

Sector size (logical/physical): 512 bytes / 512 bytes

I/O size (minimum/optimal): 512 bytes / 512 bytes

Disk identifier: 0x4e8e2338

 

Disk /dev/mtdblock3 doesn't contain a valid partition table

 

Disk /dev/mtdblock4: 121 MB, 121634816 bytes

255 heads, 63 sectors/track, 14 cylinders, total 237568 sectors

Units = sectors of 1 * 512 = 512 bytes

Sector size (logical/physical): 512 bytes / 512 bytes

I/O size (minimum/optimal): 512 bytes / 512 bytes

Disk identifier: 0x00000000

 

Disk /dev/mtdblock4 doesn't contain a valid partition table

 

WARNING: GPT (GUID Partition Table) detected on '/dev/sda'! The util fdisk doesn't support GPT. Use GNU Parted.

 

 

Disk /dev/sda: 3000.6 GB, 3000592982016 bytes

256 heads, 63 sectors/track, 363376 cylinders, total 5860533168 sectors

Units = sectors of 1 * 512 = 512 bytes

Sector size (logical/physical): 512 bytes / 4096 bytes

I/O size (minimum/optimal): 4096 bytes / 4096 bytes

Disk identifier: 0x00000000

 

   Device Boot      Start         End      Blocks   Id  System

/dev/sda1               1  4294967295  2147483647+  ee  GPT

Partition 1 does not start on physical sector boundary.

 

WARNING: GPT (GUID Partition Table) detected on '/dev/sdc'! The util fdisk doesn't support GPT. Use GNU Parted.

 

 

Disk /dev/sdc: 3000.6 GB, 3000592982016 bytes

256 heads, 63 sectors/track, 363376 cylinders, total 5860533168 sectors

Units = sectors of 1 * 512 = 512 bytes

Sector size (logical/physical): 512 bytes / 4096 bytes

I/O size (minimum/optimal): 4096 bytes / 4096 bytes

Disk identifier: 0x00000000

 

   Device Boot      Start         End      Blocks   Id  System

/dev/sdc1               1  4294967295  2147483647+  ee  GPT

Partition 1 does not start on physical sector boundary.

 

WARNING: GPT (GUID Partition Table) detected on '/dev/sdd'! The util fdisk doesn't support GPT. Use GNU Parted.

 

 

Disk /dev/sdd: 3000.6 GB, 3000592982016 bytes

256 heads, 63 sectors/track, 363376 cylinders, total 5860533168 sectors

Units = sectors of 1 * 512 = 512 bytes

Sector size (logical/physical): 512 bytes / 4096 bytes

I/O size (minimum/optimal): 4096 bytes / 4096 bytes

Disk identifier: 0x00000000

 

   Device Boot      Start         End      Blocks   Id  System

/dev/sdd1               1  4294967295  2147483647+  ee  GPT

Partition 1 does not start on physical sector boundary.

 

WARNING: GPT (GUID Partition Table) detected on '/dev/sdb'! The util fdisk doesn't support GPT. Use GNU Parted.

 

 

Disk /dev/sdb: 3000.6 GB, 3000592982016 bytes

256 heads, 63 sectors/track, 363376 cylinders, total 5860533168 sectors

Units = sectors of 1 * 512 = 512 bytes

Sector size (logical/physical): 512 bytes / 4096 bytes

I/O size (minimum/optimal): 4096 bytes / 4096 bytes

Disk identifier: 0x00000000

 

   Device Boot      Start         End      Blocks   Id  System

/dev/sdb1               1  4294967295  2147483647+  ee  GPT

Partition 1 does not start on physical sector boundary.

 

Disk /dev/md0: 4290 MB, 4290772992 bytes

2 heads, 4 sectors/track, 1047552 cylinders, total 8380416 sectors

Units = sectors of 1 * 512 = 512 bytes

Sector size (logical/physical): 512 bytes / 4096 bytes

I/O size (minimum/optimal): 4096 bytes / 4096 bytes

Disk identifier: 0x00000000

 

Disk /dev/md0 doesn't contain a valid partition table

 

Disk /dev/md1: 536 MB, 536281088 bytes

2 heads, 4 sectors/track, 130928 cylinders, total 1047424 sectors

Units = sectors of 1 * 512 = 512 bytes

Sector size (logical/physical): 512 bytes / 4096 bytes

I/O size (minimum/optimal): 4096 bytes / 4096 bytes

Disk identifier: 0x00000000

 

Disk /dev/md1 doesn't contain a valid partition table

 

Disk /dev/md127: 2000.1 GB, 2000123723776 bytes

2 heads, 4 sectors/track, 488311456 cylinders, total 3906491648 sectors

Units = sectors of 1 * 512 = 512 bytes

Sector size (logical/physical): 512 bytes / 4096 bytes

I/O size (minimum/optimal): 65536 bytes / 131072 bytes

Disk identifier: 0x00000000

 

Disk /dev/md127 doesn't contain a valid partition table

 

Disk /dev/md126: 2995.6 GB, 2995624738816 bytes

2 heads, 4 sectors/track, 731353696 cylinders, total 5850829568 sectors

Units = sectors of 1 * 512 = 512 bytes

Sector size (logical/physical): 512 bytes / 4096 bytes

I/O size (minimum/optimal): 4096 bytes / 4096 bytes

Disk identifier: 0x00000000

 

Disk /dev/md126 doesn't contain a valid partition table

root@prkt-ReadyNAS:/#

root@prkt-ReadyNAS:/# df

Filesystem      1K-blocks   Used  Available Use% Mounted on

tmpfs               10240      4      10236   1% /dev

/dev/md0          3862208 585976    3050340  17% /

tmpfs              254400     44     254356   1% /dev/shm

tmpfs              254400   1520     252880   1% /run

tmpfs              254400      0     254400   0% /sys/fs/cgroup

tmpfs              254400      0     254400   0% /media

/dev/md126     2925414784  37540 2923285212   1% /data

/dev/md126     2925414784  37540 2923285212   1% /apps

/dev/md126     2925414784  37540 2923285212   1% /home

/dev/md126     2925414784  37540 2923285212   1% /run/nfs4/home

root@prkt-ReadyNAS:/#

 

root@prkt-ReadyNAS:/# mdadm --assemble --scan

mdadm: Devices UUID-715a3222:7e5e6992:4860af2e:a284d48f and UUID-cfb00158:50416e98:000137cf:ddb6e15d have the same name: /dev/md/0

mdadm: Duplicate MD device names in conf file were found.

root@prkt-ReadyNAS:/#

What I don't know is how to get access to the data on the raid drives. I know it's still there, because if I shutdown, pull the drive in Bay 1 out and restart, the system comes up on the RAID drives (and then stops responding after about 5 minutes. Which is the whole root cause trying to be solved here.

Ultimately, what I want to do is bring up the RAID drives. Get the data off of them, wipe them and then let X-RAID reconfigure them into a new RAID with the drive in Bay 1.

Any help would be great. Thanks

[StephenB]

When you installed the single new drive, you created empty xraid volume.

Then you added back drives 2-4.  Fortunately it didn't resync.  If it had, it would have resynced 2-4 to the empty volume and deleted all your data.

Contact support (even though it is not free), and have them fix the system.

[TokyoPeter]

I contacted support and offered to pay for any assistance but haven't heard back from them. Would love to just know a couple of commands that would enable me to mount the drives. I'll do the research and work it out.

Thanks

[mdgm-ntgr]

Not sure why suport did not get back to you. I have asked them to follow up.

From the information you've provided the extent of the problem is unclear.

Support would have to do some remote diagnosis to determine the extent of the problem.

It could be relatively straightforward to resolve or it could be much more complex, depending on what the issue is.