[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

Bug#686786: marked as done (Fwd: Installation report: unable to detect netinst ISO image present on hard drive)



Your message dated Sun, 25 Aug 2013 12:42:38 +0200
with message-id <201308251243.25305.holger@layer-acht.org>
and subject line dealing with old installation-reports
has caused the Debian Bug report #686786,
regarding Fwd: Installation report: unable to detect netinst ISO image present on hard drive
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 owner@bugs.debian.org
immediately.)


-- 
686786: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=686786
Debian Bug Tracking System
Contact owner@bugs.debian.org with problems
--- Begin Message ---
Package: base
version: 7.0beta1


Debian,

                    Reg:  Debian installer 7.0 beta1

   
hd-media image (usb stick, netboot - vmlinuz & initrd.gz ) installer program fails to detect the ISO image present on the hard disk when it encounters any unformatted partition while search for ISO image.

Installation process hangs since the installer would not mount the partitions.

Thanking you,
anandarpm@gmail.com













--- End Message ---
--- Begin Message ---
reassign 701201 src:linux
retitle 701201 libata.atapi_passthru16=0 is needed by some hardware
forcemerge 690985 686954
thanks

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 were caused by broken hardware and/or
- they have been from a development phase where things were not stable and/or
- they are quite old (and thus likely fixed today) and/or
- moreinfo was asked and not given.

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

Attachment: signature.asc
Description: This is a digitally signed message part.


--- End Message ---

Reply to: