Skip to contentSkip to conversation

Problems with USB disk

DISCUSSION Niels 7 participants 15 messages Aug 7, 2007 – Sep 13, 2007 SCSI

lore
Share & tools
lore

Niels

author
#0 lore raw

Hi,

I'm having problems with a new 500 GB USB disk. It works, but sometimes I get these in dmesg:

usb 1-3: reset high speed USB device using ehci_hcd and address 2 usb 5-1: USB disconnect, address 2
drivers/usb/class/usblp.c: usblp0: removed
sd 0:0:0:0: Device not ready: <6>: Sense Key : 0x2 [current] : ASC=0x4 ASCQ=0x2
end_request: I/O error, dev sda, sector 254148215
sd 0:0:0:0: Device not ready: <6>: Sense Key : 0x2 [current] : ASC=0x4 ASCQ=0x2
end_request: I/O error, dev sda, sector 252434023
EXT3-fs error (device sda1): ext3_find_entry: reading directory #15761836 offset 0

There's also a printer connected. This is on a pci/usb2 card. When the above happens, I get I/O errors. When I mount the drive next, there are errors and often missing files. Quite annoying!

Kernel is 2.6.21

What's going on?

Thanks,
Niels

#1 lore raw
Quoted 19 lines · Niels

Hi,

I'm having problems with a new 500 GB USB disk. It works, but sometimes I get these in dmesg:

usb 1-3: reset high speed USB device using ehci_hcd and address 2 usb 5-1: USB disconnect, address 2
drivers/usb/class/usblp.c: usblp0: removed
sd 0:0:0:0: Device not ready: <6>: Sense Key : 0x2 [current] : ASC=0x4 ASCQ=0x2
end_request: I/O error, dev sda, sector 254148215
sd 0:0:0:0: Device not ready: <6>: Sense Key : 0x2 [current] : ASC=0x4 ASCQ=0x2
end_request: I/O error, dev sda, sector 252434023
EXT3-fs error (device sda1): ext3_find_entry: reading directory #15761836 offset 0

Quoted 7 lines

There's also a printer connected. This is on a pci/usb2 card. When the above happens, I get I/O errors. When I mount the drive next, there are errors and often missing files. Quite annoying!

Kernel is 2.6.21

What's going on?

You have a low voltage issue, or a bad cable. The device is electronically disconnecting itself. Try using a externally-powered hub, or a new cable.

thanks,

greg k-h

author
#2 lore raw
Quoted 28 lines · Greg KH
Quoted 19 lines · Niels

Hi,

I'm having problems with a new 500 GB USB disk. It works, but sometimes I get these in dmesg:

usb 1-3: reset high speed USB device using ehci_hcd and address 2 usb 5-1: USB disconnect, address 2
drivers/usb/class/usblp.c: usblp0: removed
sd 0:0:0:0: Device not ready: <6>: Sense Key : 0x2 [current] : ASC=0x4 ASCQ=0x2
end_request: I/O error, dev sda, sector 254148215
sd 0:0:0:0: Device not ready: <6>: Sense Key : 0x2 [current] : ASC=0x4 ASCQ=0x2
end_request: I/O error, dev sda, sector 252434023
EXT3-fs error (device sda1): ext3_find_entry: reading directory #15761836 offset 0

Quoted 7 lines

There's also a printer connected. This is on a pci/usb2 card. When the above happens, I get I/O errors. When I mount the drive next, there are errors and often missing files. Quite annoying!

Kernel is 2.6.21

What's going on?

Quoted 7 lines

You have a low voltage issue, or a bad cable. The device is electronically disconnecting itself. Try using a externally-powered hub, or a new cable.

thanks,

greg k-h

It has its own power supply. All cables are new and plugged in securely.

Thank you for your answer,
Niels

#3 lore raw
Quoted 29 lines · On Wednesday 08 August 2007 13:48:29 you wrote:
Quoted 28 lines · Greg KH
Quoted 27 lines · Niels

Hi,

I'm having problems with a new 500 GB USB disk. It works, but sometimes I get these in dmesg:

usb 1-3: reset high speed USB device using ehci_hcd and address 2 usb 5-1: USB disconnect, address 2 drivers/usb/class/usblp.c: usblp0: removed
sd 0:0:0:0: Device not ready: <6>: Sense Key : 0x2 [current]

: ASC=0x4 ASCQ=0x2

end_request: I/O error, dev sda, sector 254148215 sd 0:0:0:0: Device not ready: <6>: Sense Key : 0x2 [current]

: ASC=0x4 ASCQ=0x2

end_request: I/O error, dev sda, sector 252434023 EXT3-fs error (device sda1): ext3_find_entry: reading directory #15761836 offset 0

There's also a printer connected. This is on a pci/usb2 card. When the above happens, I get I/O errors. When I mount the drive next, there are errors and often missing files. Quite annoying!

Quoted 7 lines
Quoted 7 lines
Quoted 3 lines

Kernel is 2.6.21

What's going on?

You have a low voltage issue, or a bad cable. The device is electronically disconnecting itself. Try using a externally-powered hub, or a new cable.

I am seeing a similar problem with 2.6.22 and 2.6.23-* kernels with my 60G iPod Video, works fine with 2.6.18 kernel though.

Rehards,
ismail

Signature · 1 line
Perfect is the enemy of good
author
#4 lore raw
Quoted 38 lines · Ismail Dönmez
Quoted 29 lines · On Wednesday 08 August 2007 13:48:29 you wrote:
Quoted 28 lines · Greg KH
Quoted 27 lines · Niels

Hi,

I'm having problems with a new 500 GB USB disk. It works, but sometimes I get these in dmesg:

usb 1-3: reset high speed USB device using ehci_hcd and address 2 usb 5-1: USB disconnect, address 2 drivers/usb/class/usblp.c: usblp0: removed
sd 0:0:0:0: Device not ready: <6>: Sense Key : 0x2 [current]

: ASC=0x4 ASCQ=0x2

end_request: I/O error, dev sda, sector 254148215 sd 0:0:0:0: Device not ready: <6>: Sense Key : 0x2 [current]

: ASC=0x4 ASCQ=0x2

end_request: I/O error, dev sda, sector 252434023 EXT3-fs error (device sda1): ext3_find_entry: reading directory #15761836 offset 0

There's also a printer connected. This is on a pci/usb2 card. When the above happens, I get I/O errors. When I mount the drive next, there are errors and often missing files. Quite annoying!

Quoted 7 lines
Quoted 7 lines
Quoted 3 lines

Kernel is 2.6.21

What's going on?

You have a low voltage issue, or a bad cable. The device is electronically disconnecting itself. Try using a externally-powered hub, or a new cable.

Quoted 6 lines

I am seeing a similar problem with 2.6.22 and 2.6.23-* kernels with my 60G iPod Video, works fine with 2.6.18 kernel though.

Rehards,
ismail

(no need to CC me)

So far I'm seeing this:

- On 2.6.21 I mount the drive. After a while it spins down, and when I then unmount it, an error pops up in dmesg.

- On 2.6.18 I can't provoke the same error. The drive doesn't appear to spin down. I don't know if the data corruption from 2.6.21 occurs with regular use.

There are a number of other factor I need to eliminate on my system, but that's it so far. CONFIG_USB_SUSPEND is not set on either kernel.

//Niels

author
#5 lore raw
Quoted 58 lines · Niels
Quoted 38 lines · Ismail Dönmez
Quoted 29 lines · On Wednesday 08 August 2007 13:48:29 you wrote:
Quoted 28 lines · Greg KH
Quoted 27 lines · Niels

Hi,

I'm having problems with a new 500 GB USB disk. It works, but sometimes I get these in dmesg:

usb 1-3: reset high speed USB device using ehci_hcd and address 2 usb 5-1: USB disconnect, address 2 drivers/usb/class/usblp.c: usblp0: removed
sd 0:0:0:0: Device not ready: <6>: Sense Key : 0x2 [current]

: ASC=0x4 ASCQ=0x2

end_request: I/O error, dev sda, sector 254148215 sd 0:0:0:0: Device not ready: <6>: Sense Key : 0x2 [current]

: ASC=0x4 ASCQ=0x2

end_request: I/O error, dev sda, sector 252434023 EXT3-fs error (device sda1): ext3_find_entry: reading directory #15761836 offset 0

There's also a printer connected. This is on a pci/usb2 card. When the above happens, I get I/O errors. When I mount the drive next, there are errors and often missing files. Quite annoying!

Quoted 7 lines
Quoted 7 lines
Quoted 3 lines

Kernel is 2.6.21

What's going on?

You have a low voltage issue, or a bad cable. The device is electronically disconnecting itself. Try using a externally-powered hub, or a new cable.

Quoted 6 lines

I am seeing a similar problem with 2.6.22 and 2.6.23-* kernels with my 60G iPod Video, works fine with 2.6.18 kernel though.

Rehards,
ismail

(no need to CC me)

So far I'm seeing this:

- On 2.6.21 I mount the drive. After a while it spins down, and when I then unmount it, an error pops up in dmesg.

- On 2.6.18 I can't provoke the same error. The drive doesn't appear to spin down. I don't know if the data corruption from 2.6.21 occurs with regular use.

Quoted 5 lines

There are a number of other factor I need to eliminate on my system, but that's it so far. CONFIG_USB_SUSPEND is not set on either kernel.

//Niels

OK, on a vanilla 2.6.18.8 I also have this problem, with both the pci/usb2 card, and the usb1 on the board. I listen to music from the drive, and after some time (10-20 minutes or so), it freaks out:

=========
sd 1:0:0:0: Device not ready: <6>: Current: sense key=0x2

    ASC=0x4 ASCQ=0x2
end_request: I/O error, dev sda, sector 126693711
sd 1:0:0:0: Device not ready: <6>: Current: sense key=0x2
    ASC=0x4 ASCQ=0x2
end_request: I/O error, dev sda, sector 126693711
sd 1:0:0:0: Device not ready: <6>: Current: sense key=0x2
    ASC=0x4 ASCQ=0x2

end_request: I/O error, dev sda, sector 126693711
=========

Will updating to 2.6.23 and turning off autosuspend explicitly help? Will putting the disk on a powered hub help?

//Niels

author
#6 lore raw

Re: Problems with USB disk [solved]

Quoted 80 lines · Niels
Quoted 58 lines · Niels
Quoted 38 lines · Ismail Dönmez
Quoted 29 lines · On Wednesday 08 August 2007 13:48:29 you wrote:
Quoted 28 lines · Greg KH
Quoted 27 lines · Niels

Hi,

I'm having problems with a new 500 GB USB disk. It works, but sometimes I get these in dmesg:

usb 1-3: reset high speed USB device using ehci_hcd and address 2 usb 5-1: USB disconnect, address 2 drivers/usb/class/usblp.c: usblp0: removed
sd 0:0:0:0: Device not ready: <6>: Sense Key : 0x2 [current]

: ASC=0x4 ASCQ=0x2

end_request: I/O error, dev sda, sector 254148215 sd 0:0:0:0: Device not ready: <6>: Sense Key : 0x2 [current]

: ASC=0x4 ASCQ=0x2

end_request: I/O error, dev sda, sector 252434023 EXT3-fs error (device sda1): ext3_find_entry: reading directory #15761836 offset 0

There's also a printer connected. This is on a pci/usb2 card. When the above happens, I get I/O errors. When I mount the drive next, there are errors and often missing files. Quite annoying!

Quoted 7 lines
Quoted 7 lines
Quoted 3 lines

Kernel is 2.6.21

What's going on?

You have a low voltage issue, or a bad cable. The device is electronically disconnecting itself. Try using a externally-powered hub, or a new cable.

Quoted 6 lines

I am seeing a similar problem with 2.6.22 and 2.6.23-* kernels with my 60G iPod Video, works fine with 2.6.18 kernel though.

Rehards,
ismail

(no need to CC me)

So far I'm seeing this:

- On 2.6.21 I mount the drive. After a while it spins down, and when I then unmount it, an error pops up in dmesg.

- On 2.6.18 I can't provoke the same error. The drive doesn't appear to spin down. I don't know if the data corruption from 2.6.21 occurs with regular use.

Quoted 5 lines

There are a number of other factor I need to eliminate on my system, but that's it so far. CONFIG_USB_SUSPEND is not set on either kernel.

//Niels

OK, on a vanilla 2.6.18.8 I also have this problem, with both the pci/usb2 card, and the usb1 on the board. I listen to music from the drive, and after some time (10-20 minutes or so), it freaks out:

=========
sd 1:0:0:0: Device not ready: <6>: Current: sense key=0x2

    ASC=0x4 ASCQ=0x2
end_request: I/O error, dev sda, sector 126693711
sd 1:0:0:0: Device not ready: <6>: Current: sense key=0x2
    ASC=0x4 ASCQ=0x2
end_request: I/O error, dev sda, sector 126693711
sd 1:0:0:0: Device not ready: <6>: Current: sense key=0x2
    ASC=0x4 ASCQ=0x2
Quoted 8 lines

end_request: I/O error, dev sda, sector 126693711
=========

Will updating to 2.6.23 and turning off autosuspend explicitly help? Will putting the disk on a powered hub help?

//Niels

Using a new PSU and a powered hub made no difference. But I found a solution here:

http://alienghic.livejournal.com/382903.html

Basically, the problem is, as suspected, that the drive spins down / goes to suspend. This can be disabled with "sdparm --clear STANDBY -6 /dev/sda".

It seems to me to be an error that the kernel reports this as something like a hardware failure. Or at least very misleading.

//Niels

#7 lore raw

Re: Problems with USB disk [solved]

Quoted 78 lines · Niels
Quoted 69 lines · Niels
Quoted 47 lines · Niels
Quoted 30 lines · Ismail Dönmez
Quoted 29 lines · On Wednesday 08 August 2007 13:48:29 you wrote:
Quoted 28 lines · Greg KH
Quoted 27 lines · Niels

Hi,

I'm having problems with a new 500 GB USB disk. It works, but sometimes I get these in dmesg:

usb 1-3: reset high speed USB device using ehci_hcd and address 2 usb 5-1: USB disconnect, address 2 drivers/usb/class/usblp.c: usblp0: removed
sd 0:0:0:0: Device not ready: <6>: Sense Key : 0x2 [current]

: ASC=0x4 ASCQ=0x2

end_request: I/O error, dev sda, sector 254148215 sd 0:0:0:0: Device not ready: <6>: Sense Key : 0x2 [current]

: ASC=0x4 ASCQ=0x2

end_request: I/O error, dev sda, sector 252434023 EXT3-fs error (device sda1): ext3_find_entry: reading directory #15761836 offset 0

There's also a printer connected. This is on a pci/usb2 card. When the above happens, I get I/O errors. When I mount the drive next, there are errors and often missing files. Quite annoying!

Quoted 9 lines
Quoted 6 lines
Quoted 6 lines
Quoted 3 lines

Kernel is 2.6.21

What's going on?

You have a low voltage issue, or a bad cable. The device is electronically disconnecting itself. Try using a externally-powered hub, or a new cable.

I am seeing a similar problem with 2.6.22 and 2.6.23-* kernels with my 60G iPod Video, works fine with 2.6.18 kernel though.

So far I'm seeing this:

- On 2.6.21 I mount the drive. After a while it spins down, and when I then unmount it, an error pops up in dmesg.

Quoted 6 lines

- On 2.6.18 I can't provoke the same error. The drive doesn't appear to spin down. I don't know if the data corruption from 2.6.21 occurs with regular use.

There are a number of other factor I need to eliminate on my system, but that's it so far. CONFIG_USB_SUSPEND is not set on either kernel.

OK, on a vanilla 2.6.18.8 I also have this problem, with both the pci/usb2 card, and the usb1 on the board. I listen to music from the drive, and after some time (10-20 minutes or so), it freaks out:

=========
sd 1:0:0:0: Device not ready: <6>: Current: sense key=0x2

    ASC=0x4 ASCQ=0x2
end_request: I/O error, dev sda, sector 126693711
sd 1:0:0:0: Device not ready: <6>: Current: sense key=0x2
    ASC=0x4 ASCQ=0x2
end_request: I/O error, dev sda, sector 126693711
sd 1:0:0:0: Device not ready: <6>: Current: sense key=0x2
    ASC=0x4 ASCQ=0x2
Quoted 3 lines

end_request: I/O error, dev sda, sector 126693711
=========

Using a new PSU and a powered hub made no difference. But I found a solution here:

Quoted 8 lines

http://alienghic.livejournal.com/382903.html

Basically, the problem is, as suspected, that the drive spins down / goes to suspend. This can be disabled with "sdparm --clear STANDBY -6 /dev/sda".

It seems to me to be an error that the kernel reports this as something like a hardware failure. Or at least very misleading.

Oh, nice. The usb-storage (SCSI) disk spins itself down and we can't handle that. Should we be disabling auto-spindown when we connect the device, or be able to handle this by sending the start command when needed?

-------------------------------------------------------------------------
This SF.net email is sponsored by: Splunk Inc.
Still grepping through log files to find problems? Stop. Now Search log events and configuration files using AJAX and a browser. Download your FREE copy of Splunk now >> http://get.splunk.com/
_______________________________________________
[email protected]
To unsubscribe, use the last form field at:
https://lists.sourceforge.net/lists/listinfo/linux-usb-devel

#8 lore raw

Re: Problems with USB disk [solved]

Quoted 81 lines · Chuck Ebbert
Quoted 80 lines · Niels
Quoted 67 lines · Niels
Quoted 46 lines · Niels
Quoted 30 lines · Ismail Dönmez
Quoted 29 lines · On Wednesday 08 August 2007 13:48:29 you wrote:
Quoted 28 lines · Greg KH
Quoted 27 lines · Niels

Hi,

I'm having problems with a new 500 GB USB disk. It works, but sometimes I get these in dmesg:

usb 1-3: reset high speed USB device using ehci_hcd and address 2 usb 5-1: USB disconnect, address 2 drivers/usb/class/usblp.c: usblp0: removed
sd 0:0:0:0: Device not ready: <6>: Sense Key : 0x2 [current]

: ASC=0x4 ASCQ=0x2

end_request: I/O error, dev sda, sector 254148215 sd 0:0:0:0: Device not ready: <6>: Sense Key : 0x2 [current]

: ASC=0x4 ASCQ=0x2

end_request: I/O error, dev sda, sector 252434023 EXT3-fs error (device sda1): ext3_find_entry: reading directory #15761836 offset 0

There's also a printer connected. This is on a pci/usb2 card. When the above happens, I get I/O errors. When I mount the drive next, there are errors and often missing files. Quite annoying!

Quoted 9 lines
Quoted 6 lines
Quoted 6 lines
Quoted 3 lines

Kernel is 2.6.21

What's going on?

You have a low voltage issue, or a bad cable. The device is electronically disconnecting itself. Try using a externally-powered hub, or a new cable.

I am seeing a similar problem with 2.6.22 and 2.6.23-* kernels with my 60G iPod Video, works fine with 2.6.18 kernel though.

So far I'm seeing this:

- On 2.6.21 I mount the drive. After a while it spins down, and when I then unmount it, an error pops up in dmesg.

Quoted 6 lines

- On 2.6.18 I can't provoke the same error. The drive doesn't appear to spin down. I don't know if the data corruption from 2.6.21 occurs with regular use.

There are a number of other factor I need to eliminate on my system, but that's it so far. CONFIG_USB_SUSPEND is not set on either kernel.

OK, on a vanilla 2.6.18.8 I also have this problem, with both the pci/usb2 card, and the usb1 on the board. I listen to music from the drive, and after some time (10-20 minutes or so), it freaks out:

=========
sd 1:0:0:0: Device not ready: <6>: Current: sense key=0x2

    ASC=0x4 ASCQ=0x2
end_request: I/O error, dev sda, sector 126693711
sd 1:0:0:0: Device not ready: <6>: Current: sense key=0x2
    ASC=0x4 ASCQ=0x2
end_request: I/O error, dev sda, sector 126693711
sd 1:0:0:0: Device not ready: <6>: Current: sense key=0x2
    ASC=0x4 ASCQ=0x2
Quoted 3 lines

end_request: I/O error, dev sda, sector 126693711
=========

Using a new PSU and a powered hub made no difference. But I found a solution here:

http://alienghic.livejournal.com/382903.html

Basically, the problem is, as suspected, that the drive spins down / goes to suspend. This can be disabled with "sdparm --clear STANDBY -6 /dev/sda".

Quoted 7 lines
Quoted 3 lines

It seems to me to be an error that the kernel reports this as something like a hardware failure. Or at least very misleading.

Oh, nice. The usb-storage (SCSI) disk spins itself down and we can't handle that. Should we be disabling auto-spindown when we connect the device, or be able to handle this by sending the start command when needed?

There's more to this.

My Sandisk Cruzer Micro 1GB USB sticks suffer from this regression. Plug one in, it works for about 5 seconds, then the light goes off (bad). Next access requires a 30s timeout + reset. Etc..

This is with 2.6.23-rc6.
Works without any problems in 2.6.22. REGRESSION.

-ml

#9 lore raw

Re: Problems with USB disk [solved]

Quoted 96 lines · Mark Lord
Quoted 89 lines · Chuck Ebbert
Quoted 80 lines · Niels
Quoted 69 lines · Niels
Quoted 46 lines · Niels
Quoted 30 lines · Ismail D??nmez
Quoted 29 lines · On Wednesday 08 August 2007 13:48:29 you wrote:
Quoted 28 lines · Greg KH
Quoted 27 lines · Niels

Hi,

I'm having problems with a new 500 GB USB disk. It works, but sometimes I get these in dmesg:

usb 1-3: reset high speed USB device using ehci_hcd and address 2 usb 5-1: USB disconnect, address 2 drivers/usb/class/usblp.c: usblp0: removed
sd 0:0:0:0: Device not ready: <6>: Sense Key : 0x2 [current]

: ASC=0x4 ASCQ=0x2

end_request: I/O error, dev sda, sector 254148215 sd 0:0:0:0: Device not ready: <6>: Sense Key : 0x2 [current]

: ASC=0x4 ASCQ=0x2

end_request: I/O error, dev sda, sector 252434023 EXT3-fs error (device sda1): ext3_find_entry: reading directory #15761836 offset 0

There's also a printer connected. This is on a pci/usb2 card. When the above happens, I get I/O errors. When I mount the drive next, there are errors and often missing files. Quite annoying!

Quoted 9 lines
Quoted 6 lines
Quoted 6 lines
Quoted 3 lines

Kernel is 2.6.21

What's going on?

You have a low voltage issue, or a bad cable. The device is electronically disconnecting itself. Try using a externally-powered hub, or a new cable.

I am seeing a similar problem with 2.6.22 and 2.6.23-* kernels with my 60G iPod Video, works fine with 2.6.18 kernel though.

So far I'm seeing this:

- On 2.6.21 I mount the drive. After a while it spins down, and when I then unmount it, an error pops up in dmesg.

Quoted 7 lines

- On 2.6.18 I can't provoke the same error. The drive doesn't appear to spin down. I don't know if the data corruption from 2.6.21 occurs with regular use.

There are a number of other factor I need to eliminate on my system, but
that's it so far. CONFIG_USB_SUSPEND is not set on either kernel.

OK, on a vanilla 2.6.18.8 I also have this problem, with both the pci/usb2
card, and the usb1 on the board. I listen to music from the drive, and after some time (10-20 minutes or so), it freaks out:

=========
sd 1:0:0:0: Device not ready: <6>: Current: sense key=0x2

    ASC=0x4 ASCQ=0x2
end_request: I/O error, dev sda, sector 126693711
sd 1:0:0:0: Device not ready: <6>: Current: sense key=0x2
    ASC=0x4 ASCQ=0x2
end_request: I/O error, dev sda, sector 126693711
sd 1:0:0:0: Device not ready: <6>: Current: sense key=0x2
    ASC=0x4 ASCQ=0x2
Quoted 3 lines

end_request: I/O error, dev sda, sector 126693711
=========

Using a new PSU and a powered hub made no difference. But I found a solution
here:

http://alienghic.livejournal.com/382903.html

Quoted 8 lines

Basically, the problem is, as suspected, that the drive spins down / goes to
suspend. This can be disabled with "sdparm --clear STANDBY -6 /dev/sda".

It seems to me to be an error that the kernel reports this as something like
a hardware failure. Or at least very misleading.

Quoted 5 lines

Oh, nice. The usb-storage (SCSI) disk spins itself down and we can't handle that.
Should we be disabling auto-spindown when we connect the device, or be able to
handle this by sending the start command when needed?

Quoted 8 lines

There's more to this.

My Sandisk Cruzer Micro 1GB USB sticks suffer from this regression. Plug one in, it works for about 5 seconds, then the light goes off (bad). Next access requires a 30s timeout + reset. Etc..

This is with 2.6.23-rc6.
Works without any problems in 2.6.22. REGRESSION.

Disable CONFIG_USB_SUSPEND, that will fix the problem for you, or we can add your device to the quirk list.

thanks,

greg k-h

#10 lore raw

Re: [linux-usb-devel] Problems with USB disk [solved]

In reply to Mark Lord
Quoted 26 lines · Mark Lord
Quoted 24 lines · Chuck Ebbert
Quoted 23 lines
Quoted 9 lines

=========
sd 1:0:0:0: Device not ready: <6>: Current: sense key=0x2

    ASC=0x4 ASCQ=0x2
end_request: I/O error, dev sda, sector 126693711
sd 1:0:0:0: Device not ready: <6>: Current: sense key=0x2
    ASC=0x4 ASCQ=0x2
end_request: I/O error, dev sda, sector 126693711
sd 1:0:0:0: Device not ready: <6>: Current: sense key=0x2
    ASC=0x4 ASCQ=0x2
Quoted 3 lines

end_request: I/O error, dev sda, sector 126693711
=========

Using a new PSU and a powered hub made no difference. But I found a solution here:

http://alienghic.livejournal.com/382903.html

Basically, the problem is, as suspected, that the drive spins down / goes to suspend. This can be disabled with "sdparm --clear STANDBY -6 /dev/sda".

It seems to me to be an error that the kernel reports this as something like a hardware failure. Or at least very misleading.

Quoted 7 lines
Quoted 3 lines

Oh, nice. The usb-storage (SCSI) disk spins itself down and we can't handle that. Should we be disabling auto-spindown when we connect the device, or be able to handle this by sending the start command when needed?

There's more to this.

My Sandisk Cruzer Micro 1GB USB sticks suffer from this regression.

I seriously doubt that. Are you claiming that your USB stick spins itself down during a suspend? And then requires to be spun back up before it will resume proper operation?

(Hint: Flash memory devices don't contain rotating media...)

Alan Stern

#11 lore raw

Re: [linux-usb-devel] Problems with USB disk [solved]

Quoted 3 lines · Alan Stern
Quoted 1 line · Mark Lord

Chuck Ebbert wrote:

..

Quoted 8 lines
Quoted 6 lines
Quoted 3 lines

Oh, nice. The usb-storage (SCSI) disk spins itself down and we can't handle that. Should we be disabling auto-spindown when we connect the device, or be able to handle this by sending the start command when needed?

There's more to this.

My Sandisk Cruzer Micro 1GB USB sticks suffer from this regression.

I seriously doubt that. Are you claiming that your USB stick spins itself down during a suspend? And then requires to be spun back up before it will resume proper operation?

No, the machine is not being suspended at all.

What happens is, there's a nice little LED on the Cruzer stick, that is "lit" when the stick itself is not in a "power suspend" state (or whatever you USB folks call it).

On 2.6.22, that little LED stays "on" normally, and flickers off/on when data is being transfered.

The new "USB autosuspend" logic in 2.6.23 now causes that little LED to turn off after a few seconds of inactivity.

Once that happens, the USB stick is not accessible until after a longish timeout (~30s I think), followed by a USB reset. Then it is usable again until the next inactivity timeout and autosuspend (a few seconds).

Etc.

#12 lore raw

Re: [linux-usb-devel] Problems with USB disk [solved]

Quoted 16 lines · Mark Lord
Quoted 3 lines · Alan Stern
Quoted 1 line · Mark Lord

Chuck Ebbert wrote:

..

Quoted 10 lines
Quoted 6 lines
Quoted 3 lines

Oh, nice. The usb-storage (SCSI) disk spins itself down and we can't handle that. Should we be disabling auto-spindown when we connect the device, or be able to handle this by sending the start command when needed?

There's more to this.

My Sandisk Cruzer Micro 1GB USB sticks suffer from this regression.

I seriously doubt that. Are you claiming that your USB stick spins itself down during a suspend? And then requires to be spun back up before it will resume proper operation?

Quoted 5 lines

No, the machine is not being suspended at all.

What happens is, there's a nice little LED on the Cruzer stick, that is "lit" when the stick itself is not in a "power suspend" state (or whatever you USB folks call it).

We call it "suspended". (Wasn't there an episode of Classic Trek where Mr. Spock explained to somebody, "I call them `ears'."?)

Quoted 9 lines

On 2.6.22, that little LED stays "on" normally, and flickers off/on when data is being transfered.

The new "USB autosuspend" logic in 2.6.23 now causes that little LED to turn off after a few seconds of inactivity.

Once that happens, the USB stick is not accessible until after a longish timeout (~30s I think), followed by a USB reset. Then it is usable again until the next inactivity timeout and autosuspend (a few seconds).

So this _isn't_ the regression described above -- to wit, that the drive gets spun down and then won't work without first being spun back

Quoted 1 line · up. You
Quoted 1 line
Quoted 1 line

My Sandisk Cruzer Micro 1GB USB sticks suffer from this regression.

But it doesn't. It suffers from a different regression.

Alan Stern

#13 lore raw

Re: [linux-usb-devel] Problems with USB disk [solved]

Quoted 1 line · Alan Stern

On Thu, 13 Sep 2007, Mark Lord wrote:

..

Quoted 17 lines
Quoted 3 lines

What happens is, there's a nice little LED on the Cruzer stick, that is "lit" when the stick itself is not in a "power suspend" state (or whatever you USB folks call it).

We call it "suspended". (Wasn't there an episode of Classic Trek where Mr. Spock explained to somebody, "I call them `ears'."?)

Quoted 9 lines

On 2.6.22, that little LED stays "on" normally, and flickers off/on when data is being transfered.

The new "USB autosuspend" logic in 2.6.23 now causes that little LED to turn off after a few seconds of inactivity.

Once that happens, the USB stick is not accessible until after a longish timeout (~30s I think), followed by a USB reset. Then it is usable again until the next inactivity timeout and autosuspend (a few seconds).

Quoted 7 lines

So this _isn't_ the regression described above -- to wit, that the drive gets spun down and then won't work without first being spun back

Quoted 1 line · up. You
Quoted 1 line
Quoted 1 line

My Sandisk Cruzer Micro 1GB USB sticks suffer from this regression.

But it doesn't. It suffers from a different regression.

Perhaps, but that doesn't necessarily follow from the above.

Quoted 1 line

From this observer's point of view (and being an expert on disk technologies),

the same "spin up" issue for rotating media could be the culprit here too.

A reset to a disk drive usually (not always) causes it to spin up.

Regardless, Greg has acknowledged the regression and is planning to revert things.

Cheers

-------------------------------------------------------------------------
This SF.net email is sponsored by: Microsoft Defy all challenges. Microsoft(R) Visual Studio 2005.
http://clk.atdmt.com/MRT/go/vse0120000070mrt/direct/01/
_______________________________________________
[email protected]
To unsubscribe, use the last form field at:
https://lists.sourceforge.net/lists/listinfo/linux-usb-devel

#14 lore raw
In reply to Greg KH
Quoted 24 lines · Greg KH
Quoted 23 lines · Niels

Hi,

I'm having problems with a new 500 GB USB disk. It works, but sometimes I get these in dmesg:

usb 1-3: reset high speed USB device using ehci_hcd and address 2 usb 5-1: USB disconnect, address 2
drivers/usb/class/usblp.c: usblp0: removed
sd 0:0:0:0: Device not ready: <6>: Sense Key : 0x2 [current] : ASC=0x4 ASCQ=0x2
end_request: I/O error, dev sda, sector 254148215
sd 0:0:0:0: Device not ready: <6>: Sense Key : 0x2 [current] : ASC=0x4 ASCQ=0x2
end_request: I/O error, dev sda, sector 252434023
EXT3-fs error (device sda1): ext3_find_entry: reading directory #15761836 offset 0

There's also a printer connected. This is on a pci/usb2 card. When the above happens, I get I/O errors. When I mount the drive next, there are errors and often missing files. Quite annoying!

Quoted 8 lines
Quoted 3 lines

Kernel is 2.6.21

What's going on?

You have a low voltage issue, or a bad cable. The device is electronically disconnecting itself. Try using a externally-powered hub, or a new cable.

I see the external drive becoming read-only, although I haven't checked the dmesg for the events, since other things in my system generate a bunch of output I have to wade through.

New cable, separate power, doesn't do it under 2.6.20-* Fedora or 2.6.21.x kernel.org kernels.

I'll check the dmesg next time it happens, but I doubt a kernel version change would heal the hardware issues you mention.

Signature · 3 lines
Bill Davidsen <[email protected]>
  "We have more to fear from the bungling of the incompetent than from
the machinations of the wicked."  - from Slashdot