Windows won't boot after dual boot install

[linusNoob]

I reinstalled Lisa after breaking my wireless because I have no wired access to the net and couldn't download the drivers to fix it. I first selected "something else." Then deleted the partitions manually and reset them just as before. The only differences were:

1.I made all the partitions primary partitions this time
2.Under "Device for boot loader installation" I selected '/dev/sda1/ Windows 7 (loader)' instead of the default '/dev/sda ata st3200....'

I was hoping that this would make windows the default OS after the install. It didn't. Win was still at the bottom of the list except now it won't boot at all. If I try to boot Win7 it just goes black for about 10 secs and comes back to grub. The Partition is still there, I can access the files from nautilus. How do I get windows to boot. It won't boot at all anymore.

[mintybits]

The Mint installer has overwritten your Windows boot sector which is very naughty. You'll need to boot a Windows CD and run boot repairs to fix this, or find some other way to fix the boot sector.

Lots of new users fall foul of this, you are not alone. Unfortunately, the Mint/Ubuntu installer allows people to install Grub to partitions without any warnings and it is usually problematic. Note: always select sda or sdb but never a partition like sda1 or sdb3. And they seem very similar - so why doesn't the installer label the former as "sda MBR" so people don't get so confused? I don't know.

[linusNoob]

Let me clarify my question. How do I fix this without spending any dough? I have access from the mint side to the windows boot folder which contain BCD.logs & bootstat.dat. I can also see the Bootmgr app and bootsector.bak. Can I change the contents of these files or something to make them live again? Reinstalling windows is kinda not an option. My disks are in a shoebox two states away and my girlfriend is a little pissed right now. Someone please help me get nookie again.

[mikecrosoft]

Hello linusNoob. I've read good comments about the usage of rescatux liveCD fot that purpose; you can get it from here http://www.supergrubdisk.org/rescatux/ and here is a related videotutorial http://www.youtube.com/watch?v=SPpPgnfTdE0. Regards!.

NOTE: I haven't tried this and I can't guide you through the process, so first document yourself and use it at your own risk.

[mintybits]

The utility required off the Windows CD is called bootrec.exe. There must be free utilities out there somewhere to do the same thing but I am not aware of any. Make sure when you search that they fix the "boot sector" or "partition boot sector" rather than just the MBR. It is the start of the Windows partition that has been corrupted which is trickier to fix than the MBR. I imagine you could use any Win 7 disk to repair it...if you know anyone who might lend you one.

[HughT]

hi linusNoob,
this is very easily fixed at no expense and with no downloads required. Mint will happily give you the option to boot Windows and to make Windows the default. From a live CD

Code: Select all

sudo mount /dev/sdXY /mnt

replace X and Y with the appropriate drive and partition for Mint boot.

Code: Select all

sudo grub-install --root-directory=/mnt /dev/sdX

note - there's a gap between =/mnt and /dev, and no partition number after sdX.

Re-boot and you should see a list of boot options displayed by the grub screen. Note which line says Windows. Boot into Mint then edit the file /etc/default/grub. You'll have to do this as 'root'. Easiest way is to open the Nautilus file browser as root and browse to /grub.

Code: Select all

gksudo nautilus

then look for the line

GRUB_DEFAULT=0

which is close to the top. The value 0 is for the first OS on the grub screen, value 1 for the second etc, so edit this to the line for Windows and save. Finally

Code: Select all

sudo update-grub

Next time you boot you'll have Windows as the default OS.

[jimwg]

hi linusNoob,
this is very easily fixed at no expense and with no downloads required. Mint will happily give you the option to boot Windows and to make Windows the default. From a live CD

Code: Select all

sudo mount /dev/sdXY /mnt

replace X and Y with the appropriate drive and partition for Mint boot.

Code: Select all

sudo grub-install --root-directory=/mnt /dev/sdX

note - there's a gap between =/mnt and /dev, and no partition number after sdX.

Re-boot and you should see a list of boot options displayed by the grub screen. Note which line says Windows. Boot into Mint then edit the file /etc/default/grub. You'll have to do this as 'root'. Easiest way is to open the Nautilus file browser as root and browse to /grub.

Code: Select all

gksudo nautilus

then look for the line

GRUB_DEFAULT=0

which is close to the top. The value 0 is for the first OS on the grub screen, value 1 for the second etc, so edit this to the line for Windows and save. Finally

Code: Select all

sudo update-grub

Next time you boot you'll have Windows as the default OS.

Hello!

This situation seems to've happened to me! I just finished creating a non-persistence live Mint 9 install on a 8gig flash drive and while it works amazingly, my PC now won't boot-up without the flash drive engaged. All the screen says when I do F12 for normal boot is "error: no such device. grub rescue> "

I'd like to try HughT's solution, but being a newbie I just want to make sure step by step, like
" From a live CD

Code: Select all

sudo mount /dev/sdXY /mnt

. replace X and Y with the appropriate drive and partition for Mint boot"

Please tell me how to tell the appropriate drive and partition!

I agree with mintybits that allowing this kind of thing to happen without giving the user some warning or heads-up is really unforgivable and it might be responsible for turning off more newbies to Linux than we know!

I'm really anxious to learn without runnning ragged all over linx blogs and Google! Thanks for any assist!

Jim in NYC

[HughT]

Hi Jim,
yours is a slightly different problem. linusNoob has Mint installed on the hard drive alongside Windows. My instructions will amend the mbr (master boot record) of that hard drive so that it uses the instructions contained in Mint's grub file (grand unified bootloader). Grub can then be edited as required.
In contrast, you have grub on a flash drive, so early in the boot process, when your pc follows instructions from the mbr, it'll find nothing unless that flash drive is connected. Bottom line - if you've only got windows on your pc, you'll need a Windows answer.
I disagree with mintybits statement "The Mint installer has overwritten your Windows boot sector which is very naughty". Windows would do the same if you installed it on a linux pc. The default option which linusNoob chose to ignore would give a dual booting pc. That option would recognise other operating systems and include them in the boot options. In contrast Windows would not recognise other OSs.
I'm not sure how you've created your non-persistent OS on flash drive, but such a system would not normally even touch the hard drive, let alone write to its mbr. You would normally select to boot from the BIOS screen instead. Indeed much of the purpose of a live USB is that you can test an operating system without affecting your pc.

[mintybits]

The MBR sector and the partition boot sector are two different things. In this case, the PBS, inside the Windows partition, was overwritten when the OP chose /dev/sda1 by mistake. Windows would never overwrite a PBS like that, only an MBR. And only an MBR to fix it to standard, OS-independent, bootstrap code and to set the boot flag to Windows. By contrast, linux will replace the standard MBR code and make it linux specific. This is not ideal and is done in part because of a limitation of linux partition format, but much worse is that the installer will destroy a Windows PBS which it has no business doing at all, particularly as Grub cannot boot Windows without using the Windows PBS. Grub chain-loads Windows rather than booting it directly.

Anyway, my purpose is to clarify. We love linux but we have to take the rough with the smooth sometimes too. And in the OP's situation he has a broken PBS and no reinstalling of grub will help because Grub requires the Windows PBS.

Hope that helps explain the symptoms described.

[jimwg]

The MBR sector and the partition boot sector are two different things....And in the OP's situation he has a broken PBS and no reinstalling of grub will help because Grub requires the Windows PBS

Mintybits, after hearing sky-high over my head explanations and techo-banter on other FAQ Linux forums, you sound like a man who knows what he's talking about. Is there any remedy for my situation, that being, after creating a full (non-persistent) install of Mint-XFEC 9 on a 8gig flash drive and then finding out that my XP machine used to do it won't boot by itself but just pops up a screen that says "Grub Rescue> ? I have no XP CD, though I do have a full XP HD backup created by Macrium and a Mint-9 and Mint-Debian live CD if that will help. I am a newbie just playing it by ear via Linux maven suggestions and surprised I even got this far with a nicely working full install Mint flash drive -- and a XP PC that now I dare not turn off or nor be without the flash drive to boot back to XP again!

Any help or tips would be MUCH appreciated!

Jim in NYC

[wayne128]

Jim,
I suggest you open a new thread, you can copy your situation and question over there.

[cim]

Yesterday I reinstalled Mint (due to some persistent problems I couldn't solve). Unfortunately I made the same error as linusnoob and now have the exact same problem: I can see the different boot options at startup, but when I choose Windows the boot options menu just refreshes. I tried to repair from the Windows cd (with the plan to reinstall Mint again after that). I followed these steps:

1. Insert the windows installation disc and restart the system.
2.Choose " Repair your Computer"
3.The system will search for windows installations. Select your windows OS and click next.
4.In the system Recovery options ..choose command prompt.
5.In the command prompt window, type in "bootrec.exe/fixmbr" without quotes. This will restore Windows as the default OS..but the linux mintOS files are still there on your hard disk.
6. Restart the computer. Now Windows should boot up.

source: http://in.answers.yahoo.com/question/index?qid=20111012062217AAm00Xu

I also used the automatic repair option of Windows, but with the same result: I still can't boot into Windows.

I tried HughT suggestions using the Mint live cd as follows:

Code: Select all

mint@mint ~ $ sudo os-prober
/dev/sda1:Windows 7 (loader):Windows:chain
/dev/sda7: Linux Mint 12 Lisa (12):LinuxMint:linux
mint@mint ~ $ sudo mount /dev/sda7 /mnt
mint@mint ~ $ sudo grub-install --root-directory=/mnt /dev/sda
grub-probe: error: cannot find a device for /boot (is /dev mounted?).
/usr/sbin/grub-setup: warn: Sector 50 is already in use by FlexNet; avoiding it. This software may cause boot or other problems in future. Please ask its authors not to store data in the boot track.
Installation finished. No error reported

(Apparently the installation succeeded despite the error and warning).

After restart I end up with a grub prompt (grub>). I have no idea what to do next

[wayne128]

.
/usr/sbin/grub-setup: warn: Sector 50 is already in use by FlexNet; avoiding it. This software may cause boot or other problems in future. Please ask its authors not to store data in the boot track.
Installation finished. No error reported[/code]

(Apparently the installation succeeded despite the error and warning).

After restart I end up with a grub prompt (grub>). I have no idea what to do next

That Flexnet warning tells you it did not do ( it avoid doing)
to handle this situation, go to this website, get ubuntu boot repair, follow procedure

https://help.ubuntu.com/community/Boot-Repair

hopefully it will clear for you the flexnet issue

[cim]

to handle this situation, go to this website, get ubuntu boot repair, follow procedure

https://help.ubuntu.com/community/Boot-Repair

hopefully it will clear for you the flexnet issue

Thanks for the tip.
The tool helped me at least to get back into Mint. The boot menu also returned, but the Windows option has now completely disappeared. Repairing (again) with the Windows installation cd doesn't make any difference unfortunately.

I wonder if linusnoob had more succes?

[mintybits]

The MBR sector and the partition boot sector are two different things....And in the OP's situation he has a broken PBS and no reinstalling of grub will help because Grub requires the Windows PBS

Mintybits, after hearing sky-high over my head explanations and techo-banter on other FAQ Linux forums, you sound like a man who knows what he's talking about. Is there any remedy for my situation, that being, after creating a full (non-persistent) install of Mint-XFEC 9 on a 8gig flash drive and then finding out that my XP machine used to do it won't boot by itself but just pops up a screen that says "Grub Rescue> ? I have no XP CD, though I do have a full XP HD backup created by Macrium and a Mint-9 and Mint-Debian live CD if that will help. I am a newbie just playing it by ear via Linux maven suggestions and surprised I even got this far with a nicely working full install Mint flash drive -- and a XP PC that now I dare not turn off or nor be without the flash drive to boot back to XP again!

Any help or tips would be MUCH appreciated!

Jim in NYC

Hi Jim. It seems like you fell foul of the installer's default location for Grub being your first hard drive rather than the drive you chose to install Mint to. Mint is on a USB and its Grub replaced the MBR code on your XP drive. Since Grub cannot function beyond the rescue prompt without finding files it needs on the USB you are now unable to boot anything without the USB present. What the installer should have done was to put Grub on the USB MBR and left your XP drive well alone.

The remedy is to install Grub to the USB and reinstate a normal MBR code to the XP disk. Set your bios boot order to USB first and XP disk second.

To install Grub to usb, boot Mint and determine the device name of the usb using "sudo fdisk -lu" or use the Disk Utility program. Then run "sudo dpkg-reconfigure grub-pc".

To restore the MBR on your XP disk boot your XP CD and run the fixmbr utility. If you do not have a CD you can use Mint. Install lilo: "sudo apt-get install lilo". Find the name of your XP disk, probably sda. Do "sudo lilo -M /dev/sda mbr".

[mintybits]

to handle this situation, go to this website, get ubuntu boot repair, follow procedure

https://help.ubuntu.com/community/Boot-Repair

hopefully it will clear for you the flexnet issue

Thanks for the tip.
The tool helped me at least to get back into Mint. The boot menu also returned, but the Windows option has now completely disappeared. Repairing (again) with the Windows installation cd doesn't make any difference unfortunately.

I wonder if linusnoob had more succes?

Try the Windows CD again. You need to fix the partition boot record as well as the MBR. It may be you only fixed the MBR. have a look on microsofts website.

BTW the flexnet warning can be ignored. Grub skips the sectors that flexnet uses. A conflict arises because Grub sticks itself in an area of the disk that is not supposed to be used. Some other programs use parts of this area too from time to time. Strictly speaking, neither should be using that area.

[cim]

Try the Windows CD again. You need to fix the partition boot record as well as the MBR. It may be you only fixed the MBR. have a look on microsofts website.

I tried, but no luck. Windows repair says it didn't find any problems. Btw, I also noticed that the Ubuntu boot-repair tool didn't find a Windows bootloader, which I found strange.

[mintybits]

Try the Windows CD again. You need to fix the partition boot record as well as the MBR. It may be you only fixed the MBR. have a look on microsofts website.

I tried, but no luck. Windows repair says it didn't find any problems. Btw, I also noticed that the Ubuntu boot-repair tool didn't find a Windows bootloader, which I found strange.

Best to download and run http://bootinfoscript.sourceforge.net/ and post the results here inside code tags. This will show whats going on in detail.

[cim]

I'll try that.

Maybe the log of boot-repair may also contain useful information? http://paste.ubuntu.com/999109/

It may have nothing to do with the problem, but this seems strange to me:

Code: Select all

sda5: __________________________________________________________________________

    File system:       ntfs
    Boot sector type:  Windows XP: NTFS
    Boot sector info:  According to the info in the boot sector, sda5 starts
                       at sector 63.

While in the partition info it says sda5 starts at a different sector

[cim]

Best to download and run http://bootinfoscript.sourceforge.net/ and post the results here inside code tags. This will show whats going on in detail.

Here it is:

Code: Select all

                 Boot Info Script 0.61      [1 April 2012]


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

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

sda1: __________________________________________________________________________

    File system:       ntfs
    Boot sector type:  Grub2 (v1.99)
    Boot sector info:  Grub2 (v1.99) is installed in the boot sector of sda1
                       and looks at sector 1458284546 of the same hard drive
                       for core.img. core.img is at this location and looks
                       for (,msdos6)/grub on this drive. No errors found in
                       the Boot Parameter Block.
    Operating System: 
    Boot files:        /bootmgr /Boot/BCD

sda2: __________________________________________________________________________

    File system:       ntfs
    Boot sector type:  Windows Vista/7: NTFS
    Boot sector info:  No errors found in the Boot Parameter Block.
    Operating System:  Windows 7
    Boot files:        /boot.ini /bootmgr /Boot/BCD
                       /Windows/System32/winload.exe /ntldr /NTDETECT.COM
                       /wubildr /wubildr.mbr

sda3: __________________________________________________________________________

    File system:       ntfs
    Boot sector type:  Windows Vista/7: NTFS
    Boot sector info:  No errors found in the Boot Parameter Block.
    Operating System: 
    Boot files:       

sda4: __________________________________________________________________________

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

sda5: __________________________________________________________________________

    File system:       ntfs
    Boot sector type:  Windows XP: NTFS
    Boot sector info:  According to the info in the boot sector, sda5 starts
                       at sector 63.
    Operating System: 
    Boot files:        /ubuntu/disks/root.disk /ubuntu/disks/swap.disk

sda5/Wubi: _____________________________________________________________________

    File system:       ext3
    Boot sector type:  -
    Boot sector info:
    Operating System:  Ubuntu 11.10
    Boot files:        /etc/fstab

sda6: __________________________________________________________________________

    File system:       ext4
    Boot sector type:  -
    Boot sector info:
    Operating System: 
    Boot files:        /grub/grub.cfg /grub/core.img

sda7: __________________________________________________________________________

    File system:       ext4
    Boot sector type:  -
    Boot sector info:
    Operating System:  Linux Mint 12 Lisa
    Boot files:        /etc/fstab

sda8: __________________________________________________________________________

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

sda9: __________________________________________________________________________

    File system:       ext4
    Boot sector type:  -
    Boot sector info:
    Operating System: 
    Boot files:       

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

Drive: sda _____________________________________________________________________

Disk /dev/sda: 1000.2 GB, 1000204886016 bytes
255 heads, 63 sectors/track, 121601 cylinders, total 1953525168 sectors
Units = sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 512 bytes

Partition  Boot  Start Sector    End Sector  # of Sectors  Id System

/dev/sda1    *          2,048       206,847       204,800   7 NTFS / exFAT / HPFS
/dev/sda2             206,848   204,802,047   204,595,200   7 NTFS / exFAT / HPFS
/dev/sda3         204,802,048   409,602,047   204,800,000   7 NTFS / exFAT / HPFS
/dev/sda4         409,615,981 1,534,932,991 1,125,317,011   f W95 Extended (LBA)
/dev/sda5         409,615,983 1,458,172,799 1,048,556,817   7 NTFS / exFAT / HPFS
/dev/sda6       1,458,173,952 1,458,759,679       585,728  83 Linux
/dev/sda7       1,458,761,728 1,478,291,455    19,529,728  83 Linux
/dev/sda8       1,478,293,504 1,486,104,575     7,811,072  82 Linux swap / Solaris
/dev/sda9       1,486,106,624 1,534,932,991    48,826,368  83 Linux


"blkid" output: ________________________________________________________________

Device           UUID                                   TYPE       LABEL

/dev/sda1        FAE4D44FE4D4102D                       ntfs       System Reserved
/dev/sda2        0002BDE202BDDD3A                       ntfs       win
/dev/sda3        CEEED643EED6238D                       ntfs       docs
/dev/sda5        01CD157E4A827A60                       ntfs       storage
/dev/sda6        911e131a-5d13-4b4d-91c4-a52d5e2aba5d   ext4       
/dev/sda7        f879f352-6cd3-4547-b4bb-8332465d9a38   ext4       
/dev/sda8        93d8a7e0-fb47-4b28-9d7e-0d08378838c2   swap       
/dev/sda9        ace816f7-ef53-4465-bf52-3ea72d26206f   ext4       

================================ Mount points: =================================

Device           Mount_Point              Type       Options

/dev/sda6        /boot                    ext4       (rw,commit=0)
/dev/sda7        /                        ext4       (rw,errors=remount-ro,commit=0)
/dev/sda9        /home                    ext4       (rw,commit=0)


================================ sda2/boot.ini: ================================

--------------------------------------------------------------------------------
[boot loader]
timeout=10
default=multi(0)disk(0)rdisk(0)partition(2)\WINDOWS
[operating systems]
multi(0)disk(0)rdisk(0)partition(2)\WINDOWS="Windows" /noexecute=optin /fastdetect
--------------------------------------------------------------------------------

============================= sda5/Wubi/etc/fstab: =============================

--------------------------------------------------------------------------------
# UNCONFIGURED FSTAB FOR BASE SYSTEM
--------------------------------------------------------------------------------

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

           GiB - GB             File                                 Fragment(s)

   1.296074867 = 1.391649792    boot/initrd.img-3.0.0-12-generic              40
   1.301356316 = 1.397320704    boot/vmlinuz-3.0.0-12-generic                 20
   0.030629158 = 0.032887808    initrd.img                                     2
   1.301356316 = 1.397320704    vmlinuz                                       20

============================= sda6/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
}

function load_video {
  insmod vbe
  insmod vga
  insmod video_bochs
  insmod video_cirrus
}

insmod part_msdos
insmod ext2
set root='(hd0,msdos7)'
search --no-floppy --fs-uuid --set=root f879f352-6cd3-4547-b4bb-8332465d9a38
if loadfont /usr/share/grub/unicode.pf2 ; then
  set gfxmode=auto
  load_video
  insmod gfxterm
  insmod part_msdos
  insmod ext2
  set root='(hd0,msdos6)'
  search --no-floppy --fs-uuid --set=root 911e131a-5d13-4b4d-91c4-a52d5e2aba5d
  set locale_dir=($root)/grub/locale
  set lang=en_US
  insmod gettext
fi
terminal_output gfxterm
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
if background_color 0,0,0; then
  clear
fi
### END /etc/grub.d/05_debian_theme ###

### BEGIN /etc/grub.d/06_mint_theme ###
set menu_color_normal=white/black
set menu_color_highlight=white/light-gray
### END /etc/grub.d/06_mint_theme ###

### BEGIN /etc/grub.d/10_linux ###
if [ ${recordfail} != 1 ]; then
  if [ -e ${prefix}/gfxblacklist.txt ]; then
    if hwmatch ${prefix}/gfxblacklist.txt 3; then
      if [ ${match} = 0 ]; then
        set linux_gfx_mode=keep
      else
        set linux_gfx_mode=text
      fi
    else
      set linux_gfx_mode=text
    fi
  else
    set linux_gfx_mode=keep
  fi
else
  set linux_gfx_mode=text
fi
export linux_gfx_mode
if [ "$linux_gfx_mode" != "text" ]; then load_video; fi
menuentry 'Linux Mint 12 64-bit, 3.0.0-12-generic (/dev/sda6)' --class linuxmint --class gnu-linux --class gnu --class os {
   recordfail
   set gfxpayload=$linux_gfx_mode
   insmod gzio
   insmod part_msdos
   insmod ext2
   set root='(hd0,msdos6)'
   search --no-floppy --fs-uuid --set=root 911e131a-5d13-4b4d-91c4-a52d5e2aba5d
   linux   /vmlinuz-3.0.0-12-generic root=UUID=f879f352-6cd3-4547-b4bb-8332465d9a38 ro   quiet splash vt.handoff=7
   initrd   /initrd.img-3.0.0-12-generic
}
menuentry 'Linux Mint 12 64-bit, 3.0.0-12-generic (/dev/sda6) -- recovery mode' --class linuxmint --class gnu-linux --class gnu --class os {
   recordfail
   insmod gzio
   insmod part_msdos
   insmod ext2
   set root='(hd0,msdos6)'
   search --no-floppy --fs-uuid --set=root 911e131a-5d13-4b4d-91c4-a52d5e2aba5d
   echo   'Loading Linux 3.0.0-12-generic ...'
   linux   /vmlinuz-3.0.0-12-generic root=UUID=f879f352-6cd3-4547-b4bb-8332465d9a38 ro recovery nomodeset
   echo   'Loading initial ramdisk ...'
   initrd   /initrd.img-3.0.0-12-generic
}
### END /etc/grub.d/10_linux ###

### BEGIN /etc/grub.d/10_lupin ###
### END /etc/grub.d/10_lupin ###

### BEGIN /etc/grub.d/20_linux_xen ###
### END /etc/grub.d/20_linux_xen ###

### BEGIN /etc/grub.d/20_memtest86+ ###
menuentry "Memory test (memtest86+)" {
   insmod part_msdos
   insmod ext2
   set root='(hd0,msdos6)'
   search --no-floppy --fs-uuid --set=root 911e131a-5d13-4b4d-91c4-a52d5e2aba5d
   linux16   /memtest86+.bin
}
menuentry "Memory test (memtest86+, serial console 115200)" {
   insmod part_msdos
   insmod ext2
   set root='(hd0,msdos6)'
   search --no-floppy --fs-uuid --set=root 911e131a-5d13-4b4d-91c4-a52d5e2aba5d
   linux16   /memtest86+.bin console=ttyS0,115200n8
}
### END /etc/grub.d/20_memtest86+ ###

### BEGIN /etc/grub.d/30_os-prober ###
### 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 ###
--------------------------------------------------------------------------------

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

           GiB - GB             File                                 Fragment(s)

 695.329919815 = 746.604816384  grub/core.img                                  1
 695.457054138 = 746.741325824  grub/grub.cfg                                  1
 695.342152596 = 746.617951232  initrd.img-3.0.0-12-generic                    2
 695.349065781 = 746.625374208  vmlinuz-3.0.0-12-generic                       1

=============================== sda7/etc/fstab: ================================

--------------------------------------------------------------------------------
# /etc/fstab: static file system information.
#
# Use 'blkid' 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/sda7 during installation
UUID=f879f352-6cd3-4547-b4bb-8332465d9a38 /               ext4    errors=remount-ro 0       1
# /boot was on /dev/sda6 during installation
#UUID=911e131a-5d13-4b4d-91c4-a52d5e2aba5d /boot           ext4    defaults        0       2
# /home was on /dev/sda9 during installation
UUID=ace816f7-ef53-4465-bf52-3ea72d26206f /home           ext4    defaults        0       2
# swap was on /dev/sda8 during installation
UUID=93d8a7e0-fb47-4b28-9d7e-0d08378838c2 none            swap    sw              0       0
/dev/fd0        /media/floppy0  auto    rw,user,noauto,exec,utf8 0       0
UUID=911e131a-5d13-4b4d-91c4-a52d5e2aba5d   /boot   ext4   defaults   0   1
--------------------------------------------------------------------------------

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

           GiB - GB             File                                 Fragment(s)

 695.622426033 = 746.918892544  initrd.img                                     2
 695.629339218 = 746.926315520  vmlinuz                                        1

=============================== StdErr Messages: ===============================

xz: (stdin): Compressed data is corrupt