On checking the dashboard of my repeater this morning only ID numbers were being displayed, which has been normally a failure to update the first time correctly. However running the update this morning produced this log.
Stopping Services...
Done
Updating DV Binaries...
No updates for /usr/local/bin available
Done
Updating Pi-Star Binaries...
Updating /usr/local/sbin...
error: bad signature
fatal: index file corrupt
Updates were not successfull, reverting to Pi-Star original files...
error: bad signature
fatal: index file corrupt
Done
Updating Hostfiles...
Done
Updating Dashboard...
Updating /var/www/dashboard...
fatal: fsync error on '/var/www/dashboard/.git/objects/pack/tmp_idx_ADoTqa': St$
fatal: index-pack failed
Updates were not successfull, reverting to Pi-Star original files...
HEAD is now at 811c35d Update version.php
Done
Updating PiStar-Firewall...
Done
Starting Services...
Done
Updates complete, sleeping for a few seconds before making the disk Read-Only
Finished
Any pointers?
Nightly Update - 25/26-1-2021
Re: Nightly Update - 25/26-1-2021
This is first occasion that this has occurred.
However it has been running continuously for over two years on this RPI 3A+.
I tried a small tweak on the MMDVMHost yesterday on the offsets and the system would not return to the dashboard, lost it's repeater status, and generally went into a sulk, so I rebooted it and it returned to where it had been previously, without the tweaks. So I left it alone as it was otherwise working. Perhaps the SDCard is giving me an early warning.
However it has been running continuously for over two years on this RPI 3A+.
I tried a small tweak on the MMDVMHost yesterday on the offsets and the system would not return to the dashboard, lost it's repeater status, and generally went into a sulk, so I rebooted it and it returned to where it had been previously, without the tweaks. So I left it alone as it was otherwise working. Perhaps the SDCard is giving me an early warning.
Re: Nightly Update - 25/26-1-2021
That is certainly possible
Re: Nightly Update - 25/26-1-2021
Just to make it quite clear, that it was the operating system on the SDCard that had become corrupted, firstly preventing the nightly update from writing new data to the data files, then completely failing when I tried to make the adjustments to the card, the extent that attempting to reformat the card also failed, as it had become completely unwritable.
A new card was procured, formatted, written, installed and configured within an hour and everything is now fully operational. Thanks to the input from Andy - I'm well pleased.
A new card was procured, formatted, written, installed and configured within an hour and everything is now fully operational. Thanks to the input from Andy - I'm well pleased.