From: Albretch Mueller on
~
I have a 500 GB Maxtor OneTouch 4 external USB powered mini drive
that is missfunctioning. Even though I mount it rw, it apparently
resets itself to ro and I have also noticed that when the drive is
idle for a while it starts to missfunction, but not when I keep it
busy transferring data
~
Most problems with such drives are with the interface to the drives
and not the drives themselves, so I need to know if I could save the
drive (and of course the data) by taking the actual drive out and
putting it in another encasement
~
How can you tell exactly which model number you have? Maxtor tells me
~
http://www.seagate.com/ww/v/index.jsp?locale=en-US&name=ot4&vgnextoid=a7b42c9e46914110VgnVCM100000f5ee0a0aRCRD
~
it should be a STM90####OTA3E1-RK but there are 11 options there and
it is impossible to see exactly what mine is
~
I was having these problems under Windows too, I just used Linux
trying to troubleshoot/get more info out of it. This is what I
sometimes get when I try to list my drive
~
~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~
~
total 4
?--------- ? ? ? ? ? lost+found
drwxr-xr-x 3 root root 4096 Jan 7 07:33 prjx
~
~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~
~
this is what I get from dmesg when I mount the drive
~
usb 1-7: new high speed USB device using ehci_hcd and address 3
usb 1-7: configuration #1 chosen from 1 choice
scsi0 : SCSI emulation for USB Mass Storage devices
usb-storage: device found at 3
usb-storage: waiting for device to settle before scanning
scsi 0:0:0:0: Direct-Access Maxtor OneTouch 0125 PQ: 0
ANSI: 4
SCSI device sda: 488397168 512-byte hdwr sectors (250059 MB)
sda: Write Protect is off
sda: Mode Sense: 2d 08 00 00
sda: assuming drive cache: write through
SCSI device sda: 488397168 512-byte hdwr sectors (250059 MB)
sda: Write Protect is off
sda: Mode Sense: 2d 08 00 00
sda: assuming drive cache: write through
sda: sda1
sd 0:0:0:0: Attached scsi disk sda
usb-storage: device scan complete
sd 0:0:0:0: Device not ready: <6>: Current: sense key=0x2
ASC=0x4 ASCQ=0x2
end_request: I/O error, dev sda, sector 0
Buffer I/O error on device sda, logical block 0
kjournald starting. Commit interval 5 seconds
EXT3 FS on sda1, internal journal
EXT3-fs: mounted filesystem with ordered data mode.
sd 0:0:0:0: Device not ready: <6>: Current: sense key=0x2
ASC=0x4 ASCQ=0x2
end_request: I/O error, dev sda, sector 12839
Aborting journal on device sda1.
ext3_abort called.
EXT3-fs error (device sda1): ext3_journal_start_sb: Detected aborted
journal
Remounting filesystem read-only
kjournald starting. Commit interval 5 seconds
EXT3 FS on sda1, internal journal
EXT3-fs: recovery complete.
EXT3-fs: mounted filesystem with ordered data mode.
kjournald starting. Commit interval 5 seconds
EXT3 FS on sda1, internal journal
EXT3-fs: mounted filesystem with ordered data mode.
sd 0:0:0:0: Device not ready: <6>: Current: sense key=0x2
ASC=0x4 ASCQ=0x2
end_request: I/O error, dev sda, sector 403668791
sd 0:0:0:0: Device not ready: <6>: Current: sense key=0x2
ASC=0x4 ASCQ=0x2
end_request: I/O error, dev sda, sector 403443887
Buffer I/O error on device sda1, logical block 50430478
lost page write due to I/O error on sda1
Buffer I/O error on device sda1, logical block 50430479
lost page write due to I/O error on sda1
Buffer I/O error on device sda1, logical block 50430480
lost page write due to I/O error on sda1
Buffer I/O error on device sda1, logical block 50430481
lost page write due to I/O error on sda1
Buffer I/O error on device sda1, logical block 50430482
lost page write due to I/O error on sda1
Buffer I/O error on device sda1, logical block 50430483
lost page write due to I/O error on sda1
sd 0:0:0:0: Device not ready: <6>: Current: sense key=0x2
ASC=0x4 ASCQ=0x2
end_request: I/O error, dev sda, sector 403472551
Buffer I/O error on device sda1, logical block 50434061
lost page write due to I/O error on sda1
sd 0:0:0:0: Device not ready: <6>: Current: sense key=0x2
ASC=0x4 ASCQ=0x2
end_request: I/O error, dev sda, sector 403472663
Buffer I/O error on device sda1, logical block 50434075
lost page write due to I/O error on sda1
sd 0:0:0:0: Device not ready: <6>: Current: sense key=0x2
ASC=0x4 ASCQ=0x2
end_request: I/O error, dev sda, sector 403668599
Buffer I/O error on device sda1, logical block 50458567
lost page write due to I/O error on sda1
sd 0:0:0:0: Device not ready: <6>: Current: sense key=0x2
ASC=0x4 ASCQ=0x2
end_request: I/O error, dev sda, sector 403472671
sd 0:0:0:0: Device not ready: <6>: Current: sense key=0x2
ASC=0x4 ASCQ=0x2
end_request: I/O error, dev sda, sector 174463
Aborting journal on device sda1.
ext3_abort called.
EXT3-fs error (device sda1): ext3_journal_start_sb: Detected aborted
journal
Remounting filesystem read-only
~
and the USB controllers in my box are:
~
00:03.0 USB Controller: Silicon Integrated Systems [SiS] USB 1.0
Controller (rev 0f) (prog-if 10 [OHCI])
Subsystem: Holco Enterprise Co, Ltd/Shuttle Computer Unknown
device 3086
Flags: bus master, medium devsel, latency 64, IRQ 18
Memory at fdfff000 (32-bit, non-prefetchable) [size=4K]
00:03.1 USB Controller: Silicon Integrated Systems [SiS] USB 1.0
Controller (rev 0f) (prog-if 10 [OHCI])
Subsystem: Holco Enterprise Co, Ltd/Shuttle Computer Unknown
device 3086
Flags: bus master, medium devsel, latency 64, IRQ 19
Memory at fdffe000 (32-bit, non-prefetchable) [size=4K]
00:03.3 USB Controller: Silicon Integrated Systems [SiS] USB 2.0
Controller (prog-if 20 [EHCI])
Subsystem: Holco Enterprise Co, Ltd/Shuttle Computer Unknown
device 3086
Flags: bus master, medium devsel, latency 64, IRQ 17
Memory at fdffd000 (32-bit, non-prefetchable) [size=4K]
Capabilities: <access denied>
~
How can I fix that problem?
~
Thanks
lbrtchx
From: Bryce on
Albretch Mueller wrote:

> ~
> I have a 500 GB Maxtor OneTouch 4 external USB powered
> mini drive
> that is missfunctioning. Even though I mount it rw, it
> apparently resets itself to ro and I have also noticed
> that when the drive is idle for a while it starts to
> missfunction, but not when I keep it busy transferring
> data ~
> Most problems with such drives are with the interface to
> the drives
> and not the drives themselves, so I need to know if I
> could save the drive (and of course the data) by taking
> the actual drive out and putting it in another encasement
> ~
> How can you tell exactly which model number you have?
> Maxtor tells me
> ~
> http://www.seagate.com/ww/v/index.jsp?locale=en-
US&name=ot4&vgnextoid=a7b42c9e46914110VgnVCM100000f5ee0a0aRCRD
> ~
> it should be a STM90####OTA3E1-RK but there are 11
> options there and
> it is impossible to see exactly what mine is
> ~
> I was having these problems under Windows too, I just
> used Linux
> trying to troubleshoot/get more info out of it. This is
> what I sometimes get when I try to list my drive
> ~
> ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~
> ~
> total 4
> ?--------- ? ? ? ? ? lost+found
> drwxr-xr-x 3 root root 4096 Jan 7 07:33 prjx
> ~
> ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~
> ~
> this is what I get from dmesg when I mount the drive
> ~
> usb 1-7: new high speed USB device using ehci_hcd and
> address 3 usb 1-7: configuration #1 chosen from 1 choice
> scsi0 : SCSI emulation for USB Mass Storage devices
> usb-storage: device found at 3
> usb-storage: waiting for device to settle before scanning
> scsi 0:0:0:0: Direct-Access Maxtor OneTouch
> 0125 PQ: 0 ANSI: 4
> SCSI device sda: 488397168 512-byte hdwr sectors (250059
> MB) sda: Write Protect is off
> sda: Mode Sense: 2d 08 00 00
> sda: assuming drive cache: write through
> SCSI device sda: 488397168 512-byte hdwr sectors (250059
> MB) sda: Write Protect is off
> sda: Mode Sense: 2d 08 00 00
> sda: assuming drive cache: write through
> sda: sda1
> sd 0:0:0:0: Attached scsi disk sda
> usb-storage: device scan complete
> sd 0:0:0:0: Device not ready: <6>: Current: sense key=0x2
> ASC=0x4 ASCQ=0x2
> end_request: I/O error, dev sda, sector 0
> Buffer I/O error on device sda, logical block 0
> kjournald starting. Commit interval 5 seconds
> EXT3 FS on sda1, internal journal
> EXT3-fs: mounted filesystem with ordered data mode.
> sd 0:0:0:0: Device not ready: <6>: Current: sense key=0x2
> ASC=0x4 ASCQ=0x2
> end_request: I/O error, dev sda, sector 12839
> Aborting journal on device sda1.
> ext3_abort called.
> EXT3-fs error (device sda1): ext3_journal_start_sb:
> Detected aborted journal
> Remounting filesystem read-only
> kjournald starting. Commit interval 5 seconds
> EXT3 FS on sda1, internal journal
> EXT3-fs: recovery complete.
> EXT3-fs: mounted filesystem with ordered data mode.
> kjournald starting. Commit interval 5 seconds
> EXT3 FS on sda1, internal journal
> EXT3-fs: mounted filesystem with ordered data mode.
> sd 0:0:0:0: Device not ready: <6>: Current: sense key=0x2
> ASC=0x4 ASCQ=0x2
> end_request: I/O error, dev sda, sector 403668791
> sd 0:0:0:0: Device not ready: <6>: Current: sense key=0x2
> ASC=0x4 ASCQ=0x2
> end_request: I/O error, dev sda, sector 403443887
> Buffer I/O error on device sda1, logical block 50430478
> lost page write due to I/O error on sda1
> Buffer I/O error on device sda1, logical block 50430479
> lost page write due to I/O error on sda1
> Buffer I/O error on device sda1, logical block 50430480
> lost page write due to I/O error on sda1
> Buffer I/O error on device sda1, logical block 50430481
> lost page write due to I/O error on sda1
> Buffer I/O error on device sda1, logical block 50430482
> lost page write due to I/O error on sda1
> Buffer I/O error on device sda1, logical block 50430483
> lost page write due to I/O error on sda1
> sd 0:0:0:0: Device not ready: <6>: Current: sense key=0x2
> ASC=0x4 ASCQ=0x2
> end_request: I/O error, dev sda, sector 403472551
> Buffer I/O error on device sda1, logical block 50434061
> lost page write due to I/O error on sda1
> sd 0:0:0:0: Device not ready: <6>: Current: sense key=0x2
> ASC=0x4 ASCQ=0x2
> end_request: I/O error, dev sda, sector 403472663
> Buffer I/O error on device sda1, logical block 50434075
> lost page write due to I/O error on sda1
> sd 0:0:0:0: Device not ready: <6>: Current: sense key=0x2
> ASC=0x4 ASCQ=0x2
> end_request: I/O error, dev sda, sector 403668599
> Buffer I/O error on device sda1, logical block 50458567
> lost page write due to I/O error on sda1
> sd 0:0:0:0: Device not ready: <6>: Current: sense key=0x2
> ASC=0x4 ASCQ=0x2
> end_request: I/O error, dev sda, sector 403472671
> sd 0:0:0:0: Device not ready: <6>: Current: sense key=0x2
> ASC=0x4 ASCQ=0x2
> end_request: I/O error, dev sda, sector 174463
> Aborting journal on device sda1.
> ext3_abort called.
> EXT3-fs error (device sda1): ext3_journal_start_sb:
> Detected aborted journal
> Remounting filesystem read-only
> ~
> and the USB controllers in my box are:
> ~
> 00:03.0 USB Controller: Silicon Integrated Systems [SiS]
> USB 1.0 Controller (rev 0f) (prog-if 10 [OHCI])
> Subsystem: Holco Enterprise Co, Ltd/Shuttle
> Computer Unknown
> device 3086
> Flags: bus master, medium devsel, latency 64, IRQ
> 18 Memory at fdfff000 (32-bit, non-prefetchable)
> [size=4K]
> 00:03.1 USB Controller: Silicon Integrated Systems [SiS]
> USB 1.0 Controller (rev 0f) (prog-if 10 [OHCI])
> Subsystem: Holco Enterprise Co, Ltd/Shuttle
> Computer Unknown
> device 3086
> Flags: bus master, medium devsel, latency 64, IRQ
> 19 Memory at fdffe000 (32-bit, non-prefetchable)
> [size=4K]
> 00:03.3 USB Controller: Silicon Integrated Systems [SiS]
> USB 2.0 Controller (prog-if 20 [EHCI])
> Subsystem: Holco Enterprise Co, Ltd/Shuttle
> Computer Unknown
> device 3086
> Flags: bus master, medium devsel, latency 64, IRQ
> 17 Memory at fdffd000 (32-bit, non-prefetchable)
> [size=4K] Capabilities: <access denied>
> ~
> How can I fix that problem?
> ~
> Thanks
> lbrtchx

I followed the seagate link you provided. It appears that
your 500gB drive is STM905003OTA3E1-RK.

The Seagate site offers the Seatools diagnostic package as a
download. This should tell you a lot about what is wrong
and perhaps even fix it!

You newsgroup posting will reach more readers if you don't
post from google groups. Many newsgroup users block posts
from google because it is a major path for spam. We don't
want to know about cheap sneakers.

Bryce


From: Trevor Hemsley on
On Sun, 10 Jan 2010 08:54:54 UTC in comp.os.linux.hardware, Albretch Mueller
<lbrtchx(a)gmail.com> wrote:

> I have a 500 GB Maxtor OneTouch 4 external USB powered mini drive
> that is missfunctioning. Even though I mount it rw, it apparently
> resets itself to ro and I have also noticed that when the drive is
> idle for a while it starts to missfunction, but not when I keep it
> busy transferring data

This helps my Seagate external drive.

for f in /sys/class/scsi_disk/*; do echo 1 > $f/allow_restart; done

--
Trevor Hemsley, Brighton, UK
Trevor dot Hemsley at ntlworld dot com