Arch Linux

Firestar

Member

From: Beijing, China

Registered: 2021-07-19

Posts: 116

Website

fstab cannot mount ntfs drives when booting

I have 2 ntfs disks on my computer and I want to mount them when I boot into archlinux

so I edited fstab like this

# Static information about the filesystems.
# See fstab(5) for details.

# <file system> <dir> <type> <options> <dump> <pass>
# /dev/nvme0n1p4 UUID=3f9fbc10-b296-4a7d-80ac-a262dbf31da9
/dev/nvme0n1p4          /               ext4            rw,relatime     0 1

# /dev/nvme0n1p1 UUID=661A-A5ED
/dev/nvme0n1p1          /boot           vfat            rw,relatime,fmask=0022,dmask=0022,codepage=437,iocharset=ascii,shortname=mixed,utf8,errors=remount-ro  0 2
/dev/nvme0n1p3         /home/firestar/C        ntfs    default,noatime 0 0
/dev/nvme0n1p5         /home/firestar/D        ntfs    default,noatime 0 0

then I rebooted and crash into emergency mode, this is the journal:

Aug 29 12:03:03 ThinkPad systemd[1]: Found device SAMSUNG MZVL21T0HCLR-00BL7 C.
░░ Subject: A start job for unit dev-nvme0n1p3.device has finished successfully
░░ Defined-By: systemd
░░ Support: https://lists.freedesktop.org/mailman/listinfo/systemd-devel
░░ 
░░ A start job for unit dev-nvme0n1p3.device has finished successfully.
░░ 
░░ The job identifier is 51.
Aug 29 12:03:03 ThinkPad systemd[1]: Mounting /home/firestar/C...
░░ Subject: A start job for unit home-firestar-C.mount has begun execution
░░ Defined-By: systemd
░░ Support: https://lists.freedesktop.org/mailman/listinfo/systemd-devel
░░ 
░░ A start job for unit home-firestar-C.mount has begun execution.
░░ 
░░ The job identifier is 50.
Aug 29 12:03:03 ThinkPad mount[315]: mount: /home/firestar/C: unknown filesystem type 'ntfs'.
Aug 29 12:03:03 ThinkPad mount[315]:        dmesg(1) may have more information after failed mount system call.
Aug 29 12:03:03 ThinkPad systemd[1]: home-firestar-C.mount: Mount process exited, code=exited, status=32/n/a
░░ Subject: Unit process exited
░░ Defined-By: systemd
░░ Support: https://lists.freedesktop.org/mailman/listinfo/systemd-devel
░░ 
░░ An n/a= process belonging to unit home-firestar-C.mount has exited.
░░ 
░░ The process' exit code is 'exited' and its exit status is 32.
Aug 29 12:03:03 ThinkPad systemd[1]: home-firestar-C.mount: Failed with result 'exit-code'.
░░ Subject: Unit failed
░░ Defined-By: systemd
░░ Support: https://lists.freedesktop.org/mailman/listinfo/systemd-devel
░░ 
░░ The unit home-firestar-C.mount has entered the 'failed' state with result 'exit-code'.
Aug 29 12:03:03 ThinkPad systemd[1]: Failed to mount /home/firestar/C.
░░ Subject: A start job for unit home-firestar-C.mount has failed
░░ Defined-By: systemd
░░ Support: https://lists.freedesktop.org/mailman/listinfo/systemd-devel
░░ 
░░ A start job for unit home-firestar-C.mount has finished with a failure.
░░ 
░░ The job identifier is 50 and the job result is failed.
Aug 29 12:03:03 ThinkPad systemd[1]: Dependency failed for Local File Systems.
░░ Subject: A start job for unit local-fs.target has failed
░░ Defined-By: systemd
░░ Support: https://lists.freedesktop.org/mailman/listinfo/systemd-devel
░░ 
░░ A start job for unit local-fs.target has finished with a failure.

I use kernel 5.19 and I have not installed ntfs-3g

Last edited by Firestar (2022-08-29 04:05:24)

---

Write programs that do one thing and do it well.
Write programs to work together.
Write programs to handle text streams, because that is a universal interface.

loqs

Member

Registered: 2014-03-06

Posts: 18,964

Re: fstab cannot mount ntfs drives when booting

Aug 29 12:03:03 ThinkPad mount[315]: mount: /home/firestar/C: unknown filesystem type 'ntfs'.

Please see https://wiki.archlinux.org/title/NTFS#unknown_filesystem_type_'ntfs'

Firestar

Member

From: Beijing, China

Registered: 2021-07-19

Posts: 116

Website

Re: fstab cannot mount ntfs drives when booting

The problem is: this is fstab and it cannot decide to use `-t ntfs3`

I tried editing `/etc/udev/rules.d/ntfs3_by_default.rules`:

`SUBSYSTEM=="block", ENV{ID_FS_TYPE}=="ntfs", ENV{ID_FS_TYPE}="ntfs3"`

Aug 29 13:06:42 ThinkPad mount[313]: mount: /home/firestar/C: unknown filesystem type 'ntfs'.
Aug 29 13:06:42 ThinkPad mount[313]:        dmesg(1) may have more information after failed mount system call.
Aug 29 13:06:42 ThinkPad systemd[1]: home-firestar-C.mount: Mount process exited, code=exited, status=32/n/a

I also tried changing `ntfs` to `ntfs3` in my `/etc/fstab` but still encountered emergency mode, this is the journal:

Aug 29 12:59:56 ThinkPad systemd[1]: Mounting /home/firestar/C...
░░ Subject: A start job for unit home-firestar-C.mount has begun execution
░░ Defined-By: systemd
░░ Support: https://lists.freedesktop.org/mailman/listinfo/systemd-devel
░░ 
░░ A start job for unit home-firestar-C.mount has begun execution.
░░ 
░░ The job identifier is 19.
Aug 29 12:59:56 ThinkPad kernel: usb 3-3: new full-speed USB device number 3 using xhci_hcd
Aug 29 12:59:56 ThinkPad systemd[1]: Found device SAMSUNG MZVL21T0HCLR-00BL7 D.
░░ Subject: A start job for unit dev-nvme0n1p5.device has finished successfully
░░ Defined-By: systemd
░░ Support: https://lists.freedesktop.org/mailman/listinfo/systemd-devel
░░ 
░░ A start job for unit dev-nvme0n1p5.device has finished successfully.
░░ 
░░ The job identifier is 22.
Aug 29 12:59:56 ThinkPad systemd[1]: Mounting /home/firestar/D...
░░ Subject: A start job for unit home-firestar-D.mount has begun execution
░░ Defined-By: systemd
░░ Support: https://lists.freedesktop.org/mailman/listinfo/systemd-devel
░░ 
░░ A start job for unit home-firestar-D.mount has begun execution.
░░ 
░░ The job identifier is 21.
Aug 29 12:59:56 ThinkPad mount[314]: mount: /home/firestar/C: wrong fs type, bad option, bad superblock on /dev/nvme0n1p3, missing codepage or helper program, or other error.
Aug 29 12:59:56 ThinkPad mount[314]:        dmesg(1) may have more information after failed mount system call.
Aug 29 12:59:56 ThinkPad mount[316]: mount: /home/firestar/D: wrong fs type, bad option, bad superblock on /dev/nvme0n1p5, missing codepage or helper program, or other error.
Aug 29 12:59:56 ThinkPad mount[316]:        dmesg(1) may have more information after failed mount system call.
Aug 29 12:59:56 ThinkPad systemd[1]: home-firestar-C.mount: Mount process exited, code=exited, status=32/n/a
░░ Subject: Unit process exited
░░ Defined-By: systemd
░░ Support: https://lists.freedesktop.org/mailman/listinfo/systemd-devel
░░ 
░░ An n/a= process belonging to unit home-firestar-C.mount has exited.
░░ 
░░ The process' exit code is 'exited' and its exit status is 32.

Last edited by Firestar (2022-08-29 07:03:43)

---

Write programs that do one thing and do it well.
Write programs to work together.
Write programs to handle text streams, because that is a universal interface.

seth

Member

From: Won't reply 2 private help req

Registered: 2012-09-03

Posts: 76,494

Re: fstab cannot mount ntfs drives when booting

The problem is: this is fstab and it cannot decide to use `-t ntfs3`

/dev/nvme0n1p3         /home/firestar/C        ntfs    default,noatime 0 0
/dev/nvme0n1p5         /home/firestar/D        ntfs    default,noatime 0 0

What's field 3 and what does it say in your fstab?
https://wiki.archlinux.org/title/Fstab#Usage
So who decides which (false) module is being used?

---

How to upload text · How to boot w/o GUI · Disable Windows Fast-Start! · Fix your xinitrc

Firestar

Member

From: Beijing, China

Registered: 2021-07-19

Posts: 116

Website

Re: fstab cannot mount ntfs drives when booting

I think the error is in fstab file

default should be defaults

---

Write programs that do one thing and do it well.
Write programs to work together.
Write programs to handle text streams, because that is a universal interface.

Firestar

Member

From: Beijing, China

Registered: 2021-07-19

Posts: 116

Website

Re: fstab cannot mount ntfs drives when booting

New problem:

This time I use `ntfs3    defaults` to mount but `ls -l` tell me that the two partitions are belonged to `root`, not my username

and I have no write access unless I am in sudo mode

**fixed by adding `umask=0`**

Last edited by Firestar (2022-09-10 02:46:33)

---

Write programs that do one thing and do it well.
Write programs to work together.
Write programs to handle text streams, because that is a universal interface.