search for: icrc

...24288 1048576 4.2BSD 2048 16384 94 # (Cyl. 1040*- 1560*) e: 37529472 1572864 4.2BSD 2048 16384 94 # (Cyl. 1560*- 38791*) **************************************************************** I have that (to me) crypted errore message.. can anybody tell me what does that UDMA ICRC error means? May 24 19:58:30 saturn /kernel: ad0: DMA limited to UDMA33, non-ATA66 cable or device May 24 19:58:30 saturn /kernel: ad0: 9770MB <Maxtor 91021U2> [19852/16/63] at ata0-master UDMA33 May 24 19:58:30 saturn /kernel: ad1: 19092MB <Maxtor 2B020H1> [38792/16/63] at ata1-mas...

Hi, We're using gmirror on our sun fire x2100 and FreeBSD 6.1-p10. Some days ago I found this in the logs: Apr 1 02:12:05 x2100 kernel: ad6: WARNING - WRITE_DMA48 UDMA ICRC error (retrying request) LBA=612960533 Apr 1 02:12:05 x2100 kernel: ad6: FAILURE - WRITE_DMA48 status=51<READY,DSC,ERROR> error=10<NID_NOT_FOUND> LBA=612960533 Apr 1 02:12:05 x2100 kernel: GEOM_MIRROR: Request failed (error=5). ad6[WRITE(offset=313835792896, length=4096)] Apr 1 02:12...

Hi. I am looking for an IPv6 capable CVSUP mirror. I found a discussion from one year ago where it was stated that CVSUP was not IPv6-capable. Does anyone know if this has changed? Sam -- Samuel Tardieu -- sam@rfc1149.net -- http://www.rfc1149.net/sam

Hello, I've got a (P)ATA disk in a special frame. The disk itself supports UDMA-100 (and has an 80-ribbon cable), but the frame isn't compatible with that. By default, FreeBSD negotiates UDMA-100, and the console starts to fill with ICRC errors. In the past, I used a patch to ata-all.c that enabled the following entry in loader.conf to force the disk to UDMA-33, so it worked fine: hw.ata.ata_dma_limit="2" But with the "new world", that doesn't work anymore. What is the proper way with ATA_CAM and ada(4) t...

...days. Error 431 occurred at disk power-on lifetime: 21885 hours (911 days + 21 hours) When the command that caused the error occurred, the device was active or idle. After command completion occurred, registers were: ER ST SC SN CL CH DH -- -- -- -- -- -- -- 84 51 00 ac 28 f9 e1 Error: ICRC, ABRT at LBA = 0x01f928ac = 33106092 Commands leading to the command that caused the error were: CR FR SC SN CL CH DH DC Powered_Up_Time Command/Feature_Name -- -- -- -- -- -- -- -- ---------------- -------------------- c8 00 08 a5 28 f9 e1 00 9d+18:33:42.900 READ DMA c8 00 68 3d...

...ver. During backup with bacula I discovered an complete system freeze (no keyboard, nfs, disk...) after the following lines on the screen: ... ad0: TIMEOUT - WRITE_DMA retrying (1 retry left) LBA=108916879 ad1: TIMEOUT - WRITE_DMA retrying (1 retry left) LBA=116030287 ad1: WARNING - WRITE_DMA UDMA ICRC error (retrying request) LBA=108911183 ad1: WARNING - WRITE_DMA UDMA ICRC error (retrying request) LBA=108378767 Since I could ping the system and after waiting a couple of hours in the hope the system would would resurrection by itself, I issued an flood-ping to this machine and voila, after gett...

...IE Error 10 occurred at disk power-on lifetime: 1248 hours (52 days + 0 hours) When the command that caused the error occurred, the device was active or idle. After command completion occurred, registers were: ER ST SC SN CL CH DH -- -- -- -- -- -- -- 84 51 00 65 69 db e1 Error: ICRC, ABRT at LBA = 0x01db6965 = 31156581 Commands leading to the command that caused the error were: CR FR SC SN CL CH DH DC Powered_Up_Time Command/Feature_Name -- -- -- -- -- -- -- -- ---------------- -------------------- c8 00 10 65 69 db e1 00 00:37:33.571 READ DMA c8 00...

...******************* 67 2012-12-17 17:04 48 ***************************** SCT Error Recovery Control command not supported Device Statistics (GP Log 0x04) not supported SATA Phy Event Counters (GP Log 0x11) ID Size Value Description 0x0001 2 1 Command failed due to ICRC error 0x0002 2 1 R_ERR response for data FIS 0x0003 2 0 R_ERR response for device-to-host data FIS 0x0004 2 1 R_ERR response for host-to-device data FIS 0x0005 2 0 R_ERR response for non-data FIS 0x0006 2 0 R_ERR response for device-t...

After having massive problems with a supermicro X7DBE box using AOC-SAT2-MV8 Marvell controllers and opensolaris snv79 (same as described here: http://sunsolve.sun.com/search/document.do?assetkey=1-66-233341-1) we just start over using new hardware and opensolaris 2008.05 upgraded to snv94. We used again a supermicro X7DBE but now with two LSI SAS3081E SAS controllers. And guess what? Now we get

Hi... I really hope that somebody can help me to brainstorm this problem. Please let me describe my enviornment. Environment --------------- Fedora 16 x86_64(fully up-to-date) Wine 1.5.1 32bit and noarch binaries only Nvidia GPU - GTS 450 Nvidia Driver - 295.40 (including 32bit libraries) I've installed Perfectworld International under wine. Everything was running fine until the most recent

...7 Arktur kernel: ata5.00: cmd 35/00:00:00:62:50/00:04:5e:00:00/e0 tag 0 dma 524288 out May 7 07:12:07 Arktur kernel: res d8/d8:d8:d8:d8:d8/d8:d8:d8:d8:d8/d8 Emask 0x12 (ATA bus error) May 7 07:12:07 Arktur kernel: ata5.00: status: { Busy } May 7 07:12:07 Arktur kernel: ata5.00: error: { ICRC UNC IDNF } May 7 07:12:07 Arktur kernel: ata5: hard resetting link May 7 07:12:13 Arktur kernel: ata5: link is slow to respond, please be patient (ready=-19) May 7 07:12:15 Arktur kernel: ata5: SATA link up 1.5 Gbps (SStatus 113 SControl 310) May 7 07:12:15 Arktur kernel: ata5.00: failed to IDE...