Hi
I have setup software RAID two years ago using FC3 using the graphical installer (RAID1). In the mean time I installed CENTOS4.5 and everything is running fine. At least that was my perception. It now turns out that raid is not working and that LVS just finds 4 partitions from four disks and that's it.:
/dev/sda2 VolGroup00 lvm2 a- 94.88G 0 /dev/sdb1 VolGroup00 lvm2 a- 94.94G 10.00G /dev/sdc1 VolGroup00 lvm2 a- 94.94G 74.94G /dev/sdd1 VolGroup00 lvm2 a- 94.94G 70.81G
These are 4 disk of each 200GB, and the disks have these partitions:
Using /dev/sda (parted) print Disk geometry for /dev/sda: 0.000-194481.000 megabytes Disk label type: msdos Minor Start End Type Filesystem Flags 1 0.031 101.975 primary ext3 boot 2 101.975 97284.243 primary lvm 3 97284.243 194474.355 primary raid Disk geometry for /dev/sdb: 0.000-194481.000 megabytes Disk label type: msdos Minor Start End Type Filesystem Flags 1 0.031 97237.177 primary boot, lvm 2 97237.178 194474.355 primary raid Disk geometry for /dev/sdc: 0.000-194481.000 megabytes Disk label type: msdos Minor Start End Type Filesystem Flags 1 0.031 97237.177 primary boot, lvm 2 97237.178 194474.355 primary raid Disk geometry for /dev/sdd: 0.000-194481.000 megabytes Disk label type: msdos Minor Start End Type Filesystem Flags 1 0.031 97237.177 primary boot, lvm 2 97237.178 194474.355 primary raid
So my feeling is that I need to setup the RAID again, but I don't want to make any mistakes here, since this is a live system working fine. I tried to read the mdadm manual but it's not quit clear to me what to do. # mdadm -A --scan -v mdadm: No arrays found in config file
Shows I have to do more. The previous fedora installation is still around, but is doesn't contain a /etc/mdadm.conf file.
Can anyone help me with some steps to take to get it running again. I do have backups, but if things go wrong restoring takes several hours.
Thanks, Theo
PS. Send for the third time. Could it be that posting is limited to email addresses that are subscribed to the list?
Find out what disk belongs to which md-set and try the --assemble option..
This should fix it, I think
Theo Band wrote:
Hi
I have setup software RAID two years ago using FC3 using the graphical installer (RAID1). In the mean time I installed CENTOS4.5 and everything is running fine. At least that was my perception. It now turns out that raid is not working and that LVS just finds 4 partitions from four disks and that's it.:
/dev/sda2 VolGroup00 lvm2 a- 94.88G 0 /dev/sdb1 VolGroup00 lvm2 a- 94.94G 10.00G /dev/sdc1 VolGroup00 lvm2 a- 94.94G 74.94G /dev/sdd1 VolGroup00 lvm2 a- 94.94G 70.81G
These are 4 disk of each 200GB, and the disks have these partitions:
Using /dev/sda (parted) print Disk geometry for /dev/sda: 0.000-194481.000 megabytes Disk label type: msdos Minor Start End Type Filesystem Flags 1 0.031 101.975 primary ext3 boot 2 101.975 97284.243 primary lvm 3 97284.243 194474.355 primary raid Disk geometry for /dev/sdb: 0.000-194481.000 megabytes Disk label type: msdos Minor Start End Type Filesystem Flags 1 0.031 97237.177 primary boot, lvm 2 97237.178 194474.355 primary raid Disk geometry for /dev/sdc: 0.000-194481.000 megabytes Disk label type: msdos Minor Start End Type Filesystem Flags 1 0.031 97237.177 primary boot, lvm 2 97237.178 194474.355 primary raid Disk geometry for /dev/sdd: 0.000-194481.000 megabytes Disk label type: msdos Minor Start End Type Filesystem Flags 1 0.031 97237.177 primary boot, lvm 2 97237.178 194474.355 primary raid
So my feeling is that I need to setup the RAID again, but I don't want to make any mistakes here, since this is a live system working fine. I tried to read the mdadm manual but it's not quit clear to me what to do. # mdadm -A --scan -v mdadm: No arrays found in config file
Shows I have to do more. The previous fedora installation is still around, but is doesn't contain a /etc/mdadm.conf file.
Can anyone help me with some steps to take to get it running again. I do have backups, but if things go wrong restoring takes several hours.
Thanks, Theo
PS. Send for the third time. Could it be that posting is limited to email addresses that are subscribed to the list? _______________________________________________ CentOS mailing list CentOS@centos.org http://lists.centos.org/mailman/listinfo/centos
# mdadm -Q /dev/sda /dev/sda: is not an md array /dev/sda: No md super block found, not an md component. # mdadm -Q /dev/sda1 /dev/sda1: is not an md array /dev/sda1: No md super block found, not an md component. # mdadm -Q /dev/sda2 /dev/sda2: is not an md array
So it looks like all info is lost. Can I create a new array with the existing LVM partitions and the free partitions without destroying any data?
Thanks, Theo Centos wrote:
Find out what disk belongs to which md-set and try the --assemble option..
This should fix it, I think
Theo Band wrote:
Hi
I have setup software RAID two years ago using FC3 using the graphical installer (RAID1). In the mean time I installed CENTOS4.5 and everything is running fine. At least that was my perception. It now turns out that raid is not working and that LVS just finds 4 partitions from four disks and that's it.:
/dev/sda2 VolGroup00 lvm2 a- 94.88G 0 /dev/sdb1 VolGroup00 lvm2 a- 94.94G 10.00G /dev/sdc1 VolGroup00 lvm2 a- 94.94G 74.94G /dev/sdd1 VolGroup00 lvm2 a- 94.94G 70.81G
These are 4 disk of each 200GB, and the disks have these partitions:
Using /dev/sda (parted) print Disk geometry for /dev/sda: 0.000-194481.000 megabytes Disk label type: msdos Minor Start End Type Filesystem Flags 1 0.031 101.975 primary ext3 boot 2 101.975 97284.243 primary lvm 3 97284.243 194474.355 primary raid Disk geometry for /dev/sdb: 0.000-194481.000 megabytes Disk label type: msdos Minor Start End Type Filesystem Flags 1 0.031 97237.177 primary boot, lvm 2 97237.178 194474.355 primary raid Disk geometry for /dev/sdc: 0.000-194481.000 megabytes Disk label type: msdos Minor Start End Type Filesystem Flags 1 0.031 97237.177 primary boot, lvm 2 97237.178 194474.355 primary raid Disk geometry for /dev/sdd: 0.000-194481.000 megabytes Disk label type: msdos Minor Start End Type Filesystem Flags 1 0.031 97237.177 primary boot, lvm 2 97237.178 194474.355 primary raid
So my feeling is that I need to setup the RAID again, but I don't want to make any mistakes here, since this is a live system working fine. I tried to read the mdadm manual but it's not quit clear to me what to do. # mdadm -A --scan -v mdadm: No arrays found in config file
Shows I have to do more. The previous fedora installation is still around, but is doesn't contain a /etc/mdadm.conf file.
Can anyone help me with some steps to take to get it running again. I do have backups, but if things go wrong restoring takes several hours.
Thanks, Theo
PS. Send for the third time. Could it be that posting is limited to email addresses that are subscribed to the list? _______________________________________________ CentOS mailing list CentOS@centos.org http://lists.centos.org/mailman/listinfo/centos
CentOS mailing list CentOS@centos.org http://lists.centos.org/mailman/listinfo/centos
on 10/7/2007 2:41 PM Theo Band spake the following:
# mdadm -Q /dev/sda /dev/sda: is not an md array /dev/sda: No md super block found, not an md component. # mdadm -Q /dev/sda1 /dev/sda1: is not an md array /dev/sda1: No md super block found, not an md component. # mdadm -Q /dev/sda2 /dev/sda2: is not an md array
So it looks like all info is lost. Can I create a new array with the existing LVM partitions and the free partitions without destroying any data?
Your raid appears to be on /dev/sda3 /dev/sdb2 /dev/sdc2 /dev/sdd2 Try mdadm --examine --brief --scan --config=partitions and see if it sees anything.
Scott Silva wrote:
on 10/7/2007 2:41 PM Theo Band spake the following:
# mdadm -Q /dev/sda /dev/sda: is not an md array /dev/sda: No md super block found, not an md component. # mdadm -Q /dev/sda1 /dev/sda1: is not an md array /dev/sda1: No md super block found, not an md component. # mdadm -Q /dev/sda2 /dev/sda2: is not an md array
So it looks like all info is lost. Can I create a new array with the existing LVM partitions and the free partitions without destroying any data?
Your raid appears to be on /dev/sda3 /dev/sdb2 /dev/sdc2 /dev/sdd2 Try mdadm --examine --brief --scan --config=partitions and see if it sees anything.
# mdadm --examine --brief --scan --config=partitions
Nothing.... Indeed these are the partitions that are now unused and used to be part of the raid. Any idea what could have gone wrong when I migrated to from FC3 to Centos? I also changed the mobo of this machine and changed the CPU from single to a dual core one. I assume support is in the kernel, so no special actions should be needed to get this to work during boot up.
Theo
on 10/7/2007 10:40 PM Theo Band spake the following:
Scott Silva wrote:
on 10/7/2007 2:41 PM Theo Band spake the following:
# mdadm -Q /dev/sda /dev/sda: is not an md array /dev/sda: No md super block found, not an md component. # mdadm -Q /dev/sda1 /dev/sda1: is not an md array /dev/sda1: No md super block found, not an md component. # mdadm -Q /dev/sda2 /dev/sda2: is not an md array
So it looks like all info is lost. Can I create a new array with the existing LVM partitions and the free partitions without destroying any data?
Your raid appears to be on /dev/sda3 /dev/sdb2 /dev/sdc2 /dev/sdd2 Try mdadm --examine --brief --scan --config=partitions and see if it sees anything.
# mdadm --examine --brief --scan --config=partitions
Nothing.... Indeed these are the partitions that are now unused and used to be part of the raid. Any idea what could have gone wrong when I migrated to from FC3 to Centos? I also changed the mobo of this machine and changed the CPU from single to a dual core one. I assume support is in the kernel, so no special actions should be needed to get this to work during boot up.
Theo
When you upgraded you might have formatted the partitions accidentally. If there is no raid data there, you can try something like testdisk to see if you can recover it, but chances are that your data is gone.
Scott Silva wrote:
on 10/7/2007 10:40 PM Theo Band spake the following:
Scott Silva wrote:
on 10/7/2007 2:41 PM Theo Band spake the following:
# mdadm -Q /dev/sda /dev/sda: is not an md array /dev/sda: No md super block found, not an md component. # mdadm -Q /dev/sda1 /dev/sda1: is not an md array /dev/sda1: No md super block found, not an md component. # mdadm -Q /dev/sda2 /dev/sda2: is not an md array
So it looks like all info is lost. Can I create a new array with the existing LVM partitions and the free partitions without destroying any data?
Your raid appears to be on /dev/sda3 /dev/sdb2 /dev/sdc2 /dev/sdd2 Try mdadm --examine --brief --scan --config=partitions and see if it sees anything.
# mdadm --examine --brief --scan --config=partitions
Nothing.... Indeed these are the partitions that are now unused and used to be part of the raid. Any idea what could have gone wrong when I migrated to from FC3 to Centos? I also changed the mobo of this machine and changed the CPU from single to a dual core one. I assume support is in the kernel, so no special actions should be needed to get this to work during boot up.
Theo
When you upgraded you might have formatted the partitions accidentally. If there is no raid data there, you can try something like testdisk to see if you can recover it, but chances are that your data is gone.
No I did not format the disk. All data was present, but by LVM. Every disk has two partitions, one unused and one added to a volume group.
Just after I send the previous mail, I moved the two physical disks out of the volume group (pvmove). The first disk went OK, just in the middle of the move of the second disk I got a kernel panic. I was not able to boot anymore. Even a rescue Centos4.4 CD did not work. As soon as it started to look for existing installation it gave the same kernel panic. And this was on a live system, with everyone looking over my shoulder :-( Nice moment to try whether the backup server would work. (And it did, of course :-)
I could solve the kernel panic by booting a FC7 live CD later on. It just found the Volume group still with four physical disk partitions in it. No extends were present on the two disk that I wanted to pull out of the group. Using the lvm tools on the FC7 CD I was able to finish the job. I installed FC7 using RAID1 on the two removed disks. After that I booted in FC7 and copied my centos installation from the two old volume group to the new raid1. After some fiddling with mkinitrd, I got is to boot Centos4.5 from the RAID1 created by FC7.
So I expect a problem to exist with LVM and the kernel I'm using (2.6.9-55.0.6.ELsmp)
-
Centos -
Scott Silva -
Theo Band