Skip to content
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

Is this bad? Compression signature was 4, expected 3. #13

Open
danwdart opened this issue Jan 8, 2021 · 9 comments
Open

Is this bad? Compression signature was 4, expected 3. #13

danwdart opened this issue Jan 8, 2021 · 9 comments

Comments

@danwdart
Copy link

danwdart commented Jan 8, 2021

I got:
\Windows\System32\MRT.exe: Compression signature was 4, expected 3. with an exit code of 1. I'm not sure if it finished.
Is that bad?
Ta

@sonicrules1234
Copy link

sonicrules1234 commented Jan 9, 2021

I have the same error but on a different file. It didn't finish.

@danwdart
Copy link
Author

danwdart commented Jan 9, 2021

I pretty much gave up after I copied manually - and I guess the metadata didn't copy with it, and it didn't actually boot.
It's on a latest insider windows 10 build, so maybe it's something new the dev didn't expect.

I'd like to be able to copy to a subvolume / subvolume image to import though, which is what I was trying to do eventually in the first place.

@sonicrules1234
Copy link

sonicrules1234 commented Jan 10, 2021

I pretty much gave up after I copied manually - and I guess the metadata didn't copy with it, and it didn't actually boot.
It's on a latest insider windows 10 build, so maybe it's something new the dev didn't expect.

I'd like to be able to copy to a subvolume / subvolume image to import though, which is what I was trying to do eventually in the first place.

You should use btrfs send and receive instead of an image. There are ways to do it over a network if you have to. winbtrfs's readme says it supports send and receive.

@danwdart
Copy link
Author

You should use btrfs send and receive...

I couldn't even get to that point is my point. I'd have done something similar if I'd actually ended up with a btrfs volume.

@ghost
Copy link

ghost commented Jan 19, 2021

I have a similar issue, except mine says 2, expected 3.

@imponateado
Copy link

imponateado commented Mar 29, 2021

same, minen says 7 instead of 3
and I was using the latest Windows 7 ISO (August) from heidoc download utility
got this error on a .NET file, something with .nzz as the extension
and It didn't finish

@Scorg
Copy link

Scorg commented Apr 9, 2022

It seems the python implementation does not check the signature, and only writes the value 3 for when data was not compressed. Should there even be a check?
Edit: the line is here

@florensie
Copy link

\SteamLibrary\steamapps\common\BioShock 2 Remastered\ContentBaked\pc\BinkMovies\gul_sinc_dies.bik: Compression signature was 1, expected 3.

@JoshDoesStuff
Copy link

Hey, is there any fix to this or a workaround? Tried compressing because there wasn't enough storage for metadata (thought maybe 10gb was enough, guess not), but it crashes a Sig 1 expected 3.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

6 participants