PDA

View Full Version : Inconsistency in detecting cdrom



since1991sanchit
2022-03-19, 09:20
I inserted the cd-r in cdrom and it appears under Disks and Devices section in the tool bar. I can also see it in left panel in dolphin and browse the contents in the cd.
On running following commands the outputs are shown inline:

❯ blkid
/dev/sr0: BLOCK_SIZE="2048" UUID="2008-06-30-10-58-00-0" LABEL="Rudra Kawach" TYPE="iso9660"



❯ sudo lshw -c disk
[sudo] password for sanchit:
*-disk
description: ATA Disk
product: ST500LT012-1DG14
physical id: 0
bus info: scsi@0:0.0.0
logical name: /dev/sda
version: SDM1
serial: SBY09YN5
size: 465GiB (500GB)
capabilities: gpt-1.00 partitioned partitioned:gpt
configuration: ansiversion=5 guid=b5ae8edf-9ea8-435a-b410-c147b32cdcd7 logicalsectorsize=512 sectorsize=4096
*-cdrom
description: DVD-RAM writer
product: DVD+-RW SU-208GB
vendor: TSSTcorp
physical id: 1
bus info: scsi@1:0.0.0
logical name: /dev/cdrom
logical name: /dev/sr0
version: D100
capabilities: removable audio cd-r cd-rw dvd dvd-r dvd-ram
configuration: ansiversion=5 status=ready
*-medium
physical id: 0
logical name: /dev/cdrom


But on subsequent inserts, the behavior is pretty inconsistent. Sometimes it is not detected by cdrom and won't appear in output of sudo lshw -c disk



*-disk
description: ATA Disk
product: ST500LT012-1DG14
physical id: 0
bus info: scsi@0:0.0.0
logical name: /dev/sda
version: SDM1
serial: SBY09YN5
size: 465GiB (500GB)
capabilities: gpt-1.00 partitioned partitioned:gpt
configuration: ansiversion=5 guid=b5ae8edf-9ea8-435a-b410-c147b32cdcd7 logicalsectorsize=512 sectorsize=4096
*-cdrom
description: DVD-RAM writer
product: DVD+-RW SU-208GB
vendor: TSSTcorp
physical id: 1
bus info: scsi@1:0.0.0
logical name: /dev/cdrom
logical name: /dev/sr0
version: D100
capabilities: removable audio cd-r cd-rw dvd dvd-r dvd-ram
configuration: ansiversion=5 status=nodisc


Other times the disc is detected, but the block identification (blkid) shows nothing.

This inconsistent behavior is weird. Any clues what might be going wrong?