Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]

Groups > linux.debian.bugs.dist > #828553 > unrolled thread

Bug#864715: USB netinst fails to identify /media/cdrom as a path for base system packages or /cdrom mounting

Back to article view | Back to linux.debian.bugs.dist

Contents

  Bug#864715: USB netinst fails to identify /media/cdrom as a path for base system packages or /cdrom mounting Amos Jeffries <squid3@treenet.co.nz> - 2017-06-13 14:00 +0200
    Bug#864715: USB netinst fails to identify /media/cdrom as a path for base system packages or /cdrom mounting Steve McIntyre <steve@einval.com> - 2017-06-13 14:50 +0200
      Bug#864715: USB netinst fails to identify /media/cdrom as a path for base system packages or /cdrom mounting Amos Jeffries <squid3@treenet.co.nz> - 2017-06-13 17:00 +0200
        Bug#864715: USB netinst fails to identify /media/cdrom as a path for base system packages or /cdrom mounting Steve McIntyre <steve@einval.com> - 2017-06-13 17:50 +0200
          Bug#864715: USB netinst fails to identify /media/cdrom as a path for base system packages or /cdrom mounting Amos Jeffries <squid3@treenet.co.nz> - 2017-06-13 18:20 +0200

#828553 — Bug#864715: USB netinst fails to identify /media/cdrom as a path for base system packages or /cdrom mounting

Package: installation-reports

On running the installer manually from inside the OEM Windows installed, 
everything appeared to run smoothly up to the reboot following partition 
and formatting of the machines drives. On that boot the installer now 
running off the HDD began looping at the "Install base system" step, no 
errors or other signs of trouble - just display the progress bar for a 
few mins, then flick out to the step-by-step listing as if that step was 
done - but highlighting the same "Install base system" entry every time 
enter was pressed to start the step.

Manually going to the next step on the list failed with a message about 
the base system not being fully present.

Skipping to the shell for manual inspection showed that the path /cdrom 
was being searched for the image packages but non-existent already 
(expected after install is complete, but not halfway through). Since 
this was a USB based install the netinst image had been loaded as 
/media/cdrom, and /dev/cdrom was not a mountable device since the CD/DVD 
drive did not have a disk.

Manually creating a symlink "ln -s /media/cdrom /cdrom" allowed the 
installer to continue and successfully install the system.

NP: if this is not already fixed in the latest 1-2 installer versions it 
really should be handled for Stretch. This has a high potential for 
newbies "bricking" their machines since they will not readily know the 
manual fix necessary.


  -- Package-specific info:

Boot method: netinst image on a USB drive, run from Windows 7
Image version: unknown sorry, downloaded from Debian mirrors 2017-05-12
Date: 2017-05-21

Machine: Dell
Processor: Intel Celeron (64-bit quad-core)
Memory: 4GB
Partitions:
ilesystem     Type     1K-blocks     Used Available Use% Mounted on
udev           devtmpfs     10240        0     10240   0% /dev
tmpfs          tmpfs       400936    46044    354892  12% /run
/dev/dm-0      ext4     149393716 12988176 128793740  10% /
tmpfs          tmpfs      1002340        0   1002340   0% /dev/shm
tmpfs          tmpfs         5120        0      5120   0% /run/lock
tmpfs          tmpfs      1002340        0   1002340   0% /sys/fs/cgroup


  Output of lspci -knn (or lspci -nn):
00:00.0 Host bridge [0600]: Intel Corporation 4 Series Chipset DRAM 
Controller [8086:2e10] (rev 03)
00:01.0 PCI bridge [0604]: Intel Corporation 4 Series Chipset PCI 
Express Root Port [8086:2e11] (rev 03)
00:02.0 VGA compatible controller [0300]: Intel Corporation 4 Series 
Chipset Integrated Graphics Controller [8086:2e12] (rev 03)
00:02.1 Display controller [0380]: Intel Corporation 4 Series Chipset 
Integrated Graphics Controller [8086:2e13] (rev 03)
00:03.0 Communication controller [0780]: Intel Corporation 4 Series 
Chipset HECI Controller [8086:2e14] (rev 03)
00:03.2 IDE interface [0101]: Intel Corporation 4 Series Chipset PT IDER 
Controller [8086:2e16] (rev 03)
00:03.3 Serial controller [0700]: Intel Corporation 4 Series Chipset 
Serial KT Controller [8086:2e17] (rev 03)
00:19.0 Ethernet controller [0200]: Intel Corporation 82567LM-3 Gigabit 
Network Connection [8086:10de] (rev 02)
00:1a.0 USB controller [0c03]: Intel Corporation 82801JD/DO (ICH10 
Family) USB UHCI Controller #4 [8086:3a67] (rev 02)
00:1a.1 USB controller [0c03]: Intel Corporation 82801JD/DO (ICH10 
Family) USB UHCI Controller #5 [8086:3a68] (rev 02)
00:1a.2 USB controller [0c03]: Intel Corporation 82801JD/DO (ICH10 
Family) USB UHCI Controller #6 [8086:3a69] (rev 02)
00:1a.7 USB controller [0c03]: Intel Corporation 82801JD/DO (ICH10 
Family) USB2 EHCI Controller #2 [8086:3a6c] (rev 02)
00:1b.0 Audio device [0403]: Intel Corporation 82801JD/DO (ICH10 Family) 
HD Audio Controller [8086:3a6e] (rev 02)
00:1c.0 PCI bridge [0604]: Intel Corporation 82801JD/DO (ICH10 Family) 
PCI Express Port 1 [8086:3a70] (rev 02)
00:1c.1 PCI bridge [0604]: Intel Corporation 82801JD/DO (ICH10 Family) 
PCI Express Port 2 [8086:3a72] (rev 02)
00:1d.0 USB controller [0c03]: Intel Corporation 82801JD/DO (ICH10 
Family) USB UHCI Controller #1 [8086:3a64] (rev 02)
00:1d.1 USB controller [0c03]: Intel Corporation 82801JD/DO (ICH10 
Family) USB UHCI Controller #2 [8086:3a65] (rev 02)
00:1d.2 USB controller [0c03]: Intel Corporation 82801JD/DO (ICH10 
Family) USB UHCI Controller #3 [8086:3a66] (rev 02)
00:1d.7 USB controller [0c03]: Intel Corporation 82801JD/DO (ICH10 
Family) USB2 EHCI Controller #1 [8086:3a6a] (rev 02)
00:1e.0 PCI bridge [0604]: Intel Corporation 82801 PCI Bridge 
[8086:244e] (rev a2)
00:1f.0 ISA bridge [0601]: Intel Corporation 82801JDO (ICH10DO) LPC 
Interface Controller [8086:3a14] (rev 02)
00:1f.2 RAID bus controller [0104]: Intel Corporation SATA Controller 
[RAID mode] [8086:2822] (rev 02)
00:1f.3 SMBus [0c05]: Intel Corporation 82801JD/DO (ICH10 Family) SMBus 
Controller [8086:3a60] (rev 02)




  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:              [O]
Load installer modules: [O]
Detect hard drives:     [O]
Partition hard drives:  [O]
Install base system:    [E]
Clock/timezone setup:   [O]
User/password setup:    [O]
Install tasks:          [O]
Install boot loader:    [O]
Overall install:        [O]

Comments/Problems:

Just the one mentioned above. Same image has been used on prior machines 
and more recent one no problems. But those were all done starting from a 
boot from the USB containing installer image. This attempt seeing issues 
is the one and only time OEM's Windows install has needed to be used to 
bootstrap the installation process.


Cheers
AYJ

[toc] | [next] | [standalone]

#828557

On Tue, Jun 13, 2017 at 11:39:46PM +1200, Amos Jeffries wrote:
>Package: installation-reports
>
>On running the installer manually from inside the OEM Windows installed,
>everything appeared to run smoothly up to the reboot following partition and
>formatting of the machines drives. On that boot the installer now running off
>the HDD began looping at the "Install base system" step, no errors or other
>signs of trouble - just display the progress bar for a few mins, then flick
>out to the step-by-step listing as if that step was done - but highlighting
>the same "Install base system" entry every time enter was pressed to start
>the step.

Ummm... Question: you say "up to the reboot following partition and
formatting of the machines drives". debian-installer doesn't reboot
there. How did you prepare your USB stick, please?

-- 
Steve McIntyre, Cambridge, UK.                                steve@einval.com
"C++ ate my sanity" -- Jon Rabone

[toc] | [prev] | [next] | [standalone]

#828581

On 14/06/17 00:44, Steve McIntyre wrote:
> On Tue, Jun 13, 2017 at 11:39:46PM +1200, Amos Jeffries wrote:
>> Package: installation-reports
>>
>> On running the installer manually from inside the OEM Windows installed,
>> everything appeared to run smoothly up to the reboot following partition and
>> formatting of the machines drives. On that boot the installer now running off
>> the HDD began looping at the "Install base system" step, no errors or other
>> signs of trouble - just display the progress bar for a few mins, then flick
>> out to the step-by-step listing as if that step was done - but highlighting
>> the same "Install base system" entry every time enter was pressed to start
>> the step.
> Ummm... Question: you say "up to the reboot following partition and
> formatting of the machines drives". debian-installer doesn't reboot
> there. How did you prepare your USB stick, please?
>

It was a vanilla download of the 64-bit netinst ISO burned to the USB stick.

Formatting was the latest step I'm sure worked fine. The default process 
was followed from there until reboot needed, then more default process. 
Everything up to the step "install base system" at least appeared to 
work - until that one did not.

AYJ

[toc] | [prev] | [next] | [standalone]

#828587

On Wed, Jun 14, 2017 at 02:41:32AM +1200, Amos Jeffries wrote:
>On 14/06/17 00:44, Steve McIntyre wrote:
>> On Tue, Jun 13, 2017 at 11:39:46PM +1200, Amos Jeffries wrote:
>> > Package: installation-reports
>>>
>>> On running the installer manually from inside the OEM Windows
>>> installed, everything appeared to run smoothly up to the reboot
>>> following partition and formatting of the machines drives. On that
>>> boot the installer now running off the HDD began looping at the
>>> "Install base system" step, no errors or other signs of trouble -
>>> just display the progress bar for a few mins, then flick out to
>>> the step-by-step listing as if that step was done - but
>>> highlighting the same "Install base system" entry every time enter
>>> was pressed to start the step.
>>
>> Ummm... Question: you say "up to the reboot following partition and
>> formatting of the machines drives". debian-installer doesn't reboot
>> there. How did you prepare your USB stick, please?
>
>It was a vanilla download of the 64-bit netinst ISO burned to the USB stick.

OK. How did you write it, please? dd? cp? Something like unetbootin?

>Formatting was the latest step I'm sure worked fine. The default process was
>followed from there until reboot needed, then more default process.
>Everything up to the step "install base system" at least appeared to work -
>until that one did not.

There isn't a reboot step in the normal path of debian-installer. Oh,
hang on, sorry - I've just seen what I missed earlier in your initial
message: "On running the installer manually from inside the OEM
Windows". Did you use the win32-installer option to start
installation?

-- 
Steve McIntyre, Cambridge, UK.                                steve@einval.com
< sladen> I actually stayed in a hotel and arrived to find a post-it
          note stuck to the mini-bar saying "Paul: This fridge and
          fittings are the correct way around and do not need altering"

[toc] | [prev] | [next] | [standalone]

#828588

On 14/06/17 03:38, Steve McIntyre wrote:
> On Wed, Jun 14, 2017 at 02:41:32AM +1200, Amos Jeffries wrote:
>> On 14/06/17 00:44, Steve McIntyre wrote:
>>> On Tue, Jun 13, 2017 at 11:39:46PM +1200, Amos Jeffries wrote:
>>>> Package: installation-reports
>>>>
>>>> On running the installer manually from inside the OEM Windows
>>>> installed, everything appeared to run smoothly up to the reboot
>>>> following partition and formatting of the machines drives. On that
>>>> boot the installer now running off the HDD began looping at the
>>>> "Install base system" step, no errors or other signs of trouble -
>>>> just display the progress bar for a few mins, then flick out to
>>>> the step-by-step listing as if that step was done - but
>>>> highlighting the same "Install base system" entry every time enter
>>>> was pressed to start the step.
>>> Ummm... Question: you say "up to the reboot following partition and
>>> formatting of the machines drives". debian-installer doesn't reboot
>>> there. How did you prepare your USB stick, please?
>> It was a vanilla download of the 64-bit netinst ISO burned to the USB stick.
> OK. How did you write it, please? dd? cp? Something like unetbootin?

I believe that one was done with the "rufus" tool for Windows.

>> Formatting was the latest step I'm sure worked fine. The default process was
>> followed from there until reboot needed, then more default process.
>> Everything up to the step "install base system" at least appeared to work -
>> until that one did not.
> There isn't a reboot step in the normal path of debian-installer. Oh,
> hang on, sorry - I've just seen what I missed earlier in your initial
> message: "On running the installer manually from inside the OEM
> Windows". Did you use the win32-installer option to start
> installation?
>

I think so, yes.


AYJ

[toc] | [prev] | [standalone]

Back to top | Article view | linux.debian.bugs.dist

csiph-web