6.10 amd64 installer hangs

Bug #90292 reported by lpd on 2007-03-07
2
Affects Status Importance Assigned to Milestone
ubiquity (Ubuntu)
Undecided
Unassigned

Bug Description

Trying to install 6.10 from CD on an amd64 system hangs very early in the process. The word "ubuntu" is on the screen, with a little gray rectangle below it shuttling back and forth from right to left. I tried "noapic nolapic" with no success. By "hangs" I mean stays in this state for many minutes with no indication of any kind of progress.

This is not a system-specific problem: exactly the same thing happened on two completely different hardware configs (one desktop, one laptop).

Brian Murray (brian-murray) wrote :

Thanks for taking the time to report this bug and helping to make Ubuntu better. Have you confirmed that the burned CD is in fact good? There is an easy way to verify the integrity of the Ubuntu ISO files you download. For more information, please visit https://help.ubuntu.com/community/HowToMD5SUM . Thanks in advance.

I just now verified that the md5sum of the file ubuntu-6.10-desktop-amd64.iso from which I made the CD matches the md5sum at the above link. However, when I ran "md5sum -c md5sum.txt | grep -v 'OK$'" on the CD, it reported:

error processing ./casper/filesystem.squashfs: failed in buffer_read(fd): mdfile: Input/output error
md5sum: MD5 check failed for './casper/filesystem.squashfs'

I will re-burn the CD, try the install again, and report the outcome. I've never had a CD burning problem before, so it never occurred to me to check for errors. Thanks for the tip!

I burned a new CD and verified its md5sum.

The installer now fails in the same place as the 6.06 installer (see my bug report # 90293), but in a different way. I configured the mount points this way:

/ - hda1
swap - hda5 (autodetected)
/tmp - hda6
/usr - hda7
/var - hda8
/home - hda9

When I clicked "Forward", I got a notifier that said "No root filesystem", and I couldn't proceed past that point. I double-checked that I had selected "/" for hda1, and I even tried typing it in rather than selecting it from the list. No luck. I tried checking the "reformat" box for that partition: that didn't help either.

Now what?

Brian Murray (brian-murray) wrote :

If this is not the same bug as 90293 then the same log files you included there would be useful here too. Thanks in advance.

This does not appear to be the same bug as 90292.

In 6.10, /var/log/installer/syslog does not exist. I'm attaching /var/log/syslog and /var/log/partman here.

lpd (lpd-major2nd) wrote :

Sorry, I meant "this does not appear to be the same bug as 90293." 90293 is a crash, 90292 is a notifier.

Colin Watson (cjwatson) wrote :

Thanks for your report. This is also bug 67130; to work around it, boot the live CD and upgrade the ubiquity package on the fly to version 1.2.6 from the edgy-proposed repository before starting the installer.

lpd (lpd-major2nd) wrote :

I am not sure this is the same as bug 67130, which seems to be about reiserfs. However, this bug does appear to be a duplicate of 67264. I will try the workaround and report back.

lpd (lpd-major2nd) wrote :

Sorry, I don't understand how to execute the proposed workaround. I brought up the Synaptic GUI, but even after I clicked "Reload package data", it said that the current version of ubiquity was 1.2.5. How do I tell it to fetch the package from "the edgy-proposed repository"?

You have to add edgy-proposed repository to /etc/apt/sources.list and issue
sudo apt-get update and then install the package. Hope that helps.

2007/3/14, lpd <email address hidden>:
>
> *** This bug is a duplicate of bug 67130 ***
>
> Sorry, I don't understand how to execute the proposed workaround. I
> brought up the Synaptic GUI, but even after I clicked "Reload package
> data", it said that the current version of ubiquity was 1.2.5. How do I
> tell it to fetch the package from "the edgy-proposed repository"?
>
> --
> 6.10 amd64 installer hangs
> https://launchpad.net/bugs/90292
>

lpd (lpd-major2nd) wrote :

Thank you. I followed your suggestion and it worked: the install completed OK. This bug can be marked closed now.

To post a comment you must log in.
This report contains Public information  Edit
Everyone can see this information.

Other bug subscribers