Red HatThis forum is for the discussion of Red Hat Linux.
Notices
Welcome to LinuxQuestions.org, a friendly and active Linux Community.
You are currently viewing LQ as a guest. By joining our community you will have the ability to post topics, receive our newsletter, use the advanced search, subscribe to threads and access many other special features. Registration is quick, simple and absolutely free. Join our community today!
Note that registered members see fewer ads, and ContentLink is completely disabled once you log in.
If you have any problems with the registration process or your account login, please contact us. If you need to reset your password, click here.
Having a problem logging in? Please visit this page to clear all LQ-related cookies.
Get a virtual cloud desktop with the Linux distro that you want in less than five minutes with Shells! With over 10 pre-installed distros to choose from, the worry-free installation life is here! Whether you are a digital nomad or just looking for flexibility, Shells can put your Linux machine on the device that you want to use.
Exclusive for LQ members, get up to 45% off per month. Click here for more info.
I am running CentOS 6.6 [2.6.32-504.30.3.el6.x86_64]
We built a similar machine and the USB port was working fine but I do not have access to it at the moment.
See below the USB device is visible from dmesg and lsusb but does not show in fdisk -l so I am not able to mount it?
Tried two different USB sticks same result. Both formatted FAT32 and have had windows disk scanner run over them no problems.
Can any one please give me some pointers as to where I could look next?
Code:
[root]# dmesg
usb 3-4: USB disconnect, device number 31
usb 3-10: new high speed USB device number 39 using xhci_hcd
usb 3-10: New USB device found, idVendor=0930, idProduct=1400
usb 3-10: New USB device strings: Mfr=1, Product=2, SerialNumber=3
usb 3-10: Product: TOSHIBA USB DRV
usb 3-10: Manufacturer: TOSHIBA
usb 3-10: SerialNumber: 070839B0CA1C4C62
usb 3-10: configuration #1 chosen from 1 choice
Code:
[root]# lsusb
Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
Bus 002 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
Bus 003 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
Bus 004 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
Bus 001 Device 002: ID 8087:8008 Intel Corp.
Bus 002 Device 002: ID 8087:8000 Intel Corp.
Bus 003 Device 044: ID 17ef:6019 Lenovo
Bus 003 Device 039: ID 0930:1400 Toshiba Corp. Memory Stick 2GB
Bus 001 Device 003: ID 0624:0248 Avocent Corp. Virtual Hub
Bus 001 Device 005: ID 04b3:4010 IBM Corp.
Code:
#
#
# /etc/fstab
# Created by anaconda on Wed Apr 29 10:47:48 2015
#
# Accessible filesystems, by reference, are maintained under '/dev/disk'
# See man pages fstab(5), findfs(8), mount(8) and/or blkid(8) for more info
#
/dev/mapper/vg_wik2-lv_root / ext4 defaults 1 1
/dev/mapper/vg_wik2-lv_data /DATA ext4 defaults 1 2
UUID=4b8971ef-4572-486b-b532-62603a638913 /boot ext4 defaults 1 2
/dev/mapper/vg_wik2-lv_home /home ext4 defaults 1 2
/dev/mapper/vg_wik2-lv_tmp /tmp ext4 defaults 1 2
/dev/mapper/vg_wik2-lv_var /var ext4 defaults 1 2
/dev/mapper/vg_wik2-lv_varlog /var/log ext4 defaults 1 2
/dev/mapper/vg_wik2-lv_varlogaudit /var/log/audit ext4 defaults 1 2
/dev/mapper/vg_wik2-lv_swap swap swap defaults 0 0
tmpfs /dev/shm tmpfs defaults,noexec 0 0
devpts /dev/pts devpts gid=5,mode=620,noexec 0 0
sysfs /sys sysfs defaults,noexec 0 0
proc /proc proc defaults,noexec 0 0
/dev/cdrom /mnt/cdrom auto ro,noauto,nouser,exec,noexec 1 2
/dev/fd0 /mnt/floppy auto rw,noauto,nouser,sync,noexec 1 2
/dev/sda1 /mnt/usb1 auto rw,user,noauto 0 0
Code:
[root]# fdisk -l
Disk /dev/sda: 1000.2 GB, 1000204886016 bytes
255 heads, 63 sectors/track, 121601 cylinders
Units = cylinders of 16065 * 512 = 8225280 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 512 bytes / 512 bytes
Disk identifier: 0x00022a58
Device Boot Start End Blocks Id System
/dev/sda1 * 1 64 512000 83 Linux
Partition 1 does not end on cylinder boundary.
/dev/sda2 64 121455 975072256 8e Linux LVM
Disk /dev/sdb: 1000.2 GB, 1000204886016 bytes
255 heads, 63 sectors/track, 121601 cylinders
Units = cylinders of 16065 * 512 = 8225280 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 512 bytes / 512 bytes
Disk identifier: 0x00022a58
Device Boot Start End Blocks Id System
/dev/sdb1 * 1 64 512000 83 Linux
Partition 1 does not end on cylinder boundary.
/dev/sdb2 64 121455 975072256 8e Linux LVM
Disk /dev/mapper/ddf1_Bartco: 999.0 GB, 998999326720 bytes
255 heads, 63 sectors/track, 121454 cylinders
Units = cylinders of 16065 * 512 = 8225280 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 512 bytes / 512 bytes
Disk identifier: 0x00022a58
Device Boot Start End Blocks Id System
/dev/mapper/ddf1_Bartcop1 * 1 64 512000 83 Linux
Partition 1 does not end on cylinder boundary.
/dev/mapper/ddf1_Bartcop2 64 121455 975072256 8e Linux LVM
Disk /dev/mapper/ddf1_Bartcop1: 524 MB, 524288000 bytes
255 heads, 63 sectors/track, 63 cylinders
Units = cylinders of 16065 * 512 = 8225280 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 512 bytes / 512 bytes
Disk identifier: 0x00000000
Disk /dev/mapper/ddf1_Bartcop2: 998.5 GB, 998473990144 bytes
255 heads, 63 sectors/track, 121390 cylinders
Units = cylinders of 16065 * 512 = 8225280 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 512 bytes / 512 bytes
Disk identifier: 0x00000000
Disk /dev/mapper/vg_wag2-lv_root: 53.7 GB, 53687091200 bytes
255 heads, 63 sectors/track, 6527 cylinders
Units = cylinders of 16065 * 512 = 8225280 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 512 bytes / 512 bytes
Disk identifier: 0x00000000
Disk /dev/mapper/vg_wag2-lv_swap: 16.8 GB, 16819159040 bytes
255 heads, 63 sectors/track, 2044 cylinders
Units = cylinders of 16065 * 512 = 8225280 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 512 bytes / 512 bytes
Disk identifier: 0x00000000
Disk /dev/mapper/vg_wag2-lv_varlogaudit: 10.5 GB, 10485760000 bytes
255 heads, 63 sectors/track, 1274 cylinders
Units = cylinders of 16065 * 512 = 8225280 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 512 bytes / 512 bytes
Disk identifier: 0x00000000
Disk /dev/mapper/vg_wag2-lv_data: 865.1 GB, 865050034176 bytes
255 heads, 63 sectors/track, 105169 cylinders
Units = cylinders of 16065 * 512 = 8225280 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 512 bytes / 512 bytes
Disk identifier: 0x00000000
Disk /dev/mapper/vg_wag2-lv_var: 10.5 GB, 10485760000 bytes
255 heads, 63 sectors/track, 1274 cylinders
Units = cylinders of 16065 * 512 = 8225280 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 512 bytes / 512 bytes
Disk identifier: 0x00000000
Disk /dev/mapper/vg_wag2-lv_home: 21.0 GB, 20971520000 bytes
255 heads, 63 sectors/track, 2549 cylinders
Units = cylinders of 16065 * 512 = 8225280 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 512 bytes / 512 bytes
Disk identifier: 0x00000000
Disk /dev/mapper/vg_wag2-lv_tmp: 10.5 GB, 10485760000 bytes
255 heads, 63 sectors/track, 1274 cylinders
Units = cylinders of 16065 * 512 = 8225280 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 512 bytes / 512 bytes
Disk identifier: 0x00000000
Disk /dev/mapper/vg_wag2-lv_varlog: 10.5 GB, 10485760000 bytes
255 heads, 63 sectors/track, 1274 cylinders
Units = cylinders of 16065 * 512 = 8225280 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 512 bytes / 512 bytes
Disk identifier: 0x00000000
Looking at the output I see that you have /dev/sda and /dev/sdb.
The usb that is not showing up I'm thinking would be sdc.
To mount it try:
Code:
sudo mount /dev/sdc /mnt
If that doesn't work than maybe the module for usb storage isn't loading?
Code:
modprobe usb-storage
A few months ago my CentOS box didn't see my usb devices either. But I had an error message and looking up that error helped me find a small library to install to help the usb devices to be recognized.
In the dmesg output following the lines you posted, is there anything that says "USB Mass Storage device detected"? It appears that the device is not being so recognized. Here's what I see from dmesg on CentOS 6.7 when I plug in a USB flash drive:
Code:
usb 3-2: new high-speed USB device number 8 using xhci_hcd
usb 3-2: New USB device found, idVendor=1307, idProduct=0165
usb 3-2: New USB device strings: Mfr=1, Product=2, SerialNumber=3
usb 3-2: Product: USB Flash Drive
usb 3-2: Manufacturer: USB 2.0
usb 3-2: SerialNumber: a59730a27fe219
usb-storage 3-2:1.0: USB Mass Storage device detected
scsi host9: usb-storage 3-2:1.0
scsi 9:0:0:0: Direct-Access USB 2.0 USB Flash Drive 0.00 PQ: 0 ANSI: 2
sd 9:0:0:0: Attached scsi generic sg5 type 0
sd 9:0:0:0: [sde] 7897088 512-byte logical blocks: (4.04 GB/3.76 GiB)
sd 9:0:0:0: [sde] Write Protect is off
sd 9:0:0:0: [sde] Mode Sense: 00 00 00 00
sd 9:0:0:0: [sde] Asking for cache data failed
sd 9:0:0:0: [sde] Assuming drive cache: write through
sde: sde1 sde2
sd 9:0:0:0: [sde] Attached SCSI removable disk
Thank you all for your comments. Please see below.
@rknichols : Sorry no dice.. DMESG stops at Configuration #1 chosen from 1....
Code:
usb 3-2: new high speed USB device number 5 using xhci_hcd
usb 3-2: New USB device found, idVendor=0930, idProduct=1400
usb 3-2: New USB device strings: Mfr=1, Product=2, SerialNumber=3
usb 3-2: Product: TOSHIBA USB DRV
usb 3-2: Manufacturer: TOSHIBA
usb 3-2: SerialNumber: 070839B0CA1C4C62
usb 3-2: configuration #1 chosen from 1 choice
@Ztcoracat : I will try the kernel roll back and let you know if that works.
@jefro : Yes Toshiba is the memory stick. I am root, and have # setenforce Permissive
@Ztcoracat : I can not mount that device as it does not exist. But I did try.
I get the same two drives in /sys/block/sd* but no USB device.
When monitoring as I insert the device I get.
Code:
[root ~]# udevadm monitor
monitor will print the received events for:
UDEV - the event which udev sends out after rule processing
KERNEL - the kernel uevent
KERNEL[1439371625.946975] add /devices/pci0000:00/0000:00:14.0/usb3/3-2 (us b)
KERNEL[1439371625.947245] add /devices/pci0000:00/0000:00:14.0/usb3/3-2/3-2 :1.0 (usb)
UDEV [1439371625.955765] add /devices/pci0000:00/0000:00:14.0/usb3/3-2 (us b)
UDEV [1439371625.965629] add /devices/pci0000:00/0000:00:14.0/usb3/3-2/3-2 :1.0 (usb)
But I already knew that worked because of the DMESG output from earlier.
Device Boot Start End Blocks Id System
/dev/sdc1 * 2 8067 7561472 b W95 FAT32
and I am able to mount the device and read the file system.
dmesg is strange because it shows remounting the mouse at the same time even though I did not touch that?
Code:
usb 3-2: new high speed USB device number 11 using xhci_hcd
usb 3-2: New USB device found, idVendor=0930, idProduct=1400
usb 3-2: New USB device strings: Mfr=1, Product=2, SerialNumber=3
usb 3-2: Product: TOSHIBA USB DRV
usb 3-2: Manufacturer: TOSHIBA
usb 3-2: SerialNumber: 070839B0CA1C4C62
usb 3-2: configuration #1 chosen from 1 choice
scsi8 : SCSI emulation for USB Mass Storage devices
usb-storage: device found at 11
usb-storage: waiting for device to settle before scanning
usb-storage: device scan complete
scsi 8:0:0:0: Direct-Access TOSHIBA TOSHIBA USB DRV PMAP PQ: 0 ANSI: 4
sd 8:0:0:0: Attached scsi generic sg2 type 0
sd 8:0:0:0: [sdc] 15124992 512-byte logical blocks: (7.74 GB/7.21 GiB)
sd 8:0:0:0: [sdc] Write Protect is off
sd 8:0:0:0: [sdc] Mode Sense: 23 00 00 00
sd 8:0:0:0: [sdc] Assuming drive cache: write through
sd 8:0:0:0: [sdc] Assuming drive cache: write through
sdc: sdc1
sd 8:0:0:0: [sdc] Assuming drive cache: write through
sd 8:0:0:0: [sdc] Attached SCSI removable disk
usb 3-4: USB disconnect, device number 10
usb 3-4: new low speed USB device number 12 using xhci_hcd
usb 3-4: New USB device found, idVendor=17ef, idProduct=6019
usb 3-4: New USB device strings: Mfr=1, Product=2, SerialNumber=0
usb 3-4: Product: Lenovo USB Optical Mouse
usb 3-4: Manufacturer: PixArt
usb 3-4: configuration #1 chosen from 1 choice
usb 3-4: ep 0x81 - rounding interval to 64 microframes, ep desc says 80 microframes
input: PixArt Lenovo USB Optical Mouse as /devices/pci0000:00/0000:00:14.0/usb3/3-4/3-4:1.0/input/input10
generic-usb 0003:17EF:6019.0009: input,hidraw2: USB HID v1.11 Mouse [PixArt Lenovo USB Optical Mouse] on usb-0000:00:14.0-4/input0
Yes, that is bad. Something about that kernel installation is broken. Does /lib/modules/2.6.32-504.30.3.el6.x86_64/kernel/drivers/usb/storage/usb-storage.ko exist?
[root@WIK2 modules]# ls -l /lib/modules/2.6.32-504.el6.x86_64/kernel/drivers/usb/storage/
total 316
-rwxr--r--. 1 root root 20008 Oct 15 2014 ums-alauda.ko
-rwxr--r--. 1 root root 9000 Oct 15 2014 ums-cypress.ko
-rwxr--r--. 1 root root 15600 Oct 15 2014 ums-datafab.ko
-rwxr--r--. 1 root root 9280 Oct 15 2014 ums-freecom.ko
-rwxr--r--. 1 root root 16448 Oct 15 2014 ums-isd200.ko
-rwxr--r--. 1 root root 12632 Oct 15 2014 ums-jumpshot.ko
-rwxr--r--. 1 root root 9304 Oct 15 2014 ums-karma.ko
-rwxr--r--. 1 root root 12704 Oct 15 2014 ums-onetouch.ko
-rwxr--r--. 1 root root 22984 Oct 15 2014 ums-sddr09.ko
-rwxr--r--. 1 root root 19048 Oct 15 2014 ums-sddr55.ko
-rwxr--r--. 1 root root 18944 Oct 15 2014 ums-usbat.ko
-rwxr--r--. 1 root root 127296 Oct 15 2014 usb-storage.ko
Quote:
Originally Posted by rknichols
Yes, that is bad. Something about that kernel installation is broken. Does /lib/modules/2.6.32-504.30.3.el6.x86_64/kernel/drivers/usb/storage/usb-storage.ko exist?
OK Thanks all for your assistance, but that was one wild goose chase.
I had also been running OpenSCAP auto remediation to profile stig-rhel6-server-upstream.
One fix is to disable loading of usb-storage ..
PieFace!
Quote:
Result for Disable Modprobe Loading of USB Storage Driver
Result: pass
Rule ID: kernel_module_usb-storage_disabled
Time: 2015-08-13 18:25
Severity: low
To prevent USB storage devices from being used, configure the kernel module loading system to prevent automatic loading of the USB storage driver. To configure the system to prevent the usb-storage kernel module from being loaded, add the following line to a file in the directory /etc/modprobe.d:
install usb-storage /bin/false
This will prevent the modprobe program from loading the usb-storage module, but will not prevent an administrator (or another program) from using the insmod program to load the module manually.
USB storage devices such as thumb drives can be used to introduce malicious software.
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.