PDA

View Full Version : What ATA?


tivosohn
07-18-2003, 03:08 PM
What's the ideal ATA should I set my drives to for the HDVR2? Currently I have the WD1600JB and WD800BB. Will they work together?

David Bought
07-18-2003, 04:13 PM
Originally posted by tivosohn
What's the ideal ATA should I set my drives to for the HDVR2? Currently I have the WD1600JB and WD800BB. Will they work together?

Whatever the kernel sets them to - you should not change it unless you have DMA related problems (very rare).

Master/slave incompatibilities among modern IDE drives are also extremely rare so that combination should work, especially because they both come from the same manufacturer.

tivosohn
07-18-2003, 05:14 PM
Whatever the kernel sets them to - you should not change it unless you have DMA related problems (very rare).

DMA related problem. I am starting to see a lot of people mention that, but no in depth info. Is the following error consider DMA related problem?
Thanks...

-----------------------------------------------------------------------------------
...
ide0: reset: success
hda: dma_intr: status=0x51 { DriveReady SeekComplete Error }
hda: dma_intr: error=0x84 { DriveStatusError BadCRC }
end_request: I/O error, dev 03:09 (hda), sector 2186
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
hdb: re-enabled DMA
ide0: reset: success
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
hdb: re-enabled DMA
ide0: reset: success
hda: dma_intr: status=0x51 { DriveReady SeekComplete Error }
hda: dma_intr: error=0x84 { DriveStatusError BadCRC }
end_request: I/O error, dev 03:09 (hda), sector 2188
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
hdb: re-enabled DMA
ide0: reset: success
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 SeekComplL
...

Then it reboots itself and stuck on the Powering up screen and the following thing shows on the bash prompt :

Partition 6 signature is false, trying alternate
diskboot found partition 2 signature is false.
Ram size = 64
Service number is xxxxxxxxxxxxxxx.
What is password?

Then I pop the drives backing my PC and did a bootpage -p /dev/hda. It returns a wired string of something like this.

rnot=.ddv.hda6 BARH_........
-----------------------------------------------------------------------------------

David Bought
07-18-2003, 05:43 PM
Sounds like some serious drive corruption. Could be a hardware problem (bad cable, bad mobo) or it could be software (such as an incorrectly executed upgrade or something).