GNU GRUB ver.1.97beta - search --no-floppy

gburdine · 11-28-2009, 02:31 PM

I am forced to edit with grub and remove the following line just to be able to boot:

search --no-floppy --fs-uuid --set dd1f742f-5fd9-4cdb-b206-036f5f3e7\63d

leaving ubuntu 9.10 cdrom is drive and booting will allow me to edit this file and ctrl-x to successfully boot.

I think there is a way to permanently edit this file and save it. I have tried to to place an '#' before search. But this had no affect.

thnx

aus9 · 11-28-2009, 08:09 PM

you have a slash \ and so its the wrong length.

post the output of this command pls

Code:

ls -al /dev/disk/by-uuid/

2) look at /boot/grub/grub.cfg

how many mentions of bad uuid are there?

post this file into a code box pls.

3) ubuntu recently moved to uuids in fstab....that may be the culprit so post the output of that file as well pls

Leaping ahead....fix your fstab and run "sudo update-grub"
might fix it...but I do not use that distro.

so lets see what the results are so others can comment pls

creagru · 12-09-2009, 05:20 PM

I also had the same issue.
output of command line ls.... is:
total 0
drwxr-xr-x 2 root root 80 2009-12-09 21:58 .
drwxr-xr-x 5 root root 100 2009-12-09 21:58 ..
lrwxrwxrwx 1 root root 10 2009-12-09 21:58 112adb9f-7728-435e-9a91-f9ababffc2cc -> ../../sda1
lrwxrwxrwx 1 root root 10 2009-12-09 21:58 f2db9c54-5b3b-4489-9c1a-e4413b8347d8 -> ../../sda5

uuid is mentioned 9 times in the /boot/grub/grub.cfg file

grateful for assistance.

linus72 · 12-09-2009, 06:07 PM

you may boot puppy or partedmagic and edit grub.cfg manually

also, try running

blkid

as root with all partitions mounted

I have to manually edit my grub.cfg as I must use the cheatcode "xforcevesa" in my kernel line
or my screen will "crack" and freeze

aus9 · 12-09-2009, 07:20 PM

creagru

Feel free to use any tip from linus72.

Editting grub.cfg is frowned upon as when you update kernel or update grub2....the scripts run ..update-grub and so you will continue to have unresolved issues.

I suspect the issue is with UUID and Ubuntu recently changing to it.....but I must wait for the OP to reply.

linus72

I suggest you add your cheatcode to /etc/default/grub and run update-grub....this should resolve your issue at least.

linus72 · 12-09-2009, 08:08 PM

i'll try it aus9

creagru · 12-10-2009, 03:57 PM

linus72

sorry yr tipsalittle to advanced for me as only just installed ubuntu linux last week for first time so just learning.
how do i run blkid? can you explain a little more abt what to do.

ta

aus9 · 12-10-2009, 06:30 PM

hi

I have just realised OP has not replied for 2 weeks. so while we wait...its over to try creagru

creagru

1) Did you have to edit at grub boot the similar line with different UUID like gburdine

If so, you are more advanced than most newbies.

2) Assuming you can get into your system....I would like you to run some commands and post the results into a code box.

3) so post these files please..into separate boxes

/boot/grub/cfg
/etc/fstab

and run this command, as a non-root user.. post into a separate box

Code:

ls -al /dev/disk/by-uuid/

---------

If you can not get into your system...please say so.

Then run your distro as a live cd.

Your distro may mount = (make readable) partitions under /media or under /mnt...so just read /etc/fstab as maybe /mnt/etc/fstab

If your distro does not AUTOMATICALLY mount your hard drive partitions we can mount them manually

open a terminal and do this

Code:

sudo mkdir /z
mount /dev/sda1 /z

where I assume sda1 is your first linux partition and is where you installed linux.

if you are not sure....run gparted and look at your partitons.
For example if you are dual booting...it may be /dev/sda5?

creagru · 12-11-2009, 04:21 PM

Aus9

1) Yes I edit the grub boot and can run the system fine. in the grub boot i edit out the line "search --no-floppy --fs-uuid --set.." same as gburdine and cntrl x and the os loads normally.
2)noted
3)aa)i cannot find these files /boot/grub/cfg & /etc/fstab need a little more newbie assistance.

bb)
the result to run ls -al /dev/disk/by-uuid/ is:
total 0
drwxr-xr-x 2 root root 80 2009-12-11 20:46 .
drwxr-xr-x 5 root root 100 2009-12-11 20:46 ..
lrwxrwxrwx 1 root root 10 2009-12-11 20:46 112adb9f-7728-435e-9a91-f9ababffc2cc -> ../../sda1
lrwxrwxrwx 1 root root 10 2009-12-11 20:46 f2db9c54-5b3b-4489-9c1a-e4413b8347d8 -> ../../sda5

Ta

aus9 · 12-11-2009, 07:28 PM

ok

1) To reply with an answer in a code box....the easiest is to click on the GO ADVANCED button at bottom of reply....Now when you look at the icons just above your text....you will see a # symbol which is the icon for the code box.

click it one and it creates 2 "boxes" joined together ....I can't display them correctly but are like this
[][] with CODE (and) /CODE inside those boxes.

you can type them manually as well.

But you separate them to paste your test so in lower case to try and display it...change to capitals

[code
paste text
[/code

end square bracket left off

hmm lower case works as well

2) OK its good to know you can login.

Just use your file manager to navigate to those files please....OOPS I made a typo try

/boot/grub/grub.cfg

and

/etc/fstab

click on each and your text editor should open them.

I then use keyboard shortcuts but you can use pulldown menu to copy
then paste into code boxes.

shortcut keys ....
select all = CONTROL key and a
copy = CONTROL key and c
paste = CONTROL key and v

good luck

Bratmon · 12-11-2009, 07:59 PM

To make the code tag work, type
[code] Your text [/code]

creagru · 12-12-2009, 02:46 AM

Hi aus9,

ta for the tips have insterted the /boot/grub/grub.cfg (i think)
but still cannot locate any etc/fstab

Code:

#
# 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 /boot/grub/grubenv ]; then
  have_grubenv=true
  load_env
fi
set default="0"
if [ ${prev_saved_entry} ]; then
  saved_entry=${prev_saved_entry}
  save_env saved_entry
  prev_saved_entry=
  save_env prev_saved_entry
fi
insmod ext2
set root=(hd0,1)
search --no-floppy --fs-uuid --set 112adb9f-7728-435e-9a91-f9ababffc2cc
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
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/white
### END /etc/grub.d/05_debian_theme ###

### BEGIN /etc/grub.d/10_linux ###
menuentry "Ubuntu, Linux 2.6.31-16-generic" {
        recordfail=1
        if [ -n ${have_grubenv} ]; then save_env recordfail; fi
	set quiet=1
	insmod ext2
	set root=(hd0,1)
	search --no-floppy --fs-uuid --set 112adb9f-7728-435e-9a91-f9ababffc2cc
	linux	/boot/vmlinuz-2.6.31-16-generic root=UUID=112adb9f-7728-435e-9a91-f9ababffc2cc ro   quiet splash
	initrd	/boot/initrd.img-2.6.31-16-generic
}
menuentry "Ubuntu, Linux 2.6.31-16-generic (recovery mode)" {
        recordfail=1
        if [ -n ${have_grubenv} ]; then save_env recordfail; fi
	insmod ext2
	set root=(hd0,1)
	search --no-floppy --fs-uuid --set 112adb9f-7728-435e-9a91-f9ababffc2cc
	linux	/boot/vmlinuz-2.6.31-16-generic root=UUID=112adb9f-7728-435e-9a91-f9ababffc2cc ro single 
	initrd	/boot/initrd.img-2.6.31-16-generic
}
menuentry "Ubuntu, Linux 2.6.31-14-generic" {
        recordfail=1
        if [ -n ${have_grubenv} ]; then save_env recordfail; fi
	set quiet=1
	insmod ext2
	set root=(hd0,1)
	search --no-floppy --fs-uuid --set 112adb9f-7728-435e-9a91-f9ababffc2cc
	linux	/boot/vmlinuz-2.6.31-14-generic root=UUID=112adb9f-7728-435e-9a91-f9ababffc2cc ro   quiet splash
	initrd	/boot/initrd.img-2.6.31-14-generic
}
menuentry "Ubuntu, Linux 2.6.31-14-generic (recovery mode)" {
        recordfail=1
        if [ -n ${have_grubenv} ]; then save_env recordfail; fi
	insmod ext2
	set root=(hd0,1)
	search --no-floppy --fs-uuid --set 112adb9f-7728-435e-9a91-f9ababffc2cc
	linux	/boot/vmlinuz-2.6.31-14-generic root=UUID=112adb9f-7728-435e-9a91-f9ababffc2cc ro single 
	initrd	/boot/initrd.img-2.6.31-14-generic
}
### END /etc/grub.d/10_linux ###

### BEGIN /etc/grub.d/20_memtest86+ ###
menuentry "Memory test (memtest86+)" {
	linux16	/boot/memtest86+.bin
}
menuentry "Memory test (memtest86+, serial console 115200)" {
	linux16	/boot/memtest86+.bin console=ttyS0,115200n8
}
### END /etc/grub.d/20_memtest86+ ###

### BEGIN /etc/grub.d/30_os-prober ###
if [ ${timeout} != -1 ]; then
  if keystatus; then
    if keystatus --shift; then
      set timeout=-1
    else
      set timeout=0
    fi
  else
    if sleep --interruptible 3 ; then
      set timeout=0
    fi
  fi
fi
### 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 ###

aus9 · 12-12-2009, 05:41 AM

its folder /etc....like /boot

then its a file directly under /etc

creagru · 12-13-2009, 01:02 PM

aus9,
sorry, user error,

Code:

 
# /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
# / was on /dev/sda1 during installation
UUID=112adb9f-7728-435e-9a91-f9ababffc2cc /               ext4    errors=remount-ro 0       1
# swap was on /dev/sda5 during installation
UUID=f2db9c54-5b3b-4489-9c1a-e4413b8347d8 none            swap    sw              0       0
/dev/scd0       /media/cdrom0   udf,iso9660 user,noauto,exec,utf8 0       0

aus9 · 12-13-2009, 08:11 PM

hi

ok you have ext4.

http://grub.enbug.org/CurrentStatus
under Supported filesystems....ext4 has only just been added and I am not sure...as I have not built mine on ext4 that you have the correct grub2 to handle ext4.

2) If I am right.....reformat as ext3....then you should not need to edit your grub2 command line.