Bug#257591: (no subject)
Package: installation-reports
Debian-installer-version: tc1
Date: 4 July 2004 - 15:00 CEST
Method: booted from netinst.iso burnt to CD-ROM - problem exists when
booting with both linux and expert, but not with expert26
Machine: Compaq Proliant Server
Processor: 2xPentium Pro (200MHz)
Memory: 256M (forced with mem=240m@16M
Root Device: should be /dev/ida/cd1d0p1 (see description)
Base System Installation Checklist:
Initial boot worked: [O]
Configure network HW: [O]
Config network: [O]
Detect CD: [O]
Load installer modules: [O]
Detect hard drives: [E]
Partition hard drives: [E]
Create file systems: [ ]
Mount partitions: [ ]
Install base system: [ ]
Install boot loader: [ ]
Reboot: [ ]
[O] = OK, [E] = Error (please elaborate below), [ ] = didn't try it
Comments/Problems:
I have tried using the tc1 debian installer netinst ISO image. I cam
across the following problem with hard disc partitioning:
The machine in question has 2 SMART2/P Array controllers, one attached
to the internal drives (in slot 4) and the other attached to an external
disk array (in slot 2). The external array currently has /home
partitions on it, the internal array having the other partitions
(/,/var,/tmp,/usr,swap) - this layout should be retained following the
install, however though the cpqarray modules correctly detects both
controllers:
(output from dmesg | grep cpqarray - copied by hand...)
cpqarray: Device 0xae10 has been found at bus 2 dev 0 func 0
cpqarray: Finding drives on ida0 (SMART-2/P)
cpqarray: ida/c0d0: blksz=512 nr_blks=106626720
cpqarray: Device 0xae10 has been found at bus 3 dev 0 func 0
cpqarray: Finding drives on ida0 (SMART-2/P)
cpqarray: ida/c1d0: blksz=512 nr_blks=71081760
it is followed in dmesg by:
devfs_register(disc): could not append to parent, err: -17
Only the first array is available for partitioning, and /dev/ida/disc0
exists but no other entry appears for the other ida device.
Can confirm that the 2.6 (booted with expert26) kernel detects both
correctly and both drives can be partitioned normally.
This does appear to be a bug with the devfs implementation used by
debian-installer, but I am not sufficiently competent to establish if it
is an upstream bug or related to any specific devfs changes done for the
installer.
Many thanks,
Phil
Reply to: