My server spec:
Today my Proxmox 8 nded up having the following error:
This error appears like ~30 seconds after I load proxmox and even I can write my username and password and In a few seconds BOOM I get the error shown above.
First thing that I thought it might be the 2TB samsung NVME is dying on me. I run only one drive in the server. Luckaly I have two brand new nvme from Samsung again and they are even 4TBs. So I downloaded Clonezilla and initiated a clone from the old "suposadly" broken nvme of 2TB to the brand new 4TB nvme. The clone went sucessfully!
So I installed the new 4TB nvme and BOOM, the same error even on the brand new hard drive.
To make the things even more wierder I took that 4TB hard drive and place it on another machine where I had Ubuntu 22.04 installed. I remove the Ubuntu nvme and installed the 4TB cloned Proxmox on the machine and there Proxmox loads and runs fine on my PC and there Proxmox starts without showing me this error, but on the SuperMicro server it does not.
There on the PC which used to run my Ubuntu when I installed the 2TB initial drive from the server for even greater suprise it was runing without any kind of errors the same way the 4TB cloned was running.
So I decided to run test command to see if the disk is healthy and I executed `sudo smartctl -a /dev/nvme0n1` on which I've got:
If that result is acurate the disk should be fine, and why not it runs on my regular PC just fine. Why it does not on my SuperMicro Server ?
To test the server I took the nvme of my Ubuntu PC and place it on the server just to conclude even weirder result, the ubuntu loads in the same nvme slot in which it refuses to load the inital 2TB or the cloned 4TB nvme drives containing Proxmox.
How these strange outcomes can happen, anyone have a clue ?
This setup was running like this for months wihtout problems. What should I do not to make my Proxmox back online without this nasty `comm systemd-journal: Detected aborted journal`, any advice ?
Code:
MB: Supermicro H12SSL-i
CPU: AMD Epyc 7742
GPU: NVIDIA RTX 3090
RAM: 512GB DDR4 RDIMM ECCToday my Proxmox 8 nded up having the following error:
Code:
[40.294701] EXT-fs error (device dm-1): ext_journal_check_start:84: comm systemd-journal: Detected aborted journal
EXT4-fs (dm-1): Remounting filesystem read-onlyThis error appears like ~30 seconds after I load proxmox and even I can write my username and password and In a few seconds BOOM I get the error shown above.
First thing that I thought it might be the 2TB samsung NVME is dying on me. I run only one drive in the server. Luckaly I have two brand new nvme from Samsung again and they are even 4TBs. So I downloaded Clonezilla and initiated a clone from the old "suposadly" broken nvme of 2TB to the brand new 4TB nvme. The clone went sucessfully!
So I installed the new 4TB nvme and BOOM, the same error even on the brand new hard drive.
To make the things even more wierder I took that 4TB hard drive and place it on another machine where I had Ubuntu 22.04 installed. I remove the Ubuntu nvme and installed the 4TB cloned Proxmox on the machine and there Proxmox loads and runs fine on my PC and there Proxmox starts without showing me this error, but on the SuperMicro server it does not.
There on the PC which used to run my Ubuntu when I installed the 2TB initial drive from the server for even greater suprise it was runing without any kind of errors the same way the 4TB cloned was running.
So I decided to run test command to see if the disk is healthy and I executed `sudo smartctl -a /dev/nvme0n1` on which I've got:
Code:
SMART overall-health self-assessment test result: PASSEDIf that result is acurate the disk should be fine, and why not it runs on my regular PC just fine. Why it does not on my SuperMicro Server ?
To test the server I took the nvme of my Ubuntu PC and place it on the server just to conclude even weirder result, the ubuntu loads in the same nvme slot in which it refuses to load the inital 2TB or the cloned 4TB nvme drives containing Proxmox.
How these strange outcomes can happen, anyone have a clue ?
This setup was running like this for months wihtout problems. What should I do not to make my Proxmox back online without this nasty `comm systemd-journal: Detected aborted journal`, any advice ?
Last edited: