I installed an "optical drive" in this F-18/64 XFCE computer and it is apparently recognized by several applications however I don't see an icon come up on the desktop when I put a cdrom in the drive. The same disk works as expected in a similar F-18 computer.
When I put the disk in the drive the light flickers for a while and then stops, no icon appears, and it is reluctant to eject.
[bobg@box10 ~]$ ll /dev/sg1 crw-rw----+ 1 root cdrom 21, 1 Mar 16 2013 /dev/sg1
I don't know how to troubleshoot this so any help is appreciated.
Bob
On 15/03/13 20:00, Bob Goodwin - Zuni, Virginia, USA wrote:
I installed an "optical drive" in this F-18/64 XFCE computer and it is apparently recognized by several applications however I don't see an icon come up on the desktop when I put a cdrom in the drive. The same disk works as expected in a similar F-18 computer.
When I put the disk in the drive the light flickers for a while and then stops, no icon appears, and it is reluctant to eject.
[bobg@box10 ~]$ ll /dev/sg1 crw-rw----+ 1 root cdrom 21, 1 Mar 16 2013 /dev/sg1
I don't know how to troubleshoot this so any help is appreciated.
Bob
Another indication, I get:
[root@box10 bobg]# mount -t iso9660 -o ro /dev/sg1 /mnt/cdrom mount: /dev/sg1 is not a block device
I suppose the drive could be defective but I would like to know I'm doing everything right before I pursue that path.
On 03/16/13 16:42, Bob Goodwin - Zuni, Virginia, USA wrote:
On 15/03/13 20:00, Bob Goodwin - Zuni, Virginia, USA wrote:
I installed an "optical drive" in this F-18/64 XFCE computer and it is apparently recognized by several applications however I don't see an icon come up on the desktop when I put a cdrom in the drive. The same disk works as expected in a similar F-18 computer.
When I put the disk in the drive the light flickers for a while and then stops, no icon appears, and it is reluctant to eject.
[bobg@box10 ~]$ ll /dev/sg1 crw-rw----+ 1 root cdrom 21, 1 Mar 16 2013 /dev/sg1
I don't know how to troubleshoot this so any help is appreciated.
Bob
Another indication, I get:
[root@box10 bobg]# mount -t iso9660 -o ro /dev/sg1 /mnt/cdrom mount: /dev/sg1 is not a block device
I suppose the drive could be defective but I would like to know I'm doing everything right before I pursue that path.
What does "ls -l /dev | grep cdrom" show? On all of my the cdrom is /dev/sr0 which is a block device.
On 16/03/13 05:02, Ed Greshko wrote:
Another indication, I get:
[root@box10 bobg]# mount -t iso9660 -o ro /dev/sg1 /mnt/cdrom mount: /dev/sg1 is not a block device
I suppose the drive could be defective but I would like to know I'm doing everything right before I pursue that path.
What does "ls -l /dev | grep cdrom" show? On all of my the cdrom is /dev/sr0 which is a block device.
-- From now on, at least during winter time, Im going to blame all spelling an grammar erros on the cat sitting on my chest every time I sit down at the computer.... --
[root@box10 bobg]# ls -l /dev | grep cdrom crw-rw----+ 1 root cdrom 21, 1 Mar 16 2013 sg1 brw-rw----. 1 root cdrom 11, 0 Mar 16 2013 sr0
[root@box10 bobg]# mount -t iso9660 -o ro /dev/sg0 /mnt/cdrom mount: /dev/sg0 is not a block device
"Bob Goodwin - Zuni, Virginia, USA" bobgoodwin@wildblue.net wrote:
On 16/03/13 05:02, Ed Greshko wrote:
Another indication, I get:
[root@box10 bobg]# mount -t iso9660 -o ro /dev/sg1 /mnt/cdrom mount: /dev/sg1 is not a block device
I suppose the drive could be defective but I would like to know I'm
doing everything right before I pursue that path.
What does "ls -l /dev | grep cdrom" show? On all of my the cdrom is
/dev/sr0 which is a block device.
-- From now on, at least during winter time, Im going to blame all spelling an grammar erros on the cat sitting on my chest every time I
sit down at the computer....
[root@box10 bobg]# ls -l /dev | grep cdrom crw-rw----+ 1 root cdrom 21, 1 Mar 16 2013 sg1 brw-rw----. 1 root cdrom 11, 0 Mar 16 2013 sr0
[root@box10 bobg]# mount -t iso9660 -o ro /dev/sg0 /mnt/cdrom mount: /dev/sg0 is not a block device
Read the line again...... sr0 not sg0
On 03/16/13 20:21, Ed Greshko wrote:
"Bob Goodwin - Zuni, Virginia, USA" bobgoodwin@wildblue.net wrote:
[root@box10 bobg]# ls -l /dev | grep cdrom crw-rw----+ 1 root cdrom 21, 1 Mar 16 2013 sg1 brw-rw----. 1 root cdrom 11, 0 Mar 16 2013 sr0
[root@box10 bobg]# mount -t iso9660 -o ro /dev/sg0 /mnt/cdrom mount: /dev/sg0 is not a block device
Read the line again...... sr0 not sg0
Also, I notice you don't have the symlink....
lrwxrwxrwx. 1 root root 3 Mar 17 2013 cdrom -> sr0
Do you have a /usr/lib/udev/rules.d/60-cdrom_id.rules file?
On 16/03/13 08:32, Ed Greshko wrote:
On 03/16/13 20:21, Ed Greshko wrote:
"Bob Goodwin - Zuni, Virginia, USA" bobgoodwin@wildblue.net wrote:
[root@box10 bobg]# ls -l /dev | grep cdrom crw-rw----+ 1 root cdrom 21, 1 Mar 16 2013 sg1 brw-rw----. 1 root cdrom 11, 0 Mar 16 2013 sr0
[root@box10 bobg]# mount -t iso9660 -o ro /dev/sg0 /mnt/cdrom mount: /dev/sg0 is not a block device
Read the line again...... sr0 not sg0
Also, I notice you don't have the symlink....
lrwxrwxrwx. 1 root root 3 Mar 17 2013 cdrom -> sr0
I only find [if I'm looking in the right place]:
/dev/char: lrwxrwxrwx. 1 root root 6 Mar 16 2013 21:0 -> ../sg0 lrwxrwxrwx. 1 root root 6 Mar 16 2013 21:1 -> ../sg1
Do I need to create it under /dev/char ?
Do you have a /usr/lib/udev/rules.d/60-cdrom_id.rules file?
[root@box10 bobg]# ll /usr/lib/udev/rules.d/60-cdrom_id.rules -rw-r--r--. 1 root root 646 Jan 28 14:05 /usr/lib/udev/rules.d/60-cdrom_id.rules
On 03/16/13 21:35, Bob Goodwin - Zuni, Virginia, USA wrote:
On 16/03/13 08:32, Ed Greshko wrote:
On 03/16/13 20:21, Ed Greshko wrote:
"Bob Goodwin - Zuni, Virginia, USA" bobgoodwin@wildblue.net wrote:
[root@box10 bobg]# ls -l /dev | grep cdrom crw-rw----+ 1 root cdrom 21, 1 Mar 16 2013 sg1 brw-rw----. 1 root cdrom 11, 0 Mar 16 2013 sr0
[root@box10 bobg]# mount -t iso9660 -o ro /dev/sg0 /mnt/cdrom mount: /dev/sg0 is not a block device
Read the line again...... sr0 not sg0
Also, I notice you don't have the symlink....
lrwxrwxrwx. 1 root root 3 Mar 17 2013 cdrom -> sr0
I only find [if I'm looking in the right place]:
/dev/char: lrwxrwxrwx. 1 root root 6 Mar 16 2013 21:0 -> ../sg0 lrwxrwxrwx. 1 root root 6 Mar 16 2013 21:1 -> ../sg1
Do I need to create it under /dev/char ?
Forget all about sg0 and sg1.
You don't have
[egreshko@meimei ~]$ ll /dev/cdrom lrwxrwxrwx. 1 root root 3 Mar 12 07:27 /dev/cdrom -> sr0
Do you have a /usr/lib/udev/rules.d/60-cdrom_id.rules file?
[root@box10 bobg]# ll /usr/lib/udev/rules.d/60-cdrom_id.rules -rw-r--r--. 1 root root 646 Jan 28 14:05 /usr/lib/udev/rules.d/60-cdrom_id.rules
You do have that.... Check that file and make sure it contains the line
KERNEL=="sr0", SYMLINK+="cdrom", OPTIONS+="link_priority=-100"
Also, run "systemctl status systemd-udevd.service" to ensure it is running.
On 16/03/13 09:44, Ed Greshko wrote:
Do I need to create it under /dev/char ? You don't have
[egreshko@meimei ~]$ ll /dev/cdrom lrwxrwxrwx. 1 root root 3 Mar 12 07:27 /dev/cdrom -> sr0
Ok now I made that:
[root@box10 bobg]# ll /dev/cdrom lrwxrwxrwx. 1 root root 3 Mar 16 10:00 /dev/cdrom -> sr0
Do you have a /usr/lib/udev/rules.d/60-cdrom_id.rules file?
[root@box10 bobg]# ll /usr/lib/udev/rules.d/60-cdrom_id.rules -rw-r--r--. 1 root root 646 Jan 28 14:05 /usr/lib/udev/rules.d/60-cdrom_id.rules
You do have that.... Check that file and make sure it contains the line
KERNEL=="sr0", SYMLINK+="cdrom", OPTIONS+="link_priority=-100"
[root@box10 bobg]# cat /usr/lib/udev/rules.d/60-cdrom_id.rules # do not edit this file, it will be overwritten on update
ACTION=="remove", GOTO="cdrom_end" SUBSYSTEM!="block", GOTO="cdrom_end" KERNEL!="sr[0-9]*|xvd*", GOTO="cdrom_end" ENV{DEVTYPE}!="disk", GOTO="cdrom_end"
# unconditionally tag device as CDROM KERNEL=="sr[0-9]*", ENV{ID_CDROM}="1"
# media eject button pressed ENV{DISK_EJECT_REQUEST}=="?*", RUN+="cdrom_id --eject-media $devnode", GOTO="cdrom_end"
# import device and media properties and lock tray to # enable the receiving of media eject button events IMPORT{program}="cdrom_id --lock-media $devnode"
KERNEL=="sr0", SYMLINK+="cdrom", OPTIONS+="link_priority=-100"
LABEL="cdrom_end"
Also, run "systemctl status systemd-udevd.service" to ensure it is running.
[root@box10 bobg]# systemctl status systemd-udevd.service systemd-udevd.service - udev Kernel Device Manager Loaded: loaded (/usr/lib/systemd/system/systemd-udevd.service; static) Active: active (running) since Sat 2013-03-16 23:32:15 EDT Docs: man:systemd-udevd.service(8) man:udev(7) Main PID: 400 (systemd-udevd) CGroup: name=systemd:/system/systemd-udevd.service └─400 /usr/lib/systemd/systemd-udevd
Mar 16 23:32:18 box10 systemd-udevd[543]: failed to execute '/usr/lib/udev/pci-db' 'pci-db /devices/pci0000:00/0000:00:11.0': No such file or directory Mar 16 23:32:18 box10 mtp-probe[550]: checking bus 3, device 2: "/sys/devices/pci0000:00/0000:00:12.0/usb3/3-5" Mar 16 23:32:18 box10 mtp-probe[551]: checking bus 4, device 2: "/sys/devices/pci0000:00/0000:00:13.0/usb4/4-1" Mar 16 04:32:49 box10 systemd-udevd[447]: timeout 'ata_id --export /dev/sr0' Mar 16 04:32:49 box10 systemd-udevd[400]: worker [447] /devices/pci0000:00/0000:00:11.0/ata2/host1/target1:0:0/1:0:0:0/block/sr0 timeout; kill it Mar 16 04:32:49 box10 systemd-udevd[400]: seq 1736 '/devices/pci0000:00/0000:00:11.0/ata2/host1/target1:0:0/1:0:0:0/block/sr0' killed Mar 16 04:32:49 box10 systemd-udevd[400]: worker [447] terminated by signal 9 (Killed) Mar 16 04:37:03 box10 systemd-udevd[400]: worker [2008] /devices/pci0000:00/0000:00:11.0/ata2/host1/target1:0:0/1:0:0:0/block/sr0 timeout; kill it Mar 16 04:37:03 box10 systemd-udevd[400]: seq 2172 '/devices/pci0000:00/0000:00:11.0/ata2/host1/target1:0:0/1:0:0:0/block/sr0' killed Mar 16 04:37:03 box10 systemd-udevd[400]: worker [2008] terminated by signal 9 (Killed)
Next to get it to "eject" the disk ...
On 16/03/13 10:05, Bob Goodwin - Zuni, Virginia, USA wrote:
Next to get it to "eject" the disk ...
Eject -F did that, after that "eject" alone seems enough ...
I suspect it's time to reboot and see what results I get when a disk is inserted?
On 03/16/13 22:17, Bob Goodwin - Zuni, Virginia, USA wrote:
On 16/03/13 10:05, Bob Goodwin - Zuni, Virginia, USA wrote:
Next to get it to "eject" the disk ...
Eject -F did that, after that "eject" alone seems enough ...
I suspect it's time to reboot and see what results I get when a disk is inserted?
First of all, when you reboot the symbolic link may be gone. The entries under /dev are created at boot time. The error message you showed may be symptomatic of why the link isn't being created.
On 16/03/13 08:21, Ed Greshko wrote:
"Bob Goodwin - Zuni, Virginia, USA" bobgoodwin@wildblue.net wrote:
[root@box10 bobg]# ls -l /dev | grep cdrom crw-rw----+ 1 root cdrom 21, 1 Mar 16 2013 sg1 brw-rw----. 1 root cdrom 11, 0 Mar 16 2013 sr0
[root@box10 bobg]# mount -t iso9660 -o ro /dev/sg0 /mnt/cdrom mount: /dev/sg0 is not a block device
Read the line again...... sr0 not sg0
Sorry, I just got out of bed when I wrote that response.
mount -t iso9660 -o ro /dev/sr0 /mnt/cdrom
That is better and I can live with mounting it manually, although on the other computer it brings up an icon on the XFCE desktop when I put the same disk in it?
I rarely need the optical drive so manually mounting is fine. I had the "DVD writer" on hand with a mfr date in 2011 and thought I'd install it in this computer.
Thanks for the help,
Bob
On 15/03/13 20:00, Bob Goodwin - Zuni, Virginia, USA wrote:
I installed an "optical drive" in this F-18/64 XFCE computer and it is apparently recognized by several applications however I don't see an icon come up on the desktop when I put a cdrom in the drive. The same disk works as expected in a similar F-18 computer.
When I put the disk in the drive the light flickers for a while and then stops, no icon appears, and it is reluctant to eject.
[bobg@box10 ~]$ ll /dev/sg1 crw-rw----+ 1 root cdrom 21, 1 Mar 16 2013 /dev/sg1
I don't know how to troubleshoot this so any help is appreciated.
Bob
At least part of the problem is "/dev/cdrom -> sr0" is not being created. I still don't understand all of this but I see the following on this computer:
[root@box10 bobg]# udevadm info --query=all --name=/dev/sr0 P: /devices/pci0000:00/0000:00:11.0/ata2/host1/target1:0:0/1:0:0:0/block/sr0 N: sr0 E: DEVNAME=/dev/sr0 E: DEVPATH=/devices/pci0000:00/0000:00:11.0/ata2/host1/target1:0:0/1:0:0:0/block/sr0 E: DEVTYPE=disk E: MAJOR=11 E: MINOR=0 E: SUBSYSTEM=block
While on another computer set up identically but in which the optical drive was present when Fedora-18 was installed:
[bobg@Box7 ~]$ udevadm info --query=all --name=/dev/sr0 P: /devices/pci0000:00/0000:00:1f.2/ata3/host2/target2:0:0/2:0:0:0/block/sr0 N: sr0 L: -100 S: cdrom S: disk/by-id/ata-PLDS_DVD+_-RW_DH-16A6S E: DEVLINKS=/dev/cdrom /dev/disk/by-id/ata-PLDS_DVD+_-RW_DH-16A6S E: DEVNAME=/dev/sr0 E: DEVPATH=/devices/pci0000:00/0000:00:1f.2/ata3/host2/target2:0:0/2:0:0:0/block/sr0 E: DEVTYPE=disk E: ID_ATA=1 E: ID_ATA_SATA=1 E: ID_ATA_SATA_SIGNAL_RATE_GEN1=1 E: ID_BUS=ata E: ID_CDROM=1 E: ID_CDROM_CD=1 E: ID_CDROM_CD_R=1 E: ID_CDROM_CD_RW=1 E: ID_CDROM_DVD=1 E: ID_CDROM_DVD_PLUS_R=1 E: ID_CDROM_DVD_PLUS_RW=1 E: ID_CDROM_DVD_PLUS_R_DL=1 E: ID_CDROM_DVD_R=1 E: ID_CDROM_DVD_RAM=1 E: ID_CDROM_DVD_RW=1 E: ID_CDROM_MRW=1 E: ID_CDROM_MRW_W=1 E: ID_MODEL=PLDS_DVD+_-RW_DH-16A6S E: ID_MODEL_ENC=PLDS\x20DVD+\x2f-RW\x20DH-16A6S\x20\x20\x20\x20\x20\x20\x20\x20\x20\x20\x20\x20\x20\x20\x20\x20\x20\x20 E: ID_REVISION=YD11 E: ID_SERIAL=PLDS_DVD+_-RW_DH-16A6S E: ID_TYPE=cd E: MAJOR=11 E: MINOR=0 E: MPATH_SBIN_PATH=/sbin E: SUBSYSTEM=block E: TAGS=:seat:systemd:uaccess: E: UDISKS_PRESENTATION_NOPOLICY=0 E: USEC_INITIALIZED=662366
It seems obvious that this is related to my problem. There must be a right way to add an DVD/CD drive after the initial operating system installation?
Certainly I should not have to re-install Fedora 18 to get the optical drive to work?
Bob
On 03/19/13 00:46, Bob Goodwin - Zuni, Virginia, USA wrote:
On 15/03/13 20:00, Bob Goodwin - Zuni, Virginia, USA wrote:
I installed an "optical drive" in this F-18/64 XFCE computer and it is apparently recognized by several applications however I don't see an icon come up on the desktop when I put a cdrom in the drive. The same disk works as expected in a similar F-18 computer.
When I put the disk in the drive the light flickers for a while and then stops, no icon appears, and it is reluctant to eject.
[bobg@box10 ~]$ ll /dev/sg1 crw-rw----+ 1 root cdrom 21, 1 Mar 16 2013 /dev/sg1
I don't know how to troubleshoot this so any help is appreciated.
Bob
At least part of the problem is "/dev/cdrom -> sr0" is not being created. I still don't understand all of this but I see the following on this computer:
[root@box10 bobg]# udevadm info --query=all --name=/dev/sr0 P: /devices/pci0000:00/0000:00:11.0/ata2/host1/target1:0:0/1:0:0:0/block/sr0 N: sr0 E: DEVNAME=/dev/sr0 E: DEVPATH=/devices/pci0000:00/0000:00:11.0/ata2/host1/target1:0:0/1:0:0:0/block/sr0 E: DEVTYPE=disk E: MAJOR=11 E: MINOR=0 E: SUBSYSTEM=block
While on another computer set up identically but in which the optical drive was present when Fedora-18 was installed:
[bobg@Box7 ~]$ udevadm info --query=all --name=/dev/sr0 P: /devices/pci0000:00/0000:00:1f.2/ata3/host2/target2:0:0/2:0:0:0/block/sr0 N: sr0 L: -100 S: cdrom S: disk/by-id/ata-PLDS_DVD+_-RW_DH-16A6S E: DEVLINKS=/dev/cdrom /dev/disk/by-id/ata-PLDS_DVD+_-RW_DH-16A6S E: DEVNAME=/dev/sr0 E: DEVPATH=/devices/pci0000:00/0000:00:1f.2/ata3/host2/target2:0:0/2:0:0:0/block/sr0 E: DEVTYPE=disk E: ID_ATA=1 E: ID_ATA_SATA=1 E: ID_ATA_SATA_SIGNAL_RATE_GEN1=1 E: ID_BUS=ata E: ID_CDROM=1 E: ID_CDROM_CD=1 E: ID_CDROM_CD_R=1 E: ID_CDROM_CD_RW=1 E: ID_CDROM_DVD=1 E: ID_CDROM_DVD_PLUS_R=1 E: ID_CDROM_DVD_PLUS_RW=1 E: ID_CDROM_DVD_PLUS_R_DL=1 E: ID_CDROM_DVD_R=1 E: ID_CDROM_DVD_RAM=1 E: ID_CDROM_DVD_RW=1 E: ID_CDROM_MRW=1 E: ID_CDROM_MRW_W=1 E: ID_MODEL=PLDS_DVD+_-RW_DH-16A6S E: ID_MODEL_ENC=PLDS\x20DVD+\x2f-RW\x20DH-16A6S\x20\x20\x20\x20\x20\x20\x20\x20\x20\x20\x20\x20\x20\x20\x20\x20\x20\x20 E: ID_REVISION=YD11 E: ID_SERIAL=PLDS_DVD+_-RW_DH-16A6S E: ID_TYPE=cd E: MAJOR=11 E: MINOR=0 E: MPATH_SBIN_PATH=/sbin E: SUBSYSTEM=block E: TAGS=:seat:systemd:uaccess: E: UDISKS_PRESENTATION_NOPOLICY=0 E: USEC_INITIALIZED=662366
It seems obvious that this is related to my problem. There must be a right way to add an DVD/CD drive after the initial operating system installation?
Certainly I should not have to re-install Fedora 18 to get the optical drive to work?
Bob
Remember you posted....
Mar 16 23:32:18 box10 systemd-udevd[543]: failed to execute '/usr/lib/udev/pci-db' 'pci-db /devices/pci0000:00/0000:00:11.0': No such file or directory Mar 16 23:32:18 box10 mtp-probe[550]: checking bus 3, device 2: "/sys/devices/pci0000:00/0000:00:12.0/usb3/3-5" Mar 16 23:32:18 box10 mtp-probe[551]: checking bus 4, device 2: "/sys/devices/pci0000:00/0000:00:13.0/usb4/4-1" Mar 16 04:32:49 box10 systemd-udevd[447]: timeout 'ata_id --export /dev/sr0' Mar 16 04:32:49 box10 systemd-udevd[400]: worker [447] /devices/pci0000:00/0000:00:11.0/ata2/host1/target1:0:0/1:0:0:0/block/sr0 timeout; kill it Mar 16 04:32:49 box10 systemd-udevd[400]: seq 1736 '/devices/pci0000:00/0000:00:11.0/ata2/host1/target1:0:0/1:0:0:0/block/sr0' killed Mar 16 04:32:49 box10 systemd-udevd[400]: worker [447] terminated by signal 9 (Killed) Mar 16 04:37:03 box10 systemd-udevd[400]: worker [2008] /devices/pci0000:00/0000:00:11.0/ata2/host1/target1:0:0/1:0:0:0/block/sr0 timeout; kill it Mar 16 04:37:03 box10 systemd-udevd[400]: seq 2172 '/devices/pci0000:00/0000:00:11.0/ata2/host1/target1:0:0/1:0:0:0/block/sr0' killed Mar 16 04:37:03 box10 systemd-udevd[400]: worker [2008] terminated by signal 9 (Killed)
Did you check the logs on the "working" system to see if it has similar errors? If not, it would seem you have HW problems.
What kind of drive is it? Can you swap cables, etc from the working system to the failing system?
On 18/03/13 14:14, Ed Greshko wrote:
On 03/19/13 00:46, Bob Goodwin - Zuni, Virginia, USA wrote:
Certainly I should not have to re-install Fedora 18 to get the optical drive to work?
Bob
Remember you posted....
Mar 16 23:32:18 box10 systemd-udevd[543]: failed to execute '/usr/lib/udev/pci-db' 'pci-db /devices/pci0000:00/0000:00:11.0': No such file or directory Mar 16 23:32:18 box10 mtp-probe[550]: checking bus 3, device 2: "/sys/devices/pci0000:00/0000:00:12.0/usb3/3-5" Mar 16 23:32:18 box10 mtp-probe[551]: checking bus 4, device 2: "/sys/devices/pci0000:00/0000:00:13.0/usb4/4-1" Mar 16 04:32:49 box10 systemd-udevd[447]: timeout 'ata_id --export /dev/sr0' Mar 16 04:32:49 box10 systemd-udevd[400]: worker [447] /devices/pci0000:00/0000:00:11.0/ata2/host1/target1:0:0/1:0:0:0/block/sr0 timeout; kill it Mar 16 04:32:49 box10 systemd-udevd[400]: seq 1736 '/devices/pci0000:00/0000:00:11.0/ata2/host1/target1:0:0/1:0:0:0/block/sr0' killed Mar 16 04:32:49 box10 systemd-udevd[400]: worker [447] terminated by signal 9 (Killed) Mar 16 04:37:03 box10 systemd-udevd[400]: worker [2008] /devices/pci0000:00/0000:00:11.0/ata2/host1/target1:0:0/1:0:0:0/block/sr0 timeout; kill it Mar 16 04:37:03 box10 systemd-udevd[400]: seq 2172 '/devices/pci0000:00/0000:00:11.0/ata2/host1/target1:0:0/1:0:0:0/block/sr0' killed Mar 16 04:37:03 box10 systemd-udevd[400]: worker [2008] terminated by signal 9 (Killed)
Did you check the logs on the "working" system to see if it has similar errors? If not, it would seem you have HW problems.
What kind of drive is it? Can you swap cables, etc from the working system to the failing system?
I did not understand the implication that it was defective hardware. Actually just began considering the problem again this afternoon. The board and drive are:
[root@box10 bobg]# lshw -X box10 description: Desktop Computer product: A75MG (None) vendor: BIOSTAR Group serial: None width: 64 bits capabilities: smbios-2.7 dmi-2.7 vsyscall32 configuration: boot=normal chassis=desktop family=None sku=None uuid=00020003-0004-0005-0006-000700080009 *-core description: Motherboard product: A75MG vendor: BIOSTAR Group physical id: 0 serial: None slot: None *-firmware description: BIOS vendor: American Megatrends Inc. physical id: 0 version: 4.6.4 date: 04/11/2012 size: 64KiB capacity: 960KiB capabilities: pci upgrade shadowing cdboot bootselect socketedrom edd int13floppy1200 int13floppy720 int13floppy2880 int5printscreen int9keyboard int14serial int17printer acpi usb biosbootspecification uefi ...................... snip ................
*-scsi:1 physical id: 2 logical name: scsi1 capabilities: emulated *-cdrom description: DVD-RAM writer product: CDDVDW SH-S223C vendor: TSSTcorp physical id: 0.0.0 bus info: scsi@1:0.0.0 logical name: /dev/cdrom logical name: /dev/sr0 version: SB06 capabilities: removable audio cd-r cd-rw dvd dvd-r dvd-ram configuration: ansiversion=5 status=nodisc
I know I had that drive in another computer, presumably it worked with Fedora, although I am not certain. It just "looked" clean and had a recent date stamp. I will try a different drive and cable.
On 18/03/13 14:14, Ed Greshko wrote:
Did you check the logs on the "working" system to see if it has similar errors? If not, it would seem you have HW problems.
From the working system:
[bobg@Box7 ~]$ systemctl status systemd-udevd.service systemd-udevd.service - udev Kernel Device Manager Loaded: loaded (/usr/lib/systemd/system/systemd-udevd.service; static) Active: active (running) since Mon 2013-03-18 10:58:27 EDT; 4h 5min ago Docs: man:systemd-udevd.service(8) man:udev(7) Main PID: 385 (systemd-udevd) CGroup: name=systemd:/system/systemd-udevd.service └─385 /usr/lib/systemd/systemd-udevd
Mar 18 10:58:27 Box7 systemd[1]: Started udev Kernel Device Manager. Mar 18 10:58:31 Box7 mtp-probe[477]: checking bus 7, device 3: "/sys/devices/pci0000:00/0000:00:1d.2/usb7/7-2" Mar 18 10:58:31 Box7 mtp-probe[477]: bus: 7, device: 3 was not an MTP device Mar 18 10:58:31 Box7 mtp-probe[478]: checking bus 7, device 2: "/sys/devices/pci0000:00/0000:00:1d.2/usb7/7-1" Mar 18 10:58:31 Box7 mtp-probe[478]: bus: 7, device: 2 was not an MTP device Mar 18 10:58:31 Box7 systemd-udevd[480]: failed to execute '/usr/lib/udev/pci-db' 'pci-db /devices/pci0000:00/0000:00:1f.2': No such file or directory Warning: Journal has been rotated since unit was started. Log output is incomplete or unavailable.
And from the non- working:
[root@box10 bobg]# systemctl status systemd-udevd.service systemd-udevd.service - udev Kernel Device Manager Loaded: loaded (/usr/lib/systemd/system/systemd-udevd.service; static) Active: active (running) since Mon 2013-03-18 22:48:36 EDT Docs: man:systemd-udevd.service(8) man:udev(7) Main PID: 398 (systemd-udevd) CGroup: name=systemd:/system/systemd-udevd.service └─398 /usr/lib/systemd/systemd-udevd
Mar 18 22:48:36 box10 systemd[1]: Started udev Kernel Device Manager. Mar 18 22:48:38 box10 systemd-udevd[398]: specified group 'input' unknown Mar 18 22:48:40 box10 systemd-udevd[549]: failed to execute '/usr/lib/udev/pci-db' 'pci-db /devices/pci0000:00/0000:00:14.1': No such file or directory Mar 18 22:48:40 box10 mtp-probe[556]: checking bus 3, device 2: "/sys/devices/pci0000:00/0000:00:12.0/usb3/3-5" Mar 18 22:48:40 box10 mtp-probe[558]: checking bus 4, device 2: "/sys/devices/pci0000:00/0000:00:13.0/usb4/4-1" Mar 18 03:49:10 box10 systemd-udevd[398]: worker [438] /devices/pci0000:00/0000:00:11.0/ata2/host1/target1:0:0/1:0:0:0/block/sr0 timeout; kill it Mar 18 03:49:10 box10 systemd-udevd[398]: seq 1742 '/devices/pci0000:00/0000:00:11.0/ata2/host1/target1:0:0/1:0:0:0/block/sr0' killed Mar 18 03:49:10 box10 systemd-udevd[398]: worker [438] terminated by signal 9 (Killed) Warning: Journal has been rotated since unit was started. Log output is incomplete or unavailable.
I don't know which lines apply to the optical drive?
Anyway I will have to pull a drive from another computer and try it in this one, there's some inertia to overcome there but I will do it.
Bob
On 03/19/13 03:17, Bob Goodwin - Zuni, Virginia, USA wrote:
Mar 18 03:49:10 box10 systemd-udevd[398]: worker [438] /devices/pci0000:00/0000:00:11.0/ata2/host1/target1:0:0/1:0:0:0/block/sr0 timeout; kill it Mar 18 03:49:10 box10 systemd-udevd[398]: seq 1742 '/devices/pci0000:00/0000:00:11.0/ata2/host1/target1:0:0/1:0:0:0/block/sr0' killed Mar 18 03:49:10 box10 systemd-udevd[398]: worker [438] terminated by signal 9 (Killed) Warning: Journal has been rotated since unit was started. Log output is incomplete or unavailable.
I don't know which lines apply to the optical drive?
Notice the reference to "sr0"?
On 18/03/13 17:02, Ed Greshko wrote:
On 03/19/13 03:17, Bob Goodwin - Zuni, Virginia, USA wrote:
Mar 18 03:49:10 box10 systemd-udevd[398]: worker [438] /devices/pci0000:00/0000:00:11.0/ata2/host1/target1:0:0/1:0:0:0/block/sr0 timeout; kill it Mar 18 03:49:10 box10 systemd-udevd[398]: seq 1742 '/devices/pci0000:00/0000:00:11.0/ata2/host1/target1:0:0/1:0:0:0/block/sr0' killed Mar 18 03:49:10 box10 systemd-udevd[398]: worker [438] terminated by signal 9 (Killed) Warning: Journal has been rotated since unit was started. Log output is incomplete or unavailable.
I don't know which lines apply to the optical drive?
Notice the reference to "sr0"?
Yes I see that now that you point it out. My eyesight is a problem and I frequently miss stuff.
On 18/03/13 14:14, Ed Greshko wrote:
What kind of drive is it? Can you swap cables, etc from the working system to the failing system?
I pulled a DVD Reader from another box and substituted it for the DVD Writer I had installed. The reader works as expected, an icon pops up on the desktop when a disk is inserted.
So as you suggested it is a defective unit. I suppose I should have suspected that first but I thought all I had were in working condition. I will order a replacement, they are inexpensive from what I see advertised.
Thanks for the help.
Bob
-
Bob Goodwin -
Ed Greshko