Re: kernel errors

["Thomas Schmitt" <scdbackup@gmx.net>]

Hi,

Richmond wrote:
> kernel: [    9.506798] sr 3:0:0:0: [sr0] tag#12 FAILED Result: hostbyte=DID_OK driverbyte=DRIVER_SENSE cmd_age=2s
> kernel: [    9.507009] sr 3:0:0:0: [sr0] tag#12 Sense Key : Not Ready [current]
> kernel: [    9.507146] sr 3:0:0:0: [sr0] tag#12 Add. Sense: Medium not present - tray closed
> kernel: [    9.507304] sr 3:0:0:0: [sr0] tag#12 CDB: Read(10) 28 00 00 07 ff fc 00 00 02 00

Your optical drive gets asked for 2 blocks iand answers that there is no
medium recognized in the tray. The request was to read from block 0x07fffc
= 524284 = 1023.9921875 MiB = 1 GiB  - 4 KiB.
This is not a usual medium capcity. So i wonder from where the caller had
that block address.


> kernel: [    9.507731] sr 3:0:0:0: [sr0] tag#31 unaligned transfer

I wonder what might have caused this. But this line brings me to
  https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=948358
where pioruns@gmail.com tried to get this processed as bug of udev.
No solution was found.


> kernel: [    9.602797] sr 3:0:0:0: [sr0] tag#3 FAILED Result: hostbyte=DID_OK driverbyte=DRIVER_SENSE cmd_age=0s
> kernel: [    9.608514] sr 3:0:0:0: [sr0] tag#3 Sense Key : Not Ready [current]
> kernel: [    9.614297] sr 3:0:0:0: [sr0] tag#3 Add. Sense: Medium not present - tray closed
> kernel: [    9.620170] sr 3:0:0:0: [sr0] tag#3 CDB: Read(10) 28 00 00 00 00 00 00 00 02 00

This read attempt wanted to get 2 blocks from block address 0.
More plausible as a wild guess, than 1 GiB - 4 KiB.


What happens if you give the drive a readable DVD ?
Maybe the software which issues the READ commands shows up with some more
enlightening complaint.


Have a nice day :)

Thomas