As suggested, I did some testing: I attached the same NTFS portable USB drive to my Windws PC and created a network share.
When I mount to that shared device from pi, the backup works without issue.
Which is proof there is not an inherent problem creating a Raspberry Pi OS image file on media formatted NTFS and mounted via SMB/CIFS.
So, there is certainly something different about how Netgear XR700 is presenting the device that is different than with how Windows does. They both use SMB/CIFS but maybe there a version issue or a bug with my READYSHARE.
The problem is clearly with the Netgear XR700 and its handling of SMB/CIFS.
Also, I see that the image-backup script tries to figure out the filesystem in order to choose the proper health-check utility to launch.
dosfsck is run on the BOOT (FAT) partition and e2fsck is run on the ROOT (EXT4) partition of the image file. Nothing unusual here.
My guess is that (1) since this drive is managed as a shared device, the e2fsck should not be used (for Windows or READYSHARE) and (2) that the image-backup script is not written in a way to sense that my mounted volume is shared, so it just dangerously runs the e2fsck tool anyway.
So, is there a backup solution that is recommended for pi devices with no removable storage? Perhaps, I should just hack the image-backup with an exit command just before the e2fsck call.
image-backup and its use of e2fsck works perfectly on Windows and other proper implementations of SMB/CIFS.
It's your Netgear XR700 that has a problem.
Perhaps, I should just hack the image-backup with an exit command just before the e2fsck call.
You are free to modify image-backup as you see fit for your own use, but please don't post a copy anywhere.
Statistics: Posted by RonR — Thu May 02, 2024 6:57 pm