On 5/9/20 1:38 AM, Robert G (Doc) Savage via users wrote:
On Thu, 2020-05-07 at 10:49 -0400, sean darcy wrote:
My new laptop has Windows 10 installed with the Intel
rapid Storage Technology (optane) system chip. Windows is on an nvme
drive.
FC31 is on a SATA ssd.
BIOS allows me to choose AHCI or RST. I must use AHCI to boot the FC31
drive, and RST to boot the Windows drive. Neither will boot with the
other. Sigh.
1. Is there a way to get the FC31 drive to boot with RST ?
2. Any way to have the Windows drive boot with AHCI ?
sean
I have Intel RST "fake RAID" on my Lenovo ThinkPad P72. As delivered,
Windows 10 Pro was installed on two 2TB NVMe SSDs in a RAID1 mirror
configuration. While I could have also installed a standard notebook
SATA SSD, I postponed that idea (see below) and broke the RAID1 mirror
instead. The BIOS Storage setting gave me two options: RST or AHCI. The
BIOS is wrong. It should say RST or NVMe. SATA or AHCI are not options.
And boy are the two raw NVMe drives F-A-S-T !!!!
I went through all the hand wringing and fear of screwing up something I
didn't completely understand at the time. I backed up everything I could
think of from Windows 10, and a went to the trouble of getting a Lenovo
ThinkPad Windows restoration thumb drive.
Happily, once I broke the RAID1 mirror, I was able to boot to a Fedora
live ISO on a thumb drive. It could see both /dev/nvme0 and /dev/nvme1
SSDs. The #0 device still contained one half of the mirrored Windows 10
installation. fdisk shows the following detail:
# fdisk -l /dev/nvme0n1
Disk /dev/nvme0n1: 1.88 TiB, 2048408248320 bytes, 4000797360 sectors
Disk model: SAMSUNG MZVLB2T0HMLB-000L7
Units: sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 512 bytes / 512 bytes
Disklabel type: gpt
Disk identifier: 868B8A59-AF35-48EB-AD4F-0B2966DD92F5
Device Start End Sectors Size Type
/dev/nvme0n1p1 2048 534527 532480 260M EFI System
/dev/nvme0n1p2 534528 567295 32768 16M Microsoft reserved
/dev/nvme0n1p3 567296 3998748671 3998181376 1.9T Microsoft basic data
/dev/nvme0n1p4 3998748672 4000796671 2048000 1000M Windows recovery
environment
This frees /dev/nvme1n1 for a normal installation from a live CD image.
It will set up GRUB2 for a Windows + Fedora dual boot. When installed,
your second NVMe drive should be partitioned something like this:
# fdisk -l /dev/nvme1n1
Disk /dev/nvme1n1: 1.88 TiB, 2048408248320 bytes, 4000797360 sectors
Disk model: SAMSUNG MZVLB2T0HMLB-000L7
Units: sectors of 1 * 512 = 512 bytesSector size (logical/physical): 512
bytes / 512 bytes
I/O size (minimum/optimal): 512 bytes / 512 bytes
Disklabel type: gpt
Disk identifier: D02F3FF2-CE20-43A2-A2E2-92053E91D817
Device Start End Sectors Size Type
/dev/nvme1n1p1 2048 411647 409600 200M EFI System
/dev/nvme1n1p2 411648 2508799 2097152 1G Linux filesystem
/dev/nvme1n1p3 2508800 4000796671 3998287872 1.9T Linux LVM
As I indicated above, I later installed a 4TB SATA internal drive in an
expansion space inside the P72. I had to buy a wiring adapter to connect
the SATA drive to the P72's internal chassis wiring. That wiring doesn't
come instsalled from the factory. I got the kit from EggHead.
Hope this helps.
--Doc Savage
Fairview Heights, IL
Very interesting. Are you now able to boot into Windows on nvme0 from grub ?
sean
_______________________________________________
users mailing list -- users@lists.fedoraproject.org
To unsubscribe send an email to users-le...@lists.fedoraproject.org
Fedora Code of Conduct:
https://docs.fedoraproject.org/en-US/project/code-of-conduct/
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives:
https://lists.fedoraproject.org/archives/list/users@lists.fedoraproject.org
