Re: My CD and DVD are messed up
- To: debian-user@lists.debian.org
- Subject: Re: My CD and DVD are messed up
- From: T o n g <mlist4suntong@yahoo.com>
- Date: Sat, 2 Jul 2011 14:37:35 +0000 (UTC)
- Message-id: <[🔎] iunaff$50q$1@dough.gmane.org>
- References: <iu4umf$l8q$2@dough.gmane.org> <pan.2011.06.25.17.49.24@gmail.com> <iuavs3$7r5$3@dough.gmane.org> <pan.2011.06.28.13.01.04@gmail.com> <iud0qg$cj0$1@dough.gmane.org> <pan.2011.06.28.17.07.07@gmail.com>
Hi,
Thanks everyone for the follow ups.
Sorry for responding late.
On Tue, 28 Jun 2011 17:07:08 +0000, Camaleón wrote:
>> On my system the /dev/cdrom is actually DVD while My CD is actually
>> /dev/ cdrom1.
>
> That does not match with a "correct" fstab file.
>
> Your primary device (dvd?) should point to "/dev/cdrom0" and secondary
> (cd-rom?) to "/dev/cdrom1".
Hmmm, Ok, maybe I've trimmed that trailing "0" from my primary device.
Here is how it looks now:
$ cat /etc/udev/rules.d/70-persistent-cd.rules
# This file maintains persistent names for CD/DVD reader and writer
devices.
# See udev(7) for syntax.
#
# Entries are automatically added by the 75-cd-aliases-generator.rules
# file; however you are also free to add your own entries provided you
# add the ENV{GENERATED}=1 flag to your own rules as well.
# DVD-RW_DVR-110D (pci-0000:00:06.0-scsi-0:0:1:0)
SUBSYSTEM=="block", ENV{ID_CDROM}=="?*", ENV{ID_PATH}=="pci-0000:00:06.0-
scsi-0:0:1:0", SYMLINK+="cdrom", ENV{GENERATED}="1"
SUBSYSTEM=="block", ENV{ID_CDROM}=="?*", ENV{ID_PATH}=="pci-0000:00:06.0-
scsi-0:0:1:0", SYMLINK+="cdrw", ENV{GENERATED}="1"
SUBSYSTEM=="block", ENV{ID_CDROM}=="?*", ENV{ID_PATH}=="pci-0000:00:06.0-
scsi-0:0:1:0", SYMLINK+="dvd", ENV{GENERATED}="1"
SUBSYSTEM=="block", ENV{ID_CDROM}=="?*", ENV{ID_PATH}=="pci-0000:00:06.0-
scsi-0:0:1:0", SYMLINK+="dvdrw", ENV{GENERATED}="1"
# CD-RW_CRX195E1 (pci-0000:00:06.0-scsi-0:0:0:0)
SUBSYSTEM=="block", ENV{ID_CDROM}=="?*", ENV{ID_PATH}=="pci-0000:00:06.0-
scsi-0:0:0:0", SYMLINK+="cdrom1", ENV{GENERATED}="1"
SUBSYSTEM=="block", ENV{ID_CDROM}=="?*", ENV{ID_PATH}=="pci-0000:00:06.0-
scsi-0:0:0:0", SYMLINK+="cdrw1", ENV{GENERATED}="1"
# Virtual_CD_070A (pci-0000:00:02.1-usb-0:8:1.0-scsi-0:0:0:1)
SUBSYSTEM=="block", ENV{ID_CDROM}=="?*", ENV{ID_SERIAL}
=="WD_Virtual_CD_070A_575837304139393534343636-0:1", SYMLINK+="cdrom2",
ENV{GENERATED}="1"
>> So I put my *CD* in my *CD drive* an launch asunder the ripper to rip
>> it, but nothing happens in asunder. The ripperx will at least tell me
>> that no media is found in drive.
>>
>> Clearer this time?
>
> Yes... well, errr, no.
>
> cat /etc/fstab
> dmesg | grep -i -e "cd-rom" -e dvd
> ls -l /dev/scd*
$ dmesg | grep -i -e "cd-rom" -e dvd
-- has been quite a while since last reboot, :-)
$ grep -i -e "cd-rom" -e dvd /var/log/dmesg
[ 1.591627] ata3.01: ATAPI: PIONEER DVD-RW DVR-110D, 1.17, max UDMA/66
[ 2.558336] scsi 2:0:0:0: CD-ROM SONY CD-RW CRX195E1
ZYS5 PQ: 0 ANSI: 5
[ 2.559599] Uniform CD-ROM driver Revision: 3.20
[ 2.559746] sr 2:0:0:0: Attached scsi CD-ROM sr0
[ 2.565682] scsi 2:0:1:0: CD-ROM PIONEER DVD-RW DVR-110D
1.17 PQ: 0 ANSI: 5
[ 2.584166] sr 2:0:1:0: Attached scsi CD-ROM sr1
$ ls -l /dev/scd* /dev/dvd /dev/cdrom /dev/cdrom1
lrwxrwxrwx 1 root root 3 2011-07-01 16:58 /dev/cdrom -> sr1
lrwxrwxrwx 1 root root 3 2011-07-01 15:21 /dev/cdrom1 -> sr0
lrwxrwxrwx 1 root root 3 2011-07-01 16:58 /dev/dvd -> sr1
lrwxrwxrwx 1 root root 3 2011-07-01 15:21 /dev/scd0 -> sr0
lrwxrwxrwx 1 root root 3 2011-07-01 16:58 /dev/scd1 -> sr1
$ grep '/media/' /etc/fstab
/dev/scd0 /media/cdrom auto users,noauto,exec,ro 0 0
/dev/dvd /media/dvd auto users,noauto,exec,ro 0 0
On Tue, 28 Jun 2011 18:55:48 +0000, Camaleón wrote:
> Yep, or use udev rules:
>
> CD/DVD drives
> http://reactivated.net/writing_udev_rules.html#example-cdrom
Where should I put those rules? I believe that /etc/udev/rules.d/70-
persistent-cd.rules is automatically generated by the 75-cd-aliases-
generator.rules. I hope that I can put those rules in a standalone file
which can overwrite settings in /etc/udev/rules.d/70-persistent-cd.rules.
BTW, that document is about 5 years old now, and my Debian doesn't have
commands like udevtrigger, udevcontrol and udevtest for udev rules
testing and debugging and more.
What are the equivalents for them?
Thanks
--
Tong (remove underscore(s) to reply)
http://xpt.sourceforge.net/techdocs/
http://xpt.sourceforge.net/tools/
Reply to: