Error 22 again...

[EvanVanVan]

2.5 weeks less than a year ago I received an error 22 (https://forums.freenas.org/index.php?threads/error-22-failing-drive.42292/), and the same thing just happened again last night to the same drive.

Code:

freenas.local kernel log messages:
> (da4:mps0:0:4:0): WRITE(10). CDB: 2a 00 57 86 48 28 00 00 08 00
> (da4:mps0:0:4:0): CAM status: SCSI Status Error
> (da4:mps0:0:4:0): SCSI status: Check Condition
> (da4:mps0:0:4:0): SCSI sense: ILLEGAL REQUEST asc:21,0 (Logical block address out of range)
> (da4:mps0:0:4:0): Info: 0x57864828
> (da4:mps0:0:4:0): Error 22, Unretryable error

I ran through the Hard Drive Troubleshooting Guide (https://forums.freenas.org/index.php?resources/hard-drive-troubleshooting-guide.17/) and nothing appears wrong with the drive. Last time I ended up replacing the LSI breakout cable. Any suggestions on the next step, should I RMA the drive? Ignore the error and hope it doesn't come back? Googling, it seems that typically when an error 22 occurs, it happens over and over and there's clearly something wrong with the drive. Both times this error has occurred singularly, and everything else keeps working like normal.

Thanks

 

[Robert Trevellyan]

Sometimes FreeNAS will send you the same report a year later, because somewhere along the way, the year is not recorded.

 

[JackShine]

IBM ServeRAID M1015 run really hot, maybe install an extra fan. If u thinking the HDD is at fault, check cables. If all is good replace and resilver.

Chuck the suspect drive in a Windows PC and run WDdiag.

If it doesn’t pass, RMA.

 

[EvanVanVan]

Thanks for the replies, been busy/forgot to reply to Robert and then never saw your reply, JackShine due to the fittings notification system.

@Robert Trevellyan: Lol your comment was just short enough and to the point I can't tell if your getting serious or mocking me for even mentioning the fact the same error occurred about a year ago. But you're right I do seem to remember other problems that I got emails for 2 years in a row.

@JackShine: Thanks for the tip about temperatures... I'll check where the drive is in relation to the m1015 card and see what I can do about an extra fan. In an attempt to keep cat hair and dust out of the box I have a couple of very fine fan screens in front of each fan, every so often (usually in the summer) I fail to clean them often enough and will get an email about my HDDs reaching 40 degrees.

Like I said I replaced the cables the last time and even then didn't think the was anything seeing with them, so maybe I'll try running then through windows diagnostics. Oh, and you're saying just replace it with a new drive and then check into the one with the error. Not a bad idea to keep an extra drive on hand. I'll consider buying one.

Thanks

 

[Robert Trevellyan]

I can't tell if your getting serious

I'm serious. People have reported receiving a security alert, then the same alert one calendar year later. I forget the exact nature of the bug.

 

[EvanVanVan]

Lol thank you that's what I assumed, was just looking for confirmation.