Ubiquity: device or resource busy error message

Bug #334341 reported by Colin Ian King
4
Affects Status Importance Assigned to Milestone
ubiquity (Ubuntu)
Confirmed
High
Unassigned
Nominated for Jaunty by Charlie Kravetz

Bug Description

Testing ISO http://cdimage.ubuntu.com/daily-live/20090225/jaunty-desktop-amd64.iso

Test: http://testcases.qa.ubuntu.com/Install/DesktopWhole, Ubiquity Whole Install, Case ID: uwi-001

(note: Installation was after testing previous installations of OEM and Desktop (resize))

Ubiquity reported the following error message:

"Error informing the kernel about modifications to partition /dev
sda1 - Device or resource busy. This means Linux won't know
about any changes you made to /dev/sda1 until you reboot -
so you shouldn't mount it or use it in any way before rebooting."

And following this, during the creation of the ext3 file system I got the error message:

"The ext3 file system creation in partition #1
 of SCSI1 (0,0,0) (sda) failed."

An immediate retry of the install process worked successfully.

Attached: png screen shots of the error message and dmesg output for reference.

Revision history for this message
Colin Ian King (colin-king) wrote :
Revision history for this message
Colin Ian King (colin-king) wrote :
Revision history for this message
Colin Ian King (colin-king) wrote :
Revision history for this message
Colin Ian King (colin-king) wrote :

Just to add:

Hardware: Dell Inspiron 6400 Laptop, AMD64.

Revision history for this message
Colin Ian King (colin-king) wrote :

As requested: /var/log/partman and /var/log/syslog

Revision history for this message
Colin Ian King (colin-king) wrote :
Revision history for this message
Mario Limonciello (superm1) wrote :

Marking confirmed. I'm seeing the same thing with mythbuntu a5 candidate disk. Clearing the partitions out before the installer starts resolves it.

Changed in ubiquity:
status: New → Confirmed
Revision history for this message
Mario Limonciello (superm1) wrote :
Revision history for this message
Charlie Kravetz (cjkgeek) wrote :

Also affected by this bug. Unfortunatley, I was unable to complete the installation by starting it over. Instead, I got the messages again, then followed up with "out of space". Attaching the install log and syslog.

Changed in ubiquity:
importance: Undecided → High
Revision history for this message
Charlie Kravetz (cjkgeek) wrote :
Revision history for this message
Charlie Kravetz (cjkgeek) wrote :
Revision history for this message
Charlie Kravetz (cjkgeek) wrote :

RELEASE: Jaunty
CD/DVD VARIANT: 32bit Xubuntu Desktop cd
ISO BUILD: 20080225.3

Revision history for this message
Charlie Kravetz (cjkgeek) wrote :

My mistake.
ISO BUILD: 20090225.1

Revision history for this message
Steven Harms (sharms) wrote :

I can reproduce this on 2 systems (only 2 I tried) with the AMD64 a5 cd

Revision history for this message
Ronald McCollam (fader) wrote :

This is pretty consistently reproducible on some of the hardware certification servers if you need any logs or testing done.

Revision history for this message
Charlie Kravetz (cjkgeek) wrote :

I have been working directly with the developers on this, and even when it seems the same to us users, apparently, it is not always the same. It is better to file a new bug and include your logs for the developers to see and decide if it is a duplicate.

In the meantime, please try the daily images and see if this is fixed already for you. It has been fixed using the images from 2009-03-11 for me.

daily images are available here:
Desktop cd -
http://cdimages.ubuntu.com/daily-live/current/
Alternate cd -
http://cdimages.ubuntu.com/daily/current/

Thanks in advance

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

After some thought, I think that this is in fact the same as bug 340188 so I'm going to mark it as a duplicate. Colin, if this recurs for you, feel free to unduplicate it and let me know; anyone else, if it recurs for you with Alpha 6 or newer, please open a new bug and poke me about it on IRC.

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.