Have you been doing any commands as root?
For example especially trying to run scripts that change things on VRRP etc transition?
show kernel log might give you some helpful information as to what has happened if there’s been a disk problem causing the filesystem to go read-only.
Based on those errors I’d assume you’ve had some sort of disk error.
Is this running a VM, have you migrated the instance or something similar?
Best course of action might be to copy the configuration off the box using
tim@ferrari# save
Possible completions:
<Enter> Save to system config file
<file> Save to file on local machine
scp://<user>:<passwd>@<host>:/<file> Save to file on remote machine
sftp://<user>:<passwd>@<host>/<file> Save to file on remote machine
ftp://<user>:<passwd>@<host>/<file> Save to file on remote machine
tftp://<host>/<file> Save to file on remote machine
so you’ve got the config backed up somewhere, then reboot.
And try to figure out what happened to your router to cause it to have disk problems.
Not cusom version. Actually I install VyOS in kvm. then dd create the disk to recovery on vps. It works for a long time. But recently days the vps host has hardware error. After they recoveried the vps. it has such error like these. Maybe I might try to restore the vps with vyos again.
You should be able to recover older config from the persistence path (each installation got its own subdir which is copied when system upgrade occurs so the old stuff remains untouched) and most likely do a fresh install if possible.
My question regarding custom version is that your overlayfs sseems to want to go for “/boot/1.3.4-new/rw” which looks odd to me (but I have only been using 1.4 and 1.5 so perhaps thats a 1.3 thingy to have the path named that way).