mazzy wrote:So I had a working install of LM15, I am attempting to just reinstall Mint 16 and leave /home intact. The previous system was installed non-EFI, but the new Live CD will not boot for me non-efi (I can get the specific error if necessary...) and I think the installer just goes on however the CD is booted ?
Yes, the installer tries to install for whatever boot mode (BIOS/CSM/legacy vs. EFI/UEFI) was used to boot the installer. There should be a way to force a BIOS/CSM/legacy-mode boot of your installation medium, but the method is likely to depend on your motherboard. Sometimes there are multiple boot options in a built-in boot manager that you can access by pressing Esc or a function key; other times you may need to change options in the firmware's setup utility.
From your Boot Repair output:
Code: Select all
Disk /dev/sda: 150.0 GB, 150039945216 bytes
255 heads, 63 sectors/track, 18241 cylinders, total 293046768 sectors
Units = sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
Partition Boot Start Sector End Sector # of Sectors Id System
/dev/sda1 * 2,048 292,863 290,816 83 Linux
/dev/sda2 2,002,942 293,046,271 291,043,330 5 Extended
The presence of an extended partition indicates that you've got a [url=http://en.wikipedia.org/wiki/Master_boot_record]Master Boot Record (MBR)[/url] partition table. This makes an EFI-mode installation tricky or impossible. At the very least, you'll need to use fdisk to change the type code of your /dev/sda1 from 0x83 to 0xEF -- this is the code for an [url=http://en.wikipedia.org/wiki/EFI_System_partition]EFI System Partition (ESP)[/url] on an MBR disk. A better solution (and one that may be required, depending on your motherboard and the level of support in the Mint installer for EFI/MBR installations) is to use GPT fdisk (gdisk) to convert the disk from MBR to [url=http://en.wikipedia.org/wiki/GUID_Partition_Table]GUID Partition Table (GPT)[/url] form. (See [url=http://www.rodsbooks.com/gdisk/mbr2gpt.html]here[/url] for detailed instructions.) If you do this, you'll need to change the type code of /dev/sda1 from 8300 to EF00.
I don't know if there is a way to get that efi partition to start at sector 0 instead of 2048, but it seems like that might be part of the issue.
No, that's both impossible and not the cause of the problem. Sector 0 is the MBR, which is where an MBR-partitioned disk's partition table resides, so if you were to start the first partition at sector 0, anything that overwrote the partition's first sector (such as creating a filesystem) would wipe out the partition table. This would be a bad thing!
On a GPT disk, sectors 0-33 are normally occupied, so sector 34 is the earliest one that can possibly be used. As a practical matter, sector 2048 is the default first sector used by most tools today because that helps with performance issues on some types of disks (certain types of RAID array and SSDs). (Modern Advanced Format disks require 8-sector alignment, which the 2048-sector alignment satisfies. If you're not using RAID or SSD, you can use advanced partitioning tool options to begin the first sector of the first partition on sector 40, but it's usually not worth the effort -- the wasted space by starting the first partition at sector 2048 is so minuscule that it's not worth worrying about.)
I think I found the issue. Creating mbr boot from Ubuntu Saucy 13.10, causes the odd partition#'s. Creating mbr boot from Ubuntu Precise 12.04, everything is normal.
either a change in grub or how the mbr gets written.
MBRs contain two things: boot code and a partition table. They're created by different tools. It's unclear if you mean the MBR partition table or the MBR boot code. In any event, as I said, you should either find a way to force a BIOS-mode installation or switch to GPT and do an EFI-mode installation.
Any suggestions? I have never installed efi system before so maybe I'm just doing something stupid, hopefully
You may want to read my Web page on EFI-mode installations: