Error 500: unable to open file '/var/tmp/pve-reserved-ports.tmp.846' - Read-only file system

[Kacperro]

Hello,
I know there have been a few threads like this, but none of them solved my problem.

Two months ago, after installing proxmox and installing only HomeAssistant on it with 32GB of memory allocated (which was not completely filled), I got the error: Error 500: unable to open file '/var/tmp/pve-reserved-ports.tmp .846' - Read-only file system. I tried the methods from several threads that you describe on this forum and other sites - unfortunately I gave up and decided to reinstall the entire system and start from the beginning.

Unfortunately, after reinstalling and a month of proxmox, this error returned again. I assume that I must have something wrongly set or some temporary / dynamic memory is clogged? I think so because I can't download files on home assistant.

I can use the console for a while after restarting proxmox, then it shows Error 500: unable to open file '/var/tmp/pve-reserved-ports.tmp.846' - Read-only file system.

df - h:

df -h /var/tmp:

mount:

smartctl -a /dev/sda - in attach files.

ncdu/:

fsblk -f:


trying to scan and fix possible errors:
sda1


sda2:

I can remove the dirty bit, but I would like to get rid of the configuration problem and otherwise heal the system..

sda3:

 

[fiona]

Hi,
can you share the system logs/journal from around the time the issue happened (more is better)? Also note that /dev/sda3 does not contain a file system itself. It belongs to LVM and the file system is rather on the pve-root logical volume and you'd need to check that (from a live CD).

 

[Kacperro]

I sent in an attachment.

 

[fiona]

You got ATA requests hitting a time out:

Aug 22 21:45:22 proxmox kernel: ata1.00: exception Emask 0x0 SAct 0x1c01c SErr 0x0 action 0x6 frozen
Aug 22 21:45:27 proxmox kernel: ata1.00: failed command: WRITE FPDMA QUEUED
Aug 22 21:45:27 proxmox kernel: ata1.00: cmd 61/18:10:20:69:58/00:00:03:00:00/40 tag 2 ncq dma 12288 out
                                         res 40/00:01:00:00:00/00:00:00:00:00/00 Emask 0x4 (timeout)
Aug 22 21:45:27 proxmox kernel: ata1.00: status: { DRDY }
Aug 22 21:45:27 proxmox kernel: ata1.00: failed command: WRITE FPDMA QUEUED
Aug 22 21:45:27 proxmox kernel: ata1.00: cmd 61/08:18:00:50:14/00:00:01:00:00/40 tag 3 ncq dma 4096 out
                                         res 40/00:00:00:00:00/00:00:00:00:00/00 Emask 0x4 (timeout)
Aug 22 21:45:27 proxmox kernel: ata1.00: status: { DRDY }
Aug 22 21:45:27 proxmox kernel: ata1.00: failed command: WRITE FPDMA QUEUED
Aug 22 21:45:27 proxmox kernel: ata1.00: cmd 61/30:20:40:0d:07/01:00:03:00:00/40 tag 4 ncq dma 155648 out
                                         res 40/00:00:00:00:00/00:00:00:00:00/00 Emask 0x4 (timeout)
Aug 22 21:45:27 proxmox kernel: ata1.00: status: { DRDY }
Aug 22 21:45:27 proxmox kernel: ata1.00: failed command: WRITE FPDMA QUEUED
Aug 22 21:45:27 proxmox kernel: ata1.00: cmd 61/08:70:f0:53:54/00:00:01:00:00/40 tag 14 ncq dma 4096 out
                                         res 40/00:00:01:4f:c2/00:00:00:00:00/00 Emask 0x4 (timeout)
Aug 22 21:45:27 proxmox kernel: ata1.00: status: { DRDY }
Aug 22 21:45:27 proxmox kernel: ata1.00: failed command: WRITE FPDMA QUEUED
Aug 22 21:45:27 proxmox kernel: ata1.00: cmd 61/08:78:90:71:5b/00:00:01:00:00/40 tag 15 ncq dma 4096 out
                                         res 40/00:01:00:00:00/00:00:00:00:00/00 Emask 0x4 (timeout)
Aug 22 21:45:27 proxmox kernel: ata1.00: status: { DRDY }
Aug 22 21:45:27 proxmox kernel: ata1.00: failed command: WRITE FPDMA QUEUED
Aug 22 21:45:27 proxmox kernel: ata1.00: cmd 61/10:80:18:90:5b/00:00:01:00:00/40 tag 16 ncq dma 8192 out
                                         res 40/00:00:00:4f:c2/00:00:00:00:00/00 Emask 0x4 (timeout)
Aug 22 21:45:27 proxmox kernel: ata1.00: status: { DRDY }
Aug 22 21:45:27 proxmox kernel: ata1: hard resetting link
Aug 22 21:45:27 proxmox kernel: ata1: SATA link up 6.0 Gbps (SStatus 133 SControl 300)
Aug 22 21:45:27 proxmox kernel: ata1.00: configured for UDMA/133
Aug 22 21:45:27 proxmox kernel: ata1.00: device reported invalid CHS sector 0
Aug 22 21:45:27 proxmox kernel: ata1.00: device reported invalid CHS sector 0

and maybe the filesystem goes readonly because of those errors. It doesn't necessarily mean that the disk is broken, it (or the host) might also be overloaded, but I'd be wary and maybe try a different disk.

 

[Kacperro]

ok thanks for your help. I'll try with another disk, I hope I won't come back with the same problem in another 2 months :/

 

[Kacperro]

Hello, unfortunately the problem has returned again.
In my opinion it cannot be a disk problem.

 

[fiona]

Unfortunately, it seems like the log is cut off and doesn't contain much information. What physical drive do you have now? Did you run a health check on it? I'd also run a memory test to rule out bad memory.

 

[Kacperro]

I bought the same model.
About memory test - everything it's ok.

 

[y2kbug]

I bought the same model.
About memory test - everything it's ok.

Hello there. Do you mean it was due to RAM quality problem?