Taking a look at the docs only this looks possibly relevant, use with care and make sure you select the right disk number. The instructions are from the bottom of this doc:
Run the following command in Terminal.app, replacing N by the corresponding disk number, which you can find by running diskutil list:
According to all of your screen shots the flash stick is disk2 butl do double check, those ids for removable drives can change. After that repeat the etcher burn.
Iām now exploring the ROCK/NUC build posts and there are reported instances where the UEFI boot priority must be changed to Legacy Boot (for a ROCK install). Iām quite out of my element with PC hardware/software configuring so I plan to read more before changing any BIOS settingsā¦but maybe this is the way forward? I seem to have lost my support guyās attention. Would love to hear from anyone who understands this environmentā¦
You didnāt lose my attention, Iām just catching up after being out of the office yesterday.
In reading through things I can only see one thing to look into. For your screenshot showing the erase of Generic Flash Disk Dedia, change that format to exFAT. Itās perfect for the Linux box. If APFS is selected Iām betting thatās the issue.
After that, I may need to seek help from others. I have a Roon Core on Mac, Roon Server running on Mac, a Nucleus, Roon Server running on Windows 11, and an all-in-one core on Windows 11. But no ROCK so no hands-on experience with the process.
Thanks, Wes. That was just a screenshot I grabbed before selecting ExFAT (as APFS is only for Apple). Unfortunately, the USB flash formatting doesnāt seem to be the issue. Iād like to try changing the BIOS settings, to see if the boot priority (UEFI vs. Legacy) is the issue (as has been reported with some of the ROCK builds), but I hate to start pushing buttons in an unfamiliar environment. Is there someone in support I could follow up with that is experienced with BIOS settings for a Nucleus M.2 flash?
I have to say that that āSelect targetā screenshot of Balena Etcher looks very odd indeed.
Iām not seeing the USB stick that you presumably plugged in listed, Iām only seeing the Macās system drives.
By way of comparison, hereās the equivalent screenshot of Balena Etcher running on my Windows PC. Note that the USB stick is explicitly listed. I actually had to click on the āShow hidden drivesā option to show the system drives in my PC. By default these would be hidden.
Thank you, everyone. I did buy a new 128GB USB stick, which produced the same failed reboot result. I then tried one of the BIOS protocols from a ROCK build post (selected UEFI and booted from the USB) and was almost successful (see photo). I finally produced a ROCK install screen!..but unfortunately in the process I seem to have disconnected the keyboard. And the on/off switch. Iām unable to do anything now. Currently dead in the water. Any ideas?
Wired. USB port. I was locked out, so I disconnected the power supply and now have this screen. Current status: afraid to type anything. Hoping/waiting for someone that knows a bit about what I should do next. Fingers crossed.
Youāve simply booted into the EFI shell, thatās possibly inadvertently selected. Typing reset -c should get you a reboot. You canāt go too far wrong powering down from these early boot states if youāre really stuck. A long (5 secs) press of the power button usually does the trick. If it doesnāt pulling the plug never fails AFAIK.
Update: I can now successfully boot from the USB and produce the ROCK install menu!
Unfortunately, when I do (boot from USB), the keyboard is disabled. If I could just press"1" and āenterā I think Iād be in the home stretch. Alasā¦
Oddly, in this state the Nucleus on/off button is also disabled.
Iāve started a 2nd support post to see if I can get lucky and find someone whoās dealt with this situation. Iāve learned quite a lot this weekend about PCās, NUCās, the BIOS interface, USBās, SSDās, etcā¦ but I currently have no idea how to reconcile this.
So presumably the keyboard works properly up to this point and then nothing works? Try simply unplugging the keyboard and plugging it in again, that may allow it to be recognised. Just to be sure, what model of keyboard are you using? I doubt itās an issue but Iād like to rule out anything āexoticā as it were. BTW is the cursor flashing at all?