LQ Newbie
Registered: Jul 2012
Posts: 1
Rep:
|
JBOD Raid Rebuild
Hi All
I've perused the forum and have tried most of the solutions I did find but to no avail. In brief here's the situation.
I have a Seagate NAS 440 which I fitted with 4 x 2TB Seagate Barracude drives. I used the built-in firmware to configure it as an 8TB JBOD. A couple of weeks ago I can't login to my NAS anymore, not with any usernames/password. Performed a reset (of the firmware only, not the RAID), but still doesn't work. The NAS still reports 27% usage on the Volume, so I'm thinking 'NO data loss'. Spent three days on emails to Seagate and their eventual solution was to do a factory reset on the NAS (which destroys the RAID an consequently all data on it) and/or to send my drives for data recovery. Nice.
So what I've ended trying is to wipe Windows 7 from my machine and install the four drives, in sequence on SATA 1/2/3/4 of my motherboard. I'm running Ubuntu from the disk because I have only four SATA ports on my board and no IDE HDD's anymore. Now, I'm no Linux expert at all, so I've been hitting Google like a frantic banshee and learning as I go. I've tried everything but may be missing something small. Using mdadm I manage to get volumes mounted, but it doesn't seem to be acting the way I expected it to.
Here is the output of "cat /proc/mdstat":
ubuntu@ubuntu:~$ cat /proc/mdstat
Personalities : [linear] [raid1]
md118 : active raid1 sdb1[2]
1043840 blocks [4/1] [__U_]
md119 : active raid1 sdd1[3]
1043840 blocks [4/1] [___U]
md120 : active raid1 sdb3[2]
521408 blocks [4/1] [__U_]
md121 : active raid1 sdc1[1]
1043840 blocks [4/1] [_U__]
md122 : active raid1 sdc3[1] sdd3[3]
521408 blocks [4/2] [_U_U]
md123 : active raid1 sda1[0]
1043840 blocks [4/1] [U___]
md124 : active raid1 sda3[0]
521408 blocks [4/1] [U___]
md125 : active raid1 sda4[0]
1950707872 blocks super 1.2 [2/1] [U_]
md126 : active raid1 sdc4[0]
1950707872 blocks super 1.2 [2/1] [U_]
md127 : active linear sdb4[0] sdd4[1]
3901415936 blocks super 1.2 64k rounding
unused devices: <none>
============================
here is the output of "sudo fdisk -l":
WARNING: GPT (GUID Partition Table) detected on '/dev/sda'! The util fdisk doesn't support GPT. Use GNU Parted.
Disk /dev/sda: 2000.4 GB, 2000398934016 bytes
255 heads, 63 sectors/track, 243201 cylinders, total 3907029168 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: 0x35751000
Device Boot Start End Blocks Id System
/dev/sda1 1 3907029167 1953514583+ ee GPT
WARNING: GPT (GUID Partition Table) detected on '/dev/sdc'! The util fdisk doesn't support GPT. Use GNU Parted.
Disk /dev/sdc: 2000.4 GB, 2000398934016 bytes
255 heads, 63 sectors/track, 243201 cylinders, total 3907029168 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: 0x35751000
Device Boot Start End Blocks Id System
/dev/sdc1 1 3907029167 1953514583+ ee GPT
WARNING: GPT (GUID Partition Table) detected on '/dev/sdd'! The util fdisk doesn't support GPT. Use GNU Parted.
Disk /dev/sdd: 2000.4 GB, 2000398934016 bytes
255 heads, 63 sectors/track, 243201 cylinders, total 3907029168 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: 0x35751000
Device Boot Start End Blocks Id System
/dev/sdd1 1 3907029167 1953514583+ ee GPT
WARNING: GPT (GUID Partition Table) detected on '/dev/sdb'! The util fdisk doesn't support GPT. Use GNU Parted.
Disk /dev/sdb: 2000.4 GB, 2000398934016 bytes
255 heads, 63 sectors/track, 243201 cylinders, total 3907029168 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: 0x35751000
Device Boot Start End Blocks Id System
/dev/sdb1 1 3907029167 1953514583+ ee GPT
Disk /dev/md127: 3995.0 GB, 3995049918464 bytes
2 heads, 4 sectors/track, 975353984 cylinders, total 7802831872 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/md127 doesn't contain a valid partition table
Disk /dev/md126: 1997.5 GB, 1997524860928 bytes
2 heads, 4 sectors/track, 487676968 cylinders, total 3901415744 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/md126 doesn't contain a valid partition table
Disk /dev/md125: 1997.5 GB, 1997524860928 bytes
2 heads, 4 sectors/track, 487676968 cylinders, total 3901415744 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/md125 doesn't contain a valid partition table
Disk /dev/md124: 533 MB, 533921792 bytes
2 heads, 4 sectors/track, 130352 cylinders, total 1042816 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/md124 doesn't contain a valid partition table
Disk /dev/md123: 1068 MB, 1068892160 bytes
2 heads, 4 sectors/track, 260960 cylinders, total 2087680 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/md123 doesn't contain a valid partition table
Disk /dev/md122: 533 MB, 533921792 bytes
2 heads, 4 sectors/track, 130352 cylinders, total 1042816 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/md122 doesn't contain a valid partition table
Disk /dev/md121: 1068 MB, 1068892160 bytes
2 heads, 4 sectors/track, 260960 cylinders, total 2087680 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/md121 doesn't contain a valid partition table
Disk /dev/md120: 533 MB, 533921792 bytes
2 heads, 4 sectors/track, 130352 cylinders, total 1042816 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/md120 doesn't contain a valid partition table
Disk /dev/md119: 1068 MB, 1068892160 bytes
2 heads, 4 sectors/track, 260960 cylinders, total 2087680 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/md119 doesn't contain a valid partition table
Disk /dev/md118: 1068 MB, 1068892160 bytes
2 heads, 4 sectors/track, 260960 cylinders, total 2087680 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/md118 doesn't contain a valid partition table
=============================
I've already run mdadm --assemble --scan, which created an Array in Disk Utility, with a Volume Group which refuses to start with a very vague "no such file or folder" error. The same with some of the logical volumes.
Also, what I don't understand is how the volume configuration was done: 1 x 1.1GB, 2 x 2TB and 1 x 4TB.
So it could be that Seagate don't know what they're doing (Which I'm inclined to think) or that I set up my mdadm incorrectly.
Can anyone help? I'm at my wits end and would hate to lose my data!!!
Thanks in advance.
|