Installed 17.1 on dual-boot PC, but no GRUB, and no login/desktop
Linux MintThis forum is for the discussion of Linux Mint.
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 don't use UEFI myself so am just basing on what I have read. The link below gives a pretty detailed explanation of UEFI on Ubuntu/Mint. The original bootinfo output posted by the OP showed windows installed to the MBR on one drive and Grub on the second which would mean he is not using UEFI. Now he has installed Mint in EFI mode which generally creates problems
Where the grub.cfg resides in efi mode is distro specific. Some distros have the file in /boot/grub and other distros require the grub.cfg file to reside on the efi partition with the efi boot files. I may be wrong but I think mint installed in efi mode puts a config file on the efi partition pointing to the /boot/grub/grub.cfg file, so in a situation like this that file may not exist with the boot files on the efi partition.
Okay, I did a lot more reading and a bit more tinkering and the good news is that I have Mint installed now. For the benefit of anybody finding this on Google or whatever, the trick was to create an EFI partition (200MB, FAT32, flagged 'boot', then put the boot loader there during installation and designate it as an EFI partition) and since the BIOS had that as the first choice, it boots straight into Mint now.
Good job!
Quote:
Originally Posted by Kylotan
Unfortunately there is still no GRUB2 menu as it can't find Windows 8.1. I tried the os-prober and update-grub routes but neither found it. So I can only choose between operating systems by reordering the BIOS boot order - not optimal.
My disks are a bit unusual: Windows 8.1 is on a smaller, MBR disk. Linux Mint is on a 3TB GPT disk. (Both according to Windows disk management, at least.) Maybe if Windows was also on a GPT disk there would be no problem, but that's not something I can change easily now.
If anybody has any suggestion on how I can force GRUB2 to find Windows on the other disk, and show me a menu to let me choose between them, I'd be grateful.
I don't know of any solution for that situation. The problem is that when you chose to boot Mint, your computer boots in UEFI mode. That means when you see the Grub menu (IF you do...) the computer has already booted in UEFI mode - meaning that it is not going to boot the non-UEFI Windows. At least, that is the process as far as I understand it.
What I would do, if it were my computer, is delete all the partitions and the GPT partition table on sdb, and change it to msdos partitioning, and re-install Mint in non-UEFI mode. That would eliminate any incompatibilities between Windows on sda and Mint on sdb.
To delete the GPT partition table is very simple. Boot the live Mint DVD or USB, open the gparted program. Click on sdb > Device > New Partition Table > msdos
Then use gparted to create the partitions you want for Mint. Close gparted and run the Mint installer. Chose the Something Else option, and install to the partitions you created, making sure to install the bootloader to sdb, not sda.
Unfortunately, sdb isn't suitable for old-style partitions because it's a 3TB drive.
It seems strange that this would stop grub2 finding Windows, however - whatever mode it booted up in, those drives are still all visible, including the Windows system partition which contains its bootloader etc. Does it somehow need some extra information from the UEFI BIOS?
It seems strange that this would stop grub2 finding Windows,
Not really. If you are booting Mint in EFI then it looks on the FAT32 partition for its EFI files and if you select windows it will look on the EFI partition for the windows EFI files which you do not have since windows is not installed in EFI mode. The files below are the Ubuntu/Mint EFI files and are on the FAT32 partition. If you had windows installed EFI, the windows files would also be there obviously with different names.
The second link in post 17 above explains a method of using EFI/MBR but it seems to have a lot of restrictions and doesn't seem like it would work well on an everyday computer since some updates will break it.
Unfortunately, sdb isn't suitable for old-style partitions because it's a 3TB drive.
That statement is correct if you are using the conventional 512 bytes per sector. If you use 4 KB sectors (4096-byte logical sectors), msdos partitioning can address up to 16 TB on an "Advanced Format" drive (which a new 3TB drive should be).
I have seen that in various places, you would have to research the exact procedure for setting it up.
Here is an example, quoted from http://ubuntuforums.org/showthread.php?t=1536933
Model: Seagate FA GoFlex Desk (scsi)
Disk /dev/sdc: 3001GB
Sector size (logical/physical): 4096B/4096B
Partition Table: msdos
Number Start End Size Type File system Flags
1 28.7kB 3001GB 3001GB primary
Another example, quoted from http://ubuntuforums.org/showthread.php?t=2246256
Model: WD Ext HDD 1021 (scsi)
Disk /dev/sdb: 3001GB
Sector size (logical/physical): 4096B/4096B
Partition Table: msdos
Number Start End Size Type File system Flags
1 1049kB 3001GB 3001GB primary
You have installed Mint in legacy (msdos) mode to a drive with GPT partitioning. That is not a good thing.
GPT does not have the old style MBR where Grub would be installed. Instead, it has a "fake MBR" to accomodate legacy installations.
Here is a good tutorial on how to fix it - http://www.rodsbooks.com/gdisk/wipegpt.html
Unless you are using only one or two drives of very small capacity, I would exhaust your efforts to resolve your troubles using GPT before you fall back to using the old-school MBR. Consider 7 Ways to Dual Boot ... and Dual Boot Linux Mint 17.
The GUID Partition Table or GPT of itself is not a bad thing. There are many advantages over the previous approach Master Boot Record or MBR. When disks were small, four "primary" partitions was effective. Larger disks caused deployment of the "extended partition" which could then contain "logical partitions." Today's giant drives, by comparison, benefit from an approach that permits an all-but-unlimited number of partitions numbered 1,2,3,... It is unfortunate that the GPT features got tangled in with "secure boot" and other aspects of the unified extensible firmware interface (UEFI).
Download the USB flash drive or CD-R version of the rEFInd boot manager. - http://www.rodsbooks.com/refind/getting.html
Burn the CD (or USB).
When you boot the CD you should see a rEFInd menu with options for both Windows and Linux.
Test the boot options. Some might not work, but you should be able to boot both Linux and Windows.
If the preceding step works, boot to Linux.
Download and install the Debian-package version of rEFInd.
You should be able to boot both Linux and Windows, using rEFInd as the boot manager instead of GRUB.
You might want to clean up some non-functional or redundant entries, but that's not hard.
If you are having problems booting up your Linux or other Operating Systems (OS), you can use the very easy, useful, and very handy, program "Boot-Repair-Disk". This program can repair most booting up issues by just booting to this program and selecting the first option "recommended repair" which is usually a one click repair for fixing your booting problems. This program has saved my butt many times when I was experimenting with installing Linux distributions. I have provided a link below where you can download "Boot-Repair-Disk" as an ".iso" file and create a live usb, or CD or DVD from; or if you can boot to your Linux partition, then you can install this directly into your Linux using the instructions below.
Installing "Boot-Repair-Disk" to your Linux using PPA mode, bring up your "terminal" and type in:
(obviously you have to run it after installing it to repair your booting up problems)
If you cannot boot up your local drive(s), or want to boot to another device, then there are very good programs available to allow almost any machine to boot to your local drive(s), external USB drive(s), or CD/DVD drives, like "SuperGrub2 Boot Loader" and "PLOP" which you can burn to CD/DVD or another USB drive. With these programs, I have been able to boot to the USB drives that I have created using the default Linux Mint 17 program and "unetbootin". I prefer to use the "Super Grub2 Boot Loader" program disk to boot my USB drives; It shows all installed operating systems on the machine and lets you choose which one to boot - very cool. I'm not sure, but Super Grub2 may also be able to repair or reinstall the boot information or Grub files.
I'm still looking for a thorough explanation of whatever Windows™ 7 and 8x does during its install along with what it does and needs and uses during its boot.
I understand the Linux® boot pretty well (grin) at least up until init takes over. I used to understand the Master Boot Record (MBR) boot in that context. Now UEFI and GPT have me completely confused.
One wrinkle that I know says that Win-7 must be 64-bit to use GPT and UEFI features, with or without "secure boot."
I think that means:
power on and enter CMOS/BIOS settings dialogs
enable UEFI features
disable "secure boot" (typical for folks running Linux)
accomplish installs with MBR or GPT partitions as desired
I understand the Linux® boot pretty well (grin) at least up until init takes over. I used to understand the Master Boot Record (MBR) boot in that context. Now UEFI and GPT have me completely confused.
With BIOS firmware, the BIOS looks at the MBR for instructions on booting. With EFI firmware, the EFI mechanism includes much more of the booting information in the EFI itself, and looks only at the ESP (EFI System Partition).
Drop a private message (PM) if you want to find a beverage...
I sincerely appreciate the invitation, but the Ayn Rand quote in your sig indicates that we would not get along.
I prefer Democracy - it isn't perfect, but it is better than any alternative.
I realize that people who preach anti-social or un-democratic philosophies, like Ayn Rand and Machiavelli, have their followers, but I am not one of them.
I sincerely appreciate the invitation, but the Ayn Rand quote in your sig indicates that we would not get along.
I prefer Democracy - it isn't perfect, but it is better than any alternative.
I realize that people who preach anti-social or un-democratic philosophies, like Ayn Rand and Machiavelli, have their followers, but I am not one of them.
Austin Greetings, philosophy not withstanding...
Our political and social "differences" and discussions of them are what might make things intellectually interesting. That said, I understand that it is difficult, in these times, to attempt discussion of many topics because so few folks are able to remain open minded in the presence of opinions they disagree with or that they find distasteful. I'm not suggesting that you might be one of those folks. Rather, you have no idea how I might respond to or react to whatever might come up in conversation.
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.