Unable to mount root fs on unknown-block(0,0) [SOLVED]

[lunita]

Hi all,

I'm on a I3 64 bits proc, on a Sony Vaio. When I boot the system, I have the error:

Cannot open root device 'sda4' or unknown-block(0,0)
Please append a correct "root=" boot option: here are the available partitions:
Kernel panic - not syncing: VFS: Unable to mount root fs on unknown-block(0,0)

So, I know it's a very common error, but I can't find the solution for my case, I can't determine the source of the problem. I think that the kernel can't find the disk, it sounds like this.

I have 4 partitions,
sda1 :: /boot
sda2 :: swap
sda3 :: /home
sda4 :: /

All in ext4 except swap.

My grub.conf
root(hd0,0)
kernel (hd0,0)/$kernel root=/dev/sda4

I've check that the name of the kernel is placed on /usr/src and the link linux is pointing on it.

Most solutions relationed with this error are from config, but I tryed several (hd instead of sd, the boot partition, but not response).

lspci:

Sata controller

I tried genkernel, but same result....

Any tips?

Thanks in advance...

[cach0rr0]

your grub.conf and fstab are correct to use sda4

the unknown block 0,0 means the kernel was built without your HDD controller driver
the fact that it even gets that far means grub.conf is fine
so, you will need to rebuild the kernel to include the correct driver, copy it over to /boot, update grub.conf if needed, and reboot

first two links in my signature should get you started
_________________
Lost configuring your system?
dump lspci -n here | see Pappy's guide | Link Stash

[DONAHUE]

enter the chroot

[lunita]

[DONAHUE]

do this https://forums.gentoo.org/viewtopic-t-880149.html
_________________
Defund the FCC.

[cach0rr0]

modules reside on your root partition under /lib

if the driver for your hard disk is a module, it's like having a scuba mask, but putting it at the bottom of the ocean - you can make it to the bottom of the ocean to get your scuba mask, if only you had a scuba mask that would enable you to get to the bottom of the ocean!

for your disk driver, and for the filesystem driver that you use for your root partition, these need to be built-in, always, unless you use an initramfs and put the modules inside the initramfs (you dont need an initramfs except in special circumstances, and this is not one)

so, make the AHCI SATA driver a built-in, and let us troubleshoot from there.
the first suggestion I would make, boot from your livecd, chroot in as per the handbook, then rc-update add udev sysinit, then rebuild your kernel to make sure AHCI SATA is a built-in, then reboot. If you have any errors, post them with as much detail as you can
_________________
Lost configuring your system?
dump lspci -n here | see Pappy's guide | Link Stash

[lunita]