Filesystem still has errors

Talha

Active Member
Jan 13, 2020
57
0
26
29
Hello there. Today, while my server was running, the virtual servers suddenly crashed and started giving an i/o error. When I tried to operate on the server, I saw that it went into write-protected mode. When I restarted the server, I was faced with a screen stating that Proxmox was no longer opened and required manual action. Even if I do fsck /dev/mapper/pve-root it doesn't work. Can someone help me please?


1661884940192.png
1661884658785.png
 
I don't think this can be fixed with software. Either the drive is overheating or at the end of its lifetime (TBW) and gone into read-only mode or it is just plain broken. Maybe you can get some information about it with smartctl or try it in another working system.
 
I don't think this can be fixed with software. Either the drive is overheating or at the end of its lifetime (TBW) and gone into read-only mode or it is just plain broken. Maybe you can get some information about it with smartctl or try it in another working system.
I am using samsung 970 evo plus about 1 year old. I think it went into read-only mode because of overheating
 
I am using samsung 970 evo plus about 1 year old. I think it went into read-only mode because of overheating
Still, I do advise you to check the SMART values also. It would not be the first time Proxmox finished a consumer drive within a year (as this forum will show).
 
Available Spare: 0% means than all your flash memory is used up. Mine still shows 100% with [30.6TB] Data Units Written. My Media and Data Integrity Errors still is 0, while yours is 4444. Maybe your drive has failed for some other reason and maybe you can get a replacement under warranty?

EDIT: It's current temperature is lower than mine during normal (low usage) operation.