@grawity: Oh, yes- What I meant was: [ 1602.683559] sd 3:0:0:0: [sdc] 120093 512-byte hardware sectors: (61.4 MB/58.6 MiB) [ 1602.728250] sd 3:0:0:1: [sdd] 3995649 512-byte hardware sectors: (2.04 GB/1.90 GiB)
compared to (with the patch) [ 339.211253] sd 4:0:0:0: [sdc] 120092 512-byte hardware sectors: (61.4 MB/58.6 MiB) [ 339.250733] sd 4:0:0:1: [sdd] 3995648 512-byte hardware sectors: (2.04 GB/1.90 GiB) So both devices get their capacity reduced by one, which is ok. Unfortunately this does not seem to help completely. @I fear this bug is sadly becoming more and more bloated and confusing by the number of hw that needs to be fixed. If we could split out (create) a new bug for each device that needs to be taken care of, this would help very much. I would suggest a topic like "usbstorage: <device> shows 'No sense [current]' bug", against the linux package and "sudo lsusb -vvv", full dmesg (good)[optional] and fll dmesg (bad). If you either mail me or post the new bug number, I will assign it to me. This bug I will use to track/complete the bug on the NexStar GX (as this has been the device initially reported. And I would set the description accordingly. -- USB Hard Drive Not Accessible, vol_id hangs https://bugs.launchpad.net/bugs/264789 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list [email protected] https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
