Hi,
First some system details:
Epox EP-D3VA motherboard dual 1Ghz PIII processors 1.5GB RAM 2 x Promise SATA150 TX4 controllers 6 x Maxtor Maxline II 250GB SATA HDDs (3 per controller)
The drives are all partitioned identically with two partitions: 1.5GB + 248.5GB. The partitions are configured in raid arrays as follows:
/dev/md0: /dev/sd[ad]1 / (root filesystem) /dev/md1: /dev/sd[be]1 swap /dev/md2: /dev/sd[cf]1 swap /dev/md5: /dev/sd[abcdef]2 lvm2 volume
/home, /usr, and /var are mounted as lvm2 logical volumnes on the /dev/md5 array.
I was running FC2. I then decided to upgrade to FC3.
I booted from the DVD (the media check completed OK) and went through the system upgrade.
All seemed to go well and I rebooted.
However, the boot process halted with the following message:
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 EXT3-fs: unable to read superblock mount: error 22 mounting ext3 mount: error 2 mounting none Switching to new root switchroot: mount failed: 22 umount /initrd/dev failed: 2 Kernel panic - not syncing: Attempted to kill init!
This is with the default 2.6.9-1.667smp kernel.
I booted into rescue mode and chrooted into the upgraded system - all seems fine, i.e. all the filesystems are OK.
I then upgraded all the packages using "yum upgrade" within the chroot environment. This installed kernel-2.6.9-1.681_FC3smp.
I rebooted and got the same error as above. I also tried "downgrading" to a 2.6.8 kernel but got the same error.
Am I hitting the known bug [1] with SATA drives in the 2.6.9 kernel ? Or is this some other problem?
[1] https://bugzilla.redhat.com/bugzilla/show_bug.cgi?id=140367
Can anyone shed any light on this problem?
Thanks,
R.
On 12/2/2004 8:37 AM Robin Bowes wrote:
Hi,
First some system details:
Epox EP-D3VA motherboard dual 1Ghz PIII processors 1.5GB RAM 2 x Promise SATA150 TX4 controllers 6 x Maxtor Maxline II 250GB SATA HDDs (3 per controller)
The drives are all partitioned identically with two partitions: 1.5GB
- 248.5GB. The partitions are configured in raid arrays as follows:
/dev/md0: /dev/sd[ad]1 / (root filesystem) /dev/md1: /dev/sd[be]1 swap /dev/md2: /dev/sd[cf]1 swap /dev/md5: /dev/sd[abcdef]2 lvm2 volume
/home, /usr, and /var are mounted as lvm2 logical volumnes on the /dev/md5 array.
I was running FC2. I then decided to upgrade to FC3.
I booted from the DVD (the media check completed OK) and went through the system upgrade.
All seemed to go well and I rebooted.
However, the boot process halted with the following message:
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 EXT3-fs: unable to read superblock mount: error 22 mounting ext3 mount: error 2 mounting none Switching to new root switchroot: mount failed: 22 umount /initrd/dev failed: 2 Kernel panic - not syncing: Attempted to kill init!
This is with the default 2.6.9-1.667smp kernel.
I booted into rescue mode and chrooted into the upgraded system - all seems fine, i.e. all the filesystems are OK.
I then upgraded all the packages using "yum upgrade" within the chroot environment. This installed kernel-2.6.9-1.681_FC3smp.
I rebooted and got the same error as above. I also tried "downgrading" to a 2.6.8 kernel but got the same error.
Am I hitting the known bug [1] with SATA drives in the 2.6.9 kernel ? Or is this some other problem?
[1] https://bugzilla.redhat.com/bugzilla/show_bug.cgi?id=140367
Can anyone shed any light on this problem?
Look through the archives. I fixed it by building a new initrd file that included the driver for my SATA controller. I also noticed that my modprobe.conf file was missing things after upgrading, which might have been the original problem.
John Swartzentruber wrote:
Look through the archives.
I have - I can't find anything relevant. The archive search facility at redhat.com doesn't seem to return any useful results.
I fixed it by building a new initrd file that included the driver for my SATA controller.
Can you point me at any docs that guide me through this process?
I also noticed that my modprobe.conf file was missing things after upgrading, which might have been the original problem.
Such as? What should modprobe.conf look like? Mine just contains one line:
# Note: for use under 2.4, changes must also be made to modules.conf! alias char-major-89-* i2c-dev
However, there is a modprobe.conf.dist file which has 165 lines. Should I copy this to modprobe.conf?
R.
On 12/2/2004 9:50 AM Robin Bowes wrote:
John Swartzentruber wrote:
Look through the archives.
I have - I can't find anything relevant. The archive search facility at redhat.com doesn't seem to return any useful results.
You can search this newsgroup at http://search.gmane.org/, either search for your problem or search for my address to get my initial message about this problem.
I fixed it by building a new initrd file that included the driver for my SATA controller.
Can you point me at any docs that guide me through this process?
Not really. I'm a real newbie at all this stuff. I just did extensive googling. Look at the man page for mkinitrd. Google for it as well. I found some stuff when I googled for mkinitrd and sata_sil (although it turns out I really wanted sata_via). You should be able to boot from your Rescue CD. When you do, it should flash up a window when it loads your SATA driver. Notice which drive it is loading because that is the one you need.
I created a new image using mkinitrd (i.e., did *not* overwrite the one that was there). I created a new entry in my grub.conf and used the new image.
I also noticed that my modprobe.conf file was missing things after upgrading, which might have been the original problem.
Such as? What should modprobe.conf look like? Mine just contains one line:
# Note: for use under 2.4, changes must also be made to modules.conf! alias char-major-89-* i2c-dev
However, there is a modprobe.conf.dist file which has 165 lines. Should I copy this to modprobe.conf?
I don't know. I think I compared it with modprobe.conf.anacbak, which I assume was my previous file. There is a possibility that this relates to a different problem.
John Swartzentruber wrote:
You can search this newsgroup at http://search.gmane.org/, either search for your problem or search for my address to get my initial message about this problem.
Can you point me at any docs that guide me through this process?
Not really. I'm a real newbie at all this stuff. I just did extensive googling. Look at the man page for mkinitrd. Google for it as well. I found some stuff when I googled for mkinitrd and sata_sil (although it turns out I really wanted sata_via). You should be able to boot from your Rescue CD. When you do, it should flash up a window when it loads your SATA driver. Notice which drive it is loading because that is the one you need.
What gets me is that I can boot into rescue mode and the kernel on the DVD loads the drivers just fine!
I've actually booted into rescue mode, chroot'ed to /mnt/sysimage and run the services manually so things are back up until I fix the kernel issue. I had to do the following before running any services:
# start_udev # mount /dev/pts # mount /dev/shm
I think I then ran /etc/rc 3 to start everything that would normally start in runlevel 3
I created a new image using mkinitrd (i.e., did *not* overwrite the one that was there). I created a new entry in my grub.conf and used the new image.
OK, I'll give that a go.
I also noticed that my modprobe.conf file was missing things after upgrading, which might have been the original problem.
Such as? What should modprobe.conf look like? Mine just contains one line:
# Note: for use under 2.4, changes must also be made to modules.conf! alias char-major-89-* i2c-dev
However, there is a modprobe.conf.dist file which has 165 lines. Should I copy this to modprobe.conf?
I don't know. I think I compared it with modprobe.conf.anacbak, which I assume was my previous file. There is a possibility that this relates to a different problem.
Possibly.
I live in hope of a new kernel rpm release that will fix the problem for me! :)
R.
Am Do, den 02.12.2004 schrieb Robin Bowes um 15:50:
I also noticed that my modprobe.conf file was missing things after upgrading, which might have been the original problem.
Such as? What should modprobe.conf look like? Mine just contains one line:
# Note: for use under 2.4, changes must also be made to modules.conf! alias char-major-89-* i2c-dev
However, there is a modprobe.conf.dist file which has 165 lines. Should I copy this to modprobe.conf?
R.
No, please don't copy the modprobe.conf.dist file content over to the modprobe.conf. That file should only contain module instructions for the hardware you really have.
What certainly is missing is the alias entry for your ethernet card. Or don't you have one in that host? If you have audio there should be entries for that too.
Alexander
Alexander Dalloz wrote:
Am Do, den 02.12.2004 schrieb Robin Bowes um 15:50:
However, there is a modprobe.conf.dist file which has 165 lines. Should I copy this to modprobe.conf?
R.
No, please don't copy the modprobe.conf.dist file content over to the modprobe.conf. That file should only contain module instructions for the hardware you really have.
What certainly is missing is the alias entry for your ethernet card. Or don't you have one in that host? If you have audio there should be entries for that too.
Yes, I have an ethernet card. No audio though (at least I've never configured it) - it's a server.
There is a file modprobe.conf.anacbak in /etc/ which contains:
alias scsi_hostadapter sata_promise alias eth0 natsemi
I've copied this to modprobe.conf.
If what Fred says is correct then this won't fix my problem. I need a kernel with the ext3 filesystem built in.
Thanks,
R.
On 12/2/2004 12:41 PM Robin Bowes wrote:
Alexander Dalloz wrote:
Am Do, den 02.12.2004 schrieb Robin Bowes um 15:50:
However, there is a modprobe.conf.dist file which has 165 lines. Should I copy this to modprobe.conf?
R.
No, please don't copy the modprobe.conf.dist file content over to the modprobe.conf. That file should only contain module instructions for the hardware you really have.
What certainly is missing is the alias entry for your ethernet card. Or don't you have one in that host? If you have audio there should be entries for that too.
Yes, I have an ethernet card. No audio though (at least I've never configured it) - it's a server.
There is a file modprobe.conf.anacbak in /etc/ which contains:
alias scsi_hostadapter sata_promise alias eth0 natsemi
I've copied this to modprobe.conf.
If what Fred says is correct then this won't fix my problem. I need a kernel with the ext3 filesystem built in.
Try building a new initrd file with your driver before you give up. If you can boot from your rescue CD, you should have everything you need. My problem (and I only have one processor) was that the initrd file that was built during the upgrade didn't have sata_via (sata_promise in your case).
John Swartzentruber wrote:
On 12/2/2004 12:41 PM Robin Bowes wrote:
If what Fred says is correct then this won't fix my problem. I need a kernel with the ext3 filesystem built in.
Try building a new initrd file with your driver before you give up. If you can boot from your rescue CD, you should have everything you need. My problem (and I only have one processor) was that the initrd file that was built during the upgrade didn't have sata_via (sata_promise in your case).
John,
I've installed kernel-2.6.9-1.681_FC3 which boots fine and created a new bugzilla entry: https://bugzilla.redhat.com/bugzilla/show_bug.cgi?id=141658
Thanks for your help,
R.