@gyq just an idea, can you try using the keyboard to see if that works, Alt+(underlined letter).
Of course you will have to run the installer somewhere else to see what you have to press in the real server
In case you want to use the rsync method, the rsync options which have served me well over the years are:
# rsync -XxAaPSH src/ dest/
I know some options are "optional", I just use that string for an easy mnemonic.
Try the file '/etc/issue' which can be recreated from a post up network script (it works on Ubuntu 16, dunno if the necessary packages are installed on vanilla Debian)
If you just want to find which file, grep inside "/etc"
Assuming this is the screenshot after you do an SSH into the machine d2 ...
are you able to "touch" a file named 'forcefsck' like so:
If the 'touch' command doesn't work...
Hi, some thoughts which come to mind ...
I assume you have rebooted the server, its worth a try.
Else, could you try booting into the previous kernel and try
BTW, "read-only filesystem" smells of probably an "fsck needed" on the underlying file system.
Can you do a forced fsck on the...
Having some sort of "autoscaling group" functionality would be a great addition to Proxmox.
Of course, to keep the semantics similar to a "cloud platform", what would be useful is to be able to create a VM/LXC from a remote image url.
I have home-grown scripts which download the image...
I know the problem description seems unbelievable but its true ... "works via GUI, but not from commandline". :eek:
FWIW, I keep these servers updated every week or so, I'll check if the commandline problem is reproducible after a reboot (i.e. using the latest installed packages)
Yes, the first restore is still running, and this is expected.
The problem is that the second restore times out within a few seconds.
What is weird is that if I restore using the WebGUI, the second job correctly keeps spinning on "waiting for lock ..."