--- Begin Message ---
Package: installation-reports
INSTALL REPORT
Debian-installer-version: rc2 i386
uname -a: Linux rigel 2.6.8-1-k7 #1 Thu Nov 11 12:47:56 EST 2004 i686 GNU/Linux
Date: 2004-11-23
Method: Booted from netinst CD
Machine: custom-built Athlon-based PC
Processor: AMD Athlon 1150.549
Memory: 256 MB
Root Device: LVM2 lv on RAID-1 dm0 on 2 IDE disc partitions (hda1, hdc1)
Root Size/partition table:
rigel:~# cat /proc/partitions
major minor #blocks name
3 0 78150744 hda
3 1 78148161 hda1
22 0 120060864 hdc
22 1 78125008 hdc1
9 0 78124928 md0
253 0 262144 dm-0
253 1 524288 dm-1
253 2 5242880 dm-2
253 3 10485760 dm-3
253 4 10485760 dm-4
253 5 10485760 dm-5
253 6 749568 dm-6
rigel:~# df
Filesystem 1K-blocks Used Available Use% Mounted on
/dev/vg0/root 245679 112932 119640 49% /
tmpfs 124412 0 124412 0% /dev/shm
/dev/mapper/vg0-srv 10321208 32860 9764060 1% /srv
/dev/mapper/vg0-tmp 491364 8239 456911 2% /tmp
/dev/mapper/vg0-usr 5160576 273916 4624516 6% /usr
/dev/mapper/vg0-var 10321208 99060 9697860 2% /var
swap is on /dev/vg0/swap
Output of lspci and lspci -n:
rigel:~# lspci
0000:00:00.0 Host bridge: VIA Technologies, Inc. VT8361 [KLE133] Host Bridge
0000:00:01.0 PCI bridge: VIA Technologies, Inc. VT8361 [KLE133] AGP Bridge
0000:00:07.0 ISA bridge: VIA Technologies, Inc. VT82C686 [Apollo Super South] (rev 40)
0000:00:07.1 IDE interface: VIA Technologies, Inc. VT82C586A/B/VT82C686/A/B/VT823x/A/C PIPC Bus Master IDE (rev 06)
0000:00:07.2 USB Controller: VIA Technologies, Inc. VT82xxxxx UHCI USB 1.1 Controller (rev 1a)
0000:00:07.3 USB Controller: VIA Technologies, Inc. VT82xxxxx UHCI USB 1.1 Controller (rev 1a)
0000:00:07.4 Bridge: VIA Technologies, Inc. VT82C686 [Apollo Super ACPI] (rev 40)
0000:00:07.5 Multimedia audio controller: VIA Technologies, Inc. VT82C686 AC97 Audio Controller (rev 50)
0000:00:0f.0 Ethernet controller: Linksys NC100 Network Everywhere Fast Ethernet 10/100 (rev 11)
0000:01:00.0 VGA compatible controller: Trident Microsystems CyberBlade/i1
rigel:~# lspci -n
0000:00:00.0 0600: 1106:3112
0000:00:01.0 0604: 1106:b112
0000:00:07.0 0601: 1106:0686 (rev 40)
0000:00:07.1 0101: 1106:0571 (rev 06)
0000:00:07.2 0c03: 1106:3038 (rev 1a)
0000:00:07.3 0c03: 1106:3038 (rev 1a)
0000:00:07.4 0680: 1106:3057 (rev 40)
0000:00:07.5 0401: 1106:3058 (rev 50)
0000:00:0f.0 0200: 1317:0985 (rev 11)
0000:01:00.0 0300: 1023:8500
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: [O]
Load installer modules: [O]
Detect hard drives: [O]
Partition hard drives: [O]
Create file systems: [O]
Mount partitions: [O]
Install base system: [O]
Install boot loader: [E]
Reboot: [O]
Comments/Problems:
Everything except installing lilo worked remarkably well! Nice work, team.
I created partitions /dev/hda1 and /dev/hdc1 of type linux raid autodetect. I
then created /dev/md0 from these and configured LVM to use this as a PV. Then
I created my LV's, including one for the root filesystem, and selected
filesystem and mount point options for each. So far so good; everything was
easy to do using the d-i interface.
When I got to the part where the boot loader is installed, I was prompted for
the device on which to install it. I had 3 choices, if I remember correctly;
the first 2 were both "/dev/md0" and the 3rd was "advanced..." or similar. The
first 2 choices failed, but I was able to make it work by choosing advanced and
/dev/hda (but I had to call it "/dev/discs/disc0/disc" or similar; the device
node /dev/hda did not exist). Reboot, and behold! The thing actually booted
and mounted all my filesystems, including the root-on-lvm-on-raid. Sweeet!
Today (the install was last night), I did some more research, and determined
that d-i's suggestion of installing lilo on /dev/md0 wasn't so crazy, but that
/etc/lilo.conf needed to also have the line "raid-extra-boot=mbr-only". Once I
added that I could change the boot= option from /dev/hda to /dev/md0, and run
lilo and it installed to both /dev/hda and /dev/hdc MBRs as desired. Perhaps
"raid-extra-boot=mbr-only" is only needed if / is on LVM-on-RAID1?
Let me know if there is any further information that could be useful; I'm going
to be taking this system down shortly (it's a testbed for another project, and
I need the hard drives), but I will scp the contents of
/var/log/debian-installer to another machine for safe keeping.
Cheers,
nate
--- End Message ---
--- Begin Message ---
We are closing this installation report for one of the following
reasons:
- it was reported with a pre-lenny version of Debian
Installer.
- indications in the installation report give the feeling that
the reported problem waslying in another software, unrelated to
D-I, which we can't easily identify.
- indications in the installation report suggest that it may have been
fixed in a more recent version of a D-I component
- it was successful and we forgot closing it..:-)
- it has no information we consider useful
The D-I team is currently in the process of cleaning out the old spool
of installation reports that haven't bene processed yet.
In case you think that the problem you reported has chances to be
still present, please reiterate your installation test with
a more recent image of D-I, if you're in position of doing this.
You'll find daily builds at
http://www.debian.org/devel/debian-installer. We recommend you choose
the netboot image, in the "daily builds section", then choose to
install "squeeze" when prompted.
If some problems are found, please report them with a new bug sent
against installation-reports.
Many thanks for your understanding and your help improving Debian,
past and present.
--- End Message ---