I am hoping this is an acceptable forum to put this, i wasn't sure.
I have a Centos 5 system that i must have removed the partitions from. I was trying to partition a 4tb externally docked drive with GParted in a single large slice. When i went back in i noticed the drive designations were different. GParted named the external SDA instead of the SDC i was seeing from the OS cmd line. The hardware is a Dell R415 with 4 drives. They were initially raided but the raid groups seem to have been broken.
the kickstart config that was used is:
Code:
zerombr
clearpart --all --initlabel
partition raid.11 --size 300 --ondisk=sda
partition raid.21 --size 300 --ondisk=sdb
partition raid.12 --size 3072 --ondisk=sda
partition raid.22 --size 3072 --ondisk=sdb
partition raid.13 --size 1 --grow --ondisk=sda
partition raid.23 --size 1 --grow --ondisk=sdb
raid /boot --fstype ext3 --device md0 --level=RAID1 raid.11 raid.21
raid swap --fstype swap --device md1 --level=RAID0 raid.12 raid.22
raid pv.2 --fstype ext3 --device md2 --level=RAID0 raid.13 raid.23
volgroup VolGroup00 pv.2
logvol / -name=rootVol --vgname=VolGroup00 --size=12288
logvol /home --name=homeVol --vgname=VolGroup00 --size=30720
logvol /var --name=varVol --vgname=VolGroup00 --size=1 --grow
bootloader --location=mbr --driveorder=sda --append"rhgb quiet" --md5pass=gobbledegook
When trying to boot this system it drops into single user after erroring on /dev/md0 not having a superblock. The root partition is mounted ro so i remount rw. I ran mdadm commands to look at the md status
Code:
# mdadm --examine --scan
ARRAY /dev/md125 level=raid1 num-devices=2 UUID=6cd392e5:8f96b985:205f94ef:0446cbfa
ARRAY /dev/md1 level=raid0 num-devices=2 UUID=a8091a34:8c73f754:a4a39adc:dae395e4
ARRAY /dev/md2 level=raid0 num-devices=2 UUID=ec57b79e:a621d9c3:8d9d1259:738a2a00
# mdadm --detail --scan
ARRAY /dev/md2 level=raid0 num-devices=2 metadata=0.90 UUID=ec57b79e:a621d9c3:8d9d1259:738a2a00
ARRAY /dev/md1 level=raid0 num-devices=2 metadata=0.90 UUID=a8091a34:8c73f754:a4a39adc:dae395e4
ARRAY /dev/md125 level=raid1 num-devices=2 metadata=0.90 UUID=6cd392e5:8f96b985:205f94ef:0446cbfa
ARRAY /dev/md124 level=raid1 num-devices=2 metadata=0.90 UUID=6cd392e5:8f96b985:205f94ef:0446cbfa
# more /proc/mdstat
Personalities : [raid0] [raid1]
md124 : active raid1 sda1[0]
305088 blocks [2/1] [U_]
md125 : active raid1 sdb1[1]
305088 blocks [2/1] [_U]
md1 : active raid0 sdb2[1] sda2[0]
6297088 blocks 256k chunks
md2 : active raid0 sdb3[1] sda3[0]
480150528 blocks 256k chunks
unused devices: <none>
# more /etc/mdadm.conf
ARRAY /dev/md0 level=raid1 num-devices=2 uuid=6cd392e5:8f96b985:205f94ef:0446cbfa
ARRAY /dev/md1 level=raid0 num-devices=2 uuid=a8091a34:8c73f754:a4a39adc:dae395e4
ARRAY /dev/md2 level=raid0 num-devices=2 uuid=ec57b79e:a621d9c3:8d9d1259:738a2a00
I know i'm including a lot of data but i'm not sure what will help. Here is the results of an fdisk -l
Code:
#fdisk -l
Disk /dev/sda: 249.3 GB, 249376538624 bytes
255 heads, 63 sectors/track, 30318 cylinders
Units = cylinders of 16065 * 512 = 8225280 bytes
Device Boot Start End Blocks Id System
/dev/sda1 * 1 38 305203+ fd Linux raid autodetect
/dev/sda2 39 430 3148740 fd Linux raid autodetect
/dev/sda3 431 30318 240075360 fd Linux raid autodetect
Disk /dev/sdb: 249.3 GB, 249376538624 bytes
255 heads, 63 sectors/track, 30318 cylinders
Units = cylinders of 16065 * 512 = 8225280 bytes
Device Boot Start End Blocks Id System
/dev/sdb1 * 1 38 305203+ fd Linux raid autodetect
/dev/sdb2 39 430 3148740 fd Linux raid autodetect
/dev/sdb3 431 30318 240075360 fd Linux raid autodetect
Disk /dev/md2: 491.6 GB, 491674140672 bytes
2 heads, 4 sectors/track, 120037632 cylinders
Units = cylinders of 8 * 512 = 4096 bytes
Disk /dev/md2 doesn't contain a valid partition table
Disk /dev/md1: 6448 MB, 6448218112 bytes
2 heads, 4 sectors/track, 1574272 cylinders
Units = cylinders of 8 * 512 = 4096 bytes
Disk /dev/md1 doesn't contain a valid partition table
Disk /dev/md125: 312 MB, 312410112 bytes
2 heads, 4 sectors/track, 76272 cylinders
Units = cylinders of 8 * 512 = 4096 bytes
Disk /dev/md125 doesn't contain a valid partition table
Disk /dev/md124: 312 MB, 312410112 bytes
2 heads, 4 sectors/track, 76272 cylinders
Units = cylinders of 8 * 512 = 4096 bytes
Disk /dev/md124 doesn't contain a valid partition table
The system will somehow boot into init 5 after i have made the root partition writeable even though there is NOT anything in /boot. No files at all. I'm hoping to find how to reset the raid groups and partitions without having to start from scratch (i have all the data off of it that i need, but want to learn).
So is this recoverable or not?
