run fsck manually
-
E
VMs FS error after backup destination storage is full
Can it be so - NFS backup storage became full and VMs that was in this backup become with RO root partitions ?- emoxam
- Thread
- back up pve run fsck manually
- Replies: 4
- Forum: Proxmox VE: Installation and configuration
-
P
Filesystem failed
hello everyone When turning on my PVE, I had the following problem: I have used several FSCKs, but nothing works. Boot rescue does not fix the error. Have you ever had the problem? Do you know how to solve it? Thank you.- PCGaigher
- Thread
- disk error filesystem failed fsck run fsck manually
- Replies: 0
- Forum: Proxmox VE: Installation and configuration
-
C
[SOLVED] Proxmox start nicht mehr
Hallo, bin schon am verzweifeln, mein proxmox startet nicht mehr es bleibt mit folgenden bild hängen. Habe dann alle möglichen Befehle gestestet auch per live cd und es läßt sich nicht reparieren. Siehe z. B.- Cels
- Thread
- critical logical run fsck manually superblock umount
- Replies: 11
- Forum: Proxmox VE (Deutsch/German)
-
J
pve-cluster will not start after additional RAID1 storage upgrade
Hello everybody, today my PVE host received an additional RAID1 storage upgrade. Before the update, I had 2 x 240 GB SSD as Hardware-RAID1 (Adaptec controller). To that controller, another 2 x 480 GB SSD as Hardware-RAID1 were added. Ever since the upgrade was done, my pve-cluster will not...- JS1
- Thread
- /dev/mapper/pve-root /var/lib/pve-cluster/config.db config.db-wal contains a file system with errors incorrect filetype memdb_open failed run fsck manually unable to open database unable to set wal mode unexpected inconsistency
- Replies: 3
- Forum: Proxmox VE: Installation and configuration