[opensuse] Re: Large disks in Opensuse 11
Roger Oberholtzer a écrit :
lsusb Bus 005 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub Bus 004 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub Bus 003 Device 002: ID 046d:c043 Logitech, Inc. MX320 Laser Mouse Bus 003 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub Bus 001 Device 002: ID 046d:c30e Logitech, Inc. UltraX Keys (X) Bus 001 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub Bus 002 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
Um, which in the above is the disk?
probably nowhere, I see only mouse, keyboard and USB hubs is not there any switch in the box? (or any evidence the disk is running in the box. I understand the box and the disk where not bough together? I have had interface problems jdd -- http://www.dodin.net http://valerie.dodin.org http://news.opensuse.org/2009/04/13/people-of-opensuse-jean-daniel-dodin/ -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org
jdd wrote:
Roger Oberholtzer a écrit :
lsusb Bus 005 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub Bus 004 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub Bus 003 Device 002: ID 046d:c043 Logitech, Inc. MX320 Laser Mouse Bus 003 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub Bus 001 Device 002: ID 046d:c30e Logitech, Inc. UltraX Keys (X) Bus 001 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub Bus 002 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Um, which in the above is the disk?
probably nowhere, I see only mouse, keyboard and USB hubs is not there any switch in the box? (or any evidence the disk is running in the box. I understand the box and the disk where not bough together? I have had interface problems
I believe you are right, only the hubs are displayed. Pardon me for my misunderstanding. The disk is running, and was detected when I plugged it into a Windows Vista computer. Apparently there is nothing wrong with the disk, but Opensuse 11 will not recognize it. Per Inge Oestmoen, Norway -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org
Per Inge Oestmoen a écrit :
The disk is running, and was detected when I plugged it into a Windows Vista computer. Apparently there is nothing wrong with the disk, but Opensuse 11 will not recognize it.
run "dmesg" in an xterm before and after inserting the disk.. Be sure to use a usb port on the computer (not on an external hub) and see if there is any message jdd -- http://www.dodin.net http://valerie.dodin.org http://news.opensuse.org/2009/04/13/people-of-opensuse-jean-daniel-dodin/ -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org
jdd wrote:
Per Inge Oestmoen a écrit :
The disk is running, and was detected when I plugged it into a Windows Vista computer. Apparently there is nothing wrong with the disk, but Opensuse 11 will not recognize it.
run "dmesg" in an xterm before and after inserting the disk.. Be sure to use a usb port on the computer (not on an external hub)
This is my dmesg output with the disk attached: http://www.coldsiberia.net/text/dmesg_06052009.txt Per Inge Oestmoen, Norway -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org
On Wed, May 6, 2009 at 10:31 AM, Per Inge Oestmoen
jdd wrote:
Per Inge Oestmoen a écrit :
The disk is running, and was detected when I plugged it into a Windows Vista computer. Apparently there is nothing wrong with the disk, but Opensuse 11 will not recognize it.
run "dmesg" in an xterm before and after inserting the disk.. Be sure to use a usb port on the computer (not on an external hub)
This is my dmesg output with the disk attached:
http://www.coldsiberia.net/text/dmesg_06052009.txt
Per Inge Oestmoen, Norway
I don't see a single reference to usb in there. Is that right. "dmesg | grep usb" gives lots of stuff on my desktop machine running OS 11.1. Are you running a OpenSUSE kernel? Or a custom one? Greg -- Greg Freemyer Head of EDD Tape Extraction and Processing team Litigation Triage Solutions Specialist http://www.linkedin.com/in/gregfreemyer First 99 Days Litigation White Paper - http://www.norcrossgroup.com/forms/whitepapers/99%20Days%20whitepaper.pdf The Norcross Group The Intersection of Evidence & Technology http://www.norcrossgroup.com -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org
Greg Freemyer wrote:
This is my dmesg output with the disk attached: http://www.coldsiberia.net/text/dmesg_06052009.txt Per Inge Oestmoen, Norway
I don't see a single reference to usb in there. Is that right.
Yes, I cannot see anything either. I only typed "dmesg."
"dmesg | grep usb" gives lots of stuff on my desktop machine running OS 11.1.
That command apparently was better: http://www.coldsiberia.net/text/dmesg_06052009.txt
Are you running a OpenSUSE kernel? Or a custom one?
I am running the OpenSUSE 2.6.25.20-01-default kernel. Per Inge Oestmoen, Norway -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 On Wednesday, 2009-05-06 at 17:07 +0200, Per Inge Oestmoen wrote:
Are you running a OpenSUSE kernel? Or a custom one?
I am running the OpenSUSE 2.6.25.20-01-default kernel.
So you are using openSUSE 11.0, not 11 as you said. There is no openSUSE 11. You might try with openSUSE 11.1, there are problems with usb support of disks in 11.0. - -- Cheers, Carlos E. R. -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.9 (GNU/Linux) iEYEARECAAYFAkoB45EACgkQtTMYHG2NR9VX3wCcCE5q0zab6f5mQ8E/AHPc20lh Z7wAnRxt6T4xNdu/kLQaIYI2jQaVQ8mO =3Jiv -----END PGP SIGNATURE----- -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org
On Wednesday May 6 2009, Per Inge Oestmoen wrote:
...
run "dmesg" in an xterm before and after inserting the disk.. Be sure to use a usb port on the computer (not on an external hub)
This is my dmesg output with the disk attached:
I see no sign of a USB drive or any USB device activity at all in that log file. Are you certain that you're connecting the drive to a good cable and / or to a hub that's actually connected to that system? Are you certain the USB port to whch you're connecting that device is active / enabled?
Per Inge Oestmoen, Norway
Randall Schulz -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org
Randall R Schulz wrote:
Are you certain that you're connecting the drive to a good cable and / or to a hub that's actually connected to that system? Are you certain the USB port to whch you're connecting that device is active / enabled?
That is for sure. I have attached other disks (up to 500 Gb) and a lot of things like card readers and memory sticks. But it is only with this 1 Tb disk that I experienced failure. - Thank you all for your friendly help so far, we ar bound to approach the solution! Per Inge Oestmoen, Norway -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 On Wednesday, 2009-05-06 at 07:43 -0700, Randall R Schulz wrote:
This is my dmesg output with the disk attached:
I see no sign of a USB drive or any USB device activity at all in that log file.
But I do: usbcore: registered new interface driver usb-storage usb-storage: device found at 3 usb-storage: waiting for device to settle before scanning usb-storage: device scan complete usb 2-2: reset high speed USB device using ehci_hcd and address 3 usb 2-2: device descriptor read/64, error -71 usb 2-2: device descriptor read/64, error -71 which is quite bad news. - -- Cheers, Carlos E. R. -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.9 (GNU/Linux) iEYEARECAAYFAkoB4/0ACgkQtTMYHG2NR9UsAgCdGAQqj9NJHIbzhfhVH03pZqhz IhUAnAgAEPcdpjoTldIpGD5kBv4zo8V7 =l8uJ -----END PGP SIGNATURE----- -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org
On Wednesday May 6 2009, Carlos E. R. wrote:
On Wednesday, 2009-05-06 at 07:43 -0700, Randall R Schulz wrote:
This is my dmesg output with the disk attached:
I see no sign of a USB drive or any USB device activity at all in that log file.
But I do:
usbcore: registered new interface driver usb-storage usb-storage: device found at 3 usb-storage: waiting for device to settle before scanning usb-storage: device scan complete usb 2-2: reset high speed USB device using ehci_hcd and address 3 usb 2-2: device descriptor read/64, error -71 usb 2-2: device descriptor read/64, error -71
That was a real no-no, Per! At the time Per sent the message with that link, the contents showed no usb entries whatsoever. Now he has updated the contents of the same file, rather than putting the new contents in a different file. You apparently looked later and saw the new version.
which is quite bad news.
No news is good news.
-- Cheers, Carlos E. R.
Randall Schulz -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 On Wednesday, 2009-05-06 at 13:10 -0700, Randall R Schulz wrote:
I see no sign of a USB drive or any USB device activity at all in that log file.
But I do:
usbcore: registered new interface driver usb-storage usb-storage: device found at 3 usb-storage: waiting for device to settle before scanning usb-storage: device scan complete usb 2-2: reset high speed USB device using ehci_hcd and address 3 usb 2-2: device descriptor read/64, error -71 usb 2-2: device descriptor read/64, error -71
That was a real no-no, Per!
At the time Per sent the message with that link, the contents showed no usb entries whatsoever. Now he has updated the contents of the same file, rather than putting the new contents in a different file. You apparently looked later and saw the new version.
Ah! That explains many things.
which is quite bad news.
No news is good news.
There are read errors, that's bad news. - -- Cheers, Carlos E. R. -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.9 (GNU/Linux) iEUEARECAAYFAkoB89YACgkQtTMYHG2NR9UFKQCYzVE/HomBJM4LCn6ATVX2QaBa UACfY1ysNwtpO4elEBAwHrVoaH6ddMs= =KSbq -----END PGP SIGNATURE----- -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org
On Wednesday May 6 2009, Carlos E. R. wrote:
On Wednesday, 2009-05-06 at 13:10 -0700, Randall R Schulz wrote:
...
which is quite bad news.
No news is good news.
There are read errors, that's bad news.
Well... "No news is good news" is an English aphorism. Your English is so good I tend to assume you know it as well as a native speaker. I've always loved that particular aphorism, partly 'cause of its strong ambiguity: - There is no news that is good news. - The absence of news is itself good news.
-- Cheers, Carlos E. R.
Randall Schulz -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 On Wednesday, 2009-05-06 at 13:45 -0700, Randall R Schulz wrote:
On Wednesday May 6 2009, Carlos E. R. wrote:
On Wednesday, 2009-05-06 at 13:10 -0700, Randall R Schulz wrote:
...
which is quite bad news.
No news is good news.
There are read errors, that's bad news.
Well... "No news is good news" is an English aphorism. Your English is so good I tend to assume you know it as well as a native speaker.
No, certainly not :-)
I've always loved that particular aphorism, partly 'cause of its strong ambiguity:
- There is no news that is good news. - The absence of news is itself good news.
Ok, let me see. The aphorism means that if there is no news, that is good news in itself (because when news come, it could then be bad or good). Right? The thing is that I consider the log message: ] usb 1-2: device descriptor read/64, error -71 as bad news, it is an error. No? :-? - -- Cheers, Carlos E. R. -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.9 (GNU/Linux) iEYEARECAAYFAkoCEpEACgkQtTMYHG2NR9XSQACgiSoEW3xsOq/UTJw3RTPfJuu0 EjAAn3zMiDLigj06fWeFgSmtfwHb8R6I =vbNM -----END PGP SIGNATURE----- -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org
On Wednesday May 6 2009, Carlos E. R. wrote:
On Wednesday, 2009-05-06 at 13:45 -0700, Randall R Schulz wrote:
On Wednesday May 6 2009, Carlos E. R. wrote:
On Wednesday, 2009-05-06 at 13:10 -0700, Randall R Schulz wrote:
...
No news is good news.
There are read errors, that's bad news.
Well... "No news is good news" is an English aphorism. Your English is so good I tend to assume you know it as well as a native speaker.
No, certainly not :-)
You couldn't prove it by us.
I've always loved that particular aphorism, partly 'cause of its strong ambiguity:
- There is no news that is good news. - The absence of news is itself good news.
Ok, let me see. The aphorism means that if there is no news, that is good news in itself (because when news come, it could then be bad or good). Right?
Yes. I believe the usual connotation is that receiving no news is itself a "good news" situation. It's a statement of some pessimism implying that when news does arrive, it's likely to be bad news, so the absence of any news is welcome. Or whatever...
The thing is that I consider the log message:
] usb 1-2: device descriptor read/64, error -71
as bad news, it is an error.
No? :-?
Yes, I did get that part. My irrepressible sense of humor got the best of me, again.
-- Cheers, Carlos E. R.
Randall Schulz -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org
On Wed, May 06, 2009 at 04:31:45PM +0200, Per Inge Oestmoen wrote:
jdd wrote:
Per Inge Oestmoen a écrit :
The disk is running, and was detected when I plugged it into a Windows Vista computer. Apparently there is nothing wrong with the disk, but Opensuse 11 will not recognize it.
run "dmesg" in an xterm before and after inserting the disk.. Be sure to use a usb port on the computer (not on an external hub)
This is my dmesg output with the disk attached:
Seeing this: [...] usb 1-2: device descriptor read/64, error -71 usb 1-2: device descriptor read/64, error -71 usb 1-2: new full speed USB device using uhci_hcd and address 4 usb 1-2: device descriptor read/64, error -71 usb 1-2: device descriptor read/64, error -71 usb 1-2: new full speed USB device using uhci_hcd and address 5 usb 1-2: device not accepting address 5, error -71 usb 1-2: new full speed USB device using uhci_hcd and address 6 [...] Googling suggest auto-suspend might be the problem. Try # echo -1 >/sys/module/usbcore/parameters/autosuspend after a fresh boot and /before/ plugging in the disk. Kurt -- Finding out what goes on in the C.I.A. is like performing acupuncture on a rock. -- New York Times, Jan. 20, 1981 -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org
Kurt Wall wrote:
Seeing this:
[...] usb 1-2: device descriptor read/64, error -71 usb 1-2: device descriptor read/64, error -71 usb 1-2: new full speed USB device using uhci_hcd and address 4 usb 1-2: device descriptor read/64, error -71 usb 1-2: device descriptor read/64, error -71 usb 1-2: new full speed USB device using uhci_hcd and address 5 usb 1-2: device not accepting address 5, error -71 usb 1-2: new full speed USB device using uhci_hcd and address 6 [...]
Googling suggest auto-suspend might be the problem. Try
# echo -1 >/sys/module/usbcore/parameters/autosuspend
after a fresh boot and /before/ plugging in the disk.
Fully agree: When I started the system this morning, the disk was again available - but could not be partitioned or formatted. So there has to be something else. This is the message I got, and the whole thing stopped: http://www.coldsiberia.net/text/partition_failure.jpg Also, YaST seems to "think" that my disk is 2 Tb whereas it is "merely" one. Per Inge Oestmoen, Norway -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 On Thursday, 2009-05-07 at 10:02 +0200, Per Inge Oestmoen wrote:
Kurt Wall wrote:
Seeing this:
[...] usb 1-2: device descriptor read/64, error -71 usb 1-2: device descriptor read/64, error -71 usb 1-2: new full speed USB device using uhci_hcd and address 4 usb 1-2: device descriptor read/64, error -71 usb 1-2: device descriptor read/64, error -71 usb 1-2: new full speed USB device using uhci_hcd and address 5 usb 1-2: device not accepting address 5, error -71 usb 1-2: new full speed USB device using uhci_hcd and address 6 [...]
Googling suggest auto-suspend might be the problem. Try
# echo -1 >/sys/module/usbcore/parameters/autosuspend
after a fresh boot and /before/ plugging in the disk.
Fully agree: When I started the system this morning, the disk was again available - but could not be partitioned or formatted. So there has to be something else.
Suspending while a HD via USB is connected doesn't fully work under 11.0, it started to work with 11.1. I know, because I reported it to bugzilla. And you have 11.0
This is the message I got, and the whole thing stopped:
http://www.coldsiberia.net/text/partition_failure.jpg
Also, YaST seems to "think" that my disk is 2 Tb whereas it is "merely" one.
It could be that your disk is GPT, not "standard" partition table. One more reason to upgrade to 11.1 More info: http://en.wikipedia.org/wiki/GUID_Partition_Table Pay attention to the "Legacy MBR" paragraph. - -- Cheers, Carlos E. R. -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.9 (GNU/Linux) iEYEARECAAYFAkoDNSkACgkQtTMYHG2NR9W7ygCeMOGUO5LNfWqFYUUHfj/tORXo 5tgAn35aimZ5KsmG15yraytcCfDW9/r2 =ph+v -----END PGP SIGNATURE----- -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org
participants (6)
-
Carlos E. R. -
Greg Freemyer -
jdd -
Kurt Wall -
Per Inge Oestmoen -
Randall R Schulz