Vendor specific cdrom error messages
I got the following error trying to burn a DVD on an IBM USB2 DVD-R burner:
Nov 7 11:40:36 makani kernel: cdrom: This disc doesn't have any tracks I recognize! Nov 7 11:41:59 makani kernel: sr 0:0:0:0: SCSI error: return code = 0x8000002 Nov 7 11:41:59 makani kernel: sr0: Current: sense key: Data Protect Nov 7 11:41:59 makani kernel: ASC=0x27 <<vendor>> ASCQ=0xff
This is on Fedora Core 4 and kernel 2.6.13-1.1532_FC4.
It turns out that this is because the drive did not have enough power (it was not plugged into the separate ac adapter). I was able to determine this by booting into Windows, which gave me a nice descriptive error message.
I was wondering if it makes sense for the kernel drivers to know these error messages and report better errors, of it should be left up to user space tools.
- Orion
Quoted 11 lines · Orion Poplawski
I got the following error trying to burn a DVD on an IBM USB2 DVD-R burner:
Nov 7 11:40:36 makani kernel: cdrom: This disc doesn't have any tracks I recognize! Nov 7 11:41:59 makani kernel: sr 0:0:0:0: SCSI error: return code = 0x8000002 Nov 7 11:41:59 makani kernel: sr0: Current: sense key: Data Protect Nov 7 11:41:59 makani kernel: ASC=0x27 <<vendor>> ASCQ=0xffThis is on Fedora Core 4 and kernel 2.6.13-1.1532_FC4.
Quoted 8 lines
It turns out that this is because the drive did not have enough power (it was not plugged into the separate ac adapter). I was able to determine this by booting into Windows, which gave me a nice descriptive error message.
I was wondering if it makes sense for the kernel drivers to know these error messages and report better errors, of it should be left up to user space tools.
I think that you can guess the answer to the above query. Asc and/or ascq codes >= 0x80 (and <= 0xff) mark the additional sense code as vendor specific.
The ascq code looks suspicious. An asc/ascq tuple of <0x27,0x0> ("Write protected") would tie in pretty well with the sense key of "Data Protect". A better choice might be <0x5e,0x0> "Low power condition on".
Doug Gilbert
Quoted 17 lines · Douglas Gilbert
Quoted 16 lines · Orion Poplawski
I got the following error trying to burn a DVD on an IBM USB2 DVD-R burner:
Nov 7 11:40:36 makani kernel: cdrom: This disc doesn't have any tracks I recognize! Nov 7 11:41:59 makani kernel: sr 0:0:0:0: SCSI error: return code = 0x8000002 Nov 7 11:41:59 makani kernel: sr0: Current: sense key: Data Protect Nov 7 11:41:59 makani kernel: ASC=0x27 <<vendor>> ASCQ=0xffThis is on Fedora Core 4 and kernel 2.6.13-1.1532_FC4.
It turns out that this is because the drive did not have enough power (it was not plugged into the separate ac adapter). I was able to determine this by booting into Windows, which gave me a nice descriptive error message.
Quoted 7 lines
Quoted 3 lines
I was wondering if it makes sense for the kernel drivers to know these error messages and report better errors, of it should be left up to user space tools.
I think that you can guess the answer to the above query. Asc and/or ascq codes >=
0x80(and <=0xff) mark the additional sense code as vendor specific.
Sorry, I'm a bad guesser. So, user space?
Quoted 4 lines
The ascq code looks suspicious. An asc/ascq tuple of <0x27,0x0> ("Write protected") would tie in pretty well with the sense key of "Data Protect". A better choice might be <0x5e,0x0> "Low power condition on".
But we don't have any choice here right? Isn't this simply what the drive returns to us? Are these codes passed on to user space?
Sorry, completely unfamiliar with the linux scsi stack. Just trying to get the tools (dvd+rw-tools in this case) to return more informative error messages and thought I'd start from the bottom.