You are not logged in.
My PC runs a dual system Windows/Arch. Each system stands on a separate SSD. An additional disk (sda2) runs a NTFS partition for sharing contents between both OS.
$ blkid
/dev/mapper/volgroup-swap: UUID="3b8d1bfc-091f-424f-ac75-4624d6e85861" TYPE="swap"
/dev/nvme0n1p1: UUID="643A-9A20" BLOCK_SIZE="512" TYPE="vfat" PARTLABEL="boot" PARTUUID="3db48622-6d0d-4b0a-93e3-5b7d33643d30"
/dev/nvme0n1p2: UUID="c9758b45-9516-4c66-929d-3738796f0eeb" TYPE="crypto_LUKS" PARTLABEL="lvm" PARTUUID="563993b8-7799-4422-852c-d804a9ca6014"
/dev/mapper/volgroup-root: UUID="7ff34224-f45f-4ee9-82a3-789e4c0a1bf5" BLOCK_SIZE="4096" TYPE="ext4"
/dev/mapper/cryptlvm: UUID="bPDZcl-4bkh-nRGo-bMjI-O0eH-7WKL-5k0pHb" TYPE="LVM2_member"
/dev/nvme1n1p4: BLOCK_SIZE="512" UUID="8E88336488334A4B" TYPE="ntfs" PARTUUID="8ad4295a-cea9-4484-94f9-b6eb556eb625"
/dev/nvme1n1p2: PARTLABEL="Microsoft reserved partition" PARTUUID="dfa325dc-900a-42e0-9808-46910affa416"
/dev/nvme1n1p3: BLOCK_SIZE="512" UUID="1A4832124831ECDF" TYPE="ntfs" PARTLABEL="Basic data partition" PARTUUID="9088ce81-de70-426f-bde6-25bc8bb66098"
/dev/nvme1n1p1: UUID="8431-30A9" BLOCK_SIZE="512" TYPE="vfat" PARTLABEL="EFI system partition" PARTUUID="35eb5bc5-906f-48e7-98a6-337c7c1ca747"
/dev/sda2: LABEL="Samsung EVO 870" BLOCK_SIZE="512" UUID="D28ABDA88ABD898D" TYPE="ntfs" PARTLABEL="Basic data partition" PARTUUID="84d3fefb-3dc3-492d-a779-75e34528d852"
/dev/sda1: PARTLABEL="Microsoft reserved partition" PARTUUID="35fccc8b-ea92-401b-a76b-2d8d3b5ac655" Until yesterday my fstab was mounting and binding fine:
# /dev/mapper/volgroup-root
UUID=7ff34224-f45f-4ee9-82a3-789e4c0a1bf5 / ext4 rw,relatime 0 1
# /dev/nvme0n1p1
UUID=643A-9A20 /boot vfat rw,relatime,fmask=0022,dmask=0022,codepage=437,iocharset=ascii,shortname=mixed,utf8,errors=remount-ro 0 2
# /dev/mapper/volgroup-swap
UUID=3b8d1bfc-091f-424f-ac75-4624d6e85861 none swap defaults 0 0
# /dev/sda2
UUID=D28ABDA88ABD898D /mnt/sda2 ntfs3 defaults 0 2
# Musique
/mnt/sda2/Musique /home/fabien/Musique none bind 0 0
# Windows
/mnt/sda2/Windows /Windows none bind 0 0However, after restarting from Windows 10 to Linux, I now get the following errors from systemd:
[FAILED] Failed to mount /mnt/sda2
[DEPEND] Dependency failed for /home/fabien/Musique
[DEPEND] Dependency failed for Local File System
[DEPEND] Dependency failed for /WindowsThe journal has:
ntfs3(sda2): It is recommended to use chkdsk
mount: wrong fs type, bad option, bad superblock on /dev/sda2, missing codepage or helper program, or other errorI ran chkdsk on Windows. All looks fine.
Once I uncomment the appropriate lines in my fstab and get into my environment, I manage to manually mount the disk with ntfs-3g.
Kernel is up to date:
$ uname -a
Linux 8700g 6.12.4-arch1-1 #1 SMP PREEMPT_DYNAMIC Mon, 09 Dec 2024 14:31:57 +0000 x86_64 GNU/LinuxIntegrity on Linux looks fine as well:
$ ntfsfix /dev/sda2
Mounting volume... OK
Processing of $MFT and $MFTMirr completed successfully.
Checking the alternate boot sector... OK
NTFS volume version is 3.1.
NTFS partition /dev/sda2 was processed successfully.Last edited by jfk (2024-12-16 22:59:07)
Offline
Is there a mismatch between installed kernel package and running kernel? What is the output of `pacman -Q linux`
Offline
ntfsfix will actually set the dirty bit, to clear it without a windows chkdsk you'd do ntfsfix -d, after running chkdsk from windows make sure and double check fast boot is not enabled: https://wiki.archlinux.org/title/Dual_b … ibernation
If you want to force mount it despite the warning with ntfs3 you could supply the force flag.
Offline
ntfsfix will actually set the dirty bit, to clear it without a windows chkdsk you'd do ntfsfix -d
Thanks, the -d flag seems indeed to have solved the issue. I disabled fast boot for the future as well.
Offline
/mnt/sda2/Windows /Windows none bind 0 0
aside from me highly discourage using ntfs at all under linux (use exFAT for data exchange) mounting C:\Windows is a catastrophe waiting to happen - you should remove that line without replacement ASAP - I can't see any reason to do THAT - not even as a dev as a windows dev you should do whatever it is you do on windows instead from linux
as for bind-mount your music folder into home ... well, it's one way - I guess - why not just use a symbolic link?
as for chkdsk: when you're asked to run chkdsk from windows - do so! you don't get that prompted for nothing or to ignore it - recommend options for chkdsk: /X /F /B /R
as for fast start: do it NOW! not at some time in the future - NOW! - the issue with fast start: when you just click "shutdown" instead of "restart" and boot into linux from that state with fast start enabled you risk any ntfs partition to become corrupted - as modern windows "shutdown" isn't a proper shutdown but more of a deep hibernate - hence either disable fast start to get a full clean shutdown - or only always use "restart" from windows and kill the system when your linux bootloder shows up
Offline
mounting C:\Windows is a catastrophe waiting to happen
As I said in my description, there's no system on sda2. It is a third non-NVME disk that I use to quickly access random files from one OS to the other. "Windows" is just a user folder. My systems are not set to communicate between each other precisely for security purposes.
why not just use a symbolic link?
It is cleaner. Symbolic links necessarily add fixed objects to your folder, binding do not.
Regarding fast start, the modification is done.
Last edited by jfk (2024-12-17 01:37:09)
Offline
While I disagree with cryptearths general disdain/experiences with ntfs, doing a proper chkdsk should always be the first choice rather than ntfsfix (-d or not) since ntfsfix simply doesn't have all the necessary tooling to properly ensure consistency of the drive.
A correctly ran chkdsk (that's not masked by the fact fast boot is enabled -- that one should always be off! -- and was likely the cause for the continued dirty flag) will clear the dirty bit and properly fix any internal inconsistencies.
The ntfs3 driver was very prone to trigger this a couple of kernels ago I haven't had any issues of note with it since around 6.10 and I make fairly heavy use of the NTFS disk for shared steam games and music collections.
Offline