I have a stand alone proxmox node running 6.0 or 6.1, I am not sure.
When I checked my nas for the vzdump backups, I realized, the vm was not backed up for 3 days. Then I tried to connect to web gui. Could not connect.
I couls ssh in to it. Saw /etc/pve empty. However, my vm is hosted on a different ssd drive other than where I installed proxmox. Therefore the vm is running fine.
However, I cannot run vzdump even manually.
When I run
systemctl status pve-cluster, I get " pve-cluster.service: Start request repeated too quickly." unable to start proxmox cluster file system.
One of the lines of output of " journalctl -b -u pve-cluster" is "[main] crit: unable to create lock '/var/lib/pve-cluster/.pmxcfs.lockfile': Read-only file system"
/etc/hosts is also correctly formatted.
pveproxy service cannot be started.
pvedaemon.service is Active
CGroup: /system.slice/pvedaemon.service
├─ 1226 pvedaemon
├─ 6874 pvedaemon worker
├─10463 pvedaemon worker
└─28498 pvedaemon worker
I dont know what to do.
Please advise.
When I checked my nas for the vzdump backups, I realized, the vm was not backed up for 3 days. Then I tried to connect to web gui. Could not connect.
I couls ssh in to it. Saw /etc/pve empty. However, my vm is hosted on a different ssd drive other than where I installed proxmox. Therefore the vm is running fine.
However, I cannot run vzdump even manually.
When I run
systemctl status pve-cluster, I get " pve-cluster.service: Start request repeated too quickly." unable to start proxmox cluster file system.
One of the lines of output of " journalctl -b -u pve-cluster" is "[main] crit: unable to create lock '/var/lib/pve-cluster/.pmxcfs.lockfile': Read-only file system"
/etc/hosts is also correctly formatted.
pveproxy service cannot be started.
pvedaemon.service is Active
CGroup: /system.slice/pvedaemon.service
├─ 1226 pvedaemon
├─ 6874 pvedaemon worker
├─10463 pvedaemon worker
└─28498 pvedaemon worker
I dont know what to do.
Please advise.