HOWTO: migrate wubi install to partition

[bcbc]

OK, I uncommended that line and saved it. Then I ran the code to update ram, and got:

Run the following:

sudo blkid /dev/sda7

This will output something like:

/dev/sda7: UUID="89a1b68b-20dd-4897-b826-92ba8adeb48d" TYPE="swap"

Then note the UUID, confirm that it is type "swap" and then ensure that the UUID matches that in the fstab and resume file by running the following two commands:

cat /etc/fstab | grep swap
cat /etc/initramfs-tools/conf.d/resume

If the UUID you see is different, correct it. If they all match the uuid of your swap, then run:

sudo update-initramfs -u

[Telos3K]

I ran:

sudo blkid /dev/sda7

and got:

/dev/sda7: LABEL="Swap" UUID="24622487-0dd5-4c54-bd7f-724c9bf66979" TYPE="swap"

I then changed my fstab and resume files to match it:

bwbloch@ubuntu:~$ cat /etc/fstab | grep swap
#/host/ubuntu/disks/swap.disk	none	swap	loop,sw	0	0
UUID=24622487-0dd5-4c54-bd7f-724c9bf66979    none    swap    sw    0    0
bwbloch@ubuntu:~$ cat /etc/initramfs-tools/conf.d/resume
RESUME=UUID=24622487-0dd5-4c54-bd7f-724c9bf66979
bwbloch@ubuntu:~$

I then run:

sudo update-initramfs -u

and get:

update-initramfs: Generating /boot/initrd.img-2.6.32-27-generic
bwbloch@ubuntu:~$

Then reboot, and got to hibernate, and the system freezes up, then shuts down and performs a disk check on rebooting.

Per bcbc's suggestion, this is now a new thread....

[bcbc]

Telos3k,
There are many reasons that hibernation may not work. At this point it's best to create a new thread (because we're getting off topic for this one) and include the following info in it.

Machine brand/model - full specs

Post the result of:

grep 'PM:' /var/log/syslog

and

free

I'll find your new thread, or you can just edit your previous post with the address.

[dtx4]

kool, thanks, this is by far the easiest way to install ubuntu i believe.
for all those windows users, who have a problem partitioning hard-drive and dont wanna go through all of this mammoth of a thread, here's a quick recap:
>get wubi on your windows box
>https://help.ubuntu.com/community/HowtoPartition Go through this link
>follow the steps on page 1

peace

now i need to install kernel updates and hope that it doesnt break my ubuntu! :O

[robst]

Hi bcbc,
I congratulate you for this tool, it worked all fine and I am happy with the results, in my case i got rid of my Vista, and now I am solely on Ubuntu, I did the move basically because the available resources were getting scarce working in Windows.

Now I want to uninstall Wubi, I have seen all uninstall tools are for windows, I wonder how do i do it from the migrated Linux. I am wondering if I just reformat the partition on which it was installed first (I install it in a small 10G primary partition).

I would appreciate your comments. Best of luck.

[bcbc]

Hi bcbc,
I congratulate you for this tool, it worked all fine and I am happy with the results, in my case i got rid of my Vista, and now I am solely on Ubuntu, I did the move basically because the available resources were getting scarce working in Windows.

Now I want to uninstall Wubi, I have seen all uninstall tools are for windows, I wonder how do i do it from the migrated Linux. I am wondering if I just reformat the partition on which it was installed first (I install it in a small 10G primary partition).

I would appreciate your comments. Best of luck.

Hi Robst, yes - if you no longer have windows the 'uninstall' of wubi on the 10GB is a simple format. Or you could just delete the /ubuntu directory on this partition and keep whatever else is on it (if anything).

Once you remove the root.disk then you no longer have the wubi backup (which is still bootable, even without windows), so it's a good idea to have a backup of your migrated install in place.

Good luck!

[bcbc]

kool, thanks, this is by far the easiest way to install ubuntu i believe.
for all those windows users, who have a problem partitioning hard-drive and dont wanna go through all of this mammoth of a thread, here's a quick recap:
>get wubi on your windows box
>https://help.ubuntu.com/community/HowtoPartition Go through this link
>follow the steps on page 1

peace

now i need to install kernel updates and hope that it doesnt break my ubuntu! :O

Thanks for the feedback. You're right this thread has got fairly long, however I don't think it's required to read the whole thing unless you're interested in other people's experiences. If I hear of any bugs I'll update post #1 and following that try and get it fixed asap, so technically Post #1 should contain everything you need to know about the migration.

I though about including links to partitioning guides there, but some of them contain old information - and the resulting discussions could easily end up dominating a thread such as this.

Good luck with those update

[WeFY-KVQqr]

I'm baffled...
I've tried this nice script to copy a wubi install to a partition. I've decided to stick with the bootloader chaining into wubi grub for the moment.
It worked flawlessly except one problem. The new install won't appear in the grub menu and what's more the previous available options to boot into windows 7 and the option of memtest86 are gone too. So one could say that all os-prober options of grub won't stick.
I've tried to run the bootinfo script and that one indeed detects windows and the new linux install.

So I've decided to boot into the regular wubi install and tried to perform a grub update.
During that process it is shown that windows is detected and the new linux install but unfortunately the grub menu is STILL not updated.

In the meantime I've invested so much time in this that I could easily have installed a fresh ubuntu version at least 3 times, so for now I've done some nice tweaking and edited the wubi grub menu in order to make it boot the new linux install. However I guess that will be automatically reverted back by a future grub update.

Does someone know why the os-prober entries are not picked up?
Or is there somehow a limit in the number of entries the wubi grub menu will display?
Currently there are 8 entries in it (4 kernels and 4 recovery options of the same kernels).

[bcbc]

I'm baffled...
I've tried this nice script to copy a wubi install to a partition. I've decided to stick with the bootloader chaining into wubi grub for the moment.
It worked flawlessly except one problem. The new install won't appear in the grub menu and what's more the previous available options to boot into windows 7 and the option of memtest86 are gone too. So one could say that all os-prober options of grub won't stick.
I've tried to run the bootinfo script and that one indeed detects windows and the new linux install.

So I've decided to boot into the regular wubi install and tried to perform a grub update.
During that process it is shown that windows is detected and the new linux install but unfortunately the grub menu is STILL not updated.

In the meantime I've invested so much time in this that I could easily have installed a fresh ubuntu version at least 3 times, so for now I've done some nice tweaking and edited the wubi grub menu in order to make it boot the new linux install. However I guess that will be automatically reverted back by a future grub update.

Does someone know why the os-prober entries are not picked up?
Or is there somehow a limit in the number of entries the wubi grub menu will display?
Currently there are 8 entries in it (4 kernels and 4 recovery options of the same kernels).

What release are you on?

You mentioned that the "it is shown that windows is detected and the new linux install". Can you confirm that the auto-generated grub.cfg contains all the correct entries. Just backup your edited one first.

UPDATE:
I've duplicated this on 10.04.1 with the latest grub-pc update applied. This is somehow related to the grub bug that causes boot failures in wubi 10.04.1. The fix is the same (see here):

sudo mv /boot/grub /boot/grubold
sudo mkdir /boot/grub
sudo cp /boot/grubold/grubenv /boot/grub
sudo update-grub

[WeFY-KVQqr]

Yeah, message #200 in this thread. This is a very successful and useful thread. =D>

Anyway...

Thanks bcbc for your very quick response.

I'm using the dreaded Ubuntu 10.04.1 version.
I'm familiar with the thread you mention, but I can't exactly link my problem to one of the examples mentioned there.

Does my Windows boot? I should say yes because it is bootable with its own bootloader, but I can't boot it from the grub menu, because is not listed there anymore.
Does my Ubuntu boot? Well, that's probably a "yes" too, but I can't boot the particular version I want too because it isn't listed in the menu, but the other entries in the grub menu boot perfectly.

Furthermore I don't know exactly what to do with your suggestion. If I look it up in the thread you mentioned, it looks to me as a "partial" solution. Do you mean I've only to do these four actions to solve the problem?
If not do I have problem 1 or problem 2 according to you?
In the meantime I blew the edited grub menu and I had to repair it with a Live CD so I'm back to the "original" grub menu and I'm a bit more cautious now before performing more actions.


I found out that when I go to the command line in the grub menu and I do the following three actions I can boot the new ubuntu installation too:

linux /boot/vmlinuz-2.6.32-27-generic root=UUID=843f3473-a806-431f-a33f-45be9e8ce14c ro quiet splash
initrd /boot/initrd.img-2.6.32-27-generic
boot

You asked about grub.cfg. Well I don't know if it contains the correct entries.
It looks like this:

#
# DO NOT EDIT THIS FILE
#
# It is automatically generated by /usr/sbin/grub-mkconfig using templates
# from /etc/grub.d and settings from /etc/default/grub
#
 
### BEGIN /etc/grub.d/00_header ###
if [ -s $prefix/grubenv ]; then
  load_env
fi
set default="0"
if [ ${prev_saved_entry} ]; then
  set saved_entry=${prev_saved_entry}
  save_env saved_entry
  set prev_saved_entry=
  save_env prev_saved_entry
  set boot_once=true
fi
 
function savedefault {
  if [ -z ${boot_once} ]; then
    saved_entry=${chosen}
    save_env saved_entry
  fi
}
 
function recordfail {
  set recordfail=1
  if [ -n ${have_grubenv} ]; then if [ -z ${boot_once} ]; then save_env recordfail; fi; fi
}
insmod ntfs
set root='(hd0,2)'
search --no-floppy --fs-uuid --set c4e2d2cde2d2c2ba
loopback loop0 /ubuntu/disks/root.disk
set root=(loop0)
if loadfont /usr/share/grub/unicode.pf2 ; then
  set gfxmode=640x480
  insmod gfxterm
  insmod vbe
  if terminal_output gfxterm ; then true ; else
    # For backward compatibility with versions of terminal.mod that don't
    # understand terminal_output
    terminal gfxterm
  fi
fi
insmod ntfs
set root='(hd0,2)'
search --no-floppy --fs-uuid --set c4e2d2cde2d2c2ba
loopback loop0 /ubuntu/disks/root.disk
set root=(loop0)
set locale_dir=($root)/boot/grub/locale
set lang=nl
insmod gettext
if [ ${recordfail} = 1 ]; then
  set timeout=-1
else
  set timeout=10
fi
### END /etc/grub.d/00_header ###
 
### BEGIN /etc/grub.d/05_debian_theme ###
set menu_color_normal=white/black
set menu_color_highlight=black/light-gray
### END /etc/grub.d/05_debian_theme ###
 
### BEGIN /etc/grub.d/10_linux ###
### END /etc/grub.d/10_linux ###
 
### BEGIN /etc/grub.d/10_lupin ###
menuentry "Ubuntu, Linux 2.6.32-27-generic" {
    insmod ntfs
    set root='(hd0,2)'
    search --no-floppy --fs-uuid --set c4e2d2cde2d2c2ba
    loopback loop0 /ubuntu/disks/root.disk
    set root=(loop0)
    linux /boot/vmlinuz-2.6.32-27-generic root=/dev/sda2 loop=/ubuntu/disks/root.disk ro   quiet splash
    initrd /boot/initrd.img-2.6.32-27-generic
}
menuentry "Ubuntu, Linux 2.6.32-27-generic (recovery mode)" {
    insmod ntfs
    set root='(hd0,2)'
    search --no-floppy --fs-uuid --set c4e2d2cde2d2c2ba
    loopback loop0 /ubuntu/disks/root.disk
    set root=(loop0)
    linux /boot/vmlinuz-2.6.32-27-generic root=/dev/sda2 loop=/ubuntu/disks/root.disk ro single 
    initrd /boot/initrd.img-2.6.32-27-generic
}
menuentry "Ubuntu, Linux 2.6.32-26-generic" {
    insmod ntfs
    set root='(hd0,2)'
    search --no-floppy --fs-uuid --set c4e2d2cde2d2c2ba
    loopback loop0 /ubuntu/disks/root.disk
    set root=(loop0)
    linux /boot/vmlinuz-2.6.32-26-generic root=/dev/sda2 loop=/ubuntu/disks/root.disk ro   quiet splash
    initrd /boot/initrd.img-2.6.32-26-generic
}
menuentry "Ubuntu, Linux 2.6.32-26-generic (recovery mode)" {
    insmod ntfs
    set root='(hd0,2)'
    search --no-floppy --fs-uuid --set c4e2d2cde2d2c2ba
    loopback loop0 /ubuntu/disks/root.disk
    set root=(loop0)
    linux /boot/vmlinuz-2.6.32-26-generic root=/dev/sda2 loop=/ubuntu/disks/root.disk ro single 
    initrd /boot/initrd.img-2.6.32-26-generic
}
menuentry "Ubuntu, Linux 2.6.32-25-generic" {
    insmod ntfs
    set root='(hd0,2)'
    search --no-floppy --fs-uuid --set c4e2d2cde2d2c2ba
    loopback loop0 /ubuntu/disks/root.disk
    set root=(loop0)
    linux /boot/vmlinuz-2.6.32-25-generic root=/dev/sda2 loop=/ubuntu/disks/root.disk ro   quiet splash
    initrd /boot/initrd.img-2.6.32-25-generic
}
menuentry "Ubuntu, Linux 2.6.32-25-generic (recovery mode)" {
    insmod ntfs
    set root='(hd0,2)'
    search --no-floppy --fs-uuid --set c4e2d2cde2d2c2ba
    loopback loop0 /ubuntu/disks/root.disk
    set root=(loop0)
    linux /boot/vmlinuz-2.6.32-25-generic root=/dev/sda2 loop=/ubuntu/disks/root.disk ro single 
    initrd /boot/initrd.img-2.6.32-25-generic
}
menuentry "Ubuntu, Linux 2.6.32-24-generic" {
    insmod ntfs
    set root='(hd0,2)'
    search --no-floppy --fs-uuid --set c4e2d2cde2d2c2ba
    loopback loop0 /ubuntu/disks/root.disk
    set root=(loop0)
    linux /boot/vmlinuz-2.6.32-24-generic root=/dev/sda2 loop=/ubuntu/disks/root.disk ro   quiet splash
    initrd /boot/initrd.img-2.6.32-24-generic
}
menuentry "Ubuntu, Linux 2.6.32-24-generic (recovery mode)" {
    insmod ntfs
    set root='(hd0,2)'
    search --no-floppy --fs-uuid --set c4e2d2cde2d2c2ba
    loopback loop0 /ubuntu/disks/root.disk
    set root=(loop0)
    linux /boot/vmlinuz-2.6.32-24-generic root=/dev/sda2 loop=/ubuntu/disks/root.disk ro single 
    initrd /boot/initrd.img-2.6.32-24-generic
}
### END /etc/grub.d/10_lupin ###
 
### BEGIN /etc/grub.d/20_memtest86+ ###
### END /etc/grub.d/20_memtest86+ ###
 
### BEGIN /etc/grub.d/30_os-prober ###
menuentry "Windows 7 (loader) (on /dev/sda1)" {
    insmod ntfs
    set root='(hd0,1)'
    search --no-floppy --fs-uuid --set dc1a10b21a108ba0
    chainloader +1
}
menuentry "Windows 7 (loader) (on /dev/sda2)" {
    insmod ntfs
    set root='(hd0,2)'
    search --no-floppy --fs-uuid --set c4e2d2cde2d2c2ba
    chainloader +1
}
menuentry "Windows Vista (loader) (on /dev/sda4)" {
    insmod ntfs
    set root='(hd0,4)'
    search --no-floppy --fs-uuid --set 82deb960deb94d63
    chainloader +1
}
menuentry "Ubuntu, met Linux 2.6.32-27-generic (on /dev/sda6)" {
    insmod ext2
    set root='(hd0,6)'
    search --no-floppy --fs-uuid --set 843f3473-a806-431f-a33f-45be9e8ce14c
    linux /boot/vmlinuz-2.6.32-27-generic root=UUID=843f3473-a806-431f-a33f-45be9e8ce14c ro quiet splash
    initrd /boot/initrd.img-2.6.32-27-generic
}
menuentry "Ubuntu, met Linux 2.6.32-27-generic (herstelmodus) (on /dev/sda6)" {
    insmod ext2
    set root='(hd0,6)'
    search --no-floppy --fs-uuid --set 843f3473-a806-431f-a33f-45be9e8ce14c
    linux /boot/vmlinuz-2.6.32-27-generic root=UUID=843f3473-a806-431f-a33f-45be9e8ce14c ro single
    initrd /boot/initrd.img-2.6.32-27-generic
}
menuentry "Ubuntu, met Linux 2.6.32-26-generic (on /dev/sda6)" {
    insmod ext2
    set root='(hd0,6)'
    search --no-floppy --fs-uuid --set 843f3473-a806-431f-a33f-45be9e8ce14c
    linux /boot/vmlinuz-2.6.32-26-generic root=UUID=843f3473-a806-431f-a33f-45be9e8ce14c ro quiet splash
    initrd /boot/initrd.img-2.6.32-26-generic
}
menuentry "Ubuntu, met Linux 2.6.32-26-generic (herstelmodus) (on /dev/sda6)" {
    insmod ext2
    set root='(hd0,6)'
    search --no-floppy --fs-uuid --set 843f3473-a806-431f-a33f-45be9e8ce14c
    linux /boot/vmlinuz-2.6.32-26-generic root=UUID=843f3473-a806-431f-a33f-45be9e8ce14c ro single
    initrd /boot/initrd.img-2.6.32-26-generic
}
menuentry "Ubuntu, met Linux 2.6.32-25-generic (on /dev/sda6)" {
    insmod ext2
    set root='(hd0,6)'
    search --no-floppy --fs-uuid --set 843f3473-a806-431f-a33f-45be9e8ce14c
    linux /boot/vmlinuz-2.6.32-25-generic root=UUID=843f3473-a806-431f-a33f-45be9e8ce14c ro quiet splash
    initrd /boot/initrd.img-2.6.32-25-generic
}
menuentry "Ubuntu, met Linux 2.6.32-25-generic (herstelmodus) (on /dev/sda6)" {
    insmod ext2
    set root='(hd0,6)'
    search --no-floppy --fs-uuid --set 843f3473-a806-431f-a33f-45be9e8ce14c
    linux /boot/vmlinuz-2.6.32-25-generic root=UUID=843f3473-a806-431f-a33f-45be9e8ce14c ro single
    initrd /boot/initrd.img-2.6.32-25-generic
}
menuentry "Ubuntu, met Linux 2.6.32-24-generic (on /dev/sda6)" {
    insmod ext2
    set root='(hd0,6)'
    search --no-floppy --fs-uuid --set 843f3473-a806-431f-a33f-45be9e8ce14c
    linux /boot/vmlinuz-2.6.32-24-generic root=UUID=843f3473-a806-431f-a33f-45be9e8ce14c ro quiet splash
    initrd /boot/initrd.img-2.6.32-24-generic
}
menuentry "Ubuntu, met Linux 2.6.32-24-generic (herstelmodus) (on /dev/sda6)" {
    insmod ext2
    set root='(hd0,6)'
    search --no-floppy --fs-uuid --set 843f3473-a806-431f-a33f-45be9e8ce14c
    linux /boot/vmlinuz-2.6.32-24-generic root=UUID=843f3473-a806-431f-a33f-45be9e8ce14c ro single
    initrd /boot/initrd.img-2.6.32-24-generic
}
### END /etc/grub.d/30_os-prober ###
 
### BEGIN /etc/grub.d/40_custom ###
# This file provides an easy way to add custom menu entries.  Simply type the
# menu entries you want to add after this comment.  Be careful not to change
# the 'exec tail' line above.
### END /etc/grub.d/40_custom ###

The migrated installation is the one on /dev/sda6.

You see a few times "herstelmodus" that's the Dutch translation of "recovery mode".