How to Back Up an NTFS Partition with Partclone on Fedora Linux

When it comes to disk cloning and partition backups, Clonezilla is often the go-to tool. But under the hood, Clonezilla relies on several open-source utilities — one of the most important being Partclone. You can use Partclone directly on Linux to back up and restore partitions, which is especially handy if you want a simple command-line approach without booting into Clonezilla.


Installing Partclone on Fedora

First, make sure Partclone is installed. Fedora includes it in its repositories, so you just need:

sudo dnf install partclone

You can verify the installation with:

partclone.ntfs -v

Backing Up an NTFS Partition

Suppose you want to back up an NTFS partition (for example, /dev/nvme0n1p3) to an external drive. The syntax looks like this:

sudo partclone.ntfs -c \
    -s /dev/nvme0n1p3 \
    -o /path/to/backup/nvme0n1p3.img

Breakdown of the command:

  • -c → copy mode (create a backup)
  • -s → source partition
  • -o → output image file location

This creates an image file containing the used blocks of your NTFS partition.


Restoring the Partition

If you ever need to restore the partition, reverse the process:

sudo partclone.ntfs -r \
    -s /path/to/backup/nvme0n1p3.img \
    -o /dev/nvme0n1p3

⚠️ Warning: The restore command will overwrite the target partition, so double-check the device path before running it.


Optional: Save Space with Compression

You can combine Partclone with gzip or xz to compress your backup on the fly:

sudo partclone.ntfs -c -s /dev/nvme0n1p3 | gzip -c > /path/to/backup/nvme0n1p3.img.gz

And to restore:

gzip -dc /path/to/backup/nvme0n1p3.img.gz | sudo partclone.ntfs -r -o /dev/nvme0n1p3

Final Thoughts

Partclone is a powerful tool on its own, not just something tucked inside Clonezilla. If you’re looking for a straightforward way to clone or back up NTFS partitions on Fedora Linux, the commands above will get you started.

dd if of

On Fedora Linux, you can easily write an ISO file to a USB drive using the dd command. Here’s a simple and reliable example:

sudo dd if=/path/to.iso of=/dev/sdX bs=4M status=progress oflag=sync

Replace /path/to.iso with the ISO file location and /dev/sdX with your USB device (not a partition like /dev/sdX1).

🔧 Disable IPv6 in Rocky Linux 8 (NetworkManager)

If nmcli refuses to change ipv6.method because of leftover settings, the fastest fix is to recreate the connection with IPv6 disabled.

# Show current connections
nmcli con show

# Delete old connection
nmcli con delete "System eth0"

# Recreate with IPv4 only (replace IP/GW with yours)
nmcli con add con-name "eth0" ifname eth0 type ethernet \
ipv4.addresses 192.168.1.100/24 ipv4.gateway 192.168.1.1 \
ipv4.method manual ipv6.method disable

# Bring it up
nmcli con up "eth0"

# Verify
nmcli con show "eth0" | grep ipv6.method
ip a | grep inet6

✅ Result: ipv6.method: disable and no IPv6 addresses.

Download a WordPress Site with wget

WordPress URLs often create messy files like index.html?p=1759. Use this command for a clean offline copy:

wget -m -p -k -np -l 2 --adjust-extension --restrict-file-names=windows https://example.com

Flags explained:

  • -m mirror mode
  • -p requisites (images, CSS, JS)
  • -k convert links
  • -np no parent
  • -l 2 limit depth
  • --adjust-extension add .html
  • --restrict-file-names=windows clean filenames

✅ Result: a browsable offline WordPress site without messy filenames.

Disable Standby

Step 1: Edit logind.conf
Open a terminal.

Edit the logind configuration file with a text editor, e.g.:

bash
Copy
Edit
sudo nano /etc/systemd/logind.conf
Find (or add) the following lines, and set them like this:

ini
Copy
Edit
HandleLidSwitch=ignore
HandleLidSwitchDocked=ignore
HandleLidSwitchExternalPower=ignore
This tells systemd-logind not to suspend or power down the system when the lid is closed, including when docked or on external power.

Save and exit the file (in nano, press Ctrl+O, then Enter, then Ctrl+X).

Step 2: Restart systemd-logind
Apply the changes without rebooting:

bash
Copy
Edit
sudo systemctl restart systemd-logind
⚠️ This might log you out or restart your session. Save your work beforehand.

NMCLI

When you use nmcli to add routes via commands like nmcli con mod +ipv4.routes, the routes are added to the network connection profile and are generally persistent across reboots. These routes are stored in NetworkManager’s configuration files, so they should be re-applied each time the network connection is brought up.

However, there are a few things to keep in mind:

  1. Connection Profile: The routes you add with nmcli are tied to a specific connection profile. If the connection profile is modified or deleted, the routes associated with it might be affected.
  2. Configuration Files: NetworkManager saves its configuration in files located in /etc/NetworkManager/system-connections/. You can check these files to ensure your routes are listed there.
  3. System Changes: If you make changes to your network setup or NetworkManager configuration files directly, it might impact how routes are handled.
  4. Manual Network Changes: If you manually modify network settings or use other network management tools, this could potentially override or conflict with the settings you applied through nmcli.

In summary, routes added with nmcli should persist through reboots as long as the connection profile they are associated with remains unchanged and NetworkManager is properly managing the connection.

kubernetes-csi/csi-driver-nfs

https://github.com/kubernetes-csi/csi-driver-nfs/blob/master/charts/README.md

CSI driver example

You can use NFS CSI Driver to provision Persistent Volumes statically or dynamically. Please read Kubernetes Persistent Volumes documentation for more information about Static and Dynamic provisioning.

Please refer to driver parameters for more detailed usage.

Prerequisite