Comment 181 for bug 264789

Using:

Linux ubuntu 2.6.31-14-generic #48-Ubuntu SMP Fri Oct 16 14:04:26 UTC 2009 i686 GNU/Linux

with the same JMicron Hi-Speed USB to SATA & PATA Combo Bridge as mentioned in comment #100, I am still hitting this bug. :( I have a Western Digital Cavier SE16, 640GB SATA drive (WD6400AAKS) attached to this adapter.

idVendor 0x152d JMicron Technology Corp. / JMicron USA Technology Corp.
idProduct 0x2338 JM20337 Hi-Speed USB to SATA & PATA Combo Bridge
bcdDevice 1.00
iManufacturer JMicron
iProduct 2 USB to ATA/ATAPI Bridge

Has an intelligent fix (or idea of a solution, even) to this bug materialized? From what I understand, probing for metadata at/near the "end" of the device is necessary auto-mounting/setting up/etc. any devices not listed in /etc/fstab already and that "end" space for their magic data/sequence.

I assume an approach like this won't work (or has already been proven to fail?):

- get size from device
- start reading blocks (size-n) sectors and forward
- parse sectors for magic data
- continue until error is returned (b/c device reports no sector, etc.)
- stop reading

This bug, in combination with the failure of the kernel to robustly handle the apparent bug in the chipset of this particular adapter (see the thread at http://linux.derkeiler.com/Mailing-Lists/Kernel/2008-07/threads.html#08755) makes for craptastic times w/ this hardware. (unless that has been fixed since summer '08?) Out of curiosity, was anyone able to get a response from JMicron about the bug in the chipset?