Bug #11980 “kernel-image-2.6.10-1-686: impossible to mount the r...” : Bugs : initrd-tools package : Ubuntu

Revision history for this message

Debian Bug Importer (debzilla) wrote on 2005-01-17:

#1

Message-Id: <email address hidden>
Date: Fri, 14 Jan 2005 11:37:46 +0100
From: Olivier Lecarme <email address hidden>
To: Debian Bug Tracking System <email address hidden>
Subject: kernel-image-2.6.10-1-686: impossible to mount the root partition on a SATA
disk

Package: kernel-image-2.6.10-1-686
Version: 2.6.10-3
Severity: critical
Justification: breaks the whole system

-- System Information:
Debian Release: 3.1
APT prefers unstable
APT policy: (500, 'unstable')
Architecture: i386 (i686)
Kernel: Linux 2.4.27-2-686
Locale: LANG=fr_FR, LC_CTYPE=fr_FR (charmap=ISO-8859-1)

Versions of packages kernel-image-2.6.10-1-686 depends on:
ii coreutils [fileutils] 5.2.1-2 The GNU core utilities
ii initrd-tools 0.1.76 tools to create initrd image for p
ii module-init-tools 3.1-rel-2 tools for managing Linux kernel mo

-- no debconf information
I have a Dell Optiplex computer with a SATA hard drive. Kernel 2.4 works
OK with the disk in non-SATA mode. Kernel 2.6 panics on booting with
the message /dev/console not found, preceded by a message from pivot_root
which does not found the root partition.
I tried both SATA modes in the BIOS: combination, or normal.
I tried root=/dev/hda5 or root=/dev/sda5 in the Grub menu.lst file.
I tried to omit initrd in this file.
I tried root=probe, point to /dev/hda5 in initrd, or root=/dev/sda5.
Note that /dev/[hs]da5 is in XFS mode.

Revision history for this message

Debian Bug Importer (debzilla) wrote on 2005-01-17:

#2

Message-ID: <email address hidden>
Date: Mon, 17 Jan 2005 13:29:52 +0900
From: Horms <email address hidden>
To: Olivier Lecarme <email address hidden>, <email address hidden>
Cc: <email address hidden>
Subject: Re: Bug#290474: kernel-image-2.6.10-1-686: impossible to mount the root partition on a SATA
disk

reassign 290474 initrd-tools
thanks

On Fri, Jan 14, 2005 at 11:37:46AM +0100, Olivier Lecarme wrote:
> Package: kernel-image-2.6.10-1-686
> Version: 2.6.10-3
> Severity: critical
> Justification: breaks the whole system
>
>
>
> -- System Information:
> Debian Release: 3.1
> APT prefers unstable
> APT policy: (500, 'unstable')
> Architecture: i386 (i686)
> Kernel: Linux 2.4.27-2-686
> Locale: LANG=fr_FR, LC_CTYPE=fr_FR (charmap=ISO-8859-1)
>
> Versions of packages kernel-image-2.6.10-1-686 depends on:
> ii coreutils [fileutils] 5.2.1-2 The GNU core utilities
> ii initrd-tools 0.1.76 tools to create initrd image for p
> ii module-init-tools 3.1-rel-2 tools for managing Linux kernel mo
>
> -- no debconf information
> I have a Dell Optiplex computer with a SATA hard drive. Kernel 2.4 works
> OK with the disk in non-SATA mode. Kernel 2.6 panics on booting with
> the message /dev/console not found, preceded by a message from pivot_root
> which does not found the root partition.

> I tried both SATA modes in the BIOS: combination, or normal.
> I tried root=/dev/hda5 or root=/dev/sda5 in the Grub menu.lst file.
> I tried to omit initrd in this file.

This almost certainly won't work, as the kernel-image doesn't
have enough drivers to boot more or less any system. These are
provided by the initrd image.

I would suspect that the prblem is that mkinitrd is not adding
the drivers that are needed for your system to the initrd image.
With this in mind I am reassigning the bug to initrd-tools.

Do you have any idea what modules are required for your system.
Do you have a working 2.6 debian kernel image. If so could
you provide the output of lsmod. Ditto for 2.4, though that is probably
less useful.

--
Horms

Message-ID: <20050117042952.GA4831@verge.net.au>
Date: Mon, 17 Jan 2005 13:29:52 +0900
From: Horms <horms@debian.org>
To: Olivier Lecarme <ol@unice.fr>, 290474@bugs.debian.org
Cc: control@bugs.debian.org
Subject: Re: Bug#290474: kernel-image-2.6.10-1-686: impossible to mount the root partition on a SATA
	disk

reassign 290474 initrd-tools
thanks

On Fri, Jan 14, 2005 at 11:37:46AM +0100, Olivier Lecarme wrote:
> Package: kernel-image-2.6.10-1-686
> Version: 2.6.10-3
> Severity: critical
> Justification: breaks the whole system
> 
> 
> 
> -- System Information:
> Debian Release: 3.1
>   APT prefers unstable
>   APT policy: (500, 'unstable')
> Architecture: i386 (i686)
> Kernel: Linux 2.4.27-2-686
> Locale: LANG=fr_FR, LC_CTYPE=fr_FR (charmap=ISO-8859-1)
> 
> Versions of packages kernel-image-2.6.10-1-686 depends on:
> ii  coreutils [fileutils]         5.2.1-2    The GNU core utilities
> ii  initrd-tools                  0.1.76     tools to create initrd image for p
> ii  module-init-tools             3.1-rel-2  tools for managing Linux kernel mo
> 
> -- no debconf information
> I have a Dell Optiplex computer with a SATA hard drive. Kernel 2.4 works
> OK with the disk in non-SATA mode. Kernel 2.6 panics on booting with
> the message /dev/console not found, preceded by a message from pivot_root
> which does not found the root partition.

> I tried both SATA modes in the BIOS: combination, or normal.
> I tried root=/dev/hda5 or root=/dev/sda5 in the Grub menu.lst file.
> I tried to omit initrd in this file.

This almost certainly won't work, as the kernel-image doesn't
have enough drivers to boot more or less any system. These are
provided by the initrd image.

I would suspect that the prblem is that mkinitrd is not adding
the drivers that are needed for your system to the initrd image.
With this in mind I am reassigning the bug to initrd-tools.

Do you have any idea what modules are required for your system.
Do you have a working 2.6 debian kernel image. If so could
you provide the output of lsmod. Ditto for 2.4, though that is probably
less useful.

-- 
Horms

Revision history for this message

Øivind Hoel (eruin) wrote on 2005-01-17:

#3

Download full text (4.6 KiB)

I have the same(?) issue. Root (ext3) located on /dev/sda5, which is a non-raid
sata disk.
Problem first occurred in 2.6.10-1, still here on 2.6.10-2. I'm running the k7
flavour.
Nothing happens when selecting the 2.6.10 kernels from grub. The last thing that
draws
on my screen is "Starting Ubuntu" - after that nothing happens.

2.6.9-1-k7 runs fine, and here's relevant(?) output while running it:

Output of lspci:

eruin@ubuntu:~ $ lspci
0000:00:00.0 Host bridge: VIA Technologies, Inc. VT8377 [KT400/KT600 AGP] Host
Bridge (rev 80)
0000:00:01.0 PCI bridge: VIA Technologies, Inc. VT8237 PCI Bridge
0000:00:0b.0 Ethernet controller: Realtek Semiconductor Co., Ltd. RTL-8029(AS)
0000:00:0f.0 RAID bus controller: VIA Technologies, Inc. VIA VT6420 SATA RAID
Controller (rev 80)
0000:00:0f.1 IDE interface: VIA Technologies, Inc.
VT82C586A/B/VT82C686/A/B/VT823x/A/C PIPC Bus Master IDE (rev 06)
0000:00:10.0 USB Controller: VIA Technologies, Inc. VT82xxxxx UHCI USB 1.1
Controller (rev 81)
0000:00:10.1 USB Controller: VIA Technologies, Inc. VT82xxxxx UHCI USB 1.1
Controller (rev 81)
0000:00:10.2 USB Controller: VIA Technologies, Inc. VT82xxxxx UHCI USB 1.1
Controller (rev 81)
0000:00:10.3 USB Controller: VIA Technologies, Inc. VT82xxxxx UHCI USB 1.1
Controller (rev 81)
0000:00:10.4 USB Controller: VIA Technologies, Inc. USB 2.0 (rev 86)
0000:00:11.0 ISA bridge: VIA Technologies, Inc. VT8237 ISA bridge [K8T800
South]0000:00:11.5 Multimedia audio controller: VIA Technologies, Inc.
VT8233/A/8235/8237 AC97 Audio Controller (rev 60)
0000:00:12.0 Ethernet controller: VIA Technologies, Inc. VT6102 [Rhine-II] (rev 78)
0000:01:00.0 VGA compatible controller: nVidia Corporation NV31 [GeForce FX
5600] (rev a1)

And lsmod:

eruin@ubuntu:~ $ lsmod
Module Size Used by
binfmt_misc 11528 1
proc_intf 3972 0
freq_table 4036 0
cpufreq_userspace 5208 0
cpufreq_ondemand 6108 0
cpufreq_powersave 1664 0
button 6544 0
battery 9284 0
ac 4740 0
ipv6 257408 15
af_packet 22280 2
tsdev 7552 0
usbhid 32000 0
via_rhine 21252 0
mii 4928 1 via_rhine
snd_via82xx 27236 2
snd_ac97_codec 70544 1 snd_via82xx
snd_pcm_oss 52264 1
snd_mixer_oss 19648 2 snd_pcm_oss
snd_pcm 95368 2 snd_via82xx,snd_pcm_oss
snd_timer 25028 1 snd_pcm
snd_page_alloc 9800 2 snd_via82xx,snd_pcm
gameport 4480 1 snd_via82xx
snd_mpu401_uart 7744 1 snd_via82xx
snd_rawmidi 24804 1 snd_mpu401_uart
snd_seq_device 7944 1 snd_rawmidi
snd 55140 9
snd_via82xx,snd_ac97_codec,snd_pcm_oss,snd_mixer_oss,snd_pcm,snd_timer,snd_mpu401_uart,snd_rawmidi,snd_seq_device
soundcore 10080 3 snd
ehci_hcd 31108 0
uhci_hcd 32016 0
usbcore 116260 5 usbhid,ehci_hcd,uhci_hcd
via82cxxx 13724 1
ne2k_pci 9248 0
8390 10496 1 ne2k_pci
crc32 4224 ...

I have the same(?) issue. Root (ext3) located on /dev/sda5, which is a non-raid
sata disk.
Problem first occurred in 2.6.10-1, still here on 2.6.10-2. I'm running the k7
flavour.
Nothing happens when selecting the 2.6.10 kernels from grub. The last thing that
draws
on my screen is "Starting Ubuntu" - after that nothing happens.

2.6.9-1-k7 runs fine, and here's relevant(?) output while running it:

Output of lspci:

eruin@ubuntu:~ $ lspci
0000:00:00.0 Host bridge: VIA Technologies, Inc. VT8377 [KT400/KT600 AGP] Host
Bridge (rev 80)
0000:00:01.0 PCI bridge: VIA Technologies, Inc. VT8237 PCI Bridge
0000:00:0b.0 Ethernet controller: Realtek Semiconductor Co., Ltd. RTL-8029(AS)
0000:00:0f.0 RAID bus controller: VIA Technologies, Inc. VIA VT6420 SATA RAID
Controller (rev 80)
0000:00:0f.1 IDE interface: VIA Technologies, Inc.
VT82C586A/B/VT82C686/A/B/VT823x/A/C PIPC Bus Master IDE (rev 06)
0000:00:10.0 USB Controller: VIA Technologies, Inc. VT82xxxxx UHCI USB 1.1
Controller (rev 81)
0000:00:10.1 USB Controller: VIA Technologies, Inc. VT82xxxxx UHCI USB 1.1
Controller (rev 81)
0000:00:10.2 USB Controller: VIA Technologies, Inc. VT82xxxxx UHCI USB 1.1
Controller (rev 81)
0000:00:10.3 USB Controller: VIA Technologies, Inc. VT82xxxxx UHCI USB 1.1
Controller (rev 81)
0000:00:10.4 USB Controller: VIA Technologies, Inc. USB 2.0 (rev 86)
0000:00:11.0 ISA bridge: VIA Technologies, Inc. VT8237 ISA bridge [K8T800
South]0000:00:11.5 Multimedia audio controller: VIA Technologies, Inc.
VT8233/A/8235/8237 AC97 Audio Controller (rev 60)
0000:00:12.0 Ethernet controller: VIA Technologies, Inc. VT6102 [Rhine-II] (rev 78)
0000:01:00.0 VGA compatible controller: nVidia Corporation NV31 [GeForce FX
5600] (rev a1)

And lsmod:

eruin@ubuntu:~ $ lsmod
Module                  Size  Used by
binfmt_misc            11528  1
proc_intf               3972  0
freq_table              4036  0
cpufreq_userspace       5208  0
cpufreq_ondemand        6108  0
cpufreq_powersave       1664  0
button                  6544  0
battery                 9284  0
ac                      4740  0
ipv6                  257408  15
af_packet              22280  2
tsdev                   7552  0
usbhid                 32000  0
via_rhine              21252  0
mii                     4928  1 via_rhine
snd_via82xx            27236  2
snd_ac97_codec         70544  1 snd_via82xx
snd_pcm_oss            52264  1
snd_mixer_oss          19648  2 snd_pcm_oss
snd_pcm                95368  2 snd_via82xx,snd_pcm_oss
snd_timer              25028  1 snd_pcm
snd_page_alloc          9800  2 snd_via82xx,snd_pcm
gameport                4480  1 snd_via82xx
snd_mpu401_uart         7744  1 snd_via82xx
snd_rawmidi            24804  1 snd_mpu401_uart
snd_seq_device          7944  1 snd_rawmidi
snd                    55140  9
snd_via82xx,snd_ac97_codec,snd_pcm_oss,snd_mixer_oss,snd_pcm,snd_timer,snd_mpu401_uart,snd_rawmidi,snd_seq_device
soundcore              10080  3 snd
ehci_hcd               31108  0
uhci_hcd               32016  0
usbcore               116260  5 usbhid,ehci_hcd,uhci_hcd
via82cxxx              13724  1
ne2k_pci                9248  0
8390                   10496  1 ne2k_pci
crc32                   4224  2 via_rhine,8390
pci_hotplug            33520  0
via_agp                 9408  1
agpgart                33704  2 via_agp
floppy                 59216  0
pcspkr                  3560  0
rtc                    12536  0
nls_iso8859_1           3968  3
nls_cp437               5632  3
vfat                   14464  3
fat                    46048  1 vfat
md                     47628  0
dm_mod                 58044  1
nvidia               3470492  12
parport_pc             36804  0
lp                     10664  0
parport                40712  2 parport_pc,lp
evdev                   9408  0
ide_generic             1344  0
ide_disk               20032  3
ide_cd                 41760  0
ide_core              139440  4 via82cxxx,ide_generic,ide_disk,ide_cd
cdrom                  39900  1 ide_cd
mousedev               11352  1
psmouse                24396  0
ext3                  123624  2
jbd                    62552  1 ext3
mbcache                 9028  1 ext3
sd_mod                 17616  5
sata_via                7172  9
libata                 44164  1 sata_via
scsi_mod              123276  2 sd_mod,libata
unix                   28212  919
thermal                13128  0
processor              17384  1 thermal
fan                     3908  0
fbcon                  39808  0
font                    8256  1 fbcon
vesafb                  6688  0
cfbcopyarea             3840  1 vesafb
cfbimgblt               2944  1 vesafb
cfbfillrect             3520  1 vesafb

Revision history for this message

Fabio Massimo Di Nitto (fabbione) wrote on 2005-01-18:

#4

It would be more interesting to see where it hangs. Can you boot without the
quite options?
and attach the relevant bits here?

Revision history for this message

Øivind Hoel (eruin) wrote on 2005-01-18:

#5

without quiet when booting the 2.6.10-kernel Edit (72.3 KiB, image/jpeg)

Created an attachment (id=1065)
without quiet when booting the 2.6.10-kernel

Here's what I get (grabbed an image with my cam instead of writing it down;)

Revision history for this message

Debian Bug Importer (debzilla) wrote on 2005-01-18:

#6

Message-Id: <email address hidden>
Date: Tue, 18 Jan 2005 14:22:31 +0100
From: "Olivier Lecarme" <email address hidden>
To: <email address hidden>
Subject: new attempts to solve this problem

Somebody told me that there could be an incompatibility between Grub and
Xfs, thus I switched to Lilo. The result is the same, but with a
different error message: /sbin/init is not found.

Maybe this will help...

--

Olivier Lecarme

Revision history for this message

Fabio Massimo Di Nitto (fabbione) wrote on 2005-01-18:

#7

*** Bug 12017 has been marked as a duplicate of this bug. ***

Revision history for this message

Debian Bug Importer (debzilla) wrote on 2005-01-18:

#8

Message-ID: <email address hidden>
Date: Tue, 18 Jan 2005 17:49:30 +0100
From: maximilian attems <email address hidden>
To: Olivier Lecarme <email address hidden>, <email address hidden>
Subject: Re: Bug#290474: new attempts to solve this problem

On Tue, 18 Jan 2005, Olivier Lecarme wrote:

> Somebody told me that there could be an incompatibility between Grub and
> Xfs, thus I switched to Lilo. The result is the same, but with a
> different error message: /sbin/init is not found.
>
> Maybe this will help...
> --
>
>
> Olivier Lecarme

no please provide full error message.

--
maks

Revision history for this message

Øivind Hoel (eruin) wrote on 2005-01-25:

#9

linux-image-2.6.10-2-k7 ( Filename:
pool/main/l/linux-source-2.6.10/linux-image-2.6.10-2-k7_2.6.10-11_i386.deb )
resolves this bug for me. I can now boot from my SATA drive just fine.

Revision history for this message

Debian Bug Importer (debzilla) wrote on 2005-01-28:

#10

Message-ID: <email address hidden>
Date: Fri, 28 Jan 2005 17:11:39 +1100
From: Jason Thomas <email address hidden>
To: <email address hidden>
Subject: FYI

you will need to add your required modules before you install the
kernel or you can run mkinitrd by hand after having added your modules.

jason@bart:~$ cat /etc/mkinitrd/modules
# /etc/mkinitrd/modules: Kernel modules to load for initrd.
#
# This file should contain the names of kernel modules and their
# arguments
# (if any) that are needed to mount the root file system, one per line.
# Comments begin with a `#', and everything on the line after them are
# ignored.
#
# You must run mkinitrd(8) to effect this change.
#
# Examples:
#
# ext2
# wd io=0x300
scsi_mod
sd_mod
libata
sata_sil
jason@bart:~$

--
Jason

"I hope you learn speaking English proper I hope speak I me you."
-- Branden Robinson, 2001

Revision history for this message

Debian Bug Importer (debzilla) wrote on 2005-01-31:

#11

Message-ID: <email address hidden>
Date: Sun, 30 Jan 2005 18:38:57 +0200
From: "AKL. Mantas Kriauciunas" <email address hidden>
To: <email address hidden>
Cc: <email address hidden>
Subject: I can't boot 2.6.8 and 2.6.10 kernels on my system, while 2.6.7 starts without problems

Hi,

I can't boot 2.6.8 and 2.6.10 kernels on my system while 2.6.7 was
installed on same system and starts without problems few months ago.

I got the same error like others - cannot open dev/console, preceded
by a message from pivot_root which does not found the root partition.

I use grub and xfs file system on SATA drive (hde) on system with
Athlon (k7) CPU.

Tried several initrd versions (0.1.77, 0.1.76, 0.1.73, 0.1.67), but
without success :( AFAIK when I installed 2.6.7 kernel, then
initrd-tools version 0.1.67 were installed on my system and initrd was
generated corectly, this kernel starts without problems.

It seems bugs 290474 and 271038 are related - in both cases kernel
doesn't start with message "cannot open dev/console: No such file"

I can send initrd, generated when I install kernel-image 2.6.8 and
2.6.10, which doesn't start.

--=20
Labanaktis/Good luck,
Mantas Kriau=C4=8Di=C5=ABnas Jabber ID: <email address hidden> GPG ID: 43535BD5
Public organization "Open Source for Lithuania" - www.akl.lt

Revision history for this message

Debian Bug Importer (debzilla) wrote on 2005-01-31:

#12

Message-ID: <email address hidden>
Date: Mon, 31 Jan 2005 13:13:24 +0300
From: Horms <email address hidden>
To: "AKL. Mantas Kriauciunas" <email address hidden>, <email address hidden>
Subject: Re: Bug#290474: I can't boot 2.6.8 and 2.6.10 kernels on my system,
while 2.6.7 starts without problems

On Sun, Jan 30, 2005 at 06:38:57PM +0200, AKL. Mantas Kriauciunas wrote:
> Hi,
>
> I can't boot 2.6.8 and 2.6.10 kernels on my system while 2.6.7 was
> installed on same system and starts without problems few months ago.
>
> I got the same error like others - cannot open dev/console, preceded
> by a message from pivot_root which does not found the root partition.
>
> I use grub and xfs file system on SATA drive (hde) on system with
> Athlon (k7) CPU.
>
> Tried several initrd versions (0.1.77, 0.1.76, 0.1.73, 0.1.67), but
> without success :( AFAIK when I installed 2.6.7 kernel, then
> initrd-tools version 0.1.67 were installed on my system and initrd was
> generated corectly, this kernel starts without problems.
>
> It seems bugs 290474 and 271038 are related - in both cases kernel
> doesn't start with message "cannot open dev/console: No such file"
>
> I can send initrd, generated when I install kernel-image 2.6.8 and
> 2.6.10, which doesn't start.

If you uncomress the image you should be able to mount it using a
loopback device. And then inspect what is inside. Alternatelvely,
just regenerate the image using mkinitrd. If you add the -k argument
then it will leave what went into the image in a directory in /tmp.

In any case, the most likely cause of this is that the drivers
required to mount your root partition were not persent. This could
be a FS driver, but more likely an IDE or SCSI driver of some sort.
Can you give a little more information on what your root partition
lives on. Also, what modules are loaded up on the working 2.6.7 system?
By comparing this to what ends up on the CD, you can probably shed
some light on what has gone astray.

--
Horms

Message-ID: <20050131101321.GF5119@verge.net.au>
Date: Mon, 31 Jan 2005 13:13:24 +0300
From: Horms <horms@debian.org>
To: "AKL. Mantas Kriauciunas" <mantas@akl.lt>, 290474@bugs.debian.org
Subject: Re: Bug#290474: I can't boot 2.6.8 and 2.6.10 kernels on my system,
	while 2.6.7 starts without problems

On Sun, Jan 30, 2005 at 06:38:57PM +0200, AKL. Mantas Kriauciunas wrote:
> Hi,
> 
> I can't boot 2.6.8 and 2.6.10 kernels on my system while 2.6.7 was
> installed on same system and starts without problems few months ago.
> 
> I got the same error like others - cannot open dev/console, preceded
> by a message from pivot_root which does not found the root partition.
> 
> I use grub and xfs file system on SATA drive (hde) on system with
> Athlon (k7) CPU.
> 
> Tried several initrd versions (0.1.77, 0.1.76, 0.1.73, 0.1.67), but
> without success :( AFAIK when I installed 2.6.7 kernel, then
> initrd-tools version 0.1.67 were installed on my system and initrd was
> generated corectly, this kernel starts without problems.
> 
> It seems bugs 290474 and 271038 are related - in both cases kernel
> doesn't start with message "cannot open dev/console: No such file"
> 
> I can send initrd, generated when I install kernel-image 2.6.8 and
> 2.6.10, which doesn't start.

If you uncomress the image you should be able to mount it using a
loopback device.  And then inspect what is inside. Alternatelvely,
just regenerate the image using mkinitrd. If you add the -k argument
then it will leave what went into the image in a directory in /tmp.

In any case, the most likely cause of this is that the drivers
required to mount your root partition were not persent. This could
be a FS driver, but more likely an IDE or SCSI driver of some sort.
Can you give a little more information on what your root partition
lives on. Also, what modules are loaded up on the working 2.6.7 system?
By comparing this to what ends up on the CD, you can probably shed
some light on what has gone astray.

-- 
Horms

Revision history for this message

Debian Bug Importer (debzilla) wrote on 2005-01-31:

#13

Message-ID: <email address hidden>
Date: Mon, 31 Jan 2005 23:28:24 +0100
From: maximilian attems <email address hidden>
To: "AKL. Mantas Kriauciunas" <email address hidden>, <email address hidden>
Cc: <email address hidden>
Subject: Re: Bug#290474: I can't boot 2.6.8 and 2.6.10 kernels on my system,
while 2.6.7 starts without problems

On Sun, 30 Jan 2005, AKL. Mantas Kriauciunas wrote:

> I can't boot 2.6.8 and 2.6.10 kernels on my system while 2.6.7 was
> installed on same system and starts without problems few months ago.
>
> I got the same error like others - cannot open dev/console, preceded
> by a message from pivot_root which does not found the root partition.
>
> I use grub and xfs file system on SATA drive (hde) on system with
^^^
> Athlon (k7) CPU.
>
> Tried several initrd versions (0.1.77, 0.1.76, 0.1.73, 0.1.67), but
> without success :( AFAIK when I installed 2.6.7 kernel, then
> initrd-tools version 0.1.67 were installed on my system and initrd was
> generated corectly, this kernel starts without problems.
>
> It seems bugs 290474 and 271038 are related - in both cases kernel
> doesn't start with message "cannot open dev/console: No such file"
>
> I can send initrd, generated when I install kernel-image 2.6.8 and
> 2.6.10, which doesn't start.

after 2.6.7 the sata device name against change back to scsi style,
aka sdxN

it looks like you are specifying the wrong devie name.
hope that helps
thanks for your feedback

--
maks

Revision history for this message

Debian Bug Importer (debzilla) wrote on 2005-02-01:

#14

Message-ID: <email address hidden>
Date: Tue, 01 Feb 2005 20:22:30 +0100
From: "Harald Dunkel" <email address hidden>
To: maximilian attems <email address hidden>, <email address hidden>
CC: "AKL. Mantas Kriauciunas" <email address hidden>, <email address hidden>
Subject: Re: Bug#271038: Bug#290474: I can't boot 2.6.8 and 2.6.10 kernels
on my system, while 2.6.7 starts without problems

--------------enig4F917BDFC44B125B575E2F98
Content-Type: text/plain; charset=us-ascii; format=flowed
Content-Transfer-Encoding: 7bit

Hi Maximilian,

Since some kernel 2.6.x SATA devices are part of the
SCSI layer. This can be configured back to the
IDE layer, AFAIK. See the kernel configuration and
build a new kernel.

But the SCSI layer works pretty well. If you need
to switch back to kernel 2.4.x sometimes, then I would
suggest to label the partitions of your harddisks
(see man tune2fs, option -L, or man reiserfstune, -l).
You could use something like

LABEL=root / ext2 defaults 0 1
LABEL=swap none swap sw 0 0
LABEL=home /home ext2 defaults 0 1

in your /etc/fstab, instead of /dev/hda1 or /dev/sda1.

Regards

Harri

--------------enig4F917BDFC44B125B575E2F98
Content-Type: application/pgp-signature; name="signature.asc"
Content-Description: OpenPGP digital signature
Content-Disposition: attachment; filename="signature.asc"

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.2.5 (GNU/Linux)
Comment: Using GnuPG with Thunderbird - http://enigmail.mozdev.org

iD8DBQFB/9b6UTlbRTxpHjcRAhFwAJ9wo28xytS2rfX3zgQSjdr3OzdlHwCeP9cR
d3wR7JjP1xOMJUv+rPreJd0=
=oXZP
-----END PGP SIGNATURE-----

--------------enig4F917BDFC44B125B575E2F98--

Revision history for this message

Debian Bug Importer (debzilla) wrote on 2005-02-11:

#15

Message-Id: <email address hidden>
Date: Fri, 11 Feb 2005 11:15:47 +0200
From: Vassilii Khachaturov <email address hidden>
To: <email address hidden>
Cc: <email address hidden>, <email address hidden>
Subject: are you sure swap can be labeled?

> You could use something like
>
> LABEL=root / ext2 defaults 0 1
> LABEL=swap none swap sw 0 0
> LABEL=home /home ext2 defaults 0 1
>
> in your /etc/fstab, instead of /dev/hda1 or /dev/sda1.

Is your fstab example a real life one, or fictional? in the 1st case,
how did you manage to have the swap labeled??

I don't know how can one label a swap partition, if at all.
mkswap/swapon/swapoff don't seem to be providing such an option.
I know I can remove the swap partition and create another
one with one big file on it to hold the swap, but I suspect from the
architectural reasons this will be worse than using a dedicated partition.

I have suffered my share of problems with trying to keep
2.4 and 2.6 going together smoothly on the same machine
(see http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=286515 )
and came up with nothing better than going single and
moving the appropriate fstab (sda flavoured for 2.6 and hda for 2.4)
in place. BTW, I have never figured how to force the cdrw
not to work in the ide-scsi emulation mode in 2.6; even with the
ide-cd driver preloaded by /etc/modules and an option

options ide-scsi ignore=hdd

added to the modules.conf (via update-modutils), the scsi
emulation still grabs hdd (somehow pulled in by the sata_sil?)

Regards,
vassilii

Revision history for this message

Debian Bug Importer (debzilla) wrote on 2005-02-11:

#16

Message-ID: <email address hidden>
Date: Fri, 11 Feb 2005 18:37:38 +0100
From: maximilian attems <email address hidden>
To: <email address hidden>
Subject: strange mixture of bugs(2)

severity 290474 important
stop

Revision history for this message

Debian Bug Importer (debzilla) wrote on 2005-03-29:

#17

Message-ID: <email address hidden>
Date: Tue, 29 Mar 2005 06:55:20 +0200
From: Harald Dunkel <email address hidden>
To: Vassilii Khachaturov <email address hidden>
CC: <email address hidden>, <email address hidden>
Subject: Re: are you sure swap can be labeled?

--------------enig7EACE6DBE7248C58B8DE1DCD
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit

Vassilii Khachaturov wrote:
>>You could use something like
>>
>>LABEL=root / ext2 defaults 0 1
>>LABEL=swap none swap sw 0 0
>>LABEL=home /home ext2 defaults 0 1
>>
>>in your /etc/fstab, instead of /dev/hda1 or /dev/sda1.
>
>
> Is your fstab example a real life one, or fictional? in the 1st case,
> how did you manage to have the swap labeled??
>

mkswap -L myswap /dev/sda2

> I have suffered my share of problems with trying to keep
> 2.4 and 2.6 going together smoothly on the same machine
> (see http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=286515 )
> and came up with nothing better than going single and
> moving the appropriate fstab (sda flavoured for 2.6 and hda for 2.4)
> in place. BTW, I have never figured how to force the cdrw
> not to work in the ide-scsi emulation mode in 2.6; even with the
> ide-cd driver preloaded by /etc/modules and an option
>
> options ide-scsi ignore=hdd
>
> added to the modules.conf (via update-modutils), the scsi
> emulation still grabs hdd (somehow pulled in by the sata_sil?)
>

This is obsolete. Try something like

cdrecord /dev/cdrom my.iso

for writing CDs, regardless whether it is SCSI or IDE.

Sorry for the late response. Somehow your EMail got marked
as read in my Inbox.

Regards

Harri

--------------enig7EACE6DBE7248C58B8DE1DCD
Content-Type: application/pgp-signature; name="signature.asc"
Content-Description: OpenPGP digital signature
Content-Disposition: attachment; filename="signature.asc"

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.0 (GNU/Linux)
Comment: Using GnuPG with Thunderbird - http://enigmail.mozdev.org

iD8DBQFCSN+9UTlbRTxpHjcRAi2tAJ9T+EaTxZLR2uKG03u1gASOenfQVwCdEao4
HYw2mzXTsVXxFTveTCFWUuI=
=gjWQ
-----END PGP SIGNATURE-----

--------------enig7EACE6DBE7248C58B8DE1DCD--

Message-ID: <4248DFB8.4000904@t-online.de>
Date: Tue, 29 Mar 2005 06:55:20 +0200
From: Harald Dunkel <harald.dunkel@t-online.de>
To: Vassilii Khachaturov <vassilii@tarunz.org>
CC: 286515@bugs.debian.org,  290474@bugs.debian.org
Subject: Re: are you sure swap can be labeled?

--------------enig7EACE6DBE7248C58B8DE1DCD
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit

Vassilii Khachaturov wrote:
>>You could use something like
>>
>>LABEL=root /      ext2    defaults    0       1
>>LABEL=swap none   swap    sw          0       0
>>LABEL=home /home  ext2    defaults    0       1
>>
>>in your /etc/fstab, instead of /dev/hda1 or /dev/sda1.
>
>
> Is your fstab example a real life one, or fictional? in the 1st case,
> how did you manage to have the swap labeled??
>

mkswap -L myswap /dev/sda2

> I have suffered my share of problems with trying to keep
> 2.4 and 2.6 going together smoothly on the same machine
> (see http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=286515 )
> and came up with nothing better than going single and
> moving the appropriate fstab (sda flavoured for 2.6 and hda for 2.4)
> in place. BTW, I have never figured how to force the cdrw
> not to work in the ide-scsi emulation mode in 2.6; even with the
> ide-cd driver preloaded by /etc/modules and an option
>
>  options ide-scsi ignore=hdd
>
> added to the modules.conf (via update-modutils), the scsi
> emulation still grabs hdd (somehow pulled in by the sata_sil?)
>

This is obsolete. Try something like

cdrecord /dev/cdrom my.iso

for writing CDs, regardless whether it is SCSI or IDE.

Sorry for the late response. Somehow your EMail got marked
as read in my Inbox.

Regards

Harri

--------------enig7EACE6DBE7248C58B8DE1DCD
Content-Type: application/pgp-signature; name="signature.asc"
Content-Description: OpenPGP digital signature
Content-Disposition: attachment; filename="signature.asc"

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.0 (GNU/Linux)
Comment: Using GnuPG with Thunderbird - http://enigmail.mozdev.org

iD8DBQFCSN+9UTlbRTxpHjcRAi2tAJ9T+EaTxZLR2uKG03u1gASOenfQVwCdEao4
HYw2mzXTsVXxFTveTCFWUuI=
=gjWQ
-----END PGP SIGNATURE-----

--------------enig7EACE6DBE7248C58B8DE1DCD--

Revision history for this message

Debian Bug Importer (debzilla) wrote on 2005-03-29:

#18

Message-ID: <email address hidden>
Date: Tue, 29 Mar 2005 14:47:13 +0200 (IST)
From: Vassilii Khachaturov <email address hidden>
To: Harald Dunkel <email address hidden>
cc: <email address hidden>, <email address hidden>
Subject: Re: are you sure swap can be labeled?

On Tue, 29 Mar 2005, Harald Dunkel wrote:

> Vassilii Khachaturov wrote:
> >>You could use something like
> >>
> >>LABEL=root / ext2 defaults 0 1
> >>LABEL=swap none swap sw 0 0
> >>LABEL=home /home ext2 defaults 0 1
> >>
> >>in your /etc/fstab, instead of /dev/hda1 or /dev/sda1.
> >
> >
> > Is your fstab example a real life one, or fictional? in the 1st case,
> > how did you manage to have the swap labeled??
> >
>
> mkswap -L myswap /dev/sda2

-L doesn't work here:

travel:/home/vassilii# mkswap -L swap /dev/hda8
Usage: mkswap [-c] [-v0|-v1] [-pPAGESZ] /dev/name [blocks]
travel:/home/vassilii# mkswap --version
mkswap from util-linux-2.12
travel:/home/vassilii# dlocate /sbin/mkswap
util-linux: /sbin/mkswap
travel:/home/vassilii# dpkg --status util-linux
Package: util-linux
Essential: yes
Status: install ok installed
Priority: required
Section: base
Installed-Size: 976
Maintainer: LaMont Jones <email address hidden>
Architecture: i386
Version: 2.12-10
[snip]

What version are you using?

> > options ide-scsi ignore=hdd
> >
> > added to the modules.conf (via update-modutils), the scsi
> > emulation still grabs hdd (somehow pulled in by the sata_sil?)
> >
> This is obsolete.

What is obsolete? I know that the scsi emulation for cdrw is obsolete,
but I was asking how to make sure that it doesn't happen in 2.6,
even when the SATA hard drive forces the SCSI storage drivers into existence.

> Try something like
>
> cdrecord /dev/cdrom my.iso
>
> for writing CDs, regardless whether it is SCSI or IDE.

Yeah, and if /dev/cdrom (/dev/cdrw in my case; the cdrom is another -
R/O - device) is mapped to a scsi emulation device, I get an error.
If I force a link cdrw -> hdd, it doesn't work at all because of
the conflict with the scsi emulation layer (AFAIU you may not use
an IDE device directly once it's grabbed by the scsi emulation).

(I'm away from the PC in question at this time, otherwise I would
have cited the precise error msgs. If you need additional input,
please tell me.)

Message-ID: <Pine.LNX.4.44.0503291436390.10956-100000@stalker.iGuide.co.il>
Date: Tue, 29 Mar 2005 14:47:13 +0200 (IST)
From: Vassilii Khachaturov <vassilii@tarunz.org>
To: Harald Dunkel <harald.dunkel@t-online.de>
cc: 286515@bugs.debian.org, <290474@bugs.debian.org>
Subject: Re: are you sure swap can be labeled?

On Tue, 29 Mar 2005, Harald Dunkel wrote:

> Vassilii Khachaturov wrote:
> >>You could use something like
> >>
> >>LABEL=root /      ext2    defaults    0       1
> >>LABEL=swap none   swap    sw          0       0
> >>LABEL=home /home  ext2    defaults    0       1
> >>
> >>in your /etc/fstab, instead of /dev/hda1 or /dev/sda1.
> >
> >
> > Is your fstab example a real life one, or fictional? in the 1st case,
> > how did you manage to have the swap labeled??
> >
>
> mkswap -L myswap /dev/sda2

-L doesn't work here:

travel:/home/vassilii# mkswap -L swap /dev/hda8
	Usage: mkswap [-c] [-v0|-v1] [-pPAGESZ] /dev/name [blocks]
	travel:/home/vassilii# mkswap --version
	mkswap from util-linux-2.12
	travel:/home/vassilii# dlocate /sbin/mkswap
	util-linux: /sbin/mkswap
	travel:/home/vassilii# dpkg --status util-linux
	Package: util-linux
	Essential: yes
	Status: install ok installed
	Priority: required
	Section: base
	Installed-Size: 976
	Maintainer: LaMont Jones <lamont@debian.org>
	Architecture: i386
	Version: 2.12-10
	[snip]

What version are you using?

> >  options ide-scsi ignore=hdd
> >
> > added to the modules.conf (via update-modutils), the scsi
> > emulation still grabs hdd (somehow pulled in by the sata_sil?)
> >
> This is obsolete.

What is obsolete? I know that the scsi emulation for cdrw is obsolete,
but I was asking how to make sure that it doesn't happen in 2.6,
even when the SATA hard drive forces the SCSI storage drivers into existence.

> Try something like
>
> 	cdrecord /dev/cdrom my.iso
>
> for writing CDs, regardless whether it is SCSI or IDE.

Yeah, and if /dev/cdrom (/dev/cdrw in my case; the cdrom is another -
R/O - device) is mapped to a scsi emulation device, I get an error.
If I force a link cdrw -> hdd, it doesn't work at all because of
the conflict with the scsi emulation layer (AFAIU you may not use
an IDE device directly once it's grabbed by the scsi emulation).

(I'm away from the PC in question at this time, otherwise I would
have cited the precise error msgs. If you need additional input,
please tell me.)

Revision history for this message

Debian Bug Importer (debzilla) wrote on 2005-03-30:

#19

Message-ID: <email address hidden>
Date: Wed, 30 Mar 2005 06:15:59 +0200
From: Harald Dunkel <email address hidden>
To: Vassilii Khachaturov <email address hidden>
CC: <email address hidden>, <email address hidden>
Subject: Re: are you sure swap can be labeled?

--------------enig5AF8F5363C5D9B4DF11B623E
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit

Vassilii Khachaturov wrote:
> On Tue, 29 Mar 2005, Harald Dunkel wrote:
>>
>>mkswap -L myswap /dev/sda2
>
> -L doesn't work here:
>
> [snip]
>
> What version are you using?
>

% mkswap --version
mkswap from util-linux-2.12p
% mkswap --help
Usage: mkswap [-c] [-v0|-v1] [-pPAGESZ] [-L label] /dev/name [blocks]

>
> What is obsolete? I know that the scsi emulation for cdrw is obsolete,
> but I was asking how to make sure that it doesn't happen in 2.6,
> even when the SATA hard drive forces the SCSI storage drivers into existence.
>

I cannot verify the module load sequence from here. If you
do 'cat /proc/modules' then you get a list of modules as they
were loaded (with the most recent module on the top). On
my system lsmod returns the same module sequence. Maybe ide-scsi
is loaded much more early than you expected?

Is it an option to build a kernel without any ide-scsi
support?

Regards

Harri

--------------enig5AF8F5363C5D9B4DF11B623E
Content-Type: application/pgp-signature; name="signature.asc"
Content-Description: OpenPGP digital signature
Content-Disposition: attachment; filename="signature.asc"

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.0 (GNU/Linux)
Comment: Using GnuPG with Thunderbird - http://enigmail.mozdev.org

iD4DBQFCSigEUTlbRTxpHjcRAgblAJ42FDSdquEDcydPAexN6nwQBJQMAwCVFtCZ
Ha1FfPs3aG7Yu/3WP1Us6w==
=aZ1Y
-----END PGP SIGNATURE-----

--------------enig5AF8F5363C5D9B4DF11B623E--

Revision history for this message

Debian Bug Importer (debzilla) wrote on 2005-09-22:

#20

Download full text (4.3 KiB)

Message-id: <email address hidden>
Date: Wed, 25 May 2005 17:45:02 +0300
From: Vassilii Khachaturov <email address hidden>
To: Harald Dunkel <email address hidden>
Cc: <email address hidden>, <email address hidden>
Subject: Re: are you sure swap can be labeled?

> > I know that the scsi emulation for cdrw is obsolete,
> > but I was asking how to make sure that it doesn't happen in 2.6,
> > even when the SATA hard drive forces the SCSI storage drivers into
> > existence.
>
> I cannot verify the module load sequence from here. If you
> do 'cat /proc/modules' then you get a list of modules as they
> were loaded (with the most recent module on the top). On
> my system lsmod returns the same module sequence. Maybe ide-scsi
> is loaded much more early than you expected?
>
> Is it an option to build a kernel without any ide-scsi
> support?

Indeed, when I built the kernel without the ide-scsi support, the SATA hard
drive did work nevertheless, yet the CD-ROM and the CD-RW stayed under
the pure IDE drivers control.

Unfortunately, though, in this case, despite the docs to the countrary,
I had experienced the same long timeouts during the media check
and errors on the write when trying to record anything on the CDRW,
so I reverted back to the ide-scsi emulation nevertheless.

In any case, I was unable to achieve one of them (the CD-ROM) under
the ATAPI IDE CD driver control, and the other (the CD-RW) under the SCSI
emulation control --- once the ide-scsi was there, the option to ignore the
emulation (via the "options ide-scsi hdc=ignore" line in the modprobe.d tree)
was itself ignored.

Since it all works under 2.6 with the scsi emulation anyway, I don't think
it is worth the bother, i.e., at least for me, this is not a big deal. Of
course, if somebody wants do debug it, I'll be happy to test things here.

And here's the lsmod output:
Module Size Used by
nvidia 3923228 12
apm 21100 1
parport_pc 36900 0
lp 11176 0
parport 41800 2 parport_pc,lp
binfmt_misc 11688 1
ipv6 264644 22
af_packet 22568 2
sr_mod 17316 0
floppy 61200 0
pcspkr 3592 0
snd_intel8x0 34076 1
snd_ac97_codec 78744 1 snd_intel8x0
snd_pcm_oss 53768 0
snd_mixer_oss 20032 1 snd_pcm_oss
snd_pcm 95496 3 snd_intel8x0,snd_ac97_codec,snd_pcm_oss
snd_timer 25924 1 snd_pcm
snd 59076 8
snd_intel8x0,snd_ac97_codec,snd_pcm_oss,snd_mixer_oss,snd_pcm,snd_timer
soundcore 10336 1 snd
snd_page_alloc 10120 2 snd_intel8x0,snd_pcm
ehci_hcd 32004 0
usblp 13088 0
tsdev 7392 0
mousedev 10476 1
ov511 99392 0
ovcamchip 26248 0
joydev 9984 0
evdev 9600 0
usbhid 32224 0
videodev 10016 1 ov511
i2c_core 24176 2 ov511,ovcamchip
v4l2_common 6144 1 ov511
uhci_hcd 33136 0
usbcore ...

Message-id: <200505251745.03043.vassilii@tarunz.org>
Date: Wed, 25 May 2005 17:45:02 +0300
From: Vassilii Khachaturov <vassilii@tarunz.org>
To: Harald Dunkel <harald.dunkel@t-online.de>
Cc: 286515@bugs.debian.org, 290474@bugs.debian.org
Subject: Re: are you sure swap can be labeled?

> > I know that the scsi emulation for cdrw is obsolete,
> > but I was asking how to make sure that it doesn't happen in 2.6,
> > even when the SATA hard drive forces the SCSI storage drivers into
> > existence.
>
> I cannot verify the module load sequence from here. If you
> do 'cat /proc/modules' then you get a list of modules as they
> were loaded (with the most recent module on the top). On
> my system lsmod returns the same module sequence. Maybe ide-scsi
> is loaded much more early than you expected?
>
> Is it an option to build a kernel without any ide-scsi
> support?

Indeed, when I built the kernel without the ide-scsi support, the SATA hard
drive did work nevertheless, yet the CD-ROM and the CD-RW stayed under
the pure IDE drivers control.

Unfortunately, though, in this case, despite the docs to the countrary,
I had experienced the same long timeouts during the media check
and errors on the write when trying to record anything on the CDRW,
so I reverted back to the ide-scsi emulation nevertheless.

In any case, I was unable to achieve one of them (the CD-ROM) under
the ATAPI IDE CD driver control, and the other (the CD-RW) under the SCSI
emulation control --- once the ide-scsi was there, the option to ignore the 
emulation (via the "options ide-scsi hdc=ignore" line in the modprobe.d tree)
was itself ignored.

Since it all works under 2.6 with the scsi emulation anyway, I don't think
it is worth the bother, i.e., at least for me, this is not a big deal. Of 
course, if somebody wants do debug it, I'll be happy to test things here.

And here's the lsmod output:
Module                  Size  Used by
nvidia               3923228  12
apm                    21100  1
parport_pc             36900  0
lp                     11176  0
parport                41800  2 parport_pc,lp
binfmt_misc            11688  1
ipv6                  264644  22
af_packet              22568  2
sr_mod                 17316  0
floppy                 61200  0
pcspkr                  3592  0
snd_intel8x0           34076  1
snd_ac97_codec         78744  1 snd_intel8x0
snd_pcm_oss            53768  0
snd_mixer_oss          20032  1 snd_pcm_oss
snd_pcm                95496  3 snd_intel8x0,snd_ac97_codec,snd_pcm_oss
snd_timer              25924  1 snd_pcm
snd                    59076  8 
snd_intel8x0,snd_ac97_codec,snd_pcm_oss,snd_mixer_oss,snd_pcm,snd_timer
soundcore              10336  1 snd
snd_page_alloc         10120  2 snd_intel8x0,snd_pcm
ehci_hcd               32004  0
usblp                  13088  0
tsdev                   7392  0
mousedev               10476  1
ov511                  99392  0
ovcamchip              26248  0
joydev                  9984  0
evdev                   9600  0
usbhid                 32224  0
videodev               10016  1 ov511
i2c_core               24176  2 ov511,ovcamchip
v4l2_common             6144  1 ov511
uhci_hcd               33136  0
usbcore               119012  7 ehci_hcd,usblp,ov511,usbhid,uhci_hcd
pci_hotplug            34640  0
intel_agp              22816  0
intel_mch_agp          10608  1
agpgart                34664  3 nvidia,intel_agp,intel_mch_agp
dm_mod                 59804  0
capability              4520  0
commoncap               7232  1 capability
advansys               82528  0
e100                   32608  0
mii                     5120  1 e100
ide_cd                 42656  0
cdrom                  40732  2 sr_mod,ide_cd
genrtc                  9588  0
ext3                  127240  7
jbd                    62616  1 ext3
mbcache                 9348  1 ext3
ide_scsi               17412  0
sg                     39168  0
unix                   28756  304
font                    8320  0
vesafb                  6656  0
cfbcopyarea             3872  1 vesafb
cfbimgblt               3040  1 vesafb
cfbfillrect             3776  1 vesafb
sd_mod                 21728  9
ata_piix                8132  8
libata                 41700  1 ata_piix
scsi_mod              125228  6 sr_mod,advansys,ide_scsi,sg,sd_mod,libata
ide_generic             1408  0
ide_core              139940  3 ide_cd,ide_scsi,ide_generic

V.

Revision history for this message

Debian Bug Importer (debzilla) wrote on 2005-09-22:

#21

Download full text (13.9 KiB)

Message-id: <email address hidden>
Date: Thu, 14 Jul 2005 11:10:29 +0300
From: Vassilii Khachaturov <email address hidden>
To: <email address hidden>
Cc: <email address hidden>
Subject: sarge r0a i386 netinst partial success, IBM ThinkCentre 8189LDG

Package: installation-reports

INSTALL REPORT

Debian-installer-version: sarge stable 3.1 r0a netinst i386 CD.
Tue Jul 13, 2005 got it from an admin
in the BGU CS computing services lab, who downloaded
it from an official Debian mirror.

uname -a:=20
Linux ilmarinen 2.6.8-2-686 #1 Thu May 19 17:53:30 JST 2005 i686 GNU/=
Linux

Date: Finished circa Wed Jul 13 early A.M., IDT 2005

Method:=20
* Manual installation, at the console. Had a working laptop
plugged in as well to talk to the #debian-boot on the irc.freenode.ne=
t
when problems started happening.
* Booted off the ATAPI CD-ROM. Network install from the official
Israeli HTTP mirror at=20
deb http://mirror.hamakor.org.il/pub/mirrors/debian/ stable=20
* This happens at home, in a private LAN 10, which is routed (via NAT=
)=20
to the internet by an Alcatel Speedtouch 510 ADSL modem.

Machine: IBM ThinkCentre
As per the BIOS machine info screen:
* Machine Type/Model: 8189LDG
* Flash EEPROM Revision Level: 2AKT48AUS=20
(November 2004, there's a March 2005 version available at the time of=
writing)
* CPU Bus Speed: 800MHz
* Memory Speed: 400MHz

Processor:
processor=09: 0
vendor_id=09: GenuineIntel
cpu family=09: 15
model=09=09: 2
model name=09: Intel(R) Pentium(R) 4 CPU 2.60GHz
stepping=09: 9
cpu MHz=09=09: 2593.784
cache size=09: 512 KB
fdiv_bug=09: no
hlt_bug=09=09: no
f00f_bug=09: no
coma_bug=09: no
fpu=09=09: yes
fpu_exception=09: yes
cpuid level=09: 2
wp=09=09: yes
flags=09=09: fpu vme de pse tsc msr pae mce cx8 apic sep mtrr pge mca=
cmov pat pse36 clflush dts acpi mmx fxsr sse sse2 ss ht tm pbe cid
bogomips=09: 5144.57

Memory:
total used free shared buffers ca=
ched
Mem: 515900 59044 456856 0 26568 1=
0784
-/+ buffers/cache: 21692 494208
Swap: 1373548 0 1373548

Root Device: SATA WDC 80G drive, sda.=20
discover output from hardware-summary: WDC WD800JD-22JN;/dev/sda
Root Size/partition table: Feel free to paste the full partition
table, with notes on which partitions are mounted where.
* /proc/partitions:
major minor #blocks name

   8 0 78150744 sda
   8 1 128488 sda1
   8 2 1373557 sda2
   8 3 498015 sda3
   8 4 76148100 sda4
254 0 5242880 dm-0
254 1 3145728 dm-1
254 2 2097152 dm-2
254 3 7864320 dm-3
* /proc/mounts
rootfs / rootfs rw 0 0
/dev2/root2 / ext3 rw 0 0
proc /proc proc rw,nodiratime 0 0
sysfs /sys sysfs rw 0 0
devpts /dev/pts devpts rw 0 0
tmpfs /dev/shm tmpfs rw 0 0
usbfs /proc/bus/usb usbfs rw 0 0
/dev/sda1 /boot ext3 rw 0 0
/dev/mapper/sys-home /home reiserfs rw,noatime 0 0
/dev/mapper/sys-tmp /tmp reiserfs rw 0 0
/dev/mapper/sys-usr /usr reiserfs rw,noatime 0 0
/dev/mapper/sys-var /var reiserfs rw 0 0

Output of lspci and lspci -n:
0000:00:00.0 Host bridge: Intel Corp. 82865G/PE/P DRAM Controller/Hos=
t-Hub Interface (rev 02)
0000:00...

Message-id: <E1Dsynd-0000lU-Cu@localhost.localdomain>
Date: Thu, 14 Jul 2005 11:10:29 +0300
From: Vassilii Khachaturov <vassilii@tarunz.org>
To: submit@bugs.debian.org
Cc: 290474@bugs.debian.org
Subject: sarge r0a i386 netinst partial success, IBM ThinkCentre 8189LDG

Package: installation-reports

INSTALL REPORT

Debian-installer-version: sarge stable 3.1 r0a netinst i386 CD.
Tue Jul 13, 2005 got it from an admin
in the BGU CS computing services lab, who downloaded
it from an official Debian mirror.

uname -a:=20
Linux ilmarinen 2.6.8-2-686 #1 Thu May 19 17:53:30 JST 2005 i686 GNU/=
Linux

Date: Finished circa Wed Jul 13 early A.M., IDT 2005

Method:=20
* Manual installation, at the console. Had a working laptop
plugged in as well to talk to the #debian-boot on the irc.freenode.ne=
t
when problems started happening.
* Booted off the ATAPI CD-ROM. Network install from the official
Israeli HTTP mirror at=20
deb http://mirror.hamakor.org.il/pub/mirrors/debian/ stable=20
* This happens at home, in a private LAN 10, which is routed (via NAT=
)=20
to the internet by an Alcatel Speedtouch 510 ADSL modem.

Machine: IBM ThinkCentre
As per the BIOS machine info screen:
* Machine Type/Model: 8189LDG
* Flash EEPROM Revision Level: 2AKT48AUS=20
(November 2004, there's a March 2005 version available at the time of=
 writing)
* CPU Bus Speed: 800MHz
* Memory Speed: 400MHz

Processor:
processor=09: 0
vendor_id=09: GenuineIntel
cpu family=09: 15
model=09=09: 2
model name=09: Intel(R) Pentium(R) 4 CPU 2.60GHz
stepping=09: 9
cpu MHz=09=09: 2593.784
cache size=09: 512 KB
fdiv_bug=09: no
hlt_bug=09=09: no
f00f_bug=09: no
coma_bug=09: no
fpu=09=09: yes
fpu_exception=09: yes
cpuid level=09: 2
wp=09=09: yes
flags=09=09: fpu vme de pse tsc msr pae mce cx8 apic sep mtrr pge mca=
 cmov pat pse36 clflush dts acpi mmx fxsr sse sse2 ss ht tm pbe cid
bogomips=09: 5144.57

Memory:
             total       used       free     shared    buffers     ca=
ched
Mem:        515900      59044     456856          0      26568      1=
0784
-/+ buffers/cache:      21692     494208
Swap:      1373548          0    1373548

Root Device: SATA WDC 80G drive, sda.=20
discover output from hardware-summary: WDC WD800JD-22JN;/dev/sda
Root Size/partition table:  Feel free to paste the full partition
      table, with notes on which partitions are mounted where.
* /proc/partitions:
major minor  #blocks  name

8     0   78150744 sda
   8     1     128488 sda1
   8     2    1373557 sda2
   8     3     498015 sda3
   8     4   76148100 sda4
 254     0    5242880 dm-0
 254     1    3145728 dm-1
 254     2    2097152 dm-2
 254     3    7864320 dm-3
* /proc/mounts
rootfs / rootfs rw 0 0
/dev2/root2 / ext3 rw 0 0
proc /proc proc rw,nodiratime 0 0
sysfs /sys sysfs rw 0 0
devpts /dev/pts devpts rw 0 0
tmpfs /dev/shm tmpfs rw 0 0
usbfs /proc/bus/usb usbfs rw 0 0
/dev/sda1 /boot ext3 rw 0 0
/dev/mapper/sys-home /home reiserfs rw,noatime 0 0
/dev/mapper/sys-tmp /tmp reiserfs rw 0 0
/dev/mapper/sys-usr /usr reiserfs rw,noatime 0 0
/dev/mapper/sys-var /var reiserfs rw 0 0

Output of lspci and lspci -n:
0000:00:00.0 Host bridge: Intel Corp. 82865G/PE/P DRAM Controller/Hos=
t-Hub Interface (rev 02)
0000:00:01.0 PCI bridge: Intel Corp. 82865G/PE/P PCI to AGP Controlle=
r (rev 02)
0000:00:1d.0 USB Controller: Intel Corp. 82801EB/ER (ICH5/ICH5R) USB =
UHCI #1 (rev 02)
0000:00:1d.1 USB Controller: Intel Corp. 82801EB/ER (ICH5/ICH5R) USB =
UHCI #2 (rev 02)
0000:00:1d.2 USB Controller: Intel Corp. 82801EB/ER (ICH5/ICH5R) USB =
UHCI #3 (rev 02)
0000:00:1d.3 USB Controller: Intel Corp. 82801EB/ER (ICH5/ICH5R) USB =
UHCI #4 (rev 02)
0000:00:1d.7 USB Controller: Intel Corp. 82801EB/ER (ICH5/ICH5R) USB2=
 EHCI Controller (rev 02)
0000:00:1e.0 PCI bridge: Intel Corp. 82801 PCI Bridge (rev c2)
0000:00:1f.0 ISA bridge: Intel Corp. 82801EB/ER (ICH5/ICH5R) LPC Brid=
ge (rev 02)
0000:00:1f.2 IDE interface: Intel Corp. 82801EB (ICH5) Serial ATA 150=
 Storage Controller (rev 02)
0000:00:1f.3 SMBus: Intel Corp. 82801EB/ER (ICH5/ICH5R) SMBus Control=
ler (rev 02)
0000:00:1f.5 Multimedia audio controller: Intel Corp. 82801EB/ER (ICH=
5/ICH5R) AC'97 Audio Controller (rev 02)
0000:01:00.0 VGA compatible controller: nVidia Corporation NV11 [GeFo=
rce2 MX/MX 400] (rev a1)
0000:03:08.0 Ethernet controller: Intel Corp. 82562EZ 10/100 Ethernet=
 Controller (rev 02)
0000:03:09.0 Communication controller: PCTel Inc HSP MicroModem 56 (r=
ev 01)
0000:03:0c.0 SCSI storage controller: Advanced System Products, Inc A=
BP940-U / ABP960-U (rev 03)

0000:00:00.0 0600: 8086:2570 (rev 02)
0000:00:01.0 0604: 8086:2571 (rev 02)
0000:00:1d.0 0c03: 8086:24d2 (rev 02)
0000:00:1d.1 0c03: 8086:24d4 (rev 02)
0000:00:1d.2 0c03: 8086:24d7 (rev 02)
0000:00:1d.3 0c03: 8086:24de (rev 02)
0000:00:1d.7 0c03: 8086:24dd (rev 02)
0000:00:1e.0 0604: 8086:244e (rev c2)
0000:00:1f.0 0601: 8086:24d0 (rev 02)
0000:00:1f.2 0101: 8086:24d1 (rev 02)
0000:00:1f.3 0c05: 8086:24d3 (rev 02)
0000:00:1f.5 0401: 8086:24d5 (rev 02)
0000:01:00.0 0300: 10de:0110 (rev a1)
0000:03:08.0 0200: 8086:1050 (rev 02)
0000:03:09.0 0780: 134d:7891 (rev 01)
0000:03:0c.0 0100: 10cd:1300 (rev 03)

Base System Installation Checklist:
[O] =3D OK, [E] =3D Error (please elaborate below), [ ] =3D didn't tr=
y it

Initial boot worked:    [O]
Configure network HW:   [O]
Config network:         [O]
Detect CD:              [E]
Load installer modules: [O]
Detect hard drives:     [O]
Partition hard drives:  [E]
Create file systems:    [E]
Mount partitions:       [O]
Install base system:    [O]
Install boot loader:    [O]
Reboot:                 [E]

Comments/Problems:

1. Detect CD
Initially I tried to boot the installer CD into the "linux26" option,
and the machine said it was unable to detect my CD-ROM, because,
it said, apparently it's a non-ATAPI one and something for which
a driver floppy is needed. However, the CD-ROM *is* an ATAPI one.

Following FJP's suggestions at #debian-boot, who recognized
this as a typical problem for a SATA machine, I rebooted into "expert=
26",
and, when at the "Detect CD-ROM" stage, in the screen that
prompts for the modules to pre-load, disabled almost everything,
except for=20
=09ide-cd
=09isofs
=09ide-generic
After that, I got a dialog "Unable to load some modules" listing=20
=09i810-tco e100 ide-mod ide-probe-mod ide-detect ide-floppy
which I safely ignored. Selecting "continue" in that dialog
lead to normal CD operation further on throughout the initial
installer stage (however the CD was again inaccessible after the
reboot into the system, see below).

After that, I changed the debconf priority back to "high".

2. Partition hard drives/ 3. Create file systems
As you can see from the partions dump, I was going to have
/boot,swap and / as normal ext3/swap partitions, while /usr /var /hom=
e and /tmp
were going to be LVM2 reiserfs ones, with the LVM volume taking a par=
tition
to which the remaining hard drive space is allocated.=20
I've done such setups in past, e.g., see
a successful installation-report from me at bug# 309607.

By mistake, I had allocated 7.5M rather than 7.5G to the /usr logical
volume :-) as a result, when I told partman that I want it mounted /u=
sr=20
and formatted as reiserfs, I got a message:
failed to create a file system: the reiserfs file system creation in =
partition #1 of LVM VG sys LV usr failed

This wasn't very explanatory, and, having
hit "GO BACK" to the main menu of the installer, I went to the 2nd vc=
=20
and did a manual
=09 mkreiserfs /dev/sys/usr

This one said gave me a more elaborate error message:
reiserfs_create_journal: cannot create a journal of 8193 blocks with =
18 offset on 2048 blocks

I still didn't understand what was going on and tried ext3 instead.
This auto-kicked the installation of the base system which then stopp=
ed
with an error from which I realized that /usr was overflowing :-)
only at that moment, when I did a df -h on the second vc, I caught
my error. I then went back to the main menu, and returned to the=20
partitioner.=20

First, I went to the type of the file system and asked for reiserfs a=
gain.
Then, I selected the size (7.5) in the menu, hoping for some kind
of a resize dialog. However, as a result, I got a new dialog
=09[!!] Partition disks
=09??? ???=20
=09<Go Back> <Continue>=20
that looped self no matter which of the 2 options I select.
(I've promised to FJP to file a separate bug against partman on that,
I'll do it when I have a response from BTS on the present installatio=
n
report to xref the 2).

Then I was forced to reboot, and proceeded the same way (expert26/mod=
ules
selection trick/back to high priority) until the partition hard drive=
s stage.

Therein, I entered the LVM configuration menu, and deleted the proble=
matic
LV, recreating it again 1K times larger than it was. After that, I re=
-entered
all the mount points, fs types (reiserfs over the LVM all the way), a=
nd the
mount flags. Thereafter, the file system creation went normally, as t=
he
subsequent base system installation.

I opted not to select any additional packages at the time.

4. Reboot
While the system itself booted OK, I've still marked the item as
an error as the cdrom and the cdrw were never recognized after reboot=
.
Previosly, the same box did work with them (this is a fresh reinstall
after a hard disk crash), but only through the ide-scsi layer.
Here is an excerpt from my pre-crash administration log on that box:
=09Tue F=C5b  8 18:47:52 IST 2005
=09CDROM/CDRW don't work in 2.6. To work around:
=09* Added to /etc/mkinitrd/modules:
=09=09ide-generic
=09=09ata_piix
=09=09sd_mod
=09* cp /boot/initrd.img-2.6.8-2-686 /boot/initrd.img-2.6.8-2-686.bak
=09* mkinitrd -o /boot/initrd.img-2.6.8-2-686
=09and also in /etc/modules
=09commented sg and ide-scsi, putting ide-cd instead.

=09Now they get recognized but still ide-scsi remaps hdc and hdd.
Haven't tried this now yet, but I have all the reasons to believe
that it will work again.

Please read the bug# 286515/290474 if you're interested in more info
on how this worked, including an lsmod output from back then.
Brief summary: 1) I know ide-scsi emulation of cd/cdrw is obsolete in=
 2.6
2) I found no way of making this box work with them otherwise
3) only if ide-scsi support was totally excluded from the (custom
kpkg) kernel compilation, the cdrom agreed to work as hdc, however
the cdrw never worked, giving the same long timeouts during media
detection/write errors as used to be the case when one tried to do
recording through the ATAPI IDE drivers back in the 2.4 times.

Now, the /etc/modules created by the installer loads
=09ide-cd ide-disk ide-generic psmouse sd_mod

I had installed the 686 rather than the installer-supplied 386 varian=
t
of the 2.6.8 kernel image, and the lsmod output below is from
within the 2.6.8-2-686 after the reboot:

Module                  Size  Used by
af_packet              22568  2=20
snd_intel8x0           36460  0=20
snd_ac97_codec         69988  1 snd_intel8x0
snd_pcm_oss            55080  0=20
snd_mixer_oss          20096  1 snd_pcm_oss
snd_pcm                98728  2 snd_intel8x0,snd_pcm_oss
snd_timer              25732  1 snd_pcm
snd_page_alloc         11752  2 snd_intel8x0,snd_pcm
gameport                4704  1 snd_intel8x0
snd_mpu401_uart         7968  1 snd_intel8x0
snd_rawmidi            25124  1 snd_mpu401_uart
snd_seq_device          8200  1 snd_rawmidi
snd                    57156  9 snd_intel8x0,snd_ac97_codec,snd_pcm_o=
ss,snd_mixer_oss,snd_pcm,snd_timer,snd_mpu401_uart,snd_rawmidi,snd_se=
q_device
soundcore              10336  1 snd
reiserfs              250992  4=20
capability              4520  0=20
commoncap               7232  1 capability
ide_generic             1408  0=20
ide_disk               19296  0=20
ov511                  87740  0=20
ext3                  127240  2=20
jbd                    62616  1 ext3
mbcache                 9348  1 ext3
sr_mod                 17316  0=20
ide_scsi               17412  0=20
videodev               10016  1 ov511
ovcamchip              23208  0=20
i2c_core               24176  1 ovcamchip
tsdev                   7392  0=20
mousedev               10476  0=20
joydev                  9984  0=20
evdev                   9600  0=20
pcspkr                  3592  0=20
usblp                  13088  0=20
shpchp                101900  0=20
pciehp                 99020  0=20
pci_hotplug            34640  2 shpchp,pciehp
intel_agp              22816  0=20
intel_mch_agp          10608  1=20
agpgart                34664  2 intel_agp,intel_mch_agp
psmouse                20360  0=20
genrtc                  9588  0=20
dm_mod                 59804  5=20
sd_mod                 21728  5=20
floppy                 61200  0=20
e100                   32608  0=20
mii                     5120  1 e100
ide_cd                 42656  0=20
ide_core              139940  4 ide_generic,ide_disk,ide_scsi,ide_cd
cdrom                  40732  2 sr_mod,ide_cd
fbcon                  32100  65=20
vga16fb                13160  1=20
vgastate               10048  1 vga16fb
usbserial              29896  0=20
usbhid                 32224  0=20
usbkbd                  7424  0=20
ehci_hcd               32004  0=20
uhci_hcd               33136  0=20
usbcore               119012  9 ov511,usblp,usbserial,usbhid,usbkbd,e=
hci_hcd,uhci_hcd
thermal                12656  0=20
processor              17264  1 thermal
fan                     3980  0=20
sg                     39168  0=20
advansys               82528  0=20
ata_piix                8132  4=20
libata                 41700  1 ata_piix
scsi_mod              125228  6 sr_mod,ide_scsi,sd_mod,sg,advansys,li=
bata
unix                   28756  0=20
font                    8320  1 fbcon
vesafb                  6656  0=20
cfbcopyarea             3872  2 vga16fb,vesafb
cfbimgblt               3040  2 vga16fb,vesafb
cfbfillrect             3776  2 vga16fb,vesafb

> Install logs and other status info is available in /var/log/debian-=
installer/.
I'll take the partman logs from there for the separate partman bug;
for other info, please tell me if there's anything else you'd like
me to send in out of
=09cdebconf hardware-summary messages partman status syslog
there.

Revision history for this message

Debian Bug Importer (debzilla) wrote on 2005-09-22:

#22

Message-Id: <email address hidden>
Date: Thu, 25 Aug 2005 16:44:34 +0200
From: Thomas Richter <email address hidden>
To: Debian Bug Tracking System <email address hidden>
Subject: initrd-tools: Similar problem on K8N Neo2, sata_nv missing

Package: initrd-tools
Version: 0.1.81.1
Followup-For: Bug #290474

When upgrading from a 2.4 to a 2.6 kernel on a SATA machine,
booting becomes impossible because mkinitrd does not include
the SATA drivers that are now required to handle the SATA disk
on 2.6. On 2.4, the same disks have been handled by the generic
PATA (aka IDE) drivers.

The problem is fixable by editing the module list of the initrd
manually (mounting the cramfs, editing by hand). Specifically,
for the mentioned board (K8N Neo2), the following driver must be
supplied:

sata_nv

since this is an nforce chipset. Depending on the chipset,
more/other drivers should be included.

On upgrading from 2.4 to 2.6, it is suggested that the package upgrades
the following details:

a) Include the SATA drivers, even though SATA is currently not in use
for 2.4. (Fix in this package)
b) Update /etc/fstab since the SATA drives appear now at /dev/sd?
instead of /dev/hd? (where should this fix be done? kernel-image?)
c) Update /etc/grub/menu.list to reflect the location of root.
(fix in grub package)

-- System Information:
Debian Release: 3.1
Architecture: i386 (i686)
Kernel: Linux 2.6.11-1-k7
Locale: LANG=de_DE.UTF-8@euro, LC_CTYPE=de_DE.UTF-8@euro (charmap=UTF-8)

Versions of packages initrd-tools depends on:
ii coreutils [fileutils] 5.2.1-2 The GNU core utilities
ii cpio 2.5-1.2 GNU cpio -- a program to manage ar
ii cramfsprogs 1.1-6 Tools for CramFs (Compressed ROM F
ii dash 0.5.2-5 The Debian Almquist Shell
ii util-linux 2.12p-4 Miscellaneous system utilities

-- no debconf information

Bug Watch Updater (bug-watch-updater) on 2008-05-06

Changed in initrd-tools:
status:	New → Fix Released

Affects		Status	Importance	Assigned to	Milestone
	initrd-tools (Debian)	Fix Released	Unknown	debbugs #290474
	initrd-tools (Ubuntu)	Invalid	Critical	Jeff Bailey

Ubuntu
initrd-tools package

kernel-image-2.6.10-1-686: impossible to mount the root partition on a SATA disk

Bug Description

Other bug subscribers

Bug attachments

Remote bug watches

Ubuntuinitrd-tools package

kernel-image-2.6.10-1-686: impossible to mount the root partition on a SATA disk

Bug Description

Other bug subscribers

Bug attachments

Remote bug watches

Ubuntu
initrd-tools package