Russ Kubes

Yes, that's what it looks like. I was given the machine second hand so I don't know the full process they used when they converted it. The VMFS tools knew enough that it wasn't VMFS. Parted knew it was NTFS. Even ntfsfix and mount.ntfs had no problem with it. It just seemed the generic "mount" command was getting confused by the left over metadata and couldn't mount it. That's the component that was still identifying it as VMFS volume member. Since I removed that signature, I no longer have an i...

I also tried dropping to shell and running: partclone.ntfs -c -s /dev/sda1 -o ./test This executed successfully and backed up the contents of the partition. So, it seems partclone is able to back it up, but for some reason Clonezilla doesn't think it can. Edit: My apologies, I was able to find the Clonezilla log. I see that the drive was detected as a VMFS_Member. It is true that this drive used to be in an ESXi instance, it had since been reformatted to NTFS. VMFS6 Tools correctly identifies that...

I also tried dropping to shell and running: partclone.ntfs -c -s /dev/sda1 -o ./test This executed successfully and backed up the contents of the partition. So, it seems partclone is able to back it up, but for some reason Clonezilla doesn't think it can. Edit: My apologies, I was able to find the Clonezilla log. I see that the drive was detected as a VMFS_Member. It is true that this drive used to be in an ESXi instance, it had since been reformatted to NTFS. VMFS6 Tools correctly identifies that...

I also tried dropping to shell and running: partclone.ntfs -c -s /dev/sda1 -o ./test This executed successfully and backed up the contents of the partition. So, it seems partclone is able to back it up, but for some reason Clonezilla doesn't think it can.

I also tried dropping to shell and running: partclone -c -s /dev/sda1 -o ./test This executed successfully and backed up the contents of the partition. So, it seems partclone is able to back it up, but for some reason Clonezilla doesn't think it can.

There is a "new to me" server that I need to be able to back up. It has 2 drives, one is about 240GB and one is about 960GB. They both have NTFS partitions. The 240GB drive backs up without any issue, as expected. The 960GB volume CloneZilla 3.2.2-15 always tries to back up as raw. If I drop to the shell, I can use "mount.ntfs" and mount the 960GB volume without issue. So, I don't think there's an issue with the format/partition table. I've attached a screenshot of the parted 'print' output for both...

There is a "new to me" server that I need to be able to back up. It has 2 drives, one is about 240GB and one is about 960GB. They both have NTFS partitions. The 240GB drive backs up without any issue, as expected. The 960GB volume CloneZilla 3.2.2-15 always tries to back up as raw. If I drop to the shell, I can use "mount.ntfs" and mount the 960GB volume without issue. So, I don't think there's an issue with the format/partition table. I've attached a screenshot of the parted 'print' output for both...

I'm back to being puzzled and frustrated with this one. So, I reverted my configuration change to prevent oplocks (to allow them again), in order to ensure I could recreate the problem again. As expected, the problem was readily reproducible. I then tried the mount command that you suggested above, but oddly the problem still occurred. I then tried putting the "oplocks = no" configuration back into the smb.conf file and restarted Samba on the server again. I also unmounted the partimage and remounted...