Invalid file signature error? about ntfs2btrfs HOT 18 OPEN

Is this still an issue on today's version?

Yes sir, on version 20210105: Invalid file signature (00000000, expected 454c4946)

Edit: This was tested on arch linux, I'm happy to provide any useful additional information.

from ntfs2btrfs.

Same, also on Arch Linux, when I was trying to convert a Windows 10 OS drive.

Just searched in source and found the line that throws that error:

from ntfs2btrfs.

Essentially it means "I've opened something that should be a file but isn't", which isn't very helpful. It looks like the program could do with being tested against more filesystems...

from ntfs2btrfs.

Same error on a 500gb hdd run on Ubuntu 20.04

from ntfs2btrfs.

Same here, actually, Manjaro. REALLY hoping to try this out on my "VR Only" Windows installation for giggles.

from ntfs2btrfs.

Same issue on my 2TB SSD. GDB trace:

If running in Windows, the program will exit without any output, but the file system is not converted.

from ntfs2btrfs.

Sector signature is 0, the entire block buffer is 0. Could be an empty block or a corrupt block? I have this error as well, CHKDSK says the disk is fine. Might be an issue relating to fragmented disks / SSDs and empty blocks.

Program exiting without input is an issue relating to stderr flushing, should be fixed with my PR #5

from ntfs2btrfs.

Sector signature is 0, the entire block buffer is 0. Could be an empty block or a corrupt block? I have this error as well, CHKDSK says the disk is fine. Might be an issue relating to fragmented disks / SSDs and empty blocks.

Program exiting without input is an issue relating to stderr flushing, should be fixed with my PR #5

Mine IS on an SSD now that you mention it

from ntfs2btrfs.

Reproduced on a 512GB NVME SSD.

from ntfs2btrfs.

I've looked into it further, and it appears that the underlying issue is that (as of Windows 10 build 2004) the Windows installer picks a cluster size of 512kb for partitions on an SSD.
The README states that Ntfs2Btrfs only supports cluster sizes of 4096kb.
It seems that for now a workaround would be to manually create the partition and give it a cluster size of 4096 when installing.

from ntfs2btrfs.

There must be multiple underlying issues causing this error then, because I'm experiencing it on an HDD with 4096 cluster size.

from ntfs2btrfs.

Could you give it a go on the latest version please?

@TheGlitch76 - that's news to me, are you sure about that? There's nothing on https://support.microsoft.com/en-gb/help/140365/default-cluster-size-for-ntfs-fat-and-exfat, which says that Windows only chooses sizes other than 4KB on really massive disks. https://docs.microsoft.com/en-us/openspecs/windows_protocols/ms-fsa/4e3695bd-7574-4f24-a223-b4679c065b63 was updated a week ago, and nothing there either.

from ntfs2btrfs.

Could you give it a go on the latest version please?

@TheGlitch76 - that's news to me, are you sure about that? There's nothing on https://support.microsoft.com/en-gb/help/140365/default-cluster-size-for-ntfs-fat-and-exfat, which says that Windows only chooses sizes other than 4KB on really massive disks. https://docs.microsoft.com/en-us/openspecs/windows_protocols/ms-fsa/4e3695bd-7574-4f24-a223-b4679c065b63 was updated a week ago, and nothing there either.

I now get "Error seeking to ffffffffd781c000" when pointing it at my Windows partition.

from ntfs2btrfs.

Could you give it a go on the latest version please?

@TheGlitch76 - that's news to me, are you sure about that? There's nothing on https://support.microsoft.com/en-gb/help/140365/default-cluster-size-for-ntfs-fat-and-exfat, which says that Windows only chooses sizes other than 4KB on really massive disks. https://docs.microsoft.com/en-us/openspecs/windows_protocols/ms-fsa/4e3695bd-7574-4f24-a223-b4679c065b63 was updated a week ago, and nothing there either.

hrm, I was probably measuring something other than what I thought (found it with linux commands).
Either way, it's getting past that now, but still failing.
Here's a log, but I think the issue may be that the drive is nearly full. I'll have to do some reorganizing of my partitions and try again with more space.

from ntfs2btrfs.

Have you tried doing as it says - running chkdsk and trying again?

from ntfs2btrfs.

Yes, running chkdsk showed no errors, and a fresh install with sufficient space is giving the same issue.

from ntfs2btrfs.

Is this still an issue on today's version?

from ntfs2btrfs.

I am getting this issue on my 8TB hdd on Windows 10 (21H2)
Invalid file signature (00000000, expected 454c4946).

Edit: Got it again on Fedora 36, same drive.

from ntfs2btrfs.