Search results
-
X
[SOLVED] Dirty inode writeback failed
Fixed ;) Not enough space for work the container. Maybe too much alcohol for Christmas ;) Thanks- xmickaelx
- Post #3
- Forum: Proxmox VE: Installation and configuration
-
X
[SOLVED] Dirty inode writeback failed
Nobody for helping on this ?- xmickaelx
- Post #2
- Forum: Proxmox VE: Installation and configuration
-
X
[SOLVED] Dirty inode writeback failed
Dear All, I'am not able to start my container : pct start 100 Job for lxc@100.service failed. See 'systemctl status lxc@100.service' and 'journalctl -xn' for details. command 'systemctl start lxc@100' failed: exit code 1 journalctl -xn -- Logs begin at mar. 2017-12-26 16:14:01 CET, end at...- xmickaelx
- Thread
- Replies: 2
- Forum: Proxmox VE: Installation and configuration
-
X
PROXMOX 5 - Ubuntu 16 - Rescue Mode
Dear all, I enable the firewall on my dedicated server : PROXMOX 5 - Ubuntu 16 - Rescue Mod It was a big mistake and now, i'am not able to access over ssh. I mount partition on rescue mode but impossible to find how to disable the firewall. Someone can help me ? Regards, Mickaël- xmickaelx
- Thread
- Replies: 0
- Forum: Proxmox VE: Networking and Firewall