Filecopy stailling in SMB, number of errors/warnings, some expected, some like WTF?

[SecCon]

This is a test setup, no data can be compromised.

SMB. Windows environment. 11.2.

Doing occasional filecopies to and from FreeNAS to test. The way I copy the files are using Windows Explorer (which frankly HAS to work), the files are on my WSRV FS and I copy them via my Desktop to my NAS (which frankly also HAS to work), so three physical machines are involved over a GB network.

Had like 40 media files, from 1-3GB each in size, and started copying as above and after seconds I started to get warnings from FreeNAS via NetData and also via system notifications. The copy stalled at about 50%, transfer rates also stalled, from an average of 60-80Mbit/s to 7 and even down to 300KBit/s and also 0.

A few hours after the filecopy I got this as part of my preconfigured daily report:

(ada2:ahcich3:0:0:0): WRITE_FPDMA_QUEUED. ACB: 61 00 d8 f4 58 40 08 00 00 01 00 00
(ada2:ahcich3:0:0:0): CAM status: ATA Status Error
(ada2:ahcich3:0:0:0): ATA status: 41 (DRDY ERR), error: 10 (IDNF )
(ada2:ahcich3:0:0:0): RES: 41 10 d8 f4 58 40 08 00 00 00 00
(ada2:ahcich3:0:0:0): Retrying command
(ada2:ahcich3:0:0:0): WRITE_FPDMA_QUEUED. ACB: 61 00 e0 bb 8b 40 08 00 00 01 00 00
(ada2:ahcich3:0:0:0): CAM status: ATA Status Error
(ada2:ahcich3:0:0:0): ATA status: 41 (DRDY ERR), error: 10 (IDNF )
(ada2:ahcich3:0:0:0): RES: 41 10 e0 bb 8b 40 08 00 00 00 00
(ada2:ahcich3:0:0:0): Retrying command
(ada2:ahcich3:0:0:0): WRITE_FPDMA_QUEUED. ACB: 61 00 e0 d1 8b 40 08 00 00 01 00 00
(ada2:ahcich3:0:0:0): CAM status: ATA Status Error
(ada2:ahcich3:0:0:0): ATA status: 41 (DRDY ERR), error: 10 (IDNF )
(ada2:ahcich3:0:0:0): RES: 41 10 e0 d1 8b 40 08 00 00 00 00
(ada2:ahcich3:0:0:0): Retrying command
(ada2:ahcich3:0:0:0): WRITE_FPDMA_QUEUED. ACB: 61 00 60 ee 8b 40 08 00 00 01 00 00
(ada2:ahcich3:0:0:0): CAM status: ATA Status Error
(ada2:ahcich3:0:0:0): ATA status: 41 (DRDY ERR), error: 10 (IDNF )
(ada2:ahcich3:0:0:0): RES: 41 10 60 ee 8b 40 08 00 00 00 00
(ada2:ahcich3:0:0:0): Retrying command
(ada2:ahcich3:0:0:0): WRITE_FPDMA_QUEUED. ACB: 61 00 e0 fd 8b 40 08 00 00 01 00 00
(ada2:ahcich3:0:0:0): CAM status: ATA Status Error
(ada2:ahcich3:0:0:0): ATA status: 41 (DRDY ERR), error: 10 (IDNF )
(ada2:ahcich3:0:0:0): RES: 41 10 e0 fd 8b 40 08 00 00 00 00
(ada2:ahcich3:0:0:0): Retrying command
(ada2:ahcich3:0:0:0): FLUSHCACHE48. ACB: ea 00 00 00 00 40 00 00 00 00 00 00
(ada2:ahcich3:0:0:0): CAM status: ATA Status Error
(ada2:ahcich3:0:0:0): ATA status: 51 (DRDY SERV ERR), error: 04 (ABRT )
(ada2:ahcich3:0:0:0): RES: 51 04 28 9e e7 47 00 00 00 00 00
(ada2:ahcich3:0:0:0): Retrying command
(ada2:ahcich3:0:0:0): FLUSHCACHE48. ACB: ea 00 00 00 00 40 00 00 00 00 00 00
(ada2:ahcich3:0:0:0): CAM status: ATA Status Error
(ada2:ahcich3:0:0:0): ATA status: 51 (DRDY SERV ERR), error: 04 (ABRT )
(ada2:ahcich3:0:0:0): RES: 51 04 28 9e e7 47 00 00 00 00 00
(ada2:ahcich3:0:0:0): Error 5, Retries exhausted
(ada2:ahcich3:0:0:0): FLUSHCACHE48. ACB: ea 00 00 00 00 40 00 00 00 00 00 00
(ada2:ahcich3:0:0:0): CAM status: ATA Status Error
(ada2:ahcich3:0:0:0): ATA status: 51 (DRDY SERV ERR), error: 04 (ABRT )
(ada2:ahcich3:0:0:0): RES: 51 04 28 9e e7 47 00 00 00 00 00
(ada2:ahcich3:0:0:0): Retrying command
(ada2:ahcich3:0:0:0): FLUSHCACHE48. ACB: ea 00 00 00 00 40 00 00 00 00 00 00
(ada2:ahcich3:0:0:0): CAM status: ATA Status Error
(ada2:ahcich3:0:0:0): ATA status: 51 (DRDY SERV ERR), error: 04 (ABRT )
(ada2:ahcich3:0:0:0): RES: 51 04 28 9e e7 47 00 00 00 00 00
(ada2:ahcich3:0:0:0): Error 5, Retries exhausted
ahcich3: Timeout on slot 23 port 0
ahcich3: is 00000000 cs 00000000 ss ff8001ff rs ff8001ff tfd 40 serr 00000000 cmd 0004c817
(ada2:ahcich3:0:0:0): WRITE_FPDMA_QUEUED. ACB: 61 00 88 34 8c 40 08 00 00 01 00 00
(ada2:ahcich3:0:0:0): CAM status: Command timeout
(ada2:ahcich3:0:0:0): Retrying command
ahcich3: AHCI reset: device not ready after 31000ms (tfd = 00000080)
ahcich3: Timeout on slot 9 port 0
ahcich3: is 00000000 cs 00000000 ss 00000000 rs 00000200 tfd 150 serr 00000000 cmd 0004c917
(aprobe0:ahcich3:0:0:0): ATA_IDENTIFY. ACB: ec 00 00 00 00 40 00 00 00 00 00 00
(aprobe0:ahcich3:0:0:0): CAM status: Command timeout
(aprobe0:ahcich3:0:0:0): Retrying command
ahcich3: Timeout on slot 2 port 0
ahcich3: is 00000000 cs 00000000 ss 0000003c rs 0000003c tfd 40 serr 00000000 cmd 0004c517
(ada2:ahcich3:0:0:0): WRITE_FPDMA_QUEUED. ACB: 61 00 88 78 8c 40 08 00 00 01 00 00
(ada2:ahcich3:0:0:0): CAM status: Command timeout
(ada2:ahcich3:0:0:0): Retrying command
(ada2:ahcich3:0:0:0): WRITE_DMA. ACB: ca 00 88 94 8c 48 00 00 00 00 00 00
(ada2:ahcich3:0:0:0): CAM status: ATA Status Error
(ada2:ahcich3:0:0:0): ATA status: 51 (DRDY SERV ERR), error: 10 (IDNF )
(ada2:ahcich3:0:0:0): RES: 51 10 88 94 8c 48 08 00 00 00 00
(ada2:ahcich3:0:0:0): Retrying command
(ada2:ahcich3:0:0:0): WRITE_DMA. ACB: ca 00 88 b1 8c 48 00 00 00 00 00 00
(ada2:ahcich3:0:0:0): CAM status: ATA Status Error
(ada2:ahcich3:0:0:0): ATA status: 51 (DRDY SERV ERR), error: 10 (IDNF )
(ada2:ahcich3:0:0:0): RES: 51 10 88 b1 8c 48 08 00 00 00 00
(ada2:ahcich3:0:0:0): Retrying command
(ada2:ahcich3:0:0:0): WRITE_DMA. ACB: ca 00 88 cd 8c 48 00 00 00 00 00 00
(ada2:ahcich3:0:0:0): CAM status: ATA Status Error
(ada2:ahcich3:0:0:0): ATA status: 51 (DRDY SERV ERR), error: 10 (IDNF )
(ada2:ahcich3:0:0:0): RES: 51 10 88 cd 8c 48 08 00 00 00 00
(ada2:ahcich3:0:0:0): Retrying command
(ada2:ahcich3:0:0:0): WRITE_DMA. ACB: ca 00 08 ed 8c 48 00 00 00 00 80 00
(ada2:ahcich3:0:0:0): CAM status: ATA Status Error
(ada2:ahcich3:0:0:0): ATA status: 51 (DRDY SERV ERR), error: 10 (IDNF )
(ada2:ahcich3:0:0:0): RES: 51 10 08 ed 8c 48 08 00 00 80 00
(ada2:ahcich3:0:0:0): Retrying command
(ada2:ahcich3:0:0:0): WRITE_DMA. ACB: ca 00 88 09 8d 48 00 00 00 00 00 00
(ada2:ahcich3:0:0:0): CAM status: ATA Status Error
(ada2:ahcich3:0:0:0): ATA status: 51 (DRDY SERV ERR), error: 10 (IDNF )
(ada2:ahcich3:0:0:0): RES: 51 10 88 09 8d 48 08 00 00 00 00
(ada2:ahcich3:0:0:0): Retrying command
ahcich3: Timeout on slot 20 port 0
ahcich3: is 00000000 cs 00000000 ss 7ff00000 rs 7ff00000 tfd 40 serr 00000000 cmd 0004de17
(ada2:ahcich3:0:0:0): WRITE_FPDMA_QUEUED. ACB: 61 00 08 48 8d 40 08 00 00 01 00 00
(ada2:ahcich3:0:0:0): CAM status: Command timeout
(ada2:ahcich3:0:0:0): Retrying command
ahcich3: AHCI reset: device not ready after 31000ms (tfd = 00000080)
ahcich3: Timeout on slot 31 port 0
ahcich3: is 00000000 cs 00000000 ss 00000000 rs 80000000 tfd 150 serr 00000000 cmd 0004df17
(aprobe0:ahcich3:0:0:0): ATA_IDENTIFY. ACB: ec 00 00 00 00 40 00 00 00 00 00 00
(aprobe0:ahcich3:0:0:0): CAM status: Command timeout
(aprobe0:ahcich3:0:0:0): Retrying command
(ada2:ahcich3:0:0:0): WRITE_DMA. ACB: ca 00 88 60 8d 48 00 00 00 00 00 00
(ada2:ahcich3:0:0:0): CAM status: ATA Status Error
(ada2:ahcich3:0:0:0): ATA status: 51 (DRDY SERV ERR), error: 10 (IDNF )
(ada2:ahcich3:0:0:0): RES: 51 10 88 60 8d 48 08 00 00 00 00
(ada2:ahcich3:0:0:0): Retrying command
ahcich3: Timeout on slot 5 port 0
ahcich3: is 00000000 cs 00000000 ss 0000ffe0 rs 0000ffe0 tfd 40 serr 00000000 cmd 0004cf17
(ada2:ahcich3:0:0:0): WRITE_FPDMA_QUEUED. ACB: 61 00 48 a0 8d 40 08 00 00 01 00 00
(ada2:ahcich3:0:0:0): CAM status: Command timeout
(ada2:ahcich3:0:0:0): Retrying command
(ada2:ahcich3:0:0:0): WRITE_DMA. ACB: ca 00 48 b9 8d 48 00 00 00 00 00 00
(ada2:ahcich3:0:0:0): CAM status: ATA Status Error
(ada2:ahcich3:0:0:0): ATA status: 51 (DRDY SERV ERR), error: 10 (IDNF )
(ada2:ahcich3:0:0:0): RES: 51 10 48 b9 8d 48 08 00 00 00 00
(ada2:ahcich3:0:0:0): Retrying command
(ada2:ahcich3:0:0:0): WRITE_DMA. ACB: ca 00 c8 d5 8d 48 00 00 00 00 00 00
(ada2:ahcich3:0:0:0): CAM status: ATA Status Error
(ada2:ahcich3:0:0:0): ATA status: 51 (DRDY SERV ERR), error: 10 (IDNF )
(ada2:ahcich3:0:0:0): RES: 51 10 c8 d5 8d 48 08 00 00 00 00
(ada2:ahcich3:0:0:0): Retrying command
(ada2:ahcich3:0:0:0): WRITE_DMA. ACB: ca 00 48 f3 8d 48 00 00 00 00 00 00
(ada2:ahcich3:0:0:0): CAM status: ATA Status Error
(ada2:ahcich3:0:0:0): ATA status: 51 (DRDY SERV ERR), error: 10 (IDNF )
(ada2:ahcich3:0:0:0): RES: 51 10 48 f3 8d 48 08 00 00 00 00
(ada2:ahcich3:0:0:0): Retrying command
(ada2:ahcich3:0:0:0): WRITE_DMA. ACB: ca 00 c8 12 8e 48 00 00 00 00 00 00
(ada2:ahcich3:0:0:0): CAM status: ATA Status Error
(ada2:ahcich3:0:0:0): ATA status: 51 (DRDY SERV ERR), error: 10 (IDNF )
(ada2:ahcich3:0:0:0): RES: 51 10 c8 12 8e 48 08 00 00 00 00
(ada2:ahcich3:0:0:0): Retrying command
(ada2:ahcich3:0:0:0): WRITE_DMA. ACB: ca 00 c8 30 8e 48 00 00 00 00 00 00
(ada2:ahcich3:0:0:0): CAM status: ATA Status Error
(ada2:ahcich3:0:0:0): ATA status: 51 (DRDY SERV ERR), error: 10 (IDNF )
(ada2:ahcich3:0:0:0): RES: 51 10 c8 30 8e 48 08 00 00 00 00
(ada2:ahcich3:0:0:0): Retrying command
(ada2:ahcich3:0:0:0): WRITE_FPDMA_QUEUED. ACB: 61 00 48 5f 8e 40 08 00 00 01 00 00
(ada2:ahcich3:0:0:0): CAM status: ATA Status Error
(ada2:ahcich3:0:0:0): ATA status: 41 (DRDY ERR), error: 10 (IDNF )
(ada2:ahcich3:0:0:0): RES: 41 10 48 5f 8e 40 08 00 00 00 00
(ada2:ahcich3:0:0:0): Retrying command
(ada2:ahcich3:0:0:0): WRITE_FPDMA_QUEUED. ACB: 61 80 c8 91 8e 40 08 00 00 00 00 00
(ada2:ahcich3:0:0:0): CAM status: ATA Status Error
(ada2:ahcich3:0:0:0): ATA status: 41 (DRDY ERR), error: 10 (IDNF )
(ada2:ahcich3:0:0:0): RES: 41 10 c8 91 8e 40 08 00 00 00 00
(ada2:ahcich3:0:0:0): Retrying command
(ada2:ahcich3:0:0:0): WRITE_FPDMA_QUEUED. ACB: 61 00 48 aa 8e 40 08 00 00 01 00 00
(ada2:ahcich3:0:0:0): CAM status: ATA Status Error
(ada2:ahcich3:0:0:0): ATA status: 41 (DRDY ERR), error: 10 (IDNF )
(ada2:ahcich3:0:0:0): RES: 41 10 48 aa 8e 40 08 00 00 00 00
(ada2:ahcich3:0:0:0): Retrying command
ahcich3: Timeout on slot 1 port 0
ahcich3: is 00000000 cs 00000002 ss 00000000 rs 00000002 tfd c0 serr 00000000 cmd 0004c117

The messages from NetData are , in order of reception:

system.ram Chart ram in use = 90.8%
system RAM usage Alarm ram Family WARNING Severity

pv4.tcphandshake Chart ipv4 tcphandshake last collected secs = 00:00:11 ago
number of seconds since the last successful data collection Alarm tcp Family WARNING Severity

ipv4.udperrors Chart ipv4 udperrors last collected secs = 00:00:11 ago
number of seconds since the last successful data collection Alarm udp Family WARNING Severity

system.ram Chart ram in use (was warning for 10 seconds)
system RAM usage Alarm ram Family Recovered from WARNING Severity

disk_util.ada2 Chart 10min disk utilization = 98.4%
the percentage of time the disk was busy, during the last 10 minutes Alarm ada2 Family CRITICAL Severity

ipv4.tcphandshake Chart ipv4 tcphandshake last collected secs (was warning for 12 minutes and 47 seconds)
number of seconds since the last successful data collection Alarm tcp Family Recovered from WARNING Severity

ipv4.udperrors Chart ipv4 udperrors last collected secs (was warning for 12 minutes and 47 seconds)
number of seconds since the last successful data collection Alarm udp Family Recovered from WARNING Severity

system.ram Chart ram in use = 90.3%
system RAM usage Alarm ram Family WARNING Severity

system.ram Chart ram in use (was warning for 10 seconds)
system RAM usage Alarm ram Family Recovered from WARNING Severity

disk_util.ada2 Chart 10min disk utilization (alarm was raised for 18 minutes and 2 seconds)
the percentage of time the disk was busy, during the last 10 minutes Alarm ada2 Family Recovered from WARNING Severity

Now, I get that some of this is related to heavy disk, ram and net activity while copying these about 100GB of files, but frankly, other from the most obvious stuff related to that, WHAT IS THE FREENAS TRYING TO TELL ME?

The daily output is 70% incomprehensible jibberish, to me.

I hope someone can tell me, based on given info, why the filecopy stalled. My hardware is listed in the signature and I can post additional info as requested, of course.

 

[SecCon]

Anyone home?

 

[seanm]

"ram in use = 90.8%" -> if you copy few/smaller files such that your RAM usage is lower, is performance ok?

Anyway, probably you should add more RAM.

 

[Yorick]

RAM is fine, ARC will use it for performance. Unless you have indications from checking ARC stats that your cache hit rate on read is low, more memory won't help.

I'd dig into those errors. See https://forums.freenas.org/index.php?threads/cam-status-ata-status-error.16833/

That ada2 drive might be going. Replace it, wait for resilver, test again? It's conceivable the SATA port has issues, but SM boards are usually rock solid.

 

[SecCon]

Thanks my dear @Yorick I shall pay tribute at the Globe Theater when visiting England next time.

@seanm The ram is 16GB, should be OK considering ratio storage/ram,

The ada2 is definitely giving more errors (weekly resilver just tagged a new bunch of them), gonna switch cabling and do a physical test of it on a dock with native troubleshooting software, like seatools or something pertinent to the manufacturer. Damn, this is new stuff....

Can't help being a bit curious as to notification e-mal subjects like this one

Cron <root@freenas> PATH="/bin:/sbin:/usr/bin:/usr/sbin:/usr/local/bin:/usr/local/sbin:/root/bin" /usr/local/libexec/nas/scrub -t 35 fsa-homered-conram

Waaaay to much unix...


Doing a smartctl long test on ada2

 

[SecCon]

So got a log from ada2 that is rougly 20 pages or maybe 15... what should I look for to identify eventual errors. (Frankly I do get that posting that log to its full extent might be annoying to fellow readers...)

 

[Yorick]

https://www.backblaze.com/blog/what-smart-stats-indicate-hard-drive-failures/

 

[Yorick]

Note that smart isn’t perfect. You have errors indicating the drive is failing. If you move the drive to another sata port, and the errors follow the drive, then your best bet is likely to replace the drive before it fails.

 

[SecCon]

Yes I know.... however, the drive is in an enclosure so there is more than one likely culprit in this. I may have to rebuild/refit the computer a bit to test without enclosure...

 

[SweetAndLow]

CAM status errors means whatever is connecting your hdd to your motherboard is not working correctly. I'm also blow away that after 9 comments there is zero information about your hardware, especially since this is a hardware problem. Fix the connection issue with the disk, setup auto smart tests, post your smart data to the thread so we can see if the disk is actually failing.

 

[SecCon]

My hardware

CAM status errors means whatever is connecting your hdd to your motherboard is not working correctly. I'm also blow away that after 9 comments there is zero information about your hardware, especially since this is a hardware problem. Fix the connection issue with the disk, setup auto smart tests, post your smart data to the thread so we can see if the disk is actually failing.

My hardware is, as yours, listed in my signature. As for actually doing stuff I have not been able yet due to lack of time.

 

[SweetAndLow]

My hardware

My hardware is, as yours, listed in my signature. As for actually doing stuff I have not been able yet due to lack of time.

Signature is not the correct location for listing your hardware specs in the post like the forum rules require. It appears you are just using normal sata cables, so make sure they are connected correctly. Why did you say you hdd is in an external enclosure? You are not playing by the rules here and keeping secrets, that's no way to get help.

 

[SecCon]

@SweetAndLow
First off I don't know what your issue is so get the hell out of my thread if you are only going to complain or repeat what I or others already wrote.

Yes - I forgot about the enclosure, that is why I said I will have to refit the comp, will probably happen oncoming days.
Yes - I have my hardware specs in my signature and said that at the beginning of the thread, if you have any issues about that I suggest you bring it up with @Chris Moore and @Ericloewe since they do also have their specs in their signatures, I copied them.

If one is working on something with different specs or need to complement the specs that is obviously stated and informed upon. Again, my mistake with forgetting about the enclosure, which never was a secret but an honest mistake on my part. After all I do not have the FreeNAS very handy, it is stashed away on a hard to reach shelf in my garage, but I suppose you would blame me for concealing that info as well?
That's also why it takes me some time between actually doing anything about whats wrong.

Having said that, I do get you. I am a n00b in this, I don't use Linux, I am having trouble with stuff in the error logs that could be in Chinese to me, but I do have basic understanding of it all, its just frustrating to have to look up 2800 lines of log (45 pages, I have pasted it in to Word to check :p , 167,538 chars) only to tell me: "err this system thinks you may have issues with your sata conn". Goes to show that a correct error management and implementing meaningful error messages is not just a challenge for Microsoft... if you get what I am saying.

Peace out.

 

[Chris Moore]

First off I don't know what your issue is so get the hell out of my thread if you are only going to complain or repeat what I or others already wrote.

Please refrain from being so confrontational. We are here to help one another.

I have my hardware specs in my signature and said that at the beginning of the thread

Although that is a nice convenience to have that information in the signature. Please be mindful of the fact that those viewing the forum from a mobile device will not be able to see the signature which is why it is best to post that configuration information in the body of a post if you are asking for help with a problem.

 

[SecCon]

OK, rebuilt the comp, new chassi, ditched the enclosure, new cables all over.
While I realise that the enclosure addition was a mistake, added one additional potential fault point, it was needed to fit the drives in the old chassi, not anymore in the new one. However this only lead to get rid of potential conn errors caused by the enclosure and I still suffer from errors as specified above with ada2 drive. which I am now able to focus on properly and without distractions and something I am used to manage and troubleshoot outside the FreeNAS and Linux environments.

 

[Yorick]

I'm still advocating for ditching that drive - replace it, wait for resilver, see what happens.

No "Linux" anywhere here, by the way. FreeNAS is built on FreeBSD, which is more Unix than Linux.

 

[Chris Moore]

OP Referenced System:

Chassi: CoolerMaster HAF XB Evo
Motherboard: SuperMicro X11SSM-F
CPU: Xeon E3-1240 V6
RAM: Kingston Value DDR4 2400MHz 16GB ECC
Drives: 4 x HGST 4TB
Power: Seasonic FOCUS Plus 550 Platinum

I don't see anything particularly wrong with this. I am guessing that the four HGST drives are connected to the system board SATA ports? What mode are those ports set to in BIOS? AHCI is how they should be configured.

A few hours after the filecopy I got this as part of my preconfigured daily report:

I am also guessing that this is a new build? Did you do any burn-in testing on these drives to ensure they are not DOA before attempting to load data into the pool?

Code:

(ada2:ahcich3:0:0:0): CAM status: Command timeout
(ada2:ahcich3:0:0:0): Retrying command
ahcich3: AHCI reset: device not ready after 31000ms (tfd = 00000080)
ahcich3: Timeout on slot 9 port 0

This looks like the drive is not responding. I would suspect a faulty drive or cable connection to the drive. We also saw a faulty power cable (more than once) cause drives to not work properly.

The ada2 is definitely giving more errors (weekly resilver just tagged a new bunch of them), gonna switch cabling and do a physical test of it on a dock with native troubleshooting software, like seatools or something pertinent to the manufacturer. Damn, this is new stuff....

Did your testing of ada2 show any fault with the drive?

So got a log from ada2 that is rougly 20 pages or maybe 15... what should I look for to identify eventual errors. (Frankly I do get that posting that log to its full extent might be annoying to fellow readers...)

I love to review those. Here I will share one of mine to get the ball rolling:

Code:

smartctl -x /dev/da29
smartctl 6.6 2017-11-05 r4594 [FreeBSD 11.1-STABLE amd64] (local build)
Copyright (C) 2002-17, Bruce Allen, Christian Franke, www.smartmontools.org

=== START OF INFORMATION SECTION ===
Model Family:     Seagate Constellation ES.3
Device Model:     ST4000NM0033-9ZM170
Serial Number:    xxxxxxxx
LU WWN Device Id: 5 000c50 08cf17879
Firmware Version: SN06
User Capacity:    4,000,787,030,016 bytes [4.00 TB]
Sector Size:      512 bytes logical/physical
Rotation Rate:    7200 rpm
Form Factor:      3.5 inches
Device is:        In smartctl database [for details use: -P show]
ATA Version is:   ACS-2 (minor revision not indicated)
SATA Version is:  SATA 3.0, 6.0 Gb/s (current: 6.0 Gb/s)
Local Time is:    Sun Feb 17 09:20:59 2019 CST
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
DSN feature is:   Unavailable
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:  (0x82) Offline data collection activity
                                        was completed without error.
                                        Auto Offline Data Collection: Enabled.
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:                (  584) 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:        (   1) minutes.
Extended self-test routine
recommended polling time:        ( 486) minutes.
Conveyance self-test routine
recommended polling time:        (   2) minutes.
SCT capabilities:              (0x50bd) SCT Status supported.
                                        SCT Error Recovery Control supported.
                                        SCT Feature Control supported.
                                        SCT Data Table supported.

SMART Attributes Data Structure revision number: 10
Vendor Specific SMART Attributes with Thresholds:
ID# ATTRIBUTE_NAME          FLAGS    VALUE WORST THRESH FAIL RAW_VALUE
  1 Raw_Read_Error_Rate     POSR--   081   063   044    -    126962112
  3 Spin_Up_Time            PO----   094   094   000    -    0
  4 Start_Stop_Count        -O--CK   100   100   020    -    6
  5 Reallocated_Sector_Ct   PO--CK   100   100   010    -    0
  7 Seek_Error_Rate         POSR--   084   060   045    -    301524718
  9 Power_On_Hours          -O--CK   097   097   000    -    3470
10 Spin_Retry_Count        PO--C-   100   100   097    -    0
12 Power_Cycle_Count       -O--CK   100   100   020    -    6
184 End-to-End_Error        -O--CK   100   100   099    -    0
187 Reported_Uncorrect      -O--CK   100   100   000    -    0
188 Command_Timeout         -O--CK   100   100   000    -    0
189 High_Fly_Writes         -O-RCK   099   099   000    -    1
190 Airflow_Temperature_Cel -O---K   058   054   040    -    42 (Min/Max 37/45)
191 G-Sense_Error_Rate      -O--CK   100   100   000    -    0
192 Power-Off_Retract_Count -O--CK   100   100   000    -    5
193 Load_Cycle_Count        -O--CK   100   100   000    -    245
194 Temperature_Celsius     -O---K   042   046   000    -    42 (0 25 0 0 0)
195 Hardware_ECC_Recovered  -O-RC-   044   006   000    -    126962112
197 Current_Pending_Sector  -O--C-   100   100   000    -    0
198 Offline_Uncorrectable   ----C-   100   100   000    -    0
199 UDMA_CRC_Error_Count    -OSRCK   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      5  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
0x08       GPL     R/O      2  Power Conditions log
0x09           SL  R/W      1  Selective self-test log
0x10       GPL     R/O      1  NCQ Command 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
0x24       GPL     R/O    512  Current Device Internal Status Data log
0x30       GPL,SL  R/O      9  IDENTIFY DEVICE data log
0x80-0x9f  GPL,SL  R/W     16  Host vendor specific log
0xa1       GPL,SL  VS      20  Device vendor specific log
0xa2       GPL     VS    4496  Device vendor specific log
0xa6       GPL     VS     192  Device vendor specific log
0xa8       GPL,SL  VS     129  Device vendor specific log
0xa9       GPL,SL  VS       1  Device vendor specific log
0xad       GPL     VS      16  Device vendor specific log
0xb0       GPL     VS    5176  Device vendor specific log
0xbd       GPL     VS     512  Device vendor specific log
0xbe-0xbf  GPL     VS   65535  Device vendor specific log
0xc1       GPL,SL  VS      10  Device vendor specific log
0xc3       GPL,SL  VS       8  Device vendor specific log
0xd1       GPL     VS      39  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 (5 sectors)
No Errors Logged

SMART Extended Self-test Log Version: 1 (1 sectors)
Num  Test_Description    Status                  Remaining  LifeTime(hours)  LBA_of_first_error
# 1  Short offline       Completed without error       00%      3462         -
# 2  Short offline       Completed without error       00%      3461         -
# 3  Short offline       Completed without error       00%      3438         -
# 4  Short offline       Completed without error       00%      3437         -
# 5  Extended offline    Completed without error       00%      3405         -
# 6  Short offline       Completed without error       00%      3390         -
# 7  Short offline       Completed without error       00%      3389         -
# 8  Extended offline    Completed without error       00%      3357         -
# 9  Short offline       Completed without error       00%      3342         -
#10  Short offline       Completed without error       00%      3341         -
#11  Short offline       Completed without error       00%      3318         -
#12  Short offline       Completed without error       00%      3317         -
#13  Short offline       Completed without error       00%      3294         -
#14  Short offline       Completed without error       00%      3293         -
#15  Short offline       Completed without error       00%      3270         -
#16  Short offline       Completed without error       00%      3269         -
#17  Extended offline    Completed without error       00%      3237         -
#18  Short offline       Completed without error       00%      3221         -
#19  Extended offline    Completed without error       00%      3189         -

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):       522 (0x020a)
SCT Support Level:                   1
Device State:                        Active (0)
Current Temperature:                    42 Celsius
Power Cycle Min/Max Temperature:     37/45 Celsius
Lifetime    Min/Max Temperature:     25/46 Celsius
Under/Over Temperature Limit Count:   0/17447

SCT Temperature History Version:     2
Temperature Sampling Period:         1 minute
Temperature Logging Interval:        10 minutes
Min/Max recommended Temperature:      0/ 0 Celsius
Min/Max Temperature Limit:            0/ 0 Celsius
Temperature History Size (Index):    128 (108)

Index    Estimated Time   Temperature Celsius
109    2019-02-16 12:10    42  ***********************
...    ..( 61 skipped).    ..  ***********************
  43    2019-02-16 22:30    42  ***********************
  44    2019-02-16 22:40    43  ************************
...    ..( 24 skipped).    ..  ************************
  69    2019-02-17 02:50    43  ************************
  70    2019-02-17 03:00    42  ***********************
  71    2019-02-17 03:10    42  ***********************
  72    2019-02-17 03:20    43  ************************
  73    2019-02-17 03:30    42  ***********************
...    ..( 34 skipped).    ..  ***********************
108    2019-02-17 09:20    42  ***********************

SCT Error Recovery Control:
           Read:    100 (10.0 seconds)
          Write:    100 (10.0 seconds)

Device Statistics (GP Log 0x04)
Page  Offset Size        Value Flags Description
0x01  =====  =               =  ===  == General Statistics (rev 1) ==
0x01  0x008  4               6  ---  Lifetime Power-On Resets
0x01  0x010  4            3470  ---  Power-on Hours
0x01  0x018  6     12003443325  ---  Logical Sectors Written
0x01  0x020  6        80674648  ---  Number of Write Commands
0x01  0x028  6     29179581030  ---  Logical Sectors Read
0x01  0x030  6       193712947  ---  Number of Read Commands
0x01  0x038  6               -  ---  Date and Time TimeStamp
0x03  =====  =               =  ===  == Rotating Media Statistics (rev 1) ==
0x03  0x008  4            3470  ---  Spindle Motor Power-on Hours
0x03  0x010  4              79  ---  Head Flying Hours
0x03  0x018  4             245  ---  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
0x03  0x038  4               0  ---  Number of Realloc. Candidate Logical Sectors
0x03  0x040  4               6  ---  Number of High Priority Unload Events
0x04  =====  =               =  ===  == General Errors Statistics (rev 1) ==
0x04  0x008  4               0  ---  Number of Reported Uncorrectable Errors
0x04  0x010  4               0  ---  Resets Between Cmd Acceptance and Completion
0x05  =====  =               =  ===  == Temperature Statistics (rev 1) ==
0x05  0x008  1              42  ---  Current Temperature
0x05  0x020  1              46  ---  Highest Temperature
0x05  0x028  1              29  ---  Lowest Temperature
0x05  0x030  1               -  ---  Highest Average Short Term Temperature
0x05  0x038  1               -  ---  Lowest Average Short Term Temperature
0x05  0x040  1               -  ---  Highest Average Long Term Temperature
0x05  0x048  1               -  ---  Lowest Average Long Term Temperature
0x05  0x050  4               0  ---  Time in Over-Temperature
0x05  0x058  1              55  ---  Specified Maximum Operating Temperature
0x05  0x060  4               0  ---  Time in Under-Temperature
0x05  0x068  1              13  ---  Specified Minimum Operating Temperature
                                |||_ C monitored condition met
                                ||__ D supports DSN
                                |___ N normalized value

Pending Defects log (GP Log 0x0c) not supported

SATA Phy Event Counters (GP Log 0x11)
ID      Size     Value  Description
0x000a  2            8  Device-to-host register FISes sent due to a COMRESET
0x0001  2            0  Command failed due to ICRC error
0x0003  2            0  R_ERR response for device-to-host data FIS
0x0004  2            0  R_ERR response for host-to-device 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

Yes I know.... however, the drive is in an enclosure so there is more than one likely culprit in this. I may have to rebuild/refit the computer a bit to test without enclosure...

So, somehow ada2 is in reference to more than a single drive? I am unclear on how that is working, but I gather that you have moved the hardware to a different case now. If you would share the output of zpool status with us also, that might be informative.

The ada2 is definitely giving more errors (weekly resilver just tagged a new bunch of them)

PS. In normal use, a drive should not need to resilver. If you are getting weekly resilvers, there is definitely a problem that needs to be found and addressed.

 

[Chris Moore]

I just had another thought. Are these new drives or re-purposed?
I bought a batch of used drives from eBay once where I got almost 50% failures out of them in the first three months.

 

[SecCon]

I don't see anything particularly wrong with this. I am guessing that the four HGST drives are connected to the system board SATA ports? What mode are those ports set to in BIOS? AHCI is how they should be configured.

I am also guessing that this is a new build? Did you do any burn-in testing on these drives to ensure they are not DOA before attempting to load data into the pool?

This looks like the drive is not responding. I would suspect a faulty drive or cable connection to the drive. We also saw a faulty power cable (more than once) cause drives to not work properly.

Did your testing of ada2 show any fault with the drive?

So, somehow ada2 is in reference to more than a single drive? I am unclear on how that is working, but I gather that you have moved the hardware to a different case now. If you would share the output of zpool status with us also, that might be informative.

PS. In normal use, a drive should not need to resilver. If you are getting weekly resilvers, there is definitely a problem that needs to be found and addressed.

I know @Yorick , sorry for mixing *nix.

Chris, I have yet to diagnose the drive but in answer to your questions:

• The drives were connected via an Icy Box Enclosure with Backplane that has worked well up to now: https://www.icydock.com/goods.php?id=153
• AHCI via BIOS
• New build, no burn in test as such, only fiddling with it learning FreeNAS. I would however consider copying many large files a test as such.
• The smartctl test of ada2 gave me 45 pages of information, mostly errors. Since I will remove the drive and do manufacturer tests I haven't posted the result, but I have it.
• I have moved the drives, keeping the original order so it should be the same drive connected to the same sata port
• As it is right now, FreeNAS won't start, despite having two out of three drives available but I won't do anything about that.
• Drives are new.

I will put in some other drives meanwhile and need to change signature to reflect changes in hardware. Boot drive is the same, network is the same, configuration is the same, chassi has changed, drives will change.

As for two things I have done that may be relevant information and you ask about: I did set resilver/scrub to run weekly, there is nothing in the manual as for recommendations to that apart from not running it when expecting IO load (ref: https://en.wikipedia.org/wiki/ZFS#Resilvering_and_scrub_(array_syncing_and_integrity_checking)) .
I also set deduplication, since I do know from many projects I might have some space to save there: https://www.ixsystems.com/documentation/freenas/11.2/storage.html#deduplication. I know from work we have it on our NetApp's with good results, however not entirely applicable for private use of course.

Again, it is a test setup, it is not supposed to work 100% with my first FreeNAS configuration attempt, and now some drive is possiblybroke in the process delaying this.

 

[Chris Moore]

Drives are new.

Since it is new, I would suggest sending it back either to the vendor or to the manufacturer depending on the exact situation. I know that some retailers have a return policy and others don't, but from what you have told us, it sounds clear to me that this ada2 is a bad disk. What we call DOA.

As it is right now, FreeNAS won't start, despite having two out of three drives available but I won't do anything about that.

It should start, even with missing disks. You might need to check all the connections after the hardware rearrangement to ensure everything is connected correctly.

I also set deduplication, since I do know from many projects I might have some space to save there:

Deduplication is very processor and memory intensive. You would need very powerful processor and a lot of RAM for that. You may want to disable this as it will slow everything down.

Again, it is a test setup, it is not supposed to work 100% with my first FreeNAS configuration attempt,

It is a learning process when you jump into a new environment. I spent years learning and I don't claim to know it all. Here is a link to a very good guide for configuring and testing a new FreeNAS system. It was written for a previous version of FreeNAS but if you login with the "Legacy" UI, it should all be quite easy to follow and it does work with the "New" UI that was released in Version 11.2 but it may be difficult to find some things because it has been rearranged.

Uncle Fester's Basic FreeNAS Configuration Guide
https://www.familybrown.org/dokuwiki/doku.php?id=fester:intro