Corrupt File or wrong password Error

[G4ME]

I have a folder with multiple rar archieves split into parts. When I try to extract them with ./unrarall -s path/to/files I get the error "Corrupt file or wrong password". So I checked /home/user/.unrar_passwords for the correct password. This file is per line right?

Here is the output I get when running the command. Please note that when I run unrar e xxx.part01.rar it works(same password, same archieve)

pi@mmc:/path/to/files $ ./unrarall -s Dir\ with\ some\ spaces\ between/ Working over directory "Dir with some spaces between/" Extracting (e) "Dir with some spaces between/file-se.part01.rar"... Checksum error in the encrypted file /path/to/files/Dir\ with\ some\ spaces\ between/file-se.part01.rar. Corrupt file or wrong password.

Anyone got an idea?

[delcypher]

@G4ME

I have a folder with multiple rar archieves split into parts. When I try to extract them with ./unrarall -s path/to/files I get the error "Corrupt file or wrong password". So I checked /home/user/.unrar_passwords for the correct password. This file is per line right?

Yes it's one password per line.

Here is the output I get when running the command. Please note that when I run unrar e xxx.part01.rar it works(same password, same archieve)

> Anyone got an idea? I'm not sure what is wrong here but a few things worth noting is that * using 7z to do extraction fails if both the header and contents are password protected (if just the contents are password protected it seems to work fine). * unrarall will try each password one by one so you will see fail extraction attempts for each password that is wrong. So if you have multiple passwords in the password file you will see all the failed attempts. If you change the shebang in the script from ``` #!/bin/bash ``` to ``` #!/bin/bash -x ``` you will see all the commands executed by the script. This might help you debug what is happening.

[arfoll]

Closing as no more info