A little help please for a NOOB;
I have recently got my NAS up and running. Filled one of my ZFS pools, and am starting to load up another one.
With dumping information onto the next Pool, I've been getting errors from the security run output. This is what it's telling me;
What I can tell from this is that drive da12 is having some kind of error, but what kind, I have no idea. Can someone else help me with identifying this error and what it might mean? I know that it exists on the second Pool, which I have recently started to write/dump files to.
I have searched the forums, and I did find this post, and it seems to be very relevant. I have 24, 3.0TB Seagate drives.....but only drive da12 seems to be giving me any grief. All the other 23 seem fine so far (I haven't touched the 3rd ZFS Pool yet, so am not totally sure that statement is true, but I did test the drives for 2 weeks each before inserting into the server, and they all passed all tests). And in my pools, I have hot swap drives, so should anything happen to the da12 drive, I should be OK.....
But the above post also mentions a faulty backplane, which I have had before on another Norco RPC-4220 case (this case is a Norco RPC-4224).....but I'm not going to order a new one until I now if my 3rd pool is fully functioning in case I need more than one backplane. Tonight I'll start transfering files to the 3rd pool to see if I get any similar errors on it.
Is there a way to spin up the da12 drive so that it shows it's activity light so that I can identify it in the case? I do have spares in case I need to swap it out. That would also help me identify if its actually the drive that is faulty or if it's the backplane, swapping it out.
I have recently got my NAS up and running. Filled one of my ZFS pools, and am starting to load up another one.
With dumping information onto the next Pool, I've been getting errors from the security run output. This is what it's telling me;
Code:
+++ /tmp/security.GlB5bLOs 2013-08-01 03:01:00.000000000 -0600 +(da12:mps1:0:4:0): READ(10). CDB: 28 0 c9 29 ed c8 0 0 8 0 +(da12:mps1:0:4:0): CAM status: SCSI Status Error +(da12:mps1:0:4:0): SCSI status: Check Condition +(da12:mps1:0:4:0): SCSI sense: ABORTED COMMAND asc:47,3 (Information unit iuCRC error detected) +(da12:mps1:0:4:0): READ(10). CDB: 28 0 2 7a fb 58 0 0 8 0 +(da12:mps1:0:4:0): CAM status: SCSI Status Error +(da12:mps1:0:4:0): SCSI status: Check Condition +(da12:mps1:0:4:0): SCSI sense: ABORTED COMMAND asc:47,3 (Information unit iuCRC error detected)
What I can tell from this is that drive da12 is having some kind of error, but what kind, I have no idea. Can someone else help me with identifying this error and what it might mean? I know that it exists on the second Pool, which I have recently started to write/dump files to.
I have searched the forums, and I did find this post, and it seems to be very relevant. I have 24, 3.0TB Seagate drives.....but only drive da12 seems to be giving me any grief. All the other 23 seem fine so far (I haven't touched the 3rd ZFS Pool yet, so am not totally sure that statement is true, but I did test the drives for 2 weeks each before inserting into the server, and they all passed all tests). And in my pools, I have hot swap drives, so should anything happen to the da12 drive, I should be OK.....
But the above post also mentions a faulty backplane, which I have had before on another Norco RPC-4220 case (this case is a Norco RPC-4224).....but I'm not going to order a new one until I now if my 3rd pool is fully functioning in case I need more than one backplane. Tonight I'll start transfering files to the 3rd pool to see if I get any similar errors on it.
Is there a way to spin up the da12 drive so that it shows it's activity light so that I can identify it in the case? I do have spares in case I need to swap it out. That would also help me identify if its actually the drive that is faulty or if it's the backplane, swapping it out.