You are not logged in.
Hi,
I've installed Arch Linux 64-bit on my Dell workstation, and it doesn't seem to be picking up my USB storage drives. Kernel version is 3.6.3-1.
When I plug in a drive, I see in dmesg:
[391147.657574] usb 1-8: new high-speed USB device number 6 using ehci_hcdHowever, I don't see anything else. There's nothing about creating device nodes, or anything like that.
My output from `fstab -l` doesn't seem to mention anything about USB drives either, just my two system drives.
[victorhooi@arch-precision ~]$ sudo fdisk -l
[sudo] password for victorhooi:
WARNING: GPT (GUID Partition Table) detected on '/dev/sda'! The util fdisk doesn't support GPT. Use GNU Parted.
Disk /dev/sda: 80.0 GB, 80000000000 bytes, 156250000 sectors
Units = sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 512 bytes / 512 bytes
Disk identifier: 0x0f2d18e3
Device Boot Start End Blocks Id System
/dev/sda1 * 2048 718847 358400 7 HPFS/NTFS/exFAT
/dev/sda2 718848 156246015 77763584 7 HPFS/NTFS/exFAT
WARNING: GPT (GUID Partition Table) detected on '/dev/sdb'! The util fdisk doesn't support GPT. Use GNU Parted.
Disk /dev/sdb: 80.0 GB, 80000000000 bytes, 156250000 sectors
Units = sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 512 bytes / 512 bytes
Disk identifier: 0x3a9c7de5
Device Boot Start End Blocks Id System
/dev/sdb1 1 156249999 78124999+ ee GPTMy output from lsusb:
[victorhooi@arch-precision ~]$ lsusb
Bus 001 Device 006: ID 0930:6545 Toshiba Corp. Kingston DataTraveler 102 Flash Drive / HEMA Flash Drive 2 GB / PNY Attache 4GB Stick
Bus 002 Device 002: ID 413c:2003 Dell Computer Corp. Keyboard
Bus 002 Device 003: ID 04b3:310d IBM Corp.
Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
Bus 002 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
Bus 003 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
Bus 004 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
Bus 005 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hubOutput from blkid - both before and after inserting the drive is identical:
[victorhooi@arch-precision ~]$ blkid -o list -c /dev/null
device fs_type label mount point UUID
-------------------------------------------------------------------------------------------------------------------------------------------------
/dev/sda1 (not mounted)
/dev/sda2 (not mounted)
/dev/sdb1 /boot
/dev/sdb2 (not mounted)
/dev/sdb3 (not mounted)When I installed my kernel, I saw warnings about fsck.btrfs - not sure if that's related though:
>>> Generating initial ramdisk, using mkinitcpio. Please wait...
==> Building image from preset: 'default'
-> -k /boot/vmlinuz-linux -c /etc/mkinitcpio.conf -g /boot/initramfs-linux.img
==> Starting build: 3.6.5-1-ARCH
-> Running build hook: [base]
-> Running build hook: [udev]
-> Running build hook: [autodetect]
-> Running build hook: [pata]
-> Running build hook: [scsi]
-> Running build hook: [sata]
-> Running build hook: [filesystems]
-> Running build hook: [usbinput]
-> Running build hook: [fsck]
==> ERROR: file not found: `fsck.btrfs'
==> WARNING: No fsck helpers found. fsck will not be run on boot.
==> Generating module dependencies
==> Creating gzip initcpio image: /boot/initramfs-linux.img
==> WARNING: errors were encountered during the build. The image may not be complete.
==> Building image from preset: 'fallback'
-> -k /boot/vmlinuz-linux -c /etc/mkinitcpio.conf -g /boot/initramfs-linux-fallback.img -S autodetect
==> Starting build: 3.6.5-1-ARCH
-> Running build hook: [base]
-> Running build hook: [udev]
-> Running build hook: [pata]
-> Running build hook: [scsi]
-> Running build hook: [sata]
-> Running build hook: [filesystems]
-> Running build hook: [usbinput]
-> Running build hook: [fsck]
==> Generating module dependencies
==> Creating gzip initcpio image: /boot/initramfs-linux-fallback.img
==> Image generation successful
error: command failed to execute correctlyI checked the output from lsmod, I dont' see usb-storage, but I do see sd_mod.
Any thoughts?
Cheers,
Victor
Offline
Offline
There has been some kernel updates. Have you rebooted since updating kernels? Comapre your running kernel to the one installed currently by pacman. If they differ, reboot, or kexec that sh*t.
Offline
Offline
At least that is one of the very few times you have to reboot. MS just never actually ships you a new kernel. I have never been able to understand why I need to reboot my machine in windows when I install something like a word processor. What is it actually doing?
Edit: Don't forget to mark as solved!
Last edited by WonderWoofy (2012-11-03 15:25:18)
Offline
At least that is one of the very few times you have to reboot. MS just never actually ships you a new kernel. I have never been able to understand why I need to reboot my machine in windows when I install something like a word processor. What is it actually doing?
I have no idea, too. I usually don't reboot even after kernel update, because I always think "Oh, what the heck, I'll reboot it eventually anyway". As we can see, it's not always a good idea
.
Edit: Don't forget to mark as solved!
We have to wait for @victorhooi to confirm it
.
Offline