Search results

  1. All CT turned to Read only file system

    The line 63 is in bold below : if [ -z "${CONSOLETYPE:-}" ]; then if [ -c "/dev/stderr" -a -r "/dev/stderr" ]; then CONSOLETYPE="$(/sbin/consoletype < /dev/stderr 2>/dev/null)" else CONSOLETYPE="serial" fi # stat /dev/stderr Fichier : « /dev/stderr » -> «...
  2. All CT turned to Read only file system

    ip r returns same thing that other CT that works correctly. Something is broken in the CT and I can't repair it. All errors I get when I run basic commands like below make me hopeless. I thought maybe rights on a directory had to be corrected somewhere... I have to resign to lose the 2 CT :( #...
  3. All CT turned to Read only file system

    Well I can ping only the gateway and other ip in the same vlan.
  4. All CT turned to Read only file system

    # ip a 1: lo: <LOOPBACK,UP,LOWER_UP> mtu 65536 qdisc noqueue state UNKNOWN group default qlen 1000 link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00 inet 127.0.0.1/8 scope host lo valid_lft forever preferred_lft forever inet6 ::1/128 scope host valid_lft forever...
  5. All CT turned to Read only file system

    The CT is unreachable (no ssh, no ping, not a firewall problem). When I restart network I get : # service network restart /etc/init.d/functions: ligne63: /dev/stderr: Permission non accordée /etc/init.d/functions: line 63: /dev/stderr: Permission denied Restarting network (via systemctl)...
  6. All CT turned to Read only file system

    When I start the CT with debug I can see problem with cgroups. But I have no idea how to fix it. lxc-start 100 20220330094646.174 DEBUG conf - conf.c:idmaptool_on_path_and_privileged:2741 - The binary "/usr/bin/newuidmap" does have the setuid bit set lxc-start 100 20220330094646.174 DEBUG...
  7. All CT turned to Read only file system

    At the begining the CT was on a PVE3. The CT has been backupped and restored on this PVE6. All worked fine for the 3 CT until a few days for the 2 CentOS 7. The error with venet0 has been fixed (maybe due to multi add/delete eth). But the main problem is how to fix all the errors "Failed to...
  8. All CT turned to Read only file system

    The container starts but no network. And restarting services returns permission error I didn't have before. Example with httpd : # service httpd restart /etc/init.d/functions: ligne63: /dev/stderr: Permission non accordée Redirecting to /bin/systemctl restart httpd.service Restarting network...
  9. All CT turned to Read only file system

    I added "nesting" with CT off. Then I started and rebooted CT but no change.
  10. All CT turned to Read only file system

    Unfortunatly this did not fix the problem. Still same errors in /var/log/messages and no service works... :( The strangest is the problem seems to occur on the 2 CentOS7 CT in the same time (90% sure). And why didn't it affect the debian CT ?
  11. All CT turned to Read only file system

    Ok and how can I turn on "nesting" please ?
  12. All CT turned to Read only file system

    Not sure that's what you requested... # cat /etc/pve/local/lxc/100.conf arch: amd64 cpulimit: 1 cpuunits: 1024 hostname: vm.xxxxxxx memory: 4096 net0: name=eth0,bridge=vmbr0,gw=123.123.123.254,hwaddr=8E:E2:49:BF:6B:05,ip=123.123.123.15/24,type=veth ostype: centos rootfs...
  13. All CT turned to Read only file system

    There is no such parameter for container. The read only file system occurs only with CentOS 7 container. No problem with Debian container and VM.
  14. All CT turned to Read only file system

    I definitely not have high i/o on the pve. If I start only 1 CT (CentOS7) the problem continues. I suppose an update of PVE6 is the cause but i can't prove it.
  15. All CT turned to Read only file system

    Talking to myself... The problem seems to be related only to CentoS CT. No problem with Debian. Is there a (new) bad compatibility PVE 6 / Centos 7 ?
  16. All CT turned to Read only file system

    Even though I backup CT and restore on another PVE I still have the read only problem. Nothing work ! Mar 26 15:10:53 vm systemd-sysctl: Failed to write '0' to '/proc/sys/kernel/yama/ptrace_scope': Read-only file system Mar 26 15:10:53 vm systemd-sysctl: Failed to write '16' to...
  17. All CT turned to Read only file system

    Not a space problem. # df -h Filesystem Size Used Avail Use% Mounted on udev 5.9G 0 5.9G 0% /dev tmpfs 1.2G 8.9M 1.2G 1% /run rpool/ROOT/pve-1 404G 192G 212G 48% / tmpfs 5.9G...
  18. All CT turned to Read only file system

    Hello, I use PVE 6.4 and today I found errors in /var/log/messages of a CT like : vm systemd-sysctl: Failed to write '0' to '/proc/sys/kernel/yama/ptrace_scope': Read-only file system Finally I found same errors on others CT (only 3 CT running + 1 VM on this single node, no cluster). I...
  19. DiskIO in CT missing

    About 18 months after bug report there is still no fix (pve 6.4) :(

About

The Proxmox community has been around for many years and offers help and support for Proxmox VE, Proxmox Backup Server, and Proxmox Mail Gateway.
We think our community is one of the best thanks to people like you!

Get your subscription!

The Proxmox team works very hard to make sure you are running the best software and getting stable updates and security enhancements, as well as quick enterprise support. Tens of thousands of happy customers have a Proxmox subscription. Get your own in 60 seconds.

Buy now!