install crashed w/ 75% files copied: disk full

Bug #91962 reported by mmr160
10
This bug affects 1 person
Affects Status Importance Assigned to Milestone
ubiquity (Ubuntu)
Invalid
Undecided
Colin Watson

Bug Description

Binary package hint: ubiquity

During install from disk v. 6.10 to Drive F:/ (empty w/ 20GB size), first effort stalled during "set time." No effort to "continue," "back," or other mouse clicking changed anything. So, I shut down and turned computer off.
   Second try at install succeeded when "set time" was by-passed. Every step proceded as expected until installer was copying files. At about 75% complete, the installer crashed. On screen report said to "attach files" </var/log/syslog> and </var/log/partman>
   However, I can't access Drive F:/ from active Drive C:/Windows EX Pro, or from "Set Up" of BIOS. But I notice that the disk capacity on F:/properties reads: "Used 107MB, Free 14.8GB."
   Since unbuntu community support and documentation indicates that a partition of at least 10GB is necessary for installation, I am at a loss right now and will appreciate your counsel.

Revision history for this message
mmr160 (hclym6ky) wrote :

Re: Bug # 91962:
     Attempted installation program again. Skipped the "set time" again; instructed UBUNTU to delete everything on Drive F:/ (slave) and continue. The program performed admirably from that point on. The installation is now complete. After I take a break for a cuppa, I'll try the rest of the tweaking, such as font size and style, setting the clock, and other exploration.
     Wanted you to know that the bug reported has been circumvented, even without knowing why it occurred.
     Thanks for your attention.

Revision history for this message
Colin Watson (cjwatson) wrote :

You need to attach the log files to a bug report *before* rebooting - they're only stored in memory and will be erased as soon as you reboot. http://wiki.ubuntu.com/DebuggingUbiquity/AttachingLogs has advice. I don't suppose you'll be able to reproduce this again?

Bear with me for this slightly strange question, but how much RAM do you have? It's possible that the installer didn't notice a failure to mount the target filesystem and was actually uselessly "installing" into its own ramdisk ...

Changed in ubiquity:
assignee: nobody → kamion
status: Unconfirmed → Needs Info
Revision history for this message
mmr160 (hclym6ky) wrote :

Thanks for additional advice. I'll print that and keep. Ubuntu is now in and appears fine. Your help is greatly appreciated.
   Case "Solved."

Revision history for this message
Jean-Baptiste Lallement (jibel) wrote :

I'm closing this report due to your last comment.

Thank you again for taking the time to report this bug and helping to make Ubuntu better. Feel free to submit any future bugs you may find.

Changed in ubiquity:
status: Incomplete → Invalid
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.