Package: installation-reports INSTALL REPORT Debian-installer-version: debian-31r1a-i386-netinst.iso (downloaded on 2006-03-06 from http://cdimage.debian.org/debian-cd/3.1_r1/i386/iso-cd/debian-31r1a-i386-netinst.iso) uname -a: Linux firewall1b 2.4.27-2-386 #1 Wed Aug 17 09:33:35 UTC 2005 i686 GNU/Linux Date: 2006-03-08 10:00 GMT Method: How did you install? What did you boot off? If network install, from where? Proxied? - boot from netinst CD (from official Debian server) - network install from ftp.de.debian.org - no proxy (but a masquerading gateway) Machine: Transtec rack-mount server 1002 Processor: Intel(R) Pentium(R) 4 CPU 2.40GHz Memory: 1 GB Root Device: IDE /dev/hda and /dev/hdb Root Size/partition table: Disk /dev/hda: 4865 cylinders, 255 heads, 63 sectors/track Units = cylinders of 8225280 bytes, blocks of 1024 bytes, counting from 0 Device Boot Start End #cyls #blocks Id System /dev/hda1 0+ 607 608- 4883728+ fd Linux raid autodetect /dev/hda2 608 1215 608 4883760 fd Linux raid autodetect /dev/hda3 1216 4864 3649 29310592+ fd Linux raid autodetect /dev/hda4 0 - 0 0 0 Empty Disk /dev/hdb: 4865 cylinders, 255 heads, 63 sectors/track Units = cylinders of 8225280 bytes, blocks of 1024 bytes, counting from 0 Device Boot Start End #cyls #blocks Id System /dev/hdb1 0+ 607 608- 4883728+ fd Linux raid autodetect /dev/hdb2 608 1215 608 4883760 fd Linux raid autodetect /dev/hdb3 1216 4864 3649 29310592+ fd Linux raid autodetect /dev/hdb4 0 - 0 0 0 Empty Personalities : [raid1] read_ahead 1024 sectors md0 : active raid1 ide/host0/bus0/target0/lun0/part1 ide/host0/bus0/target1/lun0/part1 4883648 blocks [2/2] [UU] md1 : active raid1 ide/host0/bus0/target0/lun0/part2 ide/host0/bus0/target1/lun0/part2 4883648 blocks [2/2] [UU] md2 : active raid1 ide/host0/bus0/target0/lun0/part3 ide/host0/bus0/target1/lun0/part3 29310528 blocks [2/2] [UU] unused devices: <none> PV VG Fmt Attr PSize PFree /dev/md2 firewall1b lvm2 a- 27,95G 14,95G /dev/mapper/firewall1b-root on / type ext3 (rw,errors=remount-ro) /dev/md0 on /boot type ext3 (rw) /dev/mapper/firewall1b-var on /var type ext3 (rw) Output of lspci and lspci -n: 0000:00:00.0 Host bridge: Intel Corp. 82845G/GL[Brookdale-G]/GE/PE DRAM Controller/Host-Hub Interface (rev 03) 0000:00:02.0 VGA compatible controller: Intel Corp. 82845G/GL[Brookdale-G]/GE Chipset Integrated Graphics Device (rev 03) 0000:00:1d.0 USB Controller: Intel Corp. 82801DB/DBL/DBM (ICH4/ICH4-L/ICH4-M) USB UHCI Controller #1 (rev 02) 0000:00:1d.1 USB Controller: Intel Corp. 82801DB/DBL/DBM (ICH4/ICH4-L/ICH4-M) USB UHCI Controller #2 (rev 02) 0000:00:1d.2 USB Controller: Intel Corp. 82801DB/DBL/DBM (ICH4/ICH4-L/ICH4-M) USB UHCI Controller #3 (rev 02) 0000:00:1d.7 USB Controller: Intel Corp. 82801DB/DBM (ICH4/ICH4-M) USB 2.0 EHCI Controller (rev 02) 0000:00:1e.0 PCI bridge: Intel Corp. 82801 PCI Bridge (rev 82) 0000:00:1f.0 ISA bridge: Intel Corp. 82801DB/DBL (ICH4/ICH4-L) LPC Bridge (rev 02) 0000:00:1f.1 IDE interface: Intel Corp. 82801DB/DBL (ICH4/ICH4-L) UltraATA-100 IDE Controller (rev 02) 0000:00:1f.3 SMBus: Intel Corp. 82801DB/DBL/DBM (ICH4/ICH4-L/ICH4-M) SMBus Controller (rev 02) 0000:01:01.0 Ethernet controller: Syskonnect (Schneider & Koch) SK-98xx V2.0 Gigabit Ethernet Adapter (rev 13) 0000:01:03.0 Ethernet controller: 3Com Corporation 3C990B-TX-M/3C990BSVR [Typhoon2] (rev 03) 0000:01:05.0 Ethernet controller: Intel Corp. 82540EM Gigabit Ethernet Controller (rev 02) 0000:01:06.0 Ethernet controller: Intel Corp. 82540EM Gigabit Ethernet Controller (rev 02) 0000:00:00.0 0600: 8086:2560 (rev 03) 0000:00:02.0 0300: 8086:2562 (rev 03) 0000:00:1d.0 0c03: 8086:24c2 (rev 02) 0000:00:1d.1 0c03: 8086:24c4 (rev 02) 0000:00:1d.2 0c03: 8086:24c7 (rev 02) 0000:00:1d.7 0c03: 8086:24cd (rev 02) 0000:00:1e.0 0604: 8086:244e (rev 82) 0000:00:1f.0 0601: 8086:24c0 (rev 02) 0000:00:1f.1 0101: 8086:24cb (rev 02) 0000:00:1f.3 0c05: 8086:24c3 (rev 02) 0000:01:01.0 0200: 1148:4320 (rev 13) 0000:01:03.0 0200: 10b7:9904 (rev 03) 0000:01:05.0 0200: 8086:100e (rev 02) 0000:01:06.0 0200: 8086:100e (rev 02) Base System Installation Checklist: [O] = OK, [E] = Error (please elaborate below), [ ] = didn't try it Initial boot worked: [O] Configure network HW: [E] Config network: [O] Detect CD: [O] Load installer modules: [O] Detect hard drives: [O] Partition hard drives: [E] Create file systems: [O] Mount partitions: [O] Install base system: [E] Install boot loader: [E] Reboot: [E] Comments/Problems: - D-I failed to read the discover and the grub package from the downloaded and self-burnt netinst CD; I could find out the grub package name from the log on tty2 and enter a wget command on tty1, download the package and apt-get install it. Repeating the grub step did work then. The installer might perhaps offer to download defective packages from the net ... - I chose the swap space to reside on /dev/md1 (which is a RAID-1 from /dev/hda2 and /dev/hdb2). The partitioning tool accepted my choice but the swap space wasn't entered into the fstab. - The root filesystem was created on a logical volume, the PV for which is on /dev/md2 (RAID-1 from /dev/hda3 and /dev/hdb3). /boot was assigned to /dev/md0 (RAID-1 from /dev/hd?1). The partitioning tool understood this scheme only after I did everything in "the right order": Create the LVs, set / as mount point for the root LV, and _only_then_ set /boot as mount point for /dev/md0. When I assigned /boot before /, /boot was forgotten. - The network interfaces were correctly identified during the installation: The onboard e1000's as eth1 and eth2, the sk98lin as eth0 (IIRC), and the typhoon as eth3. So I configured eth1 as primary interface to the outside world, and it worked (see above: I could download the replacement grub package). But after rebooting into the installed system no interface was active (none of the necessary modules loaded, none entered into the /etc/modules file). I modprobed e1000 and with "ifup eth0=eth1" could continue with the installation. Now, looking at the installation logs, I suspect that this could have been caused by the failure to install discover. - The installation got _very_ slow because, after partitioning, the RAID-1 volumes started synchronizing. It might be better (and hopefully not too fragile) to create the RAID-1's as one-way mirrors first and later on add the second devices, thus starting off the sync process. - With /boot on RAID-1 it would be very nice and comfortable if the installer created a grub MBR and boot code on the second disk too ... Install logs and other status info is available in /var/log/debian-installer/. Once you have filled out this report, mail it to email@example.com.
Description: Binary data