If I can't get Clover working then I think my best bet might be to start looking into those Type B Sata SSD Adapters you mentioned, could you recommend any particular one from wow you honestly got further then me and I've been trying for a while haha, way to go! It would be nice to know if someone with a similar but slightly different setup runs into the same issues or not with Clover, so if you get the chance please do let me know how it works out for ya.
CLOVER EFI XEON 5660 WINDOWS
I was able to get my hands on a working safe version of BDU from a forum user so I'm currently testing that, I've been told I'll have better luck if I flash it on the Target system itself, so I'm setting up a Windows 2 Go live bootable as I write this, So wish me Luck. I'm not sure if the initial developer intended for BDU to be malicious or if it just kinda became abandoned ware and malicious actors have taken it over, a good example being the AIO Boot Tutorial you shared, Who knows why but the creator actually infested their utility with Malware and once people complained they took it down silently. I've been told that the recommended flashing utility is BDU "Boot Disk Utility" created to make Clover installations easier, however do be warned that many copies of BDU and other Clover Flashing utilities floating around the Internet unfortunately contain Malware, so it's best to attempt to find clean copies amongst popular bios modding community members. So I attempted to use a much older version that supposedly works better on older systems, this time I actually reached a number 6 with a white blinking cursor, which is a sign that it's compatible however it never reached the Clover Menu which means I incorrectly flashed it. This seems to be an issue with the latest versions of Clover when attempting to boot on Legacy BIOS systems acording to one Clover user.
CLOVER EFI XEON 5660 WINDOWS 10
When using the latest version and flashing it via Rufus on a separate Windows 10 Machine, I couldn't get the Clover key to boot on my target machine, it kept leaving me at a white blinking cursor which is usually a sign that I either incorrectly flashed it or it's corrupted in some way maybe even not compatible with my system. Regarding Clover, I've been experimenting with it for a bit before I tried moving the Boot directory to a Separate flash drive.
Do such cards provide power and data transfer through the PCie lane? I didn't consider sata type b ssd's when planing the setup, now I kinda wish I did, I could switch gears if Clover doesn't work out. Unfortunately I don't have access to a 4th sata drive, I've got 3 sata bays going to a raid controller/backplane, 2 USB 2.0 Ports, 1 USB 2.0 Header, and 1 PCie 2.0 Slot.
CLOVER EFI XEON 5660 ISO
The only other thing I can think of is to continue attempting to get Clover to boot, if I can do that I can keep everything on the NVMe but it's questionable if that's worth my I'm planing to use the TrueNasCore Instance as a file host unrelated to my XCP-ng infrastructure, however I might consider using it as a ISO SR as well, otherwise using zfs on dom0 is a great idea, just isn't preferable for my use case. why?ĭo you have any suggestions on how I might be able to work around this? Are there any configuration files I can change to correct the mounts or am I stuck with having to reconfigure my drive setup? My first question is regarding the slight changes. Text is white and not bold with colorful font like the previous setup.Ĭonfiguration Screen has changed Resolution/aspect ratio, now it's 4:3 while before it was 16:9. When booting from a SATA SSD I've noticed some interesting changes which I've noted below.ĪCPI Error during boot (could you help me troubleshoot this?) Did some further testing as you suggested and your definitely bang on, it's a migration/mounting problem most likely caused by moving Grub and the Kernel to my Flash Drive.
0 kommentar(er)
