NTFS: Difference between revisions
Remove unnecessary use of ntfs-3g and recommend generating the configuration using `nixos-generate-config`. |
→Troubleshooting: adds section on dirty flag |
||
| (4 intermediate revisions by one other user not shown) | |||
| Line 5: | Line 5: | ||
Using [[nixos-generate-config]] to automatically generate Nix config is the recommended way to setup filesystems. | Using [[nixos-generate-config]] to automatically generate Nix config is the recommended way to setup filesystems. | ||
1. Run {{ic|lsblk}} to list device names | 1. Run {{ic|lsblk}} to list device names. | ||
2. Mount the device using {{ic|mount}}, where {{ic|/dev/sdX}} replaced with your device name and {{ic|/mnt/sdX}} replaced with an existing folder path to mount your drive. | {{code| | ||
{{code|<nowiki>mount /dev/sdX /mnt/sdX -t ntfs3</nowiki>}} | sd... | ||
3. Run {{ic|nixos-generate-config --dir .}} to generate hardware configuration. This will automatically add all currently mounted devices to {{ic|hardware-configuration.nix}}. | └─sdX | ||
}} | |||
2. Mount the device using [https://man7.org/linux/man-pages/man8/mount.8.html {{ic|mount}}], where {{ic|/dev/sdX}} replaced with your device name and {{ic|/mnt/sdX}} replaced with an existing folder path to mount your drive. | |||
{{code|<nowiki>mount /dev/sdX /mnt/sdX -t ntfs3 -o uid=$UID</nowiki>}} | |||
3. Run {{ic|nixos-generate-config --dir .}} to generate hardware configuration. This will <strong>automatically</strong> add all currently mounted devices to {{ic|hardware-configuration.nix}}. | |||
{{file|/etc/nixos/hardware-configuration.nix|diff|3= | {{file|/etc/nixos/hardware-configuration.nix|diff|3= | ||
+ boot.supportedFilesystems = [ "ntfs" ]; | + boot.supportedFilesystems = [ "ntfs" ]; | ||
| Line 16: | Line 20: | ||
+ }; | + }; | ||
}} | }} | ||
4. Add {{ic|<nowiki>"uid=$UID"</nowiki>}} to {{nixos:option|fileSystems.*.options|fileSystems.<name>.options}} to get write access, where {{ic|<nowiki>$UID</nowiki>}} replaced with your UID: | 4. Add {{ic|<nowiki>"uid=$UID"</nowiki>}} to {{nixos:option|fileSystems.*.options|fileSystems.<name>.options}} to get write access, where {{ic|<nowiki>$UID</nowiki>}} <strong>replaced with your UID</strong>: | ||
{{file|/etc/nixos/configuration.nix| | {{file|/etc/nixos/configuration.nix|nix|3= | ||
fileSystems = | fileSystems = | ||
let | let | ||
| Line 26: | Line 30: | ||
lib.genAttrs ntfs-drives (path: { | lib.genAttrs ntfs-drives (path: { | ||
options = [ | options = [ | ||
"uid=$UID" | "uid=$UID" # REPLACE "$UID" WITH YOUR ACTUAL UID! | ||
# "nofail" | # "nofail" | ||
]; | ]; | ||
| Line 34: | Line 38: | ||
{{note|You may find your UID by running {{ic|echo $UID}}.}} | {{note|You may find your UID by running {{ic|echo $UID}}.}} | ||
{{aside|It is not recommended to manually edit {{ic|hardware-configuration.nix}}.}} | {{aside|It is not recommended to manually edit {{ic|hardware-configuration.nix}}.}} | ||
5. {{evaluate}} | |||
== Troubleshooting == | == Troubleshooting == | ||
| Line 60: | Line 65: | ||
[https://social.technet.microsoft.com/wiki/contents/articles/25908.fast-startup-how-to-disable-if-it-s-causing-problems.aspx This TechNet entry] explains how to disable fast startup. Additionally, [https://www.howtogeek.com/243901/the-pros-and-cons-of-windows-10s-fast-startup-mode/ this blog post on howtogeek.com] explains how the fast startup mode works, and how to disable it. | [https://social.technet.microsoft.com/wiki/contents/articles/25908.fast-startup-how-to-disable-if-it-s-causing-problems.aspx This TechNet entry] explains how to disable fast startup. Additionally, [https://www.howtogeek.com/243901/the-pros-and-cons-of-windows-10s-fast-startup-mode/ this blog post on howtogeek.com] explains how the fast startup mode works, and how to disable it. | ||
=== Unable to mount ntfs3 with dirty volume === | |||
When attempting to mount an <code>NTFS</code> partition using the <code>ntfs3</code> filesystem driver via the {{nixos:package|ntfs3g}} package, the mount operation may fail: | |||
<syntaxhighlight lang="console"> | |||
# mount /dev/sda1 /mnt -t ntfs3 | |||
mount: /mnt: wrong fs type, bad option, bad superblock on /dev/sda1, missing codepage or helper program, or other error. | |||
dmesg(1) may have more information after failed mount system call. | |||
</syntaxhighlight> | |||
With the resulting dmesg output: | |||
<syntaxhighlight lang="console"> | |||
# dmesg | |||
... | |||
[168659.819978] ntfs3: sda1: It is recommened to use chkdsk. | |||
[168659.820833] ntfs3: sda1: volume is dirty and "force" flag is not set! | |||
</syntaxhighlight> | |||
This indicates that the NTFS volume has the “dirty” flag set. In this state, the <code>ntfs3</code> driver refuses to mount the filesystem. | |||
To clear the dirty flag, run <code>ntfsfix</code> on the affected partition: | |||
<syntaxhighlight lang="console"> | |||
# ntfsfix --clear-dirty /dev/sda1 | |||
</syntaxhighlight> | |||
If <code>ntfsfix</code> fails with an error <code>Windows is hibernated, refused to mount</code>, the partition can be mounted using <code>ntfs-3g</code> with the hibernation file removed: | |||
<syntaxhighlight lang="console"> | |||
# ntfs-3g -o remove_hiberfile /dev/sda1 /mnt | |||
</syntaxhighlight> | |||
[[Category:Filesystem]] | [[Category:Filesystem]] | ||