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?
User manual 32
8 Sysdump utility
8.1 Introduction
In case Paragon team requires additional information on the test storage device and/or test platform
itself for the issue troubleshooting with specific NTFS/HFS+ volume(s), the sysdump utility can be
used to capture very compact images of volumes with file system inconsistencies. Additionally it
could be used to collect test platform system information: storage device summary, Kernel version,
loaded UFSD driver version and so on.
As volume images only include file system metadata, the risk of leaking sensitive data when using
sysdump is minimized.
8.2 Main functions
Main functions of the sysdump utility are:
• Capturing metadata image of the test volume
• Collecting HW sample system information.
Note that sysdump utility requires root privileges as they are needed for working with storage
devices on Linux platform.
When utility is run without additional options basic help is displayed
# ./sysdump
Dump NTFS/HFS/Ext volumes (metafiles only) and collect system information
,→.
Paragon’s Sysdump utility doesn’t collect any personal or user-sensitive
,→information.
Please refer to the ’Privacy policy’ described in the Sysdump utility
,→guide for more information.
Usage: sysdump [-s] [device] [-o <filename>]
-s collect system information
-o new file name (if name without suffix ".tar", then suffix ".tar"
,→will be added automatically)
E.g. sysdump /dev/hdb1
8.3 Using the sysdump utility to collect both platform system information and
metadata
1. Extract sysdump utility to a folder with read/write access.
2. In terminal change to the folder with the extracted sysdump utility. Use the following command to
capture the metadata image and to collect platform system information:
# ./sysdump -s /path/to/partition
3. This will create an archive named, based on platform parameters <Architecture>.<Kernel
version>.<date>.tar with storage device metadata image, its md5 sum and sample system
information:
Paragon Technologie GmbH
Leo-Wohleb-Straße 8, 79098 Freiburg, Germany