Hi Stephen What is your harddisk attachment? SAS? ATA? You need to build the appropriate module for the attachment. (Hint: Check the config for a running kernel) You would need to enable SCSI_LOWLEVEL without which you would not have many low level SCSI drivers.
Would enabling EXT2 help? # # SCSI Transports # CONFIG_SCSI_SPI_ATTRS=y # CONFIG_SCSI_FC_ATTRS is not set CONFIG_SCSI_ISCSI_ATTRS=y # CONFIG_SCSI_SAS_ATTRS is not set # CONFIG_SCSI_SAS_LIBSAS is not set # CONFIG_SCSI_SRP_ATTRS is not set # CONFIG_SCSI_LOWLEVEL is not set # CONFIG_SCSI_LOWLEVEL_PCMCIA is not set # CONFIG_SCSI_DH is not set Regards Durga ________________________________ From: Stephen Roberts <[email protected]> To: Durga Prasad <[email protected]> Cc: Mulyadi Santosa <[email protected]>; [email protected] Sent: Monday, March 2, 2009 2:42:05 AM Subject: Re: Kernel Panic at boot Hi Durga, Attached is my .config file. Let me know if you can see this, thanks On Sun, Mar 1, 2009 at 8:37 AM, Durga Prasad <[email protected]> wrote: Hi, Can you provide the .config file used to compile your kernel. - Durga ________________________________ From: Mulyadi Santosa <[email protected]> To: Stephen Roberts <[email protected]> Cc: [email protected] Sent: Sunday, March 1, 2009 10:42:31 AM Subject: Re: Kernel Panic at boot Hi... On Sun, Mar 1, 2009 at 6:02 AM, Stephen Roberts <[email protected]> wrote: > Hi, > Thanks for your response. > > I tried what you said and it seemed to help, but when I ran mkinitrd I got > this: > > ------------------------------------------------------------------------------------------------------------------------------------------------- > step...@the-batman:/usr/local/src/linux-2.6.28$ sudo mkinitrd -o > initrdsteo.img-2.6.28 2.6.28 > /usr/sbin/mkinitrd: add_modules_dep_2_5: modprobe failed > FATAL: Module sg not found. > FATAL: Module sd_mod not found. > WARNING: This failure MAY indicate that your kernel will not boot! > but it can also be triggered by needed modules being compiled into > the kernel. hmm, i did this to see where sg module should land: [muly...@mulyadi ~]$ cd /lib/modules/`uname -r` [muly...@mulyadi 2.6.27.12-78.2.8.fc9.i686]$ find | grep -i sg ./kernel/drivers/media/video/videobuf-dma-sg.ko ./kernel/drivers/char/ipmi/ipmi_msghandler.ko ./kernel/drivers/scsi/sg.ko so it seems that sg.ko has something to do with SCSI. are you sure you have enabled everything related to SCSI? I can't give any hints about it, so I think other people could help better here. my other suspicion is, you need to upgrade your mkinitrd to somehow match the installed kernel version. > Then when I booted the kernel: > ------------------------------------------------------------------------------------------------------------------------------------------------- > RAMDISK: Loading into RAM disk... done > List of all partitions: > 0800 sda driver: sd > 0801 <numbers> sda1 > 0802 <numbers> sda2 > 0803 <numbers> sda3 > 0804 <numbers> sda4 > 0b00 <numbers> sr0 driver: sr > No filesystem could mount root, tried: ext3 vfat msdos iso9660 > Kernel Panic - not syncing: VFS: Unable to mount root fs on unkown > block(0,0) Here's my confusion. When I looked the above messages, I think that you also forgot to compile certain filesystem types. What's the filesystem type of your root filesystem anyway? and if it's compiled as kernel modules, are you sure it's included in the initrd image? regards, Mulyadi. -- To unsubscribe from this list: send an email with "unsubscribe kernelnewbies" to [email protected] Please read the FAQ at http://kernelnewbies.org/FAQ
