Hello Adam,
perfect, that’s what I wanted to see (and thank you for the confirmation that the other Shakes are working nominally).
As you have surely understood, this is what normal files look like, and there is an evident issue with the configuration of the first Shake. We can try a last thing before resetting everything:
please open the dhcpcd.conf file with
sudo nano /etc/dhcpcd.conf
and delete all the lines that start with static, thus leaving only interface eth0. Do not modify anything else.
Then do:
sudo service dhcpcd restart
to make sure those changes took hold and then check the output file with
nano /etc/resolv.conf
The file should look like the one from your working Shake.
If it doesn’t, then a reset is the best option left on the table. I can advise to:
- re-burn the ShakeOS on your current microSD card
- or get a new microSD (to erase the chance that this one got ruined) and burn the Shake OS there.
I know that this means to retrieve the Shake from its remote location, or going there personally, but there is no other way of correcting this via remote actions.
In both mentioned cases, these are the instructions to prepare the new OS image:
- Please take the microSD card you have and format it before burning the new Shake OS image
- Make sure, when you format it, that the shown capacity is the maximum (i.e. if the SD card is 32GB like yours, then the capacity should be near or equal to that value). This is to check that no partitions have been involuntarily and erroneously created. They could be the cause of the error we see now
- Take care to format the SD card in a FAT32 File System (or exFAT if the SD card is 64GB or larger)
- Download the new Shake OS image from here: https://gitlab.com/raspberryShake-public/raspShake-SD-img/raw/master/raspishake-release.zip
- And follow the microSD burning instructions from here: raspishake-microSD-card-software-Instructions.txt · master · raspberryShake-public / raspShake-SD-img · GitLab
I followed the numbered list points to burn the files on my SD cards, and I have not used Etcher or similar software.