PDA

View Full Version : [ubuntu] grub2 not loading windows on dual boot



adampyre
June 1st, 2010, 11:05 AM
Hello,

I installed 10.04 on my laptop that was running Windows 7.

Grub loads, lets me in Linux fine. Lists my Windows install (and even an old one I removed) but won't load it/boot into it.

I actually had something working right as I edited the menu list directly... but I did and update grub and now Windows won't load.

Because if that, I am %99 certain that I don't need to do any fixes from the Windows install CD, this is something grub isn't doing right. Anyone have any suggestions? I'd be greatful.

Also I should clarify

There are 4 Partitions, 2 are obviously Ubuntu + Swap. My other 2 are for Windows ("Win7Music", has the windows install and Music Partition is just an extra partition to keep seperate)
Boot info script textfile:

Boot Info Script 0.55 dated February 15th, 2010

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

=> Grub 2 is installed in the MBR of /dev/sda and looks on the same drive in
partition #2 for /boot/grub.

sda1: __________________________________________________ _______________________

File system: ntfs
Boot sector type: Grub 2
Boot sector info: Grub 2 is installed in the boot sector of sda1 and
looks at sector 95343462 of the same hard drive for
core.img, but core.img can not be found at this
location. No errors found in the Boot Parameter Block.
Operating System: Windows 7
Boot files/dirs: /bootmgr /boot/BCD /Windows/System32/winload.exe
/grub/core.img

sda2: __________________________________________________ _______________________

File system: ext4
Boot sector type: -
Boot sector info:
Operating System: Ubuntu 10.04 LTS
Boot files/dirs: /boot/grub/grub.cfg /etc/fstab /boot/grub/core.img

sda3: __________________________________________________ _______________________

File system: ntfs
Boot sector type: Grub 2
Boot sector info: Grub 2 is installed in the boot sector of sda3 and
looks at sector 95343462 of the same hard drive for
core.img, but core.img can not be found at this
location. No errors found in the Boot Parameter Block.
Boot file info: BootPart in the file /NST/nst_grub.mbr is trying to
chain load sector #48933990 on boot drive #1
Operating System:
Boot files/dirs: /bootmgr /Boot/BCD

sda4: __________________________________________________ _______________________

File system: swap
Boot sector type: -
Boot sector info:

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

Drive: sda ___________________ __________________________________________________ ___

Disk /dev/sda: 320.1 GB, 320072933376 bytes
255 heads, 63 sectors/track, 38913 cylinders, total 625142448 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 400,886,010 449,819,999 48,933,990 7 HPFS/NTFS
/dev/sda2 2,048 392,579,071 392,577,024 83 Linux
/dev/sda3 * 449,820,000 625,137,344 175,317,345 7 HPFS/NTFS
/dev/sda4 392,579,072 400,885,759 8,306,688 82 Linux swap / Solaris


blkid -c /dev/null: __________________________________________________ __________

Device UUID TYPE LABEL

/dev/sda1 AE069FD5069F9CC1 ntfs Win7Music
/dev/sda2 5270159b-ca61-40d9-806c-f9b7adbb0471 ext4
/dev/sda3 6E9347A073AB6AFB ntfs Music Partition
/dev/sda4 596e6ad3-6341-4e95-b3e7-600e45caba2c swap
/dev/sda: PTTYPE="dos"

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

Device Mount_Point Type Options

/dev/sda2 / ext4 (rw,errors=remount-ro)


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


??GB: grub/core.img

=========================== sda2/boot/grub/grub.cfg: ===========================

#
# 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 ext2
set root='(hd0,2)'
search --no-floppy --fs-uuid --set 5270159b-ca61-40d9-806c-f9b7adbb0471
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 ext2
set root='(hd0,2)'
search --no-floppy --fs-uuid --set 5270159b-ca61-40d9-806c-f9b7adbb0471
set locale_dir=($root)/boot/grub/locale
set lang=en
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 ###
menuentry 'Ubuntu, with Linux 2.6.32-22-generic-pae' --class ubuntu --class gnu-linux --class gnu --class os {
recordfail
insmod ext2
set root='(hd0,2)'
search --no-floppy --fs-uuid --set 5270159b-ca61-40d9-806c-f9b7adbb0471
linux /boot/vmlinuz-2.6.32-22-generic-pae root=UUID=5270159b-ca61-40d9-806c-f9b7adbb0471 ro quiet splash
initrd /boot/initrd.img-2.6.32-22-generic-pae
}
menuentry 'Ubuntu, with Linux 2.6.32-22-generic-pae (recovery mode)' --class ubuntu --class gnu-linux --class gnu --class os {
recordfail
insmod ext2
set root='(hd0,2)'
search --no-floppy --fs-uuid --set 5270159b-ca61-40d9-806c-f9b7adbb0471
echo 'Loading Linux 2.6.32-22-generic-pae ...'
linux /boot/vmlinuz-2.6.32-22-generic-pae root=UUID=5270159b-ca61-40d9-806c-f9b7adbb0471 ro single
echo 'Loading initial ramdisk ...'
initrd /boot/initrd.img-2.6.32-22-generic-pae
}
### END /etc/grub.d/10_linux ###

### BEGIN /etc/grub.d/20_memtest86+ ###
menuentry "Memory test (memtest86+)" {
insmod ext2
set root='(hd0,2)'
search --no-floppy --fs-uuid --set 5270159b-ca61-40d9-806c-f9b7adbb0471
linux16 /boot/memtest86+.bin
}
menuentry "Memory test (memtest86+, serial console 115200)" {
insmod ext2
set root='(hd0,2)'
search --no-floppy --fs-uuid --set 5270159b-ca61-40d9-806c-f9b7adbb0471
linux16 /boot/memtest86+.bin console=ttyS0,115200n8
}
### 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 ae069fd5069f9cc1
chainloader +1
}
menuentry "Windows 7 (loader) (on /dev/sda3)" {
insmod ntfs
set root='(hd0,3)'
search --no-floppy --fs-uuid --set 6e9347a073ab6afb
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 ###

=============================== sda2/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 nodev,noexec,nosuid 0 0
# / was on /dev/sda2 during installation
UUID=5270159b-ca61-40d9-806c-f9b7adbb0471 / ext4 errors=remount-ro 0 1
# swap was on /dev/sda4 during installation
UUID=596e6ad3-6341-4e95-b3e7-600e45caba2c none swap sw 0 0

=================== sda2: Location of files loaded by Grub: ===================


60.2GB: boot/grub/core.img
155.1GB: boot/grub/grub.cfg
60.3GB: boot/initrd.img-2.6.32-22-generic-pae
60.2GB: boot/vmlinuz-2.6.32-22-generic-pae
60.3GB: initrd.img
60.2GB: vmlinuz

wilee-nilee
June 1st, 2010, 11:14 AM
Just a quick look at the script I see that you have loaded grub into the MS partitions. The good thing is that your on the forum about the time when you should be, for this to be looked at by a experienced user who is quite good at this sort of fix. Every thing appears to be there at a quick glance so it is just a matter of applying the right fix. If I was completely sure of one I would tell you, I think I know but am hesitant to in that there are others who are better at this.

ajgreeny
June 1st, 2010, 11:51 AM
I noticed the same thing as wilee-nilee and suspect that is your problem. Normally for as dual boot grub is put on the MBR of one or other of the disks, not into an OS partition. In your case that would be sda, not sda1 and sda3, as you currently have it.

I would, however wait for others to confirm this before you do anything more, but I think you may need to put grub on to the root of the disk with
sudo grub-install /dev/sdathen run
sudo update-grub

You could run that second command in any case right now, just to see if it helps in any way. It can not do any harm.

adampyre
June 1st, 2010, 02:47 PM
Yeah, I had tried to install grub before I reinstalled Linux onto the windows partition itself to see if that helps. I was just trying to do random crap.

I did a sudo update grub and nothing worked....

I think I will wait to see if any grub masters see this...

and what about removing grub2 and using legacy grub? There has been a few year gap for me using linux, but I remember legacy grub being easier to mess with...what is so good about grub2? It just seems more complicated and breaks more......what did grub2 make better? Trying to figure out a solution I am finding little valuable data on this for grub2, I remember it easy being able to find a solution for grub1... argh! /RANT STOP

philinux
June 1st, 2010, 03:12 PM
Yeah, I had tried to install grub before I reinstalled Linux onto the windows partition itself to see if that helps. I was just trying to do random crap.

I did a sudo update grub and nothing worked....

I think I will wait to see if any grub masters see this...

and what about removing grub2 and using legacy grub? There has been a few year gap for me using linux, but I remember legacy grub being easier to mess with...what is so good about grub2? It just seems more complicated and breaks more......what did grub2 make better? Trying to figure out a solution I am finding little valuable data on this for grub2, I remember it easy being able to find a solution for grub1... argh! /RANT STOP

See the General Help forum sticky post #2 to see if this applies to you.

Sethalos
June 1st, 2010, 03:17 PM
This is the link I followed to fix the error I was having, very similiar to your own:

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

Specifically paragraph 16:



sudo apt-get install lilo
sudo lilo -M /dev/sda mbr

adampyre
June 1st, 2010, 04:19 PM
Ok I installed lilo and it said it was ABSOLUTELY NECESSARY I run lilconfig before doing anything else (the second part of your step I assume).... it doesn't like my fstab! I got this message:

WARNING! │
│ │
│ Your /etc/fstab configuration file gives device UUID=5270159b-ca61-40d9-806c-f9b7adbb0471 as the root │
│ filesystem device. This doesn't look to me like an "ordinary" block device. Either your fstab is broken and │
│ you should fix it, or you are using hardware (such as a RAID array) which this simple configuration program │
│ does not handle. │
│ │
│ You should either repair the situation or hand-roll your own /etc/lilo.conf configuration file; you can then │
│ run /usr/sbin/liloconfig again to retry the configuration process. Documentation for LILO can be found in │
│ /usr/share/doc/lilo/.

philinux
June 1st, 2010, 04:22 PM
See post #5.

adampyre
June 1st, 2010, 04:57 PM
Hey Phil,

Just tried it (the testdisk one I assume you were referring to). No change.

Sethalos
June 1st, 2010, 05:11 PM
Ok I installed lilo and it said it was ABSOLUTELY NECESSARY I run lilconfig before doing anything else (the second part of your step I assume).... it doesn't like my fstab! I got this message:

WARNING! │
│ │
│ Your /etc/fstab configuration file gives device UUID=5270159b-ca61-40d9-806c-f9b7adbb0471 as the root │
│ filesystem device. This doesn't look to me like an "ordinary" block device. Either your fstab is broken and │
│ you should fix it, or you are using hardware (such as a RAID array) which this simple configuration program │
│ does not handle. │
│ │
│ You should either repair the situation or hand-roll your own /etc/lilo.conf configuration file; you can then │
│ run /usr/sbin/liloconfig again to retry the configuration process. Documentation for LILO can be found in │
│ /usr/share/doc/lilo/.


Ok..I recieved the same message, however, you simply hit the ok button...when it's complete, you type in the second line to create the mbr.

So step 1: in console type: sudo apt-get install lilo

Then, you'll get that little box come up about running lilconfig (8): just click ok

Step 2 - type in: sudo lilo -M /dev/sda mbr

Once it's complete, reboot, and it should work.

adampyre
June 1st, 2010, 05:28 PM
Hey Sethalos...

Well, I went ahead and tried it and now at boot, I just have a black screen with a blinking cursor. Writing this from within the live CD...

I'm guessing this thread is no longer a "fix grub" thread and hopefully will become an informative how to install grub correctly thread?

:(

adampyre
June 1st, 2010, 05:59 PM
Ok, I followed the instructions on the grub2 wiki for recovering grub. Back in the same place......

acrazyplayer
June 1st, 2010, 05:59 PM
https://help.ubuntu.com/community/Grub2

press control+F in your browser and type in

"Reinstalling from LiveCD" and go to the thrid one, then follow step one. Its pretty easy to follow, just take your time and make sure grub gets installed where you want, e.g. /dev/sda

adampyre
June 1st, 2010, 06:12 PM
acrazyplayer:

That's exactly where I just did to fix the problem already caused by another suggestion in this thread... I am currently back where I was at when I asked my initial question. Thanks though!

SRST Technologies
June 1st, 2010, 06:18 PM
You're back at the same place and not fixed because you're continually installing to a partition and not to the MBR. Also in the file you listed out for us you seem to have a missing file.

adampyre
June 1st, 2010, 06:20 PM
The install that's in the partition is from an old mistake.... for example when I just recovered grub it was to sda....not sda1 or anything like that.... but still... I have no clue what I am doing...


all I know is that I can get into ubuntu fine but I can't get into windows 7. It shows up on my grub menu at boot but just sits there with a white cursor blinking

philinux
June 1st, 2010, 06:23 PM
The install that's in the partition is from an old mistake.... for example when I just recovered grub it was to sda....not sda1 or anything like that.... but still... I have no clue what I am doing...


all I know is that I can get into ubuntu fine but I can't get into windows 7. It shows up on my grub menu at boot but just sits there with a white cursor blinking

Which partition is windows 7 on?

adampyre
June 1st, 2010, 06:25 PM
/dev/sda1

philinux
June 1st, 2010, 07:52 PM
/dev/sda1

Right so in post #1 it shows that sda1 has a grub2 bootloader which is why windows wont boot. So it needs the windows bootloader on sda1.

Just run the boot info script again for a snapshot of whats going on now before any more fiddling.

junoon53
June 2nd, 2010, 04:02 PM
I have the exact same issue, and even I seem to have installed grub2 on the windows partition by mistake. Also the boot info script program is showing the windows partition as boot.


Boot Info Script 0.55 dated February 15th, 2010

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

=> Grub 2 is installed in the MBR of /dev/sda and looks on the same drive in
partition #1 for /boot/grub.
=> No boot loader is installed in the MBR of /dev/sdb

sda1: __________________________________________________ _______________________

File system: ext3
Boot sector type: Grub 2
Boot sector info: Grub 2 is installed in the boot sector of sda1 and
looks at sector 71551120 of the same hard drive for
core.img, but core.img can not be found at this
location.
Operating System: Ubuntu 10.04 LTS
Boot files/dirs: /boot/grub/grub.cfg /etc/fstab /boot/grub/core.img

sda2: __________________________________________________ _______________________

File system: ntfs
Boot sector type: Grub 2
Boot sector info: Grub 2 is installed in the boot sector of sda2 and
looks at sector 71387136 of the same hard drive for
core.img, but core.img can not be found at this
location. No errors found in the Boot Parameter Block.
Operating System: Windows 7
Boot files/dirs: /bootmgr /Boot/BCD /Windows/System32/winload.exe

sda3: __________________________________________________ _______________________

File system: Extended Partition
Boot sector type: -
Boot sector info:

sda5: __________________________________________________ _______________________

File system: swap
Boot sector type: -
Boot sector info:

sdb1: __________________________________________________ _______________________

File system: vfat
Boot sector type: -
Boot sector info: No errors found in the Boot Parameter Block.
Operating System:
Boot files/dirs:

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

Drive: sda ___________________ __________________________________________________ ___

Disk /dev/sda: 320.1 GB, 320072933376 bytes
255 heads, 63 sectors/track, 38913 cylinders, total 625142448 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 2,048 102,783,869 102,781,822 83 Linux
/dev/sda2 * 102,783,870 619,129,034 516,345,165 7 HPFS/NTFS
/dev/sda3 619,130,878 625,141,759 6,010,882 5 Extended
/dev/sda5 619,130,880 625,141,759 6,010,880 82 Linux swap / Solaris


Drive: sdb ___________________ __________________________________________________ ___

Disk /dev/sdb: 320.1 GB, 320072843264 bytes
255 heads, 63 sectors/track, 38913 cylinders, total 625142272 sectors
Units = sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 512 bytes

Partition Boot Start End Size Id System

/dev/sdb1 63 625,137,344 625,137,282 c W95 FAT32 (LBA)


blkid -c /dev/null: __________________________________________________ __________

Device UUID TYPE LABEL

/dev/sda1 b854d985-6350-4951-9ef7-711ebb70a69f ext3
/dev/sda2 70BAC343790AE113 ntfs sda3
/dev/sda3: PTTYPE="dos"
/dev/sda5 5728bc11-a2f3-46e6-a901-fb2dde74d4a9 swap
/dev/sda: PTTYPE="dos"
/dev/sdb1 1007-0D39 vfat Transcend
/dev/sdb: PTTYPE="dos"

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

Device Mount_Point Type Options

/dev/sda1 / ext3 (rw,errors=remount-ro)
/dev/sdb1 /media/Transcend vfat (rw,nosuid,nodev,uhelper=udisks,uid=1000,gid=1000, shortname=mixed,dmask=0077,utf8=1,flush)


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

#
# 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 ext2
set root='(hd0,1)'
search --no-floppy --fs-uuid --set b854d985-6350-4951-9ef7-711ebb70a69f
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 ext2
set root='(hd0,1)'
search --no-floppy --fs-uuid --set b854d985-6350-4951-9ef7-711ebb70a69f
set locale_dir=($root)/boot/grub/locale
set lang=en
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 ###
menuentry 'Ubuntu, with Linux 2.6.32-22-generic' --class ubuntu --class gnu-linux --class gnu --class os {
recordfail
insmod ext2
set root='(hd0,1)'
search --no-floppy --fs-uuid --set b854d985-6350-4951-9ef7-711ebb70a69f
linux /boot/vmlinuz-2.6.32-22-generic root=UUID=b854d985-6350-4951-9ef7-711ebb70a69f ro quiet splash
initrd /boot/initrd.img-2.6.32-22-generic
}
menuentry 'Ubuntu, with Linux 2.6.32-22-generic (recovery mode)' --class ubuntu --class gnu-linux --class gnu --class os {
recordfail
insmod ext2
set root='(hd0,1)'
search --no-floppy --fs-uuid --set b854d985-6350-4951-9ef7-711ebb70a69f
echo 'Loading Linux 2.6.32-22-generic ...'
linux /boot/vmlinuz-2.6.32-22-generic root=UUID=b854d985-6350-4951-9ef7-711ebb70a69f ro single
echo 'Loading initial ramdisk ...'
initrd /boot/initrd.img-2.6.32-22-generic
}
menuentry 'Ubuntu, with Linux 2.6.32-21-generic' --class ubuntu --class gnu-linux --class gnu --class os {
recordfail
insmod ext2
set root='(hd0,1)'
search --no-floppy --fs-uuid --set b854d985-6350-4951-9ef7-711ebb70a69f
linux /boot/vmlinuz-2.6.32-21-generic root=UUID=b854d985-6350-4951-9ef7-711ebb70a69f ro quiet splash
initrd /boot/initrd.img-2.6.32-21-generic
}
menuentry 'Ubuntu, with Linux 2.6.32-21-generic (recovery mode)' --class ubuntu --class gnu-linux --class gnu --class os {
recordfail
insmod ext2
set root='(hd0,1)'
search --no-floppy --fs-uuid --set b854d985-6350-4951-9ef7-711ebb70a69f
echo 'Loading Linux 2.6.32-21-generic ...'
linux /boot/vmlinuz-2.6.32-21-generic root=UUID=b854d985-6350-4951-9ef7-711ebb70a69f ro single
echo 'Loading initial ramdisk ...'
initrd /boot/initrd.img-2.6.32-21-generic
}
### END /etc/grub.d/10_linux ###

### BEGIN /etc/grub.d/20_memtest86+ ###
menuentry "Memory test (memtest86+)" {
insmod ext2
set root='(hd0,1)'
search --no-floppy --fs-uuid --set b854d985-6350-4951-9ef7-711ebb70a69f
linux16 /boot/memtest86+.bin
}
menuentry "Memory test (memtest86+, serial console 115200)" {
insmod ext2
set root='(hd0,1)'
search --no-floppy --fs-uuid --set b854d985-6350-4951-9ef7-711ebb70a69f
linux16 /boot/memtest86+.bin console=ttyS0,115200n8
}
### END /etc/grub.d/20_memtest86+ ###

### BEGIN /etc/grub.d/30_os-prober ###
menuentry "Windows 7 (loader) (on /dev/sda2)" {
insmod ntfs
set root='(hd0,2)'
search --no-floppy --fs-uuid --set 70bac343790ae113
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 ###

=============================== sda1/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 nodev,noexec,nosuid 0 0
# / was on /dev/sda1 during installation
UUID=b854d985-6350-4951-9ef7-711ebb70a69f / ext3 errors=remount-ro 0 1
# swap was on /dev/sda5 during installation
UUID=5728bc11-a2f3-46e6-a901-fb2dde74d4a9 none swap sw 0 0

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


36.5GB: boot/grub/core.img
36.6GB: boot/grub/grub.cfg
36.6GB: boot/initrd.img-2.6.32-21-generic
36.5GB: boot/initrd.img-2.6.32-22-generic
36.6GB: boot/vmlinuz-2.6.32-21-generic
36.6GB: boot/vmlinuz-2.6.32-22-generic
36.5GB: initrd.img
36.6GB: initrd.img.old
36.6GB: vmlinuz
36.6GB: vmlinuz.old

wilee-nilee
June 4th, 2010, 11:28 AM
Assuming this hasn't been fixed I bump.