poisonbl at gmail
Apr 29, 2012, 5:33 PM
Post #9 of 11
On Sun, Apr 29, 2012 at 20:11, Ignas Anikevičius <anikevicius [at] gmail> wrote:
Re: Re: Please help, kernel can not load root
[In reply to]
> On 29 April 2012 18:35, Ignas Anikevičius <anikevicius [at] gmail> wrote:
>> it's been several since I have tried to make my machine boot again without
>> any live CDs and I could not narrow the main issue down. The problem is that
>> the kernel can not mount the root partition.
>> Some info about my system:
>> running ~amd64
>> kernel: gentoo-sources-3.3.3
>> bootloader: grub2-9999 (grub.cfg generated with grub2-mkconfig -o
>> root partition is ext4, but ext4 is built into kernel
>> I have a separate /boot partition
>> my grub.cfg can be found here:
>> I have written down some log messages from the last boot. Sorry if
>> something is not 100% accurate as I took a crappy picture with my phone and
>> tried to rewrite everything:
>> I would very appreciate someones help.
>> Ignas A.
> Hello to everybody once more. I gave it ago and installed drivers for all
> storage related controllers, but nothing has changed. As I understand, the
> hdd is recognized, so I do not know where to look now.
> The log can be see in this image:
> I tried to rewrite it here:
> ata1: SATA link up 1.5 Gbps (SStatus 113 SControl 300)
> ata1.00: ACPI cmd ...
> ata1.00: configured for UDMA/133
> scsi 0:0:0:0: Direct-Access ATA WDC WD3200...
> ata2: SATA link up 1.5 Gbps (SStatus 113 SControl 300)
> ata2.00: ACPI cmd ...
> ata2.00: ATAPI: Optiarc DVD RW AD-...
> ata2.00: configured for UDMA/100
> scsi 1:0:0:0: CD-ROM
> registered taskstats version 1
> Magic number...
> pci_link ... : hash matches
> console ... enabled
> netconsole: network logging started
> Root-NFS: no NFS server address
> VFS: Unable to mount root fs via NFS, trying floppy
> VFS: Cannot open root device "sda7" or unknown-block(2,0)
> Please append a correct "root=" boot option: here are the available
> Kernel panic - not syncing: VFS: Unable to mount root fs on
> Pid: 1, comm: swapper/0 Not tainted 3.3.3-gentoo #7
> Call Trace:
> ... panic
> ... ? printk
> ... mount_block_root
> ... mount_root
> ... prepare_namespace
> ... kernel_init
> ... kernel_thread
> ... ? start_kernel
> ... ? gs_change
> panic occured, switching back to text console
Well, going through the list that comes to mind after that... the
block device itself, since the scsi layer sees the device but the VFS
layer doesn't see the block device:
Joshua M. Murphy