Announcement

Collapse
No announcement yet.

VIZO External HD enclosure doesn't work with Kubuntu?

Collapse
This topic is closed.
X
X
 
  • Filter
  • Time
  • Show
Clear All
new posts

    VIZO External HD enclosure doesn't work with Kubuntu?

    Hi -

    Just got a VIZO LXE-350 (http://www.newegg.com/Product/Produc...82E16817425023).

    Lets you do IDE or SATA HD to USB or eSATA. Works fine in XP, and the hard drive is fine, but doesn't seem to work in Linux (Kubuntu 11.10 on a Dell Inspiron 6000 laptop). I'm wondering if there's a work-around or if I need to just give up and return it...

    With an IDE drive in there, connected via USB, I get the following in syslog (i've added newlines where larger gaps of time occur):

    Oct 28 17:32:16 caseylinux kernel: [ 128.564067] usb 1-5: new high speed USB device number 4 using ehci_hcd
    Oct 28 17:32:17 caseylinux mtp-probe: checking bus 1, device 4: "/sys/devices/pci0000:00/0000:00:1d.7/usb1/1-5"
    Oct 28 17:32:17 caseylinux mtp-probe: bus: 1, device: 4 was not an MTP device
    Oct 28 17:32:18 caseylinux kernel: [ 129.965973] usbcore: registered new interface driver uas
    Oct 28 17:32:18 caseylinux kernel: [ 130.413395] Initializing USB Mass Storage driver...
    Oct 28 17:32:18 caseylinux kernel: [ 130.413674] scsi2 : usb-storage 1-5:1.0
    Oct 28 17:32:18 caseylinux kernel: [ 130.414535] usbcore: registered new interface driver usb-storage
    Oct 28 17:32:18 caseylinux kernel: [ 130.414541] USB Mass Storage support registered.
    Oct 28 17:32:19 caseylinux kernel: [ 131.421416] scsi 2:0:0:0: Direct-Access ST325082 4A PQ: 0 ANSI: 2 CCS
    Oct 28 17:32:19 caseylinux kernel: [ 131.429745] sd 2:0:0:0: Attached scsi generic sg2 type 0
    Oct 28 17:32:19 caseylinux kernel: [ 131.430011] sd 2:0:0:0: [sdb] 488397168 512-byte logical blocks: (250 GB/232 GiB)
    Oct 28 17:32:19 caseylinux kernel: [ 131.431508] sd 2:0:0:0: [sdb] Write Protect is off
    Oct 28 17:32:19 caseylinux kernel: [ 131.431518] sd 2:0:0:0: [sdb] Mode Sense: 00 38 00 00
    Oct 28 17:32:19 caseylinux kernel: [ 131.432754] sd 2:0:0:0: [sdb] Asking for cache data failed
    Oct 28 17:32:19 caseylinux kernel: [ 131.432763] sd 2:0:0:0: [sdb] Assuming drive cache: write through
    Oct 28 17:32:19 caseylinux kernel: [ 131.435628] sd 2:0:0:0: [sdb] Asking for cache data failed
    Oct 28 17:32:19 caseylinux kernel: [ 131.435637] sd 2:0:0:0: [sdb] Assuming drive cache: write through
    Oct 28 17:32:19 caseylinux kernel: [ 131.492855] sdb: sdb1 sdb2 sdb3 sdb4 < sdb5 sdb6 sdb7 >
    Oct 28 17:32:19 caseylinux kernel: [ 131.496594] sd 2:0:0:0: [sdb] Asking for cache data failed
    Oct 28 17:32:19 caseylinux kernel: [ 131.496603] sd 2:0:0:0: [sdb] Assuming drive cache: write through
    Oct 28 17:32:19 caseylinux kernel: [ 131.496611] sd 2:0:0:0: [sdb] Attached SCSI disk
    Oct 28 17:32:19 caseylinux ata_id[2377]: HDIO_GET_IDENTITY failed for '/dev/sdb': Invalid argument

    Oct 28 17:32:52 caseylinux kernel: [ 163.984044] usb 1-5: reset high speed USB device number 4 using ehci_hcd

    Oct 28 17:33:00 caseylinux kernel: [ 172.347457] usb 1-5: USB disconnect, device number 4
    Oct 28 17:33:00 caseylinux kernel: [ 172.351441] scsi 2:0:0:0: Device offlined - not ready after error recovery
    Oct 28 17:33:00 caseylinux kernel: [ 172.351454] scsi 2:0:0:0: [sdb] Unhandled error code
    Oct 28 17:33:00 caseylinux kernel: [ 172.351457] scsi 2:0:0:0: [sdb] Result: hostbyte=DID_ABORT driverbyte=DRIVER_OK
    Oct 28 17:33:00 caseylinux kernel: [ 172.351462] scsi 2:0:0:0: [sdb] CDB: Read(10): 28 00 0a 00 67 a7 00 00 08 00
    Oct 28 17:33:00 caseylinux kernel: [ 172.351472] end_request: I/O error, dev sdb, sector 167798695
    Oct 28 17:33:00 caseylinux kernel: [ 172.351477] quiet_error: 27 callbacks suppressed
    Oct 28 17:33:00 caseylinux kernel: [ 172.351481] Buffer I/O error on device sdb2, logical block 41945600
    Oct 28 17:33:00 caseylinux kernel: [ 172.351485] Buffer I/O error on device sdb2, logical block 41945601
    Oct 28 17:33:00 caseylinux kernel: [ 172.351488] Buffer I/O error on device sdb2, logical block 41945602
    Oct 28 17:33:00 caseylinux kernel: [ 172.351491] Buffer I/O error on device sdb2, logical block 41945603
    Oct 28 17:33:00 caseylinux kernel: [ 172.353280] Buffer I/O error on device sdb2, logical block 41945600
    Oct 28 17:33:00 caseylinux kernel: [ 172.353286] Buffer I/O error on device sdb2, logical block 41945601
    Oct 28 17:33:00 caseylinux kernel: [ 172.353289] Buffer I/O error on device sdb2, logical block 41945602
    Oct 28 17:33:00 caseylinux kernel: [ 172.353292] Buffer I/O error on device sdb2, logical block 41945603
    Oct 28 17:33:00 caseylinux kernel: [ 172.353318] Buffer I/O error on device sdb2, logical block 41945704
    Oct 28 17:33:00 caseylinux kernel: [ 172.353321] Buffer I/O error on device sdb2, logical block 41945705
    Oct 28 17:33:02 caseylinux kernel: [ 174.016054] usb 1-5: new high speed USB device number 5 using ehci_hcd
    Oct 28 17:33:02 caseylinux kernel: [ 174.151260] scsi3 : usb-storage 1-5:1.0
    Oct 28 17:33:03 caseylinux kernel: [ 175.149312] scsi 3:0:0:0: Direct-Access ST325082 4A PQ: 0 ANSI: 2 CCS
    Oct 28 17:33:03 caseylinux kernel: [ 175.151264] sd 3:0:0:0: Attached scsi generic sg2 type 0
    Oct 28 17:33:03 caseylinux kernel: [ 175.151462] sd 3:0:0:0: [sdc] 488397168 512-byte logical blocks: (250 GB/232 GiB)
    Oct 28 17:33:03 caseylinux kernel: [ 175.152651] sd 3:0:0:0: [sdc] Mode Sense: 00 38 00 00
    Oct 28 17:33:03 caseylinux kernel: [ 175.153637] sd 3:0:0:0: [sdc] Asking for cache data failed
    Oct 28 17:33:03 caseylinux kernel: [ 175.153645] sd 3:0:0:0: [sdc] Assuming drive cache: write through
    Oct 28 17:33:03 caseylinux kernel: [ 175.158014] sd 3:0:0:0: [sdc] Asking for cache data failed
    Oct 28 17:33:03 caseylinux kernel: [ 175.158023] sd 3:0:0:0: [sdc] Assuming drive cache: write through
    Oct 28 17:33:03 caseylinux kernel: [ 175.218115] sdc: sdc1 sdc2 sdc3 sdc4 < sdc5 sdc6 sdc7 >
    Oct 28 17:33:03 caseylinux kernel: [ 175.222478] sd 3:0:0:0: [sdc] Asking for cache data failed
    Oct 28 17:33:03 caseylinux kernel: [ 175.222488] sd 3:0:0:0: [sdc] Assuming drive cache: write through
    Oct 28 17:33:03 caseylinux kernel: [ 175.222495] sd 3:0:0:0: [sdc] Attached SCSI disk
    followed by:

    Oct 28 17:33:22 caseylinux udevd[2374]: timeout '/sbin/blkid -o udev -p /dev/sdb3'
    Oct 28 17:33:22 caseylinux udevd[2375]: timeout '/sbin/blkid -o udev -p /dev/sdb4'
    Oct 28 17:33:22 caseylinux udevd[2376]: timeout '/sbin/blkid -o udev -p /dev/sdb5'
    Oct 28 17:33:22 caseylinux udevd[448]: timeout '/sbin/blkid -o udev -p /dev/sdb1'
    Oct 28 17:33:22 caseylinux udevd[2392]: timeout '/sbin/blkid -o udev -p /dev/sdb7'
    Oct 28 17:33:22 caseylinux udevd[2391]: timeout '/sbin/blkid -o udev -p /dev/sdb6'
    followed by an infinite stream of:

    Oct 28 17:33:23 caseylinux udevd[2376]: timeout: killing '/sbin/blkid -o udev -p /dev/sdb5' [2396]
    Oct 28 17:33:23 caseylinux udevd[448]: timeout: killing '/sbin/blkid -o udev -p /dev/sdb1' [2397]
    Oct 28 17:33:23 caseylinux udevd[2392]: timeout: killing '/sbin/blkid -o udev -p /dev/sdb7' [2399]
    Oct 28 17:33:23 caseylinux udevd[2375]: timeout: killing '/sbin/blkid -o udev -p /dev/sdb4' [2395]
    Oct 28 17:33:23 caseylinux udevd[2374]: timeout: killing '/sbin/blkid -o udev -p /dev/sdb3' [2394]
    Oct 28 17:33:23 caseylinux udevd[2391]: timeout: killing '/sbin/blkid -o udev -p /dev/sdb6' [2398]
    Oct 28 17:33:24 caseylinux udevd[448]: timeout: killing '/sbin/blkid -o udev -p /dev/sdb1' [2397]
    Oct 28 17:33:24 caseylinux udevd[2376]: timeout: killing '/sbin/blkid -o udev -p /dev/sdb5' [2396]
    ...etc
    ...etc
    ...etc
    Any insight? Is this enclosure maybe just not compatible with Linux, or at least Ubuntu?

    Thanks!
    -Casey

    #2
    Re: VIZO External HD enclosure doesn't work with Kubuntu?

    Have you tried it with eSATA?

    Comment


      #3
      Re: VIZO External HD enclosure doesn't work with Kubuntu?

      As Detonate suggests, if your Dell laptop has an e-SATA connector (my Latitude E6500 does), that will be WAY faster than USB. You'll need an e-SATA-to-e-SATA cable, which are available for around $10 US, plus shipping.

      e-SATA "just works" on my debian/KDE systems. I could test it on Kubuntu 11.10 if needed, but the kernel is not that different so I'm sure it will work.

      Comment


        #4
        Re: VIZO External HD enclosure doesn't work with Kubuntu?

        Thanks for the ideas - I don't have an eSATA port, I got the enclosure just so 5 years from now I'll have the ability to use SATA drives and ports, etc. So for now I'll need it work via USB... Appreciate the input, though.

        Not hearing any suggestions on the USB error, sounds like this one may be a dud for Linux (or vice-versa, depending on how you look at it. :-) ) Too bad, it's a nice enclosure, otherwise.

        I'll keep my fingers crossed for a workaround, but will prepare emotionally for another RMA. (This is the third! - the first two (different brand) had bad power supplies...)

        -c

        Comment


          #5
          Re: VIZO External HD enclosure doesn't work with Kubuntu?

          Originally posted by chconnor

          Not hearing any suggestions on the USB error, sounds like this one may be a dud for Linux (or vice-versa, depending on how you look at it. :-)
          If any USB storage device works correctly on your Kubuntu system, i.e. flash memory sticks or cameras or phones, then you can't point at the Kubuntu system as the source of the error. If you power on your external hard drive, and then plug in the connector, and if the notifier does not pop up and indicate the connected device, then the problem is 100% with the connected device.

          Comment


            #6
            Re: VIZO External HD enclosure doesn't work with Kubuntu?

            Ok, thanks, and for the record I wasn't really meaning to disparage Linux/Kubuntu. It works fine in XP, which led me to make my little joke, but of course I don't know enough about it to blame anything or anyone. I just meant to imply that this enclosure and Kubuntu seem to not get along.

            Given what I had google'd, the "HDIO_GET_IDENTITY failed for '/dev/sdb': Invalid argument" error seemed like maybe it was a script that wasn't used to this kind of enclosure or something... I was wondering if I could set something up in /etc/hdparm.conf to get around it, but of course maybe the enclosure just fails to respond as it should.

            -c

            Comment

            Working...
            X