Re: curious USB hard drive problem
I forget to me to mention that also I tested different with kernel from verison 2.6.16 to 2.6.20_rc, recompile the 2.6.18-3 of my debian etch, activating and deactivating some options and also it follows the problem. By the investigated thing to people who use ubuntu, fedora happened to them the same. In http://bugzilla.kernel.org/show_bug.cgi?id=7533 somebody comment the problem to the developers of kernel. 2007/1/15, David Garcia [EMAIL PROTECTED]: To my it happens to me the same. I have a card pci USB 4 ports with chipset VIA model VT6212L, and after of several days investigating I could not determine if is bug of kernel or is problem with the model of chipset. In the end I had to place another card pci with chipset old model VIA VT6202 and at least I fix the problem to me. I connect a hard disk Maxtor 320GB, usb 2.0. If beams rmmode ehci_hcd;modprobe ehci_hcd, fixes of temporary way the problem. I believe that is bug with module ehci_hcd because this are many happening to him the same. Excuses my ingles. 2007/1/15, Digby Tarvin [EMAIL PROTECTED]: I have a 2.5 Toshiba MK1032GAX hard drive in a USB powered enclosure which doesn't seem to work properly with Debian. I'm wondering if anyone has ever seen anything similar, or has any ideas about what might be happening... The curious thing is that I am fairly sure that the drive is ok, because if I put it into an older (looks like the same product but with older PCB version) enclosure it boots without error. But if I plug the problem enclosure into a Windows system with the same hard drive installed it works fine, making it hard to justify returning the enclosure as faulty. I have also tried booting a different version of Linux (Foundry) from different media and it can access the drive without problem. Hence it is starting to look like an issue with this Debian kernel and this particular USB HDD enclosure. The symptoms I see are that the boot starts normally Lilo reads the kernel and initrd successfully The kernel reports the HDD manufacturer/model/capacity correctly Then... sda: assuming drive cache: write through SCSI device sda: 195371568 512-byte hdwr sectors (100030 MB) sda: Write Protect is off sda: assuming drive cache: write through sda:6usb 1-2 : reset high speed USB device using ehci_hdc and address 2 usb 1-2: reset high speed USB device using ehci_hcd and address 2 usb 1-2: reset high speed USB device using ehci_hcd and address 2 usb 1-2: reset high speed USB device using ehci_hcd and address 2 usb 1-2: reset high speed USB device using ehci_hcd and address 2 usb 1-2: reset high speed USB device using ehci_hcd and address 2 sd 0:0:0:0: SCSI error: return code = 0x0005 The Debian install is Etch using RC1 install and kernel 2.6.18-3-486. (the original 2.6.17 kernel behaves the same). Does anyone have any ideas of what might be missing from this particular enclosure that would effect Debian but not Windows or Foundry Linux? Regards, DigbyT -- Digby R. S. Tarvin digbyt(at)digbyt.com http://www.digbyt.com -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED] -- David Garcia (dalx) Mcbo-Venezuela Linux counter No.291837 Machine counter No.253104 Debian User Mandriva User 0414-3627992 0412-5088432 -- David Garcia (dalx) Mcbo-Venezuela Linux counter No.291837 Machine counter No.253104 Debian User Mandriva User 0414-3627992 0412-5088432
Re: curious USB hard drive problem
On Mon, Jan 15, 2007 at 12:15:45PM +, Digby Tarvin wrote: I have a 2.5 Toshiba MK1032GAX hard drive in a USB powered enclosure which doesn't seem to work properly with Debian. The curious thing is that I am fairly sure that the drive is ok, because if I put it into an older (looks like the same product but with older PCB version) enclosure it boots without error. Hence it is starting to look like an issue with this Debian kernel and this particular USB HDD enclosure. The symptoms I see are that the boot starts normally Lilo reads the kernel and initrd successfully The kernel reports the HDD manufacturer/model/capacity correctly Then... sda: assuming drive cache: write through SCSI device sda: 195371568 512-byte hdwr sectors (100030 MB) sda: Write Protect is off sda: assuming drive cache: write through sda:6usb 1-2 : reset high speed USB device using ehci_hdc and address 2 usb 1-2: reset high speed USB device using ehci_hcd and address 2 usb 1-2: reset high speed USB device using ehci_hcd and address 2 usb 1-2: reset high speed USB device using ehci_hcd and address 2 usb 1-2: reset high speed USB device using ehci_hcd and address 2 usb 1-2: reset high speed USB device using ehci_hcd and address 2 sd 0:0:0:0: SCSI error: return code = 0x0005 The Debian install is Etch using RC1 install and kernel 2.6.18-3-486. (the original 2.6.17 kernel behaves the same). If I understand correctly, you installed debian RC1 onto this drive in another enclosure, which booted OK, but now that you've moved that drive to the new enclosure it doesn't boot. Looking at later posts to this thread, I wonder if its a module missing from the initrd. The good news, is that it seems the boot loader is able to pull the kernel and initrd off the drive. If you boot from another drive, do an lsmod, then mount this troubled drive enclosure, and do another lsmod, you may find out what module is needed to access the drive in this enclosure. You should then be able to add that module to the initrd. What happens if you boot up from the other drive, then mount this drive, then chroot into it and do an update to get newer than RC1? Perhaps that will solve the problem. Good luck, Doug. -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: curious USB hard drive problem
To my it happens to me the same. I have a card pci USB 4 ports with chipset VIA model VT6212L, and after of several days investigating I could not determine if is bug of kernel or is problem with the model of chipset. In the end I had to place another card pci with chipset old model VIA VT6202 and at least I fix the problem to me. I connect a hard disk Maxtor 320GB, usb 2.0. If beams rmmode ehci_hcd;modprobe ehci_hcd, fixes of temporary way the problem. I believe that is bug with module ehci_hcd because this are many happening to him the same. Excuses my ingles. 2007/1/15, Digby Tarvin [EMAIL PROTECTED]: I have a 2.5 Toshiba MK1032GAX hard drive in a USB powered enclosure which doesn't seem to work properly with Debian. I'm wondering if anyone has ever seen anything similar, or has any ideas about what might be happening... The curious thing is that I am fairly sure that the drive is ok, because if I put it into an older (looks like the same product but with older PCB version) enclosure it boots without error. But if I plug the problem enclosure into a Windows system with the same hard drive installed it works fine, making it hard to justify returning the enclosure as faulty. I have also tried booting a different version of Linux (Foundry) from different media and it can access the drive without problem. Hence it is starting to look like an issue with this Debian kernel and this particular USB HDD enclosure. The symptoms I see are that the boot starts normally Lilo reads the kernel and initrd successfully The kernel reports the HDD manufacturer/model/capacity correctly Then... sda: assuming drive cache: write through SCSI device sda: 195371568 512-byte hdwr sectors (100030 MB) sda: Write Protect is off sda: assuming drive cache: write through sda:6usb 1-2 : reset high speed USB device using ehci_hdc and address 2 usb 1-2: reset high speed USB device using ehci_hcd and address 2 usb 1-2: reset high speed USB device using ehci_hcd and address 2 usb 1-2: reset high speed USB device using ehci_hcd and address 2 usb 1-2: reset high speed USB device using ehci_hcd and address 2 usb 1-2: reset high speed USB device using ehci_hcd and address 2 sd 0:0:0:0: SCSI error: return code = 0x0005 The Debian install is Etch using RC1 install and kernel 2.6.18-3-486. (the original 2.6.17 kernel behaves the same). Does anyone have any ideas of what might be missing from this particular enclosure that would effect Debian but not Windows or Foundry Linux? Regards, DigbyT -- Digby R. S. Tarvin digbyt(at)digbyt.com http://www.digbyt.com -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED] -- David Garcia (dalx) Mcbo-Venezuela Linux counter No.291837 Machine counter No.253104 Debian User Mandriva User 0414-3627992 0412-5088432
Re: curious USB hard drive problem
On 1/15/07, Digby Tarvin [EMAIL PROTECTED] wrote: I have a 2.5 Toshiba MK1032GAX hard drive in a USB powered enclosure which doesn't seem to work properly with Debian. I'm wondering if anyone has ever seen anything similar, or has any ideas about what might be happening... The curious thing is that I am fairly sure that the drive is ok, because if I put it into an older (looks like the same product but with older PCB version) enclosure it boots without error. But if I plug the problem enclosure into a Windows system with the same hard drive installed it works fine, making it hard to justify returning the enclosure as faulty. I have also tried booting a different version of Linux (Foundry) from different media and it can access the drive without problem. Hence it is starting to look like an issue with this Debian kernel and this particular USB HDD enclosure. The symptoms I see are that the boot starts normally Lilo reads the kernel and initrd successfully The kernel reports the HDD manufacturer/model/capacity correctly Then... sda: assuming drive cache: write through SCSI device sda: 195371568 512-byte hdwr sectors (100030 MB) sda: Write Protect is off sda: assuming drive cache: write through sda:6usb 1-2 : reset high speed USB device using ehci_hdc and address 2 usb 1-2: reset high speed USB device using ehci_hcd and address 2 usb 1-2: reset high speed USB device using ehci_hcd and address 2 usb 1-2: reset high speed USB device using ehci_hcd and address 2 usb 1-2: reset high speed USB device using ehci_hcd and address 2 usb 1-2: reset high speed USB device using ehci_hcd and address 2 sd 0:0:0:0: SCSI error: return code = 0x0005 The Debian install is Etch using RC1 install and kernel 2.6.18-3-486. (the original 2.6.17 kernel behaves the same). Does anyone have any ideas of what might be missing from this particular enclosure that would effect Debian but not Windows or Foundry Linux? Regards, DigbyT Did you try it after installing hal and pmount ? -- Random Quotes From Megas XLR Coop: You see? The mysteries of the Universe are revealed when you break stuff. Jamie: When in doubt, blow up a planet. Kiva: It's an 80 foot robot, if we can't see it, absolutely it's not here. Glorft Technician: Unnecessary use of force in capturing the Earthers has been approved. -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: curious USB hard drive problem
On Mon, Jan 15, 2007 at 12:09:08PM -0400, David Garcia wrote: To my it happens to me the same. I have a card pci USB 4 ports with chipset VIA model VT6212L, and after of several days investigating I could not determine if is bug of kernel or is problem with the model of chipset. In the end I had to place another card pci with chipset old model VIA VT6202 and at least I fix the problem to me. I connect a hard disk Maxtor 320GB, usb 2.0. If beams rmmode ehci_hcd;modprobe ehci_hcd, fixes of temporary way the problem. I believe that is bug with module ehci_hcd because this are many happening to him the same. Excuses my ingles. Interesting - That does suggest that my problem is a Debian/Kernel compatability issue rather than faulty hardware. Wish I knew what had changed in the design of this particular enclosure to stop the newer pcb version from working. Some protocol enhancement that the Linux kernel doesn't like yet, or cutting a corner to reduce cost at the expense of compatability? Another clue I noticed is that if I boot a system from the internal (non USB) drive, using a non-Debian kernel with all AMDs patches for this chipset applied, I can plug in the USB drive and it works fine. But it it is plugged in before the booting then the drive is recognised but none of the partitions appear in /proc/partitions. I think I forgot to mention that this problem was occuring on an AMD Geode LX system. lspci shows the following devices on board: 00:01.0 Host bridge: Advanced Micro Devices [AMD] Unknown device 2080 (rev 30) 00:01.1 VGA compatible controller: Advanced Micro Devices [AMD] Geode LX Video 00:01.2 Entertainment encryption device: Advanced Micro Devices [AMD] Geode LX AES Security Block 00:0d.0 Ethernet controller: Realtek Semiconductor Co., Ltd. RTL-8139/8139C/8139C+ (rev 10) 00:0e.0 Network controller: Intel Corporation PRO/Wireless 2915ABG Network Connection (rev 05) 00:0f.0 ISA bridge: Advanced Micro Devices [AMD] CS5536 [Geode companion] ISA (rev 03) 00:0f.2 IDE interface: Advanced Micro Devices [AMD] CS5536 [Geode companion] IDE (rev 01) 00:0f.3 Multimedia audio controller: Advanced Micro Devices [AMD] CS5536 [Geode companion] Audio (rev 01) 00:0f.4 USB Controller: Advanced Micro Devices [AMD] CS5536 [Geode companion] OHC (rev 02) 00:0f.5 USB Controller: Advanced Micro Devices [AMD] CS5536 [Geode companion] EHC (rev 02) One last experiment I tried - I didn't have any other machine with a bios that could boot from USB HDD, but tried booting to this drive from my notebook by putting grub on a CD. Booted fine on the old enclosure, but with the new enclosure get: root (hd1,4) Error 21: Selected disk does not exist So it doesn't seem to be a problem limited to AMD chipsets. Regards, DigbyT -- Digby R. S. Tarvin digbyt(at)digbyt.com http://www.digbyt.com -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: curious USB hard drive problem
On Mon, Jan 15, 2007 at 04:31:51PM +, Mihira Fernando wrote: On 1/15/07, Digby Tarvin [EMAIL PROTECTED] wrote: I have a 2.5 Toshiba MK1032GAX hard drive in a USB powered enclosure which doesn't seem to work properly with Debian. I'm wondering if anyone has ever seen anything similar, or has any ideas about what might be happening... The curious thing is that I am fairly sure that the drive is ok, because if I put it into an older (looks like the same product but with older PCB version) enclosure it boots without error. But if I plug the problem enclosure into a Windows system with the same hard drive installed it works fine, making it hard to justify returning the enclosure as faulty. I have also tried booting a different version of Linux (Foundry) from different media and it can access the drive without problem. Hence it is starting to look like an issue with this Debian kernel and this particular USB HDD enclosure. The symptoms I see are that the boot starts normally Lilo reads the kernel and initrd successfully The kernel reports the HDD manufacturer/model/capacity correctly Then... sda: assuming drive cache: write through SCSI device sda: 195371568 512-byte hdwr sectors (100030 MB) sda: Write Protect is off sda: assuming drive cache: write through sda:6usb 1-2 : reset high speed USB device using ehci_hdc and address 2 usb 1-2: reset high speed USB device using ehci_hcd and address 2 usb 1-2: reset high speed USB device using ehci_hcd and address 2 usb 1-2: reset high speed USB device using ehci_hcd and address 2 usb 1-2: reset high speed USB device using ehci_hcd and address 2 usb 1-2: reset high speed USB device using ehci_hcd and address 2 sd 0:0:0:0: SCSI error: return code = 0x0005 The Debian install is Etch using RC1 install and kernel 2.6.18-3-486. (the original 2.6.17 kernel behaves the same). Does anyone have any ideas of what might be missing from this particular enclosure that would effect Debian but not Windows or Foundry Linux? Regards, DigbyT Did you try it after installing hal and pmount ? The Debian install was done with the older (working) enclosure, so everything seems to be there. pmount and hal are installed - is there any configuration that needs to be done to try what you have in mind? Regards, DigbyT -- Digby R. S. Tarvin digbyt(at)digbyt.com http://www.digbyt.com -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: curious USB hard drive problem
On 1/16/07, Digby Tarvin [EMAIL PROTECTED] wrote: The Debian install was done with the older (working) enclosure, so everything seems to be there. pmount and hal are installed - is there any configuration that needs to be done to try what you have in mind? no. I had a similar problem with my onboard CF card reader. When a CF card is plugged in, it was listed but not mounting automatically or manually and after a little googling I found out that pmount is needed but after installing that, it still didnt work and further googling suggested that hal should also be in the mix. After installing hal it works perfectly. All I have to do is to plug in the card and it works. -- Random Quotes From Megas XLR Coop: You see? The mysteries of the Universe are revealed when you break stuff. Jamie: When in doubt, blow up a planet. Kiva: It's an 80 foot robot, if we can't see it, absolutely it's not here. Glorft Technician: Unnecessary use of force in capturing the Earthers has been approved. -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
