Mounting USB pendrive in Zenwalk

POW R TOC H · 08-27-2008, 06:49 AM

I have this Kingston DataTraveler-Reader pendrive, which supports an additional MicroSD card (which is put directly in the pendrive). However, I want to use it without the microSD (so it should behave as a regular mass storage device).

Anyway, I put the pendrive in, and nothing happens, it doesn't mount. dmesg gives me this :

Code:

scsi 8:0:0:1: Direct-Access     USB2.0   KINGSTON   SD1   0500 PQ: 0 ANSI: 0
sd 8:0:0:1: [sdc] 2012160 512-byte hardware sectors (1030 MB)
sd 8:0:0:1: [sdc] Write Protect is off
sd 8:0:0:1: [sdc] Mode Sense: 03 00 00 00
sd 8:0:0:1: [sdc] Assuming drive cache: write through
sd 8:0:0:1: [sdc] 2012160 512-byte hardware sectors (1030 MB)
sd 8:0:0:1: [sdc] Write Protect is off
sd 8:0:0:1: [sdc] Mode Sense: 03 00 00 00
sd 8:0:0:1: [sdc] Assuming drive cache: write through
 sdc: sdc1
sd 8:0:0:1: [sdc] Attached SCSI removable disk
sd 8:0:0:1: Attached scsi generic sg3 type 0
usb-storage: device scan complete

I thought it I could find it as /dev/sdc# and mount it, but /dev/sdc doesn't exist :O

Any pointers would be appreciated. Also, I would be grateful if somebody would tell me what /dev/sg0 and /dev/sr0 are.
Thanks in advance

matthewg42 · 08-27-2008, 07:26 AM

Does Zenwalk use udev? If not, you might have to generate the device node with mknod, although it seems very strange to me that this is not already done by the distribution makers.

POW R TOC H · 08-27-2008, 07:36 AM

Quote:

Originally Posted by matthewg42

Does Zenwalk use udev? If not, you might have to generate the device node with mknod, although it seems very strange to me that this is not already done by the distribution makers.

It does. But I'm a newbie to linux, so... What now

?

matthewg42 · 08-27-2008, 07:40 AM

I don't know then. That is mysterious to me. I thought that udev was supposed to automatically generate nodes in /dev/ when a new device is detected. That's how it works in Ubuntu anyway.

POW R TOC H · 08-27-2008, 07:46 AM

Quote:

Originally Posted by matthewg42

I don't know then. That is mysterious to me. I thought that udev was supposed to automatically generate nodes in /dev/ when a new device is detected. That's how it works in Ubuntu anyway.

I'll try

Code:

ls /dev > ~/devc1
#Then I plugin the USB, and wait for a few seconds
ls /dev > ~/devc2
diff ~/devc1 ~/devc2

If there is any difference, it should be my USB...
I hope...

Edit :
the /dev directory didn't change at all... My USB device didn't register at all, it seems

matthewg42 · 08-27-2008, 08:11 AM

I would guess that it's one of the following:

some sort udev configuration which prevents creation of some sorts of device nodes
that the kernel does not support the device which you have connected
that there is a bug in the zenwalk distribution

ernst · 08-27-2008, 08:15 AM

> I thought it I could find it as /dev/sdc# and mount it, but /dev/sdc doesn't exist :O

Shouldn't you try to mount /dev/sdc1 ?

Ernst

POW R TOC H · 08-27-2008, 08:15 AM

Quote:

Originally Posted by matthewg42

I would guess that it's one of the following:

some sort udev configuration which prevents creation of some sorts of device nodes
that the kernel does not support the device which you have connected
that there is a bug in the zenwalk distribution

I see. I'll try asking at zenwalk forums. Thanks.

jschiwal · 08-27-2008, 08:51 AM

Monitor /var/log/messages with "sudo tail -f /var/log/messages" and plug in the pendrive. Look for a message about which device is used. A removable device might use /dev/sdd1 or /dev/sde1 the next time you plug it in.

A quick thing to do is simply to list the devices:
ls /dev/sd*

One thing to check is that you don't have the "noacpi" kernel boot option. Look in your lilo.conf or /boot/grub/menu.lst file. Check the line that looks like this:
kernel /boot/vmlinuz-2.6.25.11-0.1-default root=/dev/disk/by-id/scsi-SATA_TOSHIBA_MK2049G_48CYT01OT-part6 resume=/dev/sda5 splash=silent showopts vga=0x317

If the noacpi option is on this line, then the hald and dbusd daemons won't run. They are used by udev do udev won't work if these daemons aren't running.

POW R TOC H · 08-28-2008, 09:26 AM

Quote:

Originally Posted by jschiwal

Monitor /var/log/messages with "sudo tail -f /var/log/messages" and plug in the pendrive. Look for a message about which device is used. A removable device might use /dev/sdd1 or /dev/sde1 the next time you plug it in.

A quick thing to do is simply to list the devices:
ls /dev/sd*

One thing to check is that you don't have the "noacpi" kernel boot option. Look in your lilo.conf or /boot/grub/menu.lst file. Check the line that looks like this:
kernel /boot/vmlinuz-2.6.25.11-0.1-default root=/dev/disk/by-id/scsi-SATA_TOSHIBA_MK2049G_48CYT01OT-part6 resume=/dev/sda5 splash=silent showopts vga=0x317

If the noacpi option is on this line, then the hald and dbusd daemons won't run. They are used by udev do udev won't work if these daemons aren't running.

Read up, I did all of that

An no, I don't have noacpi option. I had to write my own configuration for grub, because Zenwalk uses lilo, and I wanted to dual boot with GRUB. Plus, I like grub's name. Lilo sounds like a cheap street whore. With all respect to those who wrote it, of course

Anyway, since I've rebooted, the problem dissapeared for some reason. Now it works. Thanks to you all for help!