View Single Post
Old 20. Aug 2011, 04:51 PM   #23 (permalink)
crank
Senior Member
 
crank's Avatar
 
Join Date: Oct 2010
Location: Central Texas aka Hell
Posts: 160
Default Useful tool for the boot-impaired

I hope this is the right place for this, after searching around I found no mention of this, so I thought I would throw it out here.

If you are no stranger to facing a machine with multiple systems on it none of which you can get to boot properly, 'Boot-Repair' might be your answer. From their Ubuntu page:

Code:
Boot-Repair is a small graphical tool to repair frequent boot problems.

Easy-to-use (repair in 1 click ! )
Can recover access to one or several operating systems
Options to reinstall GRUB2 boot-loader easily (OS by default, purge, unhide, kernel options..)
Create a Boot-Info-Script summary in 1 click


It is that last item that has proven the most help to me so far, especially if you have the same problem that plagues me often, trying to make sure you are addressing the right disk in linux. I have on 1 PC a number of identical disks, plus use a CD/DVD and/or USB drive often, on top of that there are at least 3 separate controllers for disks, the normal SATA, the RAID SATA [which for some reason not yet examined decided this old 80 Gb SATA drive I hooked up for testing purposes was by itself RAID], the USB3.

Maybe it's just that I am dense/obtuse, but most of the time figuring out who is sda or sdg etc is problematic to say the least. I can't see what else besides some random process somewhere decides the resulting order. This might cause a problem when you, say, wipe a partition or disk. "Oh, darn, that was my Windows"

So, if SuperGrub2Disk is the only way you can get boot, this guy might be able to help.

Some example output, posted to a web page so you can look at with your lappy while still elbows deep operating on the desktop:

Code:
sdd1: __________________________________________________________________________

    File system:       ntfs
    Boot sector <span class="nb">type</span>:  Windows XP
    Boot sector info:   No errors found in the Boot Parameter Block.
    Operating System:  
    Boot files:        

sde1: __________________________________________________________________________

    File system:       ntfs
    Boot sector <span class="nb">type</span>:  Windows Vista/7
    Boot sector info:   No errors found in the Boot Parameter Block.
    Operating System:  
    Boot files:        

sdf1: __________________________________________________________________________

    File system:       vfat
    Boot sector <span class="nb">type</span>:  FAT32
    Boot sector info:   According to the info in the boot sector, sdf1 starts 
                       at sector 0. But according to the info from fdisk, 
                       sdf1 starts at sector 63.
    Operating System:  
    Boot files:        

sdf2: __________________________________________________________________________

    File system:       ntfs
    Boot sector <span class="nb">type</span>:  Windows Vista/7
    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
Code:
 => Grub2 (v1.99) is installed in the MBR of /dev/sda and looks at sector 1 of 
    the same hard drive for core.img. core.img is at this location and uses an 
    embedded config file:
    
    ---------------------------------------------------------------------------
    search.fs_uuid dc695ca0-fde3-4515-8e01-f443946661c2 root 
    set 
    prefix=($root)/boot/grub---------------------------------------------------
    -----------------------------.
 => Grub2 (v1.99) is installed in the MBR of /dev/sdb and looks at sector 1 of 
    the same hard drive for core.img. core.img is at this location and uses an 
    embedded config file:
    
    ---------------------------------------------------------------------------
    search.fs_uuid dc695ca0-fde3-4515-8e01-f443946661c2 root 
    set 
    prefix=($root)/boot/grub---------------------------------------------------
    -----------------------------.
 => No boot loader is installed in the MBR of /dev/sdc.
 => Grub2 (v1.99) is installed in the MBR of /dev/sdd and looks at sector 1 of 
    the same hard drive for core.img. core.img is at this location and uses an 
    embedded config file:
    
    ---------------------------------------------------------------------------
    search.fs_uuid dc695ca0-fde3-4515-8e01-f443946661c2 root 
    set 
    prefix=($root)/boot/grub---------------------------------------------------
    -----------------------------.
 => Grub2 (v1.99) is installed in the MBR of /dev/sde and looks at sector 1 of 
    the same hard drive for core.img. core.img is at this location and uses an 
    embedded config file:
[
Code:
Device           UUID                                   TYPE       LABEL

/dev/sda1        0A6C-B8ED                              vfat       WONSHARE_RE
/dev/sdb2        AE423F31423EFDA1                       ntfs       New Volume
/dev/sdb5        01CBDC74DF90B1B0                       ntfs       HitachiCentralArchive
/dev/sdc1        F464107664103E34                       ntfs       Sto_annex
/dev/sdd1        01CBB1905DC500F0                       ntfs       rog_data
/dev/sde1        80C46776C4676CFA                       ntfs       caviar_3
/dev/sdf1        0426-15AA                              vfat       
/dev/sdf2        7A04495D04491E0F                       ntfs       rog
/dev/sdf5        dc695ca0-fde3-4515-8e01-f443946661c2   ext4       
/dev/sdh1        6CB4-26DB                              vfat       XP_PRO
/dev/sdh2        1810a79f-2a9b-4ec2-8e4a-f687a034cbbb   ext3       Kubuntu-11.04
That last is kinda embarrassing and explains the tic I've developed of late.

Very handy, and it can actually fix some boot problems, sometimes.
__________________
you must be joking, oh man you must be joking
crank is offline   Reply With Quote