Linux - HardwareThis forum is for Hardware issues.
Having trouble installing a piece of hardware? Want to know if that peripheral is compatible with Linux?
Welcome to LinuxQuestions.org, a friendly and active Linux Community.
You are currently viewing LQ as a guest. By joining our community you will have the ability to post topics, receive our newsletter, use the advanced search, subscribe to threads and access many other special features. Registration is quick, simple and absolutely free. Join our community today!
Note that registered members see fewer ads, and ContentLink is completely disabled once you log in.
When I run this command it doesn't show root it shows my user name
because you're running it as a user.
the output is the command you've entered. i.e. ps is telling you that you ran it, and piped it's result to grep which looked for "gvfsd-cdd" (whatever that is). the only result it found was you looking for "gvfsd-cdd".
For me, every time I inserted a disc (after the first one), Grip complained that the "location is already mounted" (but the software continued to work correctly anyway as long as I inserted another disc when Grip opened the drive door.
However, if I closed the drive WITH NO DISC IN IT - an empty drive - I could not get it to eject through any combination of "eject" commands, pushing a paper clip in the manual eject hole, etc.
However, at a command prompt...
$> lsof |grep gvfsd-cdd
I bet you will see /dev/sr0 (or whatever device your cd/dvd rom is).
Apparently a library that Grip uses (and probably other software as well) doesn't properly release the drive, even if you close Grip.
At a command prompt...
$> ps aux |grep gvfsd-cdd
If you are certain that the drive is empty and that it isn't doing anything useful, kill that process.
The eject button will again work.
EDDY1 and rkelson: I think you may have missed the first command of the two
lsof |grep gvfsd-cdd
in my original message. I think it is an attempt to find out what process if any is locking the drive.
Last edited by Chris.Bristol; 02-07-2012 at 03:45 PM.
rkelsen No, I didn't know how to do that. I've now looked it up and I've got a few ideas for commands to try:
umount /dev/sr0 (you mentioned sr0)
umount /dev/scd0 (scd0 appears in fstab)
umount /media/cdrom0 (cdrom0 appears in fstab)
Apart from once, it has been working today, but I'll try next time it gets stuck. The software is obviously trying to eject as I can hear it, would the software try to eject a disk even though it knew it was mounted, that seems illogical?
I've given some thought to cause and effect - I think that if the disk has something wrong with it the software gets locked into a loop which it can't get out of. Even after I have rebooted and removed the disk manually it will still be a problem. It seems to resolve itself spontaneously.
I will also go through my DVD-RWs and format them and chuck out any dodgy ones, which should lessen the problem in future, but may prompt the problem to happen now.
Last edited by Chris.Bristol; 02-07-2012 at 06:59 PM.
I: -input-charset not specified, using utf-8 (detected in locale settings)
46.41% done, estimate finish Wed Feb 8 01:28:19 2012
Total translation table size: 0
Total rockridge attributes bytes: 261
Total directory bytes: 386
Path table size(bytes): 10
Max brk space used 0
1101 extents written (2 MB)
mkisofs calculate size command:
/usr/bin/genisoimage -gui -graft-points -print-size -quiet -volid chest of drawers -volset -appid K3B THE CD KREATOR (C) 1998-2010 SEBASTIAN TRUEG AND MICHAL MALEK -publisher -preparer -sysid LINUX -volset-size 1 -volset-seqno 1 -sort /tmp/kde-chris/k3bts2079.tmp -rational-rock -hide-list /tmp/kde-chris/k3bjQ2079.tmp -joliet -joliet-long -hide-joliet-list /tmp/kde-chris/k3bcO2079.tmp -no-cache-inodes -full-iso9660-filenames -iso-level 3 -path-list /tmp/kde-chris/k3bDL2079.tmp
/usr/bin/genisoimage -gui -graft-points -volid chest of drawers -volset -appid K3B THE CD KREATOR (C) 1998-2010 SEBASTIAN TRUEG AND MICHAL MALEK -publisher -preparer -sysid LINUX -volset-size 1 -volset-seqno 1 -sort /tmp/kde-chris/k3bQh2079.tmp -rational-rock -hide-list /tmp/kde-chris/k3bGW2079.tmp -joliet -joliet-long -hide-joliet-list /tmp/kde-chris/k3bcT2079.tmp -no-cache-inodes -full-iso9660-filenames -iso-level 3 -path-list /tmp/kde-chris/k3bpQ2079.tmp
I then ejected the disk with K3B without problem!
As a further test I:
- removed the disk.
- closed the empty tray with K3B - success.
- ejected the empty tray with K3b - stuck again!
Last edited by Chris.Bristol; 02-07-2012 at 07:39 PM.
I realised that (too late of course!), but it possibly still proved that the problem was not caused by the disk being mounted. I have just done the unmount and eject commands with all three objects I mentioned above - it sticks.
I then tried:
chris cdrom floppy audio dip video plugdev netdev bluetooth scanner
I think this means that I have the permissions so it's not a permissions problem.
I then tried:
chris@Asus:~$ ls -la /usr/bin/wodim
-rwxr-xr-x 1 root root 359108 Oct 18 2010 /usr/bin/wodim
root@Asus:/home/chris# ls -la /dev/sr0
brw-rw----+ 1 root cdrom 11, 0 Feb 8 01:32 /dev/sr0
This is an earlier suggestion of yours:
root@Asus:/home/chris# fuser /dev/sr0
Last edited by Chris.Bristol; 02-07-2012 at 08:07 PM.
I assumed you'd want me to check the results:
ls -la /usr/bin/wodim
-rwsr-sr-x 1 root root 359108 Oct 18 2010 /usr/bin/wodim
I understand that this is changing permissions although I'm not quite sure what.
I also did the hal command, I've reset that though because after rebooting twice it worked with a disk in but then refused to eject an empty tray. Could the empty tray be relevant?
I wouldn't rule out the possibility that you may have damaged the drive with a paperclip after all that.
lol! No it's not damaged it - there's a solid lump of plastic there. I'm sure it's a software problem for several reasons:
- it works most of the time
- it works without the ribbon cable
- I've had it before with a different PC and a different drive
- it happens mostly with an empty drive
Last edited by Chris.Bristol; 02-07-2012 at 10:23 PM.
rkelson: I've taken out the cable select cable, put in a plain one and altered the drive jumpers from cable select to master and slave. I've also realised that I missed your message 21. I'll follow your suggestions therein.