Installer fails if windows on another partition is hibernated

Bug #156477 reported by Pnettleship on 2007-10-23
8
This bug affects 1 person
Affects Status Importance Assigned to Milestone
debian-installer (Ubuntu)
Undecided
Unassigned

Bug Description

I have an Dell Inspiron 1420. I have Windows Vista on my first partition (sda1). I am installing Gutsy on sda2 as / and sda5 as swap. I hibernate vista and go to install gutsy by booting from the cd.

I choose the manual install option. I create a ext3 partition and a swap partition in my spare space on the drive. The NTFS drive is auto-detected and I choose it to be mounted on /windows. I go next next next, fill in all the normal details, and click the install button. The 'preview' of what partitions will be effected does NOT include my windows partition.

It then formats the ext3 partition, puts 800 some odd mb's of files on it, but fails to mount the windows partition.

It gives no reasons why. It then asks me if I want to go back to the partitioner or continue.

This is one part of the bug report, for the message says I can 'Go Back' to the partitioner, or I can 'Continue'. However hitting EITHER button brings me back to the partitioner. Continue does NOT ignore the error and continue the install.

The second part of the issue is that if I abandon the install and restart, its all ready ruined my MBR preventing me from booting Vista and shutting it down properly instead of hibernating.

The installer should check if it can mount the drives which will not be formatted BEFORE formatting and installing its own MBR.

 Thank you for taking the time to report this bug and helping to make Ubuntu better. You reported this bug a while ago and there hasn't been any activity in it recently. We were wondering if this is still an issue for you. Can you try with the latest Ubuntu release? Thanks in advance.

Changed in debian-installer:
status: New → Incomplete

Thank you for taking the time to report this bug and helping to make Ubuntu better. The version of Ubuntu your using is in End of Life status. More information may be found at: https://wiki.ubuntu.com/Releases As well, the package your using is updated and issue you reported should be reproducible with the live environment of the Desktop CD development release - Maverick Meerkat. It would help us greatly if you could test with it so we can work on getting it fixed in the next release of Ubuntu. You can find more about the development release at http://www.ubuntu.com/testing/. Please repost a detailed error report and update the bug status. Thanks again and we appreciate your help.

This is an installer issue, and is therefore not reproducible in the
live environment. Please disregard the previous message sent to this
bug, which was not written by an installer developer.

 status triaged

Changed in debian-installer (Ubuntu):
status: Incomplete → Triaged
Ubfan (ubfan1) wrote :

The Maverick (10.10) live usb media (32 bit desktop) displayed this problem, refusing to get past a hibernated embedded windows which did not affect previous installations back to Intrepid. I believe the hibernated Windows partition was for a quick start of media player for DVDs or CDs but has never been used to my knowledge. The installer stalled on the Ubuntu screen with the colored dots. Typing ESC got to the underlying error screen.

The (manually copied) error was:
Windows is hibernated, refused to mount.
Failed to mount "/dev/sda3": Operation not permitted.
The NTFS partition is hibernated. Please resume and shutdown Windows properly,
or mount the volume read-only with the 'ro' mount options, or mount the volume
read-write with the 'remove_hiberfile' mount option.
For example type on the command line:
  mount -t ntfs-3g -o remove_hiberfile /dev/sda3 /cdrom

Ubfan (ubfan1) wrote :

The Maverick installer was a 2G SD card, created on a fully patched Lucid system on Nov 15, 2010. The workaround to the error was to type F6 early on, which seemed to skip some checking and got me to the language selection screen, from which I installed Maverick to a 4G stick. The error was consistent. If I let the install run without keyboard entry, it would always hang at the error.

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

Other bug subscribers