It seems like your browser didn't download the required fonts. Please revise your security settings and try again.
Barracuda NextGen Firewall X

Meaning of 'DriveStatusError BadCRC' in klogd.log

  • Type: Knowledgebase
  • Date changed: one year ago
Solution 00005305 

 
Scope:
This solution replies to:
- NG Firewall firmware versions 4.2.x, 5.0.x, 5.2.x
- netfence firmware versions 4.2.x

 
Symptoms:
Sometimes, especially on phionOS startup, the following lines appear in klogd:
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 }

 
Solution:
This line do not point a hardware failure at the affected box.

Especially machines with 2.5" harddiscs negotiate at bootup time their connection speed between harddisc controller and harddisc. As harddiscs support UDMA100 or UDMA133 speed and controller supports this speed too, the negotiation detects and sets the interface up with this speed.
There is no UDMA100 / UDMA133 44pin cable available for 2.5" harddiscs which is needed for harddisc-speed over UDMA66. The speed negotiation is not able to detect the installed cable, so a greater speed is configured as the cable supports.
 This malconfiguration is detected immediately on NG Firewall OS startup, the written klogd-lines are the result of this detection. After this the UDMA-speed is set down on this interface to UDMA66.

Note:
This errors may occur also after an IDE reset. After a reset the negotiation is done again, the interface checks again that the configured speed is too high and so the lines are written in the klogd.log.
IDE-resets have to be analyzed seperately, they may point at a hardware failure.


Ignore these harmless lines on NG Firewall OS startup and after a IDE-BUS-reset.


Link to This Page:
https://campus.barracuda.com/solution/50160000000IKbaAAG