proxmox input/output error

[en4ble]

Hi,

Freshly installed os/new hardware. It was transported so it had to be powered down, after that I have noticed access to GUI stopped working on random occasions.

When trying grab any information such as /etc/network/interfaces or even looking at the default systemctl status commands getting input/output error for all of them.

Never encountered this issue before and I did install lots of pves. Is this looking like corrupted OS or hw related? Can't even run fsck which gives same error. Probably will try rebuild but thought I'll ask or atleast if someone has similar issue they can use this thread.



Thank You in advance for any feedback.

 

[Azunai333]

Your PVE cannot even load any programs anymore (no even read only), so there seems to be a problem with the root filesystem or the disk it's on.
I would check the drive and the cables to it.

Maybe try to mount it on other linux computer to see if the drive is still working?

 

[en4ble]

Your PVE cannot even load any programs anymore (no even read only), so there seems to be a problem with the root filesystem or the disk it's on.
I would check the drive and the cables to it.

Maybe try to mount it on other linux computer to see if the drive is still working?

Thanks for reply. I mean if the issue was with the cable don't you think it wouldn't even boot instead being impaired?!

 

[Azunai333]

Thanks for reply. I mean if the issue was with the cable don't you think it wouldn't even boot instead being impaired?!

A bad cable doesn't mean necessarily that it fails continuously. It may work for some time and then drop the connection due to communication errors.

Fact is your root filesystem tries to mount itself as read-only because it detects an error. But in that state you should still be able to read and execute programs from it. This fails completely in your case.

 

[en4ble]

As soon as this message shows up (Remounting filesystem read-only) the UI stops working and no info can be captured. Reseated cables, going with new install.

 

[yoshuki]

If you're using NVMe, disabling APST may help.
I am using a Samsung SSD 990 PRO, and the problem was fixed by setting "nvme_core.default_ps_max_latency_us=0".

https://wiki.archlinux.org/title/So...Controller_failure_due_to_broken_APST_support
https://qiita-com.translate.goog/Sh..._sl=ja&_x_tr_tl=en&_x_tr_hl=ja&_x_tr_pto=wapp