-
Notifications
You must be signed in to change notification settings - Fork 161
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
ext journal_check_start:84: comm poxcfs: Detected aborted journal #185
Comments
smartctl -a /dev/nvme0n1 ? Looks like a hardware issue with cabeling or NVME connection. Please check wearout and warranty for nvme. |
Hi @TheBossME Appreciate your help here. Below the log. From my perspective I dont see anything strange here. === START OF INFORMATION SECTION === Supported Power States Supported LBA Sizes (NSID 0x1) === START OF SMART DATA SECTION === SMART Health Information (NVMe Log 0x02) Error Information (NVMe Log 0x01, 16 of 256 entries) Thank you in advance! |
Try different kernel please add with nano /etc/apt/sources.list deb https://deb.debian.org/debian bookworm-backports main contrib non-free non-free-firmware try 6.11 backport kernel and do the needed modifications for using backport kernels |
Hello everyone,
Since a couple of days I receive the following error message. It seems like a problem with The Proxmox Cluster file system (“pmxcfs”) and de NVME SSD.
[16821.351985] EX14-fs error (device nvme0n1p2): ext journal_check_start:84: comm poxcfs: Detected aborted journal
[16821.351987] EX14-fs error (device nvme0n1p2) in ext4_reserve_inode_write:5790: Journal has aborted
[16821.371313] EX14-fs (nvme0n1p2): Remounting filesystem read-only
After a hard restart, the system works properly for some time.
Hardware Config:
Software Config:
Hopefully someone could help me of guide me in the right direction.
The text was updated successfully, but these errors were encountered: