Re: CDROM device suddenly doesn't exist....
On Wed, 11 Jan 2017 11:52:30 -0500 Ric Moore sent: > On 01/11/2017 03:02 AM, Thomas Schmitt wrote: > > Hi, > > > > Charlie wrote: > >> mount: /dev/sr0 is write-protected, mounting read-only > >> mount: special device /dev/sr0 does not exist > > > > Does command dmesg report something about "sr0" after this > > happened ? > > > > > > Have a nice day :) > > Do you have a bios selection for the cdrom drive?? Last time this > happened to me, replacement of the drive fixed the problem. Ric After contemplation, my reply is: Just for completeness: Checked the BIOS to see if there was anything that might be changed or to be discovered, without result. Changed some of the numbers in: /etc/udev/rules.d/persistent-cd.rules Which brought up error messages about /dev/sr0 not being a block device. Then went through the: mknod sr0 b 11 0 process as explained previously again. Rebooted the system. Ran through discovering what was now happening- surprise: ls -l /dev/sr0 brw-rw+ 1 root cdrom 11, 0 Jan 12 08:54 /dev/sr0 Did eject, put in a data DVD, and read it. Ejected it again closed the drawer Retried eject: ~$ eject eject: tried to use `/dev/sr0' as device name but it is no block device eject: unable to find or open device for: `cdrom' So the drive is definitely crook. Thanks for your suggestions. Much appreciated. Charlie -- Registered Linux User:- 329524 *** He is a hard man who is only just, and a sad one who is only wise. --Voltaire *** Debian GNU/Linux - Magic indeed. -
Re: CDROM device suddenly doesn't exist....
On Wed, 11 Jan 2017 11:52:30 -0500 Ric Moore sent: > Do you have a bios selection for the cdrom drive?? Last time this > happened to me, replacement of the drive fixed the problem. Ric After contemplation, my reply is: Thanks Thomas and Ric, Nothing in dmesg report and I will look at the BIOS and see what is to be seen there. Not using that drive hardly at all. I'm not too worried, but it just seemed a strange thing to happen. Thank you both for your help. Charlie -- Registered Linux User:- 329524 *** A man is either free or he is not. There cannot be any apprenticeship for freedom. --Amiri Baraka *** Debian GNU/Linux - Magic indeed. -
Re: CDROM device suddenly doesn't exist....
On 01/11/2017 03:02 AM, Thomas Schmitt wrote: Hi, Charlie wrote: mount: /dev/sr0 is write-protected, mounting read-only mount: special device /dev/sr0 does not exist Does command dmesg report something about "sr0" after this happened ? Have a nice day :) Do you have a bios selection for the cdrom drive?? Last time this happened to me, replacement of the drive fixed the problem. Ric -- My father, Victor Moore (Vic) used to say: "There are two Great Sins in the world... ..the Sin of Ignorance, and the Sin of Stupidity. Only the former may be overcome." R.I.P. Dad. http://linuxcounter.net/user/44256.html
Re: CDROM device suddenly doesn't exist....
Hi, Charlie wrote: > mount: /dev/sr0 is write-protected, mounting read-only > mount: special device /dev/sr0 does not exist Does command dmesg report something about "sr0" after this happened ? Have a nice day :) Thomas
Re: CDROM device suddenly doesn't exist....
On Wed, 11 Jan 2017 13:09:59 +1100 Charlie sent: > Hello, > > Debian testing 4.6.0-1-amd64 #1 SMP Debian 4.6.4-1 (2016-07-18) x86_64 > GNU/Linux > > Suddenly have a CDROM problem: > $ mount /media/cdrom > mount: /dev/sr0 is write-protected, mounting read-only > mount: special device /dev/sr0 does not exist > > Did: > > # ls -l /dev/sr0 > ls: cannot access '/dev/sr0': No such file or directory > > # cd /dev > /dev# mknod sr0 b 11 0 > /dev# chgrp cdrom sr0 > /dev# chmod 660 sr0 > > Before reboot get: > > ~$ mount /media/cdrom > mount: /dev/sr0 is write-protected, mounting read-only > mount: /dev/sr0 is not a valid block device > > After rebooting makes Midnight Commander [mc] unresponsive? > > Obviously have done something wrong. > > Any help to get this CDROM working again, appreciated. > > Charlie After contemplation, an addendum: Now I get: $ mount /media/cdrom0 mount: /dev/sr0 is write-protected, mounting read-only mount: special device /dev/sr0 does not exist again. Will have to see what else I can find. Charlie -- Registered Linux User:- 329524 *** It is dangerous to be right when the government is wrong. ...Voltaire *** Debian GNU/Linux - Magic indeed. -
Re: No cdrom device
In gmane.linux.debian.user, you wrote: lshw output in my case has no *cdrom entry at all. I rebooted, opened the tray manually, inserted a Knoppix disk and set the BIOS to boot off the cdrom drive. No luck - booted from the hard drive. That sounds like a hardware problem with the cdrom drive. Also,modprobe sr_modgave me sg0 in /dev (?). mount /dev/sg0 /mnt/cdrom gave mount: /dev/sg0 is not a block device This is getting wierder and wierder. -- Never believe the attribution of a quotation you find on the Internet. (George Bernard Shaw) -- To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/E1Rg7jv-0005eG-Cy@lat.local
Re: No cdrom device
On Thursday, December 29, 2011 11:39:45 AM Vincent Lefevre wrote: No, it wasn't a hardware problem. After much travail with udev, modprobe, interrupts, etc. and leariing more about dmesg output than I care to know, I thought - well, no sr0? Then make one! touch /dev/sr0 chown root:disk /dev/sr0 chmod 660 /dev/sr0 You shouldn't need to do that manually. There's something broken on your system. Perhaps, but the device survives reboots, so -- if all is well, then it is. -- To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/201112291301.54809.edj...@gmail.com
Re: No cdrom device
On Wednesday, December 28, 2011 11:37:15 PM Bill Marcum wrote: In gmane.linux.debian.user, you wrote: lshw output in my case has no *cdrom entry at all. I rebooted, opened the tray manually, inserted a Knoppix disk and set the BIOS to boot off the cdrom drive. No luck - booted from the hard drive. That sounds like a hardware problem with the cdrom drive. No, it wasn't a hardware problem. After much travail with udev, modprobe, interrupts, etc. and leariing more about dmesg output than I care to know, I thought - well, no sr0? Then make one! touch /dev/sr0 chown root:disk /dev/sr0 chmod 660 /dev/sr0 And that was that. Sometimes the simplest, most obvious solution is the one that eludes us the most. -- To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/201112291110.53653.edj...@gmail.com
Re: No cdrom device
On 2011-12-29 11:10:52 -0500, edj...@gmail.com wrote: On Wednesday, December 28, 2011 11:37:15 PM Bill Marcum wrote: In gmane.linux.debian.user, you wrote: lshw output in my case has no *cdrom entry at all. I rebooted, opened the tray manually, inserted a Knoppix disk and set the BIOS to boot off the cdrom drive. No luck - booted from the hard drive. That sounds like a hardware problem with the cdrom drive. No, it wasn't a hardware problem. After much travail with udev, modprobe, interrupts, etc. and leariing more about dmesg output than I care to know, I thought - well, no sr0? Then make one! touch /dev/sr0 chown root:disk /dev/sr0 chmod 660 /dev/sr0 You shouldn't need to do that manually. There's something broken on your system. -- Vincent Lefèvre vinc...@vinc17.net - Web: http://www.vinc17.net/ 100% accessible validated (X)HTML - Blog: http://www.vinc17.net/blog/ Work: CR INRIA - computer arithmetic / Arénaire project (LIP, ENS-Lyon) -- To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/20111229163945.gr5...@xvii.vinc17.org
Re: No cdrom device
On Thu, 29 Dec 2011 13:01:54 -0500 edj...@gmail.com edj...@gmail.com suggested this: On Thursday, December 29, 2011 11:39:45 AM Vincent Lefevre wrote: No, it wasn't a hardware problem. After much travail with udev, modprobe, interrupts, etc. and leariing more about dmesg output than I care to know, I thought - well, no sr0? Then make one! touch /dev/sr0 chown root:disk /dev/sr0 chmod 660 /dev/sr0 You shouldn't need to do that manually. There's something broken on your system. Perhaps, but the device survives reboots, so -- if all is well, then it is. After an upgrade a couple of weeks ago, had to change the cdrom's from /dev/scd* to /dev/sr* Have no idea why? However, leaving them as /dev/scd* they weren't recognised. Charlie -- Registered Linux User:- 329524 *** In prosperity our friends know us; in adversity we know our friends. Churton Collins *** Debian GNU/Linux - just the best way to create magic ___ -- To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/20111230075308.06233acd@taowild
Re: No cdrom device
On 2011-12-23 20:14:32 -0500, Ed Jabbour wrote: On Friday, December 23, 2011 7:32:22 PM Vincent Lefevre wrote: Yes, /dev/scd0 disappeared after a recent upgrade (after 2011-11-17). Why do I still get error msgs referring to scd0?? Perhaps because it is mentioned in /etc/fstab? Running lshw *as root* says which /dev files can be used. In my case: *-cdrom description: DVD-RAM writer product: DVD+-RW TS-U633A vendor: TSSTcorp physical id: 1 bus info: scsi@1:0.0.0 logical name: /dev/cdrom logical name: /dev/cdrw logical name: /dev/dvd logical name: /dev/dvdrw logical name: /dev/sr0 version: D300 capabilities: removable audio cd-r cd-rw dvd dvd-r dvd-ram configuration: ansiversion=5 status=nodisc I've chosen to use /dev/cdrom in case /dev/sr0 would be replaced by something else. lshw output in my case has no *cdrom entry at all. Note: I recall that lshw must be run as root (if I run lshw as a normal user, I don't get a *-cdrom entry either). Otherwise perhaps your drive is not recognized. I rebooted, opened the tray manually, inserted a Knoppix disk and set the BIOS to boot off the cdrom drive. No luck - booted from the hard drive. Also,modprobe sr_modgave me sg0 in /dev (?). mount /dev/sg0 /mnt/cdrom gave mount: /dev/sg0 is not a block device This is getting wierder and wierder. Here I don't need modprobe sr_mod. It is loaded automatically. -- Vincent Lefèvre vinc...@vinc17.net - Web: http://www.vinc17.net/ 100% accessible validated (X)HTML - Blog: http://www.vinc17.net/blog/ Work: CR INRIA - computer arithmetic / Arénaire project (LIP, ENS-Lyon) -- To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/20111224114154.gf15...@xvii.vinc17.org
Re: No cdrom device
On 12/23/2011 06:32 PM, Vincent Lefevre wrote: On 2011-12-23 18:30:25 -0500, Wayne Topa wrote: On 12/23/2011 03:38 PM, Wayne Topa wrote: On 12/23/2011 12:18 PM, Ed Jabbour wrote: CDROM tray will not respond to eject: [Fri Dec 23] edj:~$ eject eject: tried to use `/media/cdrom0' as device name but it is no block device eject: tried to use `/dev/scd0' as device name but it is no block device eject: unable to find or open device for: `cdrom' = Yes, /dev/scd0 disappeared after a recent upgrade (after 2011-11-17). I believe that was after a udev update. It showed up in the changelog. Hugo -- To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/jd4srj$h58$1...@dough.gmane.org
Re: No cdrom device
On 2011-12-24 09:58:43 -0600, Hugo Vanwoerkom wrote: On 12/23/2011 06:32 PM, Vincent Lefevre wrote: Yes, /dev/scd0 disappeared after a recent upgrade (after 2011-11-17). I believe that was after a udev update. It showed up in the changelog. Indeed: udev (175-1) unstable; urgency=low [...] * 50-udev-default.rules: removed the obsolete scd%n symlinks. [...] -- Marco d'Itri m...@linux.it Fri, 18 Nov 2011 03:05:39 +0100 -- Vincent Lefèvre vinc...@vinc17.net - Web: http://www.vinc17.net/ 100% accessible validated (X)HTML - Blog: http://www.vinc17.net/blog/ Work: CR INRIA - computer arithmetic / Arénaire project (LIP, ENS-Lyon) -- To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/20111224163610.ga5...@xvii.vinc17.org
No cdrom device
CDROM tray will not respond to eject: [Fri Dec 23] edj:~$ eject eject: tried to use `/media/cdrom0' as device name but it is no block device eject: tried to use `/dev/scd0' as device name but it is no block device eject: unable to find or open device for: `cdrom' = Perhaps related, dmesg reveals: == 6.720030] ata1: link is slow to respond, please be patient (ready=0) [ 11.704028] ata1: device not ready (errno=-16), forcing hardreset [ 16.900028] ata1: link is slow to respond, please be patient (ready=0) [ 21.716029] ata1: SRST failed (errno=-16) [ 26.912027] ata1: link is slow to respond, please be patient (ready=0) [ 31.728027] ata1: SRST failed (errno=-16) [ 36.924030] ata1: link is slow to respond, please be patient (ready=0) [ 66.772029] ata1: SRST failed (errno=-16) [ 71.800028] ata1: SRST failed (errno=-16) [ 71.811047] ata1: reset failed, giving up [ 71.811185] ata2: port disabled--ignoring = modprobe cdrom sr_mod: == FATAL: Error inserting cdrom (/lib/modules/3.1.0-1-686- pae/kernel/drivers/cdrom/cdrom.ko): Unknown symbol in module, or unknown parameter (see dmesg) 728.919036] cdrom: Unknown parameter `sr_mod' === Nor will the tray open manually, except that it does if on reboot, I push the button before GRUB takes over. Running testing with the 3.1.0-1-686-pae kernel, although the problem persists no matter which kernel I boot into. Any advice, pointers, etc. appreciated. -- To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/201112231218.47633.e...@att.net
Re: No cdrom device
On Fri, Dec 23, 2011 at 05:18:47PM GMT, Ed Jabbour wrote: CDROM tray will not respond to eject: [Fri Dec 23] edj:~$ eject eject: tried to use `/media/cdrom0' as device name but it is no block device eject: tried to use `/dev/scd0' as device name but it is no block device eject: unable to find or open device for: `cdrom' = Which device is you optical drive? Perhaps related, dmesg reveals: == 6.720030] ata1: link is slow to respond, please be patient (ready=0) [ 11.704028] ata1: device not ready (errno=-16), forcing hardreset [ 16.900028] ata1: link is slow to respond, please be patient (ready=0) [ 21.716029] ata1: SRST failed (errno=-16) [ 26.912027] ata1: link is slow to respond, please be patient (ready=0) [ 31.728027] ata1: SRST failed (errno=-16) [ 36.924030] ata1: link is slow to respond, please be patient (ready=0) [ 66.772029] ata1: SRST failed (errno=-16) [ 71.800028] ata1: SRST failed (errno=-16) [ 71.811047] ata1: reset failed, giving up [ 71.811185] ata2: port disabled--ignoring = Might be related, see below. modprobe cdrom sr_mod: == FATAL: Error inserting cdrom (/lib/modules/3.1.0-1-686- pae/kernel/drivers/cdrom/cdrom.ko): Unknown symbol in module, or unknown parameter (see dmesg) You're trying to load two modules (cdrom and sr_mod) and modprobe treats the second one as a parameter to the first one. You should load modules one by one. 728.919036] cdrom: Unknown parameter `sr_mod' Which part of the above message is not clear? ;^) Nor will the tray open manually, except that it does if on reboot, I push the button before GRUB takes over. Running testing with the 3.1.0-1-686-pae kernel, although the problem persists no matter which kernel I boot into. Any advice, pointers, etc. appreciated. The above dmesg messages might point to faulty drive or cable. Does the optical drive work at all, e.g. under another OS? Regards, -- Raf -- To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/20111223174823.ga18...@linuxstuff.pl
Re: No cdrom device
On 12/23/2011 12:18 PM, Ed Jabbour wrote: CDROM tray will not respond to eject: [Fri Dec 23] edj:~$ eject eject: tried to use `/media/cdrom0' as device name but it is no block device eject: tried to use `/dev/scd0' as device name but it is no block device eject: unable to find or open device for: `cdrom' = Perhaps related, dmesg reveals: == 6.720030] ata1: link is slow to respond, please be patient (ready=0) [ 11.704028] ata1: device not ready (errno=-16), forcing hardreset [ 16.900028] ata1: link is slow to respond, please be patient (ready=0) [ 21.716029] ata1: SRST failed (errno=-16) [ 26.912027] ata1: link is slow to respond, please be patient (ready=0) [ 31.728027] ata1: SRST failed (errno=-16) [ 36.924030] ata1: link is slow to respond, please be patient (ready=0) [ 66.772029] ata1: SRST failed (errno=-16) [ 71.800028] ata1: SRST failed (errno=-16) [ 71.811047] ata1: reset failed, giving up [ 71.811185] ata2: port disabled--ignoring = modprobe cdrom sr_mod: == FATAL: Error inserting cdrom (/lib/modules/3.1.0-1-686- pae/kernel/drivers/cdrom/cdrom.ko): Unknown symbol in module, or unknown parameter (see dmesg) 728.919036] cdrom: Unknown parameter `sr_mod' === Nor will the tray open manually, except that it does if on reboot, I push the button before GRUB takes over. Running testing with the 3.1.0-1-686-pae kernel, although the problem persists no matter which kernel I boot into. Any advice, pointers, etc. appreciated. Locate your cdrom with: $dmesg |grep -A2 B2 cdrom Which in my case returns; ~$ dmesg |grep -A2 -B2 cdrom [2.592157] sd 2:0:0:0: [sda] Attached SCSI disk [2.640560] sr0: scsi3-mmc drive: 48x/48x writer dvd-ram cd/rw xa/form2 cdda tray [2.640634] cdrom: Uniform CD-ROM driver Revision: 3.20 [2.640848] sr 0:0:0:0: Attached scsi CD-ROM sr0 [2.704036] usb 4-1: new full speed USB device number 2 using ohci_hcd Which shows my cdrom is /dev/sd0 I eject with: eject /dev/sr0 or with this line in my /etc/fstab /dev/sr0 /media/cdrom0 udf,iso9660 user,noauto 0 0 eject /media/cdrom0 HTH WT -- To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/4ef4e6b1@gmail.com
Re: No cdrom device
On 12/23/2011 03:38 PM, Wayne Topa wrote: On 12/23/2011 12:18 PM, Ed Jabbour wrote: CDROM tray will not respond to eject: [Fri Dec 23] edj:~$ eject eject: tried to use `/media/cdrom0' as device name but it is no block device eject: tried to use `/dev/scd0' as device name but it is no block device eject: unable to find or open device for: `cdrom' = Perhaps related, dmesg reveals: == 6.720030] ata1: link is slow to respond, please be patient (ready=0) [ 11.704028] ata1: device not ready (errno=-16), forcing hardreset [ 16.900028] ata1: link is slow to respond, please be patient (ready=0) [ 21.716029] ata1: SRST failed (errno=-16) [ 26.912027] ata1: link is slow to respond, please be patient (ready=0) [ 31.728027] ata1: SRST failed (errno=-16) [ 36.924030] ata1: link is slow to respond, please be patient (ready=0) [ 66.772029] ata1: SRST failed (errno=-16) [ 71.800028] ata1: SRST failed (errno=-16) [ 71.811047] ata1: reset failed, giving up [ 71.811185] ata2: port disabled--ignoring = modprobe cdrom sr_mod: == FATAL: Error inserting cdrom (/lib/modules/3.1.0-1-686- pae/kernel/drivers/cdrom/cdrom.ko): Unknown symbol in module, or unknown parameter (see dmesg) 728.919036] cdrom: Unknown parameter `sr_mod' === Nor will the tray open manually, except that it does if on reboot, I push the button before GRUB takes over. Running testing with the 3.1.0-1-686-pae kernel, although the problem persists no matter which kernel I boot into. Any advice, pointers, etc. appreciated. Locate your cdrom with: $dmesg |grep -A2 B2 cdrom Which in my case returns; ~$ dmesg |grep -A2 -B2 cdrom [ 2.592157] sd 2:0:0:0: [sda] Attached SCSI disk [ 2.640560] sr0: scsi3-mmc drive: 48x/48x writer dvd-ram cd/rw xa/form2 cdda tray [ 2.640634] cdrom: Uniform CD-ROM driver Revision: 3.20 [ 2.640848] sr 0:0:0:0: Attached scsi CD-ROM sr0 [ 2.704036] usb 4-1: new full speed USB device number 2 using ohci_hcd Which shows my cdrom is /dev/sd0 Woops ^^^ /dev/sr0 sorry I eject with: eject /dev/sr0 or with this line in my /etc/fstab /dev/sr0 /media/cdrom0 udf,iso9660 user,noauto 0 0 eject /media/cdrom0 HTH WT -- To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/4ef50f11.2000...@gmail.com
Re: No cdrom device
On 2011-12-23 18:30:25 -0500, Wayne Topa wrote: On 12/23/2011 03:38 PM, Wayne Topa wrote: On 12/23/2011 12:18 PM, Ed Jabbour wrote: CDROM tray will not respond to eject: [Fri Dec 23] edj:~$ eject eject: tried to use `/media/cdrom0' as device name but it is no block device eject: tried to use `/dev/scd0' as device name but it is no block device eject: unable to find or open device for: `cdrom' = Yes, /dev/scd0 disappeared after a recent upgrade (after 2011-11-17). ~$ dmesg |grep -A2 -B2 cdrom [ 2.592157] sd 2:0:0:0: [sda] Attached SCSI disk [ 2.640560] sr0: scsi3-mmc drive: 48x/48x writer dvd-ram cd/rw xa/form2 cdda tray [ 2.640634] cdrom: Uniform CD-ROM driver Revision: 3.20 [ 2.640848] sr 0:0:0:0: Attached scsi CD-ROM sr0 [ 2.704036] usb 4-1: new full speed USB device number 2 using ohci_hcd Which shows my cdrom is /dev/sd0 Woops ^^^ /dev/sr0 sorry I eject with: eject /dev/sr0 or with this line in my /etc/fstab /dev/sr0 /media/cdrom0 udf,iso9660 user,noauto 0 0 eject /media/cdrom0 Running lshw *as root* says which /dev files can be used. In my case: *-cdrom description: DVD-RAM writer product: DVD+-RW TS-U633A vendor: TSSTcorp physical id: 1 bus info: scsi@1:0.0.0 logical name: /dev/cdrom logical name: /dev/cdrw logical name: /dev/dvd logical name: /dev/dvdrw logical name: /dev/sr0 version: D300 capabilities: removable audio cd-r cd-rw dvd dvd-r dvd-ram configuration: ansiversion=5 status=nodisc I've chosen to use /dev/cdrom in case /dev/sr0 would be replaced by something else. -- Vincent Lefèvre vinc...@vinc17.net - Web: http://www.vinc17.net/ 100% accessible validated (X)HTML - Blog: http://www.vinc17.net/blog/ Work: CR INRIA - computer arithmetic / Arénaire project (LIP, ENS-Lyon) -- To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/20111224003222.ge15...@xvii.vinc17.org
Re: No cdrom device
On Friday, December 23, 2011 7:32:22 PM Vincent Lefevre wrote: Yes, /dev/scd0 disappeared after a recent upgrade (after 2011-11-17). Why do I still get error msgs referring to scd0?? Running lshw *as root* says which /dev files can be used. In my case: *-cdrom description: DVD-RAM writer product: DVD+-RW TS-U633A vendor: TSSTcorp physical id: 1 bus info: scsi@1:0.0.0 logical name: /dev/cdrom logical name: /dev/cdrw logical name: /dev/dvd logical name: /dev/dvdrw logical name: /dev/sr0 version: D300 capabilities: removable audio cd-r cd-rw dvd dvd-r dvd-ram configuration: ansiversion=5 status=nodisc I've chosen to use /dev/cdrom in case /dev/sr0 would be replaced by something else. lshw output in my case has no *cdrom entry at all. I rebooted, opened the tray manually, inserted a Knoppix disk and set the BIOS to boot off the cdrom drive. No luck - booted from the hard drive. Also,modprobe sr_modgave me sg0 in /dev (?). mount /dev/sg0 /mnt/cdrom gave mount: /dev/sg0 is not a block device This is getting wierder and wierder. -- To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/201112232014.32945.e...@att.net
desmontar CDROM ( device is busy)
Pessoal, Tenho uma máquina com Debian (kernel 2.6.8) , placa mae M812, kde 3.2.Aposmontar o CDROM pelo konqueror, este não desmonta, nem com umount -f, nem dando logout. Somente dando init 1 e posteriormente init 5 é que consegui desmontá-lo com umount. Alguém tem alguma idéia?Obrigado Eduardo Yahoo! Acesso Grátis Internet rápida e grátis. Instale o discador agora!
Re: desmontar CDROM ( device is busy)
* Eduardo Braga ([EMAIL PROTECTED]) wrote: Pessoal, Tenho uma máquina com Debian (kernel 2.6.8) , placa mae M812, kde 3.2. Apos montar o CDROM pelo konqueror, este não desmonta, nem com umount -f, nem dando logout. Somente dando init 1 e posteriormente init 5 é que consegui desmontá-lo com umount. Alguém tem alguma idéia? Existe um comportamento no koquenror que exige que você clique no device com o botão direito do mouse e mande desmontar ou ejetar. Se você fecha o konqueror sem fazer isso, ele prende a midia e o umount não consegue desmontar por ela estar em uso. Não sei se isso é um bug ou um comportamento não previsto, pois só o konqueror exige este procedimento. Não vou propor a você mudar de Desktop, mas entre numa lista de KDE e verifique se este comportamento é previsto e proponha alternativas. Por enquanto, use o fuse para ver qual processo está prendendo a mídia e mate-o para poder desmontar, man fuse para ver como usar. []'s -- Qual é a minha expectativa, e por que eu sou petista, e por que com todos os desastres deste partido, eu continuo nele? Porque acho que temos um processo histórico lento a realizar, que começou muito antes de mim, e que os meus bisnetos vão finalizar. Marilena Chaui
Re: desmontar CDROM ( device is busy)
Eduardo, aqui de vez em quando acontece isso, normalmente fao assim : fuser -m /mnt/cdrom1 /mnt/cdrom 1234567x kill -9 1234567x Leve em considerao que aqui o meu cdrom o /mnt/cdrom1 e depois do kill -9 voce coloca os numeros que reportou o uso do cdrom. isso. Eduardo Braga escreveu: Pessoal, Tenho uma mquina com Debian (kernel 2.6.8) , placa mae M812, kde 3.2. Aposmontar o CDROM pelo konqueror, este no desmonta, nem com umount -f, nem dando logout. Somente dando init 1 e posteriormente init 5 que consegui desmont-lo com umount. Algum tem alguma idia? Obrigado Eduardo Yahoo! Acesso Grtis Internet rpida e grtis. Instale o discador agora!
Re: desmontar CDROM ( device is busy)
Eduardo, Como outro colega falou, o problema é que o konqueror continua como que usando o disco montado, e assim o umount dá a mensagem citada. Não é mérito só do konqueror, já vi a mesma coisa com o nautilus. Você pode dar um umount -l e vai resolver o problema, ele limpa as referências ao filesystem. Dê um man umount e veja os detalhes! Boa sorte! On 4/5/06, Eduardo Braga [EMAIL PROTECTED] wrote: Pessoal, Tenho uma máquina com Debian (kernel 2.6.8) , placa mae M812, kde 3.2.Aposmontar o CDROM pelo konqueror, este não desmonta, nem com umount -f, nem dando logout. Somente dando init 1 e posteriormente init 5 é que consegui desmontá-lo com umount. Alguém tem alguma idéia?Obrigado Eduardo Yahoo! Acesso Grátis Internet rápida e grátis. Instale o discador agora! -- Jonathan. R. MartinsMestrando em FísicaUniversidade Federal de Minas GeraisICEX
tar giving different results for same command, trying to test cdrom device integrity
I am curious if anyone can clear up the following phenomena for gnu tar on testing: # tar --version tar (GNU tar) 1.13.25 Copyright (C) 2001 Free Software Foundation, Inc. This program comes with NO WARRANTY, to the extent permitted by law. You may redistribute it under the terms of the GNU General Public License; see the file named COPYING for details. Written by John Gilmore and Jay Fenlason. basically I have cdrom mounted under a directory and i ran tar zcvf win2k.tgz /mnt and tar zcvf win2k-2.tgz /mnt Perhaps I should be using different options to get the same files: # cmp -version cmp - GNU diffutils version 2.7 cmp -l on the files yields: # cmp -l * 5 35 362 6 4 2 I also did a dd on the raw device and that at least gave no differences. I am trying to determine whether the cdrom drive is faulty. Does anyone know of good ways to test such a thing. -walter
Re: tar giving different results for same command, trying to test cdrom device integrity
Walter Tautz wrote: I am curious if anyone can clear up the following phenomena for gnu tar on testing: # tar --version tar (GNU tar) 1.13.25 Copyright (C) 2001 Free Software Foundation, Inc. This program comes with NO WARRANTY, to the extent permitted by law. You may redistribute it under the terms of the GNU General Public License; see the file named COPYING for details. Written by John Gilmore and Jay Fenlason. basically I have cdrom mounted under a directory and i ran tar zcvf win2k.tgz /mnt and tar zcvf win2k-2.tgz /mnt Perhaps I should be using different options to get the same files: # cmp -version cmp - GNU diffutils version 2.7 cmp -l on the files yields: # cmp -l * 5 35 362 6 4 2 I also did a dd on the raw device and that at least gave no differences. I am trying to determine whether the cdrom drive is faulty. Does anyone know of good ways to test such a thing. -walter I have had some success with the following procedure: 1 use dd to create an image copy of the cd on hard disk; e.g. dd if=/dev/cdrom of=/tmp/cdcpy1 2 mount a loop back view of cdcpy1 e.g. mount -t iso9660 -o ro,loop=/dev/loop0 /tmp/cdcpy1 /your/mount/point 3 use diff to compare /your/mount/point to /cdrom Paul
Re: Error accessing cdrom device
Thus spake Eric Brooks ([EMAIL PROTECTED]): I tried adding myself into the cdrom group but that did not solve the problem. Did you re-login after doing that? -- Justin R. Miller [EMAIL PROTECTED] View my website at http://codesorcery.net Please encrypt email using key 0xC9C40C31 pgpR1SukqVNwA.pgp Description: PGP signature
Re: Error accessing cdrom device
On Fri, Dec 14, 2001 at 12:47:10AM -0500, Justin R. Miller wrote: Did you re-login after doing that? No, I didn't. I'll try that. Thanks very much. pgpPiRdSMV5Vy.pgp Description: PGP signature
Re: Error accessing cdrom device
Eric Brooks wrote: On Fri, Dec 14, 2001 at 12:47:10AM -0500, Justin R. Miller wrote: Did you re-login after doing that? No, I didn't. I'll try that. Thanks very much. it's enough to do su - yourself (if you're using X and don't want to restart it) erik
Re: Error accessing cdrom device
Thus spake Erik Steffl ([EMAIL PROTECTED]): it's enough to do su - yourself (if you're using X and don't want to restart it) That'll work for at least that console, but what about if you want to start an app from the menu -- I don't think the new environment will be picked up until you re-login to X. -- Justin R. Miller [EMAIL PROTECTED] View my website at http://codesorcery.net Please encrypt email using key 0xC9C40C31 pgpwxacBsOdFR.pgp Description: PGP signature
Error accessing cdrom device
Hi. I recently installed Alsa and I am working through getting sound running. I can read data off my CDROM just fine. When I try to play music off the CD I get the error: Error accessing cdrom device. Please check to make sure cdrom drive support is compiled into the kernel, and that you have permission to access the device. Reason: Permission denied. I tried adding myself into the cdrom group but that did not solve the problem. I would appreciate any help in moving forward with this. Regards, Eric -- Eric Brooks | [EMAIL PROTECTED] | www.dimension11.net
Re: Correction: CDROM device..
Hall Stevenson wrote: okay, this.. is stupid question.. being completely spoilt by Redhats simplicity.. i'm unaware of which device /dev/cdrom was linked to. ..can someone, give me a hint? Try ls -l /dev/cdrom How's that for simplicity ?? ;-) You can even do it in completly opposite direction: Find in dmesg which device is a cdrom drive hdc: SAMSUNG CD-ROM SC-148F, ATAPI CDROM drive and make a link rm /dev/cdrom ln -s /dev/hdc /dev/cdrom :) -- Mariusz Zielinski
Re: SOLVED Re: Correction: CDROM device..
On Mon, 19 Feb 2001 03:29:37 +0100, William Leese [EMAIL PROTECTED] wrote: On Monday 19 February 2001 03:19, Hall Stevenson wrote: okay, this.. is stupid question.. being completely spoilt by Redhats simplicity.. i'm unaware of which device /dev/cdrom was linked to. ..can someone, give me a hint? Try ls -l /dev/cdrom How's that for simplicity ?? ;-) okay okay.. thank you for making me look like a moron ;) ..though that wasnt quite the problem.. ..the link that i was used to when i used redhat wasnt already present with debian.. so i needed to know which device it used to point to (i dont have redhat on any machine here).. If I'm understanding you correctly, It depends upon what type of cdrom you have. If you have an IDE cdrom, it's simply the appropriate hd device. My cdrom is the first device on the second IDE port, so /dev/cdrom is linked to /dev/hdc. If you have a SCSI, it'll be /dev/scd?, where ? is the appropriate device number. If you have one of the old, proprietary models, I'm not sure off the top of my head. If you post back which sort of interface it is (Sony, Panasonic, etc.) somebody will probably know. Dan
Correction: CDROM device..
okay, this.. is stupid question.. being completely spoilt by Redhats simplicity.. i'm unaware of which device /dev/cdrom was linked to. ..can someone, give me a hint? though not quite certain i think its master on the secondary channel. (makes sense when using one HD and one CDROM-drive)
Re: CDROM device..
On Sun, Feb 18, 2001 at 03:23:50PM +0100, William Leese wrote: okay, this.. is stupid question.. being completely spoilt by Redhats simplicity.. i'm unaware of which device /dev/cdrom was linked to. ..can someone, give me a hint? Mines linked to hdc but yours may be different. Check - $ dmesg|less to see which device your cdrom is. kent -- From seeing and seeing the seeing has become so exhausted First line of The Panther - R. M. Rilke
Re: CDROM device..
On Tuesday 18 December 2001 07:20, ktb wrote: On Sun, Feb 18, 2001 at 03:23:50PM +0100, William Leese wrote: okay, this.. is stupid question.. being completely spoilt by Redhats simplicity.. i'm unaware of which device /dev/cdrom was linked to. ..can someone, give me a hint? Mines linked to hdc but yours may be different. Check - $ dmesg|less to see which device your cdrom is. ..ah, cheers.. found it..
Re: CDROM device..
William Leese wrote: okay, this.. is stupid question.. being completely spoilt by Redhats simplicity.. i'm unaware of which device /dev/cdrom was linked to. ..can someone, give me a hint? William -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED] At a terminal MC go to the /dev directory scroll down to the: @cdrom look in the bottom info line for that pane mine sez:-hdc Sam finally a question I knew ... yippie think i'll have a beer ... hehehe
Re: Correction: CDROM device..
William Leese wrote: okay, this.. is stupid question.. being completely spoilt by Redhats simplicity.. i'm unaware of which device /dev/cdrom was linked to. ..can someone, give me a hint? though not quite certain i think its master on the secondary channel. (makes sense when using one HD and one CDROM-drive) On mine -- and I understand this to be the usual way, it is the slave on the second channel, i.e. /dev/hdd Cam -- Cam Ellison Ph.D. R.Psych. From Roberts Creek on B.C.'s incomparable Sunshine Coast [EMAIL PROTECTED] [EMAIL PROTECTED]
Re: CDROM device..
On Sun, Feb 18, 2001 at 03:05:16PM +, SamBozo Debian User wrote: William Leese wrote: okay, this.. is stupid question.. being completely spoilt by Redhats simplicity.. i'm unaware of which device /dev/cdrom was linked to. ..can someone, give me a hint? At a terminal MC go to the /dev directory scroll down to the: @cdrom look in the bottom info line for that pane mine sez:-hdc Just a tip for you - $ cd /dev $ ls | less -while in less hit / -type cdrom -hit enter Cuts down on the scrolling. I guess this would be even shorter - $ ls -l /dev/cdrom kent -- From seeing and seeing the seeing has become so exhausted First line of The Panther - R. M. Rilke
Re: CDROM device..
Ah Cmd Line Magic ... I am continuly awestruck. Now if I could just remember all this stuff. But I go the next best thing Linux in a Nutshell and Running Linux race ya to see who's wares out 1st Sam ktb wrote: On Sun, Feb 18, 2001 at 03:05:16PM +, SamBozo Debian User wrote: William Leese wrote: okay, this.. is stupid question.. being completely spoilt by Redhats simplicity.. i'm unaware of which device /dev/cdrom was linked to. ..can someone, give me a hint? At a terminal MC go to the /dev directory scroll down to the: @cdrom look in the bottom info line for that pane mine sez:-hdc Just a tip for you - $ cd /dev $ ls | less -while in less hit / -type cdrom -hit enter Cuts down on the scrolling. I guess this would be even shorter - $ ls -l /dev/cdrom kent
Re: Correction: CDROM device..
okay, this.. is stupid question.. being completely spoilt by Redhats simplicity.. i'm unaware of which device /dev/cdrom was linked to. ..can someone, give me a hint? Try ls -l /dev/cdrom How's that for simplicity ?? ;-) Regards Hall
SOLVED Re: Correction: CDROM device..
On Monday 19 February 2001 03:19, Hall Stevenson wrote: okay, this.. is stupid question.. being completely spoilt by Redhats simplicity.. i'm unaware of which device /dev/cdrom was linked to. ..can someone, give me a hint? Try ls -l /dev/cdrom How's that for simplicity ?? ;-) okay okay.. thank you for making me look like a moron ;) ..though that wasnt quite the problem.. ..the link that i was used to when i used redhat wasnt already present with debian.. so i needed to know which device it used to point to (i dont have redhat on any machine here).. cheers anyhow :)
Re: cdrom device not there
After reinstalling my system (hamm) from scratch I have no /dev/cdrom Is this obselete ? If yes then what is the name of the new device ? I have tried ./MAKEDEV cdrom and got an error Any ideas ? George /dev/cdrom is not a device, but a symbolic link to the cdrom device. If you have an ide cdrom, it will usually point to something like /dev/hdb (slave on primary port), /dev/hdc (master on secondary port) or /dev/hdd (slave on secondary port). You probably need to do something like cd /dev ln -s hdb cdrom as root. HTH, Eric -- E.L. Meijer ([EMAIL PROTECTED]) | tel. office +31 40 2472189 Eindhoven Univ. of Technology | tel. lab. +31 40 2475032 Lab. for Catalysis and Inorg. Chem. (TAK) | tel. fax+31 40 2455054
Re: cdrom device not there
On Fri, Oct 16, 1998 at 11:08:17AM +0100, G. Kapetanios wrote ... After reinstalling my system (hamm) from scratch I have no /dev/cdrom Is this obselete ? If yes then what is the name of the new device ? /dev/cdrom is just a link to another device. Is your CDROM Drive Atapi or SCSI ? If Atapi, and 1st controller, master: /dev/hda or 1st controller, slave: /dev/hdb (most cases) or 2nd controller, master: /dev/hdc or 2nd controller, slave: /dev/hdd Dominik. -- Dominik Rothert WWW: http://domix.rhein.com E-Mail: [EMAIL PROTECTED] GPG Fingerprint: BB8F 7348 18AE 565F 6ABA 453F A964 3160 B20A 5726 PGP Fingerprint: 70 1C 59 75 D8 30 65 3F FE 1E D8 B5 89 EA 4B 5A
re: umount:/cdrom: device is busy.
Hallo Alan, The same thing happened to me when I tried to unmount the cdrom while at the same time my default directory is /cdrom or one of its subdirectories. Make sure that you are in / when trying to unmount. Johann. This happens to me quite often: a floppy or a cd isn't being accessed, but I cannot unmount it: umount gives the error I have indicated. Is there any way to find out what process or which xterm might be accessing or sitting on a certain device? Thank you to all who have made my computing journey smoother. Alan -- Alan E. Davis Johann Spies [EMAIL PROTECTED] Windsorlaan 19 Pietermaritzburg 3201 Suid Afrika (South Africa) Tel/Faks Nr. +27 331-46-1310 -- TO UNSUBSCRIBE FROM THIS MAILING LIST: e-mail the word unsubscribe to [EMAIL PROTECTED] . Trouble? e-mail to [EMAIL PROTECTED] .
