pyrater

dead now? it appears to be broken

Sigh ty johnnie

ty johnnie!! 1st run Dec 27 10:38:51 Icarus kernel: md: recovery thread: PQ incorrect, sector=1052783344 Dec 27 11:50:08 Icarus kernel: md: recovery thread: PQ incorrect, sector=1892951888 Dec 27 13:43:28 Icarus kernel: md: recovery thread: PQ incorrect, sector=3281396688 Dec 27 14:08:09 Icarus kernel: md: recovery thread: PQ incorrect, sector=3579856648 Dec 27 15:56:14 Icarus kernel: md: recovery thread: PQ incorrect, sector=4879602128 Stopped at 39.7% 2nd run (with corrections on) Dec 27 20:25:38 Icarus kernel: md: recovery thread: PQ corrected,

Dec 27 10:38:51 Icarus kernel: md: recovery thread: PQ incorrect, sector=1052783344 Dec 27 11:50:08 Icarus kernel: md: recovery thread: PQ incorrect, sector=1892951888 Dec 27 13:43:28 Icarus kernel: md: recovery thread: PQ incorrect, sector=3281396688 Dec 27 14:08:09 Icarus kernel: md: recovery thread: PQ incorrect, sector=3579856648 Dec 27 15:56:14 Icarus kernel: md: recovery thread: PQ incorrect, sector=4879602128 Stopped at 39.7% Rerunning parity check to see if it detects the same sectors... IF so my guess is that sector is truly off somehow... if it gives n

I assume since the drives are not throwing errors (UDMA CRC error count etc) that its ok?

I added a controller card (2 port). and ran a (non correcting )parity check without writing corrections to confirm new hardware is ok. I have so far got 3 errors on the sync but not the drives. is this normal or a problem? I also removed one of the cache drives from the cache pool so you may see that in the logs. Dec 27 11:50:08 Icarus kernel: md: recovery thread: PQ incorrect, sector=1892951888 Dec 27 13:43:28 Icarus kernel: md: recovery thread: PQ incorrect, sector=3281396688 Total size:8 TB Elapsed time:4 hours, 47 minutes Current position:1.77 TB (22.1 %

was there ever any resolution on getting ARMA3 to run with mods from steam?

I am putting the old card back in which requires me to remove my p2200 But at this point i must rebuild 2 disks before i start losing data sooo

i swapped the cables and its following the controller. I used a different cable and port on the same controller card.

swapped out Cable and connected to new Controller. Nov 2 21:59:20 Icarus kernel: ata8.00: exception Emask 0x10 SAct 0x0 SErr 0x400000 action 0x6 frozen Nov 2 21:59:20 Icarus kernel: ata8.00: irq_stat 0x08000000, interface fatal error Nov 2 21:59:20 Icarus kernel: ata8: SError: { Handshk } Nov 2 21:59:20 Icarus kernel: ata8.00: failed command: WRITE DMA EXT Nov 2 21:59:20 Icarus kernel: ata8.00: cmd 35/00:28:40:38:08/00:02:00:00:00/e0 tag 0 dma 282624 out Nov 2 21:59:20 Icarus kernel: res 50/00:00:3f:38:08/00:00:00:00:00/40 Emask 0x10 (ATA bus error) Nov 2 21:59:20 Icaru

Nov 2 21:31:10 Icarus kernel: scsi_io_completion_action: 25 callbacks suppressed Nov 2 21:31:10 Icarus kernel: sd 7:0:0:0: [sdo] tag#22 UNKNOWN(0x2003) Result: hostbyte=0x04 driverbyte=0x00 Nov 2 21:31:10 Icarus kernel: sd 7:0:0:0: [sdo] tag#22 CDB: opcode=0x85 85 06 20 00 00 00 00 00 00 00 00 00 00 40 e5 00 Nov 2 21:31:10 Icarus kernel: sd 7:0:0:0: [sdo] tag#24 UNKNOWN(0x2003) Result: hostbyte=0x04 driverbyte=0x00 Nov 2 21:31:10 Icarus kernel: sd 7:0:0:0: [sdo] tag#24 CDB: opcode=0x85 85 06 20 00 00 00 00 00 00 00 00 00 00 40 98 00 Nov 2 21:31:10 Icarus kernel: sd 7:0:0:0: [sdo] tag

Note: the hdd that is now complaining was not plugged into the new drives, though i did swap some cables around when i installed the new cards due to length of the cables...

Installed new cards, got 1 HDD disabled.. bad card or loose cable? (new cards are the https://www.amazon.com/gp/product/B07M942LN9/ref=ppx_yo_dt_b_asin_title_o03_s00?ie=UTF8&psc=1 ) chip is ASM1061 icarus-diagnostics-20201102-2100.zip

ok changed order to 2 2 port ASM1061 cards. Thank you for all the help !!

ok gonna give the ZYT-SA3004 a try https://www.amazon.com/dp/B07S7D7DDG/ref=emc_b_5_t