Gentoo Forums
Gentoo Forums
Gentoo Forums
Quick Search: in
[SOLVED] VFS: Cannot open root device "(null)" or
View unanswered posts
View posts from last 24 hours

 
Reply to topic    Gentoo Forums Forum Index Installing Gentoo
View previous topic :: View next topic  
Author Message
augustin2
Apprentice
Apprentice


Joined: 16 Mar 2012
Posts: 188
Location: France

PostPosted: Sat Nov 17, 2012 5:09 pm    Post subject: [SOLVED] VFS: Cannot open root device "(null)" or Reply with quote

Hi,
I am in a situation very similar to the one of this post.: http://forums.gentoo.org/viewtopic-t-941980.html

Here are differences

boot is /dev/sdb1 (ext2)
root is /dev/sdb7 (ext3)

/boot/grub/grub.conf is
Code:
 default 0
 timeout 55
 splashimage=(hd1,0)/boot/grub/splash.xpm.gz

 title Gentoo Linux
 root (hd1,0)
 kernel /boot/kernel root=/dev/ram0 real_root=/dev/sdb7 rootfstype=ext3
 initrd /boot/initramfs

 title Gentoo Linux old kernel
 root (hd1,0)
 kernel /boot/kernel.old root=/dev/ram0  real_root=/dev/sdb7 rootfstype=ext3
 initrd /boot/initramfs.old


I made the following changes to genkernel.conf

Code:
OLDCONFIG="yes"
MENUCONFIG="yes"
CLEAN="no"
MRPROPER="no"
MOUNTBOOT="yes"
SYMLINK="yes"
MAKEOPTS="-j5"


I run
Code:
genkernel all


Code:
grub-install --no-floppy /dev/sda


At boot I receive this message


Quote:
VFS: Cannot open root device "(null)" or unknown-block(0,0): error -6 please append a correct "root=" boot option; here are the available partions: Kernel panic - not syncing: VFS: Unable to mount root fs on unknown-block(0,0)


What can I do ?

Thanks for help


Last edited by augustin2 on Mon Nov 19, 2012 9:17 am; edited 1 time in total
Back to top
View user's profile Send private message
NeddySeagoon
Administrator
Administrator


Joined: 05 Jul 2003
Posts: 31907
Location: 56N 3W

PostPosted: Sat Nov 17, 2012 5:24 pm    Post subject: Reply with quote

augustin2,

Your message
printk:
VFS: Cannot open root device "(null)" or unknown-block(0,0): error -6 please append a correct "root=" boot option; here are the available partions: Kernel panic - not syncing: VFS: Unable to mount root fs on unknown-block(0,0)
is from the kernel, so grub worked, read your grub.conf and loaded a kernel. Thats the good news.

Code:
unknown-block(0,0)
tells that the kernel cannot communicate with your hard drive at all, so nothing in the root file system matters yet, since the kernel cannot read it.

Something that you need to read the HDD is missing from your kernel.
In general terms thats the Partition Table driver SCSI Disk Driver or your Low Level Chipset driver.

As you used genkernel all, it should just work, as genkernel builds a fully modular kernel with almost every driver in the initramfs.
The "almost all" here is important - the one you need might be missing.

Show us the output of
Code:
lspci -k
and tell us how you partitioned your drives. The output of
Code:
fdisk -l
will do nicely.

With the above information we can tell you how to help genkernel make a kernel that will work for you.
Oh! if you are installing in a virtual machine, we need to know which one too. Answer no if you don't know what a virtual machine is.
_________________
Regards,

NeddySeagoon

Computer users fall into two groups:-
those that do backups
those that have never had a hard drive fail.
Back to top
View user's profile Send private message
augustin2
Apprentice
Apprentice


Joined: 16 Mar 2012
Posts: 188
Location: France

PostPosted: Sat Nov 17, 2012 5:59 pm    Post subject: Reply with quote

Thanks a lot. Here are the requested results
Code:
(chroot) Gentoo-2012 / # lspci -k
00:00.0 Host bridge: Intel Corporation Core Processor DMI (rev 11)
        Subsystem: Giga-byte Technology Device 5000
00:03.0 PCI bridge: Intel Corporation Core Processor PCI Express Root Port 1 (rev 11)
        Kernel driver in use: pcieport
00:05.0 PCI bridge: Intel Corporation Core Processor PCI Express Root Port 3 (rev 11)
        Kernel driver in use: pcieport
00:08.0 System peripheral: Intel Corporation Core Processor System Management Registers (rev 11)
00:08.1 System peripheral: Intel Corporation Core Processor Semaphore and Scratchpad Registers (rev 11)
00:08.2 System peripheral: Intel Corporation Core Processor System Control and Status Registers (rev 11)
00:08.3 System peripheral: Intel Corporation Core Processor Miscellaneous Registers (rev 11)
00:10.0 System peripheral: Intel Corporation Core Processor QPI Link (rev 11)
00:10.1 System peripheral: Intel Corporation Core Processor QPI Routing and Protocol Registers (rev 11)
00:1a.0 USB controller: Intel Corporation 5 Series/3400 Series Chipset USB Universal Host Controller (rev 06)
        Subsystem: Giga-byte Technology Device 5004
        Kernel driver in use: uhci_hcd
00:1a.1 USB controller: Intel Corporation 5 Series/3400 Series Chipset USB Universal Host Controller (rev 06)
        Subsystem: Giga-byte Technology Device 5004
        Kernel driver in use: uhci_hcd
00:1a.2 USB controller: Intel Corporation 5 Series/3400 Series Chipset USB Universal Host Controller (rev 06)
        Subsystem: Giga-byte Technology Device 5004
        Kernel driver in use: uhci_hcd
00:1a.7 USB controller: Intel Corporation 5 Series/3400 Series Chipset USB2 Enhanced Host Controller (rev 06)
        Subsystem: Giga-byte Technology Device 5006
        Kernel driver in use: ehci_hcd
00:1b.0 Audio device: Intel Corporation 5 Series/3400 Series Chipset High Definition Audio (rev 06)
        Subsystem: Giga-byte Technology Device a102
        Kernel driver in use: snd_hda_intel
00:1c.0 PCI bridge: Intel Corporation 5 Series/3400 Series Chipset PCI Express Root Port 1 (rev 06)
        Kernel driver in use: pcieport
00:1c.3 PCI bridge: Intel Corporation 5 Series/3400 Series Chipset PCI Express Root Port 4 (rev 06)
        Kernel driver in use: pcieport
00:1c.4 PCI bridge: Intel Corporation 5 Series/3400 Series Chipset PCI Express Root Port 5 (rev 06)
        Kernel driver in use: pcieport
00:1c.5 PCI bridge: Intel Corporation 5 Series/3400 Series Chipset PCI Express Root Port 6 (rev 06)
        Kernel driver in use: pcieport
00:1c.6 PCI bridge: Intel Corporation 5 Series/3400 Series Chipset PCI Express Root Port 7 (rev 06)
        Kernel driver in use: pcieport
00:1d.0 USB controller: Intel Corporation 5 Series/3400 Series Chipset USB Universal Host Controller (rev 06)
        Subsystem: Giga-byte Technology Device 5004
        Kernel driver in use: uhci_hcd
00:1d.1 USB controller: Intel Corporation 5 Series/3400 Series Chipset USB Universal Host Controller (rev 06)
        Subsystem: Giga-byte Technology Device 5004
        Kernel driver in use: uhci_hcd
00:1d.2 USB controller: Intel Corporation 5 Series/3400 Series Chipset USB Universal Host Controller (rev 06)
        Subsystem: Giga-byte Technology Device 5004
        Kernel driver in use: uhci_hcd
00:1d.3 USB controller: Intel Corporation 5 Series/3400 Series Chipset USB Universal Host Controller (rev 06)
        Subsystem: Giga-byte Technology Device 5004
        Kernel driver in use: uhci_hcd
00:1d.7 USB controller: Intel Corporation 5 Series/3400 Series Chipset USB2 Enhanced Host Controller (rev 06)
        Subsystem: Giga-byte Technology Device 5006
        Kernel driver in use: ehci_hcd
00:1e.0 PCI bridge: Intel Corporation 82801 PCI Bridge (rev a6)
00:1f.0 ISA bridge: Intel Corporation 5 Series Chipset LPC Interface Controller (rev 06)
        Subsystem: Giga-byte Technology Device 5001
00:1f.2 IDE interface: Intel Corporation 5 Series/3400 Series Chipset 4 port SATA IDE Controller (rev 06)
        Subsystem: Giga-byte Technology Device b002
        Kernel driver in use: ata_piix
00:1f.3 SMBus: Intel Corporation 5 Series/3400 Series Chipset SMBus Controller (rev 06)
        Subsystem: Giga-byte Technology Device 5001
        Kernel driver in use: i801_smbus
00:1f.5 IDE interface: Intel Corporation 5 Series/3400 Series Chipset 2 port SATA IDE Controller (rev 06)
        Subsystem: Giga-byte Technology Device b002
        Kernel driver in use: ata_piix
02:00.0 VGA compatible controller: NVIDIA Corporation G86 [GeForce 8500 GT] (rev a1)
        Subsystem: Giga-byte Technology Device 344c
        Kernel driver in use: nouveau
04:00.0 USB controller: NEC Corporation uPD720200 USB 3.0 Host Controller (rev 03)
        Subsystem: Giga-byte Technology Device 5007
        Kernel driver in use: xhci_hcd
05:00.0 SATA controller: JMicron Technology Corp. JMB363 SATA/IDE Controller (rev 03)
        Subsystem: Giga-byte Technology GA-EP45-DS5 Motherboard
        Kernel driver in use: ahci
05:00.1 IDE interface: JMicron Technology Corp. JMB363 SATA/IDE Controller (rev 03)
        Subsystem: Giga-byte Technology GA-EP45-DS5 Motherboard
        Kernel driver in use: pata_jmicron
06:00.0 IDE interface: Marvell Technology Group Ltd. Device 91a3 (rev 11)
        Subsystem: Giga-byte Technology Device b000
        Kernel driver in use: ahci
07:00.0 Ethernet controller: Realtek Semiconductor Co., Ltd. RTL8111/8168B PCI Express Gigabit Ethernet controller (rev 06)
        Subsystem: Giga-byte Technology GA-EP45-DS5/GA-EG45M-DS2H Motherboard
        Kernel driver in use: r8169
08:02.0 Network controller: Atheros Communications Inc. AR922X Wireless Network Adapter (rev 01)
        Subsystem: D-Link System Inc Device 3a78
        Kernel driver in use: ath9k
08:03.0 IDE interface: Integrated Technology Express, Inc. IT8213 IDE Controller
        Subsystem: Giga-byte Technology GA-EG45M-DS2H Mainboard
        Kernel driver in use: pata_it8213
08:07.0 FireWire (IEEE 1394): Texas Instruments TSB43AB23 IEEE-1394a-2000 Controller (PHY/Link)
        Subsystem: Giga-byte Technology GA-EP45-DS5/GA-EG45M-DS2H Motherboard
3f:00.0 Host bridge: Intel Corporation Core Processor QuickPath Architecture Generic Non-Core Registers (rev 04)
        Subsystem: Giga-byte Technology Device 5000
3f:00.1 Host bridge: Intel Corporation Core Processor QuickPath Architecture System Address Decoder (rev 04)
        Subsystem: Giga-byte Technology Device 5000
3f:02.0 Host bridge: Intel Corporation Core Processor QPI Link 0 (rev 04)
        Subsystem: Giga-byte Technology Device 5000
3f:02.1 Host bridge: Intel Corporation Core Processor QPI Physical 0 (rev 04)
        Subsystem: Giga-byte Technology Device 5000
3f:03.0 Host bridge: Intel Corporation Core Processor Integrated Memory Controller (rev 04)
        Subsystem: Giga-byte Technology Device 5000
3f:03.1 Host bridge: Intel Corporation Core Processor Integrated Memory Controller Target Address Decoder (rev 04)
        Subsystem: Giga-byte Technology Device 5000
3f:03.4 Host bridge: Intel Corporation Core Processor Integrated Memory Controller Test Registers (rev 04)
        Subsystem: Giga-byte Technology Device 5000
3f:04.0 Host bridge: Intel Corporation Core Processor Integrated Memory Controller Channel 0 Control Registers (rev 04)
        Subsystem: Giga-byte Technology Device 5000
3f:04.1 Host bridge: Intel Corporation Core Processor Integrated Memory Controller Channel 0 Address Registers (rev 04)
        Subsystem: Giga-byte Technology Device 5000
3f:04.2 Host bridge: Intel Corporation Core Processor Integrated Memory Controller Channel 0 Rank Registers (rev 04)
        Subsystem: Giga-byte Technology Device 5000
3f:04.3 Host bridge: Intel Corporation Core Processor Integrated Memory Controller Channel 0 Thermal Control Registers (rev 04)
        Subsystem: Giga-byte Technology Device 5000
3f:05.0 Host bridge: Intel Corporation Core Processor Integrated Memory Controller Channel 1 Control Registers (rev 04)
        Subsystem: Giga-byte Technology Device 5000
3f:05.1 Host bridge: Intel Corporation Core Processor Integrated Memory Controller Channel 1 Address Registers (rev 04)
        Subsystem: Giga-byte Technology Device 5000
3f:05.2 Host bridge: Intel Corporation Core Processor Integrated Memory Controller Channel 1 Rank Registers (rev 04)
        Subsystem: Giga-byte Technology Device 5000
3f:05.3 Host bridge: Intel Corporation Core Processor Integrated Memory Controller Channel 1 Thermal Control Registers (rev 04)
        Subsystem: Giga-byte Technology Device 5000
(chroot) Gentoo-2012 / #

Code:
(chroot) Gentoo-2012 / # fdisk -l

Disk /dev/sda: 1000.2 GB, 1000204886016 bytes
255 heads, 63 sectors/track, 121601 cylinders, total 1953525168 sectors
Units = sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 512 bytes / 512 bytes
Disk identifier: 0x000097bf

   Device Boot      Start         End      Blocks   Id  System
/dev/sda4   *     2107390  1953520064   975706337+   5  Extended
/dev/sda5      1023693993  1953520064   464913036   83  Linux
/dev/sda6         2107392    25546751    11719680   82  Linux swap / Solaris
/dev/sda7        25548800   444978487   209714844   83  Linux
/dev/sda8       444981248   502207810    28613281+  83  Linux
/dev/sda9       502210560  1023692981   260741211   83  Linux

Partition table entries are not in disk order

Disk /dev/sdb: 1000.2 GB, 1000204886016 bytes
255 heads, 63 sectors/track, 121601 cylinders, total 1953525168 sectors
Units = sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 512 bytes / 512 bytes
Disk identifier: 0x000da3c5

   Device Boot      Start         End      Blocks   Id  System
/dev/sdb1              63    55006559    27503248+  83  Linux
/dev/sdb2        55006621  1953520064   949256722    5  Extended
/dev/sdb5      1023886773  1953520064   464816646   83  Linux
/dev/sdb6        55006623   140857919    42925648+  83  Linux
/dev/sdb7   *   140859392   580525407   219833008   83  Linux
/dev/sdb8       580540968  1023886709   221672871   83  Linux

Partition table entries are not in disk order
Back to top
View user's profile Send private message
augustin2
Apprentice
Apprentice


Joined: 16 Mar 2012
Posts: 188
Location: France

PostPosted: Sat Nov 17, 2012 6:04 pm    Post subject: Reply with quote

I dont use a virtual machine
Back to top
View user's profile Send private message
NeddySeagoon
Administrator
Administrator


Joined: 05 Jul 2003
Posts: 31907
Location: 56N 3W

PostPosted: Sat Nov 17, 2012 6:15 pm    Post subject: Reply with quote

augustin2,

What a selection of disk interfaces:-
Code:
00:1f.2 IDE interface: Intel Corporation 5 Series/3400 Series Chipset 4 port SATA IDE Controller (rev 06)
        Subsystem: Giga-byte Technology Device b002
        Kernel driver in use: ata_piix
00:1f.5 IDE interface: Intel Corporation 5 Series/3400 Series Chipset 2 port SATA IDE Controller (rev 06)
        Subsystem: Giga-byte Technology Device b002
        Kernel driver in use: ata_piix
05:00.0 SATA controller: JMicron Technology Corp. JMB363 SATA/IDE Controller (rev 03)
        Subsystem: Giga-byte Technology GA-EP45-DS5 Motherboard
        Kernel driver in use: ahci
05:00.1 IDE interface: JMicron Technology Corp. JMB363 SATA/IDE Controller (rev 03)
        Subsystem: Giga-byte Technology GA-EP45-DS5 Motherboard
        Kernel driver in use: pata_jmicron
06:00.0 IDE interface: Marvell Technology Group Ltd. Device 91a3 (rev 11)
        Subsystem: Giga-byte Technology Device b000
        Kernel driver in use: ahci
08:03.0 IDE interface: Integrated Technology Express, Inc. IT8213 IDE Controller
        Subsystem: Giga-byte Technology GA-EG45M-DS2H Mainboard
        Kernel driver in use: pata_it8213

Genkernel certainly includes ahci the ata_piix drivers but I'm ot sure about pata_jmicron and pata_it8213, so if your HDD was connected to one of there controllers, it might not work.

Your fdisk -k shows that your have MSDOS Partition Tables on your drives. genkernel builds that too.

I suspect your HDDs are connected to a controller that genkernel does not build the low level driver for.
Rerun genkernel from inside the chroot but this time give it the menuconfig option. That will have either - or -- in front.
Genkernel will pause in menuconfig to allow you to check and make changes to the kernel configuration.
Make sure that the pata_jmicron and pata_it8213 options are on. If not set them as <*>. Press / to use search.
Save your menuconfig changes as you exit, then genkernel will carry on with the build.
_________________
Regards,

NeddySeagoon

Computer users fall into two groups:-
those that do backups
those that have never had a hard drive fail.
Back to top
View user's profile Send private message
augustin2
Apprentice
Apprentice


Joined: 16 Mar 2012
Posts: 188
Location: France

PostPosted: Sun Nov 18, 2012 8:33 am    Post subject: Reply with quote

hi ,

I have almost found and set all the kernel drivers that are marked above as "in use" exept for i801_smbus that I cannot find anywhere with the search tool. but the result remains the same. May be the message has a bit evolved and is like this
Quote:
VFS: Cannot open root device "/dev/ram0" or unknown-block(0,0): error -6 please append a correct "root=" boot option; here are the available partions: Kernel panic - not syncing: VFS: Unable to mount root fs on unknown-block(0,0)
Back to top
View user's profile Send private message
cach0rr0
Moderator
Moderator


Joined: 13 Nov 2008
Posts: 4121
Location: Houston, Republic of Texas

PostPosted: Sun Nov 18, 2012 9:36 am    Post subject: Reply with quote

augustin2 wrote:
hi ,

I have almost found and set all the kernel drivers that are marked above as "in use" exept for i801_smbus that I cannot find anywhere with the search tool. but the result remains the same. May be the message has a bit evolved and is like this
Quote:
VFS: Cannot open root device "/dev/ram0" or unknown-block(0,0): error -6 please append a correct "root=" boot option; here are the available partions: Kernel panic - not syncing: VFS: Unable to mount root fs on unknown-block(0,0)


i801_smbus should not be necessary for booting

one thing I noticed:

Code:

title Gentoo Linux
 root (hd1,0)
 kernel /boot/kernel root=/dev/ram0 real_root=/dev/sdb7 rootfstype=ext3
 initrd /boot/initramfs


can you please:

-make sure your boot partition is mounted
-show us the output of ls -alh /boot/

If the initramfs is loading at all, then root=/dev/ram0 should *not* be invalid.

I am wondering if there is even any file named '/boot/initramfs'
_________________
Lost configuring your system?
dump lspci -n here | see Pappy's guide | Link Stash
Back to top
View user's profile Send private message
augustin2
Apprentice
Apprentice


Joined: 16 Mar 2012
Posts: 188
Location: France

PostPosted: Sun Nov 18, 2012 10:26 am    Post subject: Reply with quote

Hi, thanks
Quote:

one thing I noticed:

Code:

title Gentoo Linux
root (hd1,0)
kernel /boot/kernel root=/dev/ram0 real_root=/dev/sdb7 rootfstype=ext3
initrd /boot/initramfs

can you please:

-make sure your boot partition is mounted
-show us the output of ls -alh /boot/

If the initramfs is loading at all, then root=/dev/ram0 should *not* be invalid.

I am wondering if there is even any file named '/boot/initramfs'


Before answering, and to make things as clear as possible to everybody, please let me sum up how I work

1- I am using a live DVD so I can communicate easyly with the forum
At each cycle, after booting and chrooting
2 - I copy the previous successful compilation like this
Code:
cp /etc/kernels/kernel-config-x86_64-3.5.7-gentoo  /usr/src/linux/.config



3- assuming a genkernel.conf as this

Quote:
OLDCONFIG="yes"
MENUCONFIG="yes"
CLEAN="no"
MRPROPER="no"
MOUNTBOOT="yes"
SYMLINK="yes"
MAKEOPTS="-j5"


I run

Code:
 genkernel all


Normally the SYMLINK="yes" provides for an updating of the symlinks in boot dir

Finaly I run
Code:
grub-install --no-floppy /dev/sda


Now the answer to your request


Quote:
(chroot) Gentoo-2012 / # ls -alh /boot/
total 15M
drwxr-xr-x 4 root root 4.0K Nov 18 10:28 .
drwxr-xr-x 21 root root 4.0K Nov 17 15:14 ..
-rw-r--r-- 1 root root 0 Nov 7 05:47 .keep
lrwxrwxrwx 1 root root 40 Nov 18 10:28 System.map -> System.map-genkernel-x86_64-3.5.7-gentoo
-rw-r--r-- 1 root root 1.8M Nov 18 10:28 System.map-genkernel-x86_64-3.5.7-gentoo
-rw-r--r-- 1 root root 1.8M Nov 18 09:49 System.map-genkernel-x86_64-3.5.7-gentoo.old
lrwxrwxrwx 1 root root 44 Nov 18 10:28 System.map.old -> System.map-genkernel-x86_64-3.5.7-gentoo.old
lrwxrwxrwx 1 root root 1 Nov 17 16:06 boot -> .
drwxr-xr-x 2 root root 4.0K Nov 18 10:28 grub
lrwxrwxrwx 1 root root 39 Nov 18 10:28 initramfs -> initramfs-genkernel-x86_64-3.5.7-gentoo
-rw-r--r-- 1 root root 1.5M Nov 18 10:28 initramfs-genkernel-x86_64-3.5.7-gentoo
-rw-r--r-- 1 root root 1.5M Nov 18 09:49 initramfs-genkernel-x86_64-3.5.7-gentoo.old
lrwxrwxrwx 1 root root 43 Nov 18 10:28 initramfs.old -> initramfs-genkernel-x86_64-3.5.7-gentoo.old
lrwxrwxrwx 1 root root 36 Nov 18 10:28 kernel -> kernel-genkernel-x86_64-3.5.7-gentoo
-rw-r--r-- 1 root root 4.1M Nov 18 10:28 kernel-genkernel-x86_64-3.5.7-gentoo
-rw-r--r-- 1 root root 4.1M Nov 18 09:49 kernel-genkernel-x86_64-3.5.7-gentoo.old
lrwxrwxrwx 1 root root 40 Nov 18 10:28 kernel.old -> kernel-genkernel-x86_64-3.5.7-gentoo.old
drwx------ 2 root root 16K Nov 17 15:05 lost+found
(chroot) Gentoo-2012 / # ls -a /etc/kernels


and to be more accurate and introduce a new question

Quote:
(chroot) Gentoo-2012 / # cat /boot/grub/grub.conf


default 0
timeout 55
splashimage=(hd1,0)/boot/grub/splash.xpm.gz

title Gentoo Linux
root (hd1,0)
kernel /boot/kernel root=/dev/ram0 init=/linuxrc real_root=/dev/sdb7 rootfstype=ext3
initrd /boot/initramfs

title Gentoo Linux old kernel
root (hd1,0)
kernel /boot/kernel.old root=/dev/ram0 init=/linuxrc real_root=/dev/sdb7 rootfstype=ext3
initrd /boot/initramfs.old


I noticed in the handbook something like
Quote:
ernel /boot/kernel-genkernel-x86-2.6.34-gentoo-r1 root=/dev/ram0 init=/linuxrc ramdisk=8192 real_root=/dev/sda3

thus I added init=/linuxrc but I hesitated with ramdisk=8192 because I was not sure it was relevant to my hardware.
I am going to test it now.
Back to top
View user's profile Send private message
BillWho
Veteran
Veteran


Joined: 03 Mar 2012
Posts: 1600
Location: US

PostPosted: Sun Nov 18, 2012 2:11 pm    Post subject: Reply with quote

augustin2,

Everything appears to be spot-on with your setup. One thing I noticed that might be a real long shot is the boot flag is set for your root partition:
Code:
/dev/sdb7   *   140859392   580525407   219833008   83  Linux

Try changing to /dev/sdb1 just to leave no stone unturned :wink:
_________________
Good luck :wink:

Since installing gentoo, my life has become one long emerge :)
Back to top
View user's profile Send private message
NeddySeagoon
Administrator
Administrator


Joined: 05 Jul 2003
Posts: 31907
Location: 56N 3W

PostPosted: Sun Nov 18, 2012 2:20 pm    Post subject: Reply with quote

augustin2,

Code:
VFS: Cannot open root device "/dev/ram0" or unknown-block(0,0)

Suggested that you don't have one or more of the following in your kernel.

Initramfs support.
DEVTMPFS
mount DEVTMPFS at boot. (Uppercase indicates a kernel symbol name that you can find with the search)

/dev/ram0 is where grub puts your initramfs so that the kernel can find it.
Check the above, if its still broken, use wgetpaste to put your kernel .config file onto a pastebin site.



BillWho,

A missing but required boot flag usually gives an Operating System not Found error from the BIOS.
_________________
Regards,

NeddySeagoon

Computer users fall into two groups:-
those that do backups
those that have never had a hard drive fail.
Back to top
View user's profile Send private message
augustin2
Apprentice
Apprentice


Joined: 16 Mar 2012
Posts: 188
Location: France

PostPosted: Sun Nov 18, 2012 4:44 pm    Post subject: Reply with quote

BillWho wrote:
augustin2,

Everything appears to be spot-on with your setup. One thing I noticed that might be a real long shot is the boot flag is set for your root partition:
Code:
/dev/sdb7   *   140859392   580525407   219833008   83  Linux

Try changing to /dev/sdb1 just to leave no stone unturned :wink:


I did so but there is no change
I even restarted from scratch with sdb1 bootable and did a first genkernel all (using config from /usr/share/genkernel/arch/x86_64-kernel-config ) that worked fine.
But after that, using the .config that I got from Pappy's seeds and improve all along this discussion only the old config runs and for the new I got the same message.
Back to top
View user's profile Send private message
augustin2
Apprentice
Apprentice


Joined: 16 Mar 2012
Posts: 188
Location: France

PostPosted: Sun Nov 18, 2012 4:46 pm    Post subject: Reply with quote

NeddySeagoon wrote:
augustin2,

Code:
VFS: Cannot open root device "/dev/ram0" or unknown-block(0,0)

Suggested that you don't have one or more of the following in your kernel.

Initramfs support.
DEVTMPFS
mount DEVTMPFS at boot. (Uppercase indicates a kernel symbol name that you can find with the search)

/dev/ram0 is where grub puts your initramfs so that the kernel can find it.
Check the above, if its still broken, use wgetpaste to put your kernel .config file onto a pastebin site.



BillWho,

A missing but required boot flag usually gives an Operating System not Found error from the BIOS.


Ok I see that. Thanks.
Back to top
View user's profile Send private message
NeddySeagoon
Administrator
Administrator


Joined: 05 Jul 2003
Posts: 31907
Location: 56N 3W

PostPosted: Sun Nov 18, 2012 4:49 pm    Post subject: Reply with quote

augustin2,

Pappys Seeds does not contain any hardware drivers - you follow the instructions to add your own.
Seeds based kernels also do not use an initramfs, so the grub.conf needs to be changed too.
_________________
Regards,

NeddySeagoon

Computer users fall into two groups:-
those that do backups
those that have never had a hard drive fail.
Back to top
View user's profile Send private message
augustin2
Apprentice
Apprentice


Joined: 16 Mar 2012
Posts: 188
Location: France

PostPosted: Sun Nov 18, 2012 5:54 pm    Post subject: Reply with quote

NeddySeagoon wrote:
augustin2,

Pappys Seeds does not contain any hardware drivers - you follow the instructions to add your own.
Seeds based kernels also do not use an initramfs, so the grub.conf needs to be changed too.



I am afraid I don't understand what to do.
As I used menuconfig to improve the seed adding the drivers for hardware, I wonder why it shouldn't work.
I had a look at this .config and it seems that the DEVTMPFS was set.
Here is this .config after my adding of many drivers http://bpaste.net/show/58821/
If I must do differently could you please give me some hints.
Back to top
View user's profile Send private message
BillWho
Veteran
Veteran


Joined: 03 Mar 2012
Posts: 1600
Location: US

PostPosted: Sun Nov 18, 2012 6:48 pm    Post subject: Reply with quote

augustin2,

In General setup # CONFIG_BLK_DEV_INITRD is not set

Set [*] Initial RAM filesystem and RAM disk (initramfs/initrd) support
_________________
Good luck :wink:

Since installing gentoo, my life has become one long emerge :)
Back to top
View user's profile Send private message
NeddySeagoon
Administrator
Administrator


Joined: 05 Jul 2003
Posts: 31907
Location: 56N 3W

PostPosted: Sun Nov 18, 2012 6:55 pm    Post subject: Reply with quote

augustin2,

Code:
CONFIG_DEVTMPFS=y
# CONFIG_DEVTMPFS_MOUNT is not set

You need the second option there too.

Code:
CONFIG_MSDOS_PARTITION=y
is good. That enable the kernel to read your partition tables.
Code:
# CONFIG_IDE is not set
is good, that turns off obsolete disk drivers.
Code:
# CONFIG_SYSFS_DEPRECATED is not set
is good. Setting that option prevents udev from working.

Code:
CONFIG_SCSI=y
CONFIG_SCSI_PROC_FS=y
CONFIG_BLK_DEV_SD=y
CONFIG_BLK_DEV_SR=yC
ONFIG_CHR_DEV_SG=y
CONFIG_SCSI_MULTI_LUN=y
CONFIG_ATA=y
are all good. The last one is important - it allows you to boot without using an initrd.

Code:
# CONFIG_SATA_AHCI is not set
# CONFIG_SATA_AHCI_PLATFORM is not set
You need the first one for your
Code:
Kernel driver in use: ahci
You may need the second one too. On my systems the _PLATFORM setting seems to be BIOS dependent, but its harmless to set it on.

Code:
CONFIG_ATA_PIIX=y
is correct for Kernel driver in use: ata_piix

Code:
CONFIG_PATA_IT8213=y
CONFIG_PATA_JMICRON=y
is correct for pata_it8213 and pata_jmicron

Code:
CONFIG_EXT3_FS=y
is good for your root filesystem.

In grub.conf you had
Code:
title Gentoo Linux
root (hd1,0)
kernel /boot/kernel root=/dev/ram0 init=/linuxrc real_root=/dev/sdb7 rootfstype=ext3
initrd /boot/initramfs

but with a seed you don't have an initrd, so don't try to load it and don't try to use it.

Code:
title Gentoo Linux
root (hd1,0)
kernel /boot/kernel root=/dev/sdb7 rootfstype=ext3
is all you need.

Provided your sdb is not attached to an ahci controller, the changes to grub.conf to not use an initrd should get you going.
If your sdb is attached to an ahci controller, you need to add the AHCI options to your kernel too.
_________________
Regards,

NeddySeagoon

Computer users fall into two groups:-
those that do backups
those that have never had a hard drive fail.
Back to top
View user's profile Send private message
augustin2
Apprentice
Apprentice


Joined: 16 Mar 2012
Posts: 188
Location: France

PostPosted: Mon Nov 19, 2012 7:32 am    Post subject: Reply with quote

Thank you very much for your help guys, I really appreciate it. But now it's a forking path that is in front of me. Which way to chose is a kind of dilemna.

Eventually, I havel tried BillWho s' suggestion that seemed a little bit faster. NeddySeagoon I must confess I dont really imagine what using or not using an initrd implies but it tells me that I have to read more about this and I preciously keep you suggestion at hand.
After trying BillWho s' suggestion, I think I went one step farther but I have a new message :

Quote:

Loading modules
::scanning for scsi_wait_scan .......................scsci_wait_scan loaded
::scanning for fuse .............. .......................fuse loaded

Hint : use parameter scandelay ................if you need waiting here

activating mdev
determining root device
!! Block device /dev/sdb7 is not a valid root device
!! Could not find the root block device in .
Please specify another value or press enter for the same , type "shell" for a shell or q to skip


Hum !


Last edited by augustin2 on Mon Nov 19, 2012 9:16 am; edited 1 time in total
Back to top
View user's profile Send private message
augustin2
Apprentice
Apprentice


Joined: 16 Mar 2012
Posts: 188
Location: France

PostPosted: Mon Nov 19, 2012 9:15 am    Post subject: Reply with quote

I have got it ! :P Thanks to you all guys, I am now entering the Gentoo wonderland.

Here is what I did:

Quote:
CONFIG_DEVTMPFS="y"
CONFIG_DEVTMPFS_MOUNT="y"

CONFIG_SATA_AHCI="y"
CONFIG_SATA_AHCI_PLATEFORM="y"

and both
Quote:

title Gentoo Linux
root (hd1,0)
kernel /boot/kernel boot=/dev/sdb7 rootfstype=ext3
initrd /boot/initramfs

and
Quote:
title Gentoo Linux
root (hd1,0)
kernel /boot/kernel initrd=/dev/ram0 real_root=/dev/sdb7 rootfstype=ext3
initrd /boot/initramfs


works .

Cheers !
Back to top
View user's profile Send private message
Display posts from previous:   
Reply to topic    Gentoo Forums Forum Index Installing Gentoo All times are GMT
Page 1 of 1

 
Jump to:  
You cannot post new topics in this forum
You cannot reply to topics in this forum
You cannot edit your posts in this forum
You cannot delete your posts in this forum
You cannot vote in polls in this forum