9.5
Table Of Contents
- Introduction
- System requirements
- Installation
- Using The Driver
- Mount options
- Additional Utilities
- Troubleshooting
- Troubleshooting processes
- Mount troubleshooting
- The install.sh script can’t find kernel sources
- Can’t compile the NTFS/HFS+ for Linux driver
- “Can’t load module” message at the end of installation
- ufsd module: kernel-module version mismatch
- ufsd module: create_module: operation is not permitted
- insmod: a module named as ufsd already exists
- insmod: Unknown symbol jnl_op (err0)
- Can’t mount NTFS/HFS+ volume
- Hardware issues
- Sysdump utility
- UFSD driver compatibility
- Frequently Asked Questions
- What are 'minor errors' reported by chkntfs utility?
- Warnings on Windows7/Vista when NTFS HDD is reconnected from Linux
- Recently changed file has its modification time a few hours ahead of or behind the current system time. Why?
- Why does mount option A make driver ignore mount option B?
- Does the driver have an optimization for avoiding data fragmentation?
- Why a lot of memory is used for volume mounting?
- Why the disk can't be dismounted?
13 Paragon NTFS&HFS+ for Linux 9.5
4 Using The Driver
After building and installing Paragon NTFS&HFS+ for Linux 9.5 driver, it can be automatically loaded
at the system startup. The driver allows to mount supported partitions and provides access to their
whole contents.
4.1 Getting started
The goal of this section is to help system engineers to quickly find out how to use the product. It
describes general approach to mounting partitions using UFSD file system driver and helps to avoid
common issues. We strongly recommend reading this section before starting using our driver.
To mount volume using UFSD driver, standard mount command is used, with FS type set to ufsd,
e.g.:
# mount -t ufsd /dev/sda1 /mnt/sda1
After this command is executed there can be several mount scenarios for a disk (for more information
see Mount troubleshooting subsection):
• The disk is “clean” (without any errors), mounted by the driver and ready to use.
• Disk can’t be mounted. In this case can be several scenarios:
1. Disk has “dirty” flag set (for more information see Dirty flag issues subsection):
– Use chkntfs/chkhfs utilities with -a -f options to check the volume for errors and incon-
sistencies and fix them (if any). This is recommended approach (see ?? or ?? subsections);
– Use ‘force’ mount option (see Dirty flag issues subsection).
2. The disk is a GPT-partitioned disk — check GPT issues subsection for more information.
3. Follow other steps on the Mount troubleshooting diagram to find the cause of the issue. Update/-
fix Kernel source code (if necessary) and request new driver for the new Kernel from Paragon
Software.
Analyze returned status and check output of (dmesg | tail). In case of failure, follow the ?? to find
possible causes and and try to mount the partition again using the same or different mount options, if
needed (see Mount options subsection).
If there is still a problem mounting the partition fill out Paragon’s online request form from your user
account so we could help you with the issue.
4.2 Mounting and unmounting partitions
Mounting NTFS and HFS+ volumes
To mount volume using UFSD driver, use mount command with FS type set to ufsd, e.g.:
# mount -t ufsd /dev/sda1 /mnt/sda1
Sometimes volumes cannot be mounted using ’mount’ command, for example:
# mount -t ufsd /dev/sdd1 /mnt/sdd1
mount: wrong fs type, bad option, bad superblock on /dev/sdd1,
missing codepage or helper program, or other error
In some cases useful info is found in syslog - try
Copyright© 1994-2017 Paragon Technologie GmbH. All rights reserved.