Modifying grub on usbstick kills boot. [Solved]

[Village Idiot]

Created an .iso of my corei7 system using mylivecd.
Created live-usb using lusbc
Boots up on a asus eee-pc 1000H. All I wanted to do was watch the bootup text. Here is the original menu.lst file:

Code: [Select]

timeout 10
color black/cyan yellow/cyan
gfxmenu (hd0,0)/boot/gfxmenu
default 0

title   LXDE
kernel (hd0,0)/LXDE_0/vmlinuz livecd=LXDE_0 fromusb root=UUID=ea6542cb-e2c1-460c-a23e-55cfee827b36 acpi=on vga=791 splash=silent
initrd (hd0,0)/LXDE_0/initrd.gz
 
title  LXDE with Persistence
kernel (hd0,0)/LXDE_0/vmlinuz livecd=LXDE_0 fromusb root=UUID=ea6542cb-e2c1-460c-a23e-55cfee827b36 acpi=on fstab=rw,noauto vga=791 changes_dev=UUID=ea6542cb-e2c1-460c-a23e-55cfee827b36 splash=silent
initrd (hd0,0)/LXDE_0/initrd.gz

It was working/booting fine previously. All I did was remove "splash=silent" from the first menu entry and save the file. Now the eeepc says it can't find the loop image and drops into a limited shell. Funny thing is I can interrupt grub and edit the line and it works fine booting verbose. I only wanted to make it do it by default.

Touchy. What have I done wrong? and how can I fix it?

[Was_Just19]

Unless there was some corruption of the file when you saved it, I cannot think of a reason.

Omitting the splash= boot code is legitimate.

Also changing it to  splash=verbose   is equally effective.

As I said ......  it sounds like there was some corruption of the file, based on what you posted above.

Try it again .......

[Village Idiot]

Unless there was some corruption of the file when you saved it, I cannot think of a reason.

Omitting the splash= boot code is legitimate.

Also changing it to  splash=verbose   is equally effective.

As I said ......  it sounds like there was some corruption of the file, based on what you posted above.

Try it again .......

I re-did the usbstick. And carefully booted/modified/booted with success.

Seems I was pulling my stick out too early!! 

Turns out I need to wait a few -extra- moments for the file system to write the data to the stick. I believe this and then a direct umount /dev/sdc1 from the CL. Then I can remove the stick.

Thank you. 

[Was_Just19]

Yes the USB device needs to be properly unmounted/ejected before extraction else changes to it will not be written correctly.

Your file manager should also have the option.

Glad you got it sorted