On 12/20/2016 10:37 AM, Andrei Borzenkov wrote:
20.12.2016 19:27, Marc Chamberlin пишет:
On 12/20/2016 6:06 AM, Andrei Borzenkov wrote: ... [Disks]
Item Value Description Disk drive Manufacturer (Standard disk drives) Model HGST HTS721010A9E630 ... Description Disk drive Manufacturer (Standard disk drives) Model NVMe THNSN5256GPU7 TO That reinforces my guess that both drives are used independently. Then it may be possible to switch to AHCI mode without reinstall. I am a bit uneasy because NVMe is also your boot drive and most discussions seem to talk about SATA drives. But you can always make clone backup (you have enough space) if something goes wrong.
There are several posts suggesting that something like descibed procedure may help: http://triplescomputers.com/blog/uncategorized/solution-switch-windows-10-fr...
In principle, there should be no difference whether you use SATA or NVMe as in both cases it involves loading different drivers than current.
Andrei - This worked!!! I now have Windows 10 booting up from the SSD disk in AHCI mode, and the Leap 42.2 installation process is happy to proceed also. Thanks so much for getting me over this hurdle. I like this particular approach as is seemed like a non-risky way to switch modes, from which I could easily recover had things not worked. Lot better than the procedure I previously found which had me change the Windows storage drivers and left my system in an unbootable state! So this brings me to my next questions, getting back to setting up the bootloader, and where to put things.... The Leap42.2 installer wants to create and put partitions for /, /home, swap, and /boot/efi on the second 7200RPM disk drive. My instincts tell me to put the partitions for / and swap on the SSD drive since it will be faster. (I do have enough unallocated space on the SSD drive.) I would leave /home on my 7200 RPM drive since that is where most of my development work data would be stored and it has the most storage space. I am not sure what to do about /boot/efi. Microsoft has already created an EFI boot partition in a 260MB FAT partition on the SSD drive. Again my instincts tell me to let the Leap42.2 installer install the /boot/efi partition on the second drive so as to keep the GRUB boot loader stuff separate from Microsoft's boot loading stuff, but the details of how bootloaders really work is one area that I do not fully understand. Should I (can I?) instead mount the Microsoft boot partition at /boot/efi, instead of having a separate partition for booting up Linux, in order to take advantage of the SSD speed in booting up each OS? I understand some of this at a high level, but as they say the devil is in the details... Still a bit confused but now at least I'm hopeful that I will manage to get Leap 42.2 installed... Marc... -- "The Truth is out there" - Spooky -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org