<b>Failed to backup partition</b> /dev/nvme0n1p2

[Brian Hand]

--The full error message is :
Failed to backup partition /dev/nvme0n1p2

The command used internally was:

partclone.ext4 --logfile /var/log/partclone.log --clone --source
/dev/nvme0n1p2 --output - | pigz --stdout -6 | split --suffix-length=2
--bytes=4GB - /mnt/backup/DECEMBER 6
ZILLA/2023-12-06-0151-img-rescuezilla/nvme0n1p2.ext4-ptcl-img.gz.

The output of the command was: Partclone v0.3.20 http://partclone.org
Starting to clone device (/dev/nvme0n1p2) to image (-)
Reading Super Block
extfsclone.c: FS has been mounted 1 times without being checked
Partclone fail, please check /var/log/partclone.log !

i have not had an error before. I use rescuezilla each and every month
I run Linux Mint 21.2 Cinnamon....fully updated
Rescuezilla is the latest: 5th March, 2023
E; condobloke@gmail.com

Help !...Please !
from Brian.

[Rescuezilla]

Hi Brian,

The key line of the error message block appears to be "extfsclone.c: FS has been mounted 1 times without being checked".

It sounds like partclone (the application that does the imaging) did not like the filesystem because it needs a filesystem check.

I recommend you run a filesystem check on that partition. Since it's an ext4 filesystem, you can do so within Rescuezilla using a command such as fsck /dev/nvme0n1p2 after opening a Terminal window.

Some Linux-based operating systems may actually automatically run the filesystem check every boot, so it may be the case that you just happened to restart into Rescuezilla in an awkward way this once.

Once the filesystem is healthy, the partclone should no longer be complaining when you use Rescuezilla to create your backup images as you have for previous months.

[Anonymous]

Hello again, imagine my surprise when I reran rescuezilla today....and everything went without a hitch.
Recently I inserted a command into terminal to run a fsck every 10th day.
sudo tune2fs -c 10 /dev/nvme0n1p2

I am left to wonder if this had some input into what I experienced. I will never know...iof only i had had my wits about me I would have run a fsck immediately when this happened.
Anyway...all good......rescuezilla is up and behaving again...the bakcup taken is restorable (i proved it )

Thanks for your time

brian

[Rescuezilla]

Hi Brian,

Glad you had a good experience with a Rescuezilla backup by configuring a filesystem check every 10 mounts (which is once every 10 days if you shutdown once a day).

Certainly it appears EXT4 filesystems aren't configured to automatically do filesystem checks by default. Eg,

sudo tune2fs -l /dev/path-to-partition | grep -i 'check\|maximum'
Maximum mount count:      -1
Last checked:             Tue Aug 25 19:04:30 2020
Check interval:           0 (<none>)

iof only i had had my wits about me I would have run a fsck immediately when this happened.

Certainly this is a situation where Rescuezilla (a tool that intends to be user-friendly) would optimally provide an error message with clear instructions on what went wrong. But even better, Rescuezilla could certainly have a default option to do a (read-only) filesystem check by default before even making the backup (though this would add to the time it takes to make a backup).