Bug#382025: marked as done (device recognition (bad) order)
Your message dated Tue, 08 Aug 2006 14:56:58 +0200
with message-id <200608081457.08551.elendil@planet.nl>
and subject line Bug#382025: device recognition (bad) order
has caused the attached Bug report to be marked as done.
This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.
(NB: If you are a system administrator and have no idea what I am
talking about this indicates a serious mail system misconfiguration
somewhere. Please contact me immediately.)
Debian bug tracking system administrator
(administrator, Debian Bugs database)
--- Begin Message ---
Package: installation-reports
INSTALL REPORT
Debian-installer-version: Tue, 18 Apr 2006 13:17:42 UTC
Debian GNU/Linux 3.1 r2 "Sarge" - Official i386 Binary-1 CD
uname -a: 2.6.8-2-386 (well this is not the running kernel right now so
I cannot show the full output)
Date: 2006-07-25
Method: CD based install
Machine: IBM Blade HS20
Processor: 2x Intel(R) Xeon(TM) CPU 3.20GHz
Memory: 2Gb
Root Device: SCSI Fusion-MPT (see lspci output)
Root Size/partition table:
# df -h
Filesystem Size Used Avail Use% Mounted on
/dev/sda5 957M 220M 738M 23% /
tmpfs 1012M 0 1012M 0% /dev/shm
/dev/sda1 89M 23M 61M 28% /boot
/dev/sda6 4.7G 33M 4.7G 1% /home
/dev/sda9 1.9G 33M 1.9G 2% /tmp
/dev/sda7 9.4G 2.2G 7.2G 24% /usr
/dev/sda8 14G 243M 14G 2% /var
/dev/sda10 36G 2.0G 34G 6% /vz
Output of lspci and lspci -n:
# lspci
0000:00:00.0 Host bridge: Intel Corp. Server Memory Controller Hub (rev 0c)
0000:00:00.1 ff00: Intel Corp. Memory Controller Hub Error Reporting Register (rev 0c)
0000:00:03.0 PCI bridge: Intel Corp. Memory Controller Hub PCI Express Port A1 (rev 0c)
0000:00:08.0 System peripheral: Intel Corp. Memory Controller Hub Extended Configuration Registers (rev 0c)
0000:00:1c.0 PCI bridge: Intel Corp. 6300ESB 64-bit PCI-X Bridge (rev 02)
0000:00:1d.0 USB Controller: Intel Corp. 6300ESB USB Universal Host Controller (rev 02)
0000:00:1d.1 USB Controller: Intel Corp. 6300ESB USB Universal Host Controller (rev 02)
0000:00:1d.4 System peripheral: Intel Corp. 6300ESB Watchdog Timer (rev 02)
0000:00:1d.5 PIC: Intel Corp. 6300ESB I/O Advanced Programmable Interrupt Controller (rev 02)
0000:00:1e.0 PCI bridge: Intel Corp. 82801 PCI Bridge (rev 0a)
0000:00:1f.0 ISA bridge: Intel Corp. 6300ESB LPC Interface Controller (rev 02)
0000:00:1f.1 IDE interface: Intel Corp. 6300ESB PATA Storage Controller (rev 02)
0000:00:1f.3 SMBus: Intel Corp. 6300ESB SMBus Controller (rev 02)
0000:01:01.0 VGA compatible controller: ATI Technologies Inc Radeon RV100 QY [Radeon 7000/VE]
0000:02:01.0 SCSI storage controller: LSI Logic / Symbios Logic 53c1030 PCI-X Fusion-MPT Dual Ultra320 SCSI (rev 08)
0000:04:00.0 PCI bridge: Intel Corp. PCI Bridge Hub A (rev 09)
0000:04:00.2 PCI bridge: Intel Corp. PCI Bridge Hub B (rev 09)
0000:05:01.0 Ethernet controller: Broadcom Corporation NetXtreme BCM5704S Gigabit Ethernet (rev 10)
0000:05:01.1 Ethernet controller: Broadcom Corporation NetXtreme BCM5704S Gigabit Ethernet (rev 10)
0000:06:01.0 Fibre Channel: QLogic Corp. QLA2312 Fibre Channel Adapter (rev 02)
0000:06:01.1 Fibre Channel: QLogic Corp. QLA2312 Fibre Channel Adapter (rev 02)
# lspci -n
0000:00:00.0 0600: 8086:3590 (rev 0c)
0000:00:00.1 ff00: 8086:3591 (rev 0c)
0000:00:03.0 0604: 8086:3596 (rev 0c)
0000:00:08.0 0880: 8086:359b (rev 0c)
0000:00:1c.0 0604: 8086:25ae (rev 02)
0000:00:1d.0 0c03: 8086:25a9 (rev 02)
0000:00:1d.1 0c03: 8086:25aa (rev 02)
0000:00:1d.4 0880: 8086:25ab (rev 02)
0000:00:1d.5 0800: 8086:25ac (rev 02)
0000:00:1e.0 0604: 8086:244e (rev 0a)
0000:00:1f.0 0601: 8086:25a1 (rev 02)
0000:00:1f.1 0101: 8086:25a2 (rev 02)
0000:00:1f.3 0c05: 8086:25a4 (rev 02)
0000:01:01.0 0300: 1002:5159
0000:02:01.0 0100: 1000:0030 (rev 08)
0000:04:00.0 0604: 8086:0329 (rev 09)
0000:04:00.2 0604: 8086:032a (rev 09)
0000:05:01.0 0200: 14e4:16a8 (rev 10)
0000:05:01.1 0200: 14e4:16a8 (rev 10)
0000:06:01.0 0c04: 1077:2312 (rev 02)
0000:06:01.1 0c04: 1077:2312 (rev 02)
Base System Installation Checklist:
[O] = OK, [E] = Error (please elaborate below), [ ] = didn't try it
Initial boot worked: [O]
Configure network HW: [O]
Config network: [O]
Detect CD: [E]
Load installer modules: [O]
Detect hard drives: [E]
Partition hard drives: [O]
Create file systems: [O]
Mount partitions: [O]
Install base system: [O]
Install boot loader: [O]
Reboot: [O]
Comments/Problems:
During the install process, the internal hard drive was recognized as
/dev/sdb. The CDROM was named as sda.
The grub configuration and the fstab was populated according to that
device name. However on the first boot they were recognized in the
reverse order. The kernel paniced because of the wrong root device.
One have to correct fstab and menu.lst to have a working system.
I think modules are loaded in the installer in the wrong order.
Ask if more info is needed.
--
CSILLAG Tamas (cstamas) - http://digitus.itk.ppke.hu/~cstamas
--- End Message ---
--- Begin Message ---
On Tuesday 08 August 2006 14:03, Csillag Tamas wrote:
> Comments/Problems:
> During the install process, the internal hard drive was recognized as
> /dev/sdb. The CDROM was named as sda.
>
> The grub configuration and the fstab was populated according to that
> device name. However on the first boot they were recognized in the
> reverse order. The kernel paniced because of the wrong root device.
>
> One have to correct fstab and menu.lst to have a working system.
This is a known issue. See:
http://www.debian.org/devel/debian-installer/errata
> I think modules are loaded in the installer in the wrong order.
The installer itself is not responsible for loading modules; the kernel
does this and does not do it in a predictable order. We are aware of the
issue and hope to resolve it before the release of Etch.
I'm closing your report as it is a known issue. Thanks for submitting your
report though.
Cheers,
FJP
--- End Message ---
Reply to: