LinuxQuestions.org

LinuxQuestions.org (/questions/)
-   Slackware (http://www.linuxquestions.org/questions/slackware-14/)
-   -   Trouble with DVD drive (http://www.linuxquestions.org/questions/slackware-14/trouble-with-dvd-drive-4175461255/)

dr.trev 05-09-2013 04:10 AM

Trouble with DVD drive
 
I'm not sure if this is a hardware or software issue. It started off as just an eject problem ala other other recent threads, although even the eject button on the drive often didn't work either. But now it sometimes doesn't even recognize when it contains media.

I am running -current. At various times during boot, there is a long pause which is usually related to udev or the dvd drive; excerpts below:

Code:

[    2.655363] ata3: SATA link up 1.5 Gbps (SStatus 113 SControl 300)
[    2.656861] ata3.00: ATAPI: TSSTcorp CDDVDW SH-S223C, SB04, max UDMA/100
...
[    3.456131] ata3.00: configured for UDMA/100
[    5.207018] scsi 2:0:0:0: CD-ROM            TSSTcorp CDDVDW SH-S223C  SB04 PQ: 0 ANSI: 5
[    5.211129] cdrom: Uniform CD-ROM driver Revision: 3.20
...
[    5.375385] udevd[967]: starting version 182  # why the 10 second pause!!
[  15.378163] Initializing USB Mass Storage driver...
...
[  26.642258] EXT4-fs (sda1): mounted filesystem with ordered data mode. Opts: (null)
[  35.963059] ata3: hard resetting link  # does a long pause before a hard reset mean something bad??
[  36.421735] ata3: SATA link up 1.5 Gbps (SStatus 113 SControl 300)
[  37.222115] ata3.00: configured for UDMA/100
[  38.020975] ata3: EH complete
...
[  38.902285] udevd[1187]: starting version 182  # how come udevd starts twice??
...
[  43.884205] sd 9:0:0:0: [sdc] Attached SCSI disk
[  70.910198] ata3: hard resetting link  # another longer pause before hard reset again???
[  71.373335] ata3: SATA link up 1.5 Gbps (SStatus 113 SControl 300)
[  72.178326] ata3.00: configured for UDMA/100
[  72.977138] ata3: EH complete
...
[  75.977373] EXT3-fs (sdc1): mounted filesystem with ordered data mode
[  107.789411] ata3: hard resetting link      # and again.......
[  108.248278] ata3: SATA link up 1.5 Gbps (SStatus 113 SControl 300)
[  109.048885] ata3.00: configured for UDMA/100
[  109.847756] ata3: EH complete

The hard resetting link happens a few more times after that too. After putting a DVD in, the drive spun up but there is no sign of anything happening; udisks shows "has media: 0". And nothing I do will open the drive again, root or not (eject; udiskctl --eject; or the physical eject button).

Although it does seem a bit random, I just tried "eject" again and this time it ejected, I put a DVD in, closed the tray and the media was recognized. /var/log/messages had the "hard resetting link" messages again when the drive was closed again...

Anyone got any suggestions, or do I need to buy a new drive?

Regards,
Trevor.

wildwizard 05-09-2013 05:48 AM

Check the connections first.

And yes this is a purely hardware problem, the delay is annoying but the kernel is blocked when an I/O fault occurs to avoid anything bad happening.

brobr 05-09-2013 06:18 AM

Sounds familiar to me; happened on my previous laptop as well. Still, the weird thing was that (often) after a fresh boot I could use the drive for writing but only once. It could be hardware, probably is, as on my new laptop I have not experienced this, but that it sometimes was fine makes it a bit more ambiguous (loose connections as suggested above?). Did you try after a fresh reboot; can you boot up with an install-DVD/CD??

Good luck,

rob

H_TeXMeX_H 05-09-2013 06:34 AM

Try a live CD and see if it works, check the cables too. If it's not that then it might be failing.

cynwulf 05-09-2013 08:22 AM

I remember reading something about the 10 second pause you're referring to at "Initializing USB Mass Storage driver" - I believe it may be by design to give USB devices a chance to settle down (?).

The hard resets could be due to cabling (signal or power).

Also if you have connected e.g. a sata 3.0 device to a sata 1.5 controller, you can sometimes get this sort of problem during device detection as well. You could also enable SMART and run some tests on it to be sure. You say the hard resets happen afterwards also - is this during normal usage of the running system?

The optical drive issue may be related or may be a separate issue. You could try to remove the optical drive from the sata controller and see if the hard resets on the other devices persist?

The problems you're having with the optical drive sounds quite normal to me though - i.e. the eject button is locked and the media not being detected. I had a lot of problems in KDE with this sort of thing, including the tray opening and immediately closing again.

T3slider 05-09-2013 11:43 AM

I don't know if you're using a desktop or laptop, but I had similar messages (and pseudo-random drive behaviour) when using an SATA optical drive with a molex-to-SATA power adapter. I had a spare SATA power connector on the power supply (and thus I have no idea why I was using a molex connector in the first place) but switching it to real SATA power fixed everything. So along with the others, I would say check connections (and connection types) first.

dr.trev 05-09-2013 08:27 PM

Thanks for all the suggestions. I will open up the box when I get home tonight and check connections (it is a desktop).

caravel:
How do I check whether the drive and controller are sata 3 or 1.5?
How do I enable SMART and are there tools on slackware to do testing?

dr.trev 05-10-2013 04:38 AM

The drive uses the SATA power connection and all seems to be okay with that. In answer to caravel, the hard resets are only occurring on the optical drive. All other (hdd) drives are fine.

I don't think its the drive as I threw in a slackware 12.1 install disc and had no problems at all. The "hard resetting link" messages did not appear upon booting from that disc.

I check /var/log/syslog after rebooting and found some more relevant messages (I switched it from ata3 to ata2). The groups of failed messages nearer the end come just before the hard reset messages.

Code:

kernel: [    2.132846] Compaq SMART2 Driver (v 2.6.0)
kernel: [    2.135725] scsi: <fdomain> Detection failed (no card)
kernel: [    2.135935] qla2xxx [0000:00:00.0]-0005: : QLogic Fibre Channel HBA Driver: 8.04.00.08-k.
kernel: [    2.136093] Emulex LightPulse Fibre Channel SCSI driver 8.3.36
kernel: [    2.136136] Copyright(c) 2004-2009 Emulex.  All rights reserved.
kernel: [    2.158384] Failed initialization of WD-7000 SCSI card!
kernel: [    2.206497] GDT-HA: Storage RAID Controller Driver. Version: 3.05
kernel: [    2.206660] 3ware Storage Controller device driver for Linux v1.26.02.003.
kernel: [    2.206762] 3ware 9000 Storage Controller device driver for Linux v2.26.02.014.
kernel: [    5.150711] sr0: scsi3-mmc drive: 52x/52x writer dvd-ram cd/rw xa/form2 cdda tray
kernel: [    5.315227] EXT3-fs (sda1): error: couldn't mount because of unsupported optional features (240)
kernel: [    5.315502] EXT2-fs (sda1): error: couldn't mount because of unsupported optional features (240)
kernel: [    7.228979] microcode: failed to load file amd-ucode/microcode_amd.bin
kernel: [    7.380010] Warning! ehci_hcd should always be loaded before uhci_hcd and ohci_hcd, not after
kernel: [    7.671470] ACPI Warning: 0x00000b00-0x00000b07 SystemIO conflicts with Region \_SB_.PCI0.SBRG.ASOC.SMRG 1 (20121018/utaddress-251)
kernel: [  37.945930] ata2.00: exception Emask 0x0 SAct 0x0 SErr 0x0 action 0x6 frozen
kernel: [  37.950175] ata2.00: failed command: IDENTIFY PACKET DEVICE
kernel: [  37.954392] ata2.00: cmd a1/00:01:00:00:00/00:00:00:00:00/00 tag 0 pio 512 in
kernel: [  37.954392]          res 40/00:03:00:00:00/00:00:00:00:00/a0 Emask 0x4 (timeout)
kernel: [  37.962839] ata2.00: status: { DRDY }
kernel: [  45.858313] kvm: disabled by bios
kernel: [  75.870297] ata2.00: exception Emask 0x0 SAct 0x0 SErr 0x0 action 0x6 frozen
kernel: [  75.870302] ata2.00: failed command: IDENTIFY PACKET DEVICE
kernel: [  75.870307] ata2.00: cmd a1/00:01:00:00:00/00:00:00:00:00/00 tag 0 pio 512 in
kernel: [  75.870307]          res 40/00:03:00:00:00/00:00:00:00:00/a0 Emask 0x4 (timeout)
kernel: [  75.870309] ata2.00: status: { DRDY }
udevd[1419]: worker [1698] timeout, kill it
udevd[1419]: seq 2931 '/devices/pci0000:00/0000:00:11.0/ata2/host3/target3:0:0/3:0:0:0/block/sr0' killed
udevd[1419]: worker [1698] terminated by signal 9 (Killed)
udevd[1419]: worker [1520] timeout, kill it
udevd[1419]: seq 3332 '/devices/pci0000:00/0000:00:11.0/ata2/host3/target3:0:0/3:0:0:0/block/sr0' killed
udevd[1419]: worker [1520] terminated by signal 9 (Killed)
kernel: [  108.814707] ata2.00: exception Emask 0x0 SAct 0x0 SErr 0x0 action 0x6 frozen
kernel: [  108.814711] ata2.00: failed command: IDENTIFY PACKET DEVICE
kernel: [  108.814716] ata2.00: cmd a1/00:01:00:00:00/00:00:00:00:00/00 tag 0 pio 512 in
kernel: [  108.814716]          res 40/00:03:00:00:00/00:00:00:00:00/a0 Emask 0x4 (timeout)
kernel: [  108.814718] ata2.00: status: { DRDY }

Any further suggestions welcomed. Thanks.

cynwulf 05-13-2013 05:52 AM

Ignore my comments regarding SMART, I somehow totally missed the fact that all of the errors referred to ata3 (the optical drive).

How is your SATA controller set up in the BIOS? The "IDENTIFY PACKET DEVICE" may refer to an old udev bug.

dr.trev 05-14-2013 04:30 AM

Well I've solved the problem with a replacement DVD drive. Its the same type only a newer generation. There must have been something faulty with the old one. I tried changing the bios settings and some other suggestions found after searching for "IDENTIFY PACKET DEVICE"; the problem seemed related, but none of the attempts worked.

I was a put off the trail a bit after installing the new drive by an entry I had in /etc/fstab which seems to break things now:
Code:

/dev/sr0        /mnt/cdrom      auto        noauto,owner,ro,x-gvfs-show 0 0
I was getting 'could not mount device' errors mentioning something about unreadable superblocks - can't remember the exact message - but removing that line entirely has fixed things (except that I have to type /run/media/blah/foo-bar instead of /mnt/cdrom now :( ). Has there been some recent changes which mean I can't do this anymore??


All times are GMT -5. The time now is 03:29 AM.