boot fails if installed to other drive

Bug #176605 reported by Dazed_75
2
Affects Status Importance Assigned to Milestone
lupin
Incomplete
Undecided
Unassigned
lupin (Ubuntu)
Expired
Undecided
Unassigned

Bug Description

re: beat wubi-installer 7.04 and alpha for 710 (unsure which build). 3 people (Larry, Marvin, Alan) working on 2 situations.

environ 1: Windows xp with drives C:, D:, F:, C: is the active boot drive, user used the beta 7.04 installer and selected to install to drive F:. Installer completed but reboot did not show the option to boot ubuntu. The user ended up re-installing to the C: drive successfully.

environ 2: Drive has a small DOS partition as Drive C: and is the active boot partition. Drive D: has Win 2K installed. User used one of the alpha wubi-installers for 7.10 (may have been build 381) and installed to drive D: with the same result. In this case it was determined that there was a boot.ini on each drive. The one on the active boot partition (C:) contained the expected entry for Win 2K while the one on the D: contained only an entry for ubuntu-linux.

Tentative hypothesis is that the installer updates boot.ini based on the drive the user selects to install the Windows file for the virtual drive rather than where Windows has placed it which was probably decided by the windows install based on the active primary partition.

Impact should be considered high due to the non technical nature of much of the target audience. One short term solution might be to recommend users only install to Drive C (assuming it is the partition marked as active).

We will continue to experiment tomorrow. At that time I will verify the the %SYSTEM% variable for environ 1 points to C: and for environ 2 points to D:

Revision history for this message
Dazed_75 (lthielster) wrote :

I forgot to mention this COULD be related to the cause for bug #164617. I did not consider that a duplicate as that bug is reported as being for UNinstall. That reporter MAY have been trying to uninstall for the same reason that generated this bug report.

Revision history for this message
Agostino Russo (ago) wrote :

Wubi modifies any boot.ini it finds since it is difficult to detect which boot.ini is the active one. So it might modify unnecessary other files but it should not miss the right boot.ini.

Many Wubi 7.04 issues have been fixed in 7.10 which uses a more recent version of grub-installer.
Some more info is required for cases when 7.10 fails (7.04 is less relevant).

Changed in lupin:
status: New → Incomplete
Revision history for this message
Dazed_75 (lthielster) wrote :

Unfortunately the systems we reported on are no longer available for testing. I could build another on which to test but would not be able to get there for at least another week due to other commitments. The one further clue I can offer is an extract from an email from Marvin back on 12/12.
-------
from Marvin on 12/12/07
I had looked at the boot.ini file earlier, and felt that it was working okay. Indeed the boot.ini file contains the directions you said it would:

        "[boot loader]
        timeout=15
        default=multi(0)disk(0)rdisk(0)partition(1)\WINDOWS
        [operating systems]
        multi(0)disk(0)rdisk(0)partition(1)\WINDOWS="Microsoft Windows XP Professional" /fastdetect /NoExecute=OptOut
        c:\wubildr.mbr="Ubuntu""

But, on the first start I had indicated the install should be to drive F: and I did the same on the second try. So, in both cases the install should have been to the same location. Now, the boot.ini file indicates the .mbr file is in C:\. I would expect that, no matter what the actual install partition. The Wubi loader would still be on drive c:\ I doubt that this code tells the Wubi installer where to install Ubuntu. I suspect it tells the system where the bootloader is. But I could be all wrong about this.
-------
So the real question may come down to how would any part of wubi (such as C:\wubildr.mbr) know that the windows file with the installed ubuntu was on drive F:. Again, Marvin did this with the 7.04 Beta of the wubi installer for ubuntu. I know that is not what you currently want info on, but it is what I have for now and perhaps is indicative for the later version as well.

I will check back here before building a new environment to test this [hopefully] next week. Sorry I can't do better sooner.

Revision history for this message
Dazed_75 (lthielster) wrote :

Bah, on rereading this another possibility came to mind. What if when he installed to F:, the installer actually put wubildr.mbr on F: along with the special file but the active boot.ini on C: pointed to c:\wubildr.mbr. Another possibility at least. Again, maybe I can get that checked next week.

Revision history for this message
Dazed_75 (lthielster) wrote :

I think we can relegate this bug to the dead bin. My testing using the alpha 7.10 rev 386 installer has not been able to reproduce it and I think 7.04 issues are moot (see below).

That said, we seem to be discovering more serious issues for those who installed using the Beta wubi-installer 7.04 and then subsequently upgraded the installed ubuntu to 7.10. I believe those issues may have been addressed already but notice the Beta 7.04 is still available for download on the web site. Perhaps that should be replaced with the 7.10. Even though alpha, it seems to work better (see below).

I have had some issues using the alpha 7.10 revisions, but I think they are ubuntu issues rather than wubi issues as I have seen them on normal (non-wubi) 7.10 installs as well. If you want more info, we should communicate separately.

Colin Watson (cjwatson)
Changed in lupin (Ubuntu):
status: New → Incomplete
Revision history for this message
Launchpad Janitor (janitor) wrote :

[Expired for lupin (Ubuntu) because there has been no activity for 60 days.]

Changed in lupin (Ubuntu):
status: Incomplete → Expired
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.