PDA

View Full Version : [ubuntu] Can't boot Lucid getting grub prompt



ypestis
June 30th, 2010, 10:39 PM
Hello after upgrading my Karmic 9.10 to Lucid 10.4 I can't boot anymore to Linux only to Windows... My installation is a WUBI installation and I installed it on the only harddisk I have in the folder c:\ubuntu\

Now when I boot I get a grub prompt and when I do LS I see hd0,msdos01 as partition...
Now's I've tried to manual boot it by using the following commands from the ubuntu manual

set root=(loop0)
linux /vmlinuz root=/dev/sda1 loop=/ubuntu/disks/root.disk ro

after this command I get an error
error: no such disk
so I am guessing that the sda1 is not the right one..

I've tried hd01 hda1 and some variations but they give the same error.
what am I doing wrong?
Is there any other way to fix this?
Thank you very much!

ypestis
July 1st, 2010, 10:59 AM
Oke I managed to get into Ubuntu Lucid now by using the following commands:

insmod ntfs
set root=(hd0,1)
loopback loop0 /ubuntu/disks/root.disk
set root=(loop0)
linux /vmlinuz root=/dev/sda1 loop=/ubuntu/disks/root.disk ro
initrd /initrd.img
boot

After this I did:
sudo grub-update

Generating grub.cfg ...
Found linux image: /boot/vmlinuz-2.6.35-6-generic
Found initrd image: /boot/initrd.img-2.6.35-6-generic
Found linux image: /boot/vmlinuz-2.6.31-22-generic
Found initrd image: /boot/initrd.img-2.6.31-22-generic
Found linux image: /boot/vmlinuz-2.6.31-21-generic
Found initrd image: /boot/initrd.img-2.6.31-21-generic
Found linux image: /boot/vmlinuz-2.6.31-20-generic
Found initrd image: /boot/initrd.img-2.6.31-20-generic
Found linux image: /boot/vmlinuz-2.6.31-14-generic
Found initrd image: /boot/initrd.img-2.6.31-14-generic
Found Ubuntu on /dev/sda1
done

Then I did:
sudo grub-install /dev/sda1
Installation finished. No error reported.

After I rebooted but I still go to the grub prompt...
I checked boot/grub/grub.cfg and as far as I can see it should be good...


Here's a paste of my bootscript log:

Boot Info Script 0.55 dated February 15th, 2010

============================= Boot Info Summary: ==============================

=> Windows is installed in the MBR of /dev/sda

sda1: __________________________________________________ _______________________

File system: ntfs
Boot sector type: Windows XP
Boot sector info: No errors found in the Boot Parameter Block.
Operating System: Windows XP
Boot files/dirs: /boot.ini /ntldr /NTDETECT.COM /wubildr.mbr
/ubuntu/winboot/wubildr.mbr /wubildr
/ubuntu/winboot/wubildr /ubuntu/disks/root.disk
/ubuntu/disks/swap.disk

sda1/Wubi: __________________________________________________ _______________________

File system: ext4
Boot sector type: -
Boot sector info:
Operating System: Ubuntu maverick (development
branch)
Boot files/dirs: /boot/grub/grub.cfg /etc/fstab

=========================== Drive/Partition Info: =============================

Drive: sda ___________________ __________________________________________________ ___

Disk /dev/sda: 80.0 GB, 80026361856 bytes
240 heads, 63 sectors/track, 10337 cylinders, total 156301488 sectors
Units = sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 512 bytes

Partition Boot Start End Size Id System

/dev/sda1 * 63 156,295,439 156,295,377 7 HPFS/NTFS


blkid -c /dev/null: __________________________________________________ __________

Device UUID TYPE LABEL

/dev/loop0 cc8922ed-667e-4e22-8134-04cdd95f78e2 ext4
/dev/sda1 1208B92908B90CAB ntfs
/dev/sda: PTTYPE="dos"

============================ "mount | grep ^/dev output: ===========================

Device Mount_Point Type Options

/dev/loop0 / ext4 (rw,errors=remount-ro)
/dev/sda1 /host fuseblk (rw,nosuid,nodev,relatime,user_id=0,group_id=0,all ow_other,blksize=4096)


================================ sda1/boot.ini: ================================

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

======================== sda1/Wubi/boot/grub/grub.cfg: ========================

#
# DO NOT EDIT THIS FILE
#
# It is automatically generated by 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
set have_grubenv=true
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 part_msdos
insmod ntfs
set root='(hd0,msdos1)'
search --no-floppy --fs-uuid --set 1208b92908b90cab
loopback loop0 /ubuntu/disks/root.disk
set root=(loop0)
if loadfont /usr/share/grub/unicode.pf2 ; then
set gfxmode=640x480
insmod gfxterm
insmod vbe
fi
if terminal_output gfxterm ; then true ; else
# For backward compatibility with versions of terminal.mod that don't
# understand terminal_output
terminal gfxterm
fi
insmod part_msdos
insmod ntfs
set root='(hd0,msdos1)'
search --no-floppy --fs-uuid --set 1208b92908b90cab
loopback loop0 /ubuntu/disks/root.disk
set root=(loop0)
set locale_dir=($root)/boot/grub/locale
set lang=en
insmod gettext
if [ "${recordfail}" = 1 ]; then
set timeout=-1
else
set timeout=1
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.35-6-generic" {
insmod part_msdos
insmod ntfs
set root='(hd0,msdos1)'
search --no-floppy --fs-uuid --set 1208b92908b90cab
loopback loop0 /ubuntu/disks/root.disk
set root=(loop0)
linux /boot/vmlinuz-2.6.35-6-generic root=/dev/sda1 loop=/ubuntu/disks/root.disk ro splash quiet quiet splash
initrd /boot/initrd.img-2.6.35-6-generic
}
menuentry "Ubuntu, Linux 2.6.35-6-generic (recovery mode)" {
insmod part_msdos
insmod ntfs
set root='(hd0,msdos1)'
search --no-floppy --fs-uuid --set 1208b92908b90cab
loopback loop0 /ubuntu/disks/root.disk
set root=(loop0)
linux /boot/vmlinuz-2.6.35-6-generic root=/dev/sda1 loop=/ubuntu/disks/root.disk ro single splash quiet
initrd /boot/initrd.img-2.6.35-6-generic
}
menuentry "Ubuntu, Linux 2.6.31-22-generic" {
insmod part_msdos
insmod ntfs
set root='(hd0,msdos1)'
search --no-floppy --fs-uuid --set 1208b92908b90cab
loopback loop0 /ubuntu/disks/root.disk
set root=(loop0)
linux /boot/vmlinuz-2.6.31-22-generic root=/dev/sda1 loop=/ubuntu/disks/root.disk ro splash quiet quiet splash
initrd /boot/initrd.img-2.6.31-22-generic
}
menuentry "Ubuntu, Linux 2.6.31-22-generic (recovery mode)" {
insmod part_msdos
insmod ntfs
set root='(hd0,msdos1)'
search --no-floppy --fs-uuid --set 1208b92908b90cab
loopback loop0 /ubuntu/disks/root.disk
set root=(loop0)
linux /boot/vmlinuz-2.6.31-22-generic root=/dev/sda1 loop=/ubuntu/disks/root.disk ro single splash quiet
initrd /boot/initrd.img-2.6.31-22-generic
}
menuentry "Ubuntu, Linux 2.6.31-21-generic" {
insmod part_msdos
insmod ntfs
set root='(hd0,msdos1)'
search --no-floppy --fs-uuid --set 1208b92908b90cab
loopback loop0 /ubuntu/disks/root.disk
set root=(loop0)
linux /boot/vmlinuz-2.6.31-21-generic root=/dev/sda1 loop=/ubuntu/disks/root.disk ro splash quiet quiet splash
initrd /boot/initrd.img-2.6.31-21-generic
}
menuentry "Ubuntu, Linux 2.6.31-21-generic (recovery mode)" {
insmod part_msdos
insmod ntfs
set root='(hd0,msdos1)'
search --no-floppy --fs-uuid --set 1208b92908b90cab
loopback loop0 /ubuntu/disks/root.disk
set root=(loop0)
linux /boot/vmlinuz-2.6.31-21-generic root=/dev/sda1 loop=/ubuntu/disks/root.disk ro single splash quiet
initrd /boot/initrd.img-2.6.31-21-generic
}
menuentry "Ubuntu, Linux 2.6.31-20-generic" {
insmod part_msdos
insmod ntfs
set root='(hd0,msdos1)'
search --no-floppy --fs-uuid --set 1208b92908b90cab
loopback loop0 /ubuntu/disks/root.disk
set root=(loop0)
linux /boot/vmlinuz-2.6.31-20-generic root=/dev/sda1 loop=/ubuntu/disks/root.disk ro splash quiet quiet splash
initrd /boot/initrd.img-2.6.31-20-generic
}
menuentry "Ubuntu, Linux 2.6.31-20-generic (recovery mode)" {
insmod part_msdos
insmod ntfs
set root='(hd0,msdos1)'
search --no-floppy --fs-uuid --set 1208b92908b90cab
loopback loop0 /ubuntu/disks/root.disk
set root=(loop0)
linux /boot/vmlinuz-2.6.31-20-generic root=/dev/sda1 loop=/ubuntu/disks/root.disk ro single splash quiet
initrd /boot/initrd.img-2.6.31-20-generic
}
menuentry "Ubuntu, Linux 2.6.31-14-generic" {
insmod part_msdos
insmod ntfs
set root='(hd0,msdos1)'
search --no-floppy --fs-uuid --set 1208b92908b90cab
loopback loop0 /ubuntu/disks/root.disk
set root=(loop0)
linux /boot/vmlinuz-2.6.31-14-generic root=/dev/sda1 loop=/ubuntu/disks/root.disk ro splash quiet quiet splash
initrd /boot/initrd.img-2.6.31-14-generic
}
menuentry "Ubuntu, Linux 2.6.31-14-generic (recovery mode)" {
insmod part_msdos
insmod ntfs
set root='(hd0,msdos1)'
search --no-floppy --fs-uuid --set 1208b92908b90cab
loopback loop0 /ubuntu/disks/root.disk
set root=(loop0)
linux /boot/vmlinuz-2.6.31-14-generic root=/dev/sda1 loop=/ubuntu/disks/root.disk ro single splash quiet
initrd /boot/initrd.img-2.6.31-14-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 "Ubuntu (on /dev/sda1)" {
insmod part_msdos
insmod ntfs
set root='(hd0,msdos1)'
search --no-floppy --fs-uuid --set 1208b92908b90cab
drivemap -s (hd0) ${root}
chainloader +1
}
### 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 ###

### BEGIN /etc/grub.d/41_custom ###
if [ -f $prefix/custom.cfg ]; then
source $prefix/custom.cfg;
fi
### END /etc/grub.d/41_custom ###

============================= sda1/Wubi/etc/fstab: =============================

# /etc/fstab: static file system information.
#
# Use 'blkid -o value -s UUID' to print the universally unique identifier
# for a device; this may be used with UUID= as a more robust way to name
# devices that works even if disks are added and removed. See fstab(5).
#
# <file system> <mount point> <type> <options> <dump> <pass>
proc /proc proc defaults 0 0
/host/ubuntu/disks/root.disk / ext4 loop,errors=remount-ro 0 1
/host/ubuntu/disks/swap.disk none swap loop,sw 0 0

================= sda1/Wubi: Location of files loaded by Grub: =================


2.6GB: boot/grub/grub.cfg
2.4GB: boot/initrd.img-2.6.31-14-generic
5.6GB: boot/initrd.img-2.6.31-20-generic
5.3GB: boot/initrd.img-2.6.31-21-generic
12.4GB: boot/initrd.img-2.6.31-22-generic
14.3GB: boot/initrd.img-2.6.35-6-generic
2.4GB: boot/vmlinuz-2.6.31-14-generic
1.2GB: boot/vmlinuz-2.6.31-20-generic
4.3GB: boot/vmlinuz-2.6.31-21-generic
5.7GB: boot/vmlinuz-2.6.31-22-generic
13.7GB: boot/vmlinuz-2.6.35-6-generic
14.3GB: initrd.img
13.7GB: vmlinuz
=============================== StdErr Messages: ===============================

mdadm: No arrays found in config file or automatically

Any suggestions??

ypestis
July 1st, 2010, 01:59 PM
tried
sudo dpkg-reconfigure grub

it says it finds a quiet splash so I just pressed enter.. It finds another I press enter again...
Then I need to select a harddisk?
sda and sda1 can be selected..
tried running the dpkg-reconfigure with selecting one of these at the time but no luck..

I have to add that during the installtion of the upgrade from karmic to lucid I answered all the grub installations questions with yes.

kansasnoob
July 1st, 2010, 03:59 PM
I know little to nothing about Wubi but I fear you might be making things worse, especially doing this:


tried
sudo dpkg-reconfigure grub

Because the proper package name for grub 2 is "grub-pc", whereas the package name "grub" is for legacy grub.

So, you'll now need to run the Boot Info Script again, and post the new RESULTS.txt. But I'd do so in this thread:

http://ubuntuforums.org/showthread.php?t=1195275

Also read the "Important Note to Wubi (Windows Ubuntu) Users" there.

Hopefully drs305 will have an answer for you.

ypestis
July 1st, 2010, 07:06 PM
Hi thanks for your reply..

Actually I looked back into my terminal history and I did a dpkg-reconfigure grub-pc

Anyway I will make a fresh bootinfo script log and I will post that in the link you gave to me.
Thank you very much!

oldfred
July 1st, 2010, 09:59 PM
I am afraid I do not know about wubi, but did you somehow install

Operating System: Ubuntu maverick (development
branch)

I did not think the wubi version of maverick was out yet?

Not many here are using wubi and only a few are using maverick at all, so you are out on the very edge of testing.

ypestis
July 2nd, 2010, 04:27 AM
I have never heard of Ubuntu Maverick but when I go to system -> about ubuntu it says:
You are using Ubuntu 10.04 LTS - the Lucid Lynx - released in April 2010

oldfred
July 2nd, 2010, 04:54 AM
Your kernels also are Maverick

To see what system says:
Grub version:
grub-install -v
System Version:
lsb_release -a
dpkg -l 'grub*'
Installed versions:
grub-install -v && aptitude show grub|head -4 && aptitude show grub-pc|head -4 && aptitude show grub-common|head -4 && aptitude show os-prober|head -4

ypestis
July 2nd, 2010, 05:20 AM
Hi thanks for that I really appreciate it!

So the following info has come up:
grub-install -v
grub-install.real (GRUB) 1.98+20100614-2ubuntu3

lsb_release -a
No LSB modules are available.
Distributor ID: Ubuntu
Description: Ubuntu maverick (development branch)
Release: 10.10
Codename: maverick

dpkg -l 'grub*'
Desired=Unknown/Install/Remove/Purge/Hold
| Status=Not/Inst/Conf-files/Unpacked/halF-conf/Half-inst/trig-aWait/Trig-pend
|/ Err?=(none)/Reinst-required (Status,Err: uppercase=bad)
||/ Name Version Description
+++-==============-==============-============================================
un grub <none> (no description available)
ii grub-common 1.98+20100614- GRand Unified Bootloader, version 2 (common
un grub-coreboot <none> (no description available)
un grub-doc <none> (no description available)
un grub-efi <none> (no description available)
un grub-efi-amd64 <none> (no description available)
un grub-efi-ia32 <none> (no description available)
un grub-emu <none> (no description available)
un grub-ieee1275 <none> (no description available)
un grub-legacy <none> (no description available)
un grub-legacy-do <none> (no description available)
un grub-linuxbios <none> (no description available)
ii grub-pc 1.98+20100614- GRand Unified Bootloader, version 2 (PC/BIOS
un grub-yeeloong <none> (no description available)
un grub2 <none> (no description available)

grub-install -v && aptitude show grub|head -4 && aptitude show grub-pc|head -4 && aptitude show grub-common|head -4 && aptitude show os-prober|head -4
grub-install.real (GRUB) 1.98+20100614-2ubuntu3
Package: grub
New: yes
State: not installed
Version: 0.97-29ubuntu60
Package: grub-pc
State: installed
Automatically installed: yes
Version: 1.98+20100614-2ubuntu3
Package: grub-common
State: installed
Automatically installed: yes
Version: 1.98+20100614-2ubuntu3
Package: os-prober
State: installed
Automatically installed: yes
Version: 1.39

Rubi1200
July 2nd, 2010, 10:11 AM
This tutorial by drs305 should help:

http://ubuntuforums.org/showthread.php?t=1195275

Read the section entitled
Important Note to Wubi (Windows Ubuntu) Users: carefully.

By the way, if you like Ubuntu why not set up a dual-boot system? Wubi has been known to cause complications and we would be happy to walk you through the process of dual-booting your system.

ypestis
July 2nd, 2010, 10:36 AM
Actually my root.disk just failed when I booted Linux Lucid from grub I fcdisk or something was running and stopped with an error so I guess the root.disk is corrupted..
I could be able to fix it with testdisk I guess but im getting a bit tired of fooling around with this install so I guess I will probably do a fresh install on a partition this time to be sure to have no problems anymore..

If you could tell me which tutorial is the better one to follow I would appreciate it.

Thanks all!

Rubi1200
July 2nd, 2010, 10:50 AM
Actually my root.disk just failed when I booted Linux Lucid from grub I fcdisk or something was running and stopped with an error so I guess the root.disk is corrupted..
I could be able to fix it with testdisk I guess but im getting a bit tired of fooling around with this install so I guess I will probably do a fresh install on a partition this time to be sure to have no problems anymore..

If you could tell me which tutorial is the better one to follow I would appreciate it.

Thanks all!

I think you need to go into Windows and first delete Wubi from Add/Remove Programs if I am not mistaken: http://wubi-installer.org/faq.php#use

Anyway, these links should provide enough information to do a clean install of Ubuntu and set up a dual-boot system:

https://help.ubuntu.com/community/DualBoot/Windows

https://help.ubuntu.com/community/GraphicalInstall

For more general information:

http://ohioloco.ubuntuforums.org/showthread.php?t=801404

http://sites.google.com/site/easylinuxtipsproject/Home

Good luck!

Be careful with partitioning and where GRUB is installed.

If you have more questions feel free to ask here.

ypestis
July 2nd, 2010, 11:46 AM
Yeah actually I do have a question.
Do you know if it's possible to split my current partition into 2 then reinstalling a fresh Linux Lucid on it while keeing the Wubi Linux Karmic on the other partition together with XP?

My computer boots into the Windows XP bootloader first so I think from there I should be able to ad another option to dual boot to the new Linux Lucid partition right?

dino99
July 2nd, 2010, 11:59 AM
make a clean real install

mini howto: http://ubuntuforums.org/showpost.php?p=9216264&postcount=14

Rubi1200
July 2nd, 2010, 12:03 PM
Yeah actually I do have a question.
Do you know if it's possible to split my current partition into 2 then reinstalling a fresh Linux Lucid on it while keeing the Wubi Linux Karmic on the other partition together with XP?

My computer boots into the Windows XP bootloader first so I think from there I should be able to ad another option to dual boot to the new Linux Lucid partition right?

This is a good question to which I do not have the answer. I suppose theoretically it is possible.

However, why keep the Wubi install if you want to put Ubuntu on the hard-drive anyway?

I also found this useful link courtesy of yetiman64:

http://members.iinet.net/~herman546/index.html

ypestis
July 2nd, 2010, 12:11 PM
Because on the Wubi I have Karmic installed now restored from backup with all my Apps mail and settings and it would be like to keep it so I can look wich apps I want to keep transfer wich files etc so I can transfer them to Lucid... Also it would give me some time to configure Lucid till it's running as I want after which I can remove the Wubi install

Rubi1200
July 2nd, 2010, 12:57 PM
Again, I am not sure if it can be done or whether it is advisable.

If you already have a backup of your important files, settings etc. that is great.

I would wait and see if someone can answer this question before you attempt it.

ypestis
July 2nd, 2010, 01:37 PM
Actually im going to try to do an upgrade of Karmic again cause it has worked good with wubi all this times and it's really easy backing up and restoring a WUBI install simply just by copying the ubuntu folder in Windows and I like that.
This and the fact I will have to reconfigure and reinstall everything I have running.

Do you have any suggestion how I can do a "safe upgrade" so that I keep my grub and won't get into the same problems?

darkod
July 2nd, 2010, 01:46 PM
If you are using wubi, when upgrading from Karmic to Lucid, if you get a window asking where to install grub2, DON'T select anything. Wubi doesn't use grub2, not in the real sense. It is only virtual install.
I'm not sure if you will be able to boot wubi Lucid without any problems later, but I am sure that if you install grub2 to the MBR of the disk or any partitions you will likely break your system because you are not using grub2 on the MBR right now.

As for adding a full Lucid install, yes, you can do it. Usually it would be better to uninstall wubi first so you get that space back, but it's not necessary. But you will need to shrink some partition to make unallocated space for the full Ubuntu, depending what is your disk layout now.

For XP, you can shrink using Gparted from the ubuntu cd in live mode. After that boot XP few times to do its disk check. Only after that proceed to install ubuntu into the unallocated space you created.

It will install grub2 to the MBR and you will have an entry for XP in the grub2 boot menu (not also for wubi because it's inside XP). Once you select XP you will get your windows bootloader that you use now, to select between XP and wubi.

It's a bit of jumping around, so as soon as you transfer your settings and data, and you are happy with it, it's better to uninstall wubi.

ypestis
July 2nd, 2010, 02:19 PM
Oke so I can run Wubi next to a partition with linux on it that's interesting!

At the moment I only have 1 SSD harddisk with 1 partition sda1 with Windows XP on it and WUBI Karmic.
Correct me if im wrong, so all I have to do is

Boot liveCD
shrink the partition with Gparted so that I create an extended 2nd partition (doesn't matter NTFS FAT cause Livecd will format anyway)

I have to shrink and create a new space on the right side right?

What about another partition for swap size of my memory 2gig for Hibernate?
Do I shrink my partiton in Gparted and create 2 extended partitions and let the Livecd Installer handle the rest?

From here on having 2 extended partition do I just boot from the Lucid Livecd and the select install Lucid and choose sda2 to install to?

darkod
July 2nd, 2010, 02:35 PM
Oke so I can run Wubi next to a partition with linux on it that's interesting!

At the moment I only have 1 SSD harddisk with 1 partition sda1 with Windows XP on it and WUBI Karmic.
Correct me if im wrong, so all I have to do is

Boot liveCD
shrink the partition with Gparted so that I create an extended 2nd partition (doesn't matter NTFS FAT cause Livecd will format anyway)

I have to shrink and create a new space on the right side right?

What about another partition for swap size of my memory 2gig for Hibernate?
Do I shrink my partiton in Gparted and create 2 extended partitions and let the Livecd Installer handle the rest?

From here on having 2 extended partition do I just boot from the Lucid Livecd and the select install Lucid and choose sda2 to install to?

No, don't create any partitions before you start the installer, no need. Just resize sda1 to make space on the right. Leave that space as unallocated, it will be unallocated by default after the shrink.
Then when you start the installer you can use the Use Largest Available Free space option. That will install into the unallocated space, because that's considered free space not belonging to any partition (not unused space inside a partition).

No need to create the partitions in advanced unless you really want to, but you seem confused what to do. Leave the installer do it for you this time.

PS. I don't know what size is the SSD but they don't have large size these days. That is one more reason to boot wubi first, copy all data you need onto an ext hdd, and uninstall wubi first so you can use the space taken by wubi right now. But we already mentioned that, it's your choice what you want to do. Like this when you uninstall wubi later, sda1 will still take the same space, instead of being able to use it for ubuntu. I wouldn't start resizing a new ubuntu installation right now.

Copying data to ext hdd, uninstalling wubi, defragmenting XP, shrinking sda1, and then installung full ubuntu is the best approach according to me. Then just put the data back.

ypestis
July 2nd, 2010, 02:42 PM
I already have my Wubi backed up but the point is to keep it working and delete it later so I can always switch back to my old karmic linux to see which programs and settings I have..
Do you think this could potentially cause problems to keep it? cause otherwise I might consider just going for the clean install without keeping wubi..

Will the installer make that 2gb SWAP partition also so I can use Hibernation?

darkod
July 2nd, 2010, 02:55 PM
I already have my Wubi backed up but the point is to keep it working and delete it later so I can always switch back to my old karmic linux to see which programs and settings I have..
Do you think this could potentially cause problems to keep it? cause otherwise I might consider just going for the clean install without keeping wubi..

Will the installer make that 2gb SWAP partition also so I can use Hibernation?

The installer will create the standard root+swap setup, two partitions. Their sizes will depend on how much space you allocate to ubuntu (how much space you leave unallocated after the shrink).

If you want full control of the partitions sizes, create them yourself using Manual Partitioning. One root partition and one swap partition.

It's not a problem to keep wubi, except that uninstalling it would help you better organize your SSD right now.