Linux - SoftwareThis forum is for Software issues.
Having a problem installing a new program? Want to know which application is best for the job? Post your question in this forum.
Notices
Welcome to LinuxQuestions.org, a friendly and active Linux Community.
You are currently viewing LQ as a guest. By joining our community you will have the ability to post topics, receive our newsletter, use the advanced search, subscribe to threads and access many other special features. Registration is quick, simple and absolutely free. Join our community today!
Note that registered members see fewer ads, and ContentLink is completely disabled once you log in.
If you have any problems with the registration process or your account login, please contact us. If you need to reset your password, click here.
Having a problem logging in? Please visit this page to clear all LQ-related cookies.
Get a virtual cloud desktop with the Linux distro that you want in less than five minutes with Shells! With over 10 pre-installed distros to choose from, the worry-free installation life is here! Whether you are a digital nomad or just looking for flexibility, Shells can put your Linux machine on the device that you want to use.
Exclusive for LQ members, get up to 45% off per month. Click here for more info.
I'm having issues with my bootloaders (yes, it's plural). Here's what I have:
Windows 7 (Internal HDD w/ MBR)
Linux Mint 17.2 (Internal HDD)
Kali Linux (External HDD w/ MBR)
I cannot boot into windows, Grub has a listing for Windows 7 (Loader). It then goes exactly back where I came from. I like linux, but there are some things that I need Windows for.
I used the Paragon Rescue CD 14, and some how bypassed Kali's MBR, and it goes straight to the Windows 7 Loader. Here are the options on the Windows 7 Loader:
Code:
Linux Mint 17.2
Memtest
Windows 7 (Loader)
Kali Linux
When I select the Windows 7 option, it brings me right back to this menu. Is there any rescue CD that can let me recreate a bootloader (preferably free).
The currently running bootloader is grub on windows. When I installed Kali, it added another bootloader. That's how I got two. When I used the Paragon Rescue disc, it bypassed Kali's bootloader. All I have left is Windows.
I know you said all you have left is Windows.....
So can you confirm are you able to boot into Linux Mint or Kail at this point?
If you can't boot into your Linux os's than use the Linux Mint CD/DVD or the usb stick to run this command and post back what the output is. Run this as root-
I'm currently in Mint, I can boot both Mint and Kali. The issue is that Grub is registering the bootloader on Windows and not the OS itself. Here's the output to that command:
Code:
Disk /dev/sda: 500.1 GB, 500107862016 bytes
255 heads, 63 sectors/track, 60801 cylinders, total 976773168 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: 0x07f2837e
Device Boot Start End Blocks Id System
/dev/sda1 63 208844 104391 de Dell Utility
Partition 1 does not start on physical sector boundary.
/dev/sda2 * 212992 41172991 20480000 7 HPFS/NTFS/exFAT
/dev/sda3 41172992 775002111 366914560 7 HPFS/NTFS/exFAT
/dev/sda4 775004158 976771071 100883457 5 Extended
Partition 4 does not start on physical sector boundary.
/dev/sda5 775004160 964366335 94681088 83 Linux
/dev/sda6 964368384 976771071 6201344 82 Linux swap / Solaris
The external that has Kali is not plugged in right now.
I updated grub, and nothing happened. Grub sees itself, and I need it to see through itself to Windows 7. The bootloader is on Windows 7. Also, I don't have a repair disc for Windows. Isn't there something out there to completely redo the bootloader? All this is doing is looking at the current one and editing it. I need a NEW one.
I updated grub, and nothing happened. Grub sees itself, and I need it to see through itself to Windows 7. The bootloader is on Windows 7. Also, I don't have a repair disc for Windows. Isn't there something out there to completely redo the bootloader? All this is doing is looking at the current one and editing it. I need a NEW one.
In your initial post, you indicate you have Mint and windows 7 on the internal drive with windows boot code in the MBR. Since a default installation of windows is not capable of booting Linux, did you install and are you using third party software such as EasyBCD or did you manually modify the windows boot files yourself? Or possibly when you say "windows loader", are you referring to the bootloader on the first drive on which you have windows 7 and Mint?
When you installed Kali, did you accept the default for the bootloader installation or did you install it to the MBR of the external drive?
Quote:
The currently running bootloader is grub on windows.
If you mean grub on the windows hard drive, it should be possible to fix. If you mean you installed grub code to the windows partition, that's another and bigger problem, especially if you don't have the windows installation medium.
Since you can boot Mint, in order for us to get detailed information, go to the site below and download and run the boot repair script. Make sure you select to 'Create BootInfo Summary" rather than try any repair. Post the file it outputs here so someone can review it.
Here: http://paste2.org/X9f9ek9e
Also, I used Easy BCD when I first installed Mint, only because I forgot to change where mint installed grub. It installed it on itself. When I installed Kali, it didn't give me an obvious place to install grub to, so, it became the new main one. On there was Windows 7 Loader (EasyBCD), and Mint. I tried to move Kali's bootloader off of my external, so I didn't need it to boot up. Instead, it created this mess. I used grub customizer to install it to the MBR. That is what made this mess.
Before you say anything, I screwed up big time.
Also, I had a USB with Linux Mint 17.2 Live on it, so that's sdc.
If you look at the very top of the boot repair output, you will see that you have windows code in the master boot record of sda and sdb, that is both the 500GB and 1TB drives. You could install Grub to the master boot record of sda where you have Mint and install Grub to the master boot record of sdb where you have Kali. I doubt that this would help as you say you can currently boot both but cannot boot windows. Did you notice in the boot repair that you have Grub installed on sda2 and sda3 and that BOTH of those partitions are windows partitions. Grub should never be installed on a windows partition and that would not have happened during an install. Most likely what happened is that you have overwritten the IPL with Grub code on the windows partitions. That would explain the continuous loop when you select windows and go back to the Grub menu, if I understand your initial post. Since you indicated you do not have a windows installation disk, you will need to find some other method to repair the windows boot code. I don't use windows so hopefully some member who does will come along with a suggestion.
Neosmart Technologies has an iso available for download which will do the job. Last I checked it was $20USD. It had been a free download but that changed when microsoft complained to them, see the second link below.
Most manufacturers with a pre-installed windows system will offer the installation medium for an additional cost at the time of purchase which considering the alternative, is the best option available. There might be some free download of a repair disk but I don't know of any.
I'm going to try the repair option with the Windows install disc. Just a quick question, would running the boot-repair possibly fix it, or would it make things worse?
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.