Short version: I have a brand new Seagate Ironwolf SSD throwing read errors and generally haulting my system. Trying to determine if the brand new drive is DOA, or if there's something lingering from my old drive.
Long version: My jails SSD was starting to have read errors, so I purchased a new SSD and tried to resilver. Resilver could never complete and went into a loop. I manually copied data onto another drive, then pulled the failing drive from the hot bay. After that, the new SSD was readable, but gave many Cam status errors, and the entire system got really laggy. I thought it might be a remnant of the removed drive, so I deleted the pool, and used the new SSD to create a new pool with a new name. The errors continued. I'm still within 30 days, so could send it back. I'm just wondering if there's something about the way that I removed the old drive before it had fully resilvered that could be stuck in that same loop - but without a drive to read from. I have moved the SSD to a different SATA port - no change. Thoughts? Tests to perform?
Code:
Oct 16 23:48:23 FreeNAS ahcich2: is 00000000 cs 00000010 ss 00000010 rs 00000010 tfd 441 serr 00000000 cmd 00044317 Oct 16 23:48:23 FreeNAS (ada2:ahcich2:0:0:0): SEND_FPDMA_QUEUED DATA SET MANAGEMENT. ACB: 64 01 00 00 00 40 00 00 00 00 00 00 Oct 16 23:48:23 FreeNAS (ada2:ahcich2:0:0:0): CAM status: Command timeout Oct 16 23:48:23 FreeNAS (ada2:ahcich2:0:0:0): Retrying command Oct 16 23:48:53 FreeNAS ahcich2: Timeout on slot 12 port 0 Oct 16 23:48:53 FreeNAS ahcich2: is 00000000 cs 00001000 ss 00000000 rs 00001000 tfd 441 serr 00000000 cmd 00044b17 Oct 16 23:48:53 FreeNAS (ada2:ahcich2:0:0:0): WRITE_DMA. ACB: ca 00 90 56 99 42 00 00 00 00 08 00 Oct 16 23:48:53 FreeNAS (ada2:ahcich2:0:0:0): CAM status: Command timeout Oct 16 23:48:53 FreeNAS (ada2:ahcich2:0:0:0): Retrying command Oct 16 23:49:54 FreeNAS ahcich2: Timeout on slot 25 port 0
Long version: My jails SSD was starting to have read errors, so I purchased a new SSD and tried to resilver. Resilver could never complete and went into a loop. I manually copied data onto another drive, then pulled the failing drive from the hot bay. After that, the new SSD was readable, but gave many Cam status errors, and the entire system got really laggy. I thought it might be a remnant of the removed drive, so I deleted the pool, and used the new SSD to create a new pool with a new name. The errors continued. I'm still within 30 days, so could send it back. I'm just wondering if there's something about the way that I removed the old drive before it had fully resilvered that could be stuck in that same loop - but without a drive to read from. I have moved the SSD to a different SATA port - no change. Thoughts? Tests to perform?
