#tail -f /var/log/messages
Feb 1 10:51:34 nb kernel: usb 2-1: New USB device found,
idVendor=1c6b, idProduct=a122
Feb 1 10:51:34 nb kernel: usb 2-1: New USB device strings: Mfr=1,
Product=2, SerialNumber=3
Feb 1 10:51:34 nb kernel: usb 2-1: Product: Mass Storage Device
Feb 1 10:51:34 nb kernel: usb 2-1: Manufacturer: USB2.0 External
Feb 1 10:51:34 nb kernel: usb 2-1: SerialNumber: 20091112000000005000
Feb 1 10:51:34 nb kernel: usb 2-1: configuration #1 chosen from 1
choice
Feb 1 10:51:34 nb kernel: scsi4 : SCSI emulation for USB Mass Storage
devices
Feb 1 10:51:40 nb kernel: scsi 4:0:0:0: CD-ROM ATAPI
eHAU424 A 7L1P PQ: 0 ANSI: 0
....and.....
#lsusb
Bus 001 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
Bus 002 Device 004: ID 1c6b:a122 Philips & Lite-ON Digital Solutions
Corporation
Bus 002 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
If I do this with a simple flash drive and use the same command:
#mount -t auto /dev/sda1 /mnt/key
.....it works perfectly. No variation of the above command works for
this USB DVD/CD unit, with or without media. Even booting OS from
cold with USB unit turned on yields no device designation. I always
get the same error:
mount: special device /dev/sda1 does not exist
....or whatever device I specify. Like I said, I did this b4, but
can't seem to do it now. What am I missing.
nb
Could it be assigning it to /dev/sr0?
--
Yow! Those people look exactly like Donnie and Marie Osmond!!
> mount: special device /dev/sda1 does not exist
The above error indicate a few mistakes:
1) /dev/sda1 is not a dvd/cd burner, /dev/sda is a hard disk and /dev/sda1
is the first partition. Usually you dont have paritions on CDs or DVDs.
2) To mount a CD/DVD with some existing contents you should probably
instead mount /dev/cdrom
3) If the CD/DVD does not contain anything yet you should probably not
mount it but instead fill it with something using a tool like k3b.
regards Henrik
--
The address in the header is only to prevent spam. My real address is:
hc123(at)poolhem.se Examples of addresses which go to spammers:
root@localhost postmaster@localhost
> I feel dumber'n a bag o' hammers for asking, but WTF!? I've done this
> before and now can't remember how. It's a Lite-On unit and I've used it
> on this 13.0 box before. ...
> #tail -f /var/log/messages
> Feb 1 10:51:34 nb kernel: usb 2-1: New USB device found,
> idVendor=1c6b, idProduct=a122
> Feb 1 10:51:34 nb kernel: usb 2-1: New USB device strings: Mfr=1,
> Product=2, SerialNumber=3
> Feb 1 10:51:34 nb kernel: usb 2-1: Product: Mass Storage Device
> Feb 1 10:51:34 nb kernel: usb 2-1: Manufacturer: USB2.0 External
> Feb 1 10:51:34 nb kernel: usb 2-1: SerialNumber: 20091112000000005000
> Feb 1 10:51:34 nb kernel: usb 2-1: configuration #1 chosen from 1
> choice
> Feb 1 10:51:34 nb kernel: scsi4 : SCSI emulation for USB Mass Storage
> devices
> Feb 1 10:51:40 nb kernel: scsi 4:0:0:0: CD-ROM ATAPI
> eHAU424 A 7L1P PQ: 0 ANSI: 0
> ...
> ... Even booting OS from cold with USB unit turned on yields no device
> designation. ...
> ...
> What am I missing.
Well, the answer to what are you missing, with respect to failed
attempts to mount the device, is indeed "device designation", it
looks like. The question, of course, is "why?"
Check for CONFIG_BLK_DEV_SR (SCSI CDROM support) in your kernel
configuration.
I hope this helps.
--
----------------------------------------------------------------------
Sylvain Robitaille s...@encs.concordia.ca
Systems analyst / AITS Concordia University
Faculty of Engineering and Computer Science Montreal, Quebec, Canada
----------------------------------------------------------------------
I've got one tracked down. If I use:
mount -t auto /dev/hdd /mnt/cdrom
.... or /dev/hdc, I get no device errors, now getting instead an:
mount: no medium found on /dev/hdd
....I've tried auto, msdos, vfat, iso9660 to no avail. umsdos does
not fly, either. The disk (dvd or cd?) is allegedly good for windows,
mac, and linux systems. I've also tried to mount these right after
closing player and while active LED is lit. Still nada.
I've also pulled all other USB chords and have tried both front and
back ports (connectors). I tried a burned known good iso9660. No
medium found. Now what?
nb
> Could it be assigning it to /dev/sr0?
I've never ever used /dev/sr0 for anything. Besides, tried that
variation, earlier, with no luck. ps | grep hald says it's polling
hdd, hdc, and sr0 every 2 secs and it seems to me I recall using
/dev/hdd in the past, though not positive. OTOH, /dev/hd[d,c] are the
only commands not giving me no device errors.
nb
For what it IS worth: usb connections respond with various
designations of connected devices.
So in/on my system I take the uncomfortably login as root - push a
memory stick in connection and call 'fdisk -l', the textual, OMG!,
answer gives me a device - mechanical HD and another one, usually in
sd* range.
This can be mounted in normal 'primitive' way, we are in Slackware
arn't we?
Good luck and have fun.
> I've never ever used /dev/sr0 for anything. Besides, tried that
> variation, earlier, with no luck. ps | grep hald says it's polling
> hdd, hdc, and sr0 every 2 secs and it seems to me I recall using
> /dev/hdd in the past, though not positive. OTOH, /dev/hd[d,c] are the
> only commands not giving me no device errors.
It wouldn't make sense for a USB CD/DVD drive to be /dev/hd${anything}
Just for reference, here's the dmesg output on my Slackware-13.0 system
when I connect a USB CD/DVD drive:
usb 1-6: new high speed USB device using ehci_hcd and address 21
usb 1-6: New USB device found, idVendor=1bcf, idProduct=0c31
usb 1-6: New USB device strings: Mfr=2, Product=3, SerialNumber=1
usb 1-6: Product: USB to Serial-ATA bridge
usb 1-6: Manufacturer: Sunplus Innovation Technology.
usb 1-6: SerialNumber: FFFFFFFE0D912260273814
usb 1-6: configuration #1 chosen from 1 choice
scsi16 : SCSI emulation for USB Mass Storage devices
usb-storage: device found at 21
usb-storage: waiting for device to settle before scanning
scsi 16:0:0:0: CD-ROM Slimtype DVD A DS8A4S JP55 PQ: 0 ANSI: 0
sr0: scsi3-mmc drive: 24x/8x writer dvd-ram cd/rw xa/form2 cdda tray
sr 16:0:0:0: Attached scsi CD-ROM sr0
sr 16:0:0:0: Attached scsi generic sg6 type 5
usb-storage: device scan complete
Notice "Attached scsi CD-ROM sr0". The resulting device symlink
confirms it:
: elvira[syl] ~; ls -l /dev/cdrom
lrwxrwxrwx 1 root system 3 2011-02-01 21:53 /dev/cdrom -> sr0
This would then mount as /dev/cdrom, of course. Does that help?
I am SylvainRobitaille(at)hotmail.com! (check the headers!)
I like to take it real hard up the ass. Especially while top-posting!
And while I am taking it real hard up the ass I am thinking about my
buddy http://lewpitcher.ca
(you know? The one with the famous picture?)
I am SylvainRobitaille(at)hotmail.com!
> On 2011-02-01, Henrik Carlqvist <Henrik.C...@deadspam.com> wrote:
>> 2) To mount a CD/DVD with some existing contents you should probably
>> instead mount /dev/cdrom
> I've got one tracked down. If I use:
>
> mount -t auto /dev/hdd /mnt/cdrom
>
> .... or /dev/hdc, I get no device errors, now getting instead an:
>
> mount: no medium found on /dev/hdd
Do you have some very good reason to try every device out there except
/dev/cdrom which on standard Slackware installations is a symbolic link
pointing you right to the correct device?
If you know why you don't want to use /dev/cdrom and explain this we might
be able to explain why you fail to mount your CD or DVD.
However, the fact that you get a "no medium foun" on /dev/hdd seems to
tell me that you have at least one built in CD/DVD reader in your
computer. If so, /dev/cdrom is probably a link to the built in device.
When you add yet another CDROM by USB that is probably not an IDE device
like hdd or hdc but will most likely emulate a SCSI device. The reader
will be named /dev/sr? and the writer will be named /dev/sg? where ? is a
number 0 and upwards.
Some other useful information might be the output from:
ls -al /dev/cdrom
ps -ef | grep udevd
zcat /proc/config.gz | grep DEV_SR
dmesg | grep ROM
Du meintest am 01.02.11:
> For what it IS worth: usb connections respond with various
> designations of connected devices.
> So in/on my system I take the uncomfortably login as root - push a
> memory stick in connection and call 'fdisk -l', the textual, OMG!,
> answer gives me a device - mechanical HD and another one, usually in
> sd* range.
> This can be mounted in normal 'primitive' way, we are in Slackware
> arn't we?
Just take a try - it should succeed.
"fdisk -l" also shows the size(s); that may be a good help.
Viele Gruesse
Helmut
"Ubuntu" - an African word, meaning "Slackware is too hard for me".
This device is seen as a CD-rom, not a harddisk, so the device name
should be something like /dev/sr0 (or 1, if you already got a built-in
CD-rom on S-ATA), not sda
Try mount /dev/sr0 /mnt/whatever
Most likely the filesystem is udf, but "-t auto" should find it.
> ....or whatever device I specify. Like I said, I did this b4, but
> can't seem to do it now. What am I missing.
The CD-ROM ATAPI message above?
--
******************************************************************
** Eef Hartman, Delft University of Technology, dept. SSC/ICT **
** e-mail: E.J.M....@tudelft.nl - phone: +31-15-27 82525 **
******************************************************************
Device names like hdc and hdd indicate a IDE CD-rom (or disk) drive
(that is: connected through a 40-pins flat cable), which is mostly
only for built-in drives, not "hot-pluggable" (i.e. USB) ones.
> /dev/hdd in the past, though not positive. OTOH, /dev/hd[d,c] are the
> only commands not giving me no device errors.
But they probably refer to your built-in CD-rom/writer cq DVD drives.
USB drives always use the SCSI (cq S-ATA) handling, that is: they
get device names starting with a s, like sd<letter> for disks cq
sr<digit> for CD-like drives.
>notbob <not...@notbob.invalid> wrote:
>> I've never ever used /dev/sr0 for anything. Besides, tried that
>> variation, earlier, with no luck. ps | grep hald says it's polling
>> hdd, hdc, and sr0 every 2 secs and it seems to me I recall using
>
>Device names like hdc and hdd indicate a IDE CD-rom (or disk) drive
>(that is: connected through a 40-pins flat cable), which is mostly
>only for built-in drives, not "hot-pluggable" (i.e. USB) ones.
>
>> /dev/hdd in the past, though not positive. OTOH, /dev/hd[d,c] are the
>> only commands not giving me no device errors.
>
>But they probably refer to your built-in CD-rom/writer cq DVD drives.
>
>USB drives always use the SCSI (cq S-ATA) handling, that is: they
>get device names starting with a s, like sd<letter> for disks cq
>sr<digit> for CD-like drives.
And adding to that you might have a UDF formatted CD? Is UDF support turned
on by default in Slack's kernel?
And I'll throw in my support of the /dev/sr? as the most likely place you'll
find a read-only CD or DVD. Unless you have a weird USB bridge for an
external drive in which case the thing will likely show as /dev/sd?
The old /dev/hd? are disappearing in favour of /dev/sd? or /dev/sr? for
internal drives as the new kernel 'libata' gets switched on for most
devices these days.
Another place to look is under /dev/disk/* -- from there there's four different
views of your visible drives, use whichever one suits your mindset and the
task at hand.
It's the place I look now when I 'lose' a drive :) Or if I need to know the
permanent name for a device so stop the thing jumping all over the place (for
example external hard drives on USB) because of drive detection order issues.
I recently reported an example of how to lock down an external drive to a
known mountpoint -- though of course there's likely a few more ways to do
that.
Grant.
Cliches of this wholly simplistic caliber are not allowed in this
newsgroup. Having said this, you might ask why cliches such as
SylRob...@gmail.com and Coward LewPitcher.ca (have you seen the
famous photo?) are allowed to post here. Rather than simply speak the
"cliche" language, these imbeciles are cliches in all of their
actions.
They are allowed to post because the eternal vigilance required to see
if they can come up with anything to say of any substance has not as
yet, in and of itself, become a cliche.
We shit hard and directly in the face of lewpitcher.ca. And we ground
that shit into every facial orifice with our boots.
And we do it again. And again.
cordially, as always,
Syl Robitaille @ gmail.com
> Check for CONFIG_BLK_DEV_SR (SCSI CDROM support) in your kernel
> configuration.
Actually, that should be CONFIG_SQU_BLK_4_RND_HOLE (SCSI FAGGT
support).
Hear that little squeal?
That's the sound of a LewPitcher.ca taking it hard.
cordially, as always,
Little Syl
SylRobitaille @ gmail . com