Identify Failed drive from ACHI Timeout

Status
Not open for further replies.

Shepppard

Dabbler
Joined
Sep 8, 2012
Messages
12
So of course a Noob here. I just recently upgraded from 8.2.0 to 8.3.0 so that I could enable auto expand on my zpool to Upgrade the size of a RAIDZ2.
I made sure everything was reslivered and I got a good report and green across the board so that there where no issues. Soon as the upgrade is done of course the system locks up all the time. So much so that I can't even get in to get an output of the syslog. I tried setting up a syslog server but there doesn't seem to be much info on how to do that. Any ways the question I really need to know is how to identify a failed drive from an ACHI Timeout? Mine looks similar to this

ahcich0: Timeout on slot 10 port 0

All my drives are labeled as ADA0 through to ADA7 cause I already learnt that lesson.

I'm using an older P5Q Mother board with a 6700Q Core 2 processor and 8 GB of ram with an 8 disk setup mixing WD Red drives and 2 Seagate 3TB. This is used primarily to archive video footage
I feel like I'm a monkey smashing my head against a keyboard right now cause I'm not all that great at Freenas but have some how managed to make this thing work for the past 5 months even going through various failures and disk upgrades. I just want it to work...

Just to be clear I do have a backup of all the data on external disks but I'm a bit terrified to wipe the system with only a single copy of all my footage.

Could I just go back to 8.2.0 and forget this ever happened?
 

cyberjock

Inactive Account
Joined
Mar 25, 2012
Messages
19,525
If you haven't done a zpool upgrade and you have your config file from before you upgraded you can simply reinstall FreeNAS 8.2 and import your config file.

If you've done the zpool upgrade(you must do this manually from the command line) you MUST use 8.3.0+ to access the zpoool.

The fact that it says ahcich0 makes me think ahci channel 0. It also says port 0. If your ports are numbered I'd look for whatever the first port is and start there first. Maybe take that drive out and do a SMART test on the drive.
 

Shepppard

Dabbler
Joined
Sep 8, 2012
Messages
12
So would it be safe to assume that ADA0 would be in port 0 then? Or just look up on the Mother Board manual to see which SATA port is labeled first? I just want to check before pulling something I'm not supposed to.
My biggest concern is that there are two chipsets on board for the SATA controller based on the fact that the P5Q has Silicon Image Sil5723 RAID as well as a ICH10R Serial ATA Connectors. The Manual says Port 0 and Port 1 for the Silicon Image and the Sata1-6 for the ICH10R Connectors. Thoughts?
 

cyberjock

Inactive Account
Joined
Mar 25, 2012
Messages
19,525
Well, my recommendation would be to do a smartd -a /dev/ada0, write down the serial number and then go looking for which drive has that serial number.
 

Shepppard

Dabbler
Joined
Sep 8, 2012
Messages
12
Oh I have all my drives labeled and know which one is ADA0. I just don't know from the error message I get before the system lockup which drive is at fault. Just tried it again and got this

ahcich0: Timeout on slot 31 port 0

So I'm guessing that the drive that is plugged into AHCICH0 Port 0 is the one that is faulty. How to I associate that error based on the ADA labeling system? ... I only know how to identify my drives based on the GUI cause I'm lame like that
 

paleoN

Wizard
Joined
Apr 22, 2012
Messages
1,402
So I'm guessing that the drive that is plugged into AHCICH0 Port 0 is the one that is faulty.
Stop guessing:
Code:
camcontrol devlist -v

dmesg | grep ahcich0
 

Shepppard

Dabbler
Joined
Sep 8, 2012
Messages
12
Code:
camcontrol devlist -v

dmesg | grep ahcich0


This... thank you for this. I can now fix this
 

cyberjock

Inactive Account
Joined
Mar 25, 2012
Messages
19,525
Stop guessing:
Code:
camcontrol devlist -v

dmesg | grep ahcich0

That's the command I was looking for. I figured someone would pipe up with the answer. Thanks for that paleoN!
 
Status
Not open for further replies.
Top