Skip to contentSkip to conversation

buffer io error on device sr0?

DISCUSSION Thomas Fjellstrom 2 participants 3 messages Oct 13, 2009 – Oct 14, 2009

lore
Share & tools
lore
#0 lore raw

I'm not sure which version it started, but it seems at least 2.6.32-rc3-git2 has issues with detecting blank DVDR disks.

[220595.198654] cdrom: This disc doesn't have any tracks I recognize!
[220595.298488] sr 3:0:0:0: [sr0] Unhandled sense code
[220595.298492] sr 3:0:0:0: [sr0] Result: hostbyte=DID_OK 
driverbyte=DRIVER_SENSE
[220595.298496] sr 3:0:0:0: [sr0] Sense Key : Blank Check [current]
[220595.298501] sr 3:0:0:0: [sr0] Add. Sense: No additional sense information
[220595.298505] sr 3:0:0:0: [sr0] CDB: Read(10): 28 00 00 00 00 00 00 00 01 00
[220595.298514] end_request: I/O error, dev sr0, sector 0
[220595.298518] Buffer I/O error on device sr0, logical block 0
[220595.304554] sr 3:0:0:0: [sr0] Unhandled sense code
[220595.304562] sr 3:0:0:0: [sr0] Result: hostbyte=DID_OK 
driverbyte=DRIVER_SENSE
[220595.304570] sr 3:0:0:0: [sr0] Sense Key : Blank Check [current]
[220595.304579] sr 3:0:0:0: [sr0] Add. Sense: No additional sense information
[220595.304588] sr 3:0:0:0: [sr0] CDB: Read(10): 28 00 00 00 00 00 00 00 01 00
[220595.304609] end_request: I/O error, dev sr0, sector 0
[220595.304616] Buffer I/O error on device sr0, logical block 0

Unless its supposed to be this way. Although I didn't receive any kind of notification when inserting the disk, as I used to (could be a hal/kde error, but the logs in dmesg seem to hint otherwise).

Signature · 2 lines
Thomas Fjellstrom
[email protected]
#1 lore raw
Quoted 21 lines · Thomas Fjellstrom

I'm not sure which version it started, but it seems at least 2.6.32-rc3-git2 has issues with detecting blank DVDR disks.

[220595.198654] cdrom: This disc doesn't have any tracks I recognize!
[220595.298488] sr 3:0:0:0: [sr0] Unhandled sense code
[220595.298492] sr 3:0:0:0: [sr0] Result: hostbyte=DID_OK
driverbyte=DRIVER_SENSE
[220595.298496] sr 3:0:0:0: [sr0] Sense Key : Blank Check [current]
[220595.298501] sr 3:0:0:0: [sr0] Add. Sense: No additional sense information
[220595.298505] sr 3:0:0:0: [sr0] CDB: Read(10): 28 00 00 00 00 00 00 00 01 00
[220595.298514] end_request: I/O error, dev sr0, sector 0
[220595.298518] Buffer I/O error on device sr0, logical block 0
[220595.304554] sr 3:0:0:0: [sr0] Unhandled sense code
[220595.304562] sr 3:0:0:0: [sr0] Result: hostbyte=DID_OK
driverbyte=DRIVER_SENSE
[220595.304570] sr 3:0:0:0: [sr0] Sense Key : Blank Check [current]
[220595.304579] sr 3:0:0:0: [sr0] Add. Sense: No additional sense information
[220595.304588] sr 3:0:0:0: [sr0] CDB: Read(10): 28 00 00 00 00 00 00 00 01 00
[220595.304609] end_request: I/O error, dev sr0, sector 0
[220595.304616] Buffer I/O error on device sr0, logical block 0
Quoted 3 lines

Unless its supposed to be this way. Although I didn't receive any kind of notification when inserting the disk, as I used to (could be a hal/kde error, but the logs in dmesg seem to hint otherwise).

Something tried to read off the disk and the drive reported "no way, it's blank". That's all this indicates. Most likely HAL or something is doing the read..

#2 lore raw
Quoted 24 lines · Robert Hancock
Quoted 23 lines · Thomas Fjellstrom

I'm not sure which version it started, but it seems at least 2.6.32-rc3-git2 has issues with detecting blank DVDR disks.

[220595.198654] cdrom: This disc doesn't have any tracks I recognize!
[220595.298488] sr 3:0:0:0: [sr0] Unhandled sense code
[220595.298492] sr 3:0:0:0: [sr0] Result: hostbyte=DID_OK
driverbyte=DRIVER_SENSE
[220595.298496] sr 3:0:0:0: [sr0] Sense Key : Blank Check [current]
[220595.298501] sr 3:0:0:0: [sr0] Add. Sense: No additional sense
information [220595.298505] sr 3:0:0:0: [sr0] CDB: Read(10): 28 00 00 00
00 00 00 00 01 00 [220595.298514] end_request: I/O error, dev sr0, sector
0
[220595.298518] Buffer I/O error on device sr0, logical block 0
[220595.304554] sr 3:0:0:0: [sr0] Unhandled sense code
[220595.304562] sr 3:0:0:0: [sr0] Result: hostbyte=DID_OK
driverbyte=DRIVER_SENSE
[220595.304570] sr 3:0:0:0: [sr0] Sense Key : Blank Check [current]
[220595.304579] sr 3:0:0:0: [sr0] Add. Sense: No additional sense
information [220595.304588] sr 3:0:0:0: [sr0] CDB: Read(10): 28 00 00 00
00 00 00 00 01 00 [220595.304609] end_request: I/O error, dev sr0, sector
0
[220595.304616] Buffer I/O error on device sr0, logical block 0
Quoted 7 lines
Quoted 3 lines

Unless its supposed to be this way. Although I didn't receive any kind of notification when inserting the disk, as I used to (could be a hal/kde error, but the logs in dmesg seem to hint otherwise).

Something tried to read off the disk and the drive reported "no way, it's blank". That's all this indicates. Most likely HAL or something is doing the read..

Ah, I was reading it as "Someone is checking for a disk, lets return an error instead of just saying the disk is blank".

Thanks for the clarification.

Quoted 6 lines

--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to [email protected]
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/

Signature · 2 lines
Thomas Fjellstrom
[email protected]