On Mon, 21 Dec 2020 12:08:40 -0500, Paul
wrote:
Charlie Hoffpauir wrote:
On Mon, 21 Dec 2020 02:21:07 -0500, Paul
wrote:
Charlie Hoffpauir wrote:
My genealogy program will create a very large file for Word that I
have been saving as a PDF for distribution at the family reunion each
year. The file is currently over 3000 pages. If I try to do any
editing in Word, it takes forever. Is there any way to change hardware
or add something to make this work reasonalby fast? I currently have
Word in my C Drive which is a Samsung 500 GB SSD. I plan on replacing
it with a Samsung 1 TB nvme. The genealogy program runs on the C drive
also, but the data is on a HDD. When I add the nvme, should I put the
data on the nvme, or would it be better to put it on the repurposed
500 GB SSD, or does it make any difference?
TIA for any suggestions.
Thanks for the suggestions from both Paul and Vangard.... but I've hit
on a bit of a problem since I posted. I got the Samsung 1TB drive, but
failed to get it working. Installed, my computer recognizes it. Sees
it on ports 4 & 5. After cloning it shows up in both Win 10 Computer
Management and in Hard disk Sentinel. but if I remove the 500 GB SSD I
cloned from, I can't get the BIOS to find the 1 TB as a boot device.
BTW the computer is a homebuilt Gigabyte MB (GS-Z97X-UD3H-BK),
processor is an Intel I-5, don't remember exact model, and there's 16
GB of RAM.OS is Win 10, latest updates.
I tried cloning from the 500 GB to the 1 TB drive, and once cloned,
the computer fails to recoginize it as a boot device. I've had no
problem at all cloning the 500 GB drive.... done it several times
without problem using HDClone.
What is the model number of the Samsung drive ?
970 EVO Model M2-V7E1T0
What is the model number of the original drive ?
860 EVo Model MZ-76E500
I assume these are SATA. But maybe you've got your
NVMe already ?
Yes, I cloned to 500GB to the 1TB, then found it wouldn't boot, and
couldn't locate it in BIOS to set it as boot drive.
What you can do, is with the Samsung connected, boot
a Macrium Rescue CD and use the "Boot Repair" option
in the optional menu. You want *only* the drive
that won't boot, connected during this exercise.
That assures that when Macrium scans the SATA drive,
it only "glues together" the boot materials from
inside that drive, and does not glue every blasted
drive in the computer into some BCD file.
--- DVD drive --- Macrium Rescue CD
--- SATA HDD ---- Samsung 1TB
-----------------/ Other ports empty
Sometimes what happens during cloning, is the
boot materials aren't completely copied. The
Rescue CD can fix that.
I'll ry that , but first I have a "new" system image created by
Windows Backup, and System Repair disk. (Both cerated using the Win 7
installed on the 500 GB Samsung SSD). I'll try doing a Repair to the
1T Samsung NVMe drive using these.
But of course, it's not a SATA drive, this new thing,
so now we move on.
*******
I have the PDF manual on disk here. It says:
"Use of licensed AMI UEFI BIOS"
Since the original drive booted, the BIOS should already
have the correct settings for doing a good job.
CSM Support
Enables or disables UEFI CSM (Compatibility Support Module)
to support a legacy PC boot process.
Always Enables UEFI CSM. (Default) === boots MSDOS era media
Never Disables UEFI CSM and supports UEFI BIOS boot process only.
Boot Mode Selection
Allows you to select which type of operating system to boot.
UEFI and Legacy Allows booting from operating systems that
support legacy option ROM or UEFI option ROM. (Default) ===
Legacy Only Allows booting from operating systems that
only support legacy Option ROM.
UEFI Only Allows booting from operating systems that
only support UEFI Option ROM.
Storage Boot Option Control
(May need adjustment, not sure...)
(M.2 PCIe may need UEFI first)
M.2 PCIE SSD RAID Mode
Enables or disables Intel Rapid Storage Technology
Sometimes, if you're booting from NVMe materials, there's
some storage ROM of some sort that has to be enabled.
Other PCI Device ROM Priority
Allows you to select whether to enable the UEFI or
Legacy option ROM for the PCI device controller other
than the LAN, storage device, and graphics controllers.
Legacy OpROM Enables legacy option ROM only.
UEFI OpROM Enables UEFI option ROM only. (Default) ===
This item is configurable only when CSM Support is set to Always.
You can see someone had your problem here, and this failure
pattern is a familiar one.
https://forums.tomshardware.com/thre...3h-bk.3416549/
My board is Asus, and some of the terminology is slightly
different. And that's why searching the PDF manual isn't
digging up any hits.
"check in the bios the SATA Controller is set to AHCI Mode "
Which should have been the case anyway. There's some
detail like that, that NVMe only work with certain
modes, and only then when the BIOS is mature enough
to not have bugs.
"The BIOS update was indeed the issue. I had read through
the update descriptions but didn't see where they mentioned
fixing a boot from an M.2 drive. Could have missed it.
I have to give them credit - the update process is SO much
easier than the last time I did that a decade or two ago. Wow...
The SATA controller was already set to AHCI."
Another breadcrumb. This is most likely to be the problem.
"Z97X Gaming5 Rev 1.0 bios F7 here. Issues like described
with hc310 6TB disk. The solution for me was to enable
Intel Rapid Start Technology and then it gave option under
it to choose the controller to be used. I choose the other
one that was available - "PCIE AHCI/NVME Controller" and
system boots just fine. My disk with system is plextor ssd
and HGST is the main storage."
RAID and AHCI typically share the same driver file package.
The RAID (RST) seems to recognize the PCIe interface to the
NVMe device. And perhaps it needs to be turned on so the
NVMe can be seen at boot, via the RAID ROM. And the option
ROMs have to be turned on, for this to work. You can't get
to the RAID window, unless the RAID ROM is turned on first,
save, then enter the BIOS and press the magic key combo
to get the RAID screen up.
Now you know why most NVMe owners are bald from the hair loss.
HTH,
Paul
Well, if I'd known there we so many issues I probably wouldn't have
tried to go with the NVMe drive. I noticed someone mentioned Intel
Rapid Start and then PCIE AHCI/NVME controller. I think I've seen an
option to use Intel Rapid start, so I'll check my BIOS and see if I
can find an option for ACHI/NVME.
Thanks for all the suggestions.