Author Topic: [SOLVED] BackBox grub loader detects Windows 7 but would not boot it  (Read 4273 times)

Halnex

  • Guest
I have 2 HDDS.

1: SSD 240GB on which Windows 7 is installed
2: HDD 1TB for storage that I shrinked and created a separate 100GB partition from with swap.

I installed BackBox 4 on the 100GB parition while leaving the SSD and windows intact.

I installed BB's bootloader on Windows 7 recovery partition (I don't know if that was the correct choice)

Now on the boot menu, I get "Windows 7" option but when I select it, it just reloads the boot menu and asks me to choose again.
It won't let me into Windows.

/dev/sda4/: BackBox 4
/dev/sda3/: Swap
/dev/sda2/ Storage
-
/dev/sdb1/: Windows

I edit grub.cfg and replaced
Code: [Select]
menuentry 'Windows 7 (loader) (on /dev/sda1)' --class windows -
With /dev/sdb1/ and ran --sudo update-grub and restarted.

Still the same error.

I then tried changing the hd0 to hd3, still not working.

What could be the problem?

« Last Edit: January 30, 2015, 09:23:26 AM by drego85 »



Halnex

  • Guest
Reply #1 on: January 12, 2015, 03:32:48 PM
I also tried adjusting the "hd0" to whatever number my HD has.

I tried from 0 to 3, none worked.

Code: [Select]
menuentry 'Windows 7 (loader) (on /dev/sdb1)' --class windows --class os $menuentry_id_option 'osprober-chain-0886FE9886FE858A' {
        insmod part_msdos
        insmod ntfs
        set root='hd0,msdos1'
        if [ x$feature_platform_search_hint = xy ]; then
          search --no-floppy --fs-uuid --set=root --hint-bios=hd0,msdos1 --hint-efi=hd0,msdos1 --hint-baremetal=ahci0,msdos1  0886FE9886FE858A
        else
          search --no-floppy --fs-uuid --set=root 0886FE9886FE858A
        fi
        parttool ${root} hidden-
        chainloader +1
}

On windows partition it says "hd0.msdos1" while on the rest it says "msdos4"
Is it somehow related?



b4d_bl0ck

  • Sr. Member
  • ****
  • Posts: 285
    • View Profile
Reply #2 on: January 12, 2015, 04:19:28 PM
Quote
I installed BB's bootloader on Windows 7 recovery partition (I don't know if that was the correct choice)
What's this?

I never had a multiple hard drive configuration, but afaik you need to install Grub to the first disk used to boot.

Bye.

bool secure = check_paranoia() ? true : false;


Halnex

  • Guest
Reply #3 on: January 12, 2015, 04:39:28 PM
Yes. I made a huge mistake by doing this.
While installing BackBox, I selected "Something Else" and did not go with the default "Installa BB alongside Windows"
And I didn't pay attention to "Install Grub loader on this partition" right underneath and it had selected "Windows 7 recovery partition" by default

Now I need to correct it. And learn in the process.

EDIT: this is the ouput of "fdisk -l"

Code: [Select]
root@Base:/# fdisk -l

Disk /dev/sda: 2000.4 GB, 2000398934016 bytes
255 heads, 63 sectors/track, 243201 cylinders, total 3907029168 sectors
Units = sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 4096 bytes
I/O size (minimum/optimal): 4096 bytes / 4096 bytes
Disk identifier: 0x0e092a46

   Device Boot      Start         End      Blocks   Id  System
/dev/sda1   *        2048      206847      102400    7  HPFS/NTFS/exFAT
/dev/sda2          206848  3679698943  1839746048    7  HPFS/NTFS/exFAT
/dev/sda3      3679700990  3698130678     9214844+   f  W95 Ext'd (LBA)
Partition 3 does not start on physical sector boundary.
/dev/sda4      3698130944  3907025475   104447266   83  Linux
/dev/sda5      3679700992  3698130678     9214843+  82  Linux swap / Solaris

Disk /dev/sdb: 240.1 GB, 240057409536 bytes
255 heads, 63 sectors/track, 29185 cylinders, total 468862128 sectors
Units = sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 512 bytes / 512 bytes
Disk identifier: 0x6a33ae40

   Device Boot      Start         End      Blocks   Id  System
/dev/sdb1            2048   468858879   234428416    7  HPFS/NTFS/exFAT

and this is the output of "blkid"
Code: [Select]
root@Base:/# blkid
/dev/sda1: LABEL="System Reserved" UUID="0886FE9886FE858A" TYPE="ntfs"
/dev/sda2: UUID="948CA6D08CA6AC64" TYPE="ntfs"
/dev/sda4: UUID="3b8e1432-345b-4166-af34-90c550313950" TYPE="ext4"
/dev/sdb1: LABEL="Windows" UUID="7C626A1E6269DE00" TYPE="ntfs"
« Last Edit: January 12, 2015, 05:39:20 PM by Halnex »



Halnex

  • Guest
Reply #4 on: January 14, 2015, 03:26:40 AM
I've been running in circles for 2 days when all I had to do was install boot-repair and let it do its magic.

Windows 7 is accessible again.