Koozali.org: home of the SME Server

Legacy Forums => Experienced User Forum => Topic started by: michael on October 09, 2003, 02:06:59 PM

Title: upgrade 6.0b3 { DriveStatusError BadCRC }
Post by: michael on October 09, 2003, 02:06:59 PM

hi all,
i upgraded my SME5.6 to 6.0beta3, evreything seemed to go well but on boot up i get the following error(s):

Journalled Block Device driver loaded
EXT3-fs: INFO: recovery required on readonly filesystem.
EXT3-fs: write access will be enabled during recovery.
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 }
blk: queue c0371d00, I/O limit 4095Mb (mask 0xffffffff)
hdb: DMA disabled
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 }
ide0: reset: success

the box still boots up and appears to work ok. can any one throw some light on this problem.

thx
michael

Title: Re: upgrade 6.0b3 { DriveStatusError BadCRC }
Post by: Reinhold on October 10, 2003, 01:45:46 AM

did you have the drive dma enabled in 5.6 ?

AFAIK 6.03 does have dma access enabled by default so now you might see a buried problem with your setup, especially cables etc.

Definitely check your hd-cable if you opened the box.

Regards
Reinhold

Title: Re: upgrade 6.0b3 { DriveStatusError BadCRC }
Post by: michael on October 10, 2003, 05:44:52 PM

big thankx to reinhold -> i have changed my hd-cable and now it works fine.

regards
michael