-
Notifications
You must be signed in to change notification settings - Fork 28
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Invalid file signature error? #4
Comments
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: Line 75 in 171e9b9
|
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... |
Same error on a 500gb hdd run on Ubuntu 20.04 |
Same here, actually, Manjaro. REALLY hoping to try this out on my "VR Only" Windows installation for giggles. |
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 |
Reproduced on a 512GB NVME SSD. |
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. |
There must be multiple underlying issues causing this error then, because I'm experiencing it on an HDD with 4096 cluster size. |
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. |
hrm, I was probably measuring something other than what I thought (found it with linux commands). |
Have you tried doing as it says - running chkdsk and trying again? |
Yes, running chkdsk showed no errors, and a fresh install with sufficient space is giving the same issue. |
Is this still an issue on today's version? |
Yes sir, on version 20210105: Edit: This was tested on arch linux, I'm happy to provide any useful additional information. |
I am getting this issue on my 8TB hdd on Windows 10 (21H2) Edit: Got it again on Fedora 36, same drive. |
What causes this error? I attempted to use this to convert a 2TB hdd but it gave me that error.
On arch linux if that matters
The text was updated successfully, but these errors were encountered: