"Unexpected end of achive" error only in 15.09 and later

Brought to you by: myspace, p7zip

#180 "Unexpected end of achive" error only in 15.09 and later

Milestone: v1.0 (example)

Status: open

Owner: nobody

Labels: None

Priority: 5

Updated: 2016-06-21

Created: 2016-05-25

Creator: ZenWalker

Private: No

error in all the isos on http://slackware.uk/people/alien-slacklive/latest/

for example, about this iso:

http://slackware.uk/people/alien-slacklive/latest/slackware64-live-xfce-current.iso

listing the contents with "7z l", p7zip 15.09 and 15.14 shows the error message:

"Unexpected end of archive"

and with p7zip 9.20 has no errors

what happens here?

Discussion

Igor Pavlov - 2016-05-26

There are 3 problems with that archive.

1) There is empty file EFI\BOOT\SLACKWARELIVE
that contains negative (-16) value at "Location of Extent" field. It was the problem for 7-zip - too big value as unsigned 32-bit.
Probably I'll try to fix that thing.

2) That file uses GPT and ISO formats at same time.
And probably GPT is main container. If we change the extension of file to gpt extension, 7-Zip can use GPT handler instead of ISO handler.

3) There is warning about 512 empty bytes after the end of GPT archive.
Probably Ill try to fix it too.

If you would like to refer to this comment somewhere else in this project, copy and paste the following link:

ZenWalker - 2016-05-30

thanks

why p7zip 9.20 has no errors ?

If you would like to refer to this comment somewhere else in this project, copy and paste the following link:

Igor Pavlov - 2016-05-31

New 7-Zip checks that the size of payload of archive is equal to size of file.
Old 7-Zip just ignored that thing.

If you know why SLACKWARELIVE item contains negative "Location of Extent" value, please notifiy me.
Do you know what software was used to create that archive?

If you would like to refer to this comment somewhere else in this project, copy and paste the following link:

ZenWalker - 2016-06-06

ISO file created with mkisofs

If you would like to refer to this comment somewhere else in this project, copy and paste the following link:

Igor Pavlov - 2016-06-06

Are there problems with another ISOs created with mkisofs?
You can try to create such iso.

If you would like to refer to this comment somewhere else in this project, copy and paste the following link:

ZenWalker - 2016-06-21

hello, one user creates the iso with these args:

mkisofs -hide-rr-moved -l -v -d -iso-level 3 -r -J -V "example" -b boot/syslinux/isolinux.bin -c boot/syslinux/isolinux.boot -no-emul-boot -boot-load-size 4 -boot-info-table -eltorito-alt-boot -eltorito-platform 0xEF -eltorito-boot EFI/boot/efiboot.img -no-emul-boot -o "example.iso" example

In http://forum.porteus.org/viewtopic.php?f=117&t=5928&start=90 "scdbackup" wrote:
" as developer of xorriso i have to nitpick that it is not the size of the ISO but the existence
" of empty files which makes mkisofs output indigestible for 7z.
" mkisofs uses block address 4294967280 (aka 0xfffffff0 aka -16) for files which are no
" directories and contain no data bytes.
" 7z checks sanity of block addresses versus ISO size.

little more info in: https://github.com/mate-desktop/engrampa/issues/128

thanks

If you would like to refer to this comment somewhere else in this project, copy and paste the following link:

Log in to post a comment.