Hello,

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 /boot/grub2/grub.cfg)
root partition is ext4, but ext4 is built into kernel


I have a separate /boot partition

my grub.cfg can be found here:
http://pastebin.com/nm6HCkpM

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:


http://pastebin.com/0zQN6X5t

I would very appreciate someones help.

Thanks,
Ignas A.

On 29 April 2012 19:21, walt <w41ter@gmail.com> wrote:


On 04/29/2012 11:35 AM, Ignas Anikevi�ius wrote:

> Hello,

>

> 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.



The error message is unknown block(2,0), which may mean that your

kernel lacks a driver for your disk controller. Â*IIRC the kernel

config menu for block devices has changed. Â*Maybe you need to

set CONFIG_ATA or some other obscure item in your kernel config

to make the correct driver visible?

OK, How to find out which controller I am using at the moment whilst using a live CD? I have successfully chrooted into my system from a Mint Live CD, so I should be able to inspect my system either using Mint utilities or the Gentoo ones.



Thanks,
Ignas

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

On 29.04.2012 21:42, Ignas Anikevi�ius wrote:
> On 29 April 2012 19:21, walt <w41ter@gmail.com> wrote:
>
>> On 04/29/2012 11:35 AM, Ignas Anikevi�ius wrote:
>>> Hello,
>>>
>>> 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.
>>
>> The error message is unknown block(2,0), which may mean that
>> your kernel lacks a driver for your disk controller. IIRC the
>> kernel config menu for block devices has changed. Maybe you need
>> to set CONFIG_ATA or some other obscure item in your kernel
>> config to make the correct driver visible?
>>
>
> OK, How to find out which controller I am using at the moment
> whilst using a live CD? I have successfully chrooted into my system
> from a Mint Live CD, so I should be able to inspect my system
> either using Mint utilities or the Gentoo ones.
>
> Thanks, Ignas
>

You could try lspci

I would recommend to try it from the live cd (because under gentoo you
may need to emerge it first - otherwise it doesn't matter).

Within the output search for something like SATA Controller or PATA
Controller. If you can't find a matching driver google for the output
of lspce and kernel module.
If it's a SATA device in most cases the generic AHCI
(CONFIG_SATA_AHCI) seems to work.

You could also try lsmod though the problem is, that you would need to
know the names of possible modules.


WKR
Hinnerk
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v2.0.19 (GNU/Linux)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/

iQEcBAEBAgAGBQJPnZuXAAoJEJwwOFaNFkYc89sIAJdkpDKC3o ro0a2K6BFqTL0R
YUrC6wiRv6uG4egKgVrpM4HfbsGFejgRDI0rFT+2qkFfkljqBS IFHJ54OrgviOr9
YzSDeodt/qzwKv3Eki0oB8XsPnOHo1pLRp2lmPpNb5YJNjlHXX6NmXNDbiY fgzdw
FP6+eCErDOUjGYpyRLEn+hkHdzD8bXsLpfpEDmcWN5duUQWA7o QJV8xcA5k2kD3F
P6PKGbdoXVN7TCjBDrpmDsKmzH885C2vXC2RjML75q4Wrsozn+ PADfCge6e+T50s
TvtA8AO777uXnqvaOlt/1RNVHz+Mzx69iLxBHGG2lMkvKMoVsIYWEvW1FpWwqcM=
=RJWR
-----END PGP SIGNATURE-----

On Sun, 29 Apr 2012 19:42:14 +0000, Ignas Anikevi�ius wrote:

> OK, How to find out which controller I am using at the moment whilst
> using a live CD?

lspci -k

The -k shows the modules in use for each device.

Incidentally, don't use pastebin for error messages, include them in
your mail so they are still there when the mail is read from the
archives.


--
Neil Bothwick

"I laugh in the face of danger, then I hide until it goes away"

On 29 April 2012 20:05, Neil Bothwick <neil@digimed.co.uk> wrote:


lspci -k



The -k shows the modules in use for each device.

Thanks, this was exactly what I was looking for. Actually the AHCI module was already compiled in, so I do not know what is happening, but we'll see what happens with the next boot.




Incidentally, don't use pastebin for error messages, include them in

your mail so they are still there when the mail is read from the

archives.

Thank for letting me know. I will do it next time.

Cheers,
Ignas A.

On 29 April 2012 18:35, Ignas Anikevi�ius <anikevicius@gmail.com> wrote:


Hello,

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 /boot/grub2/grub.cfg)
root partition is ext4, but ext4 is built into kernel



I have a separate /boot partition

my grub.cfg can be found here:
http://pastebin.com/nm6HCkpM

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:



http://pastebin.com/0zQN6X5t

I would very appreciate someones help.

Thanks,
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:
http://s10.postimage.org/hieljd661/29042012017.jpg

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 partitions:


Kernel panic - not syncing: VFS: Unable to mount root fs on unknown-block(2,0)
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
================================================== ========================



Thanks,
Ignas

On Sun, Apr 29, 2012 at 20:11, Ignas Anikevi�ius <anikevicius@gmail.com> wrote:
> On 29 April 2012 18:35, Ignas Anikevi�ius <anikevicius@gmail.com> wrote:
>>
>> Hello,
>>
>> 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
>> /boot/grub2/grub.cfg)
>> root partition is ext4, but ext4 is built into kernel
>> I have a separate /boot partition
>>
>> my grub.cfg can be found here:
>> http://pastebin.com/nm6HCkpM
>>
>> 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:
>> http://pastebin.com/0zQN6X5t
>>
>> I would very appreciate someones help.
>>
>> Thanks,
>> 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:
> http://s10.postimage.org/hieljd661/29042012017.jpg
>
> 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
> partitions:
> Kernel panic - not syncing: VFS: Unable to mount root fs on
> unknown-block(2,0)
> 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
> ================================================== ========================
>
> Thanks,
> Ignas
>

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:
CONFIG_BLOCK=y
CONFIG_BLK_DEV_SD=y


--
Poison [BLX]
Joshua M. Murphy

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:

CONFIG_BLOCK=y

CONFIG_BLK_DEV_SD=y


Thanks, it was actually compiled as a module. That crept in when I was trying to make make my cdrom work if I connect it after I load the kernel. Somehow it just does not work if it is not present during boot time. As you saw from the log, it is connected via SATA interface.



Well, I'll try to boot a kernel with this thing compiled in and will see how it goes.

Thanks a lot,
Ignas

> 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:
> CONFIG_BLOCK=y
> CONFIG_BLK_DEV_SD=y

I wanted just to let everybody know, that this was the solution to my
problems. Thanks a lot to those who helped.

Cheers,
Ignas