Bootloader problems

Bootloader problems

[Paolo Cremonese]

Hi all,
I have problems in generating a bootable device (CF)
During the setup the CF is connected to the host via an USB adapter.

These are the steps I do:

# fdisk /dev/sdb
   create a linux partition /dev/sdb1 and activate it

# mkfs.ext3 /dev/sdb1

# mount -t ext3 /dev/sdb1 /media/disk

# cd /media/disk
# tar
-xvf /home/paolo/oe/stuff/build/gpe-image/deploy/glibc/images/i586-generic/gpe-image-i586-generic.tar

and the filesystem is correctly on the CF

# cd boot
# mkdir grub
# cd grub
# < copy of grub files>
# grub ...

the menu.lst contains

title		OpenEmbedded Linux (hda1)
root		(hd0,0)
kernel		/boot/bzImage-2.6.21 root=/dev/hda1 ro
quiet


The system boots, but when the filesystem is created, the kernel crashes
with the message:

VFS: Cannot open root device "(hd0,0)" or unknown-block(0,0)
Please append a correct "root=" boot option
Kernel panic - not syncing: VFS: unable to mount root fs or
unknown-block(0,0)

but I don't understand what I have to do...

Thanks in advance
Paolo

Re: Bootloader problems

[Denys Dmytriyenko]

On Fri, Feb 27, 2009 at 12:37:32PM +0100, Paolo Cremonese wrote:
> Hi all,
> I have problems in generating a bootable device (CF)
> During the setup the CF is connected to the host via an USB adapter.
> 
> These are the steps I do:
> 
> # fdisk /dev/sdb
>    create a linux partition /dev/sdb1 and activate it
> 
> # mkfs.ext3 /dev/sdb1
> 
> # mount -t ext3 /dev/sdb1 /media/disk
> 
> # cd /media/disk
> # tar
> -xvf /home/paolo/oe/stuff/build/gpe-image/deploy/glibc/images/i586-generic/gpe-image-i586-generic.tar
> 
> and the filesystem is correctly on the CF
> 
> # cd boot
> # mkdir grub
> # cd grub
> # < copy of grub files>
> # grub ...
> 
> the menu.lst contains
> 
> title		OpenEmbedded Linux (hda1)
> root		(hd0,0)
> kernel		/boot/bzImage-2.6.21 root=/dev/hda1 ro
> quiet
> 
> 
> The system boots, but when the filesystem is created, the kernel crashes
> with the message:
> 
> VFS: Cannot open root device "(hd0,0)" or unknown-block(0,0)
> Please append a correct "root=" boot option
> Kernel panic - not syncing: VFS: unable to mount root fs or
> unknown-block(0,0)
> 
> but I don't understand what I have to do...

Please verify:

1. Your device, you are trying to boot, maps your CF at /dev/hda (or /dev/sda)
2. Your kernel has the support for the filesystem type you want - ext3/ext2
3. Your filesystem has static /dev/hda and enough /dev/hda? devnodes

-- 
Denys

Re: Bootloader problems

[Paolo Cremonese]

On ven, 2009-02-27 at 13:47 -0500, Denys Dmytriyenko wrote:
> On Fri, Feb 27, 2009 at 12:37:32PM +0100, Paolo Cremonese wrote:
> > Hi all,
> > I have problems in generating a bootable device (CF)
> > During the setup the CF is connected to the host via an USB adapter.
> > 
> > These are the steps I do:
> > 
> > # fdisk /dev/sdb
> >    create a linux partition /dev/sdb1 and activate it
> > 
> > # mkfs.ext3 /dev/sdb1
> > 
> > # mount -t ext3 /dev/sdb1 /media/disk
> > 
> > # cd /media/disk
> > # tar
> > -xvf /home/paolo/oe/stuff/build/gpe-image/deploy/glibc/images/i586-generic/gpe-image-i586-generic.tar
> > 
> > and the filesystem is correctly on the CF
> > 
> > # cd boot
> > # mkdir grub
> > # cd grub
> > # < copy of grub files>
> > # grub ...
> > 
> > the menu.lst contains
> > 
> > title		OpenEmbedded Linux (hda1)
> > root		(hd0,0)
> > kernel		/boot/bzImage-2.6.21 root=/dev/hda1 ro
> > quiet
> > 
> > 
> > The system boots, but when the filesystem is created, the kernel crashes
> > with the message:
> > 
> > VFS: Cannot open root device "(hd0,0)" or unknown-block(0,0)
> > Please append a correct "root=" boot option
> > Kernel panic - not syncing: VFS: unable to mount root fs or
> > unknown-block(0,0)
> > 
> > but I don't understand what I have to do...
> 
> Please verify:
> 
> 1. Your device, you are trying to boot, maps your CF at /dev/hda (or /dev/sda)
> 2. Your kernel has the support for the filesystem type you want - ext3/ext2
> 3. Your filesystem has static /dev/hda and enough /dev/hda? devnodes
> 

I have checked:

3. I find /dev/hda and devnodes /dev/hda1 to /dev/hda19

How can I check points 2 and 1?
for the point 1 I think yes because the CF is connected to the IDE, but
I'm not sure..
For the point 2, How can I check?

Many thanks,
Paolo

Re: Bootloader problems

[Anatoly Shipitsin]

On Sun, Mar 1, 2009 at 14:35, Paolo Cremonese <pisa.t@teledata-i.com> wrote:

> How can I check points 2 and 1?

1. You CF should be primary master in BIOS.
2. Check .config file from kernel source tree.