Your message dated Sat, 20 Jul 2013 01:11:55 +0200
with message-id <[email protected]>
and subject line dealing with old installation-reports
has caused the Debian Bug report #576329,
regarding Fwd: Debian Failed 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 [email protected]
immediately.)
--
576329: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=576329
Debian Bug Tracking System
Contact [email protected] with problems
--- Begin Message ---
Package: installation-reports
Boot method: <How did you boot the installer? CD? floppy? network?>
DVD+R
Image version:
http://caesar.acc.umu.se/debian-cd/5.0.4/i386/iso-dvd/debian-504-i386-DVD-1.iso
Used Cygwin to check md5sum - matched 202b8e90d52b7eb3ed7294211f5aadfe
Date: 03-April-2010 - 09:00:00 GMT
Used Windows Server Resource Toolkit on a Windows XP SP 2 machine -
¨C:\Program Files\Windows Resource Kit\Tools\dvdburn.exe¨ l:
c:\Downloads\Software\Debian\debian-504-i386-DVD-1.iso
Preparing media...
- 100.0% done
Finished Writing
Waiting for drive to finalize disc (this may take up to 4
minutes)..........................
Success: Finalizing media took 25 seconds
Burn successful!
Machine: HP compaq nx9005 (AMD 1.2 GHZ)
Partitions: <df -Tl will do; the raw partition table is preferred>
Existing SUSE 10.1 partitioning - single partition - was going to replace the
partitions -not relevant as did not reach partitioning stage
Base System Installation Checklist:
[O] = OK, [E] = Error (please elaborate below), [ ] = didn't try it
Initial boot: [E] Could not read mirror bin
Detect network card: [E] Could not identify NIC -
Configure network: [E]
Detect CD: [O]
Load installer modules: [ ]
Detect hard drives: [ ]
Partition hard drives: [ ]
Install base system: [ ]
Clock/timezone setup: [ ]
User/password setup: [ ]
Install tasks: [ ]
Install boot loader: [ ]
Overall install: [ ]
Comments/Problems:
<Description of the install, in prose, and any thoughts, comments
and ideas you had during the initial install.>
--
Please make sure that the hardware-summary log file, and any other
installation logs that you think would be useful are attached to this
report. Please compress large files using gzip.
Once you have filled out this report, mail it to [email protected].
Hello
Good work from your team - my colleague fitted me with a server using Debian
and as an applications writer it is easily the best environment I have worked
with
I want to mirror my applications on a laptop - using a Debian Release.
What is strange about this error is the DVD I burned reads perfectly happily
from a newer DVD Drive (say about 2 years old) on machine about two years old
(HP 6336 ES) but on two 8 year old laptops HP Compaq nx9005 and Compaq
EVON1020V (attempted destinations) it gets stuck at the mirror bin finding
process - claiming the disk is corrupt.
I performed MD5sum checks on the files themselves and they appeared okay
I suspect I know the answer to this issue - DVD surface integrity is
compromised - or the laptop drives are shot - but just in case ...
Alternatively - should I check the firmware of the DVD - Drives ?
The template report has been completed to the best of my knowledge in
MainReport.txt
I used the following to create the attached archive
tar -cvf DebianFailedInstall.tar *
gzip DebianFailedInstall.tar
Many thanks
Derrin
DebianFailedInstall.tar.gz
Description: GNU Zip compressed data
--- End Message ---
--- Begin Message ---
Hi,
thank you for submitting installation reports, much appreciated.
I read through all the bugs mentioned here (and I'm sure they were read by
several people at the time they were submitted) and am closing them now as/if
- they (finally) indicated success and/or
- I know from first hand experience that the functionality is working in
Wheezy and/or
- they only contained very little information and/or
- they contained user errors and/or
- they have been from a development phase where things were not stable and/or
- they are very old, more than 2.5 years.
If I've closed a bug incorrectly please do reply (it's easy to reopen and I'll
do if requested) or just file a new one - thats often better, as the bug log
will be clearer and shorter and not contain cruft.
cheers,
Holger
signature.asc
Description: This is a digitally signed message part.
--- End Message ---
