Wubi installer/website should warn about potential data loss with root.disk corruption

Bug #1078959 reported by bcbc
20
This bug affects 3 people
Affects Status Importance Assigned to Milestone
Wubi
New
Undecided
Unassigned
ubuntu-website-content
Fix Released
Critical
Unassigned
13.04
New
Undecided
Unassigned

Bug Description

Wubi or the http://www.ubuntu.com/download/desktop/windows-installer site (or both) should warn that the intent of wubi is for trying out Ubuntu and that it is different to a normal install in that all data is stored on a virtual disk that is a single file. In the case of file system corruption, all this data may be lost and that traditional data recovery tools are not able to recover anything.

I see this problem fairly regularly, and the community support response is generally on the lines of: "Well wubi is for testing Ubuntu only", followed by the poster with the problem saying "Well nowhere does it say that on ubuntu.com". In some cases, it's not even clear to the user that they are running something other than a normal windows/ubuntu dual boot.

I think that not providing a warning could expose Canonical to liability issues, and even if it doesn't, it's the right thing to be up front about what wubi is and what it isn't i.e. a small paragraph to state the intent of Wubi, state the limitations and state the risk.

From my own blog post on "Missing the root.disk" I've had 15,000 hits in just over a year. So even if we ignore 90% of those, that still leaves 1500 'missing root disks'. Hard to say exacly the number... but after showing how great Ubuntu can be through Wubi, it's clearly not ideal to then have something like that happen.

Here are some recent examples:
http://ubuntuforums.org/showthread.php?t=2083343 and the pastebin of the bootinfoscript/bootrepair shows a missing root.disk:
sda3: __________________________________________________________________________

    File system: ntfs
    Boot sector type: Windows Vista/7: NTFS
    Boot sector info: No errors found in the Boot Parameter Block.
    Operating System: Windows 7
    Boot files: /bootmgr /Boot/BCD /Windows/System32/winload.exe
                       /wubildr /ubuntu/winboot/wubildr /wubildr.mbr
                       /ubuntu/winboot/wubildr.mbr /ubuntu/disks/swap.disk

mount -o loop /mnt/boot-sav/sda3/ubuntu/disks/root.disk /mnt/boot-sav/wubi1
mount: /dev/loop1: can't read superblock
The file browser that just opened will let you access your Wubi (Linux installed into Windows) files. (/mnt/boot-sav/wubi1/home) Please backup your data now! Then close this window.
xdg-open: file '/mnt/boot-sav/wubi1/home' does not exist
umount /mnt/boot-sav/wubi1
umount: /mnt/boot-sav/wubi1: not mounted
This will try to repair Wubi filesystem. Please backup your data before this operation. Do you want to continue? yes
fsck -f -y /mnt/boot-sav/sda3/ubuntu/disks/root.disk
fsck from util-linux 2.20.1
e2fsck 1.42 (29-Nov-2011)
fsck.ext2: Attempt to read block from filesystem resulted in short read while trying to open /mnt/boot-sav/sda3/ubuntu/disks/root.disk
Could this be a zero-length partition?

Others (from past week):
http://askubuntu.com/q/214399/14916
http://ubuntuforums.org/showthread.php?t=2082589
http://ubuntuforums.org/showthread.php?t=2081325
http://ubuntuforums.org/showthread.php?t=2080563

Revision history for this message
Tanya Edwards (tanya-edwards) wrote :

Thank you for raising this with the Webteam.

We do suggest backing up your data before installing. However, will look at this messaging as part of the next release.

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

I expect this was more of a problem before we spent lots of effort over the last couple of releases on making sure we always unmounted / cleanly. That kind of work does take a while to trickle down into real systems though.

I agree that we should generally be downplaying Wubi on the website and explaining that it's meant as an initial trial option.

Revision history for this message
bcbc (bcbc) wrote :

I'm not sure whether it affects recent releases more or less. I think some of it may be incompatible hardware. I've been running Wubi for a long time without problems and I know of others doing the same - but if you checkout #ubuntu on IRC and other support places Wubi often gets panned and/or dismissed as hard to support, buggy and for trial only - so it's good to at least have that 'heads up' rather than leave the impression that, only once things go pear-shaped, it isn't supported and the user should never have used it in the first place.

PS I am attaching some screen shots of the 12.10 diskimage install process. There's been feedback from some that the initial boot into Ubuntu (after the disk image install) is not the most user friendly experience and I'd have to agree.

Revision history for this message
bcbc (bcbc) wrote :
Revision history for this message
Dimitri John Ledkov (xnox) wrote :

For 13.04 release we agreed to demote Wubi and not-advertise it as prominently. In the mean time we should continue to fix bugs in Wubi such that maybe it can become fully supported again.

Revision history for this message
Peter Mahnke (peterm-ubuntu) wrote :

as Dmitrijs noted, we have demoted Wubi and put large warnings on the pages.

Changed in ubuntu-website-content:
status: New → Fix Committed
Changed in ubuntu-website-content:
importance: Undecided → Critical
status: Fix Committed → Fix Released
Revision history for this message
Kamilion (kamilion) wrote :

Just wanted to make a note in this issue: A colleague sent me a keygen to analyse for malware.

I was too lazy to install VMWare Player and instead used 12.04+WUBI to stick a throwaway ubuntu on disk so I could unpack the PE executable safely.

I had already told Microsoft Security Essentials to ignore the keygen, but guess what happened after I copied the .EXE into the wubi install?

If you guessed "Microsoft Security Essentials deleted root.disk!", you're very correct! It seems as if recently, Microsoft has added the ability to search inside disk images of various types, including VMDK, VDI, VHD and raw disk image files.

Even worse, because the file was so large, Microsoft Security Essentials did not "Quarantine" it, it simply deletes it as soon as the file is found to be unlocked -- So as soon as I had closed down wubi, it evaporated.
After trying to install WUBI again, I figured out it was the virus scanner.

From Windows Explorer, Trying to press the 'delete' key on the new root.disk says "This file is too large for the Recycle Bin. Would you like to delete it?", so I am assuming that same mechanism prevents MSE from quarantine.

Thankful that WUBI will no longer be included in 13.10 to trip other folks up...

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.