usb working on -current, but can't mount external drive

bl0tt0 · 05-02-2006, 07:51 PM

Ok, I'm a relatively new linux user, and completely new to Slackware, but learning more and more with it than I did in Debian and gentoo combined. A couple of months back I decided to upgrade from 10.2 to current in order to get a look at what was in the works for 11. Perhaps that was a mistake given my level of experience, but I'm taking the advice on this board to heart and religiously reading the changelog and progressively performing upgrades from a Slackware mirror in order to make sure that know what is broken when something goes wrong I know what did the damage.

The problem is that I've now discovered that I'm unable to mount external usb drives. It seems very strange to me because it appears that the usb ports on my machine are otherwise working fine. I use a usb mouse that gets picked up just fine both by gpm and xorg, and I can see in dmesg that the usb drive and its partitions are being assigned to /dev/sda[1,2,3,4], but when I type in

Code:

 mount -t reiserfs /dev/sda2 /mnt/usb

I get an error saying that the device is unassigned.

I'm running a customized 2.6.14 kernel, and this hasn't been a problem prior to this week, when I did an upgrade, so I assume that one of the packages that has been recently released is causing the issue. I'm really at a loss as to where to look for the solution, other than downgrading a package back to stable for now. I'm assuming that the new udev package, and possibly the hotplug package is the source of the problem, but I'd like to try and get things working with the newer package, but don't know what to do exactly. Any help appreciated.

Thanks

Brian1 · 05-02-2006, 07:58 PM

Post output of the command ' /sbin/fdisk -l '. It needs to be run as root. Just want to see what is seen.

Brian1

bl0tt0 · 05-02-2006, 08:21 PM

Alrighty:

Code:

Disk /dev/hda: 100.0 GB, 100030242816 bytes
255 heads, 63 sectors/track, 12161 cylinders
Units = cylinders of 16065 * 512 = 8225280 bytes

   Device Boot      Start         End      Blocks   Id  System
/dev/hda1               1        3916    31449568+   7  HPFS/NTFS
/dev/hda2   *        3916        3922       52920   83  Linux
/dev/hda3            3922       11552    61281360    f  W95 Ext'd (LBA)
/dev/hda4           11552       12161     4898880   12  Compaq diagnostics
/dev/hda5            3922        3988      523026+  82  Linux swap
/dev/hda6            3988       10897    55501128+  83  Linux
/dev/hda7           10897       11551     5256638   83  Linux

It doesn't seem like the usb drive is being seen at all, but then in dmesg, I get this:

Code:

usb-storage: device found at 3
usb-storage: waiting for device to settle before scanning
usbcore: registered new driver usb-storage
USB Mass Storage support registered.
ohci_hcd: 2005 April 22 USB 1.1 'Open' Host Controller (OHCI) Driver (PCI)
  Vendor: ST325082  Model: 3A                Rev:  0 0
  Type:   Direct-Access                      ANSI SCSI revision: 00
SCSI device sda: 488397168 512-byte hdwr sectors (250059 MB)
sda: assuming drive cache: write through
SCSI device sda: 488397168 512-byte hdwr sectors (250059 MB)
sda: assuming drive cache: write through
 sda: sda1 sda2 sda3 sda4
Attached scsi disk sda at scsi0, channel 0, id 0, lun 0
usb-storage: device scan complete

And just to provide the output of mount -t reiserfs /dev/sda2 /mnt/usb:

Code:

mount: special device /dev/sda2 does not exist

Brian1 · 05-02-2006, 08:51 PM

Post output of the command ' lsmod '. Probably missing a module like
sd_mod
scsi_mod
usb_storage

If any are missing use the commad ' modprobe usb_storage '. Then see what fdisk -l sees.

Brian1

bl0tt0 · 05-02-2006, 09:16 PM

here it is:

Code:

Module                  Size  Used by
ipv6                  264576  6
fglrx                 474720  7
snd_seq_oss            35072  0
snd_seq_midi_event      7168  1 snd_seq_oss
snd_seq                53008  4 snd_seq_oss,snd_seq_midi_event
snd_seq_device          8972  2 snd_seq_oss,snd_seq
snd_pcm_oss            54944  0
snd_mixer_oss          19968  1 snd_pcm_oss
ipt_state               2048  1
ip_conntrack           49168  1 ipt_state
iptable_filter          3072  1
ip_tables              20736  2 ipt_state,iptable_filter
ohci_hcd               21636  0
wlan_wep                6528  1
usb_storage            77248  0
intel_agp              23964  1
uhci_hcd               33296  0
ehci_hcd               35976  0
i2c_i801                8972  0
i2c_core               22288  1 i2c_i801
snd_intel8x0           34912  2
snd_ac97_codec         97660  1 snd_intel8x0
snd_ac97_bus            2432  1 snd_ac97_codec
snd_pcm                92552  4 snd_pcm_oss,snd_intel8x0,snd_ac97_codec
snd_timer              25348  3 snd_seq,snd_pcm
snd                    54500  11 snd_seq_oss,snd_seq,snd_seq_device,snd_pcm_oss,snd_mixer_oss,snd_intel8x0,snd_ac97_codec,snd_pcm,snd_timer
snd_page_alloc         11272  2 snd_intel8x0,snd_pcm
ath_pci                81692  0
ath_rate_sample        16904  1 ath_pci
wlan                  146844  4 wlan_wep,ath_pci,ath_rate_sample
ath_hal               148560  3 ath_pci,ath_rate_sample
pcmcia                 40228  4
firmware_class         10880  1 pcmcia
yenta_socket           28300  4
rsrc_nonstatic         14720  1 yenta_socket
pcmcia_core            42896  3 pcmcia,yenta_socket,rsrc_nonstatic
agpgart                36168  2 fglrx,intel_agp

usb_storage shows up, but I think that those other modules you referred to are compiled into the kernel. Also, I realize that I shouldn't have ohci in there at all, but like I said, it seemed to work fine before.

I did try rmmod usb_storage and then modprobe usb_storage, but that was a no go too.

-=Graz=- · 05-03-2006, 04:43 AM

what happens if you plug the flash drive in and type #tail /var/log/messages - It may indicate what is happening (or not for that matter)

being that your mouse and stuff works i might be totally off track but i think you need the USBCore module loaded?i notice you have PCMCIAcore

my output of lsmod:
ohci_hcd 16196 0
uhci_hcd 26768 0
ehci_hcd 24520 0
usbcore 100676 5 usb_storage,ohci_hcd,uhci_hcd,ehci_hcd

note: usb storage automatically loads on insertion of the memory device.

my /var/log/messages:

Slack700m kernel: usb 1-5: new high speed USB device using ehci_hcd and address 4
Slack700m kernel: scsi2 : SCSI emulation for USB Mass Storage devices
Slack700m udev[5609]: creating device node '/dev/usbdev1.4'
Slack700m kernel: Vendor: SanDisk Model: Cruzer Titanium Rev: 2000
Slack700m kernel: Type: Direct-Access ANSI SCSI revision: 00
Slack700m kernel: SCSI device sda: 1014784 512-byte hdwr sectors (520 MB)
Slack700m kernel: sda: Write Protect is off
Slack700m udev[5675]: creating device node '/dev/sda'
Slack700m udev[5677]: configured rule in '/etc/udev/rules.d/udev.rules' at line 24 applied, 'sg0' becomes '%k'
Slack700m udev[5677]: creating device node '/dev/sg0'
Slack700m udev[5678]: creating device node '/dev/sda1'
Slack700m kernel: sda: sda1
Slack700m kernel: sd 2:0:0:0: Attached scsi removable disk sda
Slack700m kernel: sd 2:0:0:0: Attached scsi generic sg0 type 0

Brian1 · 05-03-2006, 04:40 PM

ohci-hcd is for USB controllers 1.0-1.1 version. Other 1.0-1.1 may use uhci-hcd. All 2.0 use ehci-hcd. If you ports on front and some on back then try the other ports. I have seen dells use both and front or back will be ehci-hcd.

Brian1

bl0tt0 · 05-04-2006, 11:51 PM

Ok, sorry for not responding sooner. I definitely have usbcore compiled into the kernel. I'm also aware that I don't need ohci modules built, and I plan to fix that on a later kernel upgrade, but like I said, it never seemed to get in the way before.

On another note, the problem I was having is definitely something with the udev package in the -current branch of Slackware. I reinstalled the udev package from 10.2, and everything seems to be working fine again. I think I might have seen another thread on this way way back, but I assumed it was something that had already been addressed. I guess I'll just wait until 11 is released before upgrading that specific bit.

Thanks anyways

Brian1 · 05-05-2006, 02:55 PM

Glad to see you have it going. Udev can be a pain.

Brian1

-=Graz=- · 05-06-2006, 04:55 AM

yes i think a lot of the problems i have seen re: USB flash devices have looked to relate to udev.. some machines udev does not seem to kick in an apply its rules.... interesting