Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]
Groups > alt.os.linux.mageia > #14260
| 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 14:11 +0000 |
| Organization | A noiseless patient Spider |
| Message-ID | <nvi4uv$u7a$1@dont-email.me> (permalink) |
| References | <nvgo9p$1rj$1@dont-email.me> <nvgt32$o7a$1@dont-email.me> |
On Thu, 03 Nov 2016 19:51:37 -0700, Bobbie Sellers wrote: > On 11/03/2016 06:29 PM, Jim Beard wrote: >> For a brief period of time, I had Mageia 5 installed on sda1 and win10 >> on sdb, and could switch from one to the other by rebooting and >> selecting which to boot from in the UEFI Bios choices. >> I tried to get fancy, and get Grub 2 to present both choices on reboot. >> This too worked, briefly. Then, I lost the ability to select and boot >> to Win10, followed by loss of ability to boot Mageia 5. >> I restored the Grub 2 bootloader, and it now works fine in booting >> Mageia 5, but the EFI partition that once held the Microsoft UEFI boot >> software now contains nothing but a path that leads to >> mageia/grub64.efi. > > You probably should have had just one EFI partition. Switching > boots though the BIOS is the wrong way to go. > Have you tried running the grub-organizer? Concur on just one EFI partition. The Win10 ESP created by the MicroCenter install was only 100MB, and I had seen recommendations for 300MB. In addition, the tools I used to try to see how full the Win10 ESP was looked like it was full. Either I was using the wrong tools or misreading, as later looks at it showed only 21MB. I had hoped to move the Win10 ESP contents to the Mageia5 ESP vfat partition, but copying them over did not work, and my attempts to use grub2-update to integrate the two ultimately failed. >> >> My belief I could simply reinstall Win10 if things went wrong has >> proved in error. My attempts to install to /dev/sdb where Win10 had >> been installed fails, with one error message saying the partition is >> locked. I do not know how to "unlock" it, or how to force an install. >> I have tried disconnecting the disk that has Mageia 5 and installing to >> Win10 on /dev/sdb by itself, but too this continues to fail. > > Microsoft really hates anyone messing about, in case you had > not figured that out. > Have you booted up a GParted and tried to look at the Windows 10 > SSD? You might be able to get past that lock. Yes, I had booted with gparted two or three times trying to look at things. No joy, perhaps because I was not familiar with gparted or the correct commands to use. >> Next possibility: Try to install Win10 under VirtualBox. The first >> question is whether I should try to install virtualbox and then use a >> Win10 image available from Microsoft (about 4 GB, iso, which I have >> downloaded) or try to install from my Win10 install usb drive >> (usbstick). >> >> In the first case, I start up virtualbox, tell it to create a new OS, >> and point it to the iso image. In the second case, I would start up >> virtualbox, tell it to create a new OS, and point to to the usb drive. >> >> Would virtualbox then install from the usb drive? Or do I need a magic >> incantation to start things off? How do I enter it, if I do? >> >> So far, I am leaning to using the Mageia virtual box packages and I >> think I need the following mageia rpm packages: >> virtualbox- >> virtualbox-kernel- >> vboxadditions-kernel- >> virtualbox-guest-additions- >> plus virtualbox-extensions available only from the virtualbox website. >> >> I think all but virtualbox-guest-additions- should be installed before >> trying to create the Win10 virtual machine, and the virtualbox-guest- >> additions installed afterward. Right? >> >> Has anyone done this, or succeeded with a different method? >> Does the above sound right? Have I overlooked something? >> >> Where should I put the new virtual Win10? I am inclined to put it in >> the ext4 partition I intend to use for Mageia 6 for the moment, and >> then move it elsewhere if it works. I understand this is possible. >> Correct? >> >> I am dithering as usual when I really do not know what I am doing, or >> should be doing. Any suggestions would be welcome. >> >> Cheers! >> >> jim b. >> >> > Wish I could offer more than suggestions but since I won't have Windows > 10 for an indefinite time to mess around with that is all I can do. > > bliss -- 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