[k3b] [Bug 387765] K3b says that blu-ray ISO is not recognizable

[Thomas Schmitt]

https://bugs.kde.org/show_bug.cgi?id=387765

--- Comment #10 from Thomas Schmitt <scdbackup at gmx.net> ---
Hi,

regardless of the question why K3B does not recognize the image file as
ISO 9660 there stays the question whether and why it then really refuses
to write.
So please answer the question what happened after you got the warning
  "Type of image file is not recognizable. Do you want to burn it anyway?"
Did you answer "Yes" ?

If you only have BD-R media, then better wait with a new attempt until we
solved the file format riddle.
If you have a BD-RE, then please repeat your burn attempt and record as
many info as possible until it really refuses (or starts to burn).


----------------------------------------------------------------------
Now for the ISO riddle:

> My image is an ISO file.
> My ISO file system is UDF.

To all accounts it is not.
Program "file" should say "... ISO 9660 CD-ROM filesystem ..." or
"... UDF filesystem ..." if an ISO 9660 superblock was present.

(As said, UDFs have a ISO superblock which might only lead to one file
 saying: "This is UDF and not ISO 9660. Mount as UDF to see more files.")


> K3b::Iso9660::openArchive no volume descriptors

That's ReadISO9660() confirming what program "file" says.

Another test would be to try to mount the image file on GNU/Linux.
I bet the reply is much like:
  "mount: wrong fs type, bad option, bad superblock ..."


>From initial message
> I can mount and read the same ISO file using cdemu client.

This does not exclude .NRG:
  https://wiki.archlinux.org/index.php/CDemu
states
  "It enables you to use other disk image formats that contain more than
   just the standard ISO-9660 filesystem, for instance .bin/.cue, .nrg,
   or .ccd images. "

According to wikipedia, a .NRG file is recognizable by its final 12 bytes.
Try this:

  end=$(ls -l file.iso | awk '{print $5}')
  start=$(expr $end - 12)
  echo $start

This should tell a large number in the range of 25 billion. Then read
12 bytes from that position of the file:

  dd bs=1 skip=$start count=12 if=file.iso | od -c

If you then read "... N   E   R   O ..." or "N   E   R   5 ...", then
it is an .NRG file (which probably contains your ISO/UDF).


> (K3b::CloneTocReader) could not open file  "/mnt/WIN7/Users/Strangiato/Desktop/file.iso.toc"
> (K3b::CueFileParser) could not open file  "/mnt/WIN7/Users/Strangiato/Desktop/file.iso.cue"

Might be that K3B looks for other input formats which it understands.
.CUE and .TOC are description files for CD layouts. They are usually
accompanied by one or more data files with payload.
Well, we already know that this is not the case here.


Have a nice day :)

Thomas

-- 
You are receiving this mail because:
You are the assignee for the bug.