NASLite Network Attached Storage

www.serverelements.com
Task-specific simplicity with low hardware requirements.
It is currently Mon Jul 04, 2022 4:37 pm

All times are UTC - 5 hours [ DST ]




Post new topic Reply to topic  [ 6 posts ] 
Author Message
 Post subject: HDD or controller?
PostPosted: Fri Apr 27, 2007 7:56 am 
Offline

Joined: Fri Mar 23, 2007 10:24 am
Posts: 11
Does this look like a drive or a controller problem? I'm inclined to think the controller might be getting flaky.

Code:
# Apr 27 06:00:21 user.warn kernel: hda: dma_timer_expiry: dma status == 0x61
# Apr 27 06:00:31 user.err kernel: hda: error waiting for DMA
# Apr 27 06:00:31 user.warn kernel: hda: dma timeout retry: status=0x58 { DriveReady SeekComplete DataRequest }
# Apr 27 06:00:31 user.warn kernel:
# Apr 27 06:00:31 user.warn kernel: hda: read_intr: status=0x51 { DriveReady SeekComplete Error }
# Apr 27 06:00:31 user.warn kernel: hda: read_intr: error=0x04 { DriveStatusError }
# Apr 27 06:00:31 user.warn kernel: hda: read_intr: status=0x51 { DriveReady SeekComplete Error }
# Apr 27 06:00:31 user.warn kernel: hda: read_intr: error=0x04 { DriveStatusError }
# Apr 27 06:00:31 user.warn kernel: hda: read_intr: status=0x51 { DriveReady SeekComplete Error }
# Apr 27 06:00:31 user.warn kernel: hda: read_intr: error=0x04 { DriveStatusError }
# Apr 27 06:00:31 user.warn kernel: hda: read_intr: status=0x51 { DriveReady SeekComplete Error }
# Apr 27 06:00:31 user.warn kernel: hda: read_intr: error=0x04 { DriveStatusError }
# Apr 27 06:00:31 user.info kernel: hdb: DMA disabled
# Apr 27 06:00:32 user.warn kernel: ide0: reset: success
# Apr 27 06:00:52 user.warn kernel: hda: dma_timer_expiry: dma status == 0x21
# Apr 27 06:01:02 user.err kernel: hda: error waiting for DMA
# Apr 27 06:01:02 user.warn kernel: hda: dma timeout retry: status=0x58 { DriveReady SeekComplete DataRequest }
# Apr 27 06:01:02 user.warn kernel:
# Apr 27 06:01:22 user.warn kernel: hda: dma_timer_expiry: dma status == 0x21
# Apr 27 06:01:32 user.err kernel: hda: error waiting for DMA
# Apr 27 06:01:32 user.warn kernel: hda: dma timeout retry: status=0x58 { DriveReady SeekComplete DataRequest }
# Apr 27 06:01:32 user.warn kernel:
# Apr 27 06:01:52 user.warn kernel: hda: dma_timer_expiry: dma status == 0x21
# Apr 27 06:02:02 user.err kernel: hda: error waiting for DMA
# Apr 27 06:02:02 user.warn kernel: hda: dma timeout retry: status=0x58 { DriveReady SeekComplete DataRequest }
# Apr 27 06:02:02 user.warn kernel:


Top
 Profile  
 
 Post subject:
PostPosted: Fri Apr 27, 2007 9:07 am 
Offline

Joined: Fri Jun 16, 2006 5:09 am
Posts: 130
What happens if you disable SMART for that drive?

I had a similar error and after checking all options it went away after disabling smart.


Top
 Profile  
 
 Post subject: So far so good
PostPosted: Fri Apr 27, 2007 5:44 pm 
Offline

Joined: Fri Mar 23, 2007 10:24 am
Posts: 11
I went ahead and disabled SMART and in the 8.25 hours that it's been up, no warnings or errors have been spat out to the syslog. So, that hopefully is what the problem was, thanks :D


Top
 Profile  
 
 Post subject: Damn it!
PostPosted: Sat Apr 28, 2007 9:05 am 
Offline

Joined: Fri Mar 23, 2007 10:24 am
Posts: 11
Things going "beep" in the night...I hadn't disabled SMART in the BIOS; so I went ahead and did that this morning and this is what showed up in the syslog after I rebooted :x

Code:
# Apr 28 12:51:56 user.warn kernel: hda: drive_cmd: status=0x51 { DriveReady SeekComplete Error }
# Apr 28 12:51:56 user.warn kernel: hda: drive_cmd: error=0x04 { DriveStatusError }
# Apr 28 12:51:56 user.warn kernel: hda: drive_cmd: status=0x51 { DriveReady SeekComplete Error }
# Apr 28 12:51:56 user.warn kernel: hda: drive_cmd: error=0x04 { DriveStatusError }
# Apr 28 12:51:56 user.warn kernel: hdb: drive_cmd: status=0x51 { DriveReady SeekComplete Error }
# Apr 28 12:51:56 user.warn kernel: hdb: drive_cmd: error=0x04 { DriveStatusError }
# Apr 28 12:51:56 user.warn kernel: hdb: drive_cmd: status=0x51 { DriveReady SeekComplete Error }
# Apr 28 12:51:56 user.warn kernel: hdb: drive_cmd: error=0x04 { DriveStatusError }
# Apr 28 12:51:56 user.info kernel: eth0: Setting full-duplex based on MII #1 link partner capability of 45e1.
# Apr 28 12:51:56 user.warn kernel: hda: drive_cmd: status=0x51 { DriveReady SeekComplete Error }
# Apr 28 12:51:56 user.warn kernel: hda: drive_cmd: error=0x04 { DriveStatusError }
# Apr 28 12:51:56 user.warn kernel: hdb: drive_cmd: status=0x51 { DriveReady SeekComplete Error }
# Apr 28 12:51:56 user.warn kernel: hdb: drive_cmd: error=0x04 { DriveStatusError }


I'll double-check the jumper settings on the drives as hda and hdb are both on the same IDE channel -- maybe scrounge up another cable and get them on separate channels, but this isn't looking too good.


Top
 Profile  
 
 Post subject: Not the HDD
PostPosted: Sun Apr 29, 2007 1:24 am 
Offline

Joined: Fri Mar 23, 2007 10:24 am
Posts: 11
I down-loaded Western Digital's Data Life Guard diagnostics and stuffed the drive into another machine. The diags came back OK; so unless anyone out there has some other advice, I'm going on my original hunch that it's the controller.

Just for grins, I'm going to swap the cable and if it still gives me grief, I'll plug things into the other IDE channel and see what happens. NewEgg will RMA this lemon for up to a year; so I guess I'll be dropping them a line.


Top
 Profile  
 
 Post subject: A possible explanation?
PostPosted: Mon Jul 02, 2007 9:41 pm 
Offline

Joined: Fri Mar 23, 2007 10:24 am
Posts: 11
http://www.captain.at/howto-linux-drive ... serror.php

I'm running v2.05 05-2007.

Code:
# Jul 3 01:15:19 user.info kernel: Uniform Multi-Platform E-IDE driver Revision: 7.00beta4-2.4
# Jul 3 01:15:19 user.info kernel: ide: Assuming 33MHz system bus speed for PIO modes; override with idebus=xx
# Jul 3 01:15:19 user.info kernel: VP_IDE: IDE controller at PCI slot 00:0f.0
# Jul 3 01:15:19 user.info kernel: VP_IDE: chipset revision 6
# Jul 3 01:15:19 user.info kernel: VP_IDE: not 100% native mode: will probe irqs later
# Jul 3 01:15:19 user.info kernel: ide: Assuming 33MHz system bus speed for PIO modes; override with idebus=xx
# Jul 3 01:15:19 user.info kernel: VP_IDE: VIA vt8237 (rev 00) IDE UDMA133 controller on pci00:0f.0
# Jul 3 01:15:19 user.info kernel: ide0: BM-DMA at 0xd400-0xd407, BIOS settings: hda:DMA, hdb:DMA
# Jul 3 01:15:19 user.info kernel: ide1: BM-DMA at 0xd408-0xd40f, BIOS settings: hdc:pio, hdd:pio
# Jul 3 01:15:19 user.warn kernel: hda: WDC WD3200JB-00KFA0, ATA DISK drive
# Jul 3 01:15:19 user.warn kernel: hdb: WDC WD3200JB-00KFA0, ATA DISK drive
# Jul 3 01:15:19 user.warn kernel: ide0 at 0x1f0-0x1f7,0x3f6 on irq 14
# Jul 3 01:15:19 user.warn kernel: hda: attached ide-disk driver.
# Jul 3 01:15:19 user.warn kernel: hda: host protected area => 1
# Jul 3 01:15:19 user.info kernel: hda: 625142448 sectors (320073 MB) w/8192KiB Cache, CHS=38913/255/63, UDMA(100)
# Jul 3 01:15:19 user.warn kernel: hdb: attached ide-disk driver.
# Jul 3 01:15:19 user.warn kernel: hdb: host protected area => 1
# Jul 3 01:15:19 user.info kernel: hdb: 625142448 sectors (320073 MB) w/8192KiB Cache, CHS=38913/255/63, UDMA(100)
# Jul 3 01:15:19 user.info kernel: Partition check:
# Jul 3 01:15:19 user.info kernel: /dev/ide/host0/bus0/target0/lun0: p1
# Jul 3 01:15:19 user.info kernel: /dev/ide/host0/bus0/target1/lun0: p1
# Jul 3 01:15:19 user.info kernel: SCSI subsystem driver Revision: 1.00


About the only time I see DriveReady SeekComplete Error/DriveStatusError is on reboot -- and perhaps about once a month in the syslog, if that. If the above link is to be believed, it's not much to worry about, but suggests something is up with the driver or HDD firmware.


Top
 Profile  
 
Display posts from previous:  Sort by  
Post new topic Reply to topic  [ 6 posts ] 

All times are UTC - 5 hours [ DST ]


Who is online

Users browsing this forum: No registered users and 2 guests


You cannot post new topics in this forum
You cannot reply to topics in this forum
You cannot edit your posts in this forum
You cannot delete your posts in this forum
You cannot post attachments in this forum

Search for:
Jump to:  
cron
Powered by phpBB® Forum Software © phpBB Group