 | nio-wiklund | 2014-09-25 12:29 | | A program tested before ubiquity left cruft in /etc/mtab, which was not seen by df, and not affecting terminal window commands (umount and swapoff), but it was affecting ubiquity. This is a very special case. Running various programs, and checking that /etc/mtab is clean (matching the output of df), makes it possible to install into this same computer with a USB 3 HDD, as well as installing into another computer's internal HDD
http://www.asus.com/Motherboards/M2NVM_DVI/
So we can give bug #1373365 very low priority.
|  |
| nio-wiklund | 2014-09-25 12:29 |
Ubiquity got stuck at 'Identifying file system...' (#1373365)
| In: |
ubiquity (Ubuntu) |
| Status: |
Expired |
| Importance: |
Undecided |
| Assignee: |
|
1 reports, 10 comments, 2 subscribers, 0 duplicates
| Tried again, this time without swap and zRAM, but running some programs before starting Ubiquity and setting up the root partition for re-formatting. The same thing happened as the first time (or very similar). Stuck at 'Identifying file system...'.
I had htop on, and it showed RAM usage approx 300 MB (of a total of 4 GB) so the computer was not running out of memory.
Just after leaving the partitioning screen the system complained that it could not shut off the swap. But I had already done it manually (including zRAM).
It seemed that Ubiquity is happy only when it is allowed to run first (not after other programs have been running).
| |
| nio-wiklund | 2014-09-24 13:56 |
Ubiquity got stuck at 'Identifying file system...' (#1373365)
| In: |
ubiquity (Ubuntu) |
| Status: |
Expired |
| Importance: |
Undecided |
| Assignee: |
|
1 reports, 10 comments, 2 subscribers, 0 duplicates
| Installing from the live session: nasty at the partitioning page: I had complaints, that swap was on, even when it was not on. After re-trying, the installer could continue.
Note: The swap partition is shared with two other linux distros/versions on a USB HDD for experimental installs. But it should work anyway.
Stuck at 'Identifying file system...', Rotating round cursor, but could initiate bug report against Ubiquity.
After writing the bug report, I tried to shut down the installer window. Then it responded with:
'The installation has finished...'. That info window was a little hard to shut down, but finally it went away. And then there was a good (normal) shutdown sequence. But no system was installed.
See separate test report:
[Trying again, this time directly from Syslinux via 'Install Lubuntu', and formatting the (same) partition: it works :-) ]
| |
| nio-wiklund | 2014-09-24 08:34 | | Trying again, this time again from a live session , and using another partition formatted by gparted: This time it created a working Lubuntu Utopic system :-)
So my conclusion so far is that either there are problems installing from the live session when several other programs has been run (testing that the live session works), or that first particular file system made by gparted was bad. The Ubiquity installer has been very sensitive during several versions, and installation should be done at once, not after running several other programs, particularly with low RAM.
With 4 GB RAM (in this test), there should not be a problem with too low RAM, but maybe zRAM was crowded and caused problems (zRAM is used in Lubuntu's live session).
| |
| nio-wiklund | 2014-09-24 07:31 | | Trying again, this time directly from Syslinux via 'Install Lubuntu', and formatting the (same) partition: It reached 'Restart' seeming to work well, but it ended at a black screen and I had to press the Enter key to make it restart. Not only was something installed, it was a working Lubuntu Utopic system :-)
So my conclusion so far is that either there are problems installing from the live session, or the installer was not happy with the file system made by gparted.
| |
