Hello.
I am trying to boot CentOS 4 from a copy of an ext3 software RAID 1 filesystem (md) which has been copied to a normal ext3 filesystem (hd). I am almost getting there, exept that the system hangs after booting the kernel. I copied the datas from the /boot and / partitions to two similar partitions on the backuped disk with mirrordir (can also be done with cp or dd). I have setup the new disk with grub and I can reach the grub stage 2. It will also boot the kernel properly, but it will hang during the SElinux initialisation (which is disabled). I don't know exactly if it's a mount or SElinux problem. Also, it seems that the raid device is trying to be initialised, and I don't have an md but an hd on that drive. This comes probably from the original setup.
My question is: does somebody know how I can change that behaviour and let linux mount the hd instead of the md coming from the original ? Do I need to boot another vmlinuz image or another initrd for it to work properly ? In this case, how could I generate those new images ?
The output of the boot sequence is the following:
Mounting sysfs Creating /dev Starting udev Loading raid1.ko module md: raid1 personnality registered as nr 3 Loading jbd.ko module Loading ext3.ko module md: Autodetecting RAID arrays. md: autorun ... md: ... autorun DONE. md: Autodetecting RAID arrays. md: autorun ... md: ... autorun DONE. md: Autodetecting RAID arrays. md: autorun ... md: ... autorun DONE. Creating root device Mounting root filesystem kjournald starting. Commit interval 5 seconds EXT3-fs: mounted filesystem with ordered data mode. mount: error 2 mounting none Switching to new root SElinux: Disabled at runtime SElinux: Unregistering netfilter hooks
Then, it hangs here undefinitely.
Here is my menu.lst grub file on the backup disk I want to boot from: default=0 timeout=5 splashimage=(hd0,0)/grub/splash.xpm.gz hiddenmenu title CentOS (2.6.9-11.106.unsupported) root (hd0,0) kernel /vmlinuz-2.6.9-11.106.unsupported root=/dev/hda3 initrd /initrd-2.6.9-11.106.unsupported.img
Here is it's fstab: none /dev/pts devpts gid=5,mode=620 0 0 none /dev/shm tmpfs defaults 0 0 none /proc proc defaults 0 0 none /sys sysfs defaults 0 0 /dev/hda1 /boot ext3 defaults 0 0 /dev/hda2 swap swap defaults 0 0 /dev/hda3 / ext3 defaults 0 0 /dev/fd0 /media/floppy auto pamconsole,exec,noauto,managed 0 0
Any help is greatly appreciated.
Thanks, Daniel
On Sat, 2005-09-24 at 14:20 +0200, dan1 wrote:
Hello.
I am trying to boot CentOS 4 from a copy of an ext3 software RAID 1 filesystem (md) which has been copied to a normal ext3 filesystem (hd). I am almost getting there, exept that the system hangs after booting the kernel. I copied the datas from the /boot and / partitions to two similar partitions on the backuped disk with mirrordir (can also be done with cp or dd). I have setup the new disk with grub and I can reach the grub stage 2. It will also boot the kernel properly, but it will hang during the SElinux initialisation (which is disabled). I don't know exactly if it's a mount or SElinux problem. Also, it seems that the raid device is trying to be initialised, and I don't have an md but an hd on that drive. This comes probably from the original setup.
My question is: does somebody know how I can change that behaviour and let linux mount the hd instead of the md coming from the original ? Do I need to boot another vmlinuz image or another initrd for it to work properly ? In this case, how could I generate those new images ?
The output of the boot sequence is the following:
Mounting sysfs Creating /dev Starting udev Loading raid1.ko module md: raid1 personnality registered as nr 3 Loading jbd.ko module Loading ext3.ko module md: Autodetecting RAID arrays. md: autorun ... md: ... autorun DONE. md: Autodetecting RAID arrays. md: autorun ... md: ... autorun DONE. md: Autodetecting RAID arrays. md: autorun ... md: ... autorun DONE. Creating root device Mounting root filesystem kjournald starting. Commit interval 5 seconds EXT3-fs: mounted filesystem with ordered data mode. mount: error 2 mounting none Switching to new root SElinux: Disabled at runtime SElinux: Unregistering netfilter hooks
Then, it hangs here undefinitely.
Here is my menu.lst grub file on the backup disk I want to boot from: default=0 timeout=5 splashimage=(hd0,0)/grub/splash.xpm.gz hiddenmenu title CentOS (2.6.9-11.106.unsupported) root (hd0,0) kernel /vmlinuz-2.6.9-11.106.unsupported root=/dev/hda3 initrd /initrd-2.6.9-11.106.unsupported.img
Here is it's fstab: none /dev/pts devpts gid=5,mode=620 0 0 none /dev/shm tmpfs defaults 0 0 none /proc proc defaults 0 0 none /sys sysfs defaults 0 0 /dev/hda1 /boot ext3 defaults 0 0 /dev/hda2 swap swap defaults 0 0 /dev/hda3 / ext3 defaults 0 0 /dev/fd0 /media/floppy auto pamconsole,exec,noauto,managed 0 0
Any help is greatly appreciated.
You could try booting the machine to single user mode. Interrupt the boot at grub, use 'e' for edit, go to the kernel line, hit 'e', add an s on the end of the line and hit 'b' to boot. if you can get to single user mode, then you can try working your way through the various start up scripts to see what is causing the problem.
Good luck.
You could try booting the machine to single user mode. Interrupt the boot at grub, use 'e' for edit, go to the kernel line, hit 'e', add an s on the end of the line and hit 'b' to boot. if you can get to single user mode, then you can try working your way through the various start up scripts to see what is causing the problem.
Good luck.
-- Sean
Hello, Sean. Thanks for replying. I tried your suggestion, but it can't even start linux in single mode. I think that there is a mount problem, but I have double checked the fstab file seated on the backup drive and it seems fine to me. Therefore I can't understand what prevents the mount to be made properly. Would the vmlinuz or initrd images be dependent of the md or hd filesystem type or are they exactly the same for both ? Else what other file should I touch that involves the mounting operation ?
Thanks, Daniel
On Mon, 2005-09-26 at 16:14, dan1 wrote:
I tried your suggestion, but it can't even start linux in single mode. I think that there is a mount problem, but I have double checked the fstab file seated on the backup drive and it seems fine to me. Therefore I can't understand what prevents the mount to be made properly. Would the vmlinuz or initrd images be dependent of the md or hd filesystem type or are they exactly the same for both ? Else what other file should I touch that involves the mounting operation ?
If you boot the install CD in rescue mode, does it find the installed system correctly and mount it under /mnt/sysimage? You mentioned an attempt to set up md devices before - are the partition types set to ext3 in fdisk? Are you sure you have the correct contents in /boot/grub/grub.conf (the one in /etc is a symlink that can be broken if things aren't mounted as expected when you modify it).
I tried your suggestion, but it can't even start linux in single mode. I think that there is a mount problem, but I have double checked the fstab file seated on the backup drive and it seems fine to me. Therefore I can't understand what prevents the mount to be made properly. Would the vmlinuz or initrd images be dependent of the md or hd filesystem type or are they exactly the same for both ? Else what other file should I touch that involves the mounting operation ?
If you boot the install CD in rescue mode, does it find the installed system correctly and mount it under /mnt/sysimage? You mentioned an attempt to set up md devices before - are the partition types set to ext3 in fdisk? Are you sure you have the correct contents in /boot/grub/grub.conf (the one in /etc is a symlink that can be broken if things aren't mounted as expected when you modify it).
-- Les Mikesell lesmikesell@gmail.com
Hello, Les.
Yes, I can run linux in rescue mode with the CD and see the correct root partition. I have also checked the contents of the /boot/grub/grub.conf and it is ok. In fstab I have also put ext3 for that backup disk. below are my important files on the backup disk:
The output of the boot sequence output is the following:
Mounting sysfs Creating /dev Starting udev Loading raid1.ko module md: raid1 personnality registered as nr 3 Loading jbd.ko module Loading ext3.ko module md: Autodetecting RAID arrays. md: autorun ... md: ... autorun DONE. md: Autodetecting RAID arrays. md: autorun ... md: ... autorun DONE. md: Autodetecting RAID arrays. md: autorun ... md: ... autorun DONE. Creating root device Mounting root filesystem kjournald starting. Commit interval 5 seconds EXT3-fs: mounted filesystem with ordered data mode. mount: error 2 mounting none Switching to new root SElinux: Disabled at runtime SElinux: Unregistering netfilter hooks
Then, it hangs here undefinitely.
Here is my menu.lst grub file on the backup disk I want to boot from: default=0 timeout=5 splashimage=(hd0,0)/grub/splash.xpm.gz hiddenmenu title CentOS (2.6.9-11.106.unsupported) root (hd0,0) kernel /vmlinuz-2.6.9-11.106.unsupported root=/dev/hda3 initrd /initrd-2.6.9-11.106.unsupported.img
Here is it's fstab: none /dev/pts devpts gid=5,mode=620 0 0 none /dev/shm tmpfs defaults 0 0 none /proc proc defaults 0 0 none /sys sysfs defaults 0 0 /dev/hda1 /boot ext3 defaults 0 0 /dev/hda2 swap swap defaults 0 0 /dev/hda3 / ext3 defaults 0 0 /dev/fd0 /media/floppy auto pamconsole,exec,noauto,managed 0 0
Thanks for any idea !
Regards, Daniel
On Tue, 2005-09-27 at 07:49 +0200, dan1 wrote:
I tried your suggestion, but it can't even start linux in single mode. I think that there is a mount problem, but I have double checked the fstab file seated on the backup drive and it seems fine to me. Therefore I can't understand what prevents the mount to be made properly. Would the vmlinuz or initrd images be dependent of the md or hd filesystem type or are they exactly the same for both ? Else what other file should I touch that involves the mounting operation ?
If you boot the install CD in rescue mode, does it find the installed system correctly and mount it under /mnt/sysimage? You mentioned an attempt to set up md devices before - are the partition types set to ext3 in fdisk? Are you sure you have the correct contents in /boot/grub/grub.conf (the one in /etc is a symlink that can be broken if things aren't mounted as expected when you modify it).
-- Les Mikesell lesmikesell@gmail.com
Hello, Les.
Yes, I can run linux in rescue mode with the CD and see the correct root partition. I have also checked the contents of the /boot/grub/grub.conf and it is ok. In fstab I have also put ext3 for that backup disk. below are my important files on the backup disk:
The output of the boot sequence output is the following:
Mounting sysfs Creating /dev Starting udev Loading raid1.ko module md: raid1 personnality registered as nr 3 Loading jbd.ko module Loading ext3.ko module md: Autodetecting RAID arrays. md: autorun ... md: ... autorun DONE. md: Autodetecting RAID arrays. md: autorun ... md: ... autorun DONE. md: Autodetecting RAID arrays. md: autorun ... md: ... autorun DONE. Creating root device Mounting root filesystem kjournald starting. Commit interval 5 seconds EXT3-fs: mounted filesystem with ordered data mode. mount: error 2 mounting none Switching to new root SElinux: Disabled at runtime SElinux: Unregistering netfilter hooks
Then, it hangs here undefinitely.
Here is my menu.lst grub file on the backup disk I want to boot from: default=0 timeout=5 splashimage=(hd0,0)/grub/splash.xpm.gz hiddenmenu title CentOS (2.6.9-11.106.unsupported) root (hd0,0) kernel /vmlinuz-2.6.9-11.106.unsupported root=/dev/hda3 initrd /initrd-2.6.9-11.106.unsupported.img
Here is it's fstab: none /dev/pts devpts gid=5,mode=620 0 0 none /dev/shm tmpfs defaults 0 0 none /proc proc defaults 0 0 none /sys sysfs defaults 0 0 /dev/hda1 /boot ext3 defaults 0 0 /dev/hda2 swap swap defaults 0 0 /dev/hda3 / ext3 defaults 0 0 /dev/fd0 /media/floppy auto pamconsole,exec,noauto,managed 0 0
Thanks for any idea !
Daniel-
One more thought, what is in /boot/grub/device.map? You may need to boot into the rescue mode
chroot /mnt/sysimage edit /boot/grub/device.map so that (hd0) is /dev/hda and then run
grub-install /dev/hda
On Tue, 2005-09-27 at 00:49, dan1 wrote:
If you boot the install CD in rescue mode, does it find the installed system correctly and mount it under /mnt/sysimage?
Yes, I can run linux in rescue mode with the CD and see the correct root partition.
That's not quite what I asked... Does the rescue mode boot automatically mount / under /mnt/sysimage and /boot in it's corresponding place? Does everything look right if you chroot /mnt/sysimage?
What does fdisk -l show?
On 26/09/05, dan1 dan1@edenpics.com wrote:
You could try booting the machine to single user mode. Interrupt the boot at grub, use 'e' for edit, go to the kernel line, hit 'e', add an s on the end of the line and hit 'b' to boot. if you can get to single user mode, then you can try working your way through the various start up scripts to see what is causing the problem.
Hello, Sean. Thanks for replying. I tried your suggestion, but it can't even start linux in single mode. I think that there is a mount problem, but I have double checked the fstab file seated on the backup drive and it seems fine to me. Therefore I can't understand what prevents the mount to be made properly. Would the vmlinuz or initrd images be dependent of the md or hd filesystem type or are they exactly the same for both ? Else what other file should I touch that involves the mounting operation ?
I had very similar symptoms a few weeks back setting up a system, check the archives for a thread titled "Boot/init problem with IBM Netfinity 4500".
In my case it actually turned out to be a hardware issue and reseating processors temporarily fixed it. The long-term fix appears to be to replace the VRM.
In your case, in /etc/fstab are you mounting by LABEL and are your partitions labelled as they should be according to fstab? You can use e2label to view/change partition labels.
Will.
-
dan1 -
Les Mikesell -
Sean O'Connell -
Will McDonald