Re: [Xen-users] Trouble mounting a USB drive on dom0

[Digimer <linux@xxxxxxxxxxx>]

On 10-02-22 04:08 PM, Digimer wrote:
> Hi all,
>
> I've got two Xen servers hosting a set of DomUs on CentOS 5.4 x86_64 in
> a simple two-node cluster configuration.
>
> I tried today to mount a USB drive on either node's dom0 and both times
> was not able to. I can see in '/var/log/messages' and 'lsusb' that the
> drive is there and seen, but 'fdisk -l' doesn't show it.
>
> /var/log/messages
> ----------------------------------------------------------------
> Feb 22 15:37:56 vsh02 kernel: usb 1-1: new high speed USB device using
> ehci_hcd and address 2
> Feb 22 15:37:56 vsh02 kernel: usb 1-1: configuration #1 chosen from 1
> choice
> Feb 22 15:37:57 vsh02 kernel: Initializing USB Mass Storage driver...
> Feb 22 15:37:57 vsh02 kernel: scsi4 : SCSI emulation for USB Mass
> Storage devices
> Feb 22 15:37:57 vsh02 kernel: usbcore: registered new driver usb-storage
> Feb 22 15:37:57 vsh02 kernel: USB Mass Storage support registered.
> Feb 22 15:38:02 vsh02 kernel: Vendor: Model: Rev:
> Feb 22 15:38:02 vsh02 kernel: Type: Direct-Access ANSI SCSI revision: 02
> Feb 22 15:38:02 vsh02 kernel: sd 4:0:0:0: Attached scsi disk sdc
> Feb 22 15:38:02 vsh02 kernel: sd 4:0:0:0: Attached scsi generic sg2 type 0
> ----------------------------------------------------------------
>
> lsusb
> ----------------------------------------------------------------
> Bus 002 Device 001: ID 0000:0000
> Bus 001 Device 003: ID 152d:2338 JMicron Technology Corp. / JMicron USA
> Technology Corp. JM20337 Hi-Speed USB to SATA & PATA Combo Bridge
> Bus 001 Device 001: ID 0000:0000
> ----------------------------------------------------------------
>
> fdisk -l
> ----------------------------------------------------------------
> Disk /dev/sda: 1500.3 GB, 1500301910016 bytes
> 255 heads, 63 sectors/track, 182401 cylinders
> Units = cylinders of 16065 * 512 = 8225280 bytes
>
> Device Boot Start End Blocks Id System
> /dev/sda1 * 1 32 257008+ fd Linux raid autodetect
> /dev/sda2 33 2582 20482875 fd Linux raid autodetect
> /dev/sda3 2583 2837 2048287+ fd Linux raid autodetect
> /dev/sda4 2838 182401 1442347830 5 Extended
> /dev/sda5 2838 182401 1442347798+ fd Linux raid autodetect
>
> Disk /dev/sdb: 1500.3 GB, 1500301910016 bytes
> 255 heads, 63 sectors/track, 182401 cylinders
> Units = cylinders of 16065 * 512 = 8225280 bytes
>
> Device Boot Start End Blocks Id System
> /dev/sdb1 * 1 32 257008+ fd Linux raid autodetect
> /dev/sdb2 33 2582 20482875 fd Linux raid autodetect
> /dev/sdb3 2583 2837 2048287+ fd Linux raid autodetect
> /dev/sdb4 2838 182401 1442347830 5 Extended
> /dev/sdb5 2838 182401 1442347798+ fd Linux raid autodetect
> ----------------------------------------------------------------
>
> I would expect to see the raw drive, if not the partition. The curious
> part is the 'messages' lists the drive as 'sdc', which is what I would
> expect. I know the drive works, as I pulled it off of a Debian (non-Xen)
> server where it works fine.
>
> So is this a Xen issue, or perhaps a CentOS/Kernel issue?
>
> Thanks!
>
> Digi
To follow-up, this turned out to be an odd incompatibility with the 
particular SATA->USB adapter with either the hardware or the kernel. It 
works elsewhere, and other drives work on my dom0's. So ya, there you go. :)
Digi

_______________________________________________
Xen-users mailing list
Xen-users@xxxxxxxxxxxxxxxxxxx
http://lists.xensource.com/xen-users