[Maverick Beta] install from USB stuck retrieving files 2/6 Hp Mini

Bug #627672 reported by Manoj Iyer
78
This bug affects 12 people
Affects Status Importance Assigned to Milestone
ubiquity (Ubuntu)
Fix Released
High
Unassigned
Maverick
Fix Released
High
Unassigned

Bug Description

Binary package hint: ubiquity

Installing from USB stick on HP Mini, installer is stuck on Retrieving files 2/6 and does not make any progress.

ProblemType: Bug
DistroRelease: Ubuntu 10.10
Package: ubiquity 2.3.10
ProcVersionSignature: Ubuntu 2.6.35-19.28-generic 2.6.35.3
Uname: Linux 2.6.35-19-generic i686
Architecture: i386
Date: Tue Aug 31 16:07:35 2010
LiveMediaBuild: Ubuntu 10.10 "Maverick Meerkat" - Alpha i386 (20100831.1)
ProcEnviron:
 LANGUAGE=
 PATH=(custom, no user)
 LANG=en_US.UTF-8
SourcePackage: ubiquity

Revision history for this message
Manoj Iyer (manjo) wrote :
Revision history for this message
Manoj Iyer (manjo) wrote :

Installer screen shot

Revision history for this message
Manoj Iyer (manjo) wrote :

tar ball of all files in /var/log

Revision history for this message
Colin Watson (cjwatson) wrote :

The syslog shows a succession of:

Aug 31 20:51:27 ubuntu in-target: Media change: please insert the disc labeled
Aug 31 20:51:27 ubuntu in-target: 'Ubuntu 10.10 _Maverick Meerkat_ - Alpha i386 (20100831.1)'
Aug 31 20:51:27 ubuntu in-target: in the drive '/cdrom/' and press enter

Revision history for this message
Manoj Iyer (manjo) wrote :

Evan,

This happend on a netbook, and it does not have a CDROM drive. I download todays (Aug 31) build of daily-live i386 iso.

Revision history for this message
Evan (ev) wrote :

Manoj,

What did you create the USB disk with?

Revision history for this message
John Webster (civil-bigpond) wrote :

I experience the same problem on my Lenovo M9952-RZ4 when attempting to install from a persistent USB stick made with the version of USB startup disk creator included in Kubuntu Maverick as of 20100826 (updated). The problem does not arise when using a LiveCD.

tags: added: iso-testing
Revision history for this message
Mario Limonciello (superm1) wrote :

Someone who can reproduce this, could you by chance launch ubiquity in debug mode? You can do so by adding 'debug-ubiquity' to the kernel command line, or launching it from the standard command line using 'ubiquity -d'. ?

If you can do this and then attach /var/log/syslog and /var/log/installer/debug, that would be quite helpful.

Changed in ubiquity (Ubuntu Maverick):
importance: Undecided → High
Revision history for this message
Manoj Iyer (manjo) wrote :

complete log files with debug-ubiquity kernel boot option.

Revision history for this message
Launchpad Janitor (janitor) wrote :

This bug was fixed in the package ubiquity - 2.3.14

---------------
ubiquity (2.3.14) maverick; urgency=low

  [ Colin Watson ]
  * KDE frontend:
    - If the slideshow doesn't exist, hide self.ui.pageMode rather than
      self.page_mode (LP: #627549).
  * Set Debug::identcdrom=true for apt-cdrom if installing from a
    non-ISO9660 filesystem, since otherwise apt-cdrom will include the free
    blocks count of /cdrom in its database which is unreliable on read-write
    filesystems, especially USB images with persistence enabled. Thanks to
    Manoj Iyer for patient testing (LP: #627672).

  [ Mario Limonciello ]
  * Provides indicator-renderer (LP: #616165)

  [ Evan Dandrea ]
  * Disconnect and destroy QSocketNotifiers when the dbfilter finishes.
    Thanks Colin Watson (LP: #625586).
  * add the check_hostname function back to ubi-usersetup (LP: #628317).
 -- Evan Dandrea <email address hidden> Thu, 02 Sep 2010 01:42:52 +0100

Changed in ubiquity (Ubuntu Maverick):
status: New → Fix Released
Revision history for this message
Colin Watson (cjwatson) wrote :

A workaround for the Ubuntu Desktop CD in Maverick Beta (we didn't have time to respin this particular image, given all the other demands on QA) is to create the USB stick without persistence enabled.

Revision history for this message
richard mullens (richard-mullens) wrote :

How is this done ?
I am using Unetbootin to create a bootable USB stick.

This is surely a disaster for netbook testing !

Revision history for this message
richard mullens (richard-mullens) wrote :

Well, I tried the daily build of 20100904 and wrote the ISO to a USB stick using Unetbootin, but on booting, it would go no further than trying to get the CDROM drivers and eventually I just had to abort. ( I was not trying to install - but rather use it to try before installing).

Revision history for this message
Mark McClary (markmcclary) wrote :

Trying the above work around as soon as the beta is done downloading again. The first USB stick I created I used "Startup Disc Creator" and left the default of 128mb of storage space left for persistence. I will uncheck that this time and report back!

Revision history for this message
Mark McClary (markmcclary) wrote :

I said I would report back! After creating a new start-up disc -- which btw was a fiasco -- without leaving a persistence file the installation sped right through and am now a happy Maverick Beta user!

Revision history for this message
Kenny Strawn (realkstrawn93) wrote :

I had this same problem and was able to work around the bug by clicking "Skip" when the installer was configuring APT (the installer then finished successfully) and then type the following commands on the finished system from a terminal window:

sudo rm -f /var/lib/apt/lists/lock
sudo dpkg --configure -a
sudo apt-get update

Now, it works correctly.

Revision history for this message
Mark McClary (markmcclary) wrote :

Two successful work arounds. I am curious as to why the installer was looking for a cd rom drive on a system that doesnt have one, such as netbooks.

Revision history for this message
richard mullens (richard-mullens) wrote :

I am now up and running with the release candidate. Hurrah !

There is still a problem for users who create their USB boot disk using an older (than Maverick) release with usb-creator - as I did.
On booting from the USB disk one receives the message "Unknown keyword in configuration file".
The problem is described at http://ubuntuforums.org/showthread.php?t=1546737
The solution proposed there - to remove "ui " from the last line of /syslinux/syslinux.cfg - worked for me.

Chris Van Hoof (vanhoof)
Changed in hwe-popular:
status: New → Fix Released
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.