5 Apr
2023
5 Apr
'23
1:29 a.m.
Hi All,
Big thanks to all who commented, esp @ndy.
IIRC the drive was vfat, and as part of the re-install, it is not ext4.
All default so journaling now on.
Will cycle the power later, and see what happens.
Can't now, the dog is on my knee, feeling poorly with the heat. It was
35C with 70% humidity at 7:30 AM this morning. (Bangkok has three
seasons - hot, damn hot, and f***ing hot in April).
Ian
On 05/04/2023 02:47, Andy Bennett via BitFolk Users wrote:
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
--
Ian Hobson
Tel (+66) 626 544 695
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?