A totally headless, no GUI, INDI server?
Another suggestion is to create a file in the root directory using command : sudo touch /forcefsck
When the Pi boots then the file is recognized and a forced fsck is done and the file is removed.
It won't hurt to run that at every bootup so you can put the command (without 'sudo') in the system crond configuration file, then the file is created at every boot.
RPi3, Ubuntu Mate, and many Arduinos..
systemctl set-default multi-user.target # next boot will be in text mode ( equ. runlevel 3 )
or, if you decide to go back to graphical mode :
systemctl set-default graphical.target # next boot will be in graphical mode ( equ. runlevel 5 )
As long as you have an ssh cnx you can swap at will between th two modes
PS : Actually, I also bring a second Pi. You're never too prudent when your night relies on this little buddy.
So you can either install Debian or Ubuntu server on the Pi, and just install INDI server there. Or if you want to use GUI-OS like StellarMate, you can do as Marc suggested above which is to set the run level to 3 to prevent going to GUI mode. Btw, SM OS already forces fsck on boot if it detects issues. What version were you running?
RonK wrote: Okay, actually I've already got a Raspberry Pi 3 with Stellarmate on it and it's connected to my MacBook through WiFi. It all works nicely… until I unplug the Raspberry Pi by accident and it doesn't start anymore. The reason why it doesn't start anymore is that the OS on which Stellarmate is built is a GUI-based OS.
What happens after a hard reboot is that, at times, it requires a fsck to be performed, but it won't do it all by itself. It's gonna to ask. One needs to type Ctrl-D, because it expects to be plugged to a monitor and a keyboard since it's a desktop environment.
Please note that this problem has nothing to do with 'desktop' or 'gui'. So especially the answers suggesting to switch to runlevel 3 / text mode won't help anything, you'd run into the same error again as it happens way before any desktop environment is started.
It is the initial system startup script that would (try to) run the file system check. And usually, it does this with the option '-y' to run unattended (for filesystems that support this).
As Jasem mentioned, the automatic fsck is already done in SM, so it might well be that in your case you did hit an error that fsck could not fix. Then of course (also) a headless system is at the loss (unless it has something like automatic restore from a separate partition).
Thus my question, is there a simple, no-fail, INDI server out there that won't let me down if I unplug the power cable by mistake? I don't care about any GUI interface on the device that runs the INDI server, I never use it. GUIs suck.
I'd just always carry a second SD card with a backup with me.....
GPDX+EQMOD, CEM60EC, ASI1600+EFW+EAF+ASI290 mini
Right, but considering Ubuntu has most probably a journaling filesystem, this shoud not even happen and a power loss shouldn't do much damage... Those days when a power loss on Unices systems was a catastrophe are long gone . If fsck could not fix the problem, maybe it's because the card itself has been corrupted ?
I always run RealVNC next to Kstars on my laptop just to start other programs on my Pi....
aj55 wrote: But perhaps VNC is also stuck on the Pi in the situation you mention?
Yes, it happens before the VNC service starts.
aj55 wrote: Out of curiosity, how do you shutdown the Pi without VNC?
Is it possible from Kstars on your laptop?
I do that either with VNC or through Stellarmate's Web interface.