Ghosted Linux box from PATA -> SATA, now kernel panic, what do I change?

[bubba]

I ghosted a linux box from an older PATA-based box to a newer SATA box. Now I get a kernel panic when I boot. I can boot off the RedHat CD in Rescue mode and mount the drives, so what do I need to change to get this thing to boot?

The / partition changed from /dev/hda1 to /dev/sda1 and I tried to change that in GRUB, but that didn't seem to get me any further.

Any ideas?

Thanks!

 

[akubi]

also change the mount points in /etc/fstab to point to sda123..

 

[bubba]

I did that and yet I still get a kernel panic. What am I missing?

 

[n0cmonkey]

Details please.

 

[bubba]

My GRUB file looks like this:

root (hd0,0)
kernel /boot/vmlinux-2.4.21-32.0.1.EL ro root=/dev/sda1
initrd /boot/initrd-2.4.21-32.0.0.EL.img



I get the following errors:

[...]
Creating block devices
kmod: failed to exec /bin/modprobe -s -k block-major-8, errno = 2
VFS: Cannot open root device "sda1" or 08:01
Please append a correct "root=" boot option
Kernel panic; VFS: Unable to mount root fs on 08:01




However, when I boot of the RedHat CD in rescue mode, it mounts the drives automatically just fine. This is RedHat Enterprise 3. The 1 SATA drive is primary master on the SATA chain and the CDRW is primary master on the PATA chain.

Any other ideas?

 

[Nothinman]

But does it show detection of the drive on bootup?

 

[sourceninja]

looks like sata drivers arn't there. Did you compile your own kernel?

 

[bubba]

Do you mean the drives show up in the BIOS? If so, then yes.

If you mean in the linux kernel dmesg, I don't know, they scroll by too fast, but I don't think it gets that far.


I did not install a custom kernel... This is just the latest RedHat Enterprise WS version 3 kernel.

 

[TGS]

Originally posted by: sourceninja
looks like sata drivers arn't there. Did you compile your own kernel?

Did you check your current kernel settings to see if the SATA drivers are there?

The CD may be loading Everything-and-the-Kitchen-Sink? in the kernel for compatibility purposes.

Are the kernels from the CD and the installed ones the same? You should just need to enable the support if your installed kernel is the same.

 

[bubba]

I am not sure what modules the kernel is loading. How do I tell what modules are loaded by the CDROM in "rescue" mode and how do I change what is loaded by the kernel on disk (when I have the disk mounted in rescue mode).

Thanks!

 

[P0ldy]

#lspci
#lsmod

Should give you some idea of what you need to tick in make menuconfig when compiling the kernel.

 

[Nothinman]

No one should be recompiling a kernel on a RH Enterprise box.

 

[AnonymouseUser]

Do you have a BIOS option that allows the SATA drive to appear as a PATA drive to the OS?

 

[silverpig]

dmesg | less

do an lsmod on the recovery cd to see what sata drivers you have (sata_nv or sata_via or something else)

 

[TonyRic]

what is needed is an initrd rebuild. It is initially built when a system gets installed. Since SATA uses the scsi subsystem (AFAIK) a new initrd is needed.

http://linuxcommand.org/man_pages/mkinitrd8.html

an example would be "/sbin/mkinitrd /boot/initrd-2.2.17-14.img 2.2.17-14"

 

[sourceninja]

Learned something new. Thats good to know. I always use my own kernels on my box's, so I've never delt with anything like that before.

Thanks for the info.