Package: installation-reports Debian-installer-version: 2005-01-24 http://cdimage.debian.org/pub/cdimage-testing/sarge_d-i/i386/rc2/sarge-i386-netinst.iso uname -a: Linux hou 2.4.27-1-386 #1 Fri Sep 3 06:24:46 UTC 2004 i686 GNU/Linux
Date: 2005-01-24 11:00 GMT+1 Method: CDROM boot, mirrors.sunsite.dk Machine: Dell PowerEdge SC1425 Processor: 2 x Xeon 2.8 GHz Memory: 1.5 GB Root Device: 2 SATA disks, Maxtor, /dev/hd[ce] Root Size/partition table: Each disk is partitioned like this: Disk /dev/hdc: 250.0 GB, 250000000000 bytes 255 heads, 63 sectors/track, 30394 cylinders Units = cylinders of 16065 * 512 = 8225280 bytes Device Boot Start End Blocks Id System /dev/hdc1 * 1 12 96358+ fd Linux raid autodetect /dev/hdc2 13 30394 244043415 fd Linux raid autodetect Output of lspci and lspci -n: 0000:00:00.0 Host bridge: Intel Corp. Server Memory Controller Hub (rev 09) 0000:00:02.0 PCI bridge: Intel Corp. Memory Controller Hub PCI Express Port A0 (rev 09) 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.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 Bridge (rev 02) 0000:00:1f.1 IDE interface: Intel Corp. 82801EB/ER (ICH5/ICH5R) Ultra ATA 100 Storage Controller (rev 02) 0000:00:1f.2 IDE interface: Intel Corp. 82801EB (ICH5) Serial ATA 150 Storage Controller (rev 02) 0000:01:00.0 PCI bridge: Intel Corp. PCI Bridge Hub A (rev 09) 0000:01:00.1 PIC: Intel Corp. PCI Bridge Hub I/OxAPIC Interrupt Controller A (rev 09) 0000:01:00.2 PCI bridge: Intel Corp. PCI Bridge Hub B (rev 09) 0000:01:00.3 PIC: Intel Corp. PCI Bridge Hub I/OxAPIC Interrupt Controller B (rev 09) 0000:02:04.0 Ethernet controller: Intel Corp. 82541GI/PI Gigabit Ethernet Controller (rev 05) 0000:04:03.0 Ethernet controller: Intel Corp. 82541GI/PI Gigabit Ethernet Controller (rev 05) 0000:04:0d.0 VGA compatible controller: ATI Technologies Inc Radeon RV100 QY [Radeon 7000/VE] 0000:00:00.0 0600: 8086:3590 (rev 09) 0000:00:02.0 0604: 8086:3595 (rev 09) 0000:00:1d.0 0c03: 8086:24d2 (rev 02) 0000:00:1d.1 0c03: 8086:24d4 (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.1 0101: 8086:24db (rev 02) 0000:00:1f.2 0101: 8086:24d1 (rev 02) 0000:01:00.0 0604: 8086:0329 (rev 09) 0000:01:00.1 0800: 8086:0326 (rev 09) 0000:01:00.2 0604: 8086:032a (rev 09) 0000:01:00.3 0800: 8086:0327 (rev 09) 0000:02:04.0 0200: 8086:1076 (rev 05) 0000:04:03.0 0200: 8086:1076 (rev 05) 0000:04:0d.0 0300: 1002:5159 Base System Installation Checklist: [O] = OK, [E] = Fejl (uddyb nedenfor på engelsk), [ ] = prøvede det ikke Initial boot worked: [O] Configure network HW: [O] 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: [O] Install boot loader: [O] Reboot: [O] Comments/Problems: I use LVM and hence the filesystem layout is a bit cumbersome to describe. But that is my problem :). This is the final result proc /proc proc defaults 0 0 /dev/mapper/vg00-root / ext3 defaults,errors=remount-ro 0 1 /dev/md0 /boot ext3 defaults 0 2 /dev/mapper/vg00-scratch /scratch xfs defaults 0 2 /dev/mapper/vg00-usr /usr ext3 defaults 0 2 /dev/mapper/vg00-var /var ext3 defaults 0 2 /dev/mapper/vg00-var_mail /var/mail xfs defaults 0 2 /dev/mapper/vg00-swap none swap sw 0 0 /dev/hda /media/cdrom0 iso9660 ro,user,noauto 0 0 but before I got their I had to realize a glitch in DI. When I first set up the raid1 for /boot inkluding specifying that the mount point should be "/boot" and thereafter setup the raid1 which underlies the DeviceMapper then DI forgets about the /boot mount point and the filesystem is not created. The result is an unbootable system, as neither LILO nor GRUB understands LVM/DeviceMapper, which is the reason why /boot should be in a flat raid1. Being aware of the glitch and respecifying the /boot-mountpoint before committing the partitioning solves the problem. Another problem which I cannot specify the details for here is, at when one tries to do the same with "linux26" then the systems comes up with a mismatch of devfs and non-devfs configuration values in md and lvm. Changing the values in /etc/mdadm/mdadm.conf to devfs references makes the system work. Brian. -- Brian B. B. Truelsen, MSc, CPSM, System Administrator The Maersk Institute, University of Southern Denmark, Odense Campusvej 55, DK-5230 Odense M, Denmark Tel: +45 6550 3542 - Fax: +45 6615 7697 - http://www.mip.sdu.dk
