Find the answer to your Linux question:
Results 1 to 7 of 7
Every time i`m trying to boot 2.6.18 kernel something like this appears: VFS: cannot open root device "hda2" or unknown block(0,0) Please append a correct "root=" boot option Kernel panic: ...
  1. #1
    Just Joined!
    Join Date
    Nov 2006
    Posts
    10

    VFS: cannot open root device "hda2" or unknown block(0,0)

    Every time i`m trying to boot 2.6.18 kernel something like this appears:
    VFS: cannot open root device "hda2" or unknown block(0,0)
    Please append a correct "root=" boot option
    Kernel panic: VFS: Unable to mount root fs on unknown-block(0,0)

    During the installation, the 2.4 kernel recognizes the hard drive as an IDE one (/dev/hda) but DMA can't be enabled, and under the 2.6 kernel, the disk is seen as a SATA drive. anyone know how to get this going i did change my /dev/hda2 to sda2 and nothing.
    here is my grub.conf file

    title Debian GNU/Linux, kernel 2.6.18
    root (hd0,1)
    kernel /boot/vmlinuz-2.6.18 root=/dev/hda2 ro
    initrd /boot/initrd.img-2.6.18
    savedefault
    boot

    title Debian GNU/Linux, kernel 2.6.18 (recovery mode)
    root (hd0,1)
    kernel /boot/vmlinuz-2.6.18 root=/dev/hda2 ro single
    initrd /boot/initrd.img-2.6.18
    savedefault
    boot

    title Debian GNU/Linux, kernel 2.4.27-3-386
    root (hd0,1)
    kernel /boot/vmlinuz-2.4.27-3-386 root=/dev/hda2 ro
    initrd /boot/initrd.img-2.4.27-3-386
    savedefault
    boot

    title Debian GNU/Linux, kernel 2.4.27-3-386 (recovery mode)
    root (hd0,1)
    kernel /boot/vmlinuz-2.4.27-3-386 root=/dev/hda2 ro single
    initrd /boot/initrd.img-2.4.27-3-386
    savedefault
    boot

    ### END DEBIAN AUTOMAGIC KERNELS LIST

  2. #2
    Just Joined! mvantuyl's Avatar
    Join Date
    Nov 2006
    Location
    San Antonio. Texas
    Posts
    32
    Your grub.conf file looks OK. Are you sure /dev/hda2 is the boot partition?

  3. #3
    Just Joined!
    Join Date
    Nov 2006
    Posts
    10
    Quote Originally Posted by mvantuyl
    Your grub.conf file looks OK. Are you sure /dev/hda2 is the boot partition?
    It is with 2.4 vertion

  4. #4
    Just Joined! mvantuyl's Avatar
    Join Date
    Nov 2006
    Location
    San Antonio. Texas
    Posts
    32
    The next question: if the 2.6 kernel sees it as a SATA drive, is SATA support enabled in the kernel?

    Here's a link to a similar thread in the Gentoo forum:
    http://www.linuxforums.org/forum/gen...ub-conf-2.html

  5. #5
    Just Joined!
    Join Date
    Nov 2006
    Posts
    10
    Quote Originally Posted by mvantuyl
    The next question: if the 2.6 kernel sees it as a SATA drive, is SATA support enabled in the kernel?
    ok here is that i have enable on the kernel

    # SCSI low-level drivers
    #
    # CONFIG_ISCSI_TCP is not set
    # CONFIG_BLK_DEV_3W_XXXX_RAID is not set
    # CONFIG_SCSI_3W_9XXX is not set
    # CONFIG_SCSI_ACARD is not set
    # CONFIG_SCSI_AACRAID is not set
    # CONFIG_SCSI_AIC7XXX is not set
    # CONFIG_SCSI_AIC7XXX_OLD is not set
    # CONFIG_SCSI_AIC79XX is not set
    # CONFIG_SCSI_DPT_I2O is not set
    # CONFIG_SCSI_ADVANSYS is not set
    # CONFIG_MEGARAID_NEWGEN is not set
    # CONFIG_MEGARAID_LEGACY is not set
    # CONFIG_MEGARAID_SAS is not set
    CONFIG_SCSI_SATA=y
    # CONFIG_SCSI_SATA_AHCI is not set
    # CONFIG_SCSI_SATA_SVW is not set
    CONFIG_SCSI_ATA_PIIX=y
    # CONFIG_SCSI_SATA_MV is not set
    # CONFIG_SCSI_SATA_NV is not set
    # CONFIG_SCSI_PDC_ADMA is not set
    # CONFIG_SCSI_HPTIOP is not set
    # CONFIG_SCSI_SATA_QSTOR is not set
    # CONFIG_SCSI_SATA_PROMISE is not set
    # CONFIG_SCSI_SATA_SX4 is not set
    # CONFIG_SCSI_SATA_SIL is not set
    # CONFIG_SCSI_SATA_SIL24 is not set
    # CONFIG_SCSI_SATA_SIS is not set
    # CONFIG_SCSI_SATA_ULI is not set
    # CONFIG_SCSI_SATA_VIA is not set
    # CONFIG_SCSI_SATA_VITESSE is not set
    # CONFIG_SCSI_BUSLOGIC is not set
    # CONFIG_SCSI_DMX3191D is not set
    # CONFIG_SCSI_EATA is not set
    # CONFIG_SCSI_FUTURE_DOMAIN is not set
    # CONFIG_SCSI_GDTH is not set
    # CONFIG_SCSI_IPS is not set
    # CONFIG_SCSI_INITIO is not set
    # CONFIG_SCSI_INIA100 is not set
    # CONFIG_SCSI_SYM53C8XX_2 is not set
    # CONFIG_SCSI_IPR is not set
    # CONFIG_SCSI_QLOGIC_1280 is not set
    # CONFIG_SCSI_QLA_FC is not set
    # CONFIG_SCSI_LPFC is not set
    # CONFIG_SCSI_DC395x is not set
    # CONFIG_SCSI_DC390T is not set
    # CONFIG_SCSI_NSP32 is not set
    # CONFIG_SCSI_DEBUG is not set

  6. #6
    Just Joined!
    Join Date
    Nov 2006
    Posts
    10
    ok guys I got it fix,what I did reinstall debian with libata.atapi_enabled=1 support
    I run the install cd @ boot time I put linux libata.atapi_enabled=1 and did the regular install, then down load and configure the new kernel 2.6.18 waalaa works good. ohh I did some changes to the /etc/fstab and my /boot/grub/menu.lst from hda to sda. thatnks guys for all your help!!

  7. #7
    Just Joined!
    Join Date
    Oct 2006
    Posts
    32
    I have the same problem installing the kernel from a floppy disk. So using:

    grub> kernel (fd0)/boot/vmlinuz init=bin/sh root=/dev/fd0 load_ramdisk=1 prompt_ramdisk=1
    grub>boot

    The result is something like:

    Kernel panic: VFS: Unable to mount root fs on unknown-block(0,0)


    Any idea?

Posting Permissions

  • You may not post new threads
  • You may not post replies
  • You may not post attachments
  • You may not edit your posts
  •