LinuxQuestions.org

LinuxQuestions.org (/questions/)
-   Slackware (https://www.linuxquestions.org/questions/slackware-14/)
-   -   Can't mount usb flash disk? (https://www.linuxquestions.org/questions/slackware-14/cant-mount-usb-flash-disk-554537/)

ak-87 05-17-2007 01:55 AM
Can't mount usb flash disk?
 
It's Slackware 11 with custom 2.6.21.1 kernel. My udev is hanging up my system, so I turned it off. I managed to mount usb flash disk for the first time with next command:

Code:
#mount -t vfat /dev/sdb1 /mnt/flash
After that I can't mount it anymore. As I wrote my udev is making problems, so I'm loading usb-storage and ehci-hcd modules on boot. When I type same command, this is what I get:

Code:
#mount -t vfat /dev/sdb1 /mnt/flash
mount: special device /dev/sdb1 does not exist
I checked /dev but there is no sdb1 node, although my dmesg shows this:

Code:
Initializing USB Mass Storage driver...
scsi5 : SCSI emulation for USB Mass Storage devices
usbcore: registered new interface driver usb-storage
USB Mass Storage support registered.
usb-storage: device found at 2
usb-storage: waiting for device to settle before scanning
scsi 5:0:0:0: Direct-Access    JetFlash TS1GJF130        8.07 PQ: 0 ANSI: 2
SCSI device sdb: 2007038 512-byte hdwr sectors (1028 MB)
sdb: Write Protect is off
sdb: Mode Sense: 03 00 00 00
sdb: assuming drive cache: write through
SCSI device sdb: 2007038 512-byte hdwr sectors (1028 MB)
sdb: Write Protect is off
sdb: Mode Sense: 03 00 00 00
sdb: assuming drive cache: write through
 sdb: sdb1
sd 5:0:0:0: Attached scsi removable disk sdb
sd 5:0:0:0: Attached scsi generic sg1 type 0
usb-storage: device scan complete
Also lsusb output:

Code:
Bus 001 Device 002: ID 058f:6387 Alcor Micro Corp.
Bus 001 Device 001: ID 0000:0000
Bus 005 Device 001: ID 0000:0000
Bus 004 Device 003: ID 05e3:1205 Genesys Logic, Inc. Afilias Optical Mouse H3003
Bus 004 Device 001: ID 0000:0000
Bus 003 Device 001: ID 0000:0000
Bus 002 Device 001: ID 0000:0000
As I said I mounted it for the first time in exactly same way, but now it is not working. Any ideas?

Alien_Hominid 05-17-2007 03:04 AM
I don't know. It should work manually. What version of usb controller do you have (1.0, 1.1, 2.0). If lower than 2.0 try uhci/ohci instead.

Try activating hotplug. Maybe it will find something.

ak-87 05-17-2007 03:16 AM
Hotplug also hangs system. I've upgraded udev with package from Slackware-current and it works now just fine. Now I can mount usb flash without any problems.

Thanks anyway!:)

Alien_Hominid 05-17-2007 03:27 AM
But it should work manually. Udev is not a magic. But that's ok if you have it working.

ak-87 05-17-2007 03:52 AM
I don't want to open new topic, but after upgrading udev I get next messages on boot:

Code:
/ect/rc.d/rc.M: line 93: /dev/.udev/failed/devices@pci0000:00@0000:00:00.0/uevent: Not a directory
/ect/rc.d/rc.M: line 93: /dev/.udev/failed/devices@pci0000:00@0000:00:01.0/uevent: Not a directory
/ect/rc.d/rc.M: line 93: /dev/.udev/failed/devices@pci0000:00@0000:00:01.1/uevent: Not a directory
/ect/rc.d/rc.M: line 93: /dev/.udev/failed/devices@pci0000:00@0000:00:01.1@ide0@0.0/uevent: Not a directory
/ect/rc.d/rc.M: line 93: /dev/.udev/failed/devices@pci0000:00@0000:00:01.1@ide1@1.0/uevent: Not a directory
/ect/rc.d/rc.M: line 93: /dev/.udev/failed/devices@pci0000:00@0000:00:02.0/uevent: Not a directory
/ect/rc.d/rc.M: line 93: /dev/.udev/failed/devices@pci0000:00@0000:00:03.0/uevent: Not a directory
/ect/rc.d/rc.M: line 93: /dev/.udev/failed/devices@pci0000:00@0000:00:04.0/uevent: Not a directory
/ect/rc.d/rc.M: line 93: /dev/.udev/failed/devices@pci0000:00@0000:00:06.0@usb1@1-0:1.0/uevent: Not a directory
/ect/rc.d/rc.M: line 93: /dev/.udev/failed/devices@platform@floppy.0/uevent: Not a directory
/ect/rc.d/rc.M: line 93: /dev/.udev/failed/devices@platform@i8042/uevent: Not a directory
/ect/rc.d/rc.M: line 93: /dev/.udev/failed/devices@platform@i8042@serio0/uevent: Not a directory
/ect/rc.d/rc.M: line 93: /dev/.udev/failed/devices@platform@pcspkr/uevent: Not a directory
/ect/rc.d/rc.M: line 93: /dev/.udev/failed/devices@platform@serial8250/uevent: Not a directory
/ect/rc.d/rc.M: line 93: /dev/.udev/failed/devices@platform@vesafb.0/uevent: Not a directory
???

Alien_Hominid 05-17-2007 03:57 AM
It's a chance that you will need to upgrade more packages. Maybe something is said in changelog.

H_TeXMeX_H 05-17-2007 11:39 AM
udev and hotplug should not be hanging your system. I think you may have made a mistake when compiling the kernel. Try the kernel compile guide and slackbook (in my sig).

How did you compile it ?

ak-87 05-17-2007 12:25 PM
Quote:
Originally Posted by H_TeXMeX_H
udev and hotplug should not be hanging your system. I think you may have made a mistake when compiling the kernel. Try the kernel compile guide and slackbook (in my sig).

How did you compile it ?
Udev and hotplug hanged my system (it is Toshiba Satellite A100-153; check this link's Installation section http://home.comcast.net/~fbui/Linux-on-ToshibaA105.html) before custom kernel (on test26.s - 2.6.18), so I don't think that custom kernel is problem. Right now udev, after upgrade from Slackware-current, is working fine (except those error messages on boot, above) and hotplug service is off.

I compiled my custom kernel like this:

#make mrproper
#make xconfig
#make bzImage && make modules && make modules_install
#cp arch/i386/boot/bzImage /boot/vmlinuz-2.6.21
#cp System.map /boot/System.map-2.6.21
#ln -s /boot/vmlinuz-2.6.21 /boot/vmlinuz
#ln -s /boot/System.map-2.6.21 /boot/System.map
#lilo
#reboot

H_TeXMeX_H 05-17-2007 12:57 PM
Oh, I see. Then I'm not sure. Maybe try upgrading to Slackware -current.

ak-87 05-17-2007 01:30 PM
I would love to, but I am still using dial-up.:cry:

rworkman 05-17-2007 04:00 PM
The udev package from -current expects different rule syntax and different location of starting udevd in the init scripts. If you're going to use packages from -current, you need to do a full upgrade to -current.
As to why it's not working on 11.0 with stock 11.0 udev package, it's likely a kernel config problem. Reproduce the issue with the stock 2.6.17.13 kernel from /extra on 11.0 and we'll go from there.

ak-87 05-18-2007 03:39 AM
Quote:
Originally Posted by rworkman
The udev package from -current expects different rule syntax and different location of starting udevd in the init scripts. If you're going to use packages from -current, you need to do a full upgrade to -current.
As to why it's not working on 11.0 with stock 11.0 udev package, it's likely a kernel config problem. Reproduce the issue with the stock 2.6.17.13 kernel from /extra on 11.0 and we'll go from there.
This is what happens with stock 11.0 kernel and udev package on boot:
Code:
cs: IO port probe 0xc00-0xcff : clean
cs: IO port probe 0x820-0x8ff : clean
cs: IO port probe 0x800-0x80f  <-- hangs on this line

H_TeXMeX_H 05-18-2007 12:15 PM
Maybe try this:
http://www.linuxquestions.org/questi...=IO+port+probe

Blacklist 'ahci' or remove it from kernel.

bassmadrigal 05-19-2007 05:42 AM
do

Code:
ls -la /dev/sd*
and paste the output.

It could be udev is assigning it a different device name. My usb drive changes occasionally.


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