Rebuild the Software RAID Array after a Drive Replacement
£10-60 GBP
완료함
게시됨 9년 이상 전
£10-60 GBP
제출할때 지불됩니다
After a disk replacement on my server I need to rebuild the software array. I have had a look at the guide supplied by 1and1 but it does not correspond to what I am seeing in linux.
[login to view URL]
Here is what I am seeing:
According to the guide they should be marked with an F as failed. I get:
rescue:/# cat /proc/mdstat
Personalities : [linear] [raid0] [raid1] [raid10] [raid6] [raid5] [raid4] [fault y]
md1 : active raid1 sda1[0]
4194240 blocks [2/1] [U_]
md3 : active raid1 sda3[1]
970470016 blocks [2/1] [_U]
unused devices: <none>
And fdisk -l is:
rescue:/# fdisk -l
Disk /dev/sda: 1000.2 GB, 1000204886016 bytes
255 heads, 63 sectors/track, 121601 cylinders, total 1953525168 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: 0xc05267b6
Device Boot Start End Blocks Id System
/dev/sda1 2048 8390655 4194304 fd Linux raid autodetect
/dev/sda2 8390656 12584959 2097152 82 Linux swap / Solaris
/dev/sda3 12584960 1953525167 970470104 fd Linux raid autodetect
Disk /dev/sdb: 1000.2 GB, 1000204886016 bytes
255 heads, 63 sectors/track, 121601 cylinders, total 1953525168 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: 0x55555555
Disk /dev/sdb doesn't contain a valid partition table
Disk /dev/md3: 993.8 GB, 993761296384 bytes
2 heads, 4 sectors/track, 242617504 cylinders, total 1940940032 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/md3 doesn't contain a valid partition table
Disk /dev/md1: 4294 MB, 4294901760 bytes
2 heads, 4 sectors/track, 1048560 cylinders, total 8388480 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/md1 doesn't contain a valid partition table
Disk /dev/mapper/vg00-usr: 4294 MB, 4294967296 bytes
255 heads, 63 sectors/track, 522 cylinders, total 8388608 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/mapper/vg00-usr doesn't contain a valid partition table
Disk /dev/mapper/vg00-var: 859.0 GB, 858993459200 bytes
255 heads, 63 sectors/track, 104433 cylinders, total 1677721600 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/mapper/vg00-var doesn't contain a valid partition table
Disk /dev/mapper/vg00-home: 6442 MB, 6442450944 bytes
255 heads, 63 sectors/track, 783 cylinders, total 12582912 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/mapper/vg00-home doesn't contain a valid partition table
So I thought maybe I just need to add the partitions of the new drive to the correct arrays. But there is nothing in [login to view URL]
Please help. All my clients websites were on here and I have no backup.
Thanks.
Hi, i have experience in RAID and software raid technology. within one to two hours i can bring back your second disk in raid. let me know what you think.