Bug#283556: marked as done (Netinst MD5 Error on P3)
Your message dated Tue, 30 Nov 2004 07:04:03 +0100
with message-id <20041130060403.GM6011@mykerinos.kheops.frmug.org>
and subject line Bug#283556: Netinst MD5 Error on P3
has caused the attached Bug 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 I am
talking about this indicates a serious mail system misconfiguration
somewhere. Please contact me immediately.)
Debian bug tracking system administrator
(administrator, Debian Bugs database)
--------------------------------------
Received: (at submit) by bugs.debian.org; 29 Nov 2004 20:46:08 +0000
>From jjwdeck@juno.com Mon Nov 29 12:46:08 2004
Return-path: <jjwdeck@juno.com>
Received: from m03.lax.untd.com [64.136.30.66]
by spohr.debian.org with smtp (Exim 3.35 1 (Debian))
id 1CYsPQ-00057G-00; Mon, 29 Nov 2004 12:46:08 -0800
Received: from m03.lax.untd.com (localhost [127.0.0.1])
by m03.lax.untd.com with SMTP id AABA4ZCUJAW75JY2
for <submit@bugs.debian.org> (sender <jjwdeck@juno.com>);
Mon, 29 Nov 2004 12:44:56 -0800 (PST)
X-UNTD-OriginStamp: R181uPBMqFMsynUYXHfDoqjNpxtilqJA93QmYlRIN3m+RxW+/OGhsg==
Received: (from jjwdeck@juno.com)
by m03.lax.untd.com (jqueuemail) id KDMQAG5T; Mon, 29 Nov 2004 12:44:16 PST
To: submit@bugs.debian.org
Date: Mon, 29 Nov 2004 14:39:22 -0600
Subject: Netinst MD5 Error on P3
Message-ID: <[🔎] 20041129.143948.-872403.2.jjwdeck@juno.com>
X-Mailer: Juno 5.0.33
MIME-Version: 1.0
Content-Type: multipart/alternative; boundary=--__JNP_000_6125.5ca3.4d05
X-Juno-Line-Breaks: 8-6,7-8,10,12,14-20,22,31,33-35,46-47,53-74,77-78,81-85,88-95,97-99,101,103,105,107,110-111,114,118-119,120-32767
From: John J Waldeck <jjwdeck@juno.com>
X-ContentStamp: 13:6:3692542229
X-MAIL-INFO: 330d8120cda5e929f135cdcdf17564ad8dc0e0f0e4fd45c0c0fd55f0f1f050b0fdb5ed242d99f4dd71d040892d0165b421d11dddd485d5d1d18544ddc4dd5d898564607dc1015d201585b99d74d97944709d9d4490a9c924a9d0d0752dfd652da4b499a444844490a5e1d4c940dd7d4045458941305d41193815
Delivered-To: submit@bugs.debian.org
X-Spam-Checker-Version: SpamAssassin 2.60-bugs.debian.org_2004_03_25
(1.212-2003-09-23-exp) on spohr.debian.org
X-Spam-Status: No, hits=-2.4 required=4.0 tests=BAYES_20,HAS_PACKAGE,
HTML_10_20,HTML_MESSAGE,OFFER autolearn=no
version=2.60-bugs.debian.org_2004_03_25
X-Spam-Level:
This message is in MIME format. Since your mail reader does not understand
this format, some or all of this message may not be legible.
----__JNP_000_6125.5ca3.4d05
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Package: installation-reports
Debian-installer-version: Debian GNU/Linux testing "Sarge" - Official
Snapshot i386 Binary-1 (20040930),
Obtained from (?) http://linux.csua.berkeley.edu/debian/ approximately
September 24, 2004
uname -a: Linux (none) 2.4.27-1-386 #1 Fri Sep 3 06:24:46 UTC 2004 i686
unknownDate: mid November, 2004 and November 29, 2004 13:40
Method: Netinst from CDROM
Machine: ASUS CUSL2-C
Processor: Intel Pentium III, 733MHz
Memory: 256 MB, SDRAM
Root Device: IDE, /dev/hda6 (using woody device structure and fdisk)
Disk /dev/hda: 255 heads, 63 sectors, 7473 cylindersUnits = cylinders of
16065 * 512 bytes
Device Boot Start End Blocks Id System/dev/hda1
1 12 96358+ 83 Linux/dev/hda2 13 273
2096482+ 16 Hidden FAT16/dev/hda3 * 274 795 4192965
b Win95 FAT32/dev/hda4 796 7473 53641035 5
Extended/dev/hda5 796 925 1044193+ 82 Linux
swap/dev/hda6 926 1447 4192933+ 83 Linux/dev/hda7
1448 2491 8385898+ 83 Linux/dev/hda8 2492 4057
12578863+ 83 Linux/dev/hda9 4058 4840 6289416 83
Linux
Root /dev/hda6 was never accessed as the installation failed before
partitioning and mount of root.
Output of lspci and lspci -n:
lspci:
00:00.0 Host bridge: Intel Corp. 82815 815 Chipset Host Bridge and Memory
Controller Hub (rev 02)00:01.0 PCI bridge: Intel Corp.: Unknown device
1131 (rev 02)00:1e.0 PCI bridge: Intel Corp. 82820 820 (Camino 2) Chipset
PCI (rev 02)00:1f.0 ISA bridge: Intel Corp. 82820 820 (Camino 2) Chipset
ISA Bridge (ICH2) (rev 02)00:1f.1 IDE interface: Intel Corp. 82820 820
(Camino 2) Chipset IDE U100 (rev 02)00:1f.2 USB Controller: Intel Corp.
82820 820 (Camino 2) Chipset USB (Hub A) (rev 02)00:1f.3 SMBus: Intel
Corp. 82820 820 (Camino 2) Chipset SMBus (rev 02)00:1f.4 USB Controller:
Intel Corp. 82820 820 (Camino 2) Chipset USB (Hub B) (rev 02)01:00.0 VGA
compatible controller: ATI Technologies Inc Rage 128 RF02:0e.0 Serial
controller: US Robotics/3Com 56K FaxModem Model 5610 (rev 01)
lspci -n:
00:00.0 Class 0600: 8086:1130 (rev 02)00:01.0 Class 0604: 8086:1131 (rev
02)00:1e.0 Class 0604: 8086:244e (rev 02)00:1f.0 Class 0601: 8086:2440
(rev 02)00:1f.1 Class 0101: 8086:244b (rev 02)00:1f.2 Class 0c03:
8086:2442 (rev 02)00:1f.3 Class 0c05: 8086:2443 (rev 02)00:1f.4 Class
0c03: 8086:2444 (rev 02)01:00.0 Class 0300: 1002:524602:0e.0 Class 0700:
12b9:1008 (rev 01)
Base System Installation Checklist:
[O] = OK, [E] = Error (please elaborate below), [ ] = didn't try it
Initial boot worked: [O ]
Configure network HW: [ ]
Config network: [ ]
Detect CD: [O ]
Load installer modules: [E ]
Detect hard drives: [ ]
Partition hard drives: [ ]
Create file systems: [ ]
Mount partitions: [ ]
Install base system: [ ]
Install boot loader: [ ]
Reboot: [ ]
Comments/Problems:
<Description of the install, in prose, and any thoughts, comments
and ideas you had during the initial install.>
Booted Netinst CD, taking default installation (enter at prompt).
Automatically proceeded through Detected Hardware to find CD-ROM drive
and Scaning CD-ROM.
Error occurred in [!!] Load installer components from CD:
There was a problem reading data from the CDROM. Please make
sure it is in the drive. If retrying does not work, you should check the
integrity of your CDROM.
Failed to copy file from CDROM
When retry didn't work, got the message:
[!!] Load installer components from CD
Installation step failed
An installation step failed. You can try to run the failing item
again from the menu, or skip it and choose something else. The failing
step is: Load installer components from CD.
At this point I checked alternate screens 3 and 4:
Alt-F3:
insmod cdrom
insmod ide-cd
Using /lib/modules/2.4.27-1-386/kernel/fs/isofs/isofs.o
insmod isofs
Alt-F4:
Nov 29 13:41:50 anna [2881]: DEBUG : resolver
(wireless-tools-udeb): mark
Nov 29 13:41:50 anna [2881]: WARNING **: bad md5sum
Nov 29 13:42:36 main-menu [321]: (process: 2879): md5sum
Nov 29 13:42:36 main-menu [321]: (process: 2879)
/var/cache/anna/mdadm-udeb_1.7.0-1_i386.udeb
Nov 29 13:42:36 main-menu [321]: (process: 2879): : Input/output
error
Nov 29 13:42:36 main-menu [321]: WARNING **: Configuring
'load-cdrom' failed with error code 7
Nov 29 13:42:36 main-menu [321]: WARNING **: Menu item
'load-cdrom' failed.
Checked CD-ROM integrity and it failed MD5 checksum verification on
./install/2.6/initrd.gzThe checksum in the MD5SUM.TXT file on the CD
was
d0e0ecffd33d919023ded989eb860bce ./install/2.6/initrd.gz
I ran the MD5SUM.EXE on the component and found it to be the same as the
checksum on the MD5SUM.TXT file on the CD:
d0e0ecffd33d919023ded989eb860bce *initrd.gz
Possibly related to Bug#283378. I suspect there is a difference between
this P3 machine that doesn't load sarge, and the P4 machine in the above
bug that doesn't load woody but does load sarge (installation-report
success to be filed).
----__JNP_000_6125.5ca3.4d05
Content-Type: text/html; charset=us-ascii
Content-Transfer-Encoding: quoted-printable
<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">
<HTML><HEAD>
<META content=3Dtext/html;charset=3Diso-8859-1 http-equiv=3Dcontent-type>
<META content=3D"MSHTML 5.00.2314.1000" name=3DGENERATOR></HEAD>
<BODY bottomMargin=3D0 leftMargin=3D3 rightMargin=3D3 topMargin=3D0><PRE>=
Package: installation-reports
Debian-installer-version: Debian GNU/Linux testing "Sarge" - Official =
Snapshot i386 Binary-1 (20040930),</PRE><PRE>Obtained from (?) <FONT size=
=3D2><A href=3D"http://linux.csua.berkeley.edu/debian/";>http://linux.csua.=
berkeley.edu/debian/</A> approximately September 24, 2004 </FONT></PRE><PRE=
>uname -a: Linux (none) 2.4.27-1-386 #1 Fri Sep 3 06:24:46 UTC 2004 i686 =
unknown<BR>Date: mid November, 2004 and November 29, 2004 13:40
Method: Netinst from CDROM
Machine: ASUS CUSL2-C
Processor: Intel Pentium III, 733MHz
Memory: 256 MB, SDRAM
Root Device: IDE, /dev/hda6 (using woody device structure and fdisk)</PRE><=
PRE>Disk /dev/hda: 255 heads, 63 sectors, 7473 cylinders<BR>Units =3D =
cylinders of 16065 * 512 bytes</PRE><PRE> Device Boot &=
nbsp; Start End =
Blocks Id System<BR>/dev/hda1 &=
nbsp; 1 &=
nbsp; 12 96358+ 83 Linux<BR=
>/dev/hda2  =
; 13 273 2096482+ 16&=
nbsp; Hidden FAT16<BR>/dev/hda3 * =
274 795 4192965 =
; b Win95 FAT32<BR>/dev/hda4  =
; 796 7473 =
; 53641035 5 Extended<BR>/dev/hda5  =
; 796 &=
nbsp; 925 1044193+ 82 Linux swap<BR>/dev/hda6=
926  =
; 1447 4192933+ 83 Linux<BR>/dev/=
hda7 1448 =
2491 8385898+ 83 Linux<BR>/dev/=
hda8 2492 =
4057 12578863+ 83 Linux<BR>/dev/hda9&=
nbsp; 4058  =
; 4840 6289416 83 Linux</PRE><PRE=
>Root /dev/hda6 was never accessed as the installation failed before =
partitioning and mount of root.</PRE><PRE>Output of lspci and lspci -n:</=
PRE><PRE>lspci:</PRE><PRE>00:00.0 Host bridge: Intel Corp. 82815 815 =
Chipset Host Bridge and Memory Controller Hub (rev 02)<BR>00:01.0 PCI =
bridge: Intel Corp.: Unknown device 1131 (rev 02)<BR>00:1e.0 PCI bridge: =
Intel Corp. 82820 820 (Camino 2) Chipset PCI (rev 02)<BR>00:1f.0 ISA bridge=
: Intel Corp. 82820 820 (Camino 2) Chipset ISA Bridge (ICH2) (rev 02)<BR>00=
:1f.1 IDE interface: Intel Corp. 82820 820 (Camino 2) Chipset IDE U100 (rev=
02)<BR>00:1f.2 USB Controller: Intel Corp. 82820 820 (Camino 2) Chipset =
USB (Hub A) (rev 02)<BR>00:1f.3 SMBus: Intel Corp. 82820 820 (Camino 2) =
Chipset SMBus (rev 02)<BR>00:1f.4 USB Controller: Intel Corp. 82820 820 (=
Camino 2) Chipset USB (Hub B) (rev 02)<BR>01:00.0 VGA compatible controller=
: ATI Technologies Inc Rage 128 RF<BR>02:0e.0 Serial controller: US =
Robotics/3Com 56K FaxModem Model 5610 (rev 01)<BR></PRE><PRE>lspci -n:</PRE=
><PRE>00:00.0 Class 0600: 8086:1130 (rev 02)<BR>00:01.0 Class 0604: 8086:=
1131 (rev 02)<BR>00:1e.0 Class 0604: 8086:244e (rev 02)<BR>00:1f.0 Class =
0601: 8086:2440 (rev 02)<BR>00:1f.1 Class 0101: 8086:244b (rev 02)<BR>00:1f=
.2 Class 0c03: 8086:2442 (rev 02)<BR>00:1f.3 Class 0c05: 8086:2443 (rev 02)=
<BR>00:1f.4 Class 0c03: 8086:2444 (rev 02)<BR>01:00.0 Class 0300: 1002:5246=
<BR>02:0e.0 Class 0700: 12b9:1008 (rev 01)<BR>
Base System Installation Checklist:
[O] =3D OK, [E] =3D Error (please elaborate below), [ ] =3D didn't try it
Initial boot worked: [O ]
Configure network HW: [ ]
Config network: [ ]
Detect CD: [O ]
Load installer modules: [E ]
Detect hard drives: [ ]
Partition hard drives: [ ]
Create file systems: [ ]
Mount partitions: [ ]
Install base system: [ ]
Install boot loader: [ ]
Reboot: [ ]
Comments/Problems:
<Description of the install, in prose, and any thoughts, comments
and ideas you had during the initial install.></PRE><PRE>Booted =
Netinst CD, taking default installation (enter at prompt). Automatically =
proceeded through Detected Hardware to find CD-ROM drive and Scaning CD-ROM=
. </PRE><PRE>Error occurred in [!!] Load installer components from CD:</=
PRE><PRE> There was a problem =
reading data from the CDROM. Please make sure it is in the drive. If =
retrying does not work, you should check the integrity of your CDROM.</PRE>=
<PRE> Failed to copy file from =
CDROM</PRE><PRE>When retry didn't work, got the message:</PRE><PRE> &=
nbsp; [!!] Load installer components from CD<=
/PRE><PRE> Installation step =
failed</PRE><PRE> An installation=
step failed. You can try to run the failing item again from the menu, or =
skip it and choose something else. The failing step is: Load installer =
components from CD.</PRE><PRE>At this point I checked alternate screens 3 =
and 4:</PRE><PRE>Alt-F3:</PRE><PRE> &=
nbsp; insmod cdrom</PRE><PRE> =
insmod ide-cd</PRE><PRE> Using /=
lib/modules/2.4.27-1-386/kernel/fs/isofs/isofs.o</PRE><PRE> &=
nbsp; insmod isofs</PRE><PRE>Alt-F4:</PRE><PRE>&=
nbsp; Nov 29 13:41:50 anna [2881]: =
DEBUG : resolver (wireless-tools-udeb): mark</PRE><PRE> &=
nbsp; Nov 29 13:41:50 anna [2881]: WARNING **: bad md5sum=
</PRE><PRE> Nov 29 13:42:36 main-=
menu [321]: (process: 2879): md5sum</PRE><PRE>  =
; Nov 29 13:42:36 main-menu [321]: (process: 2879) /var/cache/=
anna/mdadm-udeb_1.7.0-1_i386.udeb</PRE><PRE> &=
nbsp; Nov 29 13:42:36 main-menu [321]: (process: 2879): : Input/=
output error</PRE><PRE> Nov 29 13=
:42:36 main-menu [321]: WARNING **: Configuring 'load-cdrom' failed with =
error code 7</PRE><PRE> Nov 29 13=
:42:36 main-menu [321]: WARNING **: Menu item 'load-cdrom' failed.</PRE><=
PRE>Checked CD-ROM integrity and it failed MD5 checksum verification on <BR=
> <BR> ./install/2.6/initrd.=
gz<BR>The checksum in the MD5SUM.TXT file on the CD was</PRE><PRE> &=
nbsp; d0e0ecffd33d919023ded989eb860bce ./=
install/2.6/initrd.gz<BR> </PRE><PRE>I ran the MD5SUM.EXE on the =
component and found it to be the same as the checksum on the MD5SUM.TXT =
file on the CD:<BR> <BR> =
d0e0ecffd33d919023ded989eb860bce *initrd.gz </PRE><PRE>Possibly =
related to Bug#283378. I suspect there is a difference between this P3 =
machine that doesn't load sarge, and the P4 machine in the above bug that =
doesn't load woody but does load sarge (installation-report success to be =
filed).</PRE><PRE> </PRE><PRE> </PRE>
<HR noShade SIZE=3D1 width=3D"100%">
</BODY></HTML>
----__JNP_000_6125.5ca3.4d05--
________________________________________________________________
Juno Platinum $9.95. Juno SpeedBand $14.95.
Sign up for Juno Today at http://www.juno.com!
Look for special offers at Best Buy stores.
---------------------------------------
Received: (at 283556-done) by bugs.debian.org; 30 Nov 2004 07:11:42 +0000
>From bubulle@kheops.frmug.org Mon Nov 29 23:11:42 2004
Return-path: <bubulle@kheops.frmug.org>
Received: from onera.onera.fr [144.204.65.4]
by spohr.debian.org with esmtp (Exim 3.35 1 (Debian))
id 1CZ2Ao-0004QG-00; Mon, 29 Nov 2004 23:11:42 -0800
Received: from cc-mykerinos.onera (localhost [127.0.0.1])
by onera.onera.fr with ESMTP id iAU7BeXU020457;
Tue, 30 Nov 2004 08:11:40 +0100 (MET)
Received: by mykerinos.kheops.frmug.org (Postfix, from userid 7426)
id 24104232A1; Tue, 30 Nov 2004 07:04:04 +0100 (CET)
Date: Tue, 30 Nov 2004 07:04:03 +0100
From: Christian Perrier <bubulle@debian.org>
To: John J Waldeck <jjwdeck@juno.com>, 283556-done@bugs.debian.org
Subject: Re: Bug#283556: Netinst MD5 Error on P3
Message-ID: <20041130060403.GM6011@mykerinos.kheops.frmug.org>
References: <[🔎] 20041129.143948.-872403.2.jjwdeck@juno.com>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <[🔎] 20041129.143948.-872403.2.jjwdeck@juno.com>
X-message-flag: Outlook is a good virus spreading tool. It can send mail, too.
X-pot_a_miel: honeypot@kheops.frmug.org
User-Agent: Mutt/1.5.6+20040907i
Delivered-To: 283556-done@bugs.debian.org
X-Spam-Checker-Version: SpamAssassin 2.60-bugs.debian.org_2004_03_25
(1.212-2003-09-23-exp) on spohr.debian.org
X-Spam-Status: No, hits=-6.0 required=4.0 tests=BAYES_00,HAS_BUG_NUMBER
autolearn=no version=2.60-bugs.debian.org_2004_03_25
X-Spam-Level:
Quoting John J Waldeck (jjwdeck@juno.com):
>
> Package: installation-reports
>
> Debian-installer-version: Debian GNU/Linux testing "Sarge" - Official Snapshot
> i386 Binary-1 (20040930),
> Obtained from (?) [1]http://linux.csua.berkeley.edu/debian/ approximately Septe
> mber 24, 2004
Please test a more recent version of the installer, which you will
find from http://www.debian.org/devel/debian-installer.
Older versions are not supported anymore by the d-i team.
> Checked CD-ROM integrity and it failed MD5 checksum verification on
>
> ./install/2.6/initrd.gz
> The checksum in the MD5SUM.TXT file on the CD was
> d0e0ecffd33d919023ded989eb860bce ./install/2.6/initrd.gz
>
> I ran the MD5SUM.EXE on the component and found it to be the same as the checks
> um on the MD5SUM.TXT file on the CD:
>
> d0e0ecffd33d919023ded989eb860bce *initrd.gz
All this seem to indicate some mess on the burnt cd-rom or some other
problem not related to the installer itself.
Hence closing the bug report. Thanks for your time testing the
installer.
Reply to: