Your message dated Wed, 08 Sep 2010 03:58:00 +0000
with message-id <e1otbnm-0004j8...@ravel.debian.org>
and subject line Closing old installation report #312651
has caused the Debian Bug report #312651,
regarding Install report
to be marked as done.
This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.
(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact ow...@bugs.debian.org
immediately.)
--
312651: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=312651
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: installation-reports
Debian-installer-version: sarge-i386-netinst.iso 20050322, downloaded
June 06, 2005 from
http://cdimage.debian.org/pub/cdimage-testing/sarge_d-i/i386/rc3/sarge-i386-netinst.iso
uname -a: Linux sseyweb 2.4.27-2-386 #1 Thu Jan 20 10:55:08 JST 2005
i686 GNU/Linux
Date: June 08, 2005 15:00
Method: Netinst, Boot from RC3 netinst ISO, packages from
http://ftp.de.debian.org, no proxy
Machine: Transtec 1300
Processor: Pentium III @ 733 MHz
Memory: 1 GB (2x 512M SDRAM PC-133)
Root Device: Two Samsung SP2014N P-IDE drives in a RAID-1 setup
Root Size/partition table:
Disk /dev/hda: 200.0 GB, 200049647616 bytes
255 heads, 63 sectors/track, 24321 cylinders
Units = cylinders of 16065 * 512 = 8225280 bytes
Device Boot Start End Blocks Id System
Mount*1
/dev/hda1 * 1 16 128488+ fd Linux raid
autodetect /boot
/dev/hda2 17 514 4000185 fd Linux raid
autodetect /
/dev/hda3 515 757 1951897+ 82 Linux swap /
Solaris swap
/dev/hda4 758 24321 189277830 5 Extended
/dev/hda5 758 1243 3903763+ fd Linux raid
autodetect /usr
/dev/hda6 1244 3188 15623181 fd Linux raid
autodetect /var
/dev/hda7 3189 5620 19535008+ fd Linux raid
autodetect /catusr01
/dev/hda8 5621 6836 9767488+ fd Linux raid
autodetect /catiaserv
/dev/hda9 6837 24321 140448231 fd Linux raid
autodetect /seyhome
*1 Obviously, the partitions aren't mounted directly but (except for the
swap partition) are
part of a mirror. The second harddisk, hdc, is partitioned
identically and contains the
other halves of the mirrors
Output of lspci and lspci -n:
0000:00:00.0 0600: 1106:0691 (rev c4)
0000:00:01.0 0604: 1106:8598
0000:00:07.0 0601: 1106:0686 (rev 22)
0000:00:07.1 0101: 1106:0571 (rev 10)
0000:00:07.2 0c03: 1106:3038 (rev 10)
0000:00:07.4 0c05: 1106:3057 (rev 30)
0000:00:0f.0 0200: 1011:0019 (rev 41)
0000:01:00.0 0300: 10de:002d (rev 15)
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]*2
Detect CD: [O]
Load installer modules: [O]
Detect hard drives: [O]
Partition hard drives: [O]*3
Create file systems: [O]*4
Mount partitions: [O]
Install base system: [O]*5
Install boot loader: [E]*6
Reboot: [O]
Comments/Problems:
*2 User should be able to select manual configuration or DHCP. There may
be networks that
do not use DHCP, causing a pause in the install. Or worse, DHCP is
in use on the net
but wasn't intended to be used in the install.
*3 To make RAID-1 installations easier it would be helpful to have a
menu option for duplicating
the partition table of another harddisk (a la sfdisk -d <dev1> |
sfdisk <dev2>).
*4 I was not able to reproduce this but in the first installation
attempt the md devices were still
syncing (not sure if that is what caused the problem but felt that
way). The sync process was
very slow (1000+ minutes for a 140G partition according to
/proc/mdstat).
The installer hung when trying to do "something". What exactly it
was doing is beyond me, the
progress dialog had no title and stayed at 0% for over half an hour,
after which I rebooted.
To make matters worse it had somehow gotten on console 2 (but still
was accepting input from
console 1, not 2), blocking access to the shell. The installer
background color had changed from
blue to red if that helps any. No further diagnostics possible since
the shell was blocked.
*5 The installer wasn't able to access the package list of the security
update site:
Err http://security.debian.org testing/updates/contrib Packages
404 Not Found
*6 GRUB was only installed on the first harddisk's MBR so booting off
the other mirror side is not
possible. Since the system will crash when a harddisk fails (swap is
not mirrored) it will not
boot up again if the 1st harddisk fails. Not good. Kinda defeats the
purpose of a mirror.
All in all the install went well, except for the major glitch with GRUB.
--- 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 ---