unmount_busy prompt not working properly

[Elias Amaral]

Binary package hint: ubiquity

I am using feisty beta (Hmmm, the one downloadable here: http://www.ubuntu.com/news/Ubuntu704Beta). My partition table:

$ sudo fdisk -l

Disk /dev/sda: 80.0 GB, 80060424192 bytes
255 heads, 63 sectors/track, 9733 cylinders
Units = cylinders of 16065 * 512 = 8225280 bytes

   Device Boot Start End Blocks Id System
/dev/sda1 1 1094 8787523+ b W95 FAT32
/dev/sda3 1095 6272 41592285 5 Extended
/dev/sda5 1095 1290 1574338+ 82 Linux swap / Solaris
/dev/sda6 1291 1486 1574338+ 83 Linux
/dev/sda7 1487 2443 7687071 83 Linux
/dev/sda8 2444 2990 4393746 83 Linux
/dev/sda9 2991 3537 4393746 83 Linux
/dev/sda10 3538 4084 4393746 83 Linux
/dev/sda11 4085 4631 4393746 83 Linux
/dev/sda12 4632 5178 4393746 83 Linux
/dev/sda13 5179 5725 4393746 83 Linux
/dev/sda14 5726 6272 4393746 83 Linux

Disk /dev/sdb: 80.0 GB, 80026361856 bytes
255 heads, 63 sectors/track, 9729 cylinders
Units = cylinders of 16065 * 512 = 8225280 bytes

   Device Boot Start End Blocks Id System
/dev/sdb1 1 1245 10000431 83 Linux
/dev/sdb2 1246 3735 20000925 83 Linux
/dev/sdb3 3736 9729 48146805 5 Extended
/dev/sdb5 3736 8964 42001911 83 Linux
/dev/sdb6 8965 9523 4490136 83 Linux
/dev/sdb7 9524 9729 1654663+ 82 Linux swap / Solaris

I configured the partitioning manually and assigned /dev/sdb6 to / (formating) and /dev/sdb2 to /home. I mounted partitions while looking for fstab, through nautilus and forgot to umount /dev/sdb2. (Actually nautilus didn't mention I could umount, but I was umounting my partitions anyway). When the system was just about to install (After pressing continue at step 7 of 7), ubiquity said: "/media/_home is mounted and busy" (I was with a doc open). And I closed the doc and umounted it, and then I pressed "continue" (It was saying: "ubiquity will try to umount"..). Then the installer just quits. No error message, etc. Maybe it was trying to umount a partition that is already umounted, I don't know.

I was not very happy with this because now the manual partitioning is just slow (It re-reads the HD after every UI change..), I wonder why the partition manager changed, but there must be a good reason :).

PS: Error messages are actually inacurate because a) I was installing in portuguese and b) I already closed the installer.. (it is installing now -- I just kept all partitions umounted when confirming the installation)

[Colin Watson (cjwatson)]

Could you please attach /var/log/syslog and /var/log/partman to this bug, following the directions in http://wiki.ubuntu.com/DebuggingUbiquity/AttachingLogs? Thanks in advance. If you've rebooted since the crash, you'll need to reproduce it in order to retrieve useful versions of these files.

[Elias Amaral (dlight)]

Hmm, sorry for the delay. These two files was generated like you said. I tried to install in the /dev/sda1 partition (after some unsucessful attempts.. I hope this don't compromise the logs). I tried to reproduce the bug in the "import configurations" but I couldn't. So I mounted /dev/sda1, then when Installing, I umounted after the error message, then it crashed.

I don't know if it would be useful, but I am pasting the last lines of output of ubiquity too:

Apr 18 21:59:34 ubiquity: Partman: state = [['', None, None]]
Apr 18 21:59:34 ubiquity: Starting up '['log-output', '-t', 'ubiquity', '--pass-stdout', '/usr/lib/ubiquity/migration-assistant/ma-ask', '/usr/lib/ubiquity/migration-assistant']' for ubiquity.components.migrationassistant.MigrationAssistant
Apr 18 21:59:34 ubiquity: Watching for question patterns ^migration-assistant/partitions, ^migration-assistant/.*/users$, ^migration-assistant/.*/items$, ^migration-assistant/.*/user$, ^migration-assistant/.*/password$, ^migration-assistant/failed-unmount, ERROR
Apr 18 22:00:09 ubiquity: Starting up '['log-output', '-t', 'ubiquity', '--pass-stdout', '/usr/lib/ubiquity/migration-assistant/ma-ask', '/usr/lib/ubiquity/migration-assistant']' for ubiquity.components.migrationassistant.MigrationAssistant
Apr 18 22:00:09 ubiquity: Watching for question patterns ^migration-assistant/partitions, ^migration-assistant/.*/users$, ^migration-assistant/.*/items$, ^migration-assistant/.*/user$, ^migration-assistant/.*/password$, ^migration-assistant/failed-unmount, ERROR
Apr 18 22:00:23 ubiquity: Starting up '['log-output', '-t', 'ubiquity', '--pass-stdout', '/usr/lib/ubiquity/user-setup/user-setup-ask', '/target']' for ubiquity.components.usersetup.UserSetup
Apr 18 22:00:23 ubiquity: Watching for question patterns ^passwd/user-fullname$, ^passwd/username$, ^passwd/user-password$, ^passwd/user-password-again$, ERROR
Apr 18 22:00:54 ubiquity: Starting up '['log-output', '-t', 'ubiquity', '--pass-stdout', '/usr/share/ubiquity/summary']' for ubiquity.components.summary.Summary
Apr 18 22:00:54 ubiquity: Watching for question patterns ^partman/confirm.*, type:boolean, ERROR, PROGRESS, ^ubiquity/summary.*
Apr 18 22:01:19 ubiquity: Starting up '['log-output', '-t', 'ubiquity', '--pass-stdout', '/bin/partman-commit']' for ubiquity.components.partman_commit.PartmanCommit
Apr 18 22:01:19 ubiquity: Watching for question patterns ^partman/confirm.*, type:boolean, ERROR, PROGRESS
Apr 18 22:01:47 ubiquity: ['log-output', '-t', 'ubiquity', '--pass-stdout', '/bin/partman-commit'] exited with code 1

[Henrik Nilsen Omma (henrik)]

Thanks for providing logs. Confirming.

[Duncan Lithgow (duncan-lithgow)]

... and what happens with the Stable release of Feisty?

[Nanley Chery (nanoman)]

This bug has been marked as incomplete for 4 weeks now. I think we should mark this as invalid.

[Elias Amaral (dlight)]

2007/9/18, Nanley Chery <email address hidden>:
> This bug has been marked as incomplete for 4 weeks now. I think we
> should mark this as invalid.
>
> --
> [Feisty] Crash when preparing to install with busy mounted partitions
> https://bugs.launchpad.net/bugs/105104
> You received this bug notification because you are a direct subscriber
> of the bug.

Well. I am busy now, but I will try it with the most recent feisty
release today or tomorrow (when I have time). It seemed a real bug
when happened, but it was with a beta release. It may affect gutsy
tribe (I didn't checked).

--
Elias Gabriel Amaral da Silva <email address hidden>

[Nanley Chery (nanoman)]

Excellent. I will be awaiting your response. ;-)

[Elias Amaral (dlight)]

2007/9/20, Nanley Chery <email address hidden>:
> Excellent. I will be awaiting your response. ;-)

Sorry to keep you waiting so much. I tried to reproduce it now and,
after the program said that the partition can't be umounted, I
umounted the partition, clicked in continue and now it justs goes back
to the beginning of partitioner. It is the same behavior as if I just
clicked "Back". (Actually the "back" and "continue" buttons seems to
be doing _exactly_ the same thing, because they goes back in any
situation). Maybe it's the wrong behavior, but the crashing bug seems
fixed now.

Just as a note, it can umount normally the mounted partition if the
partition isn't busy, and continue normally the installation.

--
Elias Gabriel Amaral da Silva <email address hidden>

[Nanley Chery (nanoman)]

Correct me if I'm wrong, but I don't think ubiquity is designed to install on a busy mounted partition. It is probably supposed to install to a partition that isn't in use. Either that or I might just be spewing out mounds of uninformed garbage. What's your say on this Watson?

[Elias Amaral (dlight)]

2007/10/7, Nanley Chery <email address hidden>:
> Correct me if I'm wrong, but I don't think ubiquity is designed to
> install on a busy mounted partition. It is probably supposed to install
> to a partition that isn't in use.

you are right. because of this, it must wait the partition be
unmounted before installing.

what it does after this was the subject of the thread.

--
Elias Gabriel Amaral da Silva <email address hidden>

[Colin Watson (cjwatson)]

Nanley: please don't call me "Watson". You aren't my schoolteacher and it's rather rude otherwise.

The intention is as Elias described: when attempting to install to a mounted partition, ubiquity is supposed to attempt to unmount it and prompt if that doesn't work. If the mechanics of that prompt aren't working correctly, then that's a clear bug. In any case people should stop marking this bug as Incomplete, as it really isn't.

[Brian Murray (brian-murray)]

Exception during installation:
Apr 18 21:52:38 ubuntu python: Traceback (most recent call last):
Apr 18 21:52:38 ubuntu python: File "/usr/share/ubiquity/install.py", line 1523, in <module>
Apr 18 21:52:38 ubuntu python: install.run()
Apr 18 21:52:38 ubuntu python: File "/usr/share/ubiquity/install.py", line 307, in run
Apr 18 21:52:38 ubuntu python: self.copy_all()
Apr 18 21:52:38 ubuntu python: File "/usr/share/ubiquity/install.py", line 504, in copy_all
Apr 18 21:52:38 ubuntu python: self.db.progress('SET', 10 + copy_progress)
Apr 18 21:52:38 ubuntu python: File "/usr/lib/python2.5/site-packages/debconf.py", line 60, in <lambda>
Apr 18 21:52:38 ubuntu python: lambda *args, **kw: self.command(command, *args, **kw))
Apr 18 21:52:38 ubuntu python: File "/usr/lib/python2.5/site-packages/debconf.py", line 65, in command
Apr 18 21:52:38 ubuntu python: self.write.flush()
Apr 18 21:52:38 ubuntu python: IOError: [Errno 32] Broken pipe
Apr 18 21:52:38 ubuntu python:

[Elias Amaral (dlight)]

is this a new bug? (also, shouldn't you try installing a newer ubuntu version?)

2011/8/3 Brian Murray <email address hidden>:
> Exception during installation:
> Apr 18 21:52:38 ubuntu python: Traceback (most recent call last):
> Apr 18 21:52:38 ubuntu python:   File "/usr/share/ubiquity/install.py", line 1523, in <module>
> Apr 18 21:52:38 ubuntu python:     install.run()
> Apr 18 21:52:38 ubuntu python:   File "/usr/share/ubiquity/install.py", line 307, in run
> Apr 18 21:52:38 ubuntu python:     self.copy_all()
> Apr 18 21:52:38 ubuntu python:   File "/usr/share/ubiquity/install.py", line 504, in copy_all
> Apr 18 21:52:38 ubuntu python:     self.db.progress('SET', 10 + copy_progress)
> Apr 18 21:52:38 ubuntu python:   File "/usr/lib/python2.5/site-packages/debconf.py", line 60, in <lambda>
> Apr 18 21:52:38 ubuntu python:     lambda *args, **kw: self.command(command, *args, **kw))
> Apr 18 21:52:38 ubuntu python:   File "/usr/lib/python2.5/site-packages/debconf.py", line 65, in command
> Apr 18 21:52:38 ubuntu python:     self.write.flush()
> Apr 18 21:52:38 ubuntu python: IOError: [Errno 32] Broken pipe
> Apr 18 21:52:38 ubuntu python:
>
>
> ** Tags added: installer-crash
>
> --
> You received this bug notification because you are subscribed to the bug
> report.
> https://bugs.launchpad.net/bugs/105104
>
> Title:
>  unmount_busy prompt not working properly
>
> To manage notifications about this bug go to:
> https://bugs.launchpad.net/ubuntu/+source/ubiquity/+bug/105104/+subscriptions
>

[Marcus Tomlinson (marcustomlinson)]

This release of Ubuntu is no longer receiving maintenance updates. If this is still an issue on a maintained version of Ubuntu please let us know.

[Launchpad Janitor (janitor)]

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