Re: usb drive errors with automount
On 11/17/06, Roby [EMAIL PROTECTED] wrote: Seems like doing an umount after/during unplug would lead to data loss if the device had been written to recently. How do buffers get flushed? No. It's the unplugging device without unpluggins/syncing, what causes data loss. On 17.11.06 22:18, Jason Dunsmore wrote: Seems like it'd just have to mount it with the sync or async option. According to man page, it does not work for vfat, which is I think the most used FS on USB disks. -- Matus UHLAR - fantomas, [EMAIL PROTECTED] ; http://www.fantomas.sk/ Warning: I wish NOT to receive e-mail advertising to this address. Varovanie: na tuto adresu chcem NEDOSTAVAT akukolvek reklamnu postu. Linux IS user friendly, it's just selective who its friends are... -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: usb drive errors with automount
On 11/16/06, Matus UHLAR - fantomas [EMAIL PROTECTED] wrote: you can use 'usbmount' for automatic mounting of usb storage devices. However I'm afraid your USB flashdisk is dead... The USB flashdisk isn't dead. It works when I mount it manually. I didn't know about usbmount. I'll give it a try. Thanks. -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: usb drive errors with automount
Jason Dunsmore wrote: On 11/16/06, Matus UHLAR - fantomas [EMAIL PROTECTED] wrote: you can use 'usbmount' for automatic mounting of usb storage devices. However I'm afraid your USB flashdisk is dead... The USB flashdisk isn't dead. It works when I mount it manually. I didn't know about usbmount. I'll give it a try. usbmount: This package automatically mounts USB mass storage devices (typically USB pens) when they are plugged in, and unmounts them when they are removed... Seems like doing an umount after/during unplug would lead to data loss if the device had been written to recently. How do buffers get flushed? -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: usb drive errors with automount
On 11/17/06, Roby [EMAIL PROTECTED] wrote: usbmount: This package automatically mounts USB mass storage devices (typically USB pens) when they are plugged in, and unmounts them when they are removed... Seems like doing an umount after/during unplug would lead to data loss if the device had been written to recently. How do buffers get flushed? Seems like it'd just have to mount it with the sync or async option. -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
usb drive errors with automount
I just started having trouble automounting my usb drive. When I plug it in, the kernel recognizes it: usb 5-8.1: new high speed USB device using ehci_hcd and address 5 usb 5-8.1: configuration #1 chosen from 1 choice scsi34 : SCSI emulation for USB Mass Storage devices usb-storage: device found at 5 usb-storage: waiting for device to settle before scanning Vendor: Corsair Model: Flash Voyager Rev: 1.00 Type: Direct-Access ANSI SCSI revision: 00 SCSI device sdd: 4005888 512-byte hdwr sectors (2051 MB) sdd: Write Protect is off sdd: Mode Sense: 00 26 00 00 sdd: assuming drive cache: write through SCSI device sdd: 4005888 512-byte hdwr sectors (2051 MB) sdd: Write Protect is off sdd: Mode Sense: 00 26 00 00 sdd: assuming drive cache: write through sdd: sdd1 sd 34:0:0:0: Attached scsi removable disk sdd usb-storage: device scan complete but then, when I try to access it, I see the following messages in dmesg: FAT: Directory bread(block 515) failed 28:0:0:0: rejecting I/O to dead device FAT: Directory bread(block 516) failed 28:0:0:0: rejecting I/O to dead device FAT: Directory bread(block 517) failed 28:0:0:0: rejecting I/O to dead device FAT: Directory bread(block 518) failed 28:0:0:0: rejecting I/O to dead device FAT: Directory bread(block 519) failed 28:0:0:0: rejecting I/O to dead device FAT: Directory bread(block 520) failed 28:0:0:0: rejecting I/O to dead device FAT: Directory bread(block 521) failed 28:0:0:0: rejecting I/O to dead device FAT: Directory bread(block 522) failed 28:0:0:0: rejecting I/O to dead device This just started happening. I've been using automount successfully for several months on Debian testing. I'm using kernel 2.6.16.13. Here's what's in /etc/auto.removable key_drv-fstype=vfat,rw,async,uid=1000,gid=1000 :/dev/key_drv1 I've tried unloading the ehci_hcd module, since I'd had similar troubles with it in the past, but no luck. Any ideas? -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: usb drive errors with automount
On 16.11.06 12:03, Jason Dunsmore wrote: I just started having trouble automounting my usb drive. When I plug it in, the kernel recognizes it: usb-storage: device found at 5 usb-storage: waiting for device to settle before scanning Vendor: Corsair Model: Flash Voyager Rev: 1.00 Type: Direct-Access ANSI SCSI revision: 00 but then, when I try to access it, I see the following messages in dmesg: FAT: Directory bread(block 515) failed 28:0:0:0: rejecting I/O to dead device This just started happening. I've been using automount successfully for several months on Debian testing. I'm using kernel 2.6.16.13. you can use 'usbmount' for automatic mounting of usb storage devices. However I'm afraid your USB flashdisk is dead... -- Matus UHLAR - fantomas, [EMAIL PROTECTED] ; http://www.fantomas.sk/ Warning: I wish NOT to receive e-mail advertising to this address. Varovanie: na tuto adresu chcem NEDOSTAVAT akukolvek reklamnu postu. - Have you got anything without Spam in it? - Well, there's Spam egg sausage and Spam, that's not got much Spam in it. -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: BadCRC Drive Errors on Software RAID1
On Thu, Mar 23, 2006 at 05:55:55PM +, Andy wrote:
Hello List,
I am running 2x Seagate 250GB SATA-II 7200.9 disks configured as linux
software RAID-1.
The following errors occasionally appear in /var/log/kern.log:
kernel: ata1: translated ATA stat/err 0x51/84 to SCSI
SK/ASC/ASCQ 0xb/47/00
kernel: ata1: status=0x51 { DriveReady SeekComplete Error }
kernel: ata1: error=0x84 { DriveStatusError BadCRC }
I had assumed I have a bad disk, but the odd thing is when I connect
either disk individually I can use DD to fill it with zeros to its
capacity without any errors.
Do you think I have a bad disk, or should I suspect a problem with my
SATA controller or RAID-1 setup?
Thanks, Andy
I am having the same problem and did a quick google search a couple of
weeks ago. The answer at the time was that it's a bad cable. I haven't
had a chance to check my cable yet, but it made me feel better about
losing any data.
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: drive errors!
On Thu, 2003-03-13 at 05:48, Tom Allison wrote:
[EMAIL PROTECTED] wrote:
On Wed, 12 Mar 2003 17:29:05 -0500
Tom Allison [EMAIL PROTECTED] wrote:
I've been runnign this PC for about a year now.
I recently upgraded from 2.4.18 to 2.4.20.
And this is the thanks I get
Any suggestions? It seems to work.
Mar 12 12:14:21 gandolf kernel: hda: dma_intr: error=0x84 {
DriveStatusError BadCRC }Mar 12 12:14:21 gandolf kernel: hda: dma_intr:
status=0x51 { DriveReady
SeekCompleteError }
Do make menuconfig, and go to ATA/IDE/MFM/RLL support | IDE, ATA, and ATAPI Block
devices, and set Use multi-mode by default. See the help text for that option.
Kevin
Some additional information about the problem.
The kernel is a stock Debian kernel. So was the 2.4.18 kernel.
Under 2.4.18, I do not get these errors.
If I revert back to the 2.4.18 kernel, the errors go away.
Therefore I am not certain that this drive is on the virge of death,
rather I think that the kernel is just buggered.
--
Boling's postulate:
If you're feeling good, don't worry. You'll get over it.
Okay - what are the specs of the drive - make, capacity? This is
*possibly* the kernel not handling it well, but two considerations:
1) Do you really want to be stuck with a system without a hard drive?
2) If the hard drive can be kept working, wouldn't you be able to find
use for the extra storage of both it and another drive?
The only thing that comes to mind as an alternative now is to try
rolling your own 2.4.20 kernel, and seeing if you still get the errors -
if there are other stock 2.4.20 kernels available to try out, that work
for your configuration, I'd also see if any of them spew these errors.
In other words, is it a problem in the kernel, or is 2.4.20 just the
first kernel smart enough to catch that this is a bum drive?
--
Mark L. Kahnt, FLMI/M, ALHC, HIA, AIAA, ACS, MHP
ML Kahnt New Markets Consulting
Tel: (613) 531-8684 / (613) 539-0935
Email: [EMAIL PROTECTED]
signature.asc
Description: This is a digitally signed message part
Re: drive errors!
Hi
I had a similiar problem with a WD 30gb drive. Used WD diag utils and it
seemed to solve the problem. I would agree on backup, but you may still
get some live out of the drive.
Regards
Tinus
On Thu, 2003-03-13 at 00:29, Tom Allison wrote:
I've been runnign this PC for about a year now.
I recently upgraded from 2.4.18 to 2.4.20.
And this is the thanks I get
Any suggestions? It seems to work.
Mar 12 12:14:21 gandolf kernel: hda: dma_intr: error=0x84 {
DriveStatusError BadCRC }Mar 12 12:14:21 gandolf kernel: hda: dma_intr:
status=0x51 { DriveReady
SeekCompleteError }
Mar 12 12:14:21 gandolf kernel: hda: dma_intr: error=0x84 {
DriveStatusError BadCRC }Mar 12 12:14:21 gandolf kernel: hda: dma_intr:
status=0x51 { DriveReady
SeekCompleteError }
Mar 12 12:14:21 gandolf kernel: hda: dma_intr: error=0x84 {
DriveStatusError BadCRC }Mar 12 12:17:32 gandolf kernel: hda: dma_intr:
status=0x51 { DriveReady
SeekCompleteError }
Mar 12 12:17:32 gandolf kernel: hda: dma_intr: error=0x84 {
DriveStatusError BadCRC }Mar 12 12:17:32 gandolf kernel: hda: dma_intr:
status=0x51 { DriveReady
SeekCompleteError }
Mar 12 12:17:32 gandolf kernel: hda: dma_intr: error=0x84 {
DriveStatusError BadCRC }Mar 12 12:17:32 gandolf kernel: hda: dma_intr:
status=0x51 { DriveReady
SeekCompleteError }
Mar 12 12:17:32 gandolf kernel: hda: dma_intr: error=0x84 {
DriveStatusError BadCRC }Mar 12 12:26:18 gandolf kernel: hda: dma_intr:
status=0x51 { DriveReady
SeekCompleteError }
Mar 12 12:26:18 gandolf kernel: hda: dma_intr: error=0x84 {
DriveStatusError BadCRC }Mar 12 12:26:18 gandolf kernel: hda: dma_intr:
status=0x51 { DriveReady
SeekCompleteError }
Mar 12 12:26:18 gandolf kernel: hda: dma_intr: error=0x84 {
DriveStatusError BadCRC }Mar 12 12:26:18 gandolf kernel: hda: dma_intr:
status=0x51 { DriveReady
SeekCompleteError }
Mar 12 12:26:18 gandolf kernel: hda: dma_intr: error=0x84 {
DriveStatusError BadCRC }Mar 12 12:32:35 gandolf kernel: hda: dma_intr:
status=0x51 { DriveReady
SeekCompleteError }
Mar 12 12:32:35 gandolf kernel: hda: dma_intr: error=0x84 {
DriveStatusError BadCRC }Mar 12 12:32:35 gandolf kernel: hda: dma_intr:
status=0x51 { DriveReady
SeekCompleteError }
--
Boling's postulate:
If you're feeling good, don't worry. You'll get over it.
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: drive errors!
I suggest you changing this drive before it's too late.
I had the same problem and 5 days after the drive crashes.
On Thu, 2003-03-13 at 00:29, Tom Allison wrote:
I've been runnign this PC for about a year now.
I recently upgraded from 2.4.18 to 2.4.20.
And this is the thanks I get
Any suggestions? It seems to work.
Mar 12 12:14:21 gandolf kernel: hda: dma_intr: error=0x84 {
DriveStatusError BadCRC }Mar 12 12:14:21 gandolf kernel: hda: dma_intr:
status=0x51 { DriveReady
SeekCompleteError }
Mar 12 12:14:21 gandolf kernel: hda: dma_intr: error=0x84 {
DriveStatusError BadCRC }Mar 12 12:14:21 gandolf kernel: hda: dma_intr:
status=0x51 { DriveReady
SeekCompleteError }
Mar 12 12:14:21 gandolf kernel: hda: dma_intr: error=0x84 {
DriveStatusError BadCRC }Mar 12 12:17:32 gandolf kernel: hda: dma_intr:
status=0x51 { DriveReady
SeekCompleteError }
Mar 12 12:17:32 gandolf kernel: hda: dma_intr: error=0x84 {
DriveStatusError BadCRC }Mar 12 12:17:32 gandolf kernel: hda: dma_intr:
status=0x51 { DriveReady
SeekCompleteError }
Mar 12 12:17:32 gandolf kernel: hda: dma_intr: error=0x84 {
DriveStatusError BadCRC }Mar 12 12:17:32 gandolf kernel: hda: dma_intr:
status=0x51 { DriveReady
SeekCompleteError }
Mar 12 12:17:32 gandolf kernel: hda: dma_intr: error=0x84 {
DriveStatusError BadCRC }Mar 12 12:26:18 gandolf kernel: hda: dma_intr:
status=0x51 { DriveReady
SeekCompleteError }
Mar 12 12:26:18 gandolf kernel: hda: dma_intr: error=0x84 {
DriveStatusError BadCRC }Mar 12 12:26:18 gandolf kernel: hda: dma_intr:
status=0x51 { DriveReady
SeekCompleteError }
Mar 12 12:26:18 gandolf kernel: hda: dma_intr: error=0x84 {
DriveStatusError BadCRC }Mar 12 12:26:18 gandolf kernel: hda: dma_intr:
status=0x51 { DriveReady
SeekCompleteError }
Mar 12 12:26:18 gandolf kernel: hda: dma_intr: error=0x84 {
DriveStatusError BadCRC }Mar 12 12:32:35 gandolf kernel: hda: dma_intr:
status=0x51 { DriveReady
SeekCompleteError }
Mar 12 12:32:35 gandolf kernel: hda: dma_intr: error=0x84 {
DriveStatusError BadCRC }Mar 12 12:32:35 gandolf kernel: hda: dma_intr:
status=0x51 { DriveReady
SeekCompleteError }
--
--
Sebastien PICARD
IUT Belfort-Montbeliard
Technicien de Recherche
et Formation
Tel : (+33) 3 84 58 77 79
--
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: drive errors!
On Thu, 13 Mar 2003 05:48:01 -0500
Tom Allison [EMAIL PROTECTED] wrote:
[EMAIL PROTECTED] wrote:
On Wed, 12 Mar 2003 17:29:05 -0500
Tom Allison [EMAIL PROTECTED] wrote:
I've been runnign this PC for about a year now.
I recently upgraded from 2.4.18 to 2.4.20.
And this is the thanks I get
Any suggestions? It seems to work.
Mar 12 12:14:21 gandolf kernel: hda: dma_intr: error=0x84 {
DriveStatusError BadCRC }Mar 12 12:14:21 gandolf kernel: hda:
dma_intr: status=0x51 { DriveReady
SeekCompleteError }
Do make menuconfig, and go to ATA/IDE/MFM/RLL support | IDE, ATA,
and ATAPI Block devices, and set Use multi-mode by default. See
the help text for that option.
Kevin
Some additional information about the problem.
The kernel is a stock Debian kernel. So was the 2.4.18 kernel.
Under 2.4.18, I do not get these errors.
If I revert back to the 2.4.18 kernel, the errors go away.
Therefore I am not certain that this drive is on the virge of death,
rather I think that the kernel is just buggered.
I had problems like that with a sis chipset and ran the cerberus hd test
on the drive for one week flat on the drive trying to destroy it (if it
doesn't work at all you don't get BS form the warranty guys) but didn't
succeed.
This was about 6 month ago.About 3 month ago happened the same thing
again. It affects only the ext3 partitions.I tried now with reiser for
/ and it works fine so far.
Klaus
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
drive errors!
I've been runnign this PC for about a year now.
I recently upgraded from 2.4.18 to 2.4.20.
And this is the thanks I get
Any suggestions? It seems to work.
Mar 12 12:14:21 gandolf kernel: hda: dma_intr: error=0x84 {
DriveStatusError BadCRC }Mar 12 12:14:21 gandolf kernel: hda: dma_intr:
status=0x51 { DriveReady
SeekCompleteError }
Mar 12 12:14:21 gandolf kernel: hda: dma_intr: error=0x84 {
DriveStatusError BadCRC }Mar 12 12:14:21 gandolf kernel: hda: dma_intr:
status=0x51 { DriveReady
SeekCompleteError }
Mar 12 12:14:21 gandolf kernel: hda: dma_intr: error=0x84 {
DriveStatusError BadCRC }Mar 12 12:17:32 gandolf kernel: hda: dma_intr:
status=0x51 { DriveReady
SeekCompleteError }
Mar 12 12:17:32 gandolf kernel: hda: dma_intr: error=0x84 {
DriveStatusError BadCRC }Mar 12 12:17:32 gandolf kernel: hda: dma_intr:
status=0x51 { DriveReady
SeekCompleteError }
Mar 12 12:17:32 gandolf kernel: hda: dma_intr: error=0x84 {
DriveStatusError BadCRC }Mar 12 12:17:32 gandolf kernel: hda: dma_intr:
status=0x51 { DriveReady
SeekCompleteError }
Mar 12 12:17:32 gandolf kernel: hda: dma_intr: error=0x84 {
DriveStatusError BadCRC }Mar 12 12:26:18 gandolf kernel: hda: dma_intr:
status=0x51 { DriveReady
SeekCompleteError }
Mar 12 12:26:18 gandolf kernel: hda: dma_intr: error=0x84 {
DriveStatusError BadCRC }Mar 12 12:26:18 gandolf kernel: hda: dma_intr:
status=0x51 { DriveReady
SeekCompleteError }
Mar 12 12:26:18 gandolf kernel: hda: dma_intr: error=0x84 {
DriveStatusError BadCRC }Mar 12 12:26:18 gandolf kernel: hda: dma_intr:
status=0x51 { DriveReady
SeekCompleteError }
Mar 12 12:26:18 gandolf kernel: hda: dma_intr: error=0x84 {
DriveStatusError BadCRC }Mar 12 12:32:35 gandolf kernel: hda: dma_intr:
status=0x51 { DriveReady
SeekCompleteError }
Mar 12 12:32:35 gandolf kernel: hda: dma_intr: error=0x84 {
DriveStatusError BadCRC }Mar 12 12:32:35 gandolf kernel: hda: dma_intr:
status=0x51 { DriveReady
SeekCompleteError }
--
Boling's postulate:
If you're feeling good, don't worry. You'll get over it.
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: drive errors!
On Wed, 12 Mar 2003 17:29:05 -0500
Tom Allison [EMAIL PROTECTED] wrote:
I've been runnign this PC for about a year now.
I recently upgraded from 2.4.18 to 2.4.20.
And this is the thanks I get
Any suggestions? It seems to work.
Mar 12 12:14:21 gandolf kernel: hda: dma_intr: error=0x84 {
DriveStatusError BadCRC }Mar 12 12:14:21 gandolf kernel: hda: dma_intr:
status=0x51 { DriveReady
SeekCompleteError }
Do make menuconfig, and go to ATA/IDE/MFM/RLL support | IDE, ATA, and ATAPI Block
devices, and set Use multi-mode by default. See the help text for that option.
Kevin
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: drive errors!
On Wed, 2003-03-12 at 17:29, Tom Allison wrote:
I've been runnign this PC for about a year now.
I recently upgraded from 2.4.18 to 2.4.20.
And this is the thanks I get
Any suggestions? It seems to work.
Mar 12 12:14:21 gandolf kernel: hda: dma_intr: error=0x84 {
DriveStatusError BadCRC }Mar 12 12:14:21 gandolf kernel: hda: dma_intr:
status=0x51 { DriveReady
SeekCompleteError }
Mar 12 12:14:21 gandolf kernel: hda: dma_intr: error=0x84 {
DriveStatusError BadCRC }Mar 12 12:14:21 gandolf kernel: hda: dma_intr:
status=0x51 { DriveReady
SeekCompleteError }
Mar 12 12:14:21 gandolf kernel: hda: dma_intr: error=0x84 {
DriveStatusError BadCRC }Mar 12 12:17:32 gandolf kernel: hda: dma_intr:
status=0x51 { DriveReady
SeekCompleteError }
Mar 12 12:17:32 gandolf kernel: hda: dma_intr: error=0x84 {
DriveStatusError BadCRC }Mar 12 12:17:32 gandolf kernel: hda: dma_intr:
status=0x51 { DriveReady
SeekCompleteError }
Mar 12 12:17:32 gandolf kernel: hda: dma_intr: error=0x84 {
DriveStatusError BadCRC }Mar 12 12:17:32 gandolf kernel: hda: dma_intr:
status=0x51 { DriveReady
SeekCompleteError }
Mar 12 12:17:32 gandolf kernel: hda: dma_intr: error=0x84 {
DriveStatusError BadCRC }Mar 12 12:26:18 gandolf kernel: hda: dma_intr:
status=0x51 { DriveReady
SeekCompleteError }
Mar 12 12:26:18 gandolf kernel: hda: dma_intr: error=0x84 {
DriveStatusError BadCRC }Mar 12 12:26:18 gandolf kernel: hda: dma_intr:
status=0x51 { DriveReady
SeekCompleteError }
Mar 12 12:26:18 gandolf kernel: hda: dma_intr: error=0x84 {
DriveStatusError BadCRC }Mar 12 12:26:18 gandolf kernel: hda: dma_intr:
status=0x51 { DriveReady
SeekCompleteError }
Mar 12 12:26:18 gandolf kernel: hda: dma_intr: error=0x84 {
DriveStatusError BadCRC }Mar 12 12:32:35 gandolf kernel: hda: dma_intr:
status=0x51 { DriveReady
SeekCompleteError }
Mar 12 12:32:35 gandolf kernel: hda: dma_intr: error=0x84 {
DriveStatusError BadCRC }Mar 12 12:32:35 gandolf kernel: hda: dma_intr:
status=0x51 { DriveReady
SeekCompleteError }
--
Boling's postulate:
If you're feeling good, don't worry. You'll get over it.
While there is maybe a chance that you have a badly configured selection
of routines for accessing the hda's filesystems, it looks far more like
YouNeedToBackupEverythingAndGetANewPhysicalDriveInThatBoxNow.
Maybe you could have something missing about dma access or maybe even
confused irq assignments, but even if that is the case, your filesystems
could be in the midst of being shredded if there is any active writing
to those partitions.
If you go back to 2.4.18, are you getting any such messages?
--
Mark L. Kahnt, FLMI/M, ALHC, HIA, AIAA, ACS, MHP
ML Kahnt New Markets Consulting
Tel: (613) 531-8684 / (613) 539-0935
Email: [EMAIL PROTECTED]
signature.asc
Description: This is a digitally signed message part
Re: Drive errors
On Fri, Jan 17, 2003 at 10:06:01AM -0500, Matthew Daubenspeck wrote:
I have been running the same woody box for more then 2 years, and I
just got the following message:
hda: timeout waiting for DMA
hda: irq timeout: status=0x58 { DriveReady SeekComplete DataRequest }
hda: timeout waiting for DMA
hda: irq timeout: status=0xd0 { Busy }
hda: DMA disabled
ide0: reset: success
I seem to remember (the archives were no help) that someone had
suggested that this may be a bad drive? Everything seems to be working
now, but if this drive is on it's way out, I would rather replace it
now before it's completely dead...
I just had this (on a CD-RW rather than an HD). Ten minutes later the
drive lost its ability to drive the sled and loading motors. It's
completely f**ked now. So yeah, I'd be worried.
Pigeon
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: Drive errors
On Sat, 2003-01-18 at 23:42, Pigeon wrote:
On Fri, Jan 17, 2003 at 10:06:01AM -0500, Matthew Daubenspeck wrote:
I have been running the same woody box for more then 2 years, and I
just got the following message:
hda: timeout waiting for DMA
hda: irq timeout: status=0x58 { DriveReady SeekComplete DataRequest }
hda: timeout waiting for DMA
hda: irq timeout: status=0xd0 { Busy }
hda: DMA disabled
ide0: reset: success
I seem to remember (the archives were no help) that someone had
suggested that this may be a bad drive? Everything seems to be working
now, but if this drive is on it's way out, I would rather replace it
now before it's completely dead...
I just had this (on a CD-RW rather than an HD). Ten minutes later the
drive lost its ability to drive the sled and loading motors. It's
completely f**ked now. So yeah, I'd be worried.
Same experience here : an old IDE hard drive began producing these
errors under load a few days before dying completely. Your disk is
probably going to die soon. Back it up NOW if you can, and maybe
throttle the backup so that it does not stress the disk too hard - a
final crash while backing up would sure be a pity.
signature.asc
Description: This is a digitally signed message part
Drive errors
I have been running the same woody box for more then 2 years, and I
just got the following message:
hda: timeout waiting for DMA
hda: irq timeout: status=0x58 { DriveReady SeekComplete DataRequest }
hda: timeout waiting for DMA
hda: irq timeout: status=0xd0 { Busy }
hda: DMA disabled
ide0: reset: success
I seem to remember (the archives were no help) that someone had
suggested that this may be a bad drive? Everything seems to be working
now, but if this drive is on it's way out, I would rather replace it
now before it's completely dead...
Thanks for the help.
--
:wq
Matthew Daubenspeck
http://www.oddprocess.org
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: Drive errors
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On Friday 17 January 2003 16:06, Matthew Daubenspeck wrote:
I have been running the same woody box for more then 2 years, and I
just got the following message:
hda: timeout waiting for DMA
hda: irq timeout: status=0x58 { DriveReady SeekComplete DataRequest }
hda: timeout waiting for DMA
hda: irq timeout: status=0xd0 { Busy }
hda: DMA disabled
ide0: reset: success
I seem to remember (the archives were no help) that someone had
suggested that this may be a bad drive? Everything seems to be
working now, but if this drive is on it's way out, I would rather
replace it now before it's completely dead...
This could mean that the drive is developing a hardware problem while
reading data from the disk (head positioning finishes, but no data is
delivered). Depending on the type of the drive and on how hard it's
been used, it probably has reached its best-before date. If you've been
using it for two years now, that's probably the case. Most consumer
drives are not meant to last this long (they're selling 'em cheap but
in volume... figure out the rest for yourself...)
- --
Embedded Linux -- True multitasking!
TWO TOASTS AT THE SAME TIME!
-BEGIN PGP SIGNATURE-
Version: GnuPG v1.2.0 (GNU/Linux)
iD8DBQE+KDz4eOF0+zcVdv8RAneLAJ9CkWwbuDsrs+cH4xzQn6NBFXyUQwCfdKn/
f5sufDtdIjRjjvLlqVt63nM=
=dcSC
-END PGP SIGNATURE-
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: Drive errors
hi ya matthew
- what is the length of your ide cables ??
- which drive is the Master ?? which ide connector is the Master ?
- is the drive set to cable select or fixed Master
- i assume you have the new 80-conductor cables
- power the machine off... wiggle the cables... pull it off and replug it
back in
- use only the same speed disk on the ide cable
- ata66 drives only one cable
- ata100 drives only on another cable
- ata133 drives only on its cables
- if you mix and match drive speeds... its a crap-shoot
- what is the ide chipset on the motherboard or pci ide cards ?
- what kernel options is enabled for the ide chipsets ?
- when copying data off this disk.. make a copy to a dfiferent disks
other than your normal backups ... no point in copying a failing
disk to a used to be good backup until the last backups
- if you are using the IBM deskstar drives ( made in thailand)..
than yes.. go buy a new disk now and join the class action suit
c ya
alvin
On Fri, 17 Jan 2003, Matthew Daubenspeck wrote:
I have been running the same woody box for more then 2 years, and I
just got the following message:
hda: timeout waiting for DMA
hda: irq timeout: status=0x58 { DriveReady SeekComplete DataRequest }
hda: timeout waiting for DMA
hda: irq timeout: status=0xd0 { Busy }
hda: DMA disabled
ide0: reset: success
I seem to remember (the archives were no help) that someone had
suggested that this may be a bad drive? Everything seems to be working
now, but if this drive is on it's way out, I would rather replace it
now before it's completely dead...
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: Drive errors
On Fri, Jan 17, 2003 at 12:13:43PM -0800, Alvin Oga wrote: - what is the length of your ide cables ?? Standard, I would assume 24 - which drive is the Master ?? which ide connector is the Master ? - is the drive set to cable select or fixed Master This is the only drive on the controller, and it is set to Master. - i assume you have the new 80-conductor cables Yes. - power the machine off... wiggle the cables... pull it off and replug it back in And sacrifice uptime?!!? :) - use only the same speed disk on the ide cable - ata66 drives only one cable - ata100 drives only on another cable - ata133 drives only on its cables The only other ide drive is a CDROM, on another cable. - what is the ide chipset on the motherboard or pci ide cards ? It's a Via, I forget the chipset off hand... - what kernel options is enabled for the ide chipsets ? It's a stock compiled kernel from the debian install... - when copying data off this disk.. make a copy to a dfiferent disks other than your normal backups ... no point in copying a failing disk to a used to be good backup until the last backups Already started doing that :) - if you are using the IBM deskstar drives ( made in thailand).. than yes.. go buy a new disk now and join the class action suit Nope, it's a Seagate... -- :wq Matthew Daubenspeck http://www.oddprocess.org -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: Drive errors
hi ya mathew.. think you should swap your cable for an 18 cable.. and verify the chipset on your mb against the kernel ( might need to install the module for that chipset you're using ) have fun alvin - uptime will be sacrificed one way or other... - the question is do you drag data down with it or not :-) On Fri, 17 Jan 2003, Matthew Daubenspeck wrote: On Fri, Jan 17, 2003 at 12:13:43PM -0800, Alvin Oga wrote: - what is the length of your ide cables ?? Standard, I would assume 24 - which drive is the Master ?? which ide connector is the Master ? - is the drive set to cable select or fixed Master This is the only drive on the controller, and it is set to Master. - i assume you have the new 80-conductor cables Yes. - power the machine off... wiggle the cables... pull it off and replug it back in And sacrifice uptime?!!? :) - use only the same speed disk on the ide cable - ata66 drives only one cable - ata100 drives only on another cable - ata133 drives only on its cables The only other ide drive is a CDROM, on another cable. - what is the ide chipset on the motherboard or pci ide cards ? It's a Via, I forget the chipset off hand... - what kernel options is enabled for the ide chipsets ? It's a stock compiled kernel from the debian install... - when copying data off this disk.. make a copy to a dfiferent disks other than your normal backups ... no point in copying a failing disk to a used to be good backup until the last backups Already started doing that :) - if you are using the IBM deskstar drives ( made in thailand).. than yes.. go buy a new disk now and join the class action suit Nope, it's a Seagate... -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: Hard drive errors in kernel output
On Sun, May 27, 2001 at 12:36:31PM -0600, Cameron Matheson wrote:
Hey,
I enabled DMA in my kernel (w/ the VIA82 support), and now it works (my
hard drive writes are about six times faster), but now I get weird errors in
the kernel output:
Partition check:
hda:hda: dma_intr: status=0x51 { DriveReady SeekComplete Error }
hda: dma_intr: error=0x84 { DriveStatusError BadCRC }
hda: dma_intr: status=0x51 { DriveReady SeekComplete Error }
hda: dma_intr: error=0x84 { DriveStatusError BadCRC }
hda: dma_intr: status=0x51 { DriveReady SeekComplete Error }
hda: dma_intr: error=0x84 { DriveStatusError BadCRC }
hda: dma_intr: status=0x51 { DriveReady SeekComplete Error }
hda: dma_intr: error=0x84 { DriveStatusError BadCRC }
hdb: DMA disabled
ide0: reset: success
[...]
I was getting those when I was using an old tower-type case which
required the use of a long IDE cable. I switched to a smaller case and
shorter cables and that cured it.
HTH
your pal dave
--
Dave Thayer
Denver, Colorado USA
[EMAIL PROTECTED]
Hard drive errors in kernel output
Hey,
I enabled DMA in my kernel (w/ the VIA82 support), and now it works (my
hard drive writes are about six times faster), but now I get weird errors in
the kernel output:
Partition check:
hda:hda: dma_intr: status=0x51 { DriveReady SeekComplete Error }
hda: dma_intr: error=0x84 { DriveStatusError BadCRC }
hda: dma_intr: status=0x51 { DriveReady SeekComplete Error }
hda: dma_intr: error=0x84 { DriveStatusError BadCRC }
hda: dma_intr: status=0x51 { DriveReady SeekComplete Error }
hda: dma_intr: error=0x84 { DriveStatusError BadCRC }
hda: dma_intr: status=0x51 { DriveReady SeekComplete Error }
hda: dma_intr: error=0x84 { DriveStatusError BadCRC }
hdb: DMA disabled
ide0: reset: success
Everything still works, so it's probably not a problem, but it is kind of
curious. Here's my hdparm output if that matters:
/dev/hda1:
multcount= 16 (on)
I/O support = 1 (32-bit)
unmaskirq= 1 (on)
using_dma= 1 (on)
keepsettings = 0 (off)
nowerr = 0 (off)
readonly = 0 (off)
readahead= 8 (on)
geometry = 3739/255/63, sectors = 59568957, start = 63
Anyone know what these errors might mean (and what they do?)
Thanks,
Cameron Matheson
_
Do You Yahoo!?
Get your free @yahoo.com address at http://mail.yahoo.com
hard drive errors..
Hi all,
on our / partition whenever anyone tries to ssh in we get:
Sep 11 10:45:39 kaos kernel: hda: dma_intr: status=0x51 { DriveReady
SeekComplete Error }
Sep 11 10:45:39 kaos kernel: hda: dma_intr: error=0x40
{ UncorrectableError }, LBAsect=34431, sector=343
68
Sep 11 10:45:39 kaos kernel: end_request: I/O error, dev 03:01 (hda), sector
34368
the same happens for telnet through inetd.
I commented telnetd out of inetd.conf and installed tcpserver and ran:
/usr/local/bin/tcpserver 0 23 /usr/sbin/in.telnetd
and the telnet works.
anyone seen this problem before? any suggestions before i replace our
/dev/hda ?
Regards,
Marc-Adrian Napoli
Network Admin
Connect Infobahn Australia
+61 2 9281 1750
Re: hard drive errors..
Marc-Adrian Napoli wrote:
Hi all,
on our / partition whenever anyone tries to ssh in we get:
Sep 11 10:45:39 kaos kernel: hda: dma_intr: status=0x51 { DriveReady
SeekComplete Error }
Sep 11 10:45:39 kaos kernel: hda: dma_intr: error=0x40
{ UncorrectableError }, LBAsect=34431, sector=343
68
Sep 11 10:45:39 kaos kernel: end_request: I/O error, dev 03:01 (hda), sector
34368
the same happens for telnet through inetd.
I commented telnetd out of inetd.conf and installed tcpserver and ran:
/usr/local/bin/tcpserver 0 23 /usr/sbin/in.telnetd
and the telnet works.
anyone seen this problem before? any suggestions before i replace our
/dev/hda ?
There are a ton of replies to these kinds of drive errors in the
archives. It is strange it only happens when using one program. I
would guess it will start to manifest itself in other areas. Some
people have posted fixes that worked for them. Others like myself ended
up buying new drives in the end. I would at least make sure you have a
backup of the drive.
Good Luck.
kent
--
Neurosis is the way of avoiding non-being by avoiding being.
- Paul Tillich, American theologian (1886-1965).
drive errors if system comes up, need more help
Hi Wayne, me again, too. :) Try this. Unmount /dev/sdc. Do e2fsck /dev/sdc. Watch fsck as fixes the errors. I've done this, but the problem: Dec 24 04:03:53 pmurmel kernel: EXT2-fs error (device 08:0b): ext2_check_blocks_bitmap: Wrong free blocks count in super block, stored = 1188406, counted = 1188262 Dec 24 04:03:53 pmurmel kernel: EXT2-fs error (device 08:16): ext2_check_blocks_bitmap: Wrong free blocks count for group 37, stored = 7896, counted = 7888 stays alive for /dev/sda11 /var /dev/sdb6/boot /dev/sdb5/usr /dev/sdb7/opt /dev/sdb6/usr/local I really don't know what else I can do: have tried e2fsck says wrong superblock try -b 8193 /device Must I reinstall the complete system ?!? I didn't hope so. It tooks my several weeks to get the box as recordingsystem and development systems configured to my needs If You have a idea please help me THANKS Good X-mas Good 1999 -- Peter -- Peter
