Thomas Schmitt wrote:
Hi,
/dev/sr1: flushing cache
/dev/sr1: closing track
/dev/sr1: closing session
:-[ CLOSE SESSION failed with SK=5h/INVALID FIELD IN CDB]: Input/output
Such a message is rarely harmless.
The drive wrote everything but failed
to finish properly.
Well,
Hi,
me:
Such a message is rarely harmless.
Jens:
Well, that's what I thought, but Andy Polyakov commented here:
http://www.mail-archive.com/cdwrite@other.debian.org/msg12106.html
Oh indeed. Now i remember.
I stepped into that puddle previously.
So for now we count it as harmless.
It is
Thomas Schmitt wrote:
When I read the block from /dev/sr0 what I get back is all-zeroes. The
corresponding block on the udf image is full of non-zero data.
the next 2048-byte block following 8585216 on /dev/sr1 is non-zero.
Ouchers.
That looks much like a failure of transport or
Hi,
So it certainly sees /some/ of the UDF info. Gack!
It would be quite some strange incident if a
zeroed block at a more or less random address
would make this all a valid empty UDF filesystem.
I am not sure whether the empty mount directory
is really caused by the altered block(s).
Maybe
4 matches
Mail list logo
