Replies: 6 comments 8 replies
-
You should try enabling debug boot log in config.plist then check what is doing, while enabled the boot process is slower than usual so be patient :) also in Clover menu you can press F2 to create a preboot log with infos on what was done until the menu appear. |
Beta Was this translation helpful? Give feedback.
-
Try this one |
Beta Was this translation helpful? Give feedback.
-
On 2021-01-15 12:15, marc wrote:
Try this one
NTFS-64.zip [1]
Didn't work. Behaves the same. :(.
…
--
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub [2], or unsubscribe
[3].
Links:
------
[1]
https://github.com/CloverHackyColor/CloverBootloader/files/5822724/NTFS-64.zip
[2]
#340 (comment)
[3]
https://github.com/notifications/unsubscribe-auth/AJLGUGWUEYPQ4AU3GTOBGTDS2CO4PANCNFSM4WBEUDGA
|
Beta Was this translation helpful? Give feedback.
-
On 2021-01-15 14:32, marc wrote:
Well... i am not sure if i didn't missed something, but what exactly
you intend to do?
*** Boot the system off a Samsung NVME drive that I just obtained.
Hoping to get a speed boost as compared to the existing SATA SSD. The
PC reads and writes it at run-time, but will not boot off it, because no
driver in the BIOS.
I formatted the new drive as GPT partitions with gparted. Then cloned
each existing partition from the SATA boot drive with Macrium Reflect.
Windows reads the new drive OK from the GUI.
I wonder if the BIOS is just too old? The existing BIOS is dated
2013.
There are updates from ASUS up to 2018. I haven't updated it yet,
because their program to do the update requires 32-bit Windows. I can
download an old Windows from Microsoft and load it onto a junk hard
drive ( got lots of those since I converted everything to SSDs ) and
apply
that update. But that's a lot of work...
OTOH, it might be time to update this PC to a newer MB. I would need
a motherboard, a CPU, CPU cooler, DRAM... Luckily, my copy of Win10 is
the retail kind, so I would be able to move it.
-
To boot an installed windows through Clover and you
… are unable to see the boot option? Maybe you need to unhide legacy
menus in GUI > Custom > Scan by removing the # sign before Custom and
Scan
--
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub [1], or unsubscribe
[2].
Links:
------
[1]
#340 (reply in thread)
[2]
https://github.com/notifications/unsubscribe-auth/AJLGUGQK6DGWNYAA2FMVW7LS2C66RANCNFSM4WBEUDGA
|
Beta Was this translation helpful? Give feedback.
-
@jkaidor please press again F2 and provide the log file with NTFS driver installed, also provide the config.plist. Your Clover clearly see the NVME drive, find 3 partitions on the same drive 2:428 0:000 - [08]: Volume: PciRoot(0x0)\Pci(0x1C,0x4)\Pci(0x0,0x0)\NVMe(0x1,B2-30-90-01-5B-38-25-00) But does not seems to find any bootable partition and ends with only one bootable entry from Sata 2:446 0:001 === [ GetEfiBootDeviceFromNvram ] =============== |
Beta Was this translation helpful? Give feedback.
-
I have observed that your SATA HDD it is partitioned as MBR but your NVME as GPT so probably this is the issue, you should clone entire SATA-HDD over the NVME including MBR not just partitions, because your SATA use MBR you are missing exactly the BOOT flags on your newly GPT. |
Beta Was this translation helpful? Give feedback.
-
Hello,
I'm trying to use Clover to boot my ancient ( 2013 ) workstation with an NVME SSD. Windows 10 sees the SSD, but will not boot off it ( no driver in BIOS, duhh ). I loaded Clover on a thumb drive and moved the NVME driver to the two appropriate places as documented on the Web.
Here's what it's doing. Restart the PC, get it to boot off the thumb drive, Clover starts up. However, it will not boot anything. I tried each of the list of "legacy drives" shown on the screen, and for each choice, I was presented a blank screen with an unmoving flashing cursor in the upper L/H corner.
Reset button, try again... Same deal. I tried for each and every drive presented on the screen.
If, however, I choose "Exit Clover", Windows then boots normally.
So - Clover does not boot the NVME drive, AND ALSO does not boot the existing OS drive.
So I suspect that the problem is not the NVME driver, but rather something more global.
I have tried web searches, came up dry. I used to be reasonably educated on boot/MBR issues, down to the level of bytes on the drive, but that was decades ago. Have no clue as to what to even look at.
Clover seemed like a really good solution for my old but potent workstation ( 4 core XEON 3.2gHz, 32G of ECC RAM, absolutely silent build ). Really don't want to build a new PC at the moment....
Where do I start looking? Thanks in advance....
Beta Was this translation helpful? Give feedback.
All reactions