[Bug 264789] Re: USB Hard Drive Not Accessible, vol_id hangs
** Attachment removed: "C72957374002D7EF17AED2B17BEF18FE.jpg" https://bugs.launchpad.net/ubuntu/+source/linux/+bug/264789/+attachment/4870526/+files/C72957374002D7EF17AED2B17BEF18FE.jpg ** Attachment removed: "428E18A7EF2A80EE1218968A65B3C947.jpg" https://bugs.launchpad.net/ubuntu/+source/linux/+bug/264789/+attachment/4875133/+files/428E18A7EF2A80EE1218968A65B3C947.jpg ** Attachment removed: "9791D64EC53F47A1CB31EEE7A11E24B4.jpg" https://bugs.launchpad.net/ubuntu/+source/linux/+bug/264789/+attachment/4879827/+files/9791D64EC53F47A1CB31EEE7A11E24B4.jpg ** Attachment removed: "AEE8B53C164C793EE55DF5B276E714BA.jpg" https://bugs.launchpad.net/ubuntu/+source/linux/+bug/264789/+attachment/4882217/+files/AEE8B53C164C793EE55DF5B276E714BA.jpg ** Attachment removed: "02DFF7ADFCAF6D004E693D7906C06B8B.jpg" https://bugs.launchpad.net/ubuntu/+source/linux/+bug/264789/+attachment/4886118/+files/02DFF7ADFCAF6D004E693D7906C06B8B.jpg ** Attachment removed: "907BCBC20D4EDC1872A10011C91D6A94.jpg" https://bugs.launchpad.net/ubuntu/+source/linux/+bug/264789/+attachment/4888710/+files/907BCBC20D4EDC1872A10011C91D6A94.jpg ** Attachment removed: "07FA491269357B5FE8D8F2586E5DA865.jpg" https://bugs.launchpad.net/ubuntu/+source/linux/+bug/264789/+attachment/4916079/+files/07FA491269357B5FE8D8F2586E5DA865.jpg ** Attachment removed: "A15A27255BA4C89123D076C12CC37C7A.jpg" https://bugs.launchpad.net/ubuntu/+source/linux/+bug/264789/+attachment/4900542/+files/A15A27255BA4C89123D076C12CC37C7A.jpg ** Attachment removed: "D4D79674A43A0C32F3BB8BD963AAB4CF.jpg" https://bugs.launchpad.net/ubuntu/+source/linux/+bug/264789/+attachment/4917933/+files/D4D79674A43A0C32F3BB8BD963AAB4CF.jpg ** Attachment removed: "BBE1AB4128BE8BC0.jpg" https://bugs.launchpad.net/ubuntu/+source/linux/+bug/264789/+attachment/4947459/+files/BBE1AB4128BE8BC0.jpg ** Attachment removed: "59A8518FF2EC83ED.jpg" https://bugs.launchpad.net/ubuntu/+source/linux/+bug/264789/+attachment/4974398/+files/59A8518FF2EC83ED.jpg -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/264789 Title: USB Hard Drive Not Accessible, vol_id hangs To manage notifications about this bug go to: https://bugs.launchpad.net/linux/+bug/264789/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 264789] Re: USB Hard Drive Not Accessible, vol_id hangs
** Changed in: linux Importance: Unknown = Medium -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/264789 Title: USB Hard Drive Not Accessible, vol_id hangs -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 264789] Re: USB Hard Drive Not Accessible, vol_id hangs
Intrepid Ibex reached end-of-life on 30 April 2010 so I am closing the report. The bug has been fixed in newer releases of Ubuntu. ** Changed in: linux (Ubuntu Intrepid) Status: Fix Committed = Invalid -- 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 ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
Re: [Bug 264789] Re: USB Hard Drive Not Accessible, vol_id hangs
It's not been fixed for me! On 8 May 2010, at 00:07, Alex Valavanis valavanisa...@googlemail.com wrote: Intrepid Ibex reached end-of-life on 30 April 2010 so I am closing the report. The bug has been fixed in newer releases of Ubuntu. ** Changed in: linux (Ubuntu Intrepid) Status: Fix Committed = Invalid -- USB Hard Drive Not Accessible, vol_id hangs https://bugs.launchpad.net/bugs/264789 You received this bug notification because you are a direct subscriber of the bug. -- 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 ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
Re: [Bug 264789] Re: USB Hard Drive Not Accessible, vol_id hangs
no problems here.. i'm on 2.6.31-20-generic. 2010/4/29 Robert rob...@gmail.com I still have this problem in Karmic (even after a fresh install). I also have this problem after upgrading to Lucid release candidate. -- USB Hard Drive Not Accessible, vol_id hangs https://bugs.launchpad.net/bugs/264789 You received this bug notification because you are a direct subscriber of the bug. Status in The Linux Kernel: Fix Released Status in “linux” package in Ubuntu: Fix Released Status in “linux” source package in Intrepid: Fix Committed Bug description: I updated to 2.6.27-2 today, and one of my hard drives is no longer recognized. It is in a Vantec NexStar GX enclosure, and was working fine on .26, and continues to work fine on a Hardy machine. Here is the dmesg for it: [ 6722.944029] usb 5-5: new high speed USB device using ehci_hcd and address 27 [ 6723.077863] usb 5-5: configuration #1 chosen from 1 choice [ 6723.079511] hub 5-5:1.0: USB hub found [ 6723.080345] hub 5-5:1.0: 4 ports detected [ 6732.712034] usb 5-5: reset high speed USB device using ehci_hcd and address 27 [ 6733.124011] usb 5-5.1: new high speed USB device using ehci_hcd and address 28 [ 6733.364598] usb 5-5.1: configuration #1 chosen from 1 choice [ 6733.365180] scsi17 : SCSI emulation for USB Mass Storage devices [ 6733.365818] usb-storage: device found at 28 [ 6733.365830] usb-storage: waiting for device to settle before scanning [ 6738.364276] usb-storage: device scan complete [ 6738.361002] scsi 17:0:0:0: Direct-Access ST340063 2A 3.04 PQ: 0 ANSI: 0 [ 6738.361002] sd 17:0:0:0: [sdm] 781422769 512-byte hardware sectors (400088 MB) [ 6738.361002] sd 17:0:0:0: [sdm] Write Protect is off [ 6738.361002] sd 17:0:0:0: [sdm] Mode Sense: 03 00 00 00 [ 6738.361002] sd 17:0:0:0: [sdm] Assuming drive cache: write through [ 6738.361002] sd 17:0:0:0: [sdm] 781422769 512-byte hardware sectors (400088 MB) [ 6738.370354] sd 17:0:0:0: [sdm] Write Protect is off [ 6738.370362] sd 17:0:0:0: [sdm] Mode Sense: 03 00 00 00 [ 6738.370365] sd 17:0:0:0: [sdm] Assuming drive cache: write through [ 6738.371516] sdm: sdm1 [ 6738.418089] sd 17:0:0:0: [sdm] Attached SCSI disk [ 6738.418995] sd 17:0:0:0: Attached scsi generic sg8 type 0 [ 6738.656598] sd 17:0:0:0: [sdm] Sense Key : No Sense [current] [ 6738.656614] sd 17:0:0:0: [sdm] Add. Sense: No additional sense information From there, the last 2 lines about Sense Key and Add Sense repeat over and over again. The 4 port hub that is a part of the enclosure continues to work fine though, with a floppy drive, a printer, and another hard drive. I have a Vantec NexStar 3 enclosure as well, and it is working just fine. Dmesg for the working enclosure: [ 4281.996024] usb 5-3: new high speed USB device using ehci_hcd and address 19 [ 4282.131863] usb 5-3: configuration #1 chosen from 1 choice [ 4282.133222] scsi12 : SCSI emulation for USB Mass Storage devices [ 4282.133561] usb-storage: device found at 19 [ 4282.133566] usb-storage: waiting for device to settle before scanning [ 4287.132002] usb-storage: device scan complete [ 4287.136004] scsi 12:0:0:0: Direct-Access ST375064 0AS PQ: 0 ANSI: 2 [ 4287.138368] sd 12:0:0:0: [sdi] 1465149168 512-byte hardware sectors (750156 MB) [ 4287.144790] sd 12:0:0:0: [sdi] Write Protect is off [ 4287.144800] sd 12:0:0:0: [sdi] Mode Sense: 38 00 00 00 [ 4287.144804] sd 12:0:0:0: [sdi] Assuming drive cache: write through [ 4287.152388] sd 12:0:0:0: [sdi] 1465149168 512-byte hardware sectors (750156 MB) [ 4287.154966] sd 12:0:0:0: [sdi] Write Protect is off [ 4287.154975] sd 12:0:0:0: [sdi] Mode Sense: 38 00 00 00 [ 4287.154979] sd 12:0:0:0: [sdi] Assuming drive cache: write through [ 4287.154988] sdi: sdi1 [ 4287.176965] sd 12:0:0:0: [sdi] Attached SCSI disk [ 4287.177173] sd 12:0:0:0: Attached scsi generic sg7 type 0 [ 4289.129138] kjournald starting. Commit interval 5 seconds [ 4289.130101] EXT3 FS on sdi1, internal journal [ 4289.130110] EXT3-fs: mounted filesystem with ordered data mode. To unsubscribe from this bug, go to: https://bugs.launchpad.net/linux/+bug/264789/+subscribe -- 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 ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 264789] Re: USB Hard Drive Not Accessible, vol_id hangs
I still have this problem in Karmic (even after a fresh install). I also have this problem after upgrading to Lucid release candidate. -- 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 ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 264789] Re: USB Hard Drive Not Accessible, vol_id hangs
This should be fixed in the kernel that includes the update to stable 2.6.31.6. Unfortunately it is blocked atm by other things. You can get a preview of it at: https://launchpad.net/~stefan-bader- canonical/+archive/karmic for the time being. -- 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 ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 264789] Re: USB Hard Drive Not Accessible, vol_id hangs
$ uname -a Linux ehrlichman 2.6.31-16-generic #52-Ubuntu SMP Thu Dec 3 22:00:22 UTC 2009 i686 GNU/Linux [ 567.800086] usb 1-2: new high speed USB device using ehci_hcd and address 5 [ 567.933509] usb 1-2: configuration #1 chosen from 1 choice [ 567.981341] Initializing USB Mass Storage driver... [ 567.982922] scsi2 : SCSI emulation for USB Mass Storage devices [ 567.983210] usbcore: registered new interface driver usb-storage [ 567.983218] USB Mass Storage support registered. [ 567.984879] usb-storage: device found at 5 [ 567.984885] usb-storage: waiting for device to settle before scanning [ 572.984308] usb-storage: device scan complete [ 572.985296] scsi 2:0:0:0: Direct-Access Initio 0G9SA00 4.46 PQ: 0 ANSI: 0 [ 572.986231] sd 2:0:0:0: Attached scsi generic sg2 type 0 [ 573.004776] sd 2:0:0:0: [sdb] 156301488 512-byte logical blocks: (80.0 GB/74.5 GiB) [ 573.005514] sd 2:0:0:0: [sdb] Write Protect is off [ 573.005522] sd 2:0:0:0: [sdb] Mode Sense: 00 00 00 00 [ 573.005528] sd 2:0:0:0: [sdb] Assuming drive cache: write through [ 573.007013] sd 2:0:0:0: [sdb] Assuming drive cache: write through [ 573.007022] sdb: sdb1 sdb2 sdb3 sdb5 sdb6 sdb7 [ 573.120079] sd 2:0:0:0: [sdb] Assuming drive cache: write through [ 573.120090] sd 2:0:0:0: [sdb] Attached SCSI disk [ 575.955694] kjournald starting. Commit interval 5 seconds [ 575.955739] EXT3-fs warning: checktime reached, running e2fsck is recommended [ 576.089460] EXT3 FS on sdb7, internal journal [ 576.089471] EXT3-fs: recovery complete. [ 576.194774] EXT3-fs: mounted filesystem with writeback data mode. [ 578.858365] kjournald starting. Commit interval 5 seconds [ 578.858386] EXT3-fs warning: checktime reached, running e2fsck is recommended [ 578.858938] EXT3 FS on sdb5, internal journal [ 578.858945] EXT3-fs: recovery complete. [ 578.859564] EXT3-fs: mounted filesystem with writeback data mode. [ 1484.334878] sd 2:0:0:0: [sdb] Sense Key : No Sense [current] [ 1484.334893] Info fld=0x0 [ 1484.334898] sd 2:0:0:0: [sdb] Add. Sense: No additional sense information [ 1511.226389] sd 2:0:0:0: [sdb] Sense Key : No Sense [current] [ 1511.226405] Info fld=0x0 [ 1511.226410] sd 2:0:0:0: [sdb] Add. Sense: No additional sense information Bus 001 Device 005: ID 13fd:1650 Initio Corporation Device Descriptor: bLength18 bDescriptorType 1 bcdUSB 2.00 bDeviceClass0 (Defined at Interface level) bDeviceSubClass 0 bDeviceProtocol 0 bMaxPacketSize064 idVendor 0x13fd Initio Corporation idProduct 0x1650 bcdDevice4.46 iManufacturer 1 Initio iProduct2 0G9SA00 iSerial 3 001010165 bNumConfigurations 1 Configuration Descriptor: bLength 9 bDescriptorType 2 wTotalLength 32 bNumInterfaces 1 bConfigurationValue 1 iConfiguration 0 bmAttributes 0xc0 Self Powered MaxPower0mA Interface Descriptor: bLength 9 bDescriptorType 4 bInterfaceNumber0 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 bmAttributes2 Transfer TypeBulk Synch Type None Usage Type Data wMaxPacketSize 0x0200 1x 512 bytes bInterval 0 Endpoint Descriptor: bLength 7 bDescriptorType 5 bEndpointAddress 0x02 EP 2 OUT bmAttributes2 Transfer TypeBulk Synch Type None Usage Type Data wMaxPacketSize 0x0200 1x 512 bytes bInterval 0 Device Status: 0x2735 Self Powered Test Mode The first time this happened, I read 14 gigabytes from the drive before the problem started. The second time this happened, I read 10 gigabytes from the drive before the problem recurred. This USB-SATA controller worked great for many many gigabytes under 9.04. Thanks -- 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 ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 264789] Re: USB Hard Drive Not Accessible, vol_id hangs
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? -- 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 ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 264789] Re: USB Hard Drive Not Accessible, vol_id hangs
https://bugs.launchpad.net/ubuntu/+bug/460831 may be a duplicate of this occouring on WD (Western Digital) drive (My Book Essential Edition 2.0 WD1H1U-00) -- 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 ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 264789] Re: USB Hard Drive Not Accessible, vol_id hangs
A patch in the 2.6.31.5 upstream stable patch set for the kernel contains a patch which may help. The Karmic 9.10 kernel will be pulling in this set of stable patches as a stable release update to Karmic. I've taken the liberty to build a test kernel for Karmic containing this one patch which may help not only subscribers of this bug, but a few others as well. If anyone here can test and provide feedback running this test kernel within Karmic that would be much appreciated: http://people.canonical.com/~ogasawara/lp400652/ -- 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 ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
Re: [Bug 264789] Re: USB Hard Drive Not Accessible, vol_id hangs
bump! any updates? 2009/8/26 Ramaddan ramad...@gawab.com Still have this problem on Jaunty. Did not have this problem in Intrepid. This is the output I get in dmesg: [54237.142762] usb 1-1: configuration #1 chosen from 1 choice [54237.166132] scsi10 : SCSI emulation for USB Mass Storage devices [54237.169779] usb-storage: device found at 6 [54237.169785] usb-storage: waiting for device to settle before scanning [54242.169180] usb-storage: device scan complete [54242.171276] scsi 10:0:0:0: Direct-Access Ext Hard Disk PQ: 0 ANSI: 4 [54272.284042] usb 1-1: reset high speed USB device using ehci_hcd and address 6 [54287.396554] usb 1-1: device descriptor read/64, error -110 [54302.620102] usb 1-1: device descriptor read/64, error -110 [54302.836555] usb 1-1: reset high speed USB device using ehci_hcd and address 6 ramad...@ramaddancomp:~$ dmesg | tail [54466.984043] usb 2-1: new full speed USB device using ohci_hcd and address 6 [54482.160555] usb 2-1: device descriptor read/64, error -110 [54497.440053] usb 2-1: device descriptor read/64, error -110 [54497.716039] usb 2-1: new full speed USB device using ohci_hcd and address 7 [54502.736147] usb 2-1: device descriptor read/8, error -110 [54507.857152] usb 2-1: device descriptor read/8, error -110 [54508.136048] usb 2-1: new full speed USB device using ohci_hcd and address 8 [54513.157161] usb 2-1: device descriptor read/8, error -110 [54518.277164] usb 2-1: device descriptor read/8, error -110 [54518.380062] hub 2-0:1.0: unable to enumerate USB device on port 1 Any updates on this issue? -- USB Hard Drive Not Accessible, vol_id hangs https://bugs.launchpad.net/bugs/264789 You received this bug notification because you are a direct subscriber of the bug. Status in The Linux Kernel: Fix Released Status in “linux” package in Ubuntu: Fix Released Status in linux in Ubuntu Intrepid: Fix Committed Bug description: I updated to 2.6.27-2 today, and one of my hard drives is no longer recognized. It is in a Vantec NexStar GX enclosure, and was working fine on .26, and continues to work fine on a Hardy machine. Here is the dmesg for it: [ 6722.944029] usb 5-5: new high speed USB device using ehci_hcd and address 27 [ 6723.077863] usb 5-5: configuration #1 chosen from 1 choice [ 6723.079511] hub 5-5:1.0: USB hub found [ 6723.080345] hub 5-5:1.0: 4 ports detected [ 6732.712034] usb 5-5: reset high speed USB device using ehci_hcd and address 27 [ 6733.124011] usb 5-5.1: new high speed USB device using ehci_hcd and address 28 [ 6733.364598] usb 5-5.1: configuration #1 chosen from 1 choice [ 6733.365180] scsi17 : SCSI emulation for USB Mass Storage devices [ 6733.365818] usb-storage: device found at 28 [ 6733.365830] usb-storage: waiting for device to settle before scanning [ 6738.364276] usb-storage: device scan complete [ 6738.361002] scsi 17:0:0:0: Direct-Access ST340063 2A 3.04 PQ: 0 ANSI: 0 [ 6738.361002] sd 17:0:0:0: [sdm] 781422769 512-byte hardware sectors (400088 MB) [ 6738.361002] sd 17:0:0:0: [sdm] Write Protect is off [ 6738.361002] sd 17:0:0:0: [sdm] Mode Sense: 03 00 00 00 [ 6738.361002] sd 17:0:0:0: [sdm] Assuming drive cache: write through [ 6738.361002] sd 17:0:0:0: [sdm] 781422769 512-byte hardware sectors (400088 MB) [ 6738.370354] sd 17:0:0:0: [sdm] Write Protect is off [ 6738.370362] sd 17:0:0:0: [sdm] Mode Sense: 03 00 00 00 [ 6738.370365] sd 17:0:0:0: [sdm] Assuming drive cache: write through [ 6738.371516] sdm: sdm1 [ 6738.418089] sd 17:0:0:0: [sdm] Attached SCSI disk [ 6738.418995] sd 17:0:0:0: Attached scsi generic sg8 type 0 [ 6738.656598] sd 17:0:0:0: [sdm] Sense Key : No Sense [current] [ 6738.656614] sd 17:0:0:0: [sdm] Add. Sense: No additional sense information From there, the last 2 lines about Sense Key and Add Sense repeat over and over again. The 4 port hub that is a part of the enclosure continues to work fine though, with a floppy drive, a printer, and another hard drive. I have a Vantec NexStar 3 enclosure as well, and it is working just fine. Dmesg for the working enclosure: [ 4281.996024] usb 5-3: new high speed USB device using ehci_hcd and address 19 [ 4282.131863] usb 5-3: configuration #1 chosen from 1 choice [ 4282.133222] scsi12 : SCSI emulation for USB Mass Storage devices [ 4282.133561] usb-storage: device found at 19 [ 4282.133566] usb-storage: waiting for device to settle before scanning [ 4287.132002] usb-storage: device scan complete [ 4287.136004] scsi 12:0:0:0: Direct-Access ST375064 0AS PQ: 0 ANSI: 2 [ 4287.138368] sd 12:0:0:0: [sdi] 1465149168 512-byte hardware sectors (750156 MB) [ 4287.144790] sd 12:0:0:0: [sdi] Write Protect is off [ 4287.144800] sd 12:0:0:0: [sdi] Mode Sense: 38 00 00 00 [ 4287.144804] sd 12:0:0:0: [sdi] Assuming drive cache: write through [ 4287.152388] sd 12:0:0:0: [sdi] 1465149168 512-byte hardware sectors (750156 MB) [ 4287.154966] sd 12:0:0:0: [sdi] Write
[Bug 264789] Re: USB Hard Drive Not Accessible, vol_id hangs
Still have this problem on Jaunty. Did not have this problem in Intrepid. This is the output I get in dmesg: [54237.142762] usb 1-1: configuration #1 chosen from 1 choice [54237.166132] scsi10 : SCSI emulation for USB Mass Storage devices [54237.169779] usb-storage: device found at 6 [54237.169785] usb-storage: waiting for device to settle before scanning [54242.169180] usb-storage: device scan complete [54242.171276] scsi 10:0:0:0: Direct-Access Ext Hard Disk PQ: 0 ANSI: 4 [54272.284042] usb 1-1: reset high speed USB device using ehci_hcd and address 6 [54287.396554] usb 1-1: device descriptor read/64, error -110 [54302.620102] usb 1-1: device descriptor read/64, error -110 [54302.836555] usb 1-1: reset high speed USB device using ehci_hcd and address 6 ramad...@ramaddancomp:~$ dmesg | tail [54466.984043] usb 2-1: new full speed USB device using ohci_hcd and address 6 [54482.160555] usb 2-1: device descriptor read/64, error -110 [54497.440053] usb 2-1: device descriptor read/64, error -110 [54497.716039] usb 2-1: new full speed USB device using ohci_hcd and address 7 [54502.736147] usb 2-1: device descriptor read/8, error -110 [54507.857152] usb 2-1: device descriptor read/8, error -110 [54508.136048] usb 2-1: new full speed USB device using ohci_hcd and address 8 [54513.157161] usb 2-1: device descriptor read/8, error -110 [54518.277164] usb 2-1: device descriptor read/8, error -110 [54518.380062] hub 2-0:1.0: unable to enumerate USB device on port 1 Any updates on this issue? -- 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 ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
Re: [Bug 264789] Re: USB Hard Drive Not Accessible, vol_id hangs
Robert wrote: If there's so many special exceptions, then maybe the drivers need to be rethought in a way that is more generic. Because there is no way to have the same driver (usb-storage) to say whether a device returns the total number of blocks or the highest block number (as it is expected). And when the drives response to actually reading the last sector in the case of a too high number is to return without any information and this can be a valid case for some other devices, you will have a hard time to come up with a generic solution that works for all. Upstream already started to have a list of vendors which seem always to return the wrong thing. But this cannot be the default behavior as otherwise some devices would get a too small capacity detected. -- 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 ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
Re: [Bug 264789] Re: USB Hard Drive Not Accessible, vol_id hangs
On 20/07/09 09:43 Stefan Bader wrote: Because there is no way to have the same driver (usb-storage) to say whether a device returns the total number of blocks or the highest block number (as it is expected). And when the drives response to actually reading the last sector in the case of a too high number is to return without any information and this can be a valid case for some other devices, you will have a hard time to come up with a generic solution that works for all. These devices seem to work fine on Windows and OS/X. What do they do differently? (Especially OS/X, since it is in part open source as Darwin.) -- 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 ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
Re: [Bug 264789] Re: USB Hard Drive Not Accessible, vol_id hangs
Robert wrote: These devices seem to work fine on Windows and OS/X. What do they do differently? (Especially OS/X, since it is in part open source as Darwin.) Not access the last sector for example. The problems with most of the devices started when Linux added scans for md meta-data on the complete drive (not the partition). And md meta-data is at the end of the usable space. Actually somewhere in those many reports (can't remember which) there was a comment that those cases also start behaving badly when you really try to access the last sector from Windows. -- 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 ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 264789] Re: USB Hard Drive Not Accessible, vol_id hangs
Stefan Bader wrote: If I remove the MemoryStick and reconnect the phone, it still shows exactly the same thing. Hm, right. I missed the fact that in dmesg the second device appears to be sort of a LUN. The unusual_devs entries would match on the one device... Hm, I am not sure whether its in the bug. With the unpatched normal kernel. What sector readings would you get there? I don't know what are sector readings, but they probably are in this dmesg output. ** Attachment added: dmesg output using the normal kernel (2.6.28-14-generic #46-Ubuntu) http://launchpadlibrarian.net/29180297/normal-dmesg.txt -- 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 ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 264789] Re: USB Hard Drive Not Accessible, vol_id hangs
@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 ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
Re: [Bug 264789] Re: USB Hard Drive Not Accessible, vol_id hangs
If there's so many special exceptions, then maybe the drivers need to be rethought in a way that is more generic. On Fri, Jul 17, 2009 at 1:07 PM, Stefan Baderstefan.ba...@canonical.com wrote: @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 ... -- 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 ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
Re: [Bug 264789] Re: USB Hard Drive Not Accessible, vol_id hangs
Robert wrote: I tried that patch with a Sony Ericson w800i mobile phone. It still doesn't work. That is not too surprising as the additional quirk entries only will affect Ericson w760i and z780i. A z800i would have a different usb id. -- 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 ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 264789] Re: USB Hard Drive Not Accessible, vol_id hangs
here ya go: Bus 001 Device 004: ID 0dc4:0073 Macpower Peripherals, Ltd Device Descriptor: bLength18 bDescriptorType 1 bcdUSB 2.00 bDeviceClass0 (Defined at Interface level) bDeviceSubClass 0 bDeviceProtocol 0 bMaxPacketSize064 idVendor 0x0dc4 Macpower Peripherals, Ltd idProduct 0x0073 bcdDevice0.01 iManufacturer 1 Macpower Technology Co.LTD. iProduct2 USB 2.0 3.5 DEVICE iSerial 3 BC30CD bNumConfigurations 1 Configuration Descriptor: bLength 9 bDescriptorType 2 wTotalLength 32 bNumInterfaces 1 bConfigurationValue 1 iConfiguration 0 bmAttributes 0xc0 Self Powered MaxPower 100mA Interface Descriptor: bLength 9 bDescriptorType 4 bInterfaceNumber0 bAlternateSetting 0 bNumEndpoints 2 bInterfaceClass 8 Mass Storage bInterfaceSubClass 6 SCSI bInterfaceProtocol 80 Bulk (Zip) iInterface 0 Endpoint Descriptor: bLength 7 bDescriptorType 5 bEndpointAddress 0x01 EP 1 OUT bmAttributes2 Transfer TypeBulk Synch Type None Usage Type Data wMaxPacketSize 0x0200 1x 512 bytes bInterval 0 Endpoint Descriptor: bLength 7 bDescriptorType 5 bEndpointAddress 0x82 EP 2 IN bmAttributes2 Transfer TypeBulk Synch Type None Usage Type Data wMaxPacketSize 0x0200 1x 512 bytes bInterval 0 Device Qualifier (for other device speed): bLength10 bDescriptorType 6 bcdUSB 2.00 bDeviceClass0 (Defined at Interface level) bDeviceSubClass 0 bDeviceProtocol 0 bMaxPacketSize064 bNumConfigurations 1 Device Status: 0x (Bus Powered) -- 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 ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 264789] Re: USB Hard Drive Not Accessible, vol_id hangs
@lpad, can you try the v2 version at http://people.canonical.com/~smb//bug287701/ ? -- 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 ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 264789] Re: USB Hard Drive Not Accessible, vol_id hangs
Sony-Ericsson W760i, lsusb output attached. ** Attachment added: lsusb output http://launchpadlibrarian.net/29149794/lsusb-massstorage.txt -- 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 ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
Re: [Bug 264789] Re: USB Hard Drive Not Accessible, vol_id hangs
grawity wrote: Sony-Ericsson W760i, lsusb output attached. Hm, well _that_ id should already be in. Have you tried the kernel I mentioned above? -- 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 ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 264789] Re: USB Hard Drive Not Accessible, vol_id hangs
Stefan Bader wrote: grawity wrote: Sony-Ericsson W760i, lsusb output attached. Hm, well _that_ id should already be in. Have you tried the kernel I mentioned above? I just tried it, and it partially works. The phone presents itself as _two_ removable devices - one for internal memory, the other for MemoryStick. With your test kernel (unless I failed to install it correctly), the memory card works correctly and is mounted by GNOME, but the other - internal memory - still causes the No Sense flood in dmesg. ** Attachment added: dmesg output using the test kernel http://launchpadlibrarian.net/29153459/testkernel-dmesg.txt -- 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 ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 264789] Re: USB Hard Drive Not Accessible, vol_id hangs
@Stefan Bader, what patch did you add to the kernel? something like this: UNUSUAL_DEV( 0x0dc4, 0x0073, 0x0001, 0x0001, Macpower, Storage, US_SC_DEVICE, US_PR_DEVICE, NULL, US_FL_FIX_CAPACITY), to the drivers/usb/storage/unusual_devs.h? and A + B'' patch too from this link: http://bugzilla.kernel.org/show_bug.cgi?id=11843#c26? cause I've tried adding both patches - it worked out, but another my hdd started failing.. -- 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 ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
Re: [Bug 264789] Re: USB Hard Drive Not Accessible, vol_id hangs
UNUSUAL_DEV( 0x0dc4, 0x0073, 0x0001, 0x0001, Macpower, Storage, US_SC_DEVICE, US_PR_DEVICE, NULL, US_FL_FIX_CAPACITY), Exactly this with slightly different strings. And two other similar additions for the Ericsons. to the drivers/usb/storage/unusual_devs.h? and A + B'' patch too from this link: http://bugzilla.kernel.org/show_bug.cgi?id=11843#c26? Patch A was always in the code for Jaunty. B'', based on comment 36 in that bugzilla would not be acceptable (to avoid potential other regressions). For that reason it is not included in my test kernel. -- 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 ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 264789] Re: USB Hard Drive Not Accessible, vol_id hangs
Exactly this with slightly different strings. And two other similar additions for the Ericsons. which strings you've used? -- 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 ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
Re: [Bug 264789] Re: USB Hard Drive Not Accessible, vol_id hangs
The phone presents itself as _two_ removable devices - one for internal memory, the other for MemoryStick. In that case there should be two devices visible with the lsusb output. At the moment every device has to be declared independently. Though it somehow looks as for upstream Ericson might qualify for the list of vendors which only do devices with that bug. -- 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 ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
Re: [Bug 264789] Re: USB Hard Drive Not Accessible, vol_id hangs
This entry, though the strings are just informational, what counts is the numerical id for vendor and model, plus the lower and upper ranger for the firmware (the first line). +UNUSUAL_DEV( 0x0dc4, 0x0073, 0x0001, 0x0001, + Macpower Peripherals, Ltd, + IDE to USB 2.0 HDD case with 3-port hub, + US_SC_DEVICE, US_PR_DEVICE, NULL, + US_FL_FIX_CAPACITY ), + -- 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 ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 264789] Re: USB Hard Drive Not Accessible, vol_id hangs
The phone presents itself as _two_ removable devices - one for internal memory, the other for MemoryStick. In that case there should be two devices visible with the lsusb output. At the moment every device has to be declared independently. Though it somehow looks as for upstream Ericson might qualify for the list of vendors which only do devices with that bug. Hmm, let me check. *plugs in phone* r...@theory ~/Desktop/Bug reports# lsusb Bus 002 Device 007: ID 0fce:e0c6 Sony Ericsson Mobile Communications AB Bus 002 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub Bus 001 Device 002: ID 3538:0051 Power Quotient International Co., Ltd Bus 001 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub If I remove the MemoryStick and reconnect the phone, it still shows exactly the same thing. ** Attachment added: Probably completely irrelevant output from udevadm monitor when plugging in the phone http://launchpadlibrarian.net/29157084/testkernel-udevadm.txt -- 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 ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
Re: [Bug 264789] Re: USB Hard Drive Not Accessible, vol_id hangs
If I remove the MemoryStick and reconnect the phone, it still shows exactly the same thing. Hm, right. I missed the fact that in dmesg the second device appears to be sort of a LUN. The unusual_devs entries would match on the one device... Hm, I am not sure whether its in the bug. With the unpatched normal kernel. What sector readings would you get there? -- 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 ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 264789] Re: USB Hard Drive Not Accessible, vol_id hangs
(plugged it in, and off again) ** Attachment added: dmesg output http://launchpadlibrarian.net/29160866/dmesg.txt -- 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 ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 264789] Re: USB Hard Drive Not Accessible, vol_id hangs
hello stefan, here some ifo, hth... attaching hdd with usb-ide adapter ** Attachment added: lsusb output http://launchpadlibrarian.net/29160797/sudo-lsusb-vvv.txt -- 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 ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 264789] Re: USB Hard Drive Not Accessible, vol_id hangs
sorry wrong file . THIS should be the correct lsusb ** Attachment added: sudo lsusb -vvv http://launchpadlibrarian.net/29160986/sudo-lsusb-vvv.txt -- 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 ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 264789] Re: USB Hard Drive Not Accessible, vol_id hangs
@aecl and lpad, if you want to get any change, please supply both dmesg and sudo lsusb -vvv @Gonzalo, I added some code that tries to fix up your device. The change is included in the test kernel of another bug. You can find it at http://people.canonical.com/~smb//bug287701/. Could you try whether that change helps? Thanks. -- 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 ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 264789] Re: USB Hard Drive Not Accessible, vol_id hangs
my device is vantec nexstar gx: http://www.vantecusa.com/front/product/view_detail/182 dmesg: [12020.656380] usb 1-1.1: new high speed USB device using ehci_hcd and address 12 [12020.800029] usb 1-1.1: configuration #1 chosen from 1 choice [12020.800601] scsi7 : SCSI emulation for USB Mass Storage devices [12020.801800] usb-storage: device found at 12 [12020.801807] usb-storage: waiting for device to settle before scanning [12025.800330] usb-storage: device scan complete [12025.801323] scsi 7:0:0:0: Direct-Access WDC WD32 00JB-99AA0 08.0 PQ: 0 ANSI: 0 [12025.805526] sd 7:0:0:0: [sdd] 625142449 512-byte hardware sectors: (320 GB/298 GiB) [12025.828368] sd 7:0:0:0: [sdd] Write Protect is off [12025.828378] sd 7:0:0:0: [sdd] Mode Sense: 03 00 00 00 [12025.828439] sd 7:0:0:0: [sdd] Assuming drive cache: write through [12025.834424] sd 7:0:0:0: [sdd] 625142449 512-byte hardware sectors: (320 GB/298 GiB) [12025.835519] sd 7:0:0:0: [sdd] Write Protect is off [12025.835528] sd 7:0:0:0: [sdd] Mode Sense: 03 00 00 00 [12025.835535] sd 7:0:0:0: [sdd] Assuming drive cache: write through [12025.835546] sdd: sdd1 [12025.849684] sd 7:0:0:0: [sdd] Attached SCSI disk [12025.849866] sd 7:0:0:0: Attached scsi generic sg3 type 0 [12025.953475] sd 7:0:0:0: [sdd] Result: hostbyte=DID_OK driverbyte=DRIVER_SENSE,SUGGEST_OK [12025.953482] sd 7:0:0:0: [sdd] Sense Key : Medium Error [current] [12025.953487] sd 7:0:0:0: [sdd] Add. Sense: Recorded entity not found [12025.953493] end_request: I/O error, dev sdd, sector 625142448 [12025.953496] __ratelimit: 128944 callbacks suppressed [12025.953499] Buffer I/O error on device sdd, logical block 625142448 [12025.958095] sd 7:0:0:0: [sdd] Result: hostbyte=DID_OK driverbyte=DRIVER_SENSE,SUGGEST_OK [12025.958099] sd 7:0:0:0: [sdd] Sense Key : Medium Error [current] [12025.958103] sd 7:0:0:0: [sdd] Add. Sense: Recorded entity not found [12025.958107] end_request: I/O error, dev sdd, sector 625142448 [12025.958110] Buffer I/O error on device sdd, logical block 625142448 [12025.965845] sd 7:0:0:0: [sdd] Result: hostbyte=DID_OK driverbyte=DRIVER_SENSE,SUGGEST_OK [12025.965849] sd 7:0:0:0: [sdd] Sense Key : Medium Error [current] [12025.965853] sd 7:0:0:0: [sdd] Add. Sense: Recorded entity not found [12025.965858] end_request: I/O error, dev sdd, sector 625142448 [12025.965861] Buffer I/O error on device sdd, logical block 625142448 [12025.968965] sd 7:0:0:0: [sdd] Result: hostbyte=DID_OK driverbyte=DRIVER_SENSE,SUGGEST_OK [12025.968969] sd 7:0:0:0: [sdd] Sense Key : Medium Error [current] [12025.968973] sd 7:0:0:0: [sdd] Add. Sense: Recorded entity not found [12025.968977] end_request: I/O error, dev sdd, sector 625142448 [12025.968980] Buffer I/O error on device sdd, logical block 625142448 [12025.972251] sd 7:0:0:0: [sdd] Result: hostbyte=DID_OK driverbyte=DRIVER_SENSE,SUGGEST_OK [12025.972255] sd 7:0:0:0: [sdd] Sense Key : Medium Error [current] [12025.972259] sd 7:0:0:0: [sdd] Add. Sense: Recorded entity not found [12025.972263] end_request: I/O error, dev sdd, sector 625142448 [12025.972267] Buffer I/O error on device sdd, logical block 625142448 [12025.985105] sd 7:0:0:0: [sdd] Result: hostbyte=DID_OK driverbyte=DRIVER_SENSE,SUGGEST_OK [12025.985109] sd 7:0:0:0: [sdd] Sense Key : Medium Error [current] [12025.985113] sd 7:0:0:0: [sdd] Add. Sense: Recorded entity not found [12025.985118] end_request: I/O error, dev sdd, sector 625142448 [12025.985121] Buffer I/O error on device sdd, logical block 625142448 [12025.988466] sd 7:0:0:0: [sdd] Result: hostbyte=DID_OK driverbyte=DRIVER_SENSE,SUGGEST_OK [12025.988470] sd 7:0:0:0: [sdd] Sense Key : Medium Error [current] [12025.988474] sd 7:0:0:0: [sdd] Add. Sense: Recorded entity not found [12025.988478] end_request: I/O error, dev sdd, sector 625142448 [12025.988481] Buffer I/O error on device sdd, logical block 625142448 lsusb for that device: Bus 001 Device 006: ID 05e3:0606 Genesys Logic, Inc. USB 2.0 Hub / D-Link DUB-H4 USB 2.0 Hub Device Descriptor: bLength18 bDescriptorType 1 bcdUSB 2.00 bDeviceClass9 Hub bDeviceSubClass 0 Unused bDeviceProtocol 1 Single TT bMaxPacketSize064 idVendor 0x05e3 Genesys Logic, Inc. idProduct 0x0606 USB 2.0 Hub / D-Link DUB-H4 USB 2.0 Hub bcdDevice7.02 iManufacturer 0 iProduct1 USB2.0 Hub iSerial 0 bNumConfigurations 1 Configuration Descriptor: bLength 9 bDescriptorType 2 wTotalLength 25 bNumInterfaces 1 bConfigurationValue 1 iConfiguration 0 bmAttributes 0xe0 Self Powered Remote Wakeup MaxPower 100mA Interface Descriptor: bLength 9 bDescriptorType 4 bInterfaceNumber0 bAlternateSetting 0 bNumEndpoints 1
[Bug 264789] Re: USB Hard Drive Not Accessible, vol_id hangs
lpad, can you add the lsusb information for the storage device? The part you supplied is for the integrated hub. -- 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 ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
Re: [Bug 264789] Re: USB Hard Drive Not Accessible, vol_id hangs
On 15/07/09 16:39 Stefan Bader wrote: @Gonzalo, I added some code that tries to fix up your device. The change is included in the test kernel of another bug. You can find it at http://people.canonical.com/~smb//bug287701/. Could you try whether that change helps? Thanks. I tried that patch with a Sony Ericson w800i mobile phone. It still doesn't work. -- 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 ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 264789] Re: USB Hard Drive Not Accessible, vol_id hangs
Doesnt work for me either. # uname -r 2.6.28-13-generic [12025.835546] sdd: sdd1 [12025.849684] sd 7:0:0:0: [sdd] Attached SCSI disk [12025.849866] sd 7:0:0:0: Attached scsi generic sg3 type 0 [12025.953475] sd 7:0:0:0: [sdd] Result: hostbyte=DID_OK driverbyte=DRIVER_SENSE,SUGGEST_OK [12025.953482] sd 7:0:0:0: [sdd] Sense Key : Medium Error [current] [12025.953487] sd 7:0:0:0: [sdd] Add. Sense: Recorded entity not found [12025.953493] end_request: I/O error, dev sdd, sector 625142448 [12025.953496] __ratelimit: 128944 callbacks suppressed [12025.953499] Buffer I/O error on device sdd, logical block 625142448 [12025.958095] sd 7:0:0:0: [sdd] Result: hostbyte=DID_OK driverbyte=DRIVER_SENSE,SUGGEST_OK [12025.958099] sd 7:0:0:0: [sdd] Sense Key : Medium Error [current] [12025.958103] sd 7:0:0:0: [sdd] Add. Sense: Recorded entity not found [12025.958107] end_request: I/O error, dev sdd, sector 625142448 [12025.958110] Buffer I/O error on device sdd, logical block 625142448 [12025.965845] sd 7:0:0:0: [sdd] Result: hostbyte=DID_OK driverbyte=DRIVER_SENSE,SUGGEST_OK [12025.965849] sd 7:0:0:0: [sdd] Sense Key : Medium Error [current] [12025.965853] sd 7:0:0:0: [sdd] Add. Sense: Recorded entity not found [12025.965858] end_request: I/O error, dev sdd, sector 625142448 [12025.965861] Buffer I/O error on device sdd, logical block 625142448 [12025.968965] sd 7:0:0:0: [sdd] Result: hostbyte=DID_OK driverbyte=DRIVER_SENSE,SUGGEST_OK [12025.968969] sd 7:0:0:0: [sdd] Sense Key : Medium Error [current] [12025.968973] sd 7:0:0:0: [sdd] Add. Sense: Recorded entity not found [12025.968977] end_request: I/O error, dev sdd, sector 625142448 [12025.968980] Buffer I/O error on device sdd, logical block 625142448 [12025.972251] sd 7:0:0:0: [sdd] Result: hostbyte=DID_OK driverbyte=DRIVER_SENSE,SUGGEST_OK [12025.972255] sd 7:0:0:0: [sdd] Sense Key : Medium Error [current] [12025.972259] sd 7:0:0:0: [sdd] Add. Sense: Recorded entity not found [12025.972263] end_request: I/O error, dev sdd, sector 625142448 [12025.972267] Buffer I/O error on device sdd, logical block 625142448 [12025.985105] sd 7:0:0:0: [sdd] Result: hostbyte=DID_OK driverbyte=DRIVER_SENSE,SUGGEST_OK [12025.985109] sd 7:0:0:0: [sdd] Sense Key : Medium Error [current] [12025.985113] sd 7:0:0:0: [sdd] Add. Sense: Recorded entity not found [12025.985118] end_request: I/O error, dev sdd, sector 625142448 [12025.985121] Buffer I/O error on device sdd, logical block 625142448 [12025.988466] sd 7:0:0:0: [sdd] Result: hostbyte=DID_OK driverbyte=DRIVER_SENSE,SUGGEST_OK [12025.988470] sd 7:0:0:0: [sdd] Sense Key : Medium Error [current] [12025.988474] sd 7:0:0:0: [sdd] Add. Sense: Recorded entity not found [12025.988478] end_request: I/O error, dev sdd, sector 625142448 [12025.988481] Buffer I/O error on device sdd, logical block 625142448 Even echo Y /sys/module/usbcore/parameters/old_scheme_first doesnt fix this... I see it was fixed in 2.6.29 kernel, but ubuntu uses 2.6.28 tree. Will it be fixed ever? Thanks. -- 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 ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 264789] Re: USB Hard Drive Not Accessible, vol_id hangs
same problem here with 2.6.28-13 kernel. real showstopper for me. -- 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 ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 264789] Re: USB Hard Drive Not Accessible, vol_id hangs
Using Ubuntu Jaunty Linux richard 2.6.28-13-generic #45-Ubuntu SMP Tue Jun 30 19:49:51 UTC 2009 i686 GNU/Linux I still have the same problem using Sony Ericsson w760i as a massive storage device. I get lot of this lines like: [ 176.583368] sd 7:0:0:1: [sdg] Sense Key : No Sense [current] [ 176.583375] sd 7:0:0:1: [sdg] Add. Sense: No additional sense information [ 176.586002] sd 7:0:0:0: [sdf] Sense Key : No Sense [current] [ 176.586007] sd 7:0:0:0: [sdf] Add. Sense: No additional sense information [ 176.610978] sd 7:0:0:1: [sdg] Sense Key : No Sense [current] [ 176.610985] sd 7:0:0:1: [sdg] Add. Sense: No additional sense information [ 176.613724] sd 7:0:0:0: [sdf] Sense Key : No Sense [current] (... and lots of similar lines...) result of lsusb -v Bus 001 Device 006: ID 0fce:e0c6 Sony Ericsson Mobile Communications AB Device Descriptor: bLength18 bDescriptorType 1 bcdUSB 2.00 bDeviceClass0 (Defined at Interface level) bDeviceSubClass 0 bDeviceProtocol 0 bMaxPacketSize064 idVendor 0x0fce Sony Ericsson Mobile Communications AB idProduct 0xe0c6 bcdDevice0.00 iManufacturer 1 Sony Ericsson iProduct2 Memory Stick iSerial 3 3592370205434140 bNumConfigurations 1 Configuration Descriptor: bLength 9 bDescriptorType 2 wTotalLength 32 bNumInterfaces 1 bConfigurationValue 2 iConfiguration 6 MSC Device bmAttributes 0x80 (Bus Powered) MaxPower 500mA Interface Descriptor: bLength 9 bDescriptorType 4 bInterfaceNumber0 bAlternateSetting 0 bNumEndpoints 2 bInterfaceClass 8 Mass Storage bInterfaceSubClass 6 SCSI bInterfaceProtocol 80 Bulk (Zip) iInterface 7 Sony Ericsson Memory Stick Endpoint Descriptor: bLength 7 bDescriptorType 5 bEndpointAddress 0x05 EP 5 OUT bmAttributes2 Transfer TypeBulk Synch Type None Usage Type Data wMaxPacketSize 0x0200 1x 512 bytes bInterval 0 Endpoint Descriptor: bLength 7 bDescriptorType 5 bEndpointAddress 0x85 EP 5 IN bmAttributes2 Transfer TypeBulk Synch Type None Usage Type Data wMaxPacketSize 0x0200 1x 512 bytes bInterval 0 Device Qualifier (for other device speed): bLength10 bDescriptorType 6 bcdUSB 2.00 bDeviceClass2 Communications bDeviceSubClass 0 bDeviceProtocol 0 bMaxPacketSize064 bNumConfigurations 4 Device Status: 0x (Bus Powered) -- 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 ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 264789] Re: USB Hard Drive Not Accessible, vol_id hangs
my USB device now works in the latest ubuntu kernel: 2.6.28-13-generic thanks everyone. jdawgaz -- 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 ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 264789] Re: USB Hard Drive Not Accessible, vol_id hangs
To clarify your clarification :) [1] current Jaunty means up to date with newest kernel update (released a few days ago) [2] you can install the KernelMainBuilds in your Jaunty system. -- 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 ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 264789] Re: USB Hard Drive Not Accessible, vol_id hangs
Thanks Tormod, think I was getting a little muddled up :) This can still be tested in Karmic also, based on the 2.6.30 kernel for reference. -- 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 ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 264789] Re: USB Hard Drive Not Accessible, vol_id hangs
I am unable to test this myself - unfortunately no access to a USB hard drive. -- 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 ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 264789] Re: USB Hard Drive Not Accessible, vol_id hangs
To be more precise here: in order to get any Jaunty SRU: 1. Check against current Jaunty 2. Compare against a recent https://wiki.ubuntu.com/KernelMainlineBuilds (2.6.30) 3. Report whether it works in 1. and/or 2. and supply lsusb -v output for the device -- 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 ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 264789] Re: USB Hard Drive Not Accessible, vol_id hangs
To clarify: [1] is definitely a no, as stated by previous users, so there is no need to report that back guys, and [2] if someone with this problem has any way of testing in Karmic, it would be a great help, as Karmic uses the 2.6.30 kernel as explained above - p.s I know it's in Alpha 2/3 state, but if anyone can then please do [3] also provide this information as stated by Stefan Thank you. -- 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 ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 264789] Re: USB Hard Drive Not Accessible, vol_id hangs
To see if this can be fixed in previous versions of Ubuntu, please do steps 1 and 2 of the SRU Procedure [1] to bring the need to a developer's attention. [1]: https://wiki.ubuntu.com/StableReleaseUpdates#Procedure That's all I can suggest really, thats the procedure to get this into an earlier version. -- 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 ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 264789] Re: USB Hard Drive Not Accessible, vol_id hangs
Yes, it was quite a fix ;) -- 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 ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 264789] Re: USB Hard Drive Not Accessible, vol_id hangs
According to the upstream bugtracker, this was only fixed in 2.6.29, therefore I believe the only version that will work with this issue will be Karmic onwards, as it currently uses the 2.6.30 kernel. I am not sure if this is being worked on to be backported, but that is why it has been marked as Fix Released. I think the best option is to wait until Karmic is released in October. :) -- 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 ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 264789] Re: USB Hard Drive Not Accessible, vol_id hangs
I wonder why apparently nothing is done about this bug? I think it is quite serious and defenetly a show stopper for new linux users, who doesn't wants to mingle around with virtualbox and other workarounds, just to acces their external drives. Also, it seems to be a fairly simple bug (based on the above and the fact that it actualy worked fine until 8.04). -- 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 ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 264789] Re: USB Hard Drive Not Accessible, vol_id hangs
Just confirming that my Intrepid (2.6.27-14-generic) still had this problem. After editing 60-persistent-storage.rules with the trick the problem with my Sony Ericsson K750i vanished. -- 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 ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 264789] Re: USB Hard Drive Not Accessible, vol_id hangs
I have had a similar problem. My external USB drive absolutely cannot be loaded in UBUNTU version 8.04 and version 9.04. In fact, version 9.04 does not even DETECT the external USB hard drive. In order to have access to my USB external hard drive, I have to use version 7.04. I wonder just what improvements were inserted, and what old code was removed in order to make versions 8.04 and 9.04 apparently totally incapable of detecting and loading my external USB hard drive. So for abandoned version of UBUNTU, because it is so superior to the newer versions. But I will definitely try the next new release, because perhaps those wonderful folks who know so much more than I do, will have fixed this persistent bug that appeared with version 8.04 and persists in the latest version. -- 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 ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 264789] Re: USB Hard Drive Not Accessible, vol_id hangs
Sony Ericsson C902 does not mount on Jaunty with all updates (not yet proposed). Neither in telephone nor in data mode. No problems on the same machine with Windows XP. Sony Ericsson K750i on the same machine and on the same cable does auto mount on Jaunty. -- 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 ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 264789] Re: USB Hard Drive Not Accessible, vol_id hangs
Same problem here (sense key: no sense) with an external Maxtor 5000DV in Jaunty. The 60-persistent-storage.rules did something. The drive actually mounted, but then locked everything that has to do with drives (places, commands like dmesg and fdisk all froze). So I removed them again. Are there any progress on this issue??? -- 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 ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 264789] Re: USB Hard Drive Not Accessible, vol_id hangs
Hi all
Same problem here with a Nokia 5310 Xpress Music:
sa...@hal-9000:/etc/udev/rules.d$ uname -a
Linux hal-9000 2.6.27-11-generic #1 SMP Wed Apr 1 20:57:48 UTC 2009 i686
GNU/Linux
sa...@hal-9000:/etc/udev/rules.d$ vi /var/log/messages:
May 10 14:14:30 hal-9000 kernel: [ 3556.916044] usb 2-6: new full speed USB
device using ohci_hcd and address 24
May 10 14:14:30 hal-9000 kernel: [ 3557.154936] usb 2-6: configuration #1
chosen from 1 choice
May 10 14:14:30 hal-9000 kernel: [ 3557.208892] cdc_acm 2-6:1.1: ttyACM0: USB
ACM device
May 10 14:14:30 hal-9000 kernel: [ 3557.221002] usb 2-6: bad CDC descriptors
May 10 14:14:30 hal-9000 kernel: [ 3557.228741] usb 2-6: bad CDC descriptors
May 10 14:14:30 hal-9000 kernel: [ 3557.411673] usb 2-6: USB disconnect,
address 24
May 10 14:15:27 hal-9000 kernel: [ 3614.136117] usb 2-6: new full speed USB
device using ohci_hcd and address 25
May 10 14:15:27 hal-9000 kernel: [ 3614.376173] usb 2-6: configuration #1
chosen from 1 choice
May 10 14:15:27 hal-9000 kernel: [ 3614.429912] cdc_acm 2-6:1.1: ttyACM0: USB
ACM device
May 10 14:15:27 hal-9000 kernel: [ 3614.437000] usb 2-6: bad CDC descriptors
May 10 14:15:27 hal-9000 kernel: [ 3614.444908] usb 2-6: bad CDC descriptors
May 10 14:15:29 hal-9000 kernel: [ 3616.124667] usb 2-6: USB disconnect,
address 25
May 10 14:15:30 hal-9000 kernel: [ 3616.884036] usb 2-6: new full speed USB
device using ohci_hcd and address 26
May 10 14:15:30 hal-9000 kernel: [ 3617.118667] usb 2-6: configuration #1
chosen from 1 choice
May 10 14:15:30 hal-9000 kernel: [ 3617.140048] scsi15 : SCSI emulation for USB
Mass Storage devices
May 10 14:15:35 hal-9000 kernel: [ 3622.148738] scsi 15:0:0:0: Direct-Access
NokiaNokia 5310 Xpres PQ: 0 ANSI: 4
May 10 14:15:35 hal-9000 kernel: [ 3622.180073] sd 15:0:0:0: [sdc] 3862529
512-byte hardware sectors (1978 MB)
May 10 14:15:35 hal-9000 kernel: [ 3622.208732] sd 15:0:0:0: [sdc] Write
Protect is off
May 10 14:15:35 hal-9000 kernel: [ 3622.234865] sd 15:0:0:0: [sdc] 3862529
512-byte hardware sectors (1978 MB)
May 10 14:15:35 hal-9000 kernel: [ 3622.241803] sd 15:0:0:0: [sdc] Write
Protect is off
May 10 14:15:35 hal-9000 kernel: [ 3622.242715] sdc:
May 10 14:15:35 hal-9000 kernel: [ 3622.456540] sd 15:0:0:0: [sdc] Attached
SCSI removable disk
May 10 14:15:35 hal-9000 kernel: [ 3622.457580] sd 15:0:0:0: Attached scsi
generic sg4 type 0
May 10 14:15:36 hal-9000 kernel: [ 3622.817691] sd 15:0:0:0: [sdc] Sense Key :
No Sense [current]
May 10 14:15:36 hal-9000 kernel: [ 3622.817705] sd 15:0:0:0: [sdc] Add. Sense:
No additional sense information
The patched version of 60-persistent-storage.rules dind't work, neither adding
the ENV{DEVTYPE}=partition workaround.
Somebody has other suggestion to try to figure out how to use my phone's
data ?
Thanks.
--
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
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
Re: [Bug 264789] Re: USB Hard Drive Not Accessible, vol_id hangs
I still have this problem as well. On Sat, May 2, 2009 at 10:09 PM, Leon l...@tim-online.nl wrote: I'm still having this problem. I tried the 2.6.28-11-generic kernel and a mainline build. But with both I can't get rid of this nasty bug. -- USB Hard Drive Not Accessible, vol_id hangs https://bugs.launchpad.net/bugs/264789 You received this bug notification because you are a direct subscriber of the bug. -- 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 ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 264789] Re: USB Hard Drive Not Accessible, vol_id hangs
I'm still having this problem. I tried the 2.6.28-11-generic kernel and a mainline build. But with both I can't get rid of this nasty bug. -- 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 ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 264789] Re: USB Hard Drive Not Accessible, vol_id hangs
I updated to Jaunty Desktop rc and my external drive is working again. uname -a Linux 2.6.28-11-generic #42-Ubuntu SMP Fri Apr 17 01:58:03 UTC 2009 x86_64 GNU/Linux -- 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 ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 264789] Re: USB Hard Drive Not Accessible, vol_id hangs
The .deb's from kernel.org are a straight forward install. I am unaware of .deb's at kernel.org, but until karmic kernels are built, you can look at https://wiki.ubuntu.com/KernelMainlineBuilds for some options -- 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 ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 264789] Re: USB Hard Drive Not Accessible, vol_id hangs
I'm still having the problem with: 2.6.28-11-server #42-Ubuntu SMP Fri Apr 17 02:45:36 UTC 2009 x86_64 GNU/Linux -- 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 ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 264789] Re: USB Hard Drive Not Accessible, vol_id hangs
@FireMan300 : do you have a link? I can't find the debs on kernel.org. I'm still having the same problems with: 2.6.28-11-server #41-Ubuntu SMP Wed Apr 8 05:29:01 UTC 2009 x86_64 and a 067b:3507 drive. -- 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 ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 264789] Re: USB Hard Drive Not Accessible, vol_id hangs
FYI - I installed the beta Ubuntu 9.04 (jaunty) w/ the 2.6.28-11 kernel, the SenseKey problem with my external USB drive has gone away. The drive is working as before. -- 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 ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 264789] Re: USB Hard Drive Not Accessible, vol_id hangs
Well two things: 1. Has this been tested under Ubuntu 9.4 Jaunty? i.e is it fixed in the Ubuntu 2.6.28 kernels? 2. I can confirm that in Kernel 2.6.29 from kernel.org (stable 64-bit) the drive (2116:0320) works. The .deb's from kernel.org are a straight forward install. -- 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 ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 264789] Re: USB Hard Drive Not Accessible, vol_id hangs
I cant use my SE C905 phone right now. When can I see a fix release into my installation?! -- 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 ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 264789] Re: USB Hard Drive Not Accessible, vol_id hangs
How should I work around it for the moment? -- 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 ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
R: [Bug 264789] Re: USB Hard Drive Not Accessible, vol_id hangs
You could try using the old kernel 2.6.24-23, in my case (Nokia Phone 5220) it works. Messaggio originale Da: f...@kth.se Data: 02/04/2009 19.11 A: mario.picc...@libero.it Ogg: [Bug 264789] Re: USB Hard Drive Not Accessible, vol_id hangs How should I work around it for the moment? -- USB Hard Drive Not Accessible, vol_id hangs https://bugs.launchpad. net/bugs/264789 You received this bug notification because you are a direct subscriber of a duplicate bug. Status in The Linux Kernel: Fix Released Status in “linux” source package in Ubuntu: Fix Released Status in linux in Ubuntu Intrepid: Fix Committed Bug description: I updated to 2.6.27-2 today, and one of my hard drives is no longer recognized. It is in a Vantec NexStar GX enclosure, and was working fine on .26, and continues to work fine on a Hardy machine. Here is the dmesg for it: [ 6722.944029] usb 5-5: new high speed USB device using ehci_hcd and address 27 [ 6723.077863] usb 5-5: configuration #1 chosen from 1 choice [ 6723.079511] hub 5-5:1.0: USB hub found [ 6723.080345] hub 5-5:1.0: 4 ports detected [ 6732.712034] usb 5-5: reset high speed USB device using ehci_hcd and address 27 [ 6733.124011] usb 5- 5.1: new high speed USB device using ehci_hcd and address 28 [ 6733.364598] usb 5-5.1: configuration #1 chosen from 1 choice [ 6733.365180] scsi17 : SCSI emulation for USB Mass Storage devices [ 6733.365818] usb-storage: device found at 28 [ 6733.365830] usb-storage: waiting for device to settle before scanning [ 6738.364276] usb-storage: device scan complete [ 6738.361002] scsi 17:0:0:0: Direct-Access ST340063 2A 3.04 PQ: 0 ANSI: 0 [ 6738.361002] sd 17:0:0:0: [sdm] 781422769 512-byte hardware sectors (400088 MB) [ 6738.361002] sd 17:0:0:0: [sdm] Write Protect is off [ 6738.361002] sd 17:0: 0:0: [sdm] Mode Sense: 03 00 00 00 [ 6738.361002] sd 17:0:0:0: [sdm] Assuming drive cache: write through [ 6738.361002] sd 17:0:0:0: [sdm] 781422769 512- byte hardware sectors (400088 MB) [ 6738.370354] sd 17:0:0:0: [sdm] Write Protect is off [ 6738.370362] sd 17:0:0:0: [sdm] Mode Sense: 03 00 00 00 [ 6738.370365] sd 17:0:0:0: [sdm] Assuming drive cache: write through [ 6738.371516] sdm: sdm1 [ 6738.418089] sd 17:0:0:0: [sdm] Attached SCSI disk [ 6738.418995] sd 17:0:0:0: Attached scsi generic sg8 type 0 [ 6738.656598] sd 17:0:0:0: [sdm] Sense Key : No Sense [current] [ 6738.656614] sd 17:0:0:0: [sdm] Add. Sense: No additional sense information From there, the last 2 lines about Sense Key and Add Sense repeat over and over again. The 4 port hub that is a part of the enclosure continues to work fine though, with a floppy drive, a printer, and another hard drive. I have a Vantec NexStar 3 enclosure as well, and it is working just fine. Dmesg for the working enclosure: [ 4281.996024] usb 5-3: new high speed USB device using ehci_hcd and address 19 [ 4282.131863] usb 5-3: configuration #1 chosen from 1 choice [ 4282.133222] scsi12 : SCSI emulation for USB Mass Storage devices [ 4282.133561] usb-storage: device found at 19 [ 4282.133566] usb-storage: waiting for device to settle before scanning [ 4287.132002] usb-storage: device scan complete [ 4287.136004] scsi 12:0:0:0: Direct-Access ST375064 0AS PQ: 0 ANSI: 2 [ 4287.138368] sd 12:0:0:0: [sdi] 1465149168 512-byte hardware sectors (750156 MB) [ 4287.144790] sd 12:0:0:0: [sdi] Write Protect is off [ 4287.144800] sd 12:0:0:0: [sdi] Mode Sense: 38 00 00 00 [ 4287.144804] sd 12:0:0:0: [sdi] Assuming drive cache: write through [ 4287.152388] sd 12:0:0:0: [sdi] 1465149168 512-byte hardware sectors (750156 MB) [ 4287.154966] sd 12:0:0:0: [sdi] Write Protect is off [ 4287.154975] sd 12:0:0:0: [sdi] Mode Sense: 38 00 00 00 [ 4287.154979] sd 12:0:0:0: [sdi] Assuming drive cache: write through [ 4287.154988] sdi: sdi1 [ 4287.176965] sd 12:0:0:0: [sdi] Attached SCSI disk [ 4287.177173] sd 12:0:0:0: Attached scsi generic sg7 type 0 [ 4289.129138] kjournald starting. Commit interval 5 seconds [ 4289.130101] EXT3 FS on sdi1, internal journal [ 4289.130110] EXT3- fs: mounted filesystem with ordered data mode. -- 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 ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 264789] Re: USB Hard Drive Not Accessible, vol_id hangs
The bug status for Intrepid says Fix commited. But what is the estimated time of Fix released? Jarl -- 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 ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
Re: [Bug 264789] Re: USB Hard Drive Not Accessible, vol_id hangs
On 28/02/09 16:35 Malcolm Lalkaka wrote: This bug is in the upstream kernel, meaning it is not specific to the Ubuntu distribution; I believe Fedora, for example, has been having this problem too. The latest version of Debian, version 5.0, may not have this problem because it contains kernel version 2.6.28. It's also a problem in Debian 5.0. -- 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 ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 264789] Re: USB Hard Drive Not Accessible, vol_id hangs
Same problem with an external USB Hitachi HDD (250GB), but work fine with a 4GB USB key. kernel : 2.6.27-11-generic ; Distrib : Kubuntu intrepid I think this problem exist for all HDD 80GB. And I wonder why it was not yet fixed if it is just a udev rule to change !! Moreover this bug exist for 6 month I think !! Thank you *buntu (ubuntu, kubuntu ...) to make me win so much time. I think I will go to a pure debian. -- 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 ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 264789] Re: USB Hard Drive Not Accessible, vol_id hangs
This bug does not only affect USB hard drives larger than 80 GB. I have a Nokia 5200 cell phone with a 1 GB SD card in it that also suffers from this problem when connect the phone as a USB mass storage device. I am running Ubuntu 8.10, Intrepid Ibex (kernel version 2.6.27-11-generic). This worked on older versions of Ubuntu. Changing the udev rule as specified above did not fix the problem for me. Furthermore, by looking at other people's comments, it seems that changing that udev rule just masks a larger problem, and causes more problems for other hardware. This bug is in the upstream kernel, meaning it is not specific to the Ubuntu distribution; I believe Fedora, for example, has been having this problem too. The latest version of Debian, version 5.0, may not have this problem because it contains kernel version 2.6.28. -- 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 ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 264789] Re: USB Hard Drive Not Accessible, vol_id hangs
Ok, so it is a problem at kernel level. Does a bug is open at kernel.org or something like that ? Since it was working with a 2.6.24-21-generic, they should be able to correct this bug quickly,isn't it ? -- 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 ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 264789] Re: USB Hard Drive Not Accessible, vol_id hangs
In fact it's a bug in your USB device (and in many many other too) Your USB device does return the wrong size information (1 too large) The kernel bug is http://bugzilla.kernel.org/show_bug.cgi?id=11843 which is the effort to work arround the bug in the usb devices. It did work because older kernels did not try to read the last block in the past, now they try to read the last block of the device (the one the USB did tell the kernel is the last block) But the device then rejects that request, the kernel retrys, and retrys and retrys... -- 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 ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 264789] Re: USB Hard Drive Not Accessible, vol_id hangs
getting the same bug in intrepid 64bit 2.6.27-11-generic with a nokia 5310 Xpm -- 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 ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 264789] Re: USB Hard Drive Not Accessible, vol_id hangs
Instead of having a (always incomplete/outdated) blacklist, perhaps the kernel can try to auto detect that error... ? Is it (almost) always so, that the capacity is returned a one sector too large ? -- 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 ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
Re: [Bug 264789] Re: USB Hard Drive Not Accessible, vol_id hangs
Actually, this fix makes it so that partitions mounted by volume id in
/etc/fstab aren't mountable.
On 16/02/09 17:18 Robert Rothenberg wrote:
This also works with my Sony Ericsson W800i.
I also note that this fix works on Debian Lenny, so it should be
reported upstream.
On 16/02/09 16:43 Ketil Malde wrote:
I had similar problems mounting my Sony Ericsson C702 on Ubuntu 8.10. I
edited /etc/udev/rules.d/60-persistent-storage.rules, commenting out the
line looking like:
IMPORT{program}=vol_id --export $tempnode
and after that change, I could then mount it as a normal USB disk.
I really hope this will be fixed soon, USB mass storage is old enough
that it should Just Work (tm).
--
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
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 264789] Re: USB Hard Drive Not Accessible, vol_id hangs
... and renders dm fakeraid installations unbootable. It is NOT the correct fix. The correct fix is to remove the infinite retry loop from the kernel SCSI error code and blacklist all the bad devices so the kernel knows that they return a capacity value that is one sector too large. Sadly the latter is going to be seriously painful because this brokenness seems to be incredibly widespread. -- 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 ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 264789] Re: USB Hard Drive Not Accessible, vol_id hangs
I had similar problems mounting my Sony Ericsson C702 on Ubuntu 8.10. I
edited /etc/udev/rules.d/60-persistent-storage.rules, commenting out the
line looking like:
IMPORT{program}=vol_id --export $tempnode
and after that change, I could then mount it as a normal USB disk.
I really hope this will be fixed soon, USB mass storage is old enough
that it should Just Work (tm).
--
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
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
Re: [Bug 264789] Re: USB Hard Drive Not Accessible, vol_id hangs
This also works with my Sony Ericsson W800i.
I also note that this fix works on Debian Lenny, so it should be reported
upstream.
On 16/02/09 16:43 Ketil Malde wrote:
I had similar problems mounting my Sony Ericsson C702 on Ubuntu 8.10. I
edited /etc/udev/rules.d/60-persistent-storage.rules, commenting out the
line looking like:
IMPORT{program}=vol_id --export $tempnode
and after that change, I could then mount it as a normal USB disk.
I really hope this will be fixed soon, USB mass storage is old enough
that it should Just Work (tm).
--
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
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 264789] Re: USB Hard Drive Not Accessible, vol_id hangs
I still having this bug too with Nokia 6230i. It renders Ubuntu almost unusable for me, since the phone is always with me, so it's great than to carry my all data on it (no other pendrives etc are needed), photos/musics, etc, so it would be a must every time for me, but I can't use Ubuntu Intrepid to acess the mmc card of the phone. I had to install an older version of Ubuntu on the other PC to be able to access it, and it's not the best solution I guess :( -- 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 ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
Re: [Bug 264789] Re: USB Hard Drive Not Accessible, vol_id hangs
My solution is to use kernel from HH. It works for me. I have newer apps and usable usb phone and pendrive connection. Dear hackers, please tell me about drawbacks of my solution. Is there any danger? :) -- 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 ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 264789] Re: USB Hard Drive Not Accessible, vol_id hangs
I'm using 2.6.27-11 and still unable to mount a Sony Ericson 800i that I used to be able to mount in Hardy. -- 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 ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 264789] Re: USB Hard Drive Not Accessible, vol_id hangs
Still getting these errors with 2.6.27-11 from intrepid-updates: [ 327.945908] sd 9:0:0:0: [sdc] Sense Key : No Sense [current] [ 327.945913] sd 9:0:0:0: [sdc] Add. Sense: No additional sense information [ 327.949057] sd 9:0:0:1: [sdd] Sense Key : No Sense [current] [ 327.949063] sd 9:0:0:1: [sdd] Add. Sense: No additional sense information With the latest updates, the system will even hang at boot when I have a DVD in my dvd drive. The above error messages are from attaching a Sony Ericsson W760 mobile phone. -- 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 ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 264789] Re: USB Hard Drive Not Accessible, vol_id hangs
Based on the feedback reported, it looks like verification has failed to me, marking as such. According to the upstream bugreport, this issue should be fixed in 2.6.28, which is what Jaunty's kernel is based on. I'm closing that portion of the bug, but it would be great if someone affected by this issue could confirm that the jaunty kernel fixes it for them. Thanks. ** Changed in: linux (Ubuntu) Status: Triaged = Fix Released ** Tags added: verification-failed ** Tags removed: verification-needed -- 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 ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 264789] Re: USB Hard Drive Not Accessible, vol_id hangs
Correct, I have installed 2.6.28-4 and 2.6.28-5(currently) and the problems I had with the external drive not working are gone. r...@kaput:~# uname -a Linux Kaput 2.6.28-5-generic #13-Ubuntu SMP Wed Jan 21 21:54:44 UTC 2009 x86_64 GNU/Linux r...@kaput:~# dpkg -l | grep linux-image-2.6.28- ii linux-image-2.6.28-4-generic 2.6.28-4.11 Linux kernel image for version 2.6.28 on x86 ii linux-image-2.6.28-5-generic 2.6.28-5.13 Linux kernel image for version 2.6.28 on x86 Relevant Syslog: - Jan 23 18:09:18 Kaput kernel: [ 8656.484103] usb 2-3: new high speed USB device using ehci_hcd and address 3 Jan 23 18:09:18 Kaput kernel: [ 8656.632932] usb 2-3: configuration #1 chosen from 1 choice Jan 23 18:09:18 Kaput kernel: [ 8656.710585] Initializing USB Mass Storage driver... Jan 23 18:09:18 Kaput kernel: [ 8656.725414] scsi5 : SCSI emulation for USB Mass Storage devices Jan 23 18:09:18 Kaput kernel: [ 8656.749068] usb-storage: device found at 3 Jan 23 18:09:18 Kaput kernel: [ 8656.749071] usb-storage: waiting for device to settle before scanning Jan 23 18:09:18 Kaput kernel: [ 8656.749094] usbcore: registered new interface driver usb-storage Jan 23 18:09:18 Kaput kernel: [ 8656.749098] USB Mass Storage support registered. Jan 23 18:09:23 Kaput kernel: [ 8661.748499] usb-storage: device scan complete Jan 23 18:09:25 Kaput kernel: [ 8663.218597] scsi 5:0:0:0: Direct-Access Maxtor OneTouch III 0364 PQ: 0 ANSI: 4 Jan 23 18:09:25 Kaput kernel: [ 8663.400660] sd 5:0:0:0: [sdb] 117210240 512-byte hardware sectors: (60.0 GB/55.8 GiB) Jan 23 18:09:25 Kaput kernel: [ 8663.401649] sd 5:0:0:0: [sdb] Write Protect is off Jan 23 18:09:25 Kaput kernel: [ 8663.401655] sd 5:0:0:0: [sdb] Mode Sense: 17 00 00 00 Jan 23 18:09:25 Kaput kernel: [ 8663.401660] sd 5:0:0:0: [sdb] Assuming drive cache: write through Jan 23 18:09:25 Kaput kernel: [ 8663.402651] sd 5:0:0:0: [sdb] 117210240 512-byte hardware sectors: (60.0 GB/55.8 GiB) Jan 23 18:09:25 Kaput kernel: [ 8663.403648] sd 5:0:0:0: [sdb] Write Protect is off Jan 23 18:09:25 Kaput kernel: [ 8663.403653] sd 5:0:0:0: [sdb] Mode Sense: 17 00 00 00 Jan 23 18:09:25 Kaput kernel: [ 8663.403657] sd 5:0:0:0: [sdb] Assuming drive cache: write through Jan 23 18:09:25 Kaput kernel: [ 8663.403664] sdb: sdb1 Jan 23 18:09:25 Kaput kernel: [ 8663.415353] sd 5:0:0:0: [sdb] Attached SCSI disk Jan 23 18:09:25 Kaput kernel: [ 8663.415491] sd 5:0:0:0: Attached scsi generic sg2 type 0 Jan 23 18:09:26 Kaput ntfs-3g[13971]: Version 1.2506 external FUSE 27 Jan 23 18:09:26 Kaput ntfs-3g[13971]: Mounted /dev/sdb1 (Read-Write, label OneTouch, NTFS 3.1) Jan 23 18:09:26 Kaput ntfs-3g[13971]: Cmdline options: rw,nosuid,nodev,uhelper=hal,locale=en_US.UTF-8 Jan 23 18:09:26 Kaput ntfs-3g[13971]: Mount options: rw,nosuid,nodev,uhelper=hal,silent,allow_other,nonempty,relatime,fsname=/dev/sdb1,blkdev,blksize=4096 Jan 23 18:09:26 Kaput hald: mounted /dev/sdb1 on behalf of uid 1000 -- 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 ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 264789] Re: USB Hard Drive Not Accessible, vol_id hangs
same problem here with an external usb hard disk. perfectly works under windows or after removing ehci_hcd (SLOW!). udev patch doesn't solve. dmesg: usb 1-6: reset high speed USB device using ehci_hcd and address 3 usb 1-6: reset high speed USB device using ehci_hcd and address 3 usb 1-6: reset high speed USB device using ehci_hcd and address 3 usb 1-6: reset high speed USB device using ehci_hcd and address 3 usb 1-6: reset high speed USB device using ehci_hcd and address 3 usb 1-6: reset high speed USB device using ehci_hcd and address 3 usb 1-6: reset high speed USB device using ehci_hcd and address 3 usb 1-6: reset high speed USB device using ehci_hcd and address 3 usb 1-6: reset high speed USB device using ehci_hcd and address 3 lsusb: Bus 001 Device 003: ID 067b:2507 Prolific Technology, Inc. PL2507 Hi-speed USB to IDE bridge controller Device Descriptor: bLength18 bDescriptorType 1 bcdUSB 2.00 bDeviceClass0 (Defined at Interface level) bDeviceSubClass 0 bDeviceProtocol 0 bMaxPacketSize064 idVendor 0x067b Prolific Technology, Inc. idProduct 0x2507 PL2507 Hi-speed USB to IDE bridge controller bcdDevice1.00 iManufacturer 1 iProduct2 iSerial 3 bNumConfigurations 1 Configuration Descriptor: bLength 9 bDescriptorType 2 wTotalLength 32 bNumInterfaces 1 bConfigurationValue 1 iConfiguration 0 bmAttributes 0xc0 Self Powered MaxPower 100mA Interface Descriptor: bLength 9 bDescriptorType 4 bInterfaceNumber0 bAlternateSetting 0 bNumEndpoints 2 bInterfaceClass 8 Mass Storage bInterfaceSubClass 6 SCSI bInterfaceProtocol 80 Bulk (Zip) iInterface 0 Endpoint Descriptor: bLength 7 bDescriptorType 5 bEndpointAddress 0x01 EP 1 OUT bmAttributes2 Transfer TypeBulk Synch Type None Usage Type Data wMaxPacketSize 0x0200 1x 512 bytes bInterval 0 Endpoint Descriptor: bLength 7 bDescriptorType 5 bEndpointAddress 0x82 EP 2 IN bmAttributes2 Transfer TypeBulk Synch Type None Usage Type Data wMaxPacketSize 0x0200 1x 512 bytes bInterval 0 -- 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 ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 264789] Re: USB Hard Drive Not Accessible, vol_id hangs
@Tim Wright I assume when you say 'don't do that' you mean, don't submit the bug fix? As opposed to 'don't make the change to your config'. The changes suggested to 60-persistent-storage.rules worked an absolute treat for me. I understand that you want the correct fix in the kernel for both the infinite loop and the device exceptions, but the pragmatic thing to do as of now, would be to suggest those affected by the bug make the change. Unless of course there is a danger in doing so! I went from a deathly slow-booting computer, with processes locked in a loop eating my CPU and no access to my USB drives, to a fully functioning Ubuntu install. I had tried multiple kernels and added repositories I wish I hadn't in vain to try and fix the issue. I have backed up the edited file. Does this file get overwritten by updates? (i.e. new kernels) If so, an update that fixes the issue (i.e. a new kernel) should also correct the file, no? Thanks all, and regards, Paul McConnon -- 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 ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 264789] Re: USB Hard Drive Not Accessible, vol_id hangs
I have the same problem with my log files being filled with the following... Jan 8 19:30:36 media-linux kernel: [ 525.910359] sd 4:0:0:0: [sdb] Sense Key : No Sense [current] Jan 8 19:30:36 media-linux kernel: [ 525.910367] sd 4:0:0:0: [sdb] Add. Sense: No additional sense information for 100's of megabytes. The logs will continually grow until I kill dd and klogd (which eat all my CPU). The computer is a HP mediacenter 1170.uk, with an internal USB drive (in an enclosure) I am running Intrepid and the bug occurs in kernel 27-9 and 27-11. No idea what to do. First time I've ever been bitten doing an upgrade in Ubuntu. 8.04 worked absolutely fine. Regards, Paul -- 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 ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 264789] Re: USB Hard Drive Not Accessible, vol_id hangs
This usb bridge is affected by the bug too. Bus 007 Device 004: ID 152d:2338 JMicron Technology Corp. / JMicron USA Technology Corp. JM20337 Hi-Speed USB to SATA PATA Combo Bridge Device Descriptor: bLength18 bDescriptorType 1 bcdUSB 2.00 bDeviceClass0 (Defined at Interface level) bDeviceSubClass 0 bDeviceProtocol 0 bMaxPacketSize064 idVendor 0x152d JMicron Technology Corp. / JMicron USA Technology Corp. idProduct 0x2338 JM20337 Hi-Speed USB to SATA PATA Combo Bridge bcdDevice1.00 iManufacturer 1 JMicron iProduct2 USB to ATA/ATAPI Bridge iSerial 5 31354D718300 bNumConfigurations 1 Configuration Descriptor: bLength 9 bDescriptorType 2 wTotalLength 32 bNumInterfaces 1 bConfigurationValue 1 iConfiguration 4 USB Mass Storage bmAttributes 0xc0 Self Powered MaxPower2mA Interface Descriptor: bLength 9 bDescriptorType 4 bInterfaceNumber0 bAlternateSetting 0 bNumEndpoints 2 bInterfaceClass 8 Mass Storage bInterfaceSubClass 6 SCSI bInterfaceProtocol 80 Bulk (Zip) iInterface 6 MSC Bulk-Only Transfer
[Bug 264789] Re: USB Hard Drive Not Accessible, vol_id hangs
Another device for the list: Sony Ericsson K850i mobile phone. It used to work for some time with Ubuntu 8.04 but I don't remember at which kernel update. Upgrading to 8.10 didn't work, obviously. Editing 60 -persistent-storage.rules and replacing 40-permissions.rules doesn't seem to work either: Dmesg: [10575.848048] usb 1-1: new high speed USB device using ehci_hcd and address 34 [10576.062586] usb 1-1: configuration #2 chosen from 1 choice [10576.067535] scsi29 : SCSI emulation for USB Mass Storage devices [10576.072052] usb-storage: device found at 34 [10576.072062] usb-storage: waiting for device to settle before scanning [10581.072812] usb-storage: device scan complete [10581.075782] scsi 29:0:0:0: Direct-Access Sony Eri Memory Stick0 PQ: 0 ANSI: 0 [10581.077515] scsi 29:0:0:1: Direct-Access Sony Eri Memory Stick0 PQ: 0 ANSI: 0 [10581.089449] sd 29:0:0:0: [sdc] Attached SCSI removable disk [10581.090242] sd 29:0:0:0: Attached scsi generic sg4 type 0 [10581.096345] sd 29:0:0:1: [sdd] Attached SCSI removable disk [10581.097089] sd 29:0:0:1: Attached scsi generic sg5 type 0 [10581.959637] sd 29:0:0:1: [sdd] 7959552 512-byte hardware sectors (4075 MB) [10581.964026] sd 29:0:0:1: [sdd] Test WP failed, assume Write Enabled [10581.964037] sd 29:0:0:1: [sdd] Assuming drive cache: write through [10581.966248] sd 29:0:0:1: [sdd] 7959552 512-byte hardware sectors (4075 MB) [10581.970016] sd 29:0:0:1: [sdd] Test WP failed, assume Write Enabled [10581.970028] sd 29:0:0:1: [sdd] Assuming drive cache: write through [10581.973732] sdd: sdd1 [10582.895138] sd 29:0:0:0: [sdc] 128093 512-byte hardware sectors (66 MB) [10582.900267] sd 29:0:0:0: [sdc] Test WP failed, assume Write Enabled [10582.900283] sd 29:0:0:0: [sdc] Assuming drive cache: write through [10582.906830] sd 29:0:0:0: [sdc] 128093 512-byte hardware sectors (66 MB) [10582.910511] sd 29:0:0:0: [sdc] Test WP failed, assume Write Enabled [10582.910524] sd 29:0:0:0: [sdc] Assuming drive cache: write through [10582.910533] sdc: sdc1 [10613.116044] usb 1-1: reset high speed USB device using ehci_hcd and address 34 [10643.372049] usb 1-1: reset high speed USB device using ehci_hcd and address 34 [10673.692049] usb 1-1: reset high speed USB device using ehci_hcd and address 34 [10704.004053] usb 1-1: reset high speed USB device using ehci_hcd and address 34 [10734.280045] usb 1-1: reset high speed USB device using ehci_hcd and address 34 [10764.596076] usb 1-1: reset high speed USB device using ehci_hcd and address 34 [10764.804697] sd 29:0:0:0: [sdc] Result: hostbyte=DID_ABORT driverbyte=DRIVER_OK,SUGGEST_OK [10764.804713] end_request: I/O error, dev sdc, sector 128072 [10764.804722] __ratelimit: 260 callbacks suppressed [10764.804727] Buffer I/O error on device sdc, logical block 128072 [10764.804735] Buffer I/O error on device sdc, logical block 128073 [10764.804740] Buffer I/O error on device sdc, logical block 128074 [10764.804745] Buffer I/O error on device sdc, logical block 128075 [10764.804750] Buffer I/O error on device sdc, logical block 128076 [10764.804755] Buffer I/O error on device sdc, logical block 128077 [10764.804760] Buffer I/O error on device sdc, logical block 128078 [10764.804765] Buffer I/O error on device sdc, logical block 128079 [10794.944050] usb 1-1: reset high speed USB device using ehci_hcd and address 34 [10825.256050] usb 1-1: reset high speed USB device using ehci_hcd and address 34 [10855.524051] usb 1-1: reset high speed USB device using ehci_hcd and address 34 [10885.804053] usb 1-1: reset high speed USB device using ehci_hcd and address 34 [10916.064041] usb 1-1: reset high speed USB device using ehci_hcd and address 34 [10946.344102] usb 1-1: reset high speed USB device using ehci_hcd and address 34 [10946.512391] sd 29:0:0:0: [sdc] Result: hostbyte=DID_ABORT driverbyte=DRIVER_OK,SUGGEST_OK [10946.512407] end_request: I/O error, dev sdc, sector 128072 [10946.512417] Buffer I/O error on device sdc, logical block 128072 [10946.512425] Buffer I/O error on device sdc, logical block 128073 [10946.512430] Buffer I/O error on device sdc, logical block 128074 [10946.512435] Buffer I/O error on device sdc, logical block 128075 [10946.512440] Buffer I/O error on device sdc, logical block 128076 [10946.512445] Buffer I/O error on device sdc, logical block 128077 [10946.512450] Buffer I/O error on device sdc, logical block 128078 [10946.512455] Buffer I/O error on device sdc, logical block 128079 [10976.652055] usb 1-1: reset high speed USB device using ehci_hcd and address 34 [10991.764042] usb 1-1: device descriptor read/64, error -110 [11006.980060] usb 1-1: device descriptor read/64, error -110 [11007.196044] usb 1-1: reset high speed USB device using ehci_hcd and address 34 [11022.308049] usb 1-1: device descriptor read/64, error -110 [11037.524053] usb 1-1: device descriptor read/64, error -110 [11037.740044] usb 1-1: reset high speed USB device using ehci_hcd and address 34
[Bug 264789] Re: USB Hard Drive Not Accessible, vol_id hangs
See https://bugzilla.redhat.com/show_bug.cgi?id=473017 Its a problem with udev. See comment #3 on the list for the workaround -- 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 ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 264789] Re: USB Hard Drive Not Accessible, vol_id hangs
Thanks kja999, it works for me ! I've followed the bug on redhat's bugzilla and I've fixed udev's rules, I'm attaching the patch for an up to date intrepid, based on upstream udev tree: http://git.kernel.org/?p=linux/hotplug/udev.git;a=blobdiff;f=etc/udev/rules.d/60 -persistent- storage.rules;h=85a9270027b9ea06e11e1fa125cdef45bb1aa3a5;hp=a1e0917ab55ac9f8d234fc57c412e4f2b846eec3;hb=41677cf51fb2c14aa512ecf9410e43eb35560408;hpb=803ac7a6d8d06787305a01a068c2e0ca47e2536d No further changes are needed (no need to update the kernel), only /etc/init.d/udev restart after applying the patch. IMHO, this issue is critical, and an package update should be followed ASAP. Regards, Roman ** Attachment added: 60-persistent-storage.rules fix (rollback) for external USB storage devices http://launchpadlibrarian.net/20796987/udev-persistent-storage.rules.diff -- 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 ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 264789] Re: USB Hard Drive Not Accessible, vol_id hangs
Please do NOT do this. That is not the correct fix. The bug is with the
USB/SCSI retry logic (which changed between 2.6.26 and 2.6.27 and causes an
infinite retry loop in this case).
I tried the adding ENV{DEVTYPE}=partition workaround a while ago and rendered
my system unbootable and I got to spend a merry time with the live CD undoing
the change. If you use dmraid (fakeraid) support, then the vol_id line NEEDS to
occur for the whole disk, not for a partition only. If your udev changes don't
break dm/fakeraid, then that's much better, but it's still papering over the
real underlying problem.
The kernel retry code needs to be fixed, and to avoid getting any I/O
error at all from vol_id, all the broken devices which return
(last_sector + 1) from the call to find the capacity, instead of
last_sector need to have an UNUSUAL_DEV entry with US_FL_FIX_CAPACITY in
the flags. Sadly, this seems to be a very large number of devices.
The kernel fix that Alan Stern provided should prevent the infinite
retry logic and so you should see a handful of failures and then
everything should carry on. I haven't yet downloaded the Ubuntu -11
kernel source to see why this isn't happening.
--
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
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 264789] Re: USB Hard Drive Not Accessible, vol_id hangs
As I've written at bug 300394 : is it possible that this kernel bug report is related? http://bugzilla.kernel.org/show_bug.cgi?id=12099 -- 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 ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 264789] Re: USB Hard Drive Not Accessible, vol_id hangs
http://bugzilla.kernel.org/show_bug.cgi?id=12099 is an example of needing to added the UNUSUAL_DEV entry to fix up the the returned capacity. However, the kernel is also still broken. Attempting to do I/O to an illegal offset should never result in an infinite loop of retries. This in essence is the point. There are 2 bugs here. The infinite retry trying to read a non-existent sector is one. The other is to add all of the UNUSUAL_DEV entries for broken devices. Sadly, I think there are so many, the table size is going to dwarf the size of the driver code itself :-( -- 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 ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 264789] Re: USB Hard Drive Not Accessible, vol_id hangs
2.6.27-11 does not solve the problem here, either. -- 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 ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 264789] Re: USB Hard Drive Not Accessible, vol_id hangs
Just tried 2.6.27-11 from proposed and it still doesn't work with my CompactFlash reader (07c4:a400). vol_id hangs as usual. -- 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 ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 264789] Re: USB Hard Drive Not Accessible, vol_id hangs
I've tried 2.6.27-11 as well, the problem still exists here for me too. Bus 002 Device 006: ID 0421:0429 Nokia Mobile Phones 6230i MultiMedia Card -- 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 ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 264789] Re: USB Hard Drive Not Accessible, vol_id hangs
Got 2.6.27-11 from proposed with apt-get upgrade today and booted it. Still getting the same errors with Nokia 6500c phone in storage mode. -- 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 ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
