Take the 2-minute tour ×
Server Fault is a question and answer site for professional system and network administrators. It's 100% free, no registration required.

I'm going to ask this question as if I'm not going to receieve an answer. I'm trying to mount a 2TB USB drive onto a RHEL 3 server that is running a 2.4 kernel. Alone, the volume size of 2TB is meeting the limitation of the kernel, however, I was wondering if there was a sneaky way of getting it to load as a device on this system. Here's what the system says:

lsusb -vv output

# lsusb -vv
Bus 001 Device 006: ID 0411:019d MelCo., Inc. 
Device Descriptor:
  bLength                18
  bDescriptorType         1
  bcdUSB               2.00
  bDeviceClass            0 (Defined at Interface level)
  bDeviceSubClass         0 
  bDeviceProtocol         0 
  bMaxPacketSize0        64
  idVendor           0x0411 MelCo., Inc.
  idProduct          0x019d 
  bcdDevice            1.00
  iManufacturer           1 BUFFALO 
  iProduct                2  HD-CXTU2       
  iSerial                 3 00101007000A23920
  bNumConfigurations      1
  Configuration Descriptor:
    bLength                 9
    bDescriptorType         2
    wTotalLength           32
    bNumInterfaces          1
    bConfigurationValue     1
    iConfiguration          0
    bmAttributes         0xc0
      Self Powered
    MaxPower                2mA
    Interface Descriptor:
      bLength                 9
      bDescriptorType         4
      bInterfaceNumber        0
      bAlternateSetting       0
      bNumEndpoints           2
      bInterfaceClass         8 Mass Storage
      bInterfaceSubClass      6 SCSI
      bInterfaceProtocol     80 Bulk (Zip)
      iInterface              0 
      Endpoint Descriptor:
        bLength                 7
        bDescriptorType         5
        bEndpointAddress     0x81  EP 1 IN
        bmAttributes            2
          Transfer Type            Bulk
          Synch Type               none
        wMaxPacketSize         64
        bInterval               0
      Endpoint Descriptor:
        bLength                 7
        bDescriptorType         5
        bEndpointAddress     0x02  EP 2 OUT
        bmAttributes            2
          Transfer Type            Bulk
          Synch Type               none
        wMaxPacketSize         64
        bInterval               0
  Language IDs: (length=4)
     0409 English(US)

/var/log/messages

Aug 6 02:38:23 server devlabel: devlabel service started/restarted
Aug 6 02:38:24 server kernel: hub.c: new USB device 01:00.0-2, assigned address 4
Aug 6 02:38:25 server /etc/hotplug/usb.agent: ... no modules for USB product 411/19d/100
Aug 6 02:38:25 server kernel: usb.c: USB device not responding, giving up (error=-110)
Aug 6 02:38:27 server kernel: hub.c: new USB device 01:00.0-2, assigned address 5
Aug 6 02:38:32 server /etc/hotplug/usb.agent: Setup usb-storage for USB product 411/19d/100
Aug 6 02:38:33 server kernel: SCSI disk error : host 0 channel 0 id 0 lun 0 return code = 8000002
Aug 6 02:38:33 server kernel: Current sd08:00: sense key None
Aug 6 02:38:33 server kernel: I/O error: dev 08:00, sector 0
Aug 6 02:38:33 server kernel: Device 08:00 not ready.
Aug 6 02:38:33 server kernel: I/O error: dev 08:00, sector 2
Aug 6 02:38:33 server devlabel: devlabel's temporary ignore list /etc/sysconfig/devlabel.d/ignore_list has been emptied due to a change in device configuration.

OS and Kernel Versions

[root@server root]# cat /etc/redhat-release && uname -r
Red Hat Enterprise Linux ES release 3 (Taroon Update 6)
2.4.21-37.ELsmp

fdisk -l shows only the main disk, not the USB drive. Basically, it's not loading the device so that I can mount it manually, however, it appears that the kernel is loading some sort of data and is aware that the device has been plugged in and knows some of the details of the device.

The device in question is a DriveStation DataVault - HD-CXTU2 (Buffalo Technologies) and I have already spoken to the vendor and they do no support linux but indicate that it's a standard storage driver. I don't know how knowledgable the guy was, so I can't be for sure, but I still want to blame the OS/Kernel versions since they are so old.

Any ideas, or am I just SOL?

share|improve this question
    
Have you tried to contact RedHat support? –  rvs Aug 7 '11 at 19:54
    
Nope. I think this is way past that. –  drewrockshard Aug 7 '11 at 20:17
1  
I'm just curious. Why are you still using this ancient OS while trying to access a state of the art hardware? What prevents you from upgrading? You OS is way out of maintenance. –  mailq Aug 7 '11 at 21:13
    
@mailq: You are preaching to the choir. This system is currently not able to be upgraded. Period. It's out of my hands in regards to that. I just support it. –  drewrockshard Aug 7 '11 at 21:55
    
Last comment from me. The old driver is unable to access the drive whereas the correct driver was loaded. - As RedHat doesn't support the system I wouldn't support it either. - Some things just don't work. And to get them working you need a newer version. [And yes you have the same opinion] –  mailq Aug 7 '11 at 22:14
add comment

Your Answer

 
discard

By posting your answer, you agree to the privacy policy and terms of service.

Browse other questions tagged or ask your own question.