/dev/sda1 not found after I replace with new kernel image

softarts · 12-07-2010, 10:09 AM

hi
I used kernel 2.6.5 in vmware
I copied new kernel 2.6.37 image and initrd from other machine,to replace the current one
after reboot,the initrd.img can be loaded,but soon it report "/dev/sda1 not found, waiting for ..."
I need to do anything in initrd.img to make it recognize "/dev/sda1" device?
/dev/sda1 is vmware scsi disk.

thanks!

stress_junkie · 12-07-2010, 10:22 AM

The initrd image may be the beginning of problems using this kernel. You did not copy the system map or other configuration files, you did not copy new modules, you did not link the modules, etc.

If you can boot the old kernel then it would be better to do that, remove the new kernel and initrd, and perform a normal kernel upgrade. That will create all of the files and linking that the new kernel needs.

lazlow · 12-07-2010, 10:42 AM

IF you have both pata and sata/scsi drives in the machine it MAY be the change in drive designations. On most distros pata has traditionally been designated as hdX and sata/scsi as sdX, but on newer kernels (post .18?) it has changed to designate all drives (pata/sata/...) as sdX.

softarts · 12-07-2010, 07:43 PM

hi stress_junkie:
what do you mean "a normal kernel upgrade."? I build and boot the new kernel on the other machine and got a similar problem "/dev/cciss/c0d0p2 not found,waiting for ...."
(cciss.ko included in initrd.img) so I want to know how this happen? because I didn't update my udev configuration or something like that?