what does DriveReady SeekComplete Error mean ?
From: charly (charlyspam_at_yahoo.fr)
Date: 01/28/04
- Next message: Darryl Schultz: "Re: SATA with P4P800 - My Experience"
- Previous message: Fedora User: "Re: Abit NF7 with Linux"
- Next in thread: Kamus of Kadizhar: "Re: what does DriveReady SeekComplete Error mean ?"
- Reply: Kamus of Kadizhar: "Re: what does DriveReady SeekComplete Error mean ?"
- Reply: Michael Buchenrieder: "Re: what does DriveReady SeekComplete Error mean ?"
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
Date: Wed, 28 Jan 2004 12:27:06 +0100
Greetings, I'm setting up a server and have some hard time with the
drives. I downloaded the boot drive CD but would like to understand what
does the followng mean.
(Otherwise the disks work rougly fine..)
thx !
I post here a sniplet of my dmesg and informations about the drives...:
hdb: task_no_data_intr: status=0x51 { DriveReady SeekComplete Error }
hdb: task_no_data_intr: error=0x04 { DriveStatusError }
hdb: 3171270 sectors (1624 MB), CHS=3737/255/63, DMA
hdc: host protected area => 1
hdc: 60036480 sectors (30739 MB) w/380KiB Cache, CHS=59560/16/63, UDMA(100)
hdd: task_no_data_intr: status=0x51 { DriveReady SeekComplete Error }
hdd: task_no_data_intr: error=0x04 { DriveStatusError }
hdd: 6303024 sectors (3227 MB) w/128KiB Cache, CHS=6253/16/63, UDMA(33)
.
.
.
hdc: dma_intr: status=0x51 { DriveReady SeekComplete Error }
hdc: dma_intr: error=0x84 { DriveStatusError BadCRC }
hdc: dma_intr: status=0x51 { DriveReady SeekComplete Error }
hdc: dma_intr: error=0x84 { DriveStatusError BadCRC }
hdc: dma_intr: status=0x51 { DriveReady SeekComplete Error }
hdc: dma_intr: error=0x84 { DriveStatusError BadCRC }
hdc: dma_intr: status=0x51 { DriveReady SeekComplete Error }
hdc: dma_intr: error=0x84 { DriveStatusError BadCRC }
blk: queue c03bed60, I/O limit 4095Mb (mask 0xffffffff)
hdd: DMA disabled
ide1: reset: success
hdc: dma_intr: status=0x51 { DriveReady SeekComplete Error }
hdc: dma_intr: error=0x84 { DriveStatusError BadCRC }
hdc: dma_intr: status=0x51 { DriveReady SeekComplete Error }
hdc: dma_intr: error=0x84 { DriveStatusError BadCRC }
hdc: dma_intr: status=0x51 { DriveReady SeekComplete Error }
hdc: dma_intr: error=0x84 { DriveStatusError BadCRC }
hdc: dma_intr: status=0x51 { DriveReady SeekComplete Error }
hdc: dma_intr: error=0x84 { DriveStatusError BadCRC }
/dev/hdd:
ATA device, with non-removable media
Model Number: ST33232A
Serial Number: VGC84643
Firmware Revision: 3.02
Standards:
Supported: 2 1
Likely used: 4
Configuration:
Logical max current
cylinders 6253 6253
heads 16 16
sectors/track 63 63
--
CHS current addressable sectors: 6303024
LBA user addressable sectors: 6303024
device size with M = 1024*1024: 3077 MBytes
device size with M = 1000*1000: 3227 MBytes (3 GB)
Capabilities:
LBA, IORDY(can be disabled)
Buffer size: 128.0kB bytes avail on r/w long: 4 Queue depth: 1
Standby timer values: spec'd by Vendor
R/W multiple sector transfer: Max = 16 Current = 16
DMA: mdma0 mdma1 mdma2 udma0 udma1 *udma2
Cycle time: min=120ns recommended=120ns
PIO: pio0 pio1 pio2 pio3 pio4
Cycle time: no flow control=383ns IORDY flow control=120ns
Commands/features:
Enabled Supported:
Power Management feature set
SMART feature set
/dev/hdc:
ATA device, with non-removable media
powers-up in standby; SET FEATURES subcmd spins-up.
Model Number: IBM-DTLA-305030
Serial Number: YG0YGL13459
Firmware Revision: TW3OA60A
Standards:
Used: ATA/ATAPI-5 T13 1321D revision 1
Supported: 5 4 3 2 & some of 6
Configuration:
Logical max current
cylinders 16383 16383
heads 16 16
sectors/track 63 63
--
CHS current addressable sectors: 16514064
LBA user addressable sectors: 60036480
device size with M = 1024*1024: 29314 MBytes
device size with M = 1000*1000: 30738 MBytes (30 GB)
Capabilities:
LBA, IORDY(can be disabled)
bytes avail on r/w long: 40 Queue depth: 32
Standby timer values: spec'd by Standard, no device specific minimum
R/W multiple sector transfer: Max = 16 Current = 16
Advanced power management level: unknown setting (0x0000)
Recommended acoustic management value: 128, current value: 254
DMA: mdma0 mdma1 mdma2 udma0 udma1 udma2 *udma3 udma4 udma5
Cycle time: min=120ns recommended=120ns
PIO: pio0 pio1 pio2 pio3 pio4
Cycle time: no flow control=240ns IORDY flow control=120ns
Commands/features:
Enabled Supported:
* NOP cmd
* READ BUFFER cmd
* WRITE BUFFER cmd
* Host Protected Area feature set
Release interrupt
* Look-ahead
* Write cache
* Power Management feature set
Security Mode feature set
* SMART feature set
Automatic Acoustic Management feature set
SET MAX security extension
Address Offset Reserved Area Boot
SET FEATURES subcommand required to spinup after power up
Power-Up In Standby feature set
Advanced Power Management feature set
* READ/WRITE DMA QUEUED
Security:
Master password revision code = 65534
supported
not enabled
not locked
not frozen
not expired: security count
not supported: enhanced erase
32min for SECURITY ERASE UNIT.
HW reset results:
CBLID- below Vih
Device num = 0 determined by the jumper
Checksum: correct
- Next message: Darryl Schultz: "Re: SATA with P4P800 - My Experience"
- Previous message: Fedora User: "Re: Abit NF7 with Linux"
- Next in thread: Kamus of Kadizhar: "Re: what does DriveReady SeekComplete Error mean ?"
- Reply: Kamus of Kadizhar: "Re: what does DriveReady SeekComplete Error mean ?"
- Reply: Michael Buchenrieder: "Re: what does DriveReady SeekComplete Error mean ?"
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
Relevant Pages
|
