Koozali.org formerly Contribs.org

New 6.01-1 Install. Mirrored Drives - CRC Errors

pistonpilot

New 6.01-1 Install. Mirrored Drives - CRC Errors
« on: January 30, 2005, 05:30:13 AM »
I installed 6.01-1 on a 1200mhz AMD no name brand computer with two 20gig drives on an IDE bus.  Installation went fine, and it was quick.  

When I brought the system up and started configuring using the server-manager, I noticed CRC errors on the console screen.

Then I looked at the log which I have attached the last 10 minutes of the messages file.  

Can anyone tell me what you think is the problem?  Bad harddrive or could it be a controller issue between the two drives?  This computer was running Windows XP and was slow but not complaining.  

I'll have a more definitive answer as I'm running Spinrite 6.0 on it at its deepest level.  It will run for 16 hours.  If spinrite doesn't find massive HD errors, then I'll have to blame the controller.  

So what do you think, controller or platter?




Jan 29 20:06:29 server e-smith[4262]: Processing event: ibay-modify practice
Jan 29 20:06:29 server e-smith[4262]: Running event handler: /etc/e-smith/events/ibay-modify/S15ibay-modify
Jan 29 20:06:30 server e-smith[4262]: S15ibay-modify=action|Event|ibay-modify|Action|S15ibay-modify|Start|1107047189 884037|End|1107047190 93095|Elapsed|0.209058
Jan 29 20:06:30 server e-smith[4262]: Running event handler: /etc/e-smith/events/ibay-modify/S47proftpd-conf
Jan 29 20:06:30 server e-smith[4262]: S47proftpd-conf=action|Event|ibay-modify|Action|S47proftpd-conf|Start|1107047190 93380|End|1107047190 455810|Elapsed|0.36243
Jan 29 20:06:30 server e-smith[4262]: Running event handler: /etc/e-smith/events/ibay-modify/S50conf-security
Jan 29 20:06:30 server e-smith[4262]: S50conf-security=action|Event|ibay-modify|Action|S50conf-security|Start|1107047190 455994|End|1107047190 893830|Elapsed|0.437836
Jan 29 20:06:30 server e-smith[4262]: Running event handler: /etc/e-smith/events/ibay-modify/S55atalk-conf
Jan 29 20:06:31 server e-smith[4262]: S55atalk-conf=action|Event|ibay-modify|Action|S55atalk-conf|Start|1107047190 894023|End|1107047191 231368|Elapsed|0.337345
Jan 29 20:06:31 server e-smith[4262]: Running event handler: /etc/e-smith/events/ibay-modify/S55conf-httpd
Jan 29 20:06:31 server e-smith[4262]: S55conf-httpd=action|Event|ibay-modify|Action|S55conf-httpd|Start|1107047191 231541|End|1107047191 888548|Elapsed|0.657007
Jan 29 20:06:31 server e-smith[4262]: Running event handler: /etc/e-smith/events/ibay-modify/S55conf-samba
Jan 29 20:06:32 server e-smith[4262]: S55conf-samba=action|Event|ibay-modify|Action|S55conf-samba|Start|1107047191 888722|End|1107047192 326350|Elapsed|0.437628
Jan 29 20:06:32 server e-smith[4262]: Running event handler: /etc/e-smith/events/ibay-modify/S90atalk-reload
Jan 29 20:06:32 server afpd[2637]: disallowing logins
Jan 29 20:06:32 server afpd[2637]: re-reading configuration file
Jan 29 20:06:32 server e-smith[4262]: S90atalk-reload=action|Event|ibay-modify|Action|S90atalk-reload|Start|1107047192 326526|End|1107047192 528287|Elapsed|0.201761
Jan 29 20:06:32 server e-smith[4262]: Running event handler: /etc/e-smith/events/ibay-modify/S90reload-samba
Jan 29 20:06:32 server e-smith[4262]: S90reload-samba=action|Event|ibay-modify|Action|S90reload-samba|Start|1107047192 528470|End|1107047192 784164|Elapsed|0.255694
Jan 29 20:06:32 server e-smith[4262]: Running event handler: /etc/e-smith/events/ibay-modify/S90restart-httpd-graceful
Jan 29 20:03:33 server last message repeated 2 times
Jan 29 20:06:33 server httpd-e-smith: httpd -USR1 succeeded
Jan 29 20:06:34 server kernel: hdb: dma_intr: status=0x51 { DriveReady SeekComplete Error }
Jan 29 20:06:34 server kernel: hdb: dma_intr: error=0x84 { DriveStatusError BadCRC }
Jan 29 20:06:35 server kernel: hdb: dma_intr: status=0x51 { DriveReady SeekComplete Error }
Jan 29 20:06:35 server kernel: hdb: dma_intr: error=0x84 { DriveStatusError BadCRC }
Jan 29 20:06:38 server e-smith[4262]: Gracefully reloading httpd: [   OK   ]^M
Jan 29 20:06:38 server e-smith[4262]: S90restart-httpd-graceful=action|Event|ibay-modify|Action|S90restart-httpd-graceful|Start|1107047192 784357|End|1107047198 283652|Elapsed|5.499295
Jan 29 20:06:38 server afpd[2637]: server:AFPServer@* started on 65280.232:128 (1.5.5)
Jan 29 20:06:38 server afpd[2637]: ASIP started on 192.168.1.1:548(3) (1.5.5)
Jan 29 20:06:38 server afpd[2637]: uam: loading (/usr/lib/uams_dhx.so)
Jan 29 20:06:38 server afpd[2637]: uam: uams_dhx.so loaded
Jan 29 20:06:38 server afpd[2637]: uam: loading (/usr/lib/uams_pgp.so)
Jan 29 20:06:38 server afpd[2637]: uam: uams_pgp.so loaded
Jan 29 20:06:38 server afpd[2637]: uam: "PGPuam 1.0" available
Jan 29 20:06:38 server afpd[2637]: uam: "DHCAST128" available
Jan 29 20:06:39 server kernel: hdb: dma_intr: status=0x51 { DriveReady SeekComplete Error }
Jan 29 20:06:39 server kernel: hdb: dma_intr: error=0x84 { DriveStatusError BadCRC }
Jan 29 20:06:40 server kernel: hdb: dma_intr: status=0x51 { DriveReady SeekComplete Error }
Jan 29 20:06:40 server kernel: hdb: dma_intr: error=0x84 { DriveStatusError BadCRC }
Jan 29 20:06:42 server kernel: hdb: dma_intr: status=0x51 { DriveReady SeekComplete Error }
Jan 29 20:06:42 server kernel: hdb: dma_intr: error=0x84 { DriveStatusError BadCRC }
Jan 29 20:06:46 server kernel: hdb: dma_intr: status=0x51 { DriveReady SeekComplete Error }
Jan 29 20:06:46 server kernel: hdb: dma_intr: error=0x84 { DriveStatusError BadCRC }
Jan 29 20:06:48 server kernel: hdb: dma_intr: status=0x51 { DriveReady SeekComplete Error }
Jan 29 20:06:48 server kernel: hdb: dma_intr: error=0x84 { DriveStatusError BadCRC }
Jan 29 20:06:50 server kernel: hdb: dma_intr: status=0x51 { DriveReady SeekComplete Error }
Jan 29 20:06:50 server kernel: hdb: dma_intr: error=0x84 { DriveStatusError BadCRC }
Jan 29 20:07:01 server kernel: hdb: dma_intr: status=0x51 { DriveReady SeekComplete Error }
Jan 29 20:07:01 server kernel: hdb: dma_intr: error=0x84 { DriveStatusError BadCRC }
Jan 29 20:07:08 server kernel: hdb: dma_intr: status=0x51 { DriveReady SeekComplete Error }
Jan 29 20:07:08 server kernel: hdb: dma_intr: error=0x84 { DriveStatusError BadCRC }
Jan 29 20:07:10 server kernel: hdb: dma_intr: status=0x51 { DriveReady SeekComplete Error }
Jan 29 20:07:10 server kernel: hdb: dma_intr: error=0x84 { DriveStatusError BadCRC }
Jan 29 20:07:15 server kernel: hdb: dma_intr: status=0x51 { DriveReady SeekComplete Error }
Jan 29 20:07:15 server kernel: hdb: dma_intr: error=0x84 { DriveStatusError BadCRC }
Jan 29 20:07:19 server kernel: hdb: dma_intr: status=0x51 { DriveReady SeekComplete Error }
Jan 29 20:07:19 server kernel: hdb: dma_intr: error=0x84 { DriveStatusError BadCRC }
Jan 29 20:07:22 server kernel: hdb: dma_intr: status=0x51 { DriveReady SeekComplete Error }
Jan 29 20:07:22 server kernel: hdb: dma_intr: error=0x84 { DriveStatusError BadCRC }
Jan 29 20:07:23 server kernel: hdb: dma_intr: status=0x51 { DriveReady SeekComplete Error }
Jan 29 20:07:23 server kernel: hdb: dma_intr: error=0x84 { DriveStatusError BadCRC }
Jan 29 20:07:32 server kernel: hdb: dma_intr: status=0x51 { DriveReady SeekComplete Error }
Jan 29 20:07:32 server kernel: hdb: dma_intr: error=0x84 { DriveStatusError BadCRC }
Jan 29 20:07:33 server kernel: hdb: dma_intr: status=0x51 { DriveReady SeekComplete Error }
Jan 29 20:07:33 server kernel: hdb: dma_intr: error=0x84 { DriveStatusError BadCRC }
Jan 29 20:07:35 server kernel: hdb: dma_intr: status=0x51 { DriveReady SeekComplete Error }
Jan 29 20:07:35 server kernel: hdb: dma_intr: error=0x84 { DriveStatusError BadCRC }
Jan 29 20:07:36 server kernel: hdb: dma_intr: status=0x51 { DriveReady SeekComplete Error }
Jan 29 20:07:36 server kernel: hdb: dma_intr: error=0x84 { DriveStatusError BadCRC }
Jan 29 20:07:46 server kernel: hdb: dma_intr: status=0x51 { DriveReady SeekComplete Error }
Jan 29 20:07:46 server kernel: hdb: dma_intr: error=0x84 { DriveStatusError BadCRC }
Jan 29 20:07:50 server kernel: hdb: dma_intr: status=0x51 { DriveReady SeekComplete Error }
Jan 29 20:07:50 server kernel: hdb: dma_intr: error=0x84 { DriveStatusError BadCRC }
Jan 29 20:07:51 server kernel: hdb: dma_intr: status=0x51 { DriveReady SeekComplete Error }
Jan 29 20:07:51 server kernel: hdb: dma_intr: error=0x84 { DriveStatusError BadCRC }
Jan 29 20:07:53 server kernel: hdb: dma_intr: status=0x51 { DriveReady SeekComplete Error }
Jan 29 20:07:53 server kernel: hdb: dma_intr: error=0x84 { DriveStatusError BadCRC }
Jan 29 20:07:54 server kernel: hdb: dma_intr: status=0x51 { DriveReady SeekComplete Error }
Jan 29 20:07:54 server kernel: hdb: dma_intr: error=0x84 { DriveStatusError BadCRC }
Jan 29 20:07:55 server kernel: hdb: dma_intr: status=0x51 { DriveReady SeekComplete Error }
Jan 29 20:07:55 server kernel: hdb: dma_intr: error=0x84 { DriveStatusError BadCRC }
Jan 29 20:07:56 server kernel: hdb: dma_intr: status=0x51 { DriveReady SeekComplete Error }
Jan 29 20:07:56 server kernel: hdb: dma_intr: error=0x84 { DriveStatusError BadCRC }
Jan 29 20:07:57 server kernel: hdb: dma_intr: status=0x51 { DriveReady SeekComplete Error }
Jan 29 20:07:57 server kernel: hdb: dma_intr: error=0x84 { DriveStatusError BadCRC }
Jan 29 20:07:59 server kernel: hdb: dma_intr: status=0x51 { DriveReady SeekComplete Error }
Jan 29 20:07:59 server kernel: hdb: dma_intr: error=0x84 { DriveStatusError BadCRC }
Jan 29 20:08:00 server kernel: hdb: dma_intr: status=0x51 { DriveReady SeekComplete Error }
Jan 29 20:08:00 server kernel: hdb: dma_intr: error=0x84 { DriveStatusError BadCRC }
Jan 29 20:08:04 server kernel: hdb: dma_intr: status=0x51 { DriveReady SeekComplete Error }
Jan 29 20:08:04 server kernel: hdb: dma_intr: error=0x84 { DriveStatusError BadCRC }
Jan 29 20:08:05 server kernel: hdb: dma_intr: status=0x51 { DriveReady SeekComplete Error }
Jan 29 20:08:05 server kernel: hdb: dma_intr: error=0x84 { DriveStatusError BadCRC }
Jan 29 20:08:06 server kernel: hdb: dma_intr: status=0x51 { DriveReady SeekComplete Error }
Jan 29 20:08:06 server kernel: hdb: dma_intr: error=0x84 { DriveStatusError BadCRC }
Jan 29 20:08:08 server kernel: hdb: dma_intr: status=0x51 { DriveReady SeekComplete Error }
Jan 29 20:08:08 server kernel: hdb: dma_intr: error=0x84 { DriveStatusError BadCRC }
Jan 29 20:08:09 server kernel: hdb: dma_intr: status=0x51 { DriveReady SeekComplete Error }
Jan 29 20:08:09 server kernel: hdb: dma_intr: error=0x84 { DriveStatusError BadCRC }
Jan 29 20:08:13 server kernel: hdb: dma_intr: status=0x51 { DriveReady SeekComplete Error }
Jan 29 20:08:13 server kernel: hdb: dma_intr: error=0x84 { DriveStatusError BadCRC }
Jan 29 20:08:14 server kernel: hdb: dma_intr: status=0x51 { DriveReady SeekComplete Error }
Jan 29 20:08:14 server kernel: hdb: dma_intr: error=0x84 { DriveStatusError BadCRC }
Jan 29 20:08:15 server kernel: hdb: dma_intr: status=0x51 { DriveReady SeekComplete Error }
Jan 29 20:08:15 server kernel: hdb: dma_intr: error=0x84 { DriveStatusError BadCRC }
Jan 29 20:08:17 server kernel: hdb: dma_intr: status=0x51 { DriveReady SeekComplete Error }
Jan 29 20:08:17 server kernel: hdb: dma_intr: error=0x84 { DriveStatusError BadCRC }
Jan 29 20:08:17 server kernel: hdb: dma_intr: status=0x51 { DriveReady SeekComplete Error }
Jan 29 20:08:17 server kernel: hdb: dma_intr: error=0x84 { DriveStatusError BadCRC }
Jan 29 20:08:21 server kernel: hdb: dma_intr: status=0x51 { DriveReady SeekComplete Error }
Jan 29 20:08:21 server kernel: hdb: dma_intr: error=0x84 { DriveStatusError BadCRC }
Jan 29 20:08:23 server kernel: hdb: dma_intr: status=0x51 { DriveReady SeekComplete Error }
Jan 29 20:08:23 server kernel: hdb: dma_intr: error=0x84 { DriveStatusError BadCRC }
Jan 29 20:08:26 server kernel: hdb: dma_intr: status=0x51 { DriveReady SeekComplete Error }
Jan 29 20:08:26 server kernel: hdb: dma_intr: error=0x84 { DriveStatusError BadCRC }
Jan 29 20:08:27 server kernel: hdb: dma_intr: status=0x51 { DriveReady SeekComplete Error }
Jan 29 20:08:27 server kernel: hdb: dma_intr: error=0x84 { DriveStatusError BadCRC }
Jan 29 20:08:29 server kernel: hdb: dma_intr: status=0x51 { DriveReady SeekComplete Error }
Jan 29 20:08:29 server kernel: hdb: dma_intr: error=0x84 { DriveStatusError BadCRC }
Jan 29 20:08:29 server kernel: hdb: dma_intr: status=0x51 { DriveReady SeekComplete Error }
Jan 29 20:08:29 server kernel: hdb: dma_intr: error=0x84 { DriveStatusError BadCRC }
Jan 29 20:08:30 server kernel: hdb: dma_intr: status=0x51 { DriveReady SeekComplete Error }
Jan 29 20:08:30 server kernel: hdb: dma_intr: error=0x84 { DriveStatusError BadCRC }
Jan 29 20:08:36 server kernel: hdb: dma_intr: status=0x51 { DriveReady SeekComplete Error }
Jan 29 20:08:36 server kernel: hdb: dma_intr: error=0x84 { DriveStatusError BadCRC }
Jan 29 20:08:37 server kernel: hdb: dma_intr: status=0x51 { DriveReady SeekComplete Error }
Jan 29 20:08:37 server kernel: hdb: dma_intr: error=0x84 { DriveStatusError BadCRC }
Jan 29 20:08:37 server kernel: hdb: dma_intr: status=0x51 { DriveReady SeekComplete Error }
Jan 29 20:08:37 server kernel: hdb: dma_intr: error=0x84 { DriveStatusError BadCRC }
Jan 29 20:08:40 server kernel: hdb: dma_intr: status=0x51 { DriveReady SeekComplete Error }
Jan 29 20:08:40 server kernel: hdb: dma_intr: error=0x84 { DriveStatusError BadCRC }
Jan 29 20:08:41 server kernel: hdb: dma_intr: status=0x51 { DriveReady SeekComplete Error }
Jan 29 20:08:41 server kernel: hdb: dma_intr: error=0x84 { DriveStatusError BadCRC }
Jan 29 20:08:41 server kernel: hdb: dma_intr: status=0x51 { DriveReady SeekComplete Error }
Jan 29 20:08:41 server kernel: hdb: dma_intr: error=0x84 { DriveStatusError BadCRC }
Jan 29 20:08:43 server kernel: hdb: dma_intr: status=0x51 { DriveReady SeekComplete Error }
Jan 29 20:08:43 server kernel: hdb: dma_intr: error=0x84 { DriveStatusError BadCRC }
Jan 29 20:08:43 server kernel: hdb: dma_intr: status=0x51 { DriveReady SeekComplete Error }
Jan 29 20:08:43 server kernel: hdb: dma_intr: error=0x84 { DriveStatusError BadCRC }
Jan 29 20:08:48 server kernel: hdb: dma_intr: status=0x51 { DriveReady SeekComplete Error }
Jan 29 20:08:48 server kernel: hdb: dma_intr: error=0x84 { DriveStatusError BadCRC }
Jan 29 20:08:49 server kernel: hdb: dma_intr: status=0x51 { DriveReady SeekComplete Error }
Jan 29 20:08:49 server kernel: hdb: dma_intr: error=0x84 { DriveStatusError BadCRC }
Jan 29 20:08:51 server kernel: hdb: dma_intr: status=0x51 { DriveReady SeekComplete Error }
Jan 29 20:08:51 server kernel: hdb: dma_intr: error=0x84 { DriveStatusError BadCRC }
Jan 29 20:08:53 server kernel: hdb: dma_intr: status=0x51 { DriveReady SeekComplete Error }
Jan 29 20:08:53 server kernel: hdb: dma_intr: error=0x84 { DriveStatusError BadCRC }
Jan 29 20:08:55 server kernel: hdb: dma_intr: status=0x51 { DriveReady SeekComplete Error }
Jan 29 20:08:55 server kernel: hdb: dma_intr: error=0x84 { DriveStatusError BadCRC }
Jan 29 20:08:55 server kernel: hdb: dma_intr: status=0x51 { DriveReady SeekComplete Error }
Jan 29 20:08:55 server kernel: hdb: dma_intr: error=0x84 { DriveStatusError BadCRC }
Jan 29 20:08:56 server kernel: hdb: dma_intr: status=0x51 { DriveReady SeekComplete Error }
Jan 29 20:08:56 server kernel: hdb: dma_intr: error=0x84 { DriveStatusError BadCRC }
Jan 29 20:08:58 server kernel: hdb: dma_intr: status=0x51 { DriveReady SeekComplete Error }
Jan 29 20:08:58 server kernel: hdb: dma_intr: error=0x84 { DriveStatusError BadCRC }
Jan 29 20:09:00 server kernel: hdb: dma_intr: status=0x51 { DriveReady SeekComplete Error }
Jan 29 20:09:00 server kernel: hdb: dma_intr: error=0x84 { DriveStatusError BadCRC }
Jan 29 20:09:01 server kernel: hdb: dma_intr: status=0x51 { DriveReady SeekComplete Error }
Jan 29 20:09:01 server kernel: hdb: dma_intr: error=0x84 { DriveStatusError BadCRC }
Jan 29 20:09:03 server kernel: hdb: dma_intr: status=0x51 { DriveReady SeekComplete Error }
Jan 29 20:09:03 server kernel: hdb: dma_intr: error=0x84 { DriveStatusError BadCRC }
Jan 29 20:09:13 server kernel: hdb: dma_intr: status=0x51 { DriveReady SeekComplete Error }
Jan 29 20:09:13 server kernel: hdb: dma_intr: error=0x84 { DriveStatusError BadCRC }
Jan 29 20:09:15 server kernel: hdb: dma_intr: status=0x51 { DriveReady SeekComplete Error }
Jan 29 20:09:15 server kernel: hdb: dma_intr: error=0x84 { DriveStatusError BadCRC }
Jan 29 20:09:17 server kernel: hdb: dma_intr: status=0x51 { DriveReady SeekComplete Error }
Jan 29 20:09:17 server kernel: hdb: dma_intr: error=0x84 { DriveStatusError BadCRC }
Jan 29 20:09:18 server kernel: hdb: dma_intr: status=0x51 { DriveReady SeekComplete Error }
Jan 29 20:09:18 server kernel: hdb: dma_intr: error=0x84 { DriveStatusError BadCRC }
Jan 29 20:09:23 server kernel: hdb: dma_intr: status=0x51 { DriveReady SeekComplete Error }
Jan 29 20:09:23 server kernel: hdb: dma_intr: error=0x84 { DriveStatusError BadCRC }
Jan 29 20:09:24 server kernel: hdb: dma_intr: status=0x51 { DriveReady SeekComplete Error }
Jan 29 20:09:24 server kernel: hdb: dma_intr: error=0x84 { DriveStatusError BadCRC }
Jan 29 20:09:29 server kernel: hdb: dma_intr: status=0x51 { DriveReady SeekComplete Error }
Jan 29 20:09:29 server kernel: hdb: dma_intr: error=0x84 { DriveStatusError BadCRC }
Jan 29 20:09:30 server kernel: hdb: dma_intr: status=0x51 { DriveReady SeekComplete Error }
Jan 29 20:09:30 server kernel: hdb: dma_intr: error=0x84 { DriveStatusError BadCRC }
Jan 29 20:09:34 server kernel: hdb: dma_intr: status=0x51 { DriveReady SeekComplete Error }
Jan 29 20:09:34 server kernel: hdb: dma_intr: error=0x84 { DriveStatusError BadCRC }
Jan 29 20:09:36 server kernel: hdb: dma_intr: status=0x51 { DriveReady SeekComplete Error }
Jan 29 20:09:36 server kernel: hdb: dma_intr: error=0x84 { DriveStatusError BadCRC }
Jan 29 20:09:39 server kernel: hdb: dma_intr: status=0x51 { DriveReady SeekComplete Error }
Jan 29 20:09:39 server kernel: hdb: dma_intr: error=0x84 { DriveStatusError BadCRC }
Jan 29 20:09:40 server kernel: hdb: dma_intr: status=0x51 { DriveReady SeekComplete Error }
Jan 29 20:09:40 server kernel: hdb: dma_intr: error=0x84 { DriveStatusError BadCRC }
Jan 29 20:09:43 server kernel: hdb: dma_intr: status=0x51 { DriveReady SeekComplete Error }
Jan 29 20:09:43 server kernel: hdb: dma_intr: error=0x84 { DriveStatusError BadCRC }
Jan 29 20:09:45 server kernel: hdb: dma_intr: status=0x51 { DriveReady SeekComplete Error }
Jan 29 20:09:45 server kernel: hdb: dma_intr: error=0x84 { DriveStatusError BadCRC }
Jan 29 20:09:52 server kernel: hdb: dma_intr: status=0x51 { DriveReady SeekComplete Error }
Jan 29 20:09:52 server kernel: hdb: dma_intr: error=0x84 { DriveStatusError BadCRC }
Jan 29 20:09:54 server kernel: hdb: dma_intr: status=0x51 { DriveReady SeekComplete Error }
Jan 29 20:09:54 server kernel: hdb: dma_intr: error=0x84 { DriveStatusError BadCRC }
Jan 29 20:09:55 server kernel: hdb: dma_intr: status=0x51 { DriveReady SeekComplete Error }
Jan 29 20:09:55 server kernel: hdb: dma_intr: error=0x84 { DriveStatusError BadCRC }
Jan 29 20:09:56 server kernel: hdb: dma_intr: status=0x51 { DriveReady SeekComplete Error }
Jan 29 20:09:56 server kernel: hdb: dma_intr: error=0x84 { DriveStatusError BadCRC }
Jan 29 20:09:58 server kernel: hdb: dma_intr: status=0x51 { DriveReady SeekComplete Error }
Jan 29 20:09:58 server kernel: hdb: dma_intr: error=0x84 { DriveStatusError BadCRC }
Jan 29 20:10:00 server kernel: hdb: dma_intr: status=0x51 { DriveReady SeekComplete Error }
Jan 29 20:10:00 server kernel: hdb: dma_intr: error=0x84 { DriveStatusError BadCRC }
Jan 29 20:10:01 server kernel: hdb: dma_intr: status=0x51 { DriveReady SeekComplete Error }
Jan 29 20:10:01 server kernel: hdb: dma_intr: error=0x84 { DriveStatusError BadCRC }
Jan 29 20:10:05 server kernel: hdb: dma_intr: status=0x51 { DriveReady SeekComplete Error }
Jan 29 20:10:05 server kernel: hdb: dma_intr: error=0x84 { DriveStatusError BadCRC }
Jan 29 20:10:07 server kernel: hdb: dma_intr: status=0x51 { DriveReady SeekComplete Error }
Jan 29 20:10:07 server kernel: hdb: dma_intr: error=0x84 { DriveStatusError BadCRC }
Jan 29 20:10:07 server kernel: hdb: dma_intr: status=0x51 { DriveReady SeekComplete Error }
Jan 29 20:10:07 server kernel: hdb: dma_intr: error=0x84 { DriveStatusError BadCRC }
Jan 29 20:10:09 server kernel: hdb: dma_intr: status=0x51 { DriveReady SeekComplete Error }
Jan 29 20:10:09 server kernel: hdb: dma_intr: error=0x84 { DriveStatusError BadCRC }
Jan 29 20:10:10 server kernel: hdb: dma_intr: status=0x51 { DriveReady SeekComplete Error }
Jan 29 20:10:10 server kernel: hdb: dma_intr: error=0x84 { DriveStatusError BadCRC }
Jan 29 20:10:16 server kernel: hdb: dma_intr: status=0x51 { DriveReady SeekComplete Error }
Jan 29 20:10:16 server kernel: hdb: dma_intr: error=0x84 { DriveStatusError BadCRC }
Jan 29 20:10:17 server kernel: hdb: dma_intr: status=0x51 { DriveReady SeekComplete Error }
Jan 29 20:10:17 server kernel: hdb: dma_intr: error=0x84 { DriveStatusError BadCRC }
Jan 29 20:10:20 server kernel: hdb: dma_intr: status=0x51 { DriveReady SeekComplete Error }
Jan 29 20:10:20 server kernel: hdb: dma_intr: error=0x84 { DriveStatusError BadCRC }
Jan 29 20:10:23 server kernel: hdb: dma_intr: status=0x51 { DriveReady SeekComplete Error }
Jan 29 20:10:23 server kernel: hdb: dma_intr: error=0x84 { DriveStatusError BadCRC }
Jan 29 20:10:30 server kernel: hdb: dma_intr: status=0x51 { DriveReady SeekComplete Error }
Jan 29 20:10:30 server kernel: hdb: dma_intr: error=0x84 { DriveStatusError BadCRC }
Jan 29 20:10:43 server kernel: hdb: dma_intr: status=0x51 { DriveReady SeekComplete Error }
Jan 29 20:10:43 server kernel: hdb: dma_intr: error=0x84 { DriveStatusError BadCRC }
Jan 29 20:10:43 server kernel: hdb: dma_intr: status=0x51 { DriveReady SeekComplete Error }
Jan 29 20:10:43 server kernel: hdb: dma_intr: error=0x84 { DriveStatusError BadCRC }
Jan 29 20:10:52 server kernel: hdb: dma_intr: status=0x51 { DriveReady SeekComplete Error }
Jan 29 20:10:52 server kernel: hdb: dma_intr: error=0x84 { DriveStatusError BadCRC }
Jan 29 20:11:01 server kernel: hdb: dma_intr: status=0x51 { DriveReady SeekComplete Error }
Jan 29 20:11:01 server kernel: hdb: dma_intr: error=0x84 { DriveStatusError BadCRC }
Jan 29 20:11:03 server kernel: hdb: dma_intr: status=0x51 { DriveReady SeekComplete Error }
Jan 29 20:11:03 server kernel: hdb: dma_intr: error=0x84 { DriveStatusError BadCRC }
Jan 29 20:11:19 server kernel: hdb: dma_intr: status=0x51 { DriveReady SeekComplete Error }
Jan 29 20:11:19 server kernel: hdb: dma_intr: error=0x84 { DriveStatusError BadCRC }
Jan 29 20:11:29 server kernel: hdb: dma_intr: status=0x51 { DriveReady SeekComplete Error }
Jan 29 20:11:29 server kernel: hdb: dma_intr: error=0x84 { DriveStatusError BadCRC }
Jan 29 20:11:31 server kernel: hdb: dma_intr: status=0x51 { DriveReady SeekComplete Error }
Jan 29 20:11:31 server kernel: hdb: dma_intr: error=0x84 { DriveStatusError BadCRC }
Jan 29 20:11:34 server kernel: hdb: dma_intr: status=0x51 { DriveReady SeekComplete Error }
Jan 29 20:11:34 server kernel: hdb: dma_intr: error=0x84 { DriveStatusError BadCRC }
Jan 29 20:11:37 server kernel: hdb: dma_intr: status=0x51 { DriveReady SeekComplete Error }
Jan 29 20:11:37 server kernel: hdb: dma_intr: error=0x84 { DriveStatusError BadCRC }
Jan 29 20:11:40 server kernel: hdb: dma_intr: status=0x51 { DriveReady SeekComplete Error }
Jan 29 20:11:40 server kernel: hdb: dma_intr: error=0x84 { DriveStatusError BadCRC }
Jan 29 20:11:48 server kernel: hdb: dma_intr: status=0x51 { DriveReady SeekComplete Error }
Jan 29 20:11:48 server kernel: hdb: dma_intr: error=0x84 { DriveStatusError BadCRC }
Jan 29 20:11:50 server kernel: hdb: dma_intr: status=0x51 { DriveReady SeekComplete Error }
Jan 29 20:11:50 server kernel: hdb: dma_intr: error=0x84 { DriveStatusError BadCRC }
Jan 29 20:11:53 server kernel: hdb: dma_intr: status=0x51 { DriveReady SeekComplete Error }
Jan 29 20:11:53 server kernel: hdb: dma_intr: error=0x84 { DriveStatusError BadCRC }
Jan 29 20:12:00 server kernel: hdb: dma_intr: status=0x51 { DriveReady SeekComplete Error }
Jan 29 20:12:00 server kernel: hdb: dma_intr: error=0x84 { DriveStatusError BadCRC }
Jan 29 20:12:00 server kernel: hdb: dma_intr: status=0x51 { DriveReady SeekComplete Error }
Jan 29 20:12:00 server kernel: hdb: dma_intr: error=0x84 { DriveStatusError BadCRC }
Jan 29 20:12:01 server kernel: hdb: dma_intr: status=0x51 { DriveReady SeekComplete Error }
Jan 29 20:12:01 server kernel: hdb: dma_intr: error=0x84 { DriveStatusError BadCRC }
Jan 29 20:12:10 server kernel: hdb: dma_intr: status=0x51 { DriveReady SeekComplete Error }
Jan 29 20:12:10 server kernel: hdb: dma_intr: error=0x84 { DriveStatusError BadCRC }
Jan 29 20:12:12 server kernel: hdb: dma_intr: status=0x51 { DriveReady SeekComplete Error }
Jan 29 20:12:12 server kernel: hdb: dma_intr: error=0x84 { DriveStatusError BadCRC }
Jan 29 20:12:13 server kernel: hdb: dma_intr: status=0x51 { DriveReady SeekComplete Error }
Jan 29 20:12:13 server kernel: hdb: dma_intr: error=0x84 { DriveStatusError BadCRC }
Jan 29 20:12:16 server kernel: hdb: dma_intr: status=0x51 { DriveReady SeekComplete Error }
Jan 29 20:12:16 server kernel: hdb: dma_intr: error=0x84 { DriveStatusError BadCRC }
Jan 29 20:12:19 server kernel: hdb: dma_intr: status=0x51 { DriveReady SeekComplete Error }
Jan 29 20:12:19 server kernel: hdb: dma_intr: error=0x84 { DriveStatusError BadCRC }
Jan 29 20:12:26 server kernel: hdb: dma_intr: status=0x51 { DriveReady SeekComplete Error }
Jan 29 20:12:26 server kernel: hdb: dma_intr: error=0x84 { DriveStatusError BadCRC }
Jan 29 20:12:29 server kernel: i8253 count too high! resetting..
Jan 29 20:12:29 server kernel: hdb: dma_intr: status=0x51 { DriveReady SeekComplete Error }
Jan 29 20:12:29 server kernel: hdb: dma_intr: error=0x84 { DriveStatusError BadCRC }
Jan 29 20:12:37 server kernel: hdb: dma_intr: status=0x51 { DriveReady SeekComplete Error }
Jan 29 20:12:37 server kernel: hdb: dma_intr: error=0x84 { DriveStatusError BadCRC }
Jan 29 20:12:38 server kernel: hdb: dma_intr: status=0x51 { DriveReady SeekComplete Error }
Jan 29 20:12:38 server kernel: hdb: dma_intr: error=0x84 { DriveStatusError BadCRC }
Jan 29 20:12:39 server kernel: hdb: dma_intr: status=0x51 { DriveReady SeekComplete Error }
Jan 29 20:12:39 server kernel: hdb: dma_intr: error=0x84 { DriveStatusError BadCRC }
Jan 29 20:12:41 server kernel: hdb: dma_intr: status=0x51 { DriveReady SeekComplete Error }
Jan 29 20:12:41 server kernel: hdb: dma_intr: error=0x84 { DriveStatusError BadCRC }
Jan 29 20:12:43 server kernel: hdb: dma_intr: status=0x51 { DriveReady SeekComplete Error }
Jan 29 20:12:43 server kernel: hdb: dma_intr: error=0x84 { DriveStatusError BadCRC }
Jan 29 20:12:43 server kernel: hdb: dma_intr: status=0x51 { DriveReady SeekComplete Error }
Jan 29 20:12:43 server kernel: hdb: dma_intr: error=0x84 { DriveStatusError BadCRC }
Jan 29 20:12:46 server kernel: hdb: dma_intr: status=0x51 { DriveReady SeekComplete Error }
Jan 29 20:12:46 server kernel: hdb: dma_intr: error=0x84 { DriveStatusError BadCRC }
Jan 29 20:12:48 server kernel: hdb: dma_intr: status=0x51 { DriveReady SeekComplete Error }
Jan 29 20:12:48 server kernel: hdb: dma_intr: error=0x84 { DriveStatusError BadCRC }
Jan 29 20:12:49 server kernel: hdb: dma_intr: status=0x51 { DriveReady SeekComplete Error }
Jan 29 20:12:49 server kernel: hdb: dma_intr: error=0x84 { DriveStatusError BadCRC }
Jan 29 20:12:57 server kernel: hdb: dma_intr: status=0x51 { DriveReady SeekComplete Error }
Jan 29 20:12:57 server kernel: hdb: dma_intr: error=0x84 { DriveStatusError BadCRC }
Jan 29 20:12:59 server kernel: hdb: dma_intr: status=0x51 { DriveReady SeekComplete Error }
Jan 29 20:12:59 server kernel: hdb: dma_intr: error=0x84 { DriveStatusError BadCRC }
Jan 29 20:13:06 server kernel: hdb: dma_intr: status=0x51 { DriveReady SeekComplete Error }
Jan 29 20:13:06 server kernel: hdb: dma_intr: error=0x84 { DriveStatusError BadCRC }
Jan 29 20:13:08 server kernel: hdb: dma_intr: status=0x53 { DriveReady SeekComplete Index Error }
Jan 29 20:13:08 server kernel: hdb: dma_intr: error=0x84 { DriveStatusError BadCRC }
Jan 29 20:13:13 server kernel: hdb: dma_intr: status=0x51 { DriveReady SeekComplete Error }
Jan 29 20:13:13 server kernel: hdb: dma_intr: error=0x84 { DriveStatusError BadCRC }
Jan 29 20:13:17 server kernel: hdb: dma_intr: status=0x51 { DriveReady SeekComplete Error }
Jan 29 20:13:17 server kernel: hdb: dma_intr: error=0x84 { DriveStatusError BadCRC }
Jan 29 20:13:29 server kernel: hdb: dma_intr: status=0x51 { DriveReady SeekComplete Error }
Jan 29 20:13:29 server kernel: hdb: dma_intr: error=0x84 { DriveStatusError BadCRC }
Jan 29 20:13:41 server kernel: hdb: dma_intr: status=0x51 { DriveReady SeekComplete Error }
Jan 29 20:13:41 server kernel: hdb: dma_intr: error=0x84 { DriveStatusError BadCRC }
Jan 29 20:13:43 server kernel: hdb: dma_intr: status=0x51 { DriveReady SeekComplete Error }
Jan 29 20:13:43 server kernel: hdb: dma_intr: error=0x84 { DriveStatusError BadCRC }
Jan 29 20:13:54 server kernel: hdb: dma_intr: status=0x51 { DriveReady SeekComplete Error }
Jan 29 20:13:54 server kernel: hdb: dma_intr: error=0x84 { DriveStatusError BadCRC }
Jan 29 20:13:56 server kernel: hdb: dma_intr: status=0x51 { DriveReady SeekComplete Error }
Jan 29 20:13:56 server kernel: hdb: dma_intr: error=0x84 { DriveStatusError BadCRC }
Jan 29 20:13:57 server kernel: hdb: dma_intr: status=0x51 { DriveReady SeekComplete Error }
Jan 29 20:13:57 server kernel: hdb: dma_intr: error=0x84 { DriveStatusError BadCRC }
Jan 29 20:14:03 server kernel: hdb: dma_intr: status=0x51 { DriveReady SeekComplete Error }
Jan 29 20:14:03 server kernel: hdb: dma_intr: error=0x84 { DriveStatusError BadCRC }
Jan 29 20:14:06 server kernel: hdb: dma_intr: status=0x51 { DriveReady SeekComplete Error }
Jan 29 20:14:06 server kernel: hdb: dma_intr: error=0x84 { DriveStatusError BadCRC }
Jan 29 20:14:11 server kernel: hdb: dma_intr: status=0x51 { DriveReady SeekComplete Error }
Jan 29 20:14:11 server kernel: hdb: dma_intr: error=0x84 { DriveStatusError BadCRC }
Jan 29 20:14:13 server kernel: hdb: dma_intr: status=0x51 { DriveReady SeekComplete Error }
Jan 29 20:14:13 server kernel: hdb: dma_intr: error=0x84 { DriveStatusError BadCRC }
Jan 29 20:14:14 server kernel: hdb: dma_intr: status=0x53 { DriveReady SeekComplete Index Error }
Jan 29 20:14:14 server kernel: hdb: dma_intr: error=0x84 { DriveStatusError BadCRC }
Jan 29 20:14:18 server kernel: hdb: dma_intr: status=0x51 { DriveReady SeekComplete Error }
Jan 29 20:14:18 server kernel: hdb: dma_intr: error=0x84 { DriveStatusError BadCRC }
Jan 29 20:14:19 server kernel: hdb: dma_intr: status=0x51 { DriveReady SeekComplete Error }
Jan 29 20:14:19 server kernel: hdb: dma_intr: error=0x84 { DriveStatusError BadCRC }
Jan 29 20:14:20 server kernel: hdb: dma_intr: status=0x51 { DriveReady SeekComplete Error }
Jan 29 20:14:20 server kernel: hdb: dma_intr: error=0x84 { DriveStatusError BadCRC }
Jan 29 20:14:21 server kernel: hdb: dma_intr: status=0x51 { DriveReady SeekComplete Error }
Jan 29 20:14:21 server kernel: hdb: dma_intr: error=0x84 { DriveStatusError BadCRC }
Jan 29 20:14:22 server kernel: hdb: dma_intr: status=0x51 { DriveReady SeekComplete Error }
Jan 29 20:14:22 server kernel: hdb: dma_intr: error=0x84 { DriveStatusError BadCRC }
Jan 29 20:14:28 server kernel: hdb: dma_intr: status=0x51 { DriveReady SeekComplete Error }
Jan 29 20:14:28 server kernel: hdb: dma_intr: error=0x84 { DriveStatusError BadCRC }
Jan 29 20:14:30 server kernel: hdb: dma_intr: status=0x51 { DriveReady SeekComplete Error }
Jan 29 20:14:30 server kernel: hdb: dma_intr: error=0x84 { DriveStatusError BadCRC }
Jan 29 20:14:33 server kernel: hdb: dma_intr: status=0x51 { DriveReady SeekComplete Error }
Jan 29 20:14:33 server kernel: hdb: dma_intr: error=0x84 { DriveStatusError BadCRC }
Jan 29 20:14:45 server kernel: hdb: dma_intr: status=0x51 { DriveReady SeekComplete Error }
Jan 29 20:14:45 server kernel: hdb: dma_intr: error=0x84 { DriveStatusError BadCRC }
Jan 29 20:14:48 server kernel: hdb: dma_intr: status=0x51 { DriveReady SeekComplete Error }
Jan 29 20:14:48 server kernel: hdb: dma_intr: error=0x84 { DriveStatusError BadCRC }
Jan 29 20:15:00 server su(pam_unix)[4354]: session opened for user qmailr by (uid=0)
Jan 29 20:15:00 server su(pam_unix)[4354]: session closed for user qmailr
Jan 29 20:15:01 server kernel: hdb: dma_intr: status=0x51 { DriveReady SeekComplete Error }
Jan 29 20:15:01 server kernel: hdb: dma_intr: error=0x84 { DriveStatusError BadCRC }
Jan 29 20:15:02 server kernel: hdb: dma_intr: status=0x51 { DriveReady SeekComplete Error }
Jan 29 20:15:02 server kernel: hdb: dma_intr: error=0x84 { DriveStatusError BadCRC }
Jan 29 20:15:03 server kernel: hdb: dma_intr: status=0x51 { DriveReady SeekComplete Error }
Jan 29 20:15:03 server kernel: hdb: dma_intr: error=0x84 { DriveStatusError BadCRC }
Jan 29 20:15:21 server kernel: hdb: dma_intr: status=0x51 { DriveReady SeekComplete Error }
Jan 29 20:15:21 server kernel: hdb: dma_intr: error=0x84 { DriveStatusError BadCRC }
Jan 29 20:15:25 server kernel: hdb: dma_intr: status=0x51 { DriveReady SeekComplete Error }
Jan 29 20:15:25 server kernel: hdb: dma_intr: error=0x84 { DriveStatusError BadCRC }
Jan 29 20:17:28 server PAM_pwdb[4392]: authentication failure; (uid=101) -> admin for pwauth service
Jan 29 20:17:56 server kernel: hdb: dma_intr: status=0x51 { DriveReady SeekComplete Error }
Jan 29 20:17:56 server kernel: hdb: dma_intr: error=0x84 { DriveStatusError BadCRC }
Jan 29 20:18:43 server kernel: md: md1: sync done.
Jan 29 20:20:47 server kernel: denylog:IN=eth1 OUT= MAC=00:30:bd:72:e5:e3:00:05:74:f1:dc:a8:08:00 SRC=200.252.246.10 DST=69.142.252.133 LEN=48 TOS=0x00 PREC=0x00 TTL=107 ID=27051 PROTO=TCP SPT=12268 DPT=3389 WINDOW=65535 RES=0x00 SYN URGP=0
Jan 29 20:20:50 server kernel: denylog:IN=eth1 OUT= MAC=00:30:bd:72:e5:e3:00:05:74:f1:dc:a8:08:00 SRC=200.252.246.10 DST=69.142.252.133 LEN=48 TOS=0x00 PREC=0x00 TTL=107 ID=27228 PROTO=TCP SPT=12268 DPT=3389 WINDOW=65535 RES=0x00 SYN URGP=0
Jan 29 20:21:20 server kernel: hdb: dma_intr: status=0x51 { DriveReady SeekComplete Error }
Jan 29 20:21:20 server kernel: hdb: dma_intr: error=0x84 { DriveStatusError BadCRC }
Jan 29 20:21:57 server kernel: hdb: dma_intr: status=0x51 { DriveReady SeekComplete Error }
Jan 29 20:21:57 server kernel: hdb: dma_intr: error=0x84 { DriveStatusError BadCRC }
Jan 29 20:21:57 server kernel: hdb: dma_intr: status=0x51 { DriveReady SeekComplete Error }
Jan 29 20:21:57 server kernel: hdb: dma_intr: error=0x84 { DriveStatusError BadCRC }
Jan 29 20:22:54 server kernel: i8253 count too high! resetting..
Jan 29 20:23:18 server kernel: denylog:IN=eth1 OUT= MAC=00:30:bd:72:e5:e3:00:05:74:f1:dc:a8:08:00 SRC=69.41.170.124 DST=69.142.252.133 LEN=40 TOS=0x00 PREC=0x00 TTL=240 ID=19645 PROTO=TCP SPT=3978 DPT=3306 WINDOW=4096 RES=0x00 SYN URGP=0
Jan 29 20:23:29 server kernel: i8253 count too high! resetting..
Jan 29 20:23:31 server kernel: i8253 count too high! resetting..
Jan 29 20:25:29 server kernel: hdb: dma_intr: status=0x51 { DriveReady SeekComplete Error }
Jan 29 20:25:29 server kernel: hdb: dma_intr: error=0x84 { DriveStatusError BadCRC }
Jan 29 20:25:40 server kernel: hdb: dma_intr: status=0x51 { DriveReady SeekComplete Error }
Jan 29 20:25:40 server kernel: hdb: dma_intr: error=0x84 { DriveStatusError BadCRC }
Jan 29 20:25:45 server kernel: hdb: dma_intr: status=0x51 { DriveReady SeekComplete Error }
Jan 29 20:25:45 server kernel: hdb: dma_intr: error=0x84 { DriveStatusError BadCRC }
Jan 29 20:25:45 server kernel: hdb: dma_intr: status=0x51 { DriveReady SeekComplete Error }
Jan 29 20:25:45 server kernel: hdb: dma_intr: error=0x84 { DriveStatusError BadCRC }
Jan 29 20:25:53 server kernel: hdb: dma_intr: status=0x51 { DriveReady SeekComplete Error }
Jan 29 20:25:53 server kernel: hdb: dma_intr: error=0x84 { DriveStatusError BadCRC }
Jan 29 20:26:00 server kernel: hdb: dma_intr: status=0x51 { DriveReady SeekComplete Error }
Jan 29 20:26:00 server kernel: hdb: dma_intr: error=0x84 { DriveStatusError BadCRC }
Jan 29 20:26:04 server kernel: hdb: dma_intr: status=0x51 { DriveReady SeekComplete Error }
Jan 29 20:26:04 server kernel: hdb: dma_intr: error=0x84 { DriveStatusError BadCRC }
Jan 29 20:26:04 server kernel: hdb: dma_intr: status=0x51 { DriveReady SeekComplete Error }
Jan 29 20:26:04 server kernel: hdb: dma_intr: error=0x84 { DriveStatusError BadCRC }
Jan 29 20:26:05 server kernel: hdb: dma_intr: status=0x51 { DriveReady SeekComplete Error }
Jan 29 20:26:05 server kernel: hdb: dma_intr: error=0x84 { DriveStatusError BadCRC }
Jan 29 20:26:09 server kernel: hdb: dma_intr: status=0x51 { DriveReady SeekComplete Error }
Jan 29 20:26:09 server kernel: hdb: dma_intr: error=0x84 { DriveStatusError BadCRC }
Jan 29 20:26:10 server kernel: hdb: dma_intr: status=0x51 { DriveReady SeekComplete Error }
Jan 29 20:26:10 server kernel: hdb: dma_intr: error=0x84 { DriveStatusError BadCRC }
Jan 29 20:26:11 server kernel: hdb: dma_intr: status=0x51 { DriveReady SeekComplete Error }
Jan 29 20:26:11 server kernel: hdb: dma_intr: error=0x84 { DriveStatusError BadCRC }
Jan 29 20:26:11 server kernel: hdb: dma_intr: status=0x51 { DriveReady SeekComplete Error }
Jan 29 20:26:11 server kernel: hdb: dma_intr: error=0x84 { DriveStatusError BadCRC }
Jan 29 20:26:13 server kernel: hdb: dma_intr: status=0x51 { DriveReady SeekComplete Error }
Jan 29 20:26:13 server kernel: hdb: dma_intr: error=0x84 { DriveStatusError BadCRC }
Jan 29 20:26:14 server kernel: hdb: dma_intr: status=0x51 { DriveReady SeekComplete Error }
Jan 29 20:26:14 server kernel: hdb: dma_intr: error=0x84 { DriveStatusError BadCRC }
Jan 29 20:26:14 server kernel: hdb: dma_intr: status=0x51 { DriveReady SeekComplete Error }
Jan 29 20:26:14 server kernel: hdb: dma_intr: error=0x84 { DriveStatusError BadCRC }
Jan 29 20:26:22 server kernel: hdb: dma_intr: status=0x51 { DriveReady SeekComplete Error }
Jan 29 20:26:22 server kernel: hdb: dma_intr: error=0x84 { DriveStatusError BadCRC }
Jan 29 20:26:22 server kernel: hdb: dma_intr: status=0x51 { DriveReady SeekComplete Error }
Jan 29 20:26:22 server kernel: hdb: dma_intr: error=0x84 { DriveStatusError BadCRC }
Jan 29 20:26:22 server kernel: hdb: dma_intr: status=0x51 { DriveReady SeekComplete Error }
Jan 29 20:26:22 server kernel: hdb: dma_intr: error=0x84 { DriveStatusError BadCRC }
Jan 29 20:26:22 server kernel: hdb: dma_intr: status=0x51 { DriveReady SeekComplete Error }
Jan 29 20:26:22 server kernel: hdb: dma_intr: error=0x84 { DriveStatusError BadCRC }
Jan 29 20:26:22 server kernel: hdb: dma_intr: status=0x51 { DriveReady SeekComplete Error }
Jan 29 20:26:22 server kernel: hdb: dma_intr: error=0x84 { DriveStatusError BadCRC }
Jan 29 20:26:22 server kernel: hdb: dma_intr: status=0x51 { DriveReady SeekComplete Error }
Jan 29 20:26:22 server kernel: hdb: dma_intr: error=0x84 { DriveStatusError BadCRC }
Jan 29 20:26:50 server kernel: hdb: dma_intr: status=0x51 { DriveReady SeekComplete Error }
Jan 29 20:26:50 server kernel: hdb: dma_intr: error=0x84 { DriveStatusError BadCRC }
Jan 29 20:27:03 server kernel: i8253 count too high! resetting..
Jan 29 20:28:12 server kernel: hdb: dma_intr: status=0x51 { DriveReady SeekComplete Error }
Jan 29 20:28:12 server kernel: hdb: dma_intr: error=0x84 { DriveStatusError BadCRC }
Jan 29 20:28:40 server kernel: i8253 count too high! resetting..
Jan 29 20:30:00 server su(pam_unix)[4427]: session opened for user qmailr by (uid=0)
Jan 29 20:30:00 server su(pam_unix)[4427]: session closed for user qmailr
Jan 29 20:30:47 server kernel: i8253 count too high! resetting..
Jan 29 20:31:22 server kernel: hdb: dma_intr: status=0x51 { DriveReady SeekComplete Error }
Jan 29 20:31:22 server kernel: hdb: dma_intr: error=0x84 { DriveStatusError BadCRC }
Jan 29 20:31:27 server kernel: hdb: dma_intr: status=0x51 { DriveReady SeekComplete Error }
Jan 29 20:31:27 server kernel: hdb: dma_intr: error=0x84 { DriveStatusError BadCRC }
Jan 29 20:31:27 server kernel: hdb: dma_intr: status=0x51 { DriveReady SeekComplete Error }
Jan 29 20:31:27 server kernel: hdb: dma_intr: error=0x84 { DriveStatusError BadCRC }
Jan 29 20:31:36 server kernel: hdb: dma_intr: status=0x51 { DriveReady SeekComplete Error }
Jan 29 20:31:36 server kernel: hdb: dma_intr: error=0x84 { DriveStatusError BadCRC }
Jan 29 20:31:36 server kernel: hdb: dma_intr: status=0x51 { DriveReady SeekComplete Error }
Jan 29 20:31:36 server kernel: hdb: dma_intr: error=0x84 { DriveStatusError BadCRC }
Jan 29 20:31:41 server kernel: hdb: dma_intr: status=0x51 { DriveReady SeekComplete Error }
Jan 29 20:31:41 server kernel: hdb: dma_intr: error=0x84 { DriveStatusError BadCRC }
Jan 29 20:31:44 server kernel: hdb: dma_intr: status=0x51 { DriveReady SeekComplete Error }
Jan 29 20:31:44 server kernel: hdb: dma_intr: error=0x84 { DriveStatusError BadCRC }
Jan 29 20:32:11 server kernel: hdb: dma_intr: status=0x51 { DriveReady SeekComplete Error }
Jan 29 20:32:11 server kernel: hdb: dma_intr: error=0x84 { DriveStatusError BadCRC }
Jan 29 20:32:19 server kernel: hdb: dma_intr: status=0x51 { DriveReady SeekComplete Error }
Jan 29 20:32:19 server kernel: hdb: dma_intr: error=0x84 { DriveStatusError BadCRC }
Jan 29 20:32:20 server kernel: hdb: dma_intr: status=0x51 { DriveReady SeekComplete Error }
Jan 29 20:32:20 server kernel: hdb: dma_intr: error=0x84 { DriveStatusError BadCRC }
Jan 29 20:32:30 server kernel: hdb: dma_intr: status=0x51 { DriveReady SeekComplete Error }
Jan 29 20:32:30 server kernel: hdb: dma_intr: error=0x84 { DriveStatusError BadCRC }
Jan 29 20:32:56 server kernel: hdb: dma_intr: status=0x51 { DriveReady SeekComplete Error }
Jan 29 20:32:56 server kernel: hdb: dma_intr: error=0x84 { DriveStatusError BadCRC }
Jan 29 20:33:46 server kernel: hdb: dma_intr: status=0x51 { DriveReady SeekComplete Error }
Jan 29 20:33:46 server kernel: hdb: dma_intr: error=0x84 { DriveStatusError BadCRC }
Jan 29 20:33:46 server kernel: hdb: dma_intr: status=0x51 { DriveReady SeekComplete Error }
Jan 29 20:33:46 server kernel: hdb: dma_intr: error=0x84 { DriveStatusError BadCRC }
Jan 29 20:33:47 server kernel: hdb: dma_intr: status=0x51 { DriveReady SeekComplete Error }
Jan 29 20:33:47 server kernel: hdb: dma_intr: error=0x84 { DriveStatusError BadCRC }
Jan 29 20:34:01 server kernel: hdb: dma_intr: status=0x51 { DriveReady SeekComplete Error }
Jan 29 20:34:01 server kernel: hdb: dma_intr: error=0x84 { DriveStatusError BadCRC }
Jan 29 20:34:01 server kernel: hdb: dma_intr: status=0x51 { DriveReady SeekComplete Error }
Jan 29 20:34:01 server kernel: hdb: dma_intr: error=0x84 { DriveStatusError BadCRC }
Jan 29 20:34:01 server kernel: hdb: dma_intr: status=0x51 { DriveReady SeekComplete Error }
Jan 29 20:34:01 server kernel: hdb: dma_intr: error=0x84 { DriveStatusError BadCRC }
Jan 29 20:34:06 server kernel: hdb: dma_intr: status=0x51 { DriveReady SeekComplete Error }
Jan 29 20:34:06 server kernel: hdb: dma_intr: error=0x84 { DriveStatusError BadCRC }
Jan 29 20:34:07 server kernel: hdb: dma_intr: status=0x51 { DriveReady SeekComplete Error }
Jan 29 20:34:07 server kernel: hdb: dma_intr: error=0x84 { DriveStatusError BadCRC }
Jan 29 20:34:20 server kernel: hdb: dma_intr: status=0x51 { DriveReady SeekComplete Error }
Jan 29 20:34:20 server kernel: hdb: dma_intr: error=0x84 { DriveStatusError BadCRC }
Jan 29 20:34:22 server kernel: hdb: dma_intr: status=0x51 { DriveReady SeekComplete Error }
Jan 29 20:34:22 server kernel: hdb: dma_intr: error=0x84 { DriveStatusError BadCRC }
Jan 29 20:34:26 server kernel: hdb: dma_intr: status=0x51 { DriveReady SeekComplete Error }
Jan 29 20:34:26 server kernel: hdb: dma_intr: error=0x84 { DriveStatusError BadCRC }
Jan 29 20:34:33 server sshd[4462]: Accepted password for root from 192.168.1.3 port 4477 ssh2
Jan 29 20:34:34 server sshd(pam_unix)[4464]: session opened for user root by root(uid=0)
Jan 29 20:34:56 server kernel: hdb: dma_intr: status=0x51 { DriveReady SeekComplete Error }
Jan 29 20:34:56 server kernel: hdb: dma_intr: error=0x84 { DriveStatusError BadCRC }
Jan 29 20:34:58 server kernel: hdb: dma_intr: status=0x51 { DriveReady SeekComplete Error }
Jan 29 20:34:58 server kernel: hdb: dma_intr: error=0x84 { DriveStatusError BadCRC }
Jan 29 20:34:59 server kernel: hdb: dma_intr: status=0x51 { DriveReady SeekComplete Error }
Jan 29 20:34:59 server kernel: hdb: dma_intr: error=0x84 { DriveStatusError BadCRC }
Jan 29 20:35:09 server kernel: hdb: dma_intr: status=0x51 { DriveReady SeekComplete Error }
Jan 29 20:35:09 server kernel: hdb: dma_intr: error=0x84 { DriveStatusError BadCRC }
Jan 29 20:35:10 server kernel: hdb: dma_intr: status=0x51 { DriveReady SeekComplete Error }
Jan 29 20:35:10 server kernel: hdb: dma_intr: error=0x84 { DriveStatusError BadCRC }
Jan 29 20:35:19 server kernel: i8253 count too high! resetting..
Jan 29 20:36:37 server kernel: hdb: dma_intr: status=0x51 { DriveReady SeekComplete Error }
Jan 29 20:36:37 server kernel: hdb: dma_intr: error=0x84 { DriveStatusError BadCRC }
Jan 29 20:36:50 server kernel: denylog:IN=eth1 OUT= MAC=00:30:bd:72:e5:e3:00:05:74:f1:dc:a8:08:00 SRC=222.88.173.5 DST=69.142.252.133 LEN=668 TOS=0x00 PREC=0x00 TTL=105 ID=32538 PROTO=UDP SPT=9495 DPT=1026 LEN=648
Jan 29 20:37:31 server kernel: i8253 count too high! resetting..
Jan 29 20:38:25 server oidentd[4518]: Connection from amsnac3.com (69.72.229.82):56313
Jan 29 20:38:25 server oidentd[4518]: [amsnac3.com] 32916 , 25 : ERROR : NO-USER

New 6.01-1 Install. Mirrored Drives - CRC Errors
« Reply #1 on: January 30, 2005, 03:26:13 PM »
.. drive hdb has a faulty format (low level) or has one or more bad sectors (the crc errors reported come from the drive electronics).

Best get another drive!
..................

pistonpilot

New 6.01-1 Install. Mirrored Drives - CRC Errors
« Reply #2 on: January 30, 2005, 07:11:47 PM »
Quote from: "smeghead"
.. drive hdb has a faulty format (low level) or has one or more bad sectors (the crc errors reported come from the drive electronics).

Best get another drive!


I'm running Spinrite on the drive - http://www.grc.com

If there are bad sectors, spinrite will move the data and mark them as bad.  If it is the low level format, then Spinrite will also fix this as it does a low-level format with data in place.  It literally picks up the data, formats the sector and then lays the data back onto the sector.

My concern was that it was a problem with the controller or the software raid built into e-smith.

H

New 6.01-1 Install. Mirrored Drives - CRC Errors
« Reply #3 on: January 30, 2005, 09:17:49 PM »
.. basically I work on the idea that all my important stuff is on the server so why use anything in it that might fail & give me grief I can do without.

Replace the drive and use the old one for testing purposes where it can't bite ya.
..................

pistonpilot

New 6.01-1 Install. Mirrored Drives - CRC Errors
« Reply #4 on: January 30, 2005, 10:04:38 PM »
You're correct, but if the drive has a few bad sectors that can be blocked out, why worry about it?  It's an older set of drives so I expect some error if not due anything other than needed an new ll format.

Well, they just got their low-level format via Spinrite so they should be good to go.  I'll know later tonight when I go there to finish the job.

I run spinrite on my drives once in a while when I can afford the day's downtime.  Spinrite is a great preventative in addition to being an emergency lifesaver.

PP

pistonpilot

New 6.01-1 Install. Mirrored Drives - CRC Errors
« Reply #5 on: January 31, 2005, 10:42:38 AM »
Score one for Spinrite.  Spinrite said the drives were flawless.  Spinrite did blame a bunch of CRC errors on cabling.  

I rebooted and the CRC errors disappeared.

New 6.01-1 Install. Mirrored Drives - CRC Errors
« Reply #6 on: February 07, 2005, 10:59:11 PM »
Did you replace the cable?

Quote from: "pistonpilot"
Score one for Spinrite.  Spinrite said the drives were flawless.  Spinrite did blame a bunch of CRC errors on cabling.  

I rebooted and the CRC errors disappeared.

pistonpilot

New 6.01-1 Install. Mirrored Drives - CRC Errors
« Reply #7 on: February 08, 2005, 02:02:15 AM »
No I did not.  I noticed the errors came back.  I'm not sure if it is the actual cable or controller.  Could be an incompatability between E-smith and the controller - who knows.

I think it has more to do with the delayed writes on the mirror.

New 6.01-1 Install. Mirrored Drives - CRC Errors
« Reply #8 on: February 08, 2005, 02:07:46 AM »
Hi,
No I do not think that is what it is, as I have the same thing happening on one machine with an MRS Hardware subraid in it (*the system sees it as one drive)
I am going to try different drives.
Dan
Quote from: "pistonpilot"
No I did not.  I noticed the errors came back.  I'm not sure if it is the actual cable or controller.  Could be an incompatability between E-smith and the controller - who knows.

I think it has more to do with the delayed writes on the mirror.

brabus

New 6.01-1 Install. Mirrored Drives - CRC Errors
« Reply #9 on: February 12, 2005, 08:32:27 AM »
Just in case anyone else gets a similar error, just on boot and all that it says is "CRC error", look at your box again and see if you have it overclocked.  I tried different drives, different cables, different cd rom drive and a whole host of other variables.  Then i looked in the bios and realised my little Tualatin was running at 133 mhz FSB instead of the stock 100 Mhz.  Bumped it back down and installed again and everything was fine.

Though it seems a bit illogical to have the box overclocked all other OS i have loaded on, Smoothwall, clarkconnect, debian, xp pro and 2003 server have not had any issues with installation or day to day running activities.  Just diving into the world of E-smith and im sure i will have a host of questions for you guys  :-D

New 6.01-1 Install. Mirrored Drives - CRC Errors
« Reply #10 on: February 12, 2005, 02:31:45 PM »
@pistonpilot
Quote
Jan 29 20:12:19 server kernel: hdb: dma_intr: status=0x51 { DriveReady SeekComplete Error }
Jan 29 20:12:19 server kernel: hdb: dma_intr: error=0x84 { DriveStatusError BadCRC }
Jan 29 20:12:26 server kernel: hdb: dma_intr: status=0x51 { DriveReady SeekComplete Error }
Jan 29 20:12:26 server kernel: hdb: dma_intr: error=0x84 { DriveStatusError BadCRC }
Jan 29 20:12:29 server kernel: i8253 count too high! resetting..


That's shure looks like a typical cable/dma fault.
HD cannot run/be accessed via dma at that speed.
If it did run, XP won't show you (and mostly due to it's caching it just "feels" slower <Beg>).
Maybe you just have a (cheap) cable that's not pressed hard enough onto it's connectors (bent ?).
- Post a: hdparm -I /dev/hdb
- It would be helpful to know the name/make of your controller (chipset)...

Note that spinrite isn't all helpful with newer (=1999)drives.
If you want an "almost recent review" or "flack from the other side" visit:
http://www.kickstartnews.com/reviews/utilities/spinrite_v6.html
http://grcsucks.com/spinrite.htm

Have a look into S.M.A.R.T. "Self monitoring, analysis, and reporting technology".
...most HD's will just correct the problems you mention by themselves and
nowadays spinrite will never even "see" an error of the kind you are discussing.
Controllers that intermittendly fail are extremely rare. They either work (master&slave) or are dead.
Please buy a new ide-cable for 2 $/Euro if it has only 40 wires running !!!

And @ brabus ...
How much do you "speed-up" a server that's operating around 5% of its load in general ? -
How much faster will "all other OS i have loaded" be with 30% more cpu clock ?? -
How much more will that server "serve" across the net ???
Note: X-ing fingers you are not in any way related to the company that installed some expensive stuff into my car  :-o :-(
...at least please assure me that you are not running any of their IT stuff  8-) .

Regards
Reinhold

P.S.: Sheez - this in "experienced"  :oops:
............

brabus

New 6.01-1 Install. Mirrored Drives - CRC Errors
« Reply #11 on: February 13, 2005, 12:27:48 AM »
Yeah sorry guys realised its a bit of a newbie reply but what i always keep in mind is that more often than not, many issues affecting "experienced" admins or techs are simple ones that are overlooked.  The server i am running is not for mission critical its a test box for myself and running at the greater FSB made a significant performance difference in Windows 2003, Windows 2000 server and also XP.  This was due to loading times and also when the processor had a heavy load.

New 6.01-1 Install. Mirrored Drives - CRC Errors
« Reply #12 on: March 03, 2005, 07:25:44 PM »
Quote

That's shure looks like a typical cable/dma fault.
HD cannot run/be accessed via dma at that speed.
If it did run, XP won't show you (and mostly due to it's caching it just "feels" slower <Beg>).
Maybe you just have a (cheap) cable that's not pressed hard enough onto it's connectors (bent ?).
- Post a: hdparm -I /dev/hdb
- It would be helpful to know the name/make of your controller (chipset)...


Hi,
I have found a second server also doing the same thing.
It is important to note I did change IDE cables, tested the drives etc with no improvement (the errors are still there)
When these errors happen the server slows to a useless state.
Dan

results of two different servers: hdparm -I /dev/hda
« Reply #13 on: March 04, 2005, 05:24:46 AM »
SERVER#1
[root@smeserver root]# hdparm -I /dev/hda

/dev/hda:

non-removable ATA device, with non-removable media
        Model Number:           MRS SubRAID Rev 3.50
        Serial Number:
        Firmware Revision:      Rev 3.50
Standards:
        Supported: 1 2 3 4 5 6
        Likely used: 6
Configuration:
        Logical         max     current
        cylinders       16383   65535
        heads           16      1
        sectors/track   63      63
        bytes/track:    0               (obsolete)
        bytes/sector:   0               (obsolete)
        current sector capacity: 4128705
        LBA user addressable sectors = 156301488
Capabilities:
        LBA, IORDY(can be disabled)
        Queue depth: 1
        Standby timer values: spec'd by standard, with device specific minimum
        r/w multiple sector transfer: Max = 16  Current = 16
        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:
           *    Power Management feature set
           *    SMART feature set
HW reset results:
        CBLID- above Vih
        Device num = 1
[root@smeserver root]#

SERVER#2
[root@smeserver root]# hdparm -I /dev/hda

/dev/hda:

non-removable ATA device, with non-removable media
Model Number:           MRS SubRAID Rev 3.40
Serial Number:
Firmware Revision:      Rev 3.40
Standards:
Supported: 1 2 3 4 5 6
Likely used: 6
Configuration:
Logical         max     current
cylinders       16383   65535
heads           16      1
sectors/track   63      63
bytes/track:    0               (obsolete)
bytes/sector:   0               (obsolete)
current sector capacity: 4128705
LBA user addressable sectors = 78165360
Capabilities:
LBA, IORDY(can be disabled)
Queue depth: 1
Standby timer values: spec'd by standard, with device specific minimum
r/w multiple sector transfer: Max = 16  Current = 16
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:
*    Power Management feature set
*    SMART feature set
SET MAX security extension
*    DOWNLOAD MICROCODE cmd
HW reset results:
CBLID- above Vih
Device num = 1
[root@smeserver root]#