SOLVED Update from 11.0-U4 to 11.1 now reports DEGRADED status on pool

Status
Not open for further replies.

Ericloewe

Server Wrangler
Moderator
Joined
Feb 15, 2014
Messages
20,194
smartctl -a /dev/ada2 | grep Serial
 

Ericloewe

Server Wrangler
Moderator
Joined
Feb 15, 2014
Messages
20,194
Then why did you ask how to identify them?

Thought maybe there was something more that could be done.
The drives themselves look fine. Replace dubious cables and scrub the pool.
 

wblock

Documentation Engineer
Joined
Nov 14, 2014
Messages
1,506
smartctl -a /dev/ada2 | grep Serial

That has been recommended for years, but the easier way is diskinfo -v ada2 | grep ident.
 

wblock

Documentation Engineer
Joined
Nov 14, 2014
Messages
1,506

wblock

Documentation Engineer
Joined
Nov 14, 2014
Messages
1,506
Water cooling, giant fans, add-on fan controllers, LED lighting, 97-button mice, that sort of thing. Some of those things have specific applications for gaming, but not so much for a NAS.
 

Redcoat

MVP
Joined
Feb 18, 2014
Messages
2,925
Overclocking?
 

wblock

Documentation Engineer
Joined
Nov 14, 2014
Messages
1,506
Oh yes, definitely that too.
 

danb35

Hall of Famer
Joined
Aug 16, 2011
Messages
15,504
Also there is nothing more that I can do at this point then other than replacing it?
Swap cables, swap motherboard ports, possibly swap power cables. I'm pretty sure all this is covered in @joeschmuck's guide.
 

André Fettouhi

Contributor
Joined
Nov 12, 2016
Messages
108
Well the scrub of the whole pool just completed and it just writes

Code:
Errors: 0			 Repaired: 122M
 
Last edited by a moderator:

Redcoat

MVP
Joined
Feb 18, 2014
Messages
2,925
See the manual section 8.1.10, point 1. "If there is no Offline button but only a Replace button, the disk is already offlined and this step can be skipped."
 

André Fettouhi

Contributor
Joined
Nov 12, 2016
Messages
108
Well, I went through everything again on the server. Checked the connections again and pulled all the drives out in order to find out which drive was causing the issue. After identifying the problematic drive I turned the server on again. Now it reports the whole pool and the drive as healthy. No checksum errors at all and it has been running for 5 hours now. The new drive I ordered also arrived today, so I can switch the drive at any time. Bit unsure if I should replace it anyway now or just way and see it if the issue returns? I am getting though every two minutes in the console this warning

Code:
2017/12/18 14:49:09 [WARN] agent: Check 'service:nas-health' is now warning


Looking at the FreeNAS bugtracker this seems to be reported as bug. Or should I be concerned about this?
 
Last edited by a moderator:

Redcoat

MVP
Joined
Feb 18, 2014
Messages
2,925
No, do not be concerned about that message.

It sounds as if replugging your drive may have eliminated the issue. I would run the SMART tests on the drive again. if it checks out OK I would continue to run the server and monitor it for any recurrence of issues.
 

SweetAndLow

Sweet'NASty
Joined
Nov 6, 2013
Messages
6,421
Well, I went through everything again on the server. Checked the connections again and pulled all the drives out in order to find out which drive was causing the issue. After identifying the problematic drive I turned the server on again. Now it reports the whole pool and the drive as healthy. No checksum errors at all and it has been running for 5 hours now. The new drive I ordered also arrived today, so I can switch the drive at any time. Bit unsure if I should replace it anyway now or just way and see it if the issue returns? I am getting though every two minutes in the console this warning

Code:
2017/12/18 14:49:09 [WARN] agent: Check 'service:nas-health' is now warning


Looking at the FreeNAS bugtracker this seems to be reported as bug. Or should I be concerned about this?
I would just leave the drive and keep an eye on it. Making sure you have smart tests enabled and email notifications. You should also burn in that new drive to make sure it's actually ok to use.
 
Last edited by a moderator:

André Fettouhi

Contributor
Joined
Nov 12, 2016
Messages
108
Ran smart tests on the drive again and it came up clean. So I added the drive back into the weekly smart tests again and leave it as it is for now.
 
Status
Not open for further replies.
Top