Vic Ubnann

That did it, thank you. Although the part 'some data may be corrupt' is concerning. I should do a backup. $ sudo fsck -n /dev/mapper/veracrypt1 fsck from util-linux 2.38.1 fsck.fat 4.2 (2021-01-31) There are differences between boot sector and its backup. This is mostly harmless. Differences: (offset:original/backup) 65:01/00 Not automatically fixing this. Dirty bit is set. Fs was not properly unmounted and some data may be corrupt. Automatically removing dirty bit. Leaving filesystem unchanged.

I forgot to say - my understanding is that fsck can only be run on an unmounted drive. At least, whenever I want to run it on a system drive I need to start it from a live usb, i.e. before system boot. But therein lies the problem: fsck can still 'see' the system drive even though it's not mounted whereas it can't 'see' an unmounted encrypted drive. Or am I missing something?

Thanks for your advice. After unmounting the volume I ran fsck but then got this - which kind of makes sense; if the volume is unmounted then there is no veracrypt1, right? fsck -n /dev/mapper/veracrypt1 fsck from util-linux 2.38.1 e2fsck 1.47.0 (5-Feb-2023) fsck.ext2: No such file or directory while trying to open /dev/mapper/veracrypt1 Possibly non-existent device?

So I installed the latest version from the package manager, 1.25.9, but still getting the same error. Not sure if gnome-terminal would work as I think it requires systemd.

When I set up this OS about 8 months ago I installed Veracrypt from the package manager but I always got this annoying nag screen every time I started it so I went back to this earlier version. Maybe it's been fixed now so I'll try that, thanks.

Okay, thanks. The volume was on an external 4 TB drive, with both the host drive and the volume itself formatted in ext4. After reboot I mounted it and in the main Veracrypt window I right-clicked on the volume and selected Check Filesystem. This is not confined to this volume alone as the error is displayed whenever I try Check Filesystem on any other volume. I'm using VeraCrypt 1.24 - Update 4.

Hello, I'm new here. I recently had a system (Debian based) freeze while a volume was mounted then after a reboot I tried to check the filesystem but got this error: QStandardPaths: XDG_RUNTIME_DIR not set, defaulting to '/tmp/runtime-root' QStandardPaths: XDG_RUNTIME_DIR not set, defaulting to '/tmp/runtime-root' QStandardPaths: XDG_RUNTIME_DIR not set, defaulting to '/tmp/runtime-root' konsole: Unknown option 'caption'. I've asked on other forums but the advice to ignore it doesn't help as it doesn't...