EXT4-fs (dm-1): Remounting filesystem read only

[SirMarco]

I don't think that's good

 

[waltar]

Try to repair as shown but definitive get a new nvme and switch over by copies or backup.

 

[wokkie]

I had the same error in my lxc. Showing this error on my PVE node:
journalctl -xe -p 3 --no-pager gives me

 Mar 10 08:42:33 pve kernel: loop: Write error at byte offset 38420480, length 4096. Mar 10 08:42:33 pve kernel: I/O error, dev loop4, sector 75040 op 0x1:(WRITE) flags 0x3800 phys_seg 1 prio class 0

The LXC only had mount points, but on the host something was writing data an drive was almost completely full. I've now free'd up 100GB. Let's see if that works.

The drive itself should be fine. It's just a month old and the other LXC using a different mount on the same drive has 0 issues.

Update: 3 days without issue now.

 

[rian81]

Please don't use truenas, i had bad experience when integration truenas and pve or pbs, after a few days the connection seem restart from truenas side. So on pve or pbs will get "readonly disk". When reconnect, the lun disk will connect, but it will happen again and again after few days. I connect use iscsi mode

I am new to proxmox and servers. I installed proxmox on my ibm system x3550 m4 server. and installed truenas on it. I did PCI passthrough and turned on truenas. immediately my proxmox showed connection error and in cli it displayed
"EXT4-fs (dm-1): Remounting filesystem read only "
if I try to type something it says :
"-bash: /usr/bin/ls: Input/output error "

what should I do now

 

[buttonpresser]

I ran into this issue and after an hour of panic I figured out the solution. SimIar to you, I mistakenly passed through my boot drive and faced immediate failure while configuring truenas.

Resolution:

• Enter recovery mode (via grub or ISO)
• Run

  pmxcfs

• navigate to /etc/pve/qemu-server

  cd /etc/pve/qemu-server

• Open the offending VM in a text editor (vim/nano)
• Set "onboot" to "0"
• Reboot (Should load normally)
• Remove the PCI passthrough configuration
• Live to fight another day

TLDR; Login to recovery mode and disable the auto boot for the VM causing issue. If the VM isn't on it won't hijack the PCI device and crash the system.

 

[VinnyG]

I ran into this issue and after an hour of panic I figured out the solution. SimIar to you, I mistakenly passed through my boot drive and faced immediate failure while configuring truenas.

Resolution:

• Enter recovery mode (via grub or ISO)
• Run

  pmxcfs

• navigate to /etc/pve/qemu-server

  cd /etc/pve/qemu-server

• Open the offending VM in a text editor (vim/nano)
• Set "onboot" to "0"
• Reboot (Should load normally)
• Remove the PCI passthrough configuration
• Live to fight another day

TLDR; Login to recovery mode and disable the auto boot for the VM causing issue. If the VM isn't on it won't hijack the PCI device and crash the system.

Thanks
saved my ass when migrating my nvme install to another laptop