Just happened (somewhat late in the process) with Ubuntu GNOME 20150318
i386. Can't just quit the installation at that point, must just restart
live DVD, then format with Gparted, and then install.
** Attachment added: Screenshot from 2015-03-19 09_16_41.png
I had the same issue. It was clean installation as replacement of
windows 7 on Lenovo T440s. First instalation cycle was ok but there was
something bad with parttiions, I thought it was because I wanted to keep
untouched partition for Intel Rapid Start Technology and recreated only
some partitions
Hi,
I had the same issue when I tried to install Kubuntu 14.10 over the old
14.04 installation. The workaround I found ist quite simple. I chose not
the default file system (ext4) but btrfs for the root partition and
the installation succeeded without any further issues. I guess, the
issue is
** Attachment added: syslog
https://bugs.launchpad.net/ubuntu/+source/ubiquity/+bug/1361951/+attachment/4250832/+files/syslog
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1361951
Title:
Utopic
This is it for now, but since I used a live USB instead of a DVD any
addirtional logs needed should hopefully be saved.
** Attachment added: version
https://bugs.launchpad.net/ubuntu/+source/ubiquity/+bug/1361951/+attachment/4250836/+files/version
--
You received this bug notification
** Attachment added: debug
https://bugs.launchpad.net/ubuntu/+source/ubiquity/+bug/1361951/+attachment/4250834/+files/debug
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1361951
Title:
Utopic
OK, finally got to this. I saved ps aux to white.text and I'll attach
that as well as other applicable logs. I'll try to read them more
closely when I'm in a more comfortable environment for my tired old
eyes. You should probably know that the live USB booted directly to the
install dialog after
** Attachment added: dm
https://bugs.launchpad.net/ubuntu/+source/ubiquity/+bug/1361951/+attachment/4250835/+files/dm
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1361951
Title:
Utopic
** Attachment added: partman
https://bugs.launchpad.net/ubuntu/+source/ubiquity/+bug/1361951/+attachment/4250833/+files/partman
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1361951
Title:
Looks like mkfs is still running:
root 22613 0.0 0.1 5088 2460 ?S15:48 0:00
mkfs.ext4 /dev/sda10
Or at least it's still consuming memory.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
I noticed this in the syslog:
Nov 1 15:48:08 ubuntu partman: mke2fs 1.42.10 (18-May-2014)
Nov 1 15:48:08 ubuntu partman: Found a dos partition table in /dev/sda10
It seems you have something that looks like a dos partition table in
/dev/sda10. I'm guessing that mke2fs is printing that warning
I'm curious where to add those two additional lines in
/etc/rsyslog.conf??? This is what it looks like out_of_box:
# /etc/rsyslog.confConfiguration file for rsyslog.
#
# For more information see
# /usr/share/doc/rsyslog-doc/html/rsyslog_conf.html
#
Lance,
it really doesnt matter where you add them, anywhere is fine.
`ps -aux` will be fine, though the '-' is somewhat redundant if you are
going to be typing it a lot. `ps aux` should do
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to
Neither ps or top really show anything of interest, see screenshot. But
top does show ubiquity itself is running. I'll also attach logs from
that attempt.
** Attachment added: Screenshot from 2014-10-29 20_02_45.png
And var/log/installer/debug
** Attachment added: debug
https://bugs.launchpad.net/ubuntu/+source/ubiquity/+bug/1361951/+attachment/4248501/+files/debug
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
And /version
** Attachment added: version
https://bugs.launchpad.net/ubuntu/+source/ubiquity/+bug/1361951/+attachment/4248504/+files/version
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1361951
Here's the partman log from that last attempt which was BTW done with
Ubuntu Utopic i386 final.
** Attachment added: partman
https://bugs.launchpad.net/ubuntu/+source/ubiquity/+bug/1361951/+attachment/4248500/+files/partman
--
You received this bug notification because you are a member of
And /installer/dm
** Attachment added: dm
https://bugs.launchpad.net/ubuntu/+source/ubiquity/+bug/1361951/+attachment/4248502/+files/dm
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1361951
Just thinking out loud :^)
I seem to recall some time ago being able to collect more detailed info
if I started the live DVD with a boot parameter like ubiquity-maybe
but I didn't keep notes and I'm unsure what the actual boot parameter is
- would something like that help at all?
--
You
On 30/10/14 07:44, Erick Brunzell wrote:
Just thinking out loud :^)
I seem to recall some time ago being able to collect more detailed info
if I started the live DVD with a boot parameter like ubiquity-maybe
but I didn't keep notes and I'm unsure what the actual boot parameter is
- would
It sounds like the mkfs works then and ubiquity freezes after for some
reason. You might just double check with a full ps since it likely
won't show up in top if it is hung.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
Is it only the installer that freezes or the whole system? Can you go
to a command prompt and check with ps if mkfs or mke2fs are still
running?
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1361951
Only ubiquity appears to freeze so I should be able to try that. Don't
hold your breath though because it's not consistently reproducible.
Sometimes it works as expected and other times it freezes using the same
exact partitions, same process, etc. It should prove to be a real
challenge :^(
--
Status changed to 'Confirmed' because the bug affects multiple users.
** Changed in: ubiquity (Ubuntu)
Status: New = Confirmed
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1361951
Title:
I could not produce this bug:
https://bugs.launchpad.net/ubuntu/+source/ubiquity/+bug/1361951
In my case, everything was just fine. However, I must say that in my
case, there is only one Hard Drive, not 2 Hard Drives as in the bug
report:
According to comment #9 one other person has encountered this, but it's
not easily or consistently reproducible.
So far I've only been able to reproduce it if 3 criteria are met:
(1) The partition selected for change must contain a previously installed OS.
(2) The selected partition must be a
When I tried to re-produce this bug, I had a previously installed Ubuntu
GNOME Utopic Unicorn RC and when I tried to do the manual installation,
I removed/deleted the old partitions and created new ones. Then,
installed and everything was just fine.
It seems this is a hard to re-produce bug and I
With the 20141016 image the freeze appears to happen later in the
process - actually just a graphical thing I think - see attached
screenshot. So in order to quit the install and format the partition
with Gparted instead of being able to click on Quit I just logged out
and then logged back in. The
Hi, have had this same issue with the install procedure for 14.10 64-bit
desktop (daily build 9 Oct 2014) freezing while reformating.
Followed the work around above (ie. reformating via gparted) and the
install procedure has continued.
--
You received this bug notification because you are a
I have not found a reliable way to reproduce this - sometimes the
reformatting proceeds as expected and sometimes it just never seems to
proceed beyond displaying Creating ext4 filesystem for / in partition
#1 of SCSI2 (0,0,0) (sda) I did poke around a bit after
the most recent freeze
Oddly I tried once last night and then once more this AM to reproduce
this using the same DVD, same hardware, same installation steps, etc and
couldn't reproduce so for now I suppose we can only wait and see if
anyone has the same issue.
--
You received this bug notification because you are a
I just tested this in a VM and manual partioning worked just fine.
Lance, can you post the ubiquity logs up?
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1361951
Title:
Utopic installation
I assume the attached logs are incomplete?
I filed the bug report using ubuntu-bug ubiquity while the installer
still appeared to be trying to create the / partition. I could not find
a way to kill the process before filing the bug report.
I've since wiped that failed install but I'll reproduce
Here also is a screenshot of my chosen partitioning prior to beginning
the install.
** Attachment added: Screenshot from 2014-08-27 02:57:37.png
https://bugs.launchpad.net/ubuntu/+source/ubiquity/+bug/1361951/+attachment/4187965/+files/Screenshot%20from%202014-08-27%2002%3A57%3A37.png
--
This is what Gparted shows had been done after a reboot.
BTW I just reformatted that partition to ext4 and ran a check via
Gparted which showed the partition being OK, and smart status via GNOME
Disk Utility shows the drive being OK.
** Attachment added: Screenshot from 2014-08-26 22:53:49.png
This bug has been reported on the Ubuntu ISO testing tracker.
A list of all reports related to this bug can be found here:
http://iso.qa.ubuntu.com/qatracker/reports/bugs/1361951
** Tags added: iso-testing
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is
Installation completes successfully if partitions are created prior to
performing the installation, so I think it would be reasonable to set a
milestone for Beta 2 or even Final as long as we mention this in the
release notes.
--
You received this bug notification because you are a member of
37 matches
Mail list logo
