Hello All,
on a Centos5 system installed with software raid I'm getting:
raid1: raid set md127 active with 2 out of 2 mirrors
md:.... autorun DONE
md: Autodetecting RAID arrays
md: autorun.....
md : autorun DONE
trying to resume form /dev/md1
creating root device
mounting root device
mounting root filesystem
ext3-fs : unable to read superblock
mount : error mounting /dev/root on /sysroot as ext3: invalid argument
setting up other filesystems.7
setting up new root fs
setuproot: moving /dev failed : no such file of directory
no fstab.sys, mounting internal defaults
setuproot : error mounting /proc : no such file or directory
setuproot: error mounting /sys : No such file of directory
Switching to new root and running init
unmounting old /dev
unmounting old /proc
unmounting old /sys
switchroot : mount failed : No such file of directory
kernel panic - not syncing : Attempted to kill init!
Now I'm trying to boot into rescue mode from a Centos dvd, at the end of the Anaconda sequence I get:
no linux partitions found.
at the command prompt, fdisk -l gives me:
/dev/sdb1*
/dev/sdb2
/dev/sdb3
/dev/sda1*
/dev/sda2
/dev/sda3
I'm not sure where to go from here.
I try chrooting as described here :http://wiki.centos.org/HowTos/Install_On_Partitionable_RAID1
but chrooting always fails with:
chroot : failed to run command ' /usr/bin/bash" : no such file or directory.
Any help would be deeply appreciated.
greetings, Johan
On Tue, 2015-03-17 at 23:28 +0100, johan.vermeulen7@telenet.be wrote:
on a Centos5 system installed with software raid I'm getting:
raid1: raid set md127 active with 2 out of 2 mirrors
md:.... autorun DONE
md: Autodetecting RAID arrays
md: autorun.....
md : autorun DONE
trying to resume form /dev/md1
Hi Johan,
Your system is assembling md127, but is apparently expecting md1.
I suspect that you examined the raid1 from a previously working EL5 system using a more-recent-than-EL5 LiveDVD, which assembled the raid1 as md127 and wrote super-minor 127 to the raid1 (assuming ver. 0.90 metadata). When started under EL5, it then assembled as md127, not md1, hence the problem.
If that is what happened, then boot the system with the same LiveDVD, stop the raid and then assemble it as md1 while updating the super-minor. (You might want to mount the installation and look at fstab and grub.conf while running the LiveDVD to verify that it is looking for md1).
For example (assuming md1 contained partitions sda1 and sdb1):
- (Boot using the LiveDVD)
- (Unmount anything from md127 > # df -h)
- (Inactivate any VGs/LVs > # vgchange -an <VG> or lvchange -an <LV>)
# mdadm -S /dev/md127
# mdadm -A /dev/md1 -U super-minor /dev/sd[ab]1
Then shut down the LiveDVD and attempt to boot the system under EL5.
Steve
PS I don't watch EL5 boot very often/recently, so I might have misses something relevant in your post.
On Tue, 2015-03-17 at 20:20 -0400, S.Tindall wrote:
On Tue, 2015-03-17 at 23:28 +0100, johan.vermeulen7@telenet.be wrote:
on a Centos5 system installed with software raid I'm getting:
raid1: raid set md127 active with 2 out of 2 mirrors
md:.... autorun DONE
md: Autodetecting RAID arrays
md: autorun.....
md : autorun DONE
trying to resume form /dev/md1
Hi Johan,
Your system is assembling md127, but is apparently expecting md1.
I suspect that you examined the raid1 from a previously working EL5 system using a more-recent-than-EL5 LiveDVD, which assembled the raid1 as md127 and wrote super-minor 127 to the raid1 (assuming ver. 0.90 metadata). When started under EL5, it then assembled as md127, not md1, hence the problem.
If that is what happened, then boot the system with the same LiveDVD, stop the raid and then assemble it as md1 while updating the super-minor. (You might want to mount the installation and look at fstab and grub.conf while running the LiveDVD to verify that it is looking for md1).
For example (assuming md1 contained partitions sda1 and sdb1):
- (Boot using the LiveDVD)
I forgot (at least) one thing:
- (Stop md127-based swap > # swapoff -a )
(Unmount anything from md127 > # df -h)
(Inactivate any VGs/LVs > # vgchange -an <VG> or lvchange -an <LV>)
# mdadm -S /dev/md127
# mdadm -A /dev/md1 -U super-minor /dev/sd[ab]1
Then shut down the LiveDVD and attempt to boot the system under EL5.
Steve
PS I don't watch EL5 boot very often/recently, so I might have misses something relevant in your post.
CentOS mailing list CentOS@centos.org http://lists.centos.org/mailman/listinfo/centos
----- Oorspronkelijk bericht ----- Van: "S.Tindall" tindall.satwth@brandxmail.com Aan: "CentOS mailing list" centos@centos.org Verzonden: Woensdag 18 maart 2015 01:20:47 Onderwerp: Re: [CentOS] unable to recover software raid1 install
On Tue, 2015-03-17 at 23:28 +0100, johan.vermeulen7@telenet.be wrote:
on a Centos5 system installed with software raid I'm getting:
raid1: raid set md127 active with 2 out of 2 mirrors
md:.... autorun DONE
md: Autodetecting RAID arrays
md: autorun.....
md : autorun DONE
trying to resume form /dev/md1
Hi Johan,
Your system is assembling md127, but is apparently expecting md1.
I suspect that you examined the raid1 from a previously working EL5 system using a more-recent-than-EL5 LiveDVD, which assembled the raid1 as md127 and wrote super-minor 127 to the raid1 (assuming ver. 0.90 metadata). When started under EL5, it then assembled as md127, not md1, hence the problem.
If that is what happened, then boot the system with the same LiveDVD, stop the raid and then assemble it as md1 while updating the super-minor. (You might want to mount the installation and look at fstab and grub.conf while running the LiveDVD to verify that it is looking for md1).
For example (assuming md1 contained partitions sda1 and sdb1):
- (Boot using the LiveDVD)
- (Unmount anything from md127 > # df -h)
- (Inactivate any VGs/LVs > # vgchange -an <VG> or lvchange -an <LV>)
# mdadm -S /dev/md127
# mdadm -A /dev/md1 -U super-minor /dev/sd[ab]1
Then shut down the LiveDVD and attempt to boot the system under EL5.
Steve
PS I don't watch EL5 boot very often/recently, so I might have misses something relevant in your post.
Steve,
thanks for the replies. I do use a centos6 livecd, and that might very well cause the confusion.
In the end, I was able to pull the data off the machine using Parted Magic, after spending a lot of time trying to chroot into the machine.
It was the only Centos5 I had and I'l replace it with Centos7, if I can get that to work.
greetings, Johan
_______________________________________________ CentOS mailing list CentOS@centos.org http://lists.centos.org/mailman/listinfo/centos
-
johan.vermeulen7＠telenet.be -
S.Tindall