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?
33 Paragon NTFS&HFS+ for Linux 9.5
# ./sysdump -s /dev/sdc1
Scanning NTFS...
Added 13 files/dirs from $Extend .
Recognized as NTFS.
Dumping "/dev/sdc1" (465.76 Gb) ...
Dump finished. File size 1248334848 bytes (including tail)
Collecting system information...
System information was saved to /home/UFSD_utilites/i686
,→.3.13.0.20141105.tar
8.4 Changing the name of output archive
Name of the output archive can be changed by using the additional ’-o’ parameter and adding new
file name. For example:
# ./sysdump -s /dev/sdc1 -o test.tar
Scanning NTFS...
Added 13 files/dirs from $Extend .
Recognized as NTFS.
Dumping "/dev/sdc1" (465.76 Gb) ...
Dump finished. File size 1248334848 bytes (including tail)
Collecting system information...
System information was saved to /home/UFSD_utilites/test.tar
8.5 Output file description
The Sysdump utility creates a single tar archive in the working folder with its’ work results for easier
data transfer to Paragon team. This archive can be easily uncompressed with the tar utility, e.g.:
# tar -xf ./x86_64.3.11.9.20131211.tar
There are several files inside archive:
• dmesg - contents of the ’dmesg’ command output
• dumpbin.gz - compressed metadata image of the test volume
• dumpbin.md5 -md5 checksum for the collected image itself, not the archive file
• modules - list of all Kernel modules (*.ko files) found on the platform
• sysinfo - file with platform system information: list of storage devices, Linux Kernel version, version
of the loaded UFSD driver, CPU, memory information, etc.
8.6 Delivering collected data to Paragon
Please send the tar file, generated by the ’Sysdump’ utility to your support contact at Paragon Soft-
ware via e-mail, via ’My account’ page at Paragon Software Support Portal.
8.7 Privacy policy
Paragon’s Sysdump utility doesn’t collect any personal or user-sensitive information. Platform data
is obtained via usage of the native Linux utilities and standard system files (e.g. fdisk, parted,
Copyright© 1994-2017 Paragon Technologie GmbH. All rights reserved.