Help with log file

[Pancackewaffle]

Hello,
I am somewhat still a noob with FreeNAS and I have had a daily security output of something that fails for awhile now. I'm not the best at reading logs and was wondering if someone out there could help decode what what is being said.
I do have a bit of background to these logs though; I have a failing drive (failed smart test and has corrupted sectors) and I was trying to move it to a mirrored volume without success. This is my jail drive and it's 11 years old so it's probably about time it died.
Also I have been trying to do rsync of my movies and TV shows to another Nas box that's running CentOS but that hasn't worked either. I kinda got frustrated with stuff not working.

Log file output:



WatchTower.local kernel log messages:
> (ada2:ahcich4:0:0:0): READ_DMA. ACB: c8 00 50 17 15 4c 00 00 00 00 08 00
> (ada2:ahcich4:0:0:0): CAM status: ATA Status Error
> (ada2:ahcich4:0:0:0): ATA status: 51 (DRDY SERV ERR), error: 40 (UNC )
> (ada2:ahcich4:0:0:0): RES: 51 40 53 17 15 4c 00 00 00 08 00
> (ada2:ahcich4:0:0:0): Retrying command
> (ada2:ahcich4:0:0:0): READ_DMA. ACB: c8 00 50 17 15 4c 00 00 00 00 08 00
> (ada2:ahcich4:0:0:0): CAM status: ATA Status Error
> (ada2:ahcich4:0:0:0): ATA status: 51 (DRDY SERV ERR), error: 40 (UNC )
> (ada2:ahcich4:0:0:0): RES: 51 40 53 17 15 4c 00 00 00 08 00
> (ada2:ahcich4:0:0:0): Retrying command
> (ada2:ahcich4:0:0:0): READ_DMA. ACB: c8 00 50 17 15 4c 00 00 00 00 08 00
> (ada2:ahcich4:0:0:0): CAM status: ATA Status Error
> (ada2:ahcich4:0:0:0): ATA status: 51 (DRDY SERV ERR), error: 40 (UNC )
> (ada2:ahcich4:0:0:0): RES: 51 40 53 17 15 4c 00 00 00 08 00
> (ada2:ahcich4:0:0:0): Retrying command
> (ada2:ahcich4:0:0:0): READ_DMA. ACB: c8 00 50 17 15 4c 00 00 00 00 08 00
> (ada2:ahcich4:0:0:0): CAM status: ATA Status Error
> (ada2:ahcich4:0:0:0): ATA status: 51 (DRDY SERV ERR), error: 40 (UNC )
> (ada2:ahcich4:0:0:0): RES: 51 40 53 17 15 4c 00 00 00 08 00
> (ada2:ahcich4:0:0:0): Retrying command
> (ada2:ahcich4:0:0:0): READ_DMA. ACB: c8 00 50 17 15 4c 00 00 00 00 08 00
> (ada2:ahcich4:0:0:0): CAM status: ATA Status Error
> (ada2:ahcich4:0:0:0): ATA status: 51 (DRDY SERV ERR), error: 40 (UNC )
> (ada2:ahcich4:0:0:0): RES: 51 40 53 17 15 4c 00 00 00 08 00
> (ada2:ahcich4:0:0:0): Error 5, Retries exhausted
> (ada2:ahcich4:0:0:0): READ_DMA. ACB: c8 00 50 17 15 4c 00 00 00 00 08 00
> (ada2:ahcich4:0:0:0): CAM status: ATA Status Error
> (ada2:ahcich4:0:0:0): ATA status: 51 (DRDY SERV ERR), error: 40 (UNC )
> (ada2:ahcich4:0:0:0): RES: 51 40 53 17 15 4c 00 00 00 08 00
> (ada2:ahcich4:0:0:0): Retrying command
> (ada2:ahcich4:0:0:0): READ_DMA. ACB: c8 00 50 17 15 4c 00 00 00 00 08 00
> (ada2:ahcich4:0:0:0): CAM status: ATA Status Error
> (ada2:ahcich4:0:0:0): ATA status: 51 (DRDY SERV ERR), error: 40 (UNC )
> (ada2:ahcich4:0:0:0): RES: 51 40 53 17 15 4c 00 00 00 08 00
> (ada2:ahcich4:0:0:0): Retrying command
> (ada2:ahcich4:0:0:0): READ_DMA. ACB: c8 00 50 17 15 4c 00 00 00 00 08 00
> (ada2:ahcich4:0:0:0): CAM status: ATA Status Error
> (ada2:ahcich4:0:0:0): ATA status: 51 (DRDY SERV ERR), error: 40 (UNC )
> (ada2:ahcich4:0:0:0): RES: 51 40 53 17 15 4c 00 00 00 08 00
> (ada2:ahcich4:0:0:0): Retrying command
> (ada2:ahcich4:0:0:0): READ_DMA. ACB: c8 00 50 17 15 4c 00 00 00 00 08 00
> (ada2:ahcich4:0:0:0): CAM status: ATA Status Error
> (ada2:ahcich4:0:0:0): ATA status: 51 (DRDY SERV ERR), error: 40 (UNC )
> (ada2:ahcich4:0:0:0): RES: 51 40 53 17 15 4c 00 00 00 08 00
> (ada2:ahcich4:0:0:0): Retrying command
> (ada2:ahcich4:0:0:0): READ_DMA. ACB: c8 00 50 17 15 4c 00 00 00 00 08 00
> (ada2:ahcich4:0:0:0): CAM status: ATA Status Error
> (ada2:ahcich4:0:0:0): ATA status: 51 (DRDY SERV ERR), error: 40 (UNC )
> (ada2:ahcich4:0:0:0): RES: 51 40 53 17 15 4c 00 00 00 08 00
> (ada2:ahcich4:0:0:0): Error 5, Retries exhausted

WatchTower.local login failures:
Nov 18 00:39:48 WatchTower sshd[96067]: Bad protocol version identification '@RSYNCD: 30.0' from 192.168.250.15 port 59770
Nov 18 00:44:02 WatchTower sshd[96547]: Bad protocol version identification '@RSYNCD: 30.0' from 192.168.250.15 port 59776

-- End of security output --

 

[joeschmuck]

Well you nailed it, the drive ada2 has failed.

I can't speak to the Rsync messages, I barely know how to spell rsync.

If you are able to transfer files via SMB or direct copy from ada2 to a different vdev then I'd try that however odds are you will still have lots of error messages. Focus on the most important data you want to copy first. 11 years, not bad at all.

 

[Pancackewaffle]

Well you nailed it, the drive ada2 has failed.

I can't speak to the Rsync messages, I barely know how to spell rsync.

If you are able to transfer files via SMB or direct copy from ada2 to a different vdev then I'd try that however odds are you will still have lots of error messages. Focus on the most important data you want to copy first. 11 years, not bad at all.

Awesome suggestion, completely forgot that I could use samba on cent. And just FYI, that was 11 years and I got it used ;)

 

[Pancackewaffle]

Alright so I know samba can transfer the rsync things like movies and TV shows but as for the jail stuff... How do I transfer all my jail to a new hard drive? Can I do that with shares too or is there a specific command?
Failing HDD jail config:
Jails
>Jails
>>(Installed plugins, jails, custom configs (probably about 6 different ones))
New HDD config:
Jails2
>Jails2

 

[joeschmuck]

You can use the cp to copy data in a shell. The issue will be in FreeNAS GUI recognizing the jails properly. If you can I'd try to add a new drive to replace it in place but I've never done that with a single drive vdev. Follow the user guide on how to replace a drive. If you can replace the drive this way then you will maintain all your data and jails. The problem occurs when the failed drive starts throwing errors of course.

Worst case is you have to rebuild your jails. I guess this leads me to ask, why have your jails on a seperate hard drive? If you really want a seperate hard drive then I'd suggest you run a mirrored pair for this application if you don't want it on your main pool.

 

[Pancackewaffle]

Ya, it was suggested to me if I were to run a media server then I should put the jails on it's own drive... Less impact on actual storage drive(s)

Sent from my SM-G930W8 using Tapatalk

 

[joeschmuck]

My drives have been running for about 3 days over 5 years. That is spinning non-stop with the heads loaded and and an active jail. However it's really up to you how you build and run your system. The only reason I know to place your jails on a SSD is to allow the main storage drives to spin down for long periods of time, however if the drives spin up frequently then that will typically cause more harm to the drives due to the current surge to spin up the drive motor. I understand that there is a reason to do this however you need to ensure you have everything setup properly to achieve it. If all you did was move the jails to a seperate hard drive and your main pool is still up and running then you are causing yourself grief for no reason. And again, it's up to you how you run your system. If you desire advice on the configuration of the vdevs/pools and jails and such, post all your system details and your use case and several of us will chime in and give you sound advice.

I hope you are able to recover all your data, please let us know, it's good to have closure.