I don’t really know, but I’m thinking that when doing the initial install attempt, you might have reformatted the 128 m2 as part of that process. If so, you might have lost something on that drive that is needed.
Again, someone who knows will respond, I hope. You might want to post this in the Support forum.
Sorry if I sounded blunt, I am Autistic and was really fed up and my social niceties sometimes are not the best.
The first question is what is the correct boot order.
I have a M2 and SSD 1tb for my music.
Second is what does the software get installed onto? My guess is the M2.
Third - the left side of the text was missing on my tv for some reason. So I guessed. Incorrectly.
Forth, when the installation of the software ends, it says you will get an IP address, but nowhere in the docs does it state plug in a network cable during this part of installation. So originally I didn’t get an IP address. But managed to find the Ip with software.
So basically this worked but the drives were the wrong way around. The m2 was way too small for my collection.
But the Rock showed on my Mac when I went to continue the installation.
So I started again. Trying to do the same, but the software installed onto the correct drives. When you finally finish and it asks you to reboot there is no message about ip address, just some programming on screen.
When I finish and attach to my router, there is no sign of the Nuc. No ip address or anything.
If you have a tablet or phone install a program called Fing on it. It will look on your network and find all of your devices network addresses including your nuc/rock.
This will allow you to complete the steps.
As to the instructions, they are clear if you know what you are doing and I guess the thought is if you didn’t know what you were doing you would be unlikely to try doing it
But like nearly all technical documentation there is assumed knowledge.
Fing is an essential tool if you have a home network. So useful if you have an issue.
Just this morning I couldn’t get into Roon. Then couldn’t get to Nas either. So opened Fing and NAS was not discovered, checked it was on and running upstairs which led me to Re Boot the switch.
Result, all up and running again.
In your case I would start with the basics of troubleshooting.
First I would count my blessings one by one: your BIOS is working and you had been able to install ROCK once and it had operated while showing a wrong operating drive.
Then I would affix a screen to the HDMI port of the NUCK and having done this, I would enter the BIOS by using the keyboard key (read the online? manual of your NUC) directly after starting the NUC.
In the BIOS I would check the status of both drives, to notice which drives are bootable and what is the booting order of both drives. The BIOS may well show that both drives are bootable and the first bootable drive is still 1tb drive without Operating system: in that case your NUC will wait endless for ROCK to start. If so: change the boot-order of both drives. In case ROCK works fine: happy/lucky you.
If this doesn’t work, I would consider a probing tool. In this case a bootable USB stick containing Ubuntu or another Linux version (there are many sources on internet to make one). With this USB-stick in an USB-port of the NUC and changing the boot-order in the BIOS to USB-first, I would restart the NUC. Ubuntu will start from the USB-stick and I would be able to see the content of both internal drives.
If ROCK is installed on 128 MB drive and this drive is not bootable, I would look how to make this internal drive bootable on internet. If you have succeeded making the 128 MB drive bootable and ROCK is still on this drive, I would shut down the NUC, remove the USB stick and restart the NUC and immediately enter the BIOS to change the boot-order to the 128 MB drive first. Restart the NUC and if ROCK starts correctly, you will be relieved.
If not, I would start considering to fully reformat both drives and start anew.
I would follow this basic troubleshooting order in your case.