[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

Bug#457388: my guess is udev



On 07/01/2008, Geert Stappers <stappers@stappers.nl> wrote:
> Op 06-01-2008 om 15:26 schreef Richard van der Veen:
> > Again the kernel hangs with the message
> >
> > Linux.........................................................................
> > BIOS data check successful
> > Uncompressing Linux...  OK, booting the kernel.
> > PCI:BIOS BUG: MCFG area at f0000000 is not E820-reserved
> > PCI: Not using MMCONFIG
> > PCI: Failed to allocate mem resource #6:20000@90000000 for 0000:01:00.0
> > Loading , please wait....
> > ide0: I/O resource 0x3F6-0x3F6 not free.
> > ide0: ports already in use, skipping probe
> > ide1: I/O resource 0x376-0x376 not free.
> > ide1: ports already in use, skipping probe
> > mount: Mounting /dev/root on /root failed: No such device
> > mount: Mounting /root/dev/ on /dev/.static/dev failed: No such file or
> > directory
> > mount: Mounting /sys on /root/sys failed: No such file or directory
> > mount: Mounting /proc on /root/proc failed: No such file or directory
> > Target filesystem doesn't have /sbin/init

Sorry if my information is not sufficient enough, but i am not sure if
can pin-point exactly where the causes of my problem with using Debian
are. Maybe it is a problem in the debian specific kernel. Anyway.
Ubuntu, Mandrake, OpenSuse and Fedora do not give problems like this
on the same hardware.


> When I do `grep -i mount /var/log/syslog` on an installed system,
> I don't get a line like:
> > mount: Mounting /dev/root on /root failed: No such device
>
> What is '/dev/root'?
> I would expect something like '/dev/sda1'

Yes, Don't know.
Why? ...

> Why is it '/root'?
> I would expect '/'

Yes, me too, but  /etc/lilo.conf says clearly that /dev/sdf1 is the
partition which should be used as root partition. Which is recognized
by debian as the 200GB ATA disk on which installed Debian.


> I think^Wguess there is still some bootloader data on some disk
> (the computer has several disks) and that data is not overwritten
> during install. The computer boots from the wrong disk.
>

I have 3 disks in my computer. 2 ATA disks and 1 SATA disk. I can
change to boot order from these disks in the BIOS. When my 200GB ATA
disks boot i would like to boot Debian, When my 250 GB SATA disk boots
(is first boot device) i can boot Ubuntu 7.10 and when my 320 GB ATA
disk is first boot device i can boot OpenSuse 10.3 All disks have
indeed a boot loader in their masterboot record.

When i install debian from a testing-netinstall image on the 200 GB
ATA disk i get the problems i described. Ubuntu on the same disc gives
no problems, Fedora on the same disk also with the same boot order
from the BIOS gives no problems, Mandrake also does not give any
problems with the same disk order in the BIOS settings.

Debian Etch doesn't even see my ATA disks, and booting with generic
ata enabled gives a kernel OOPS.

Only Debian gives a message about MMCONFIG (also during boot from the
install CD) And i see this also back in the error messages after i
installed with a hanging kernel.



Reply to: