Your message dated Fri, 29 Mar 2013 18:40:44 +0000 with message-id <1364582444.3520.95.camel@deadeye.wl.decadent.org.uk> and subject line Re: Bug#704138: "No disk drive was detected" during install has caused the Debian Bug report #704138, regarding "No disk drive was detected" during install 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.) -- 704138: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=704138 Debian Bug Tracking System Contact owner@bugs.debian.org with problems
--- Begin Message ---
- To: submit@bugs.debian.org
- Subject: "No disk drive was detected" during install
- From: Anshu Prateek <anshprat@gmail.com>
- Date: Thu, 28 Mar 2013 19:08:23 +0530
- Message-id: <CAK3Kwn5U-0Dcp+e5=tD7sqkFc8EAkNjeQLXZ8jvuy+BkCQd0rw@mail.gmail.com>
Package: installation-reports
Boot method: <How did you boot the installer? CD? floppy? network?>
Network/ pxe boot
Image version: <Full URL to image you downloaded is best>
http://ftp.nl.debian.org/debian/dists/squeeze/main/installer-amd64/current/images/
Date: <Date and time of the install>
March 28, 2013
Machine: <Description of machine (eg, IBM Thinkpad R32)> Custom build
Processor: i3-2120 lspci
Memory:
Partitions: <df -Tl will do; the raw partition table is preferred>
Output of lspci -knn (or lspci -nn):
00:00.0 Host bridge [0600]: Intel Corporation Sandy Bridge DRAM Controller [8086:0100] (rev 09
Subsystem: Intel Corporation Device [8086:2017] 00:02.0 VGA compatible controller [0300]: Intel Corporation Sandy Bridge Integrated Graphics Controller [8086:0102] (rev 09
Subsystem: Intel Corporation Device [8086:2017] 00:16.0 Communication controller [0780]: Intel Corporation Cougar Point HECI Controller #1 [8086:1c3a] (rev 04
Subsystem: Intel Corporation Device [8086:2017] 00:19.0 Ethernet controller [0200]: Intel Corporation 82579V Gigabit Network Connection [8086:1503] (rev 05
Subsystem: Intel Corporation Device [8086:2017] Kernel driver in use: e1000e 00:1a.0 USB Controller [0c03]: Intel Corporation Cougar Point USB Enhanced Host Co00:00.0 Host bridge [0600]: Intel Corporation Sandy Bridge DRAM Controller [8086:0100] (rev 09
Subsystem: Intel Corporation Device [8086:2017] 00:02.0 VGA compatible controller [0300]: Intel Corporation Sandy Bridge Integrated Graphics Controller [8086:0102] (rev 09
Subsystem: Intel Corporation Device [8086:2017] 00:16.0 Communication controller [0780]: Intel Corporation Cougar Point HECI Controller #1 [8086:1c3a] (rev 04
Subsystem: Intel Corporation Device [8086:2017] 00:19.0 Ethernet controller [0200]: Intel Corporation 82579V Gigabit Network Connection [8086:1503] (rev 05
Subsystem: Intel Corporation Device [8086:2017] Kernel driver in use: e1000e 00:1a.0 USB Controller [0c03]: Intel Corporation Cougar Point USB Enhanced Host Controller #2 [8086:1c2d] (rev 05
Subsystem: Intel Corporation Device [8086:2017] Kernel driver in use: ehci hcd 00:1b.0 Audio device [0403]: Intel Corporation Cougar Point High Definition Audio Controller [8086:1c20] (rev 05
Subsystem: Intel Corporation Device [8086:2017] 00:1c.0 PCI bridge [0604]: Intel Corporation Cougar Point PCI Express Root Port 1 [8086:1c10] (rev b5
Kernel driver in use: pcieport 00:1d.0 USB Controller [0c03]: Intel Corporation Cougar Point USB Enhanced Host Controller #1 [8086:1c26] (rev 05
Subsystem: Intel Corporation Device [8086:2017] Kernel driver in use: ehci hcd 00:1f.0 ISA bridge [0601]: Intel Corporation Cougar Point LPC Controller [8086:1c5c] (rev 05
Subsystem: Intel Corporation Device [8086:2017] 00:1f.2 SATA controller [0106]: Intel Corporation Cougar Point 6 port SATA AHCI Controller [8086:1c02] (rev 05
Subsystem: Intel Corporation Device [8086:2017] 00:1f.3 SMBus [0c05]: Intel Corporation Cougar Point SMBus Controller [8086:1c22] (rev 05
Subsystem: Intel Corporation Device [8086:2017] 01:00.0 PCI bridge [0604]: Integrated Technology Express, Inc. Device [1283:8892] (rev 30
Base System Installation Checklist:
[O] = OK, [E] = Error (please elaborate below), [ ] = didn't try it
Initial boot: [O]
Detect network card: [O]
Configure network: [O]
Detect CD: [-]
Load installer modules: [O]
Detect hard drives: [E]
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.>
Tried pxe install using netinst and 6.0.7 cd image.
Detect disks fail with : No disk drive was detected. If you know the name of the driver needed by your disk drive, you can select it from the list.
Tried on two similar systems, one with raw disk without any FS and no partitions, another with a vfat partition. It failed with both. (Seagate Barracuda 500 GB SATA)/var/log/syslog says:hw-detect:Loading PCMCIA bridge driver module: i82365FATAL:Module i82365 not foundcheck-missing-firmware: no missing firmware ..related board:regards
Anshu Prateek
--- End Message ---
--- Begin Message ---
- To: 704138-done@bugs.debian.org
- Subject: Re: Bug#704138: "No disk drive was detected" during install
- From: Ben Hutchings <ben@decadent.org.uk>
- Date: Fri, 29 Mar 2013 18:40:44 +0000
- Message-id: <1364582444.3520.95.camel@deadeye.wl.decadent.org.uk>
- In-reply-to: <1364545878377-2902234.post@n7.nabble.com>
- References: <CAK3Kwn5U-0Dcp+e5=tD7sqkFc8EAkNjeQLXZ8jvuy+BkCQd0rw@mail.gmail.com> <1364536625.3520.78.camel@deadeye.wl.decadent.org.uk> <1364545878377-2902234.post@n7.nabble.com>
On Fri, 2013-03-29 at 01:31 -0700, anshprat wrote: > I tried install with a cd rom image on USB and it worked! > So I tried the pxe boot image again, went through the logs and looks like > the scsi modules are missing in the netboot tar gz. > > 630: anna[1750]: DEBUG: resolver (scsi-modules-2.6.32-5-amd64-di): package > doesn't exist (ignored) > > [anshup@isis in]$ grep -inr scsi-modules var/lib/dpkg/status > > Same thing on the cd initrd gives.. > [anshup@isis in]$ grep -inr scsi-modules ../../cd/in/var/lib/dpkg/status > 126:Package: scsi-modules-2.6.32-5-amd64-di > 129:Provides: scsi-modules > > [anshup@isis in]$ cat var/lib/dpkg/status |grep scsi|grep Pack > Package: scsi-modules-2.6.32-5-amd64-di > Package: scsi-common-modules-2.6.32-5-amd64-di > Package: scsi-core-modules-2.6.32-5-amd64-di > [anshup@isis in]$ cat ../../netboot/in/var/lib/dpkg/status |grep scsi|grep > Pack > Package: scsi-core-modules-2.6.32-5-amd64-di > > > so issue is with the netboot initrd missing scsi modules I guess? No, this is correct - the netboot image should only contain network driver modules, and will install the others from the network. > I ve attached the syslog files in netboot vs cd-through-usb cases > > regards > Anshu Prateek > syslog.pxe.txt <http://debian.2.n7.nabble.com/file/n2902234/syslog.pxe.txt> > syslog.cd.usb.txt > <http://debian.2.n7.nabble.com/file/n2902234/syslog.cd.usb.txt> Your Debian mirror is broken. Ben. -- Ben Hutchings I'm not a reverse psychological virus. Please don't copy me into your sig.Attachment: signature.asc
Description: This is a digitally signed message part
--- End Message ---