4 Apr
2023
4 Apr
'23
7:47 p.m.
Hi,
I think it was vfat or ext4. Have reformatted and installed O/S
on another drive, so cannot be sure.
If it was vfat then that will need an fsck every time the machine reboots
unexpectedly. vfat doesn't have good support for UNIX/Linux style
permissions so I'd expect it to contain disk images or something for the
the containers.
ext4 is journaled (by default) and should survive an unexpected reboot so
if this is causing an fsck then you might want to look into other causes.
Perhaps it's set up in one of the non-default / non-journaling modes or
perhaps there are some harware errors or settings (writeback caches) that
make the mounter think the log is unrecoverable.
Best wishes,
@ndy
--
andyjpb(a)ashurst.eu.org
http://www.ashurst.eu.org/
0x7EBA75FF
The problem following a power loss, is that it would
boot,
but fail to start Proxmox, and complain that I have to run
fsck manually (on the boot spinning rust drive).
Do you know what filesystem is in use on the drive?