Package: installation-reports
INSTALL REPORT
Debian-installer-version: 8-11-2006 amd64 etch daily build netinstall cd
image from http://www.debian.org/devel/debian-installer/
uname -a: Linux physa 2.6.16-2-amd64-k8 #1 Sun Jul 16 01:27:59 CEST 2006
x86_64 GNU/Linux
Date: 8-11-2006
Method: Botted and Installed root via net install CD & an old 10/100 NIC
to download files.
Machine: AMD64 based sata raid server (DIY make)
Processor: AMD Athlon 64 3500+ Orleans 2000MHz HT Socket AM2 Processor
Memory: OCZ (2 x 512MB) 240-Pin DDR2 SDRAM (PC2 6400)
Root Device: /dev/hda (pATA)
Root Size/partition table:
Disk /dev/hda: 163.9 GB, 163928604672 bytes
255 heads, 63 sectors/track, 19929 cylinders
Units = cylinders of 16065 * 512 = 8225280 bytes
Device Boot Start End Blocks Id System
(/boot) /dev/hda1 1 122 979933+ 83 Linux
(/emergency, 2nd root) /dev/hda2 123 730 4883760 83 Linux
/dev/hda3 731 973 1951897+ 82 Linux swap / Solaris
/dev/hda4 974 19929 152264070 5 Extended
(/, primray root) /dev/hda5 974 19929 152264038+ 8e Linux LVM
there is also an array of 6 + 1 spare 250gb drives in a raid 5 array
using LVM, each drive looks like the folowing:
Disk /dev/sda: 250.0 GB, 250059350016 bytes
255 heads, 63 sectors/track, 30401 cylinders
Units = cylinders of 16065 * 512 = 8225280 bytes
Device Boot Start End Blocks Id System
/dev/sda1 1 30401 244196001 fd Linux raid autodetect
Output of lspci and lspci -n:
00:00.0 0500: 10de:0369 (rev a1)
00:01.0 0601: 10de:0362 (rev a2)
00:01.1 0c05: 10de:0368 (rev a2)
00:01.2 0500: 10de:036a (rev a2)
00:02.0 0c03: 10de:036c (rev a1)
00:02.1 0c03: 10de:036d (rev a2)
00:04.0 0101: 10de:036e (rev a1)
00:05.0 0101: 10de:037f (rev a2)
00:05.1 0101: 10de:037f (rev a2)
00:05.2 0101: 10de:037f (rev a2)
00:06.0 0604: 10de:0370 (rev a2)
00:06.1 0403: 10de:0371 (rev a2)
00:08.0 0680: 10de:0373 (rev a2)
00:09.0 0680: 10de:0373 (rev a2)
00:0b.0 0604: 10de:0374 (rev a2)
00:0c.0 0604: 10de:0374 (rev a2)
00:0d.0 0604: 10de:0378 (rev a2)
00:0e.0 0604: 10de:0375 (rev a2)
00:0f.0 0604: 10de:0377 (rev a2)
00:18.0 0600: 1022:1100
00:18.1 0600: 1022:1101
00:18.2 0600: 1022:1102
00:18.3 0600: 1022:1103
01:00.0 0104: 1095:0680 (rev 02)
01:02.0 0200: 100b:0020
01:04.0 0c00: 1106:3044 (rev 80)
06:00.0 0300: 10de:0163 (rev a1)
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: [E]
Detect CD: [O]
Load installer modules: [O]
Detect hard drives: [E]
Partition hard drives: [E]
Create file systems: [O]
Mount partitions: [O]
Install base system: [O]
Install boot loader: [O]
Reboot: [O]
Comments/Problems:
There were a number of problems, most critical however was that
The gigabit Ethernet adapter, and SATA adapter was not supported by the
installer.
I was using the sarge amg64 netinstall cd, hwever since it did not work,
i tried the more up to date testing daily image. Both failed to work,
however unlike the stable CD, the testing installer image would hard
lock If i tried to config network with the 1000/100 nic plugged in. This
problem was solved by dropping in an older netgear 10/100 NIC card in
for the install. Since the SATA was also not detected so i could not set
that up via the installer. When I tried to install raid 1 for the root
installer would error and not make raid1 arrays. i had planed to put LVM
on top of a raid 1 for root sys. Instead I just did LVM to see if it
worked, ill have to migrate the system over to raid1 manually later.
The most annoying thing was that once I had installed the system and got
rebooted, the sata adapter and the gigabit NIC was detected and I could
set up the array and use the NIC. I am not sure if there was a different
kernel in the installer than (using 2.6.8 just after reboot, i think)
got installed on the hdd but somting was odd about it.
Post installer notes:
After install the order of the NICs change, ie the firewire adapter is
not noticed in the installer, but once you reboot for the first time it
is, so the order of eth0 eth1 ... changes once the firewire card gets
its eth# designation. Sorta annoying if you are unlucky enough to have
your primary nic that was setup in the install bumped up a # like this.
You can't install packages via apt or ping anything until you manually
edit interfaces to fix this. And of course you don't know about it until
the installer drops you into tasksel to install packages. I have had to
help more than a few new “Debian geeks” fix this, since they are GUI
oriented and don't know what to do without their X11 or mc. These people
are unaware they can get a command prompt on another tty to fix this so
they often reboot and try install again, and fail again ...
tasksel does not work right, ie can't install “desktop” with it. It
errors out with error 255, this is probably just etch being etch, there
seems to be abit of dependency hell on some X bits right now. apt-get &
dselect worked fine.
gigabit adapter only works completely (works with ethtool etc...) under
newer kernels, I found 2.6.16 worked well.
Install logs and other status info is available in
/var/log/debian-installer/.
Once you have filled out this report, mail it to [EMAIL PROTECTED]
--
--------------------------------
James C. Baldwin, PhD
USDA-ARS-CCRU
501 N. Walnut St.
Madison, WI 53726
