mesg: change /dev/pts/10 mode failed: Read-only file system

encore

Well-Known Member
May 4, 2018
108
1
58
36
Hi,

getting
mesg: change /dev/pts/10 mode failed: Read-only file system
on a pve node. Some CTs do not start. After a reboot it works for some time then it happens again.
What could be the reason? FS errors on the root disk?

Thank you
 
ooo I get exact same issue. Been struggling with this one.

mesg: change /dev/pts/4 mode failed: Read-only file system

Really not sure what is the cause. Thought I was alone :)
 
I noticed this was mount read only on the problem node:

devpts on /dev/pts type devpts (ro,nosuid,noexec,relatime,mode=600,ptmxmode=000)

whereas this is rw on a node working fine:

devpts on /dev/pts type devpts (rw,nosuid,noexec,relatime,gid=5,mode=620,ptmxmode=000)
 
I noticed this was mount read only on the problem node:

devpts on /dev/pts type devpts (ro,nosuid,noexec,relatime,mode=600,ptmxmode=000)

whereas this is rw on a node working fine:

devpts on /dev/pts type devpts (rw,nosuid,noexec,relatime,gid=5,mode=620,ptmxmode=000)
Did changing it to rw helped?
 
Getting closer.

I ran this :

mount -t devpts -o remount,gid=5,mode=620 devpts /dev/pts

and now it doesnt say read only but getting new error now which made me think some stale things still left behind.

So I ran
find /sys/fs/cgroup/*/lxc/113* -type d | tac | xargs rmdir

where 113 is the container ID and not I started it and all is good again in the world :)

Probably some bug somewhere.
 

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 yours easily in our online shop.

Buy now!