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

M

mtd

New Member
Jun 25, 2022
7
0
1
Hi Guys,

I recently deployed my proxmox and everything went well until today, i started getting this error: Erro 500: unable to open file '/var/tmp/pve-reserved-ports.tmp.30648 -Read-only file system.

I can't login to my proxmox anymore, however i can ping the ip and can still ssh the server.

I tried to changed the permission of this file "pve-reserved-ports" and i'm getting this error message "chmod: changing permissions of '/var/tmp/pve-reserved-ports': Read-only file system"

1656564594655.png

Honestly i'm not sure if i'm doing things right. I would really appreciate any suggestions on how i can fix this issue. Thanks
 
mtd said:
Read-only file system.
Click to expand...
what's the output from mount? (please post with a code block instead of a screenshot, if possible)

but it sounds like your disk or filesystem faulty, which lead to it being remounted as read-only (to avoid creating more inconsistencies on it).

you could check the output from smartctl -a /dev/sda on your device to see if there are any disk errors.

worst case you might have to replace a faulty disk
 
@oguz : I'm not sure about the disk but it's a new ssd disk which i have tested so many times before i started using in the proxmox server.
By the way, all my VMs running without any problem, it just that i can't access proxmox admin portal.

Proxmox is installed on this new ssd disk and the VMs are on my NVMe drive
 

Attachments

in your mount output: /dev/mapper/pve-root on / type ext4 (ro,relatime,errors=remount-ro,stripe=8191)
errors=remount-ro means that the filesystem is remounted read-only if any errors are detected.

your smartctl looks like it's okay... so then it might be a filesystem error instead.

best way would be to shutdown your node, boot into some recovery environment and check the filesystem with fsck or similar tools for any inconsistency
 
@oguz : can you please elaborate how can i boot the proxmox server in recovery mode and check the filesystem? Thanksy
 
mtd said:
@oguz : can you please elaborate how can i boot the proxmox server in recovery mode and check the filesystem? Thanksy
Click to expand...
if you have physical access to your server you can boot one of many available recovery images (e.g. gparted, or just about any live linux environment should work).
without physical access you'll have to explore what your hoster offers you for booting your server into recovery.

once that's done, you can use fsck command to check your filesystem, for example fsck /dev/sda

hope this helps!
 
Error 500: unable to open file '/var/tmp/pve-reserved-ports.tmp.1454033' - Read-only file system

This morning I got this error message. all local-lvm volumes had disappeared. Login to the proxmox shell was no longer possible. Of course the vm no longer worked either. A shutdown was no longer possible. That's why I turned the server power off manually. After restarting everything worked again. Does anyone have an idea?


these are the last entries in the log:
Feb 29 05:03:14 Proxmox systemd[1]: Starting pve-daily-update.service - Daily PVE download activities...
Feb 29 05:03:15 Proxmox pveupdate[1509912]: <root@pam> starting task UPID:Proxmox:00170A2E:02F23465:65E00203:aptupdate::root@pam:
Feb 29 05:03:16 Proxmox pveupdate[1509934]: update new package list: /var/lib/pve-manager/pkgupdates
Feb 29 05:03:17 Proxmox pveupdate[1509912]: <root@pam> end task UPID:Proxmox:00170A2E:02F23465:65E00203:aptupdate::root@pam: OK
Feb 29 05:03:17 Proxmox systemd[1]: pve-daily-update.service: Deactivated successfully.
Feb 29 05:03:17 Proxmox systemd[1]: Finished pve-daily-update.service - Daily PVE download activities.
Feb 29 05:03:17 Proxmox systemd[1]: pve-daily-update.service: Consumed 2.485s CPU time.
Feb 29 05:17:01 Proxmox CRON[1512857]: pam_unix(cron:session): session opened for user root(uid=0) by (uid=0)
Feb 29 05:17:01 Proxmox CRON[1512858]: (root) CMD (cd / && run-parts --report /etc/cron.hourly)
Feb 29 05:17:01 Proxmox CRON[1512857]: pam_unix(cron:session): session closed for user root
Feb 29 06:17:01 Proxmox CRON[1523703]: pam_unix(cron:session): session opened for user root(uid=0) by (uid=0)
Feb 29 06:17:01 Proxmox CRON[1523704]: (root) CMD (cd / && run-parts --report /etc/cron.hourly)
Feb 29 06:17:01 Proxmox CRON[1523703]: pam_unix(cron:session): session closed for user root
Feb 29 06:25:01 Proxmox CRON[1525134]: pam_unix(cron:session): session opened for user root(uid=0) by (uid=0)
Feb 29 06:25:01 Proxmox CRON[1525135]: (root) CMD (test -x /usr/sbin/anacron || { cd / && run-parts --report /etc/cron.daily; })
Feb 29 06:25:01 Proxmox CRON[1525134]: pam_unix(cron:session): session closed for user root
Feb 29 06:31:31 Proxmox dhclient[1067]: DHCPREQUEST for 192.168.24.59 on vmbr0 to 192.168.24.1 port 67
Feb 29 06:31:31 Proxmox dhclient[1067]: DHCPACK of 192.168.24.59 from 192.168.24.1
Feb 29 06:31:31 Proxmox dhclient[1067]: bound to 192.168.24.59 -- renewal in 33226 seconds.
Feb 29 06:37:14 Proxmox systemd[1]: Starting apt-daily-upgrade.service - Daily apt upgrade and clean activities...
Feb 29 06:37:14 Proxmox systemd[1]: apt-daily-upgrade.service: Deactivated successfully.
Feb 29 06:37:14 Proxmox systemd[1]: Finished apt-daily-upgrade.service - Daily apt upgrade and clean activities.
Feb 29 07:17:01 Proxmox CRON[1534488]: pam_unix(cron:session): session opened for user root(uid=0) by (uid=0)
Feb 29 07:17:01 Proxmox CRON[1534489]: (root) CMD (cd / && run-parts --report /etc/cron.hourly)
Feb 29 07:17:01 Proxmox CRON[1534488]: pam_unix(cron:session): session closed for user root
Feb 29 08:17:01 Proxmox CRON[1545203]: pam_unix(cron:session): session opened for user root(uid=0) by (uid=0)
Feb 29 08:17:01 Proxmox CRON[1545204]: (root) CMD (cd / && run-parts --report /etc/cron.hourly)
Feb 29 08:17:01 Proxmox CRON[1545203]: pam_unix(cron:session): session closed for user root
Feb 29 09:17:01 Proxmox CRON[1555920]: pam_unix(cron:session): session opened for user root(uid=0) by (uid=0)
Feb 29 09:17:01 Proxmox CRON[1555921]: (root) CMD (cd / && run-parts --report /etc/cron.hourly)
Feb 29 09:17:01 Proxmox CRON[1555920]: pam_unix(cron:session): session closed for user root
-- Reboot --
 
我出现了同样的问题，我的是PVE 7.4 ：Virtual Environment 7.4-19。似乎是local-lvm volumes 丢失？但是出现问题之前我执行过删除虚拟机，并且勾选了：“销毁客户机拥有的未引用磁盘”。然后就出现了这个问题。我的也是SSD，我感觉不是SSD的问题。
 
You must log in or register to reply here.
Top Bottom