Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]
Groups > alt.os.linux.mageia > #14262
| From | Jim Beard <jim.beard@verizon.net> |
|---|---|
| Newsgroups | alt.os.linux.mageia |
| Subject | Re: Further Suggestions on Dual-Boot with Win10 solicited |
| Date | 2016-11-04 15:21 +0000 |
| Organization | A noiseless patient Spider |
| Message-ID | <nvi91k$u7a$2@dont-email.me> (permalink) |
| References | <nvgo9p$1rj$1@dont-email.me> <nvgt32$o7a$1@dont-email.me> <LIUSz.303593$QY1.145265@fx28.fr7> |
On Fri, 04 Nov 2016 16:07:54 +1100, dlbendigo wrote:
> Bobbie Sellers <bliss@mouse-potato.com> Wrote in message:
>> On 11/03/2016 06:29 PM, Jim Beard wrote:
<snip>
> I agree with Bobbie. They used to say that Windows needed to be on
> /dev/sda1, but I don't think that it is strictly true any longer.
>
> My set-up is:
> /dev/sda 1 &3 :Windows machinery.
> /dev/sda2 :/boot/EFI for Windows and everything else.
> /dev/sda4 :Windows C:
> /dev/sda5 :Mageia /.
> (etc.)
MicroCenter installed Win10 to what became /dev/sdb. Due to problems
trying to install Mageia 5, all drives were disconnected except the ssd
that became /dev/sda. I installed Mageia5 UEFI, and things looked like
this.
NAME MAJ:MIN RM SIZE RO TYPE MOUNTPOINT
sda 8:0 0 232.9G 0 disk
├─sda1 8:1 0 500M 0 part /boot/EFI #not used by Grub 2 ?
├─sda2 8:2 0 39.1G 0 part / # mageia5
├─sda3 8:3 0 73.2G 0 part /home # mageia5home
├─sda4 8:4 0 34.2G 0 part # mageia6
├─sda5 8:5 0 73.2G 0 part # mageia6home
└─sda6 8:6 0 12.7G 0 part
sdb 8:16 0 232.9G 0 disk
├─sdb1 8:17 0 450M 0 part #Windows recover
├─sdb2 8:18 0 100M 0 part #Windows & Grub EFI System partition
├─sdb3 8:19 0 16M 0 part #Compaq diagnostics
└─sdb4 8:20 0 232.3G 0 part #/media/win_c2
sdc 8:32 0 1.8T 0 disk
├─sdc1 8:33 0 33.6G 0 part [SWAP]
├─sdc2 8:34 0 150.9G 0 part .....
After reconnecting all drives, the above would dual boot, but I had to
hit DEL or F2 upon rebooting and select which ssd and partition to boot
to, each time I wished to reboot to the non-default.
In trying to put all UEFI boot stuff in the /dev/sda EFI partition and
boot my choice of Win10 or Linux from a grub2 menu, I did not know the
range of commands I would need and what to do with them, and somewhere in
the process the Win10 boot files were deleted. I have been unable to
reinstall Win10 to get them back.
At this point, rather than learn new commands including (but probably not
limited to) efibootmgr, grub2-mkconfig, gdisk -l, and use a suitably
modified version of /etc/grub.d/40_custom (below) with grub2-mkconfig to
set up a Win10 entry in the grub2 menu, I think I will try for the
virtualbox approach.
Among other problems, the /dev/sdb was originally split into two
partitions, and Win10 installed as it wished in the first. Win10 created
four partitions, leaving 232GB unallocated. But now, all the unallocated
space appears to be part of a single partion that includes the original
sdb4. I can't start Win10, but anticipate that would be a problem if I
could. If I can make vbox work, simply erasing the /dev/sdb ssd and
creating ext partitions on it may be the best thing to do.
Anyway, part of the recipe for adding an entry to the grub2 menu (that I
did not know) seems to be,
edit /etc/grub.d/40_custom and add:
menuentry 'Windows' {
insmod part_gpt
insmod fat
insmod chain
set root='hd0,gpt2'
chainloader ($root)/EFI/Microsoft/Boot/bootmgfw.efi
}
> On sdb, I have:
>
> Sdb1 & 2 : EFI system partitions created by other distros.
> The balance is OpenSuse.
>
> update-grub finds what it needs from sdb, and creates a special kind of
> link. I saw its name when update-grub was running, but it doesn't
> appear in grub.cfg. For a while,
> it worked only in Cauldron, although Mga5 had the same version of Grub2.
> Now I have Cauldron as default.
>
> I recently reinstalled Win10, and the only problem was a new UUID.
??? Sdb1 & 2 : EFI system partitions created by other distros.
Do you have a separate EFI partition for each distro? How do you keep
them separate and choose among them? Do all show on your grub2
--
UNIX is not user-unfriendly, it merely expects users to be computer-
friendly.
Back to alt.os.linux.mageia | Previous | Next — Previous in thread | Next in thread | Find similar | Unroll thread
Further Suggestions on Dual-Boot with Win10 solicited Jim Beard <jim.beard@verizon.net> - 2016-11-04 01:29 +0000
Re: Further Suggestions on Dual-Boot with Win10 solicited Bobbie Sellers <bliss@mouse-potato.com> - 2016-11-03 19:51 -0700
Re: Further Suggestions on Dual-Boot with Win10 solicited dlbendigo <laidlaws@hotkey.net.au> - 2016-11-04 16:07 +1100
Re: Further Suggestions on Dual-Boot with Win10 solicited Jim Beard <jim.beard@verizon.net> - 2016-11-04 15:21 +0000
Re: Further Suggestions on Dual-Boot with Win10 solicited Jim Beard <jim.beard@verizon.net> - 2016-11-04 14:11 +0000
Re: Further Suggestions on Dual-Boot with Win10 solicited Bobbie Sellers <bliss@mouse-potato.com> - 2016-11-04 07:28 -0700
Re: Further Suggestions on Dual-Boot with Win10 solicited Bit Twister <BitTwister@mouse-potato.com> - 2016-11-04 04:57 +0000
Re: Further Suggestions on Dual-Boot with Win10 solicited Jim Beard <jim.beard@verizon.net> - 2016-11-04 15:45 +0000
Re: Further Suggestions on Dual-Boot with Win10 solicited Jim Beard <jim.beard@verizon.net> - 2016-11-05 18:46 +0000
Re: Further Suggestions on Dual-Boot with Win10 solicited Bit Twister <BitTwister@mouse-potato.com> - 2016-11-05 20:25 +0000
csiph-web