4 replies to this topic

[NaraLTD]

Hi guys. I have done a bit of searching but can't seem to find what I am looking for.

If anyone is able to help I would greatly appreciate it.

A bit of background:
I am an AIX/HP-UX/Linux SysAdmin where I work. So naturally I feel at home w/ the UNIX environment, moreso than say Windows.

Well I was running Ubuntu as my desktop for a while, but just recently the Windows Support Folks dictated that I couldn't do that any more because they couldn't support me.... So now I have Windows installed. The new laptop policy says I can't install any software on the laptop w/o prior written approval from my director. So I installed WUBI at home w/ the intention of 'copying' the files to the HD and booting from a USB key.

I have WUBI working when it hooks into the ntldr/boot.ini, but I can't for the life of me figure out how to get it to work w/ Grub4Dos. I have a bootable USB key that presents me w/ a GRUB menu. But it doesn't find the files to load. I am wondering if there is something special about the WUBILDR that understands the loop device.

Like I said, I get the GRUB menu but when I try to load anything from it, I get a file not found error. Also I took the default menu.lst from WUBI. Here is paste of the relevant stuff:

[codebox]title Ubuntu hardy (development branch), kernel 2.6.24-12-generic
root (hd0,0)/ubuntu/disks
kernel /boot/vmlinuz-2.6.24-12-generic root=UUID=F06C2BB96C2B798C loop=/ubuntu/disks/root.disk ro quiet splash
initrd /boot/initrd.img-2.6.24-12-generic

title Ubuntu hardy (development branch), kernel 2.6.24-12-generic (recovery mode)
root (hd0,0)/ubuntu/disks
kernel /boot/vmlinuz-2.6.24-12-generic root=UUID=F06C2BB96C2B798C loop=/ubuntu/disks/root.disk ro single
initrd /boot/initrd.img-2.6.24-12-generic

title Ubuntu hardy (development branch), memtest86+
root (hd0,0)/ubuntu/disks
kernel /boot/memtest86+.bin[/codebox]

Any help you guys can provide would be greatly appreciated!

Thanks!
Eric

[was_jaclaz]

Hmmm, since I only use grub4dos, and know knothing or almost nothing about Linux/Ubuntu, maybe we can get somewhere together.

First thing, press "c" in the grub4dos menu and enter command mode.

Then enter manually one at the time the lines you have in menu entries, pressing [ENTER] to end the line.

Use [TAB] key for autocompletion, instead of manually entering paths to files.

See WHICH line gives you the file not found.

If the error does not come out, type
boot [ENTER]
to actually trying booting.

jaclaz

[NaraLTD]

Hmmm, since I only use grub4dos, and know knothing or almost nothing about Linux/Ubuntu, maybe we can get somewhere together.

First thing, press "c" in the grub4dos menu and enter command mode.

Then enter manually one at the time the lines you have in menu entries, pressing [ENTER] to end the line.

Use [TAB] key for autocompletion, instead of manually entering paths to files.

See WHICH line gives you the file not found.

If the error does not come out, type
boot [ENTER]
to actually trying booting.

jaclaz

Sorry I didn't get back sooner, but I got busy at work with a few server problems.

At any rate, I did what you suggested and found that my USB device is hd0 when it is the first boot device. I changed the root line to (hd1,0) and it booted up like a champ!

Thanks for your help!

[was_jaclaz]

Yep,
it is advised to ise a "tag file" of some kind, as an example "mytag.tag" putting it in the partition/directory you wisy to set as root , then use:

find --set-root /ubuntu/disks/mytag.tag

kernel		/boot/vmlinuz-2.6.24-12-generic root=UUID=F06C2BB96C2B798C loop=/ubuntu/disks/root.disk ro quiet splash

initrd		/boot/initrd.img-2.6.24-12-generic

this way there will be no problems with "hardcoded paths" such as (hd0,0) or (hd1,0)...

jaclaz

[ktp]

@jaclaz

Excellent tip !