unmount problem with Unetbootin

Bug #274389 reported by fabb
14
This bug affects 1 person
Affects Status Importance Assigned to Milestone
Linux Mint
Incomplete
Undecided
Unassigned
ubiquity (Ubuntu)
Expired
Undecided
Unassigned

Bug Description

edit: this actually consists of two problems. the first one is old, the second breaks Unetbootin support /

I'm on Intrepid Alpha 6 here. booting from the live cd via Unetbootin works fine, but the first ntfs partition on sda1 is recognized and mounted in /CDROM. i can access it though, but that is not the problem.
edit: this also happend with 8.04. /

when i start the ubuntu installer, at the last step it shouts that it can't unmount /CDROM, whyever this is needed. but i can't unmount /CDROM, as the ubuntu livecd is booted from there via Unetbootin.
edit: this did NOT happen in 8.04. /

my harddrive has got 3 partitions: first is ntfs, second linux swap and third ext3. in the setup i did not change the partition table, just tell the installer to use the last partition as root. (un)checking the format checkbox doesn't make a difference.

Revision history for this message
Patrick Kilgore (patrick-kilgore) wrote :

Thanks for your bug report. I'm classifing this as fuse, but if a fuse developer thinks I'm off base please correct this.

Revision history for this message
fabb (milkservice) wrote : Re: Intrepid installer unmount problem with Unetbootin

ps: i wanted to add it to the intrepid installer package, but i don't know which this is.

description: updated
Revision history for this message
fabb (milkservice) wrote :

the first problem, that the unetbootin partition (in my case the first ntfs partition) is recognized as cdrom, has got further impact:
after installing, the ntfs partition will be inserted as cdrom into /etc/fstab and NO MORE BE ACESSIBLE as the filesystem now isn't recognized automatically any more.

the line in fstab will be as for every other cdrom device:
/dev/sda1 /media/cdrom0 udf,iso9660 user,noauto,exec,utf8 0 0

Revision history for this message
fabb (milkservice) wrote :

It also happens with the new Linux Mint 6 (final). In the installer, NO partitions are displayed at all.

Revision history for this message
emorrp1 (emorrp1) wrote : Re: [ubiquity] unmount problem with Unetbootin

Which version of unetbootin? Is this still a problem in Gloria?

summary: - Intrepid installer unmount problem with Unetbootin
+ [ubiquity] unmount problem with Unetbootin
Changed in linuxmint:
status: New → Incomplete
tags: added: ubiquity
removed: installer intrepid
emorrp1 (emorrp1)
tags: removed: fuse ubiquity unetbootin
emorrp1 (emorrp1)
Changed in fuse (Ubuntu):
status: New → Incomplete
summary: - [ubiquity] unmount problem with Unetbootin
+ unmount problem with Unetbootin
tags: added: ubiquity
emorrp1 (emorrp1)
tags: removed: ubiquity
Revision history for this message
Tom Jaeger (thjaeger) wrote :

This is clearly a bug in ubiquity: It thinks it needs to re-read the partition table but won't be able to do so because a partition is mounted on that disk and then aborts the installation. But in fact, the partition table doesn't change at all, so it could just continue.

Revision history for this message
emorrp1 (emorrp1) wrote :

on advice from Tom Jaeger

Changed in fuse (Ubuntu):
status: Incomplete → Invalid
affects: fuse (Ubuntu) → ubiquity (Ubuntu)
Changed in ubiquity (Ubuntu):
status: Invalid → Incomplete
Revision history for this message
Tom Jaeger (thjaeger) wrote :

I should have said 'also'. There's still something funny going with the /cdrom partition that can't be unmounted despite fuser/lsof not reporting any open files, but fuse was the wrong package anyway.

Revision history for this message
emorrp1 (emorrp1) wrote :

ahh well, ubiquity team will have a better way of knowing exactly what's causing it.

Revision history for this message
Niels Peen (niels-peen) wrote :

As a work-around (a dirty one), after you finish partitioning, remove the /cdrom line from /etc/mtab before you click Next.

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.