installation program requires unmounting itself

Bug #601723 reported by Jeremy Dawson
10
This bug affects 1 person
Affects Status Importance Assigned to Milestone
ubiquity (Ubuntu)
Expired
Undecided
Unassigned

Bug Description

After following the instructions in https://help.ubuntu.com/community/Installation/FromLinux,
(putting the installation stuff into /dev/sdb4), successfully booting into that partition,
going through a significant part of the install program, it then asks that /cdrom be unmounted,
bacause it wants to write to the partition table.

(Note - this install was setup to use existing partitions, so I can't wee why it wanted to write to the partition
table anyway).

But since /dev/sdb4 was mounted at /cdrom, the installation program was running from /cdrom.

Anyway, when I tried to unmount /cdrom, it said Device busy.

This seems crazy - the code that is running wants the partition where it is located to be unmounted.

priya (priyamtk)
affects: ubuntu → setcd (Ubuntu)
Victor Vargas (kamus)
tags: added: needs-reassignment
Revision history for this message
kurt belgrave (trinikrono) wrote :

Thank you for taking the time to report this bug and helping to make Ubuntu better. This bug did not have a package associated with it, which is important for ensuring that it gets looked at by the proper developers. You can learn more about finding the right package at https://wiki.ubuntu.com/Bugs/FindRightPackage . I have classified this bug as a bug ubiquity.

affects: setcd (Ubuntu) → ubiquity (Ubuntu)
Revision history for this message
kurt belgrave (trinikrono) wrote :

Have you gotten anywhere with this jeremy?
Cheers

tags: removed: needs-reassignment
Changed in ubiquity (Ubuntu):
status: New → Incomplete
Revision history for this message
kurt belgrave (trinikrono) wrote :

We'd like to figure out what's causing this bug for you, but we haven't heard back from you in a while. Could you please provide the requested information? Thanks!

Revision history for this message
Jeremy Dawson (jeremy-rsise) wrote :

I replied to the email you sent me in January, as follows:

Dear Kurt,

Thanks for your interest.

No, no response whatever until your email.

And there was a related bug, 601722 - I did get a response to that one, which was roughly that I should have asked a question rather than reported a bug unless I was sure it was a bug - but no hint as to why I might have suspected it wasn't a bug.

Regards,

Jeremy Dawson

Revision history for this message
kurt belgrave (trinikrono) wrote :

Looking at the wikipage where you are trying this from
quote "Note2: Instead of using 'workaround', an alternative is to modify the file /etc/mtab by erasing the line that specifies the partition where the cdrom is mounted. This way the kernel thinks thats the /cdrom is not mounted and will not show the advice when installing ubuntu. I think this procedure is less dangerous than the one in the previus note. "
Can you try this and let me know if you are sucessful.

Revision history for this message
Jeremy Dawson (jeremy-rsise) wrote :

Dear Kurt,

In the intervening 8 months I've managed to install Ubuntu10.04 (on about the dozenth attempt - from a USB, which required deleting the partition /dev/sdb4, see the bug report 610722), and also Fedora13 and Fedora14 (on the first attempt, in each case).

But now that I have Ubuntu10.04 working, I really don't want to try to reinstall it again, in case something doesn't work.

In any case, if you are having trouble reproducing this bug, I'm just as likely to have trouble doing so (ie, I can't remember what I did, beyond what I said in the bug report).

Of course if you have any questions about exact details of what I did, I'll try to remember.

Regards,

Jeremy

PS - doesn't the suggestion that editing /etc/mtab as a workaround confirm the existence of the bug ?

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

[Expired for ubiquity (Ubuntu) because there has been no activity for 60 days.]

Changed in ubiquity (Ubuntu):
status: Incomplete → Expired
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.