-
Important Announcement for the TrueNAS Community.
The TrueNAS Community has now been moved. This forum has become READ-ONLY for historical purposes. Please feel free to join us on the new TrueNAS Community Forums
SOLVED Various SCSI sense errors during scrubbing
- Thread starter tobiasbp
- Start date
- Status
I still get errors when running of off the new motherboard.
The thing is, that now, the errors still occur on the same twos disks (da0 & da6). Looking at my notes, I can see, that the errors used to occur on random disks.
I'm now thinking, the problem could be with some slots on the backplane(s).
I will now move da0 & da6 to new slots and scrub again.
The thing is, that now, the errors still occur on the same twos disks (da0 & da6). Looking at my notes, I can see, that the errors used to occur on random disks.
I'm now thinking, the problem could be with some slots on the backplane(s).
I will now move da0 & da6 to new slots and scrub again.
Code:
... ... (da6:mps0:0:17:0): READ(10). CDB: 28 00 a4 40 25 68 00 00 b0 00 length 90112 SMID 1017 terminated ioc 804b scsi 0 state 0 xfer 0 (da6:mps0:0:17:0): READ(10). CDB: 28 00 a4 40 25 68 00 00 b0 00 (da6:mps0:0:17:0): CAM status: CCB request completed with an error (da6:mps0:0:17:0): Retrying command (da6:mps0:0:17:0): READ(10). CDB: 28 00 a4 40 24 a8 00 00 c0 00 (da6:mps0:0:17:0): CAM status: SCSI Status Error (da6:mps0:0:17:0): SCSI status: Check Condition (da6:mps0:0:17:0): SCSI sense: MEDIUM ERROR asc:11,0 (Unrecovered read error) (da6:mps0:0:17:0): Info: 0xa44024a8 (da6:mps0:0:17:0): Error 5, Unretryable error ... ... (da0:mps0:0:9:0): READ(10). CDB: 28 00 ac 39 98 e8 00 00 d8 00 length 110592 SMID 851 terminated ioc 804b scsi 0 state 0 xfer 0 (da0:mps0:0:9:0): READ(10). CDB: 28 00 a8 6a 7e 88 00 00 08 00 length 4096 SMID 204 terminated ioc 804b scsi 0 state 0 xfer 0(da0:mps0:0:9:0): READ(10). CDB: 28 00 ac 39 98 e8 00 00 d8 00 (da0:mps0:0:9:0): CAM status: CCB request completed with an error (da0:mps0:0:9:0): READ(10). CDB: 28 00 a8 6c 5e f0 00 00 08 00 length 4096 SMID 678 terminated ioc 804b scsi 0 state 0 xfer 0(da0: mps0:0:9:0): Retrying command (da0:mps0:0:9:0): READ(10). CDB: 28 00 a8 6a 7e 88 00 00 08 00 (da0:mps0:0:9:0): CAM status: CCB request completed with an error (da0:mps0:0:9:0): Retrying command (da0:mps0:0:9:0): READ(10). CDB: 28 00 a8 6c 5e f0 00 00 08 00 (da0:mps0:0:9:0): CAM status: CCB request completed with an error (da0:mps0:0:9:0): Retrying command (da0:mps0:0:9:0): READ(10). CDB: 28 00 ac 39 98 10 00 00 d8 00 (da0:mps0:0:9:0): CAM status: SCSI Status Error (da0:mps0:0:9:0): SCSI status: Check Condition (da0:mps0:0:9:0): SCSI sense: MEDIUM ERROR asc:11,0 (Unrecovered read error) (da0:mps0:0:9:0): Info: 0xac399810 (da0:mps0:0:9:0): Error 5, Unretryable error ... ...
The errors occur at "all" slots in the backplanes. There seems to be no bad slots.
I have reseated all power connections and moved the HBA (ServeRAID) to a different slot.
Now, I get a LOT of errors on alot of disk right when I begin my scrub. But now, they are a "type" I have not seen before (Information unit iuCRC error detected):
I have reseated all power connections and moved the HBA (ServeRAID) to a different slot.
Now, I get a LOT of errors on alot of disk right when I begin my scrub. But now, they are a "type" I have not seen before (Information unit iuCRC error detected):
Code:
... ... Jul 27 15:27:41 ultraman (da4:mps0:0:15:0): READ(10). CDB: 28 00 42 eb 33 a0 00 01 00 00 length 131072 SMID 125 terminated ioc 804b scsi 0 state 0 xfer 0 Jul 27 15:27:41 ultraman (da4:mps0:0:15:0): READ(10). CDB: 28 00 42 eb 33 a0 00 01 00 00 Jul 27 15:27:41 ultraman (da4:mps0:0:15:0): CAM status: CCB request completed with an error Jul 27 15:27:41 ultraman (da4:mps0:0:15:0): Retrying command Jul 27 15:27:41 ultraman (da4:mps0:0:15:0): READ(10). CDB: 28 00 42 eb 34 a0 00 00 60 00 Jul 27 15:27:41 ultraman (da4:mps0:0:15:0): CAM status: SCSI Status Error Jul 27 15:27:41 ultraman (da4:mps0:0:15:0): SCSI status: Check Condition Jul 27 15:27:41 ultraman (da4:mps0:0:15:0): SCSI sense: ABORTED COMMAND asc:47,3 (Information unit iuCRC error detected) Jul 27 15:27:41 ultraman (da4:mps0:0:15:0): Retrying command (per sense data) ... ...
I have reseated the disk cables on the HBA. The iuCRC error errors appear to have gone.
I still get SCSI errors after having reseated all power cables (I could find).
Two of my disks are way more likely to have errors happen on them (As I have noticed before). Surely, that can not be coincidence? I will remove the disks (currently) called da0 & da6, and replace them with other disks.
Trying to quantify it, I use grep to get all lines relating to a SCSI error from dmesg, and see how many times each drive has been mentioned. As shown below, da0 & da6 have way more mentions than other disks. I'm guessing, each error results in 9 mentions. That puts da0 at 270/9 = 30 errors and da6 at 342/9 = 38 errors.
In other news: I have ordered a replacement power distribution unit for the machine.
Two of my disks are way more likely to have errors happen on them (As I have noticed before). Surely, that can not be coincidence? I will remove the disks (currently) called da0 & da6, and replace them with other disks.
Trying to quantify it, I use grep to get all lines relating to a SCSI error from dmesg, and see how many times each drive has been mentioned. As shown below, da0 & da6 have way more mentions than other disks. I'm guessing, each error results in 9 mentions. That puts da0 at 270/9 = 30 errors and da6 at 342/9 = 38 errors.
Code:
dmesg | grep -E "^\(da[0-9]+" -o | sort | uniq -c 270 (da0 9 (da11 9 (da12 9 (da13 18 (da17 9 (da18 9 (da20 18 (da21 9 (da23 342 (da6
In other news: I have ordered a replacement power distribution unit for the machine.
I can only speak for myself, but i think i understand what fixed the issue for me.
Before I went on vacation I replaced the SAS->SATA cable hoping I fixed the issue. With me not home for 2 weeks and a server without errors I thought that was the problem.
But when i arrived home within days the errors started coming back....
But after a few more weeks with during daytime (trying) to check the console every hour to see when the error arrived I started to see a pattern.
When I am working behind my PC I changed the fanspeed of the server to medium instead of high (the server is like 3 feet next to me).
So almost everytime I was working for a longer period of time behind my pc I recieved an SCSi error.
Right now i keep the the Fanspeed at high and i am allready error free for ~3+ weeks.
I can't speak for your situation.
But in my case I have the feeling it was an heat issue..
Before I went on vacation I replaced the SAS->SATA cable hoping I fixed the issue. With me not home for 2 weeks and a server without errors I thought that was the problem.
But when i arrived home within days the errors started coming back....
But after a few more weeks with during daytime (trying) to check the console every hour to see when the error arrived I started to see a pattern.
When I am working behind my PC I changed the fanspeed of the server to medium instead of high (the server is like 3 feet next to me).
So almost everytime I was working for a longer period of time behind my pc I recieved an SCSi error.
Right now i keep the the Fanspeed at high and i am allready error free for ~3+ weeks.
I can't speak for your situation.
But in my case I have the feeling it was an heat issue..
Have you logged the temperature of your disks? Running "smartctl -a /dev/daX" should tell you.
If you did, maybe you could tell what impact your fans have on drive temperature.
No I don't have the temperature logged.
But I think it is the SAS controller (HBA, onboard on my X11SSL-cf mobo) which was to hot.
Even now it feels hotter compared to my chipset heatsinks (the heatsinks are the same) but HBA's are somehow known to run quite hot...
I dont have a Heatgun to see how hot the heatsink actually is...
I can try and run a command on it to see how high the temperature is (if someone knows the right command)
:)
*EDIT*
I know for sure that the drives are running under 40 degrees C.
I have a mailnotification set up when they run hotter than that.
Last edited:
Last time, i replaced two disks, which had a lot more errors than others. I replaced them with different disks. Now the two new disks are the ones with the most errors. That's really odd (I think). Earlier, I have moved disks around, and the problems do not appear to be tied to specific slots in the backplane.
The two new disks are da0 & da4. This the the number of mentions of disk errors pr. disk from dmesg:
I am replacing da0 with a new disk. The new one is WD Gold. Old was WD Red.
Will the new disk inherit the trait of having much more SCSI errors than other disks? I'll report back.
The two new disks are da0 & da4. This the the number of mentions of disk errors pr. disk from dmesg:
Code:
dmesg | grep -E "^\(da[0-9]+" -o | sort | uniq -c 157 (da0 9 (da11 9 (da12 9 (da13 13 (da18 6 (da20 67 (da4
I am replacing da0 with a new disk. The new one is WD Gold. Old was WD Red.
Will the new disk inherit the trait of having much more SCSI errors than other disks? I'll report back.
Still getting errors. 14% into the scrub 
. I need to look in to the firmware on the backplanes.
From /var/log/messages:
Pool status:
SMART data from da3 (The disk with errors):
. I need to look in to the firmware on the backplanes.From /var/log/messages:
Code:
... ... Aug 21 12:38:18 ultraman (da3:mps0:0:14:0): READ(10). CDB: 28 00 78 39 af a8 00 00 a8 00 length 86016 SMID 711 terminated ioc 804b scsi 0 state 0 xfer 0 Aug 21 12:38:18 ultraman (da3:mps0:0:14:0): READ(10). CDB: 28 00 78 39 af a8 00 00 a8 00 Aug 21 12:38:18 ultraman (da3:mps0:0:14:0): CAM status: CCB request completed with an error Aug 21 12:38:18 ultraman (da3:mps0:0:14:0): Retrying command Aug 21 12:38:18 ultraman (da3:mps0:0:14:0): READ(10). CDB: 28 00 78 39 af 00 00 00 a8 00 Aug 21 12:38:18 ultraman (da3:mps0:0:14:0): CAM status: SCSI Status Error Aug 21 12:38:18 ultraman (da3:mps0:0:14:0): SCSI status: Check Condition Aug 21 12:38:18 ultraman (da3:mps0:0:14:0): SCSI sense: MEDIUM ERROR asc:11,0 (Unrecovered read error) Aug 21 12:38:18 ultraman (da3:mps0:0:14:0): Info: 0x7839af00 Aug 21 12:38:18 ultraman (da3:mps0:0:14:0): Error 5, Unretryable error ... ... Aug 21 12:54:43 ultraman (da3:mps0:0:14:0): READ(10). CDB: 28 00 7c 21 08 f8 00 00 b8 00 length 94208 SMID 111 terminated ioc 804b scsi 0 state 0 xfer 0 Aug 21 12:54:43 ultraman (da3:mps0:0:14:0): READ(10). CDB: 28 00 7c 21 08 f8 00 00 b8 00 Aug 21 12:54:43 ultraman (da3:mps0:0:14:0): CAM status: CCB request completed with an error Aug 21 12:54:43 ultraman (da3:mps0:0:14:0): Retrying command Aug 21 12:54:43 ultraman (da3:mps0:0:14:0): READ(10). CDB: 28 00 7c 21 08 40 00 00 b8 00 Aug 21 12:54:43 ultraman (da3:mps0:0:14:0): CAM status: SCSI Status Error Aug 21 12:54:43 ultraman (da3:mps0:0:14:0): SCSI status: Check Condition Aug 21 12:54:43 ultraman (da3:mps0:0:14:0): SCSI sense: MEDIUM ERROR asc:11,0 (Unrecovered read error) Aug 21 12:54:43 ultraman (da3:mps0:0:14:0): Info: 0x7c210840 Aug 21 12:54:43 ultraman (da3:mps0:0:14:0): Error 5, Unretryable error ... ...
Pool status:
Code:
pool: ultraman state: ONLINE scan: scrub in progress since Mon Aug 21 10:50:43 2017 5.85T scanned out of 39.2T at 809M/s, 11h59m to go 176K repaired, 14.94% done config: NAME STATE READ WRITE CKSUM ultraman ONLINE 0 0 0 mirror-0 ONLINE 0 0 0 gptid/2e00ac23-183d-11e7-ae9d-0025901ef244 ONLINE 0 0 0 gptid/6e71919e-1618-11e7-a3b7-0025901ef244 ONLINE 0 0 0 mirror-1 ONLINE 0 0 0 gptid/6f22c98c-1618-11e7-a3b7-0025901ef244 ONLINE 0 0 0 gptid/6fe54bfe-1618-11e7-a3b7-0025901ef244 ONLINE 0 0 0 mirror-2 ONLINE 0 0 0 gptid/70bfd5c6-1618-11e7-a3b7-0025901ef244 ONLINE 0 0 0 gptid/424dc93e-7923-11e7-b91b-0cc47a5312f0 ONLINE 0 0 0 (repairing) mirror-3 ONLINE 0 0 0 gptid/7ad0f185-1619-11e7-a3b7-0025901ef244 ONLINE 0 0 0 gptid/9e899578-183c-11e7-ae9d-0025901ef244 ONLINE 0 0 0 mirror-4 ONLINE 0 0 0 gptid/427c2189-184c-11e7-ae9d-0025901ef244 ONLINE 0 0 0 gptid/4342a98c-184c-11e7-ae9d-0025901ef244 ONLINE 0 0 0 mirror-5 ONLINE 0 0 0 gptid/a1ab9a69-184c-11e7-ae9d-0025901ef244 ONLINE 0 0 0 gptid/a2851364-184c-11e7-ae9d-0025901ef244 ONLINE 0 0 0 mirror-6 ONLINE 0 0 0 gptid/0dcbcccd-184d-11e7-ae9d-0025901ef244 ONLINE 0 0 0 gptid/0e9ed582-184d-11e7-ae9d-0025901ef244 ONLINE 0 0 0 mirror-7 ONLINE 0 0 0 gptid/2b56cf1c-184d-11e7-ae9d-0025901ef244 ONLINE 0 0 0 gptid/2c2a1c62-184d-11e7-ae9d-0025901ef244 ONLINE 0 0 0 mirror-8 ONLINE 0 0 0 gptid/69718320-184d-11e7-ae9d-0025901ef244 ONLINE 0 0 0 gptid/6a4e6afa-184d-11e7-ae9d-0025901ef244 ONLINE 0 0 0 mirror-9 ONLINE 0 0 0 gptid/8fccb2c6-184d-11e7-ae9d-0025901ef244 ONLINE 0 0 0 gptid/90b48d70-184d-11e7-ae9d-0025901ef244 ONLINE 0 0 0 mirror-10 ONLINE 0 0 0 gptid/aeda4f88-184d-11e7-ae9d-0025901ef244 ONLINE 0 0 0 gptid/afb5bfc3-184d-11e7-ae9d-0025901ef244 ONLINE 0 0 0 mirror-11 ONLINE 0 0 0 gptid/bca6e4f0-1b71-11e7-ae9d-0025901ef244 ONLINE 0 0 0 gptid/d06f5f86-7b79-11e7-b91b-0cc47a5312f0 ONLINE 0 0 0 errors: No known data errors
SMART data from da3 (The disk with errors):
Code:
SMART Attributes Data Structure revision number: 16 Vendor Specific SMART Attributes with Thresholds: ID# ATTRIBUTE_NAME FLAG VALUE WORST THRESH TYPE UPDATED WHEN_FAILED RAW_VALUE 1 Raw_Read_Error_Rate 0x002f 200 200 051 Pre-fail Always - 0 3 Spin_Up_Time 0x0027 205 204 021 Pre-fail Always - 8708 4 Start_Stop_Count 0x0032 100 100 000 Old_age Always - 15 5 Reallocated_Sector_Ct 0x0033 200 200 140 Pre-fail Always - 0 7 Seek_Error_Rate 0x002e 100 253 000 Old_age Always - 0 9 Power_On_Hours 0x0032 099 099 000 Old_age Always - 975 10 Spin_Retry_Count 0x0032 100 253 000 Old_age Always - 0 11 Calibration_Retry_Count 0x0032 100 253 000 Old_age Always - 0 12 Power_Cycle_Count 0x0032 100 100 000 Old_age Always - 15 192 Power-Off_Retract_Count 0x0032 200 200 000 Old_age Always - 13 193 Load_Cycle_Count 0x0032 200 200 000 Old_age Always - 22 194 Temperature_Celsius 0x0022 110 107 000 Old_age Always - 42 196 Reallocated_Event_Count 0x0032 200 200 000 Old_age Always - 0 197 Current_Pending_Sector 0x0032 200 200 000 Old_age Always - 0 198 Offline_Uncorrectable 0x0030 100 253 000 Old_age Offline - 0 199 UDMA_CRC_Error_Count 0x0032 200 200 000 Old_age Always - 0 200 Multi_Zone_Error_Rate 0x0008 200 200 000 Old_age Offline - 0
I finally took a look at the firmware on my two backplanes (SAS2-826EL1 & SAS2-846EL1).
Supermicro provide tools to flash the firmware here:
ftp://ftp.supermicro.com/utility/ExpanderXtools_Lite/
Windows and Linux versions are available. I prefer Linux, so I download the 64 bit Linux version:
SMC ExpanderXtoolsLite v1.5_Linux64.zip
The only file I need from the zip file is the binary xflash.
I boot my server from a Debian 8 install USB stick. I enter rescue mode and enter a shell.
I copy the xflash binary to different USB stick. I mount it using the Debian shell.
Let's find the SAS addresses of my backplanes:
Let's see what firmware is on the backplanes:
Some time spent Googling, seems to indicate that the latest version of the firmware is called 55.14.18.0. Apparently, the FW is not freely available from Supermicro (?!). The way to get it, seems to be to download it from some unknown FTP site! Well, I'm desperate, so I do it even though I do not like it.
ftp://211.214.88.34/bios/BP_FW/FW_55.14.18.0.zip
In the zip file, the firmware is in the file sas2xfw_55.14.18.0.fw.
Let's flash the firmware to the backplane(s). The SAS address must be entered with out the colon in the middle, hence:
Looks good (Screendump). It worked!
To make sure, I reboot the machine back in to Linux, and check firmware on both backplanes with the command xflash -i <SAS_ADDRESS> get ver (This returns the active firmware as fas as I understand). The firmware on both backplanes is reported as 55.14.18.0.
I boot up FreeNAS again and start to scrub the pool.
Within a few minutes, I get a SCSI error!!
So it is still not fixed! I have now installed:
I'm now considering trashing the whole machine. I have no more things left to try.
Supermicro provide tools to flash the firmware here:
ftp://ftp.supermicro.com/utility/ExpanderXtools_Lite/
Windows and Linux versions are available. I prefer Linux, so I download the 64 bit Linux version:
SMC ExpanderXtoolsLite v1.5_Linux64.zip
The only file I need from the zip file is the binary xflash.
I boot my server from a Debian 8 install USB stick. I enter rescue mode and enter a shell.
I copy the xflash binary to different USB stick. I mount it using the Debian shell.
Let's find the SAS addresses of my backplanes:
xflash -i get avail
********************************************************************************
Xflash
LSI SAS Expander Flash Utility
Version: 7.0.0.0
Copyright (c) 2010 LSI Corporation. All rights reserved.
********************************************************************************
Initializing Interface.
Expander: SAS2x28
1) SAS2x28 (50030480:0157F6FF) (0.0.0.0)
2) SAS2x36 (50030480:0120CDFF) (0.0.0.0)
Let's see what firmware is on the backplanes:
xflash -i 500304800120CDFF get ver
********************************************************************************
Xflash
LSI SAS Expander Flash Utility
Version: 7.0.0.0
Copyright (c) 2010 LSI Corporation. All rights reserved.
********************************************************************************
Initializing Interface.
Expander: SAS2x36
Firmware Region Version: 55.07.23.00
Some time spent Googling, seems to indicate that the latest version of the firmware is called 55.14.18.0. Apparently, the FW is not freely available from Supermicro (?!). The way to get it, seems to be to download it from some unknown FTP site! Well, I'm desperate, so I do it even though I do not like it.
ftp://211.214.88.34/bios/BP_FW/FW_55.14.18.0.zip
In the zip file, the firmware is in the file sas2xfw_55.14.18.0.fw.
Let's flash the firmware to the backplane(s). The SAS address must be entered with out the colon in the middle, hence:
Looks good (Screendump). It worked!
To make sure, I reboot the machine back in to Linux, and check firmware on both backplanes with the command xflash -i <SAS_ADDRESS> get ver (This returns the active firmware as fas as I understand). The firmware on both backplanes is reported as 55.14.18.0.
I boot up FreeNAS again and start to scrub the pool.
Within a few minutes, I get a SCSI error!!
Code:
(da3:mps0:0:14:0): READ(10). CDB: 28 00 4b e9 b8 30 00 01 00 00 length 131072 SMID 493 terminated ioc 804b scsi 0 state 0 xfer 0 (da3:mps0:0:14:0): READ(10). CDB: 28 00 4b e9 b8 30 00 01 00 00 (da3:mps0:0:14:0): CAM status: CCB request completed with an error (da3:mps0:0:14:0): Retrying command (da3:mps0:0:14:0): READ(10). CDB: 28 00 4b e9 b7 50 00 00 e0 00 (da3:mps0:0:14:0): CAM status: SCSI Status Error (da3:mps0:0:14:0): SCSI status: Check Condition (da3:mps0:0:14:0): SCSI sense: MEDIUM ERROR asc:11,0 (Unrecovered read error) (da3:mps0:0:14:0): Info: 0x4be9b750 (da3:mps0:0:14:0): Error 5, Unretryable error
So it is still not fixed! I have now installed:
- Two new power supplies.
- Two new SAS cables between HBA and backplanes.
- A new Power Distribution Unit
- New firmware on both backplanes
- New motherboard
I'm now considering trashing the whole machine. I have no more things left to try.
- Joined
- Feb 15, 2014
- Messages
- 20,194
This is beyond weird. Is the behavior the same on a different OS?
At this point, the only thing left are the drives, but everyone and their mother uses WD Reds. Plenty of 6TB models in the mix, too.
Now that I think about it, could there be something intermittently shorting out something on the backplane? What's the output of
At this point, the only thing left are the drives, but everyone and their mother uses WD Reds. Plenty of 6TB models in the mix, too.
Now that I think about it, could there be something intermittently shorting out something on the backplane? What's the output of
smartctl -x /dev/daX, for a representative drive or two?Let's see the number of "SCSI Status Error"s in dmesg after 3 scrubs during the weekend:
Most errors occur on /dev/da3. This was also the case before updating the firmware on the backplanes.
In fact, the disks reported are mostly the same as before upgrading the backplane firmware, as seen here:
Here is an example of an error on /dev/da3:
As suggested, Let's see what smartctl has to say about /dev/da3 (The drive with the most errors logged).
Code:
[root@ultraman] ~# dmesg | grep -i scsi\ status\ error | sort | uniq -c 1 (da10:mps0:0:22:0): CAM status: SCSI Status Error 1 (da11:mps0:0:23:0): CAM status: SCSI Status Error 1 (da12:mps0:0:24:0): CAM status: SCSI Status Error 1 (da16:mps0:0:28:0): CAM status: SCSI Status Error 1 (da17:mps0:0:29:0): CAM status: SCSI Status Error 1 (da19:mps0:0:31:0): CAM status: SCSI Status Error 1 (da20:mps0:0:32:0): CAM status: SCSI Status Error 1 (da22:mps0:0:34:0): CAM status: SCSI Status Error 9 (da3:mps0:0:14:0): CAM status: SCSI Status Error 1 (da7:mps0:0:19:0): CAM status: SCSI Status Error
Most errors occur on /dev/da3. This was also the case before updating the firmware on the backplanes.
In fact, the disks reported are mostly the same as before upgrading the backplane firmware, as seen here:
Code:
[root@ultraman] ~# dmesg | grep -i scsi\ status\ error | sort | uniq -c 1 (da10:mps0:0:22:0): CAM status: SCSI Status Error 1 (da11:mps0:0:23:0): CAM status: SCSI Status Error 1 (da12:mps0:0:24:0): CAM status: SCSI Status Error 1 (da16:mps0:0:28:0): CAM status: SCSI Status Error 1 (da17:mps0:0:29:0): CAM status: SCSI Status Error 1 (da19:mps0:0:31:0): CAM status: SCSI Status Error 1 (da20:mps0:0:32:0): CAM status: SCSI Status Error 19 (da3:mps0:0:14:0): CAM status: SCSI Status Error 1 (da7:mps0:0:19:0): CAM status: SCSI Status Error 1 (da9:mps0:0:21:0): CAM status: SCSI Status Error
Here is an example of an error on /dev/da3:
Code:
(da3:mps0:0:14:0): READ(16). CDB: 88 00 00 00 00 01 7b 45 17 b0 00 00 00 c8 00 00 length 102400 SMID 853 terminated ioc 804b scsi 0 state 0 xfer 0 (da3:mps0:0:14:0): READ(16). CDB: 88 00 00 00 00 01 7b 45 17 b0 00 00 00 c8 00 00 (da3:mps0:0:14:0): CAM status: CCB request completed with an error (da3:mps0:0:14:0): Retrying command (da3:mps0:0:14:0): READ(16). CDB: 88 00 00 00 00 01 7b 45 16 e8 00 00 00 c8 00 00 (da3:mps0:0:14:0): CAM status: SCSI Status Error (da3:mps0:0:14:0): SCSI status: Check Condition (da3:mps0:0:14:0): SCSI sense: MEDIUM ERROR asc:11,0 (Unrecovered read error) (da3:mps0:0:14:0): Info: 0x17b4516e8 (da3:mps0:0:14:0): Error 5, Unretryable error
As suggested, Let's see what smartctl has to say about /dev/da3 (The drive with the most errors logged).
Code:
[root@ultraman] ~# smartctl -x /dev/da3 smartctl 6.5 2016-05-07 r4318 [FreeBSD 10.3-STABLE amd64] (local build) Copyright (C) 2002-16, Bruce Allen, Christian Franke, www.smartmontools.org === START OF INFORMATION SECTION === Model Family: Western Digital Red Device Model: WDC WD60EFRX-68L0BN1 Serial Number: WD-WX11DC61YDPV LU WWN Device Id: 5 0014ee 263cb5ce4 Firmware Version: 82.00A82 User Capacity: 6,001,175,126,016 bytes [6.00 TB] Sector Sizes: 512 bytes logical, 4096 bytes physical Rotation Rate: 5700 rpm Device is: In smartctl database [for details use: -P show] ATA Version is: ACS-2, ACS-3 T13/2161-D revision 3b SATA Version is: SATA 3.1, 6.0 Gb/s (current: 6.0 Gb/s) Local Time is: Mon Aug 28 09:32:18 2017 CEST SMART support is: Available - device has SMART capability. SMART support is: Enabled AAM feature is: Unavailable APM feature is: Unavailable Rd look-ahead is: Enabled Write cache is: Enabled ATA Security is: Disabled, NOT FROZEN [SEC1] Wt Cache Reorder: Enabled === START OF READ SMART DATA SECTION === SMART overall-health self-assessment test result: PASSED General SMART Values: Offline data collection status: (0x00) Offline data collection activity was never started. Auto Offline Data Collection: Disabled. Self-test execution status: ( 0) The previous self-test routine completed without error or no self-test has ever been run. Total time to complete Offline data collection: ( 2384) seconds. Offline data collection capabilities: (0x7b) SMART execute Offline immediate. Auto Offline data collection on/off support. Suspend Offline collection upon new command. Offline surface scan supported. Self-test supported. Conveyance Self-test supported. Selective Self-test supported. SMART capabilities: (0x0003) Saves SMART data before entering power-saving mode. Supports SMART auto save timer. Error logging capability: (0x01) Error logging supported. General Purpose Logging supported. Short self-test routine recommended polling time: ( 2) minutes. Extended self-test routine recommended polling time: ( 678) minutes. Conveyance self-test routine recommended polling time: ( 5) minutes. SCT capabilities: (0x303d) SCT Status supported. SCT Error Recovery Control supported. SCT Feature Control supported. SCT Data Table supported. SMART Attributes Data Structure revision number: 16 Vendor Specific SMART Attributes with Thresholds: ID# ATTRIBUTE_NAME FLAGS VALUE WORST THRESH FAIL RAW_VALUE 1 Raw_Read_Error_Rate POSR-K 200 200 051 - 0 3 Spin_Up_Time POS--K 204 204 021 - 8775 4 Start_Stop_Count -O--CK 100 100 000 - 19 5 Reallocated_Sector_Ct PO--CK 200 200 140 - 0 7 Seek_Error_Rate -OSR-K 100 253 000 - 0 9 Power_On_Hours -O--CK 099 099 000 - 1138 10 Spin_Retry_Count -O--CK 100 253 000 - 0 11 Calibration_Retry_Count -O--CK 100 253 000 - 0 12 Power_Cycle_Count -O--CK 100 100 000 - 19 192 Power-Off_Retract_Count -O--CK 200 200 000 - 17 193 Load_Cycle_Count -O--CK 200 200 000 - 27 194 Temperature_Celsius -O---K 114 107 000 - 38 196 Reallocated_Event_Count -O--CK 200 200 000 - 0 197 Current_Pending_Sector -O--CK 200 200 000 - 0 198 Offline_Uncorrectable ----CK 100 253 000 - 0 199 UDMA_CRC_Error_Count -O--CK 200 200 000 - 0 200 Multi_Zone_Error_Rate ---R-- 200 200 000 - 0 ||||||_ K auto-keep |||||__ C event count ||||___ R error rate |||____ S speed/performance ||_____ O updated online |______ P prefailure warning General Purpose Log Directory Version 1 SMART Log Directory Version 1 [multi-sector log support] Address Access R/W Size Description 0x00 GPL,SL R/O 1 Log Directory 0x01 SL R/O 1 Summary SMART error log 0x02 SL R/O 5 Comprehensive SMART error log 0x03 GPL R/O 6 Ext. Comprehensive SMART error log 0x04 GPL,SL R/O 8 Device Statistics log 0x06 SL R/O 1 SMART self-test log 0x07 GPL R/O 1 Extended self-test log 0x09 SL R/W 1 Selective self-test log 0x0c GPL R/O 2048 Pending Defects log 0x10 GPL R/O 1 SATA NCQ Queued Error log 0x11 GPL R/O 1 SATA Phy Event Counters log 0x21 GPL R/O 1 Write stream error log 0x22 GPL R/O 1 Read stream error log 0x30 GPL,SL R/O 9 IDENTIFY DEVICE data log 0x80-0x9f GPL,SL R/W 16 Host vendor specific log 0xa0-0xa7 GPL,SL VS 16 Device vendor specific log 0xa8-0xb6 GPL,SL VS 1 Device vendor specific log 0xb7 GPL,SL VS 54 Device vendor specific log 0xbd GPL,SL VS 1 Device vendor specific log 0xc0 GPL,SL VS 1 Device vendor specific log 0xc1 GPL VS 93 Device vendor specific log 0xe0 GPL,SL R/W 1 SCT Command/Status 0xe1 GPL,SL R/W 1 SCT Data Transfer SMART Extended Comprehensive Error Log Version: 1 (6 sectors) Device Error Count: 76 (device log contains only the most recent 24 errors) CR = Command Register FEATR = Features Register COUNT = Count (was: Sector Count) Register LBA_48 = Upper bytes of LBA High/Mid/Low Registers ] ATA-8 LH = LBA High (was: Cylinder High) Register ] LBA LM = LBA Mid (was: Cylinder Low) Register ] Register LL = LBA Low (was: Sector Number) Register ] DV = Device (was: Device/Head) Register DC = Device Control Register ER = Error register ST = Status register Powered_Up_Time is measured from power on, and printed as DDd+hh:mm:SS.sss where DD=days, hh=hours, mm=minutes, SS=sec, and sss=millisec. It "wraps" after 49.710 days. Error 76 [3] occurred at disk power-on lifetime: 1135 hours (47 days + 7 hours) When the command that caused the error occurred, the device was active or idle. After command completion occurred, registers were: ER -- ST COUNT LBA_48 LH LM LL DV DC -- -- -- == -- == == == -- -- -- -- -- 40 -- 51 00 00 00 01 5c 2b 8f 00 40 00 Error: UNC at LBA = 0x15c2b8f00 = 5841325824 Commands leading to the command that caused the error were: CR FEATR COUNT LBA_48 LH LM LL DV DC Powered_Up_Time Command/Feature_Name -- == -- == -- == == == -- -- -- -- -- --------------- -------------------- 60 00 b8 00 08 00 01 5c 2b 8f b8 40 00 2d+14:27:14.165 READ FPDMA QUEUED 60 00 b8 00 00 00 01 5c 2b 8f 00 40 00 2d+14:27:14.165 READ FPDMA QUEUED 60 00 c8 00 08 00 01 5c 2b 8e 38 40 00 2d+14:27:14.153 READ FPDMA QUEUED 60 00 c8 00 00 00 01 5c 2b 8d 70 40 00 2d+14:27:14.153 READ FPDMA QUEUED 60 00 c8 00 08 00 01 5c 2b 8c a8 40 00 2d+14:27:14.142 READ FPDMA QUEUED Error 75 [2] occurred at disk power-on lifetime: 1132 hours (47 days + 4 hours) When the command that caused the error occurred, the device was active or idle. After command completion occurred, registers were: ER -- ST COUNT LBA_48 LH LM LL DV DC -- -- -- == -- == == == -- -- -- -- -- 40 -- 51 00 00 00 01 7b 45 16 e8 40 00 Error: UNC at LBA = 0x17b4516e8 = 6363092712 Commands leading to the command that caused the error were: CR FEATR COUNT LBA_48 LH LM LL DV DC Powered_Up_Time Command/Feature_Name -- == -- == -- == == == -- -- -- -- -- --------------- -------------------- 60 00 c8 00 08 00 01 7b 45 17 b0 40 00 2d+11:38:04.384 READ FPDMA QUEUED 60 00 c8 00 00 00 01 7b 45 16 e8 40 00 2d+11:38:04.384 READ FPDMA QUEUED 60 00 c0 00 00 00 01 7b 45 16 28 40 00 2d+11:38:04.383 READ FPDMA QUEUED 60 00 c8 00 08 00 01 7b 45 15 60 40 00 2d+11:38:04.372 READ FPDMA QUEUED 60 00 c8 00 00 00 01 7b 45 14 98 40 00 2d+11:38:04.372 READ FPDMA QUEUED Error 74 [1] occurred at disk power-on lifetime: 1130 hours (47 days + 2 hours) When the command that caused the error occurred, the device was active or idle. After command completion occurred, registers were: ER -- ST COUNT LBA_48 LH LM LL DV DC -- -- -- == -- == == == -- -- -- -- -- 40 -- 51 00 00 00 01 34 2f d9 b8 40 00 Error: UNC at LBA = 0x1342fd9b8 = 5170518456 Commands leading to the command that caused the error were: CR FEATR COUNT LBA_48 LH LM LL DV DC Powered_Up_Time Command/Feature_Name -- == -- == -- == == == -- -- -- -- -- --------------- -------------------- 60 00 e0 00 08 00 01 34 2f da 98 40 00 2d+09:36:26.840 READ FPDMA QUEUED 60 00 e0 00 00 00 01 34 2f d9 b8 40 00 2d+09:36:26.840 READ FPDMA QUEUED 60 00 e0 00 08 00 01 34 2f d8 d8 40 00 2d+09:36:26.829 READ FPDMA QUEUED 60 00 d8 00 00 00 01 34 2f d8 00 40 00 2d+09:36:26.828 READ FPDMA QUEUED 60 00 e0 00 08 00 01 34 2f d7 20 40 00 2d+09:36:26.817 READ FPDMA QUEUED Error 73 [0] occurred at disk power-on lifetime: 1127 hours (46 days + 23 hours) When the command that caused the error occurred, the device was active or idle. After command completion occurred, registers were: ER -- ST COUNT LBA_48 LH LM LL DV DC -- -- -- == -- == == == -- -- -- -- -- 40 -- 51 00 00 00 00 d8 12 4c 50 40 00 Error: UNC at LBA = 0xd8124c50 = 3625077840 Commands leading to the command that caused the error were: CR FEATR COUNT LBA_48 LH LM LL DV DC Powered_Up_Time Command/Feature_Name -- == -- == -- == == == -- -- -- -- -- --------------- -------------------- 60 01 00 00 08 00 00 d8 12 4d 50 40 00 2d+06:27:33.777 READ FPDMA QUEUED 60 01 00 00 00 00 00 d8 12 4c 50 40 00 2d+06:27:33.777 READ FPDMA QUEUED 60 00 d8 00 00 00 00 d8 12 4b 78 40 00 2d+06:27:33.775 READ FPDMA QUEUED 60 01 00 00 08 00 00 d8 12 4a 78 40 00 2d+06:27:33.764 READ FPDMA QUEUED 60 01 00 00 00 00 00 d8 12 48 40 40 00 2d+06:27:33.764 READ FPDMA QUEUED Error 72 [23] occurred at disk power-on lifetime: 1106 hours (46 days + 2 hours) When the command that caused the error occurred, the device was active or idle. After command completion occurred, registers were: ER -- ST COUNT LBA_48 LH LM LL DV DC -- -- -- == -- == == == -- -- -- -- -- 40 -- 51 00 00 00 01 15 c4 27 30 40 00 Error: UNC at LBA = 0x115c42730 = 4660143920 Commands leading to the command that caused the error were: CR FEATR COUNT LBA_48 LH LM LL DV DC Powered_Up_Time Command/Feature_Name -- == -- == -- == == == -- -- -- -- -- --------------- -------------------- 60 00 c8 00 08 00 01 15 c4 27 f8 40 00 1d+09:50:45.002 READ FPDMA QUEUED 60 00 c8 00 00 00 01 15 c4 27 30 40 00 1d+09:50:45.002 READ FPDMA QUEUED 60 00 b8 00 08 00 01 15 c4 26 78 40 00 1d+09:50:44.990 READ FPDMA QUEUED 60 00 c0 00 00 00 01 15 c4 25 b8 40 00 1d+09:50:44.990 READ FPDMA QUEUED 60 00 d0 00 00 00 01 15 c4 24 e8 40 00 1d+09:50:44.989 READ FPDMA QUEUED Error 71 [22] occurred at disk power-on lifetime: 1099 hours (45 days + 19 hours) When the command that caused the error occurred, the device was doing SMART Offline or Self-test. After command completion occurred, registers were: ER -- ST COUNT LBA_48 LH LM LL DV DC -- -- -- == -- == == == -- -- -- -- -- 40 -- 51 00 00 00 00 78 39 af 00 40 00 Error: UNC at LBA = 0x7839af00 = 2017046272 Commands leading to the command that caused the error were: CR FEATR COUNT LBA_48 LH LM LL DV DC Powered_Up_Time Command/Feature_Name -- == -- == -- == == == -- -- -- -- -- --------------- -------------------- 60 00 a8 00 08 00 00 78 39 af a8 40 00 1d+03:04:06.588 READ FPDMA QUEUED 60 00 a8 00 00 00 00 78 39 af 00 40 00 1d+03:04:06.588 READ FPDMA QUEUED 60 00 a0 00 08 00 00 78 39 ae 60 40 00 1d+03:04:06.577 READ FPDMA QUEUED 60 00 a8 00 00 00 00 78 39 ad b8 40 00 1d+03:04:06.577 READ FPDMA QUEUED 60 00 a8 00 08 00 00 78 39 ad 10 40 00 1d+03:04:06.535 READ FPDMA QUEUED Error 70 [21] occurred at disk power-on lifetime: 1080 hours (45 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 COUNT LBA_48 LH LM LL DV DC -- -- -- == -- == == == -- -- -- -- -- 40 -- 51 00 00 00 00 28 27 35 28 40 00 Error: UNC at LBA = 0x28273528 = 673658152 Commands leading to the command that caused the error were: CR FEATR COUNT LBA_48 LH LM LL DV DC Powered_Up_Time Command/Feature_Name -- == -- == -- == == == -- -- -- -- -- --------------- -------------------- 60 00 d0 00 08 00 00 28 27 36 00 40 00 07:48:14.170 READ FPDMA QUEUED 60 00 d8 00 00 00 00 28 27 35 28 40 00 07:48:14.170 READ FPDMA QUEUED 60 00 d8 00 00 00 00 28 27 34 50 40 00 07:48:14.169 READ FPDMA QUEUED 60 00 d0 00 08 00 00 28 27 33 80 40 00 07:48:14.158 READ FPDMA QUEUED 60 00 d8 00 00 00 00 28 27 32 a8 40 00 07:48:14.158 READ FPDMA QUEUED Error 69 [20] occurred at disk power-on lifetime: 1076 hours (44 days + 20 hours) When the command that caused the error occurred, the device was active or idle. After command completion occurred, registers were: ER -- ST COUNT LBA_48 LH LM LL DV DC -- -- -- == -- == == == -- -- -- -- -- 40 -- 51 00 00 00 00 a8 2b b0 38 40 00 Error: UNC at LBA = 0xa82bb038 = 2821435448 Commands leading to the command that caused the error were: CR FEATR COUNT LBA_48 LH LM LL DV DC Powered_Up_Time Command/Feature_Name -- == -- == -- == == == -- -- -- -- -- --------------- -------------------- 60 00 b8 00 08 00 00 a8 2b b0 e8 40 00 03:23:48.845 READ FPDMA QUEUED 60 00 b0 00 00 00 00 a8 2b b0 38 40 00 03:23:48.845 READ FPDMA QUEUED 60 00 98 00 08 00 00 a8 2b af a0 40 00 03:23:48.834 READ FPDMA QUEUED 60 00 c0 00 00 00 00 a8 2b ae e0 40 00 03:23:48.833 READ FPDMA QUEUED 60 00 c0 00 00 00 00 a8 2b ae 20 40 00 03:23:48.832 READ FPDMA QUEUED SMART Extended Self-test Log Version: 1 (1 sectors) Num Test_Description Status Remaining LifeTime(hours) LBA_of_first_error # 1 Extended offline Completed without error 00% 1102 - # 2 Extended offline Completed without error 00% 941 - # 3 Extended offline Completed without error 00% 762 - # 4 Extended offline Completed without error 00% 20 - SMART Selective self-test log data structure revision number 1 SPAN MIN_LBA MAX_LBA CURRENT_TEST_STATUS 1 0 0 Not_testing 2 0 0 Not_testing 3 0 0 Not_testing 4 0 0 Not_testing 5 0 0 Not_testing Selective self-test flags (0x0): After scanning selected spans, do NOT read-scan remainder of disk. If Selective self-test is pending on power-up, resume after 0 minute delay. SCT Status Version: 3 SCT Version (vendor specific): 258 (0x0102) SCT Support Level: 1 Device State: Active (0) Current Temperature: 38 Celsius Power Cycle Min/Max Temperature: 38/43 Celsius Lifetime Min/Max Temperature: 25/45 Celsius Under/Over Temperature Limit Count: 0/0 Vendor specific: 01 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 SCT Temperature History Version: 2 Temperature Sampling Period: 1 minute Temperature Logging Interval: 1 minute Min/Max recommended Temperature: 0/60 Celsius Min/Max Temperature Limit: -41/85 Celsius Temperature History Size (Index): 478 (406) Index Estimated Time Temperature Celsius 407 2017-08-28 01:35 38 ******************* ... ..( 48 skipped). .. ******************* 456 2017-08-28 02:24 38 ******************* 457 2017-08-28 02:25 41 ********************** ... ..(305 skipped). .. ********************** 285 2017-08-28 07:31 41 ********************** 286 2017-08-28 07:32 40 ********************* ... ..( 44 skipped). .. ********************* 331 2017-08-28 08:17 40 ********************* 332 2017-08-28 08:18 39 ******************** ... ..( 26 skipped). .. ******************** 359 2017-08-28 08:45 39 ******************** 360 2017-08-28 08:46 38 ******************* ... ..( 45 skipped). .. ******************* 406 2017-08-28 09:32 38 ******************* SCT Error Recovery Control: Read: 70 (7.0 seconds) Write: 70 (7.0 seconds) Device Statistics (GP Log 0x04) Page Offset Size Value Flags Description 0x01 ===== = = === == General Statistics (rev 2) == 0x01 0x008 4 19 --- Lifetime Power-On Resets 0x01 0x010 4 1138 --- Power-on Hours 0x01 0x018 6 26384963078 --- Logical Sectors Written 0x01 0x020 6 134865765 --- Number of Write Commands 0x01 0x028 6 182479148242 --- Logical Sectors Read 0x01 0x030 6 861594856 --- Number of Read Commands 0x03 ===== = = === == Rotating Media Statistics (rev 1) == 0x03 0x008 4 1136 --- Spindle Motor Power-on Hours 0x03 0x010 4 875 --- Head Flying Hours 0x03 0x018 4 45 --- Head Load Events 0x03 0x020 4 0 --- Number of Reallocated Logical Sectors 0x03 0x028 4 0 --- Read Recovery Attempts 0x03 0x030 4 0 --- Number of Mechanical Start Failures 0x04 ===== = = === == General Errors Statistics (rev 1) == 0x04 0x008 4 76 --- Number of Reported Uncorrectable Errors 0x04 0x010 4 0 --- Resets Between Cmd Acceptance and Completion 0x05 ===== = = === == Temperature Statistics (rev 1) == 0x05 0x008 1 38 --- Current Temperature 0x05 0x010 1 40 --- Average Short Term Temperature 0x05 0x018 1 39 --- Average Long Term Temperature 0x05 0x020 1 45 --- Highest Temperature 0x05 0x028 1 32 --- Lowest Temperature 0x05 0x030 1 43 --- Highest Average Short Term Temperature 0x05 0x038 1 34 --- Lowest Average Short Term Temperature 0x05 0x040 1 39 --- Highest Average Long Term Temperature 0x05 0x048 1 38 --- Lowest Average Long Term Temperature 0x05 0x050 4 0 --- Time in Over-Temperature 0x05 0x058 1 60 --- Specified Maximum Operating Temperature 0x05 0x060 4 0 --- Time in Under-Temperature 0x05 0x068 1 0 --- Specified Minimum Operating Temperature 0x06 ===== = = === == Transport Statistics (rev 1) == 0x06 0x008 4 28 --- Number of Hardware Resets 0x06 0x010 4 0 --- Number of ASR Events 0x06 0x018 4 0 --- Number of Interface CRC Errors |||_ C monitored condition met ||__ D supports DSN |___ N normalized value SATA Phy Event Counters (GP Log 0x11) ID Size Value Description 0x0001 2 0 Command failed due to ICRC error 0x0002 2 0 R_ERR response for data FIS 0x0003 2 0 R_ERR response for device-to-host data FIS 0x0004 2 0 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-to-host non-data FIS 0x0007 2 0 R_ERR response for host-to-device non-data FIS 0x0008 2 0 Device-to-host non-data FIS retries 0x0009 2 0 Transition from drive PhyRdy to drive PhyNRdy 0x000a 2 1 Device-to-host register FISes sent due to a COMRESET 0x000b 2 0 CRC errors within host-to-device FIS 0x000d 2 0 Non-CRC errors within host-to-device FIS 0x000f 2 0 R_ERR response for host-to-device data FIS, CRC 0x0012 2 0 R_ERR response for host-to-device non-data FIS, CRC 0x8000 4 238278 Vendor specific
Last edited:
The firmware on /dev/da3 is 82.00A82 according to SMART. Is there a newer firmware? All I could find was WD Red SMART load/Unload utility 3.5" Drive, but the release date is 12/20/2013 (My drive is probably newer), and the page does not seem to mention the firmware version for comparison?
Update:
Looking around for firmware updates, I found this post which may be relevant to me. What do you (eager readers) think?
Code:
My problem is that the drives are not behaving the same (APM wise) with the same WDidle3 settings and it can cause sync problems when different bios drives are sitting on the same SAS lane. Therefore, I had to separate the drives to different SAS ports and it seems to working stable now (FreeBSD).
Last edited:
Stux
MVP
- Joined
- Jun 2, 2016
- Messages
- 4,419
Looking around I also found this post:
https://community.wd.com/t/wd60efrx-68l0bn1-different-firmware-different-sizes/159208/3
Also, https://support.wdc.com/knowledgebase/answer.aspx?ID=11757
- Status
