UtterDisbelief Goes Small - NUC10 i5 UHD630 32GB

[UtterDisbelief]

Well this is new...
As soon as I removed the USB I use to configure it, it wont boot to the internal SSD.

I put the USB stick back in and it works..., it looks like something funky with the boot loader , needing to be on the USB to kick start the loading from the SSD.

If it's the original EFI folder you have transferred to the SSD EFI partition, then it sounds like the drive might be formatted incorrectly or corruption has occurred. Otherwise ZIP and attach the SSD EFI folder so we can check it?

 

[hardcorefs]

I just spent the worst afternoon with a clone....

The NUC just kept saying "no bootable devices found" even though I re-did it a number of times & followed the article.

In the end I suspected faulty hardware, since it was showing the SSD in the BIOS,
but saying not bootable.

So I installed Win 10 and it worked first time... and would boot.

So even when I put the OC & boot folder back in, it went directly to the Windows boot.

folders were
APPLE OC BOOT MICROSOFT
so I renamed the folder "Microsoft" to "zmicrosoft"

same boot problem. "no bootable device"

I renamed the zmicrosoft back to microsoft; and
then I copied the "BOOT" folder again".

It still booted back into MS.
Finally, I went into the MS folder and removed the *.EFI" files,
and bizarrely it now is booting correctly, without a USB and directly into the macOS.

And the EFI partition folder is now called "no name" and works perfectly.

So.....

As regards to your files , corrupting... nope .. I used MD5 to check them all, and they were fine.
What I copied was the same checksum, both sides.

And, if it was the format of the EFI partition being wrong, then it would not boot the Windows...

It's clearly some incompatibility with the NUC boot.
But there is no debug at this stage of the boot process.


anyway ... ill leave it over night, then gradually delete stuff that does not belong in the EFI partition.

 

[Feartech]

I just spent the worst afternoon with a clone....

The NUC just kept saying "no bootable devices found" even though I re-did it a number of times & followed the article.

In the end I suspected faulty hardware, since it was showing the SSD in the BIOS,
but saying not bootable.

So I installed Win 10 and it worked first time... and would boot.

So even when I put the OC & boot folder back in, it went directly to the Windows boot.

folders were
APPLE OC BOOT MICROSOFT
so I renamed the folder "Microsoft" to "zmicrosoft"

same boot problem. "no bootable device"

I renamed the zmicrosoft back to microsoft; and
then I copied the "BOOT" folder again".

It still booted back into MS.
Finally, I went into the MS folder and removed the *.EFI" files,
and bizarrely it now is booting correctly, without a USB and directly into the macOS.

And the EFI partition folder is now called "no name" and works perfectly.

So.....

As regards to your files , corrupting... nope .. I used MD5 to check them all, and they were fine.
What I copied was the same checksum, both sides.

And, if it was the format of the EFI partition being wrong, then it would not boot the Windows...

It's clearly some incompatibility with the NUC boot.
But there is no debug at this stage of the boot process.


anyway ... ill leave it over night, then gradually delete stuff that does not belong in the EFI partition.

normally your EFI partition will have a folder called EFI inside and in that would be the 2 folders OC and BOOT....

 

[UtterDisbelief]

As regards to your files , corrupting... nope .. I used MD5 to check them all, and they were fine.
What I copied was the same checksum, both sides.

Curious. I don't think I offered an MD5 checksum to verify the files. What happens locally, of course, I can't help with.

And, if it was the format of the EFI partition being wrong, then it would not boot the Windows...

Not quite.

Windows does not have the same EFI partition size requirement as macOS does.

It's clearly some incompatibility with the NUC boot.

No evidence of that here, unfortunately. However you have to be careful with the BIOS settings as it was initially tricky to iron-out those for sleep/wake.

anyway ... ill leave it over night, then gradually delete stuff that does not belong in the EFI partition.

Good luck.

 

[hardcorefs]

Yep... it's not the first clone I have built , this is what is so insane, there is nothing normal about this.
But after 12 hours It's still fine.
I'm going to start to try and clean it up...
I bought the NUC real cheap brand new, from clearance, fully sealed.

I'm going to try and re-install montery over the current montery, see if that blows the cobwebs out...

 

[Feartech]

Yep... it's not the first clone I have built , this is what is so insane, there is nothing normal about this.
But after 12 hours It's still fine.
I'm going to start to try and clean it up...
I bought the NUC real cheap brand new, from clearance, fully sealed.

I'm going to try and re-install montery over the current montery, see if that blows the cobwebs out...

the EFI partition would normally be named EFI

 

[hardcorefs]

OK! I updated to the latest Monterey.
Yep, ref EFI....... "one 'thing' at a time sweet Jesus......"

The latest Monterey went in clean.
I removed the Apple folder in the EFI & its still OK. No changes to the other files.

I'll slowly clean up over the next few days.

One interesting thing is the main macOS disk was named "details2", and the EFi boots to "details2"

I renamed the drive on macOS to "boot",
and the osx startup drive in system shows this.

But in the EFI , it's still called "details2" , but boots fine.

 

[UtterDisbelief]

Hey! Don't worry about your feedback delay. Thanks! My errors I only see in the System Report, otherwise NUC starts and works. I still have a few things to clarify. Then I will let you know what and how, of course, if you/or anyone else is interested.

P.S. As I read, do you think, that the hackintosh will survive Apple invasion, that they constantly working to eliminate old hardware from macOS?

I plan on keeping my NUC running macOS whatever Apple decides to do! If they stop it accessing iCloud, that's no problem for me. There are other online services. If we can only go as far as Sonoma then we should still have three more years of security updates (unless Apple stops that). When Safari starts to become old and insecure along with Google Chrome or Edge, and no longer supported, I will perhaps dual-boot Chrome OS Flex because the NUC runs that very, very well. But I expect that to be a few years away just yet.

 

[UtterDisbelief]

but on Sonoma, we have problem with WIFI

I don't.

Works fine with alpha itlwm.kext

 

[UtterDisbelief]

but it will work litle with the lower speed transfer

Well at least we have functionality from the Intel wireless chipset since Sonoma, thanks to OpenIntelWireless, otherwise our NUC PCs would have to use Ethernet only.