I have two SSDs, one is for my Windows 7, and one is for testing and tweaking it (like installing Linux, or other operating systems...).

I've already installed Windows 7 on the first SSD, and I tried to install Debian distribution on the second SSD, the installation was successful.

But the problem is that I installed something called boot loader into first SSD (which Windows 7 is installed), so if I run second SSD, nothing happens and if I run the first SSD, automatically Debian boot loader runs, and what thing fundamentally makes me annoying is that there is no option for Windows, just for Debian. (I thought I can use both of the choices if I install the boot loader into any SSD.)

If I open the SSD which Win installed, I can see those files and folders.

[Folder] Boot
[Folder] Documents and Settings
[Folder] Intel
[Folder] Perflogs
[Folder] ProgramData
[Folder] Program files
[Folder] Program files (x86)
[Folder] Recovery
[Folder] $Recycle.Bin
[Folder] System Volume Information
[Folder] Users
[Folder] Windows
[File] bootmgr
[File] BOOTSECT.BAK
[File] hiberfil.sys
[File] pagefile.sys

I think those all folders & files have relationships to Windows OS, but actually I don't know. (I just googled it.)

Can I change the directory of the boot loader or delete it? What can I do?

  • Your title makes no sense at all. – Anthon May 28 '16 at 11:28
up vote 9 down vote accepted

It depends on which boot-loader was installed. If its a standard Debian install it should be GRUB2.

Boot the computer with all disks containing bootable installations attached and powered.

you need to open Root Terminal application to open a terminal as root, then enter these commands:

apt-get update
apt-get install os-prober

if os-prober package is already installed, apt will let you know, without doing any changes to the system.

Then edit /etc/default/grub and make sure you have a line like

GRUB_DISABLE_OS_PROBER=false

you can edit the file using a GUI text editor like Gedit, or a CLI Editor, such as Vim or Nano.

Using Gedit:

gksu gedit /etc/default/grub

You need to close gedit to be able to use the terminal again

Using Nano

nano /etc/default/grub

I don't recommend using vim if you're a beginner, it takes some time to get used to it's operation modes and interface.

Once you're done with editing the file, if necessary, enter this command

update-grub

Note: You can skip the file editing process on your first try, but if that doesn't work you'll need to do it, then retry update-grub command.

Hope this helps ^_^

  • More complete answer than mine; well done :) – Alex Stragies May 28 '16 at 10:54
  • @AlexStragies thanks :D, although I missed the very important part: start the computer with both disks attached lol – Jenny T-Type May 28 '16 at 10:58
  • 1
    Yeah, I think his problem initially was, that the windows SSD was disconnected during the Debian install (, which normally picks up other, foreign installations, and auto-adds GRUB entries for them) – Alex Stragies May 28 '16 at 11:05
  • Solved the problem, thank you so much. :D – Eunsu Jang May 28 '16 at 11:18
  • @EunsuJang I'm glad it worked well for you. – Jenny T-Type May 28 '16 at 11:25

You could:

  • start the computer with both disks attached,
  • boot into (your currently only choice) Debian
  • run update-grub

It should detect Windows on the first Disk, and add an entry to the boot-loader choices.

And you could then optionally install grub also to the other disk boot sector by running grub-install /dev/sdb

sdb is what I assume to be the device node for the second attached disk, else try sda

Your Answer

By clicking "Post Your Answer", you acknowledge that you have read our updated terms of service, privacy policy and cookie policy, and that your continued use of the website is subject to these policies.

Not the answer you're looking for? Browse other questions tagged or ask your own question.