5.6653081 XFS (dm-0): Internal error XFS_WANT_CORRUPTED_GOTO at line 1753 of file fs/xfs/libxfs/xfs_alloc.c.
Caller xfs_free_extent+0xaa/0x150 [xfs]
5.6659161 XFS (dm-B): Internal error xfs_trans_cancel at line 993 of file fs/xfs/xfs_trans.c.
Caller xfs_efi_recover+0x18e/0x1c0 Ixfs]
5.6664901 XFS (dm-0): Corruption of in memory data detected.
Shutting down filesystem
5.6665451 XFS (dm-8): Please umount the filesystem and rectify the problem(s)
5.6666081 XFS
(dm-0): Failed to recover intents
Generating
"/run/initramfs/rdsosreport.txt"
Entering emergency mode. Exit the shell to continue.
Type
"journalct 1"
to view system logs.
You might want to save
"/run/initramfs/rdsosreport.txt" to a USB stick or /boot
after mounting them and attach it to a bug report.
:/#
Since access via the web console or ssh is not possible, I don’t know what I could do. The instructions in the console message are not executable for me.
I have already imported an old backup, and it also starts. I was actually reassured after that.
But at some point the error occurs again without me being able to identify the trigger or the conditions.
A file system can become corrupted, even virtual ones!
This usually can be repaired. Unfortunately, this is not possible with XFS easily, the system needs to be booted from a different system. Ext4 can be repaired on the fly, but it also needs repairs more often!
On the second hand, how stable is XFS? How long has your server been running without any file system issues? Probably a very long time!
If it keeps repeating the error (in a virtual system), there’s probably a hardware defect somewhere (Chip, IO, RAM, etc.).
Start up the VM with a working backup, verify this!
Shut down NethServer VM.
Boot using the latest SystemRescueCD Image.
This can easily repair the NethServers XFS file system (also used in Proxmox as default, if not set to use ZFS).
Use xfs_repair… Note: NethServer 7 main filesystem is on LVM. The LVM must NOT be mounted to run XFS_Repair! (Ideal for SystemRescue!)
After that, reboot the Nethserver - and make a backup right away in Proxmox.
Watch and observer the VM the next couple of days, it should be OK!
My 2 cents
Andy
From my notes:
Boot ab CD: SystemrescueCD:
xfs_repair /dev/sda1
xfs_repair /dev/VolGroup/lv_root
Fertig!
Note: SystemRescue has a GUI option (startx), but this is not needed here, console is enough!
And as it’s a VM, the paths above are always correct!
/dev/sda is the default boot partition of NS7
/dev/VolGroup/lv_root is where the actual file system resides…
No real need to worry, if the error crops up (rare!), it can be fixed in Proxmox 7 just as easily as in. Proxmox 8.
Keeping a copy of SystemrescueCD ready on Proxmox ISO libraries always makes sense!
When booting such a host (suspected of hardware errors!), one almost MUST have a screen hooked up and observe the screen during boot, and about 5 minutes after boot!!!
A lot of errors are shown on the screen, and in the very depths of certain logfiles, when you know what you’re looking for.
Watching the screen is much easier!
(Normally, only the login appears, no error messages!)
It’s in German. As I don’t know what kernel you do use right now, basically the thread says downgrading to i.e. kernel 5.15.108-1-pve solves the problem that the machine is not reachable.
I don’t know if there’s a fix already rolled out. You could check or roll back, just to check if you reach stability again.
