@CwF: Thanks, I understand you now. Nonetheless . . .
Code: Select all
root@newlaptop:/home/nick# dd if=/dev/cdrom of=test.iso bs=2048 count=8191
dd: error reading '/dev/cdrom': Input/output error
0+0 records in
0+0 records out
0 bytes copied, 0.102789 s, 0.0 kB/s
root@newlaptop:/home/nick#
Same with all smaller multiples of bs=512 and a few larger multiples of 2048.
So unless you can convince me otherwise, I'm going to assume @p.H is right about dd
not being able to handle audio tracks.
Also, now (first without
, but also after reboot) I don't get all the extra error info from isoinfo as root posted just now. Something is unpredictable here. My desktop is mate, using caja file browser, which does some fancy and at times weirdly unpredictable things with mounting devices. Not sure if that is connected.
In any case inserting an audio CD into drive causes caja to mount the disk automatically, recognize it as audio and allows you to copy the tracks directly into .wav files, which is convenient.
EDIT: Just realized all of the symptoms described
below are only because of the following:
Code: Select all
root@newlaptop:/media# cat /etc/fstab | grep cdrom
/dev/sr0 /media/cdrom0 udf,iso9660 user,noauto 0 0
root@newlaptop:/media#
and so are a consequence of strange interactions between the new fangled way of device management used by mate/caja and the traditional way involving mostly just fstab. Removing this from fstab avoids this confusion in caja, however I need it so I can access real iso data disks via /media/cdrom -> /media/cdrom0. Anyway,obviously the following observations have nothing to do with what I'm trying to resolve with @CwF:
At the same time as caja mounts the disk (shown there as device "Audio DIsk"), "cdrom0" also shows up there then as a "mountable" device, though it actually can't be accessed from caja, eventually disappears, and once even weirdly stopped reappearing at all in caja's device list when audio CDs were reinserted (haven't reproduced that behavior again yet).