CLI shows constant resilvering, GUI does not.

[fullspeed]

I think I initiated a resilver a month ago on this box (from the GUI) and it's been infinitely resilvering since then.. How can i fix/stop this? I read somewhere that offlining the disk would stop it but im not sure if that is a good idea.

If I log into the GUI I see this:

CLI shows this:

 

[Ericloewe]

Ooh, that vdev is a bit too wide...

In any case, you'll need to share more details for useful advice. This is an unusual situation...

 

[fullspeed]

Ooh, that vdev is a bit too wide...

In any case, you'll need to share more details for useful advice. This is an unusual situation...

It's two disks wider than I would like but I have eight of these and they are working great actually, aside from this odd problem.

This server was working fine for a few months then I initiated a replacement and this happened..

Now for details... I can tell you that:

- Freenas version is FreeNAS-9.3-STABLE-201605170422 (on all eight nodes)
- Server info is in my sig (this one is 64GB ram)
- I'm replicating to an identical box
- I'm running snapshots every 4 hrs for a week which are pruning properly, no issues

Storage (in a health state in gui)

I have these tunables (which are on all eight nodes)

CLI shows degraded

I see these errors, which is obviously a problem and I can deal with that disk, but why would GUI be telling me I'm in a healthy state? it's clearly trying to replace a disk and failing indefinately, I'll have to tail to logs and look for errors.. but for now im a bit baffled.

 

[Ericloewe]

Hmm, I just noticed you're using SAS3. Given its bleeding edge reputation, I'd advise you to upgrade to FreeNAS 9.10, which has the updated driver, and flash the controllers to match.

 

[fullspeed]

Hmm, I just noticed you're using SAS3. Given its bleeding edge reputation, I'd advise you to upgrade to FreeNAS 9.10, which has the updated driver, and flash the controllers to match.

I did test 9.10 initially and reverted because I couldn't disable SSH cyphers, I needed that extra speed for the inital replication sync. I suppose now that's completed I could upgrade all my nodes but I'm not convinced that's the problem here. Hopefully someone has seen this before.. or knows how to stop this phantom replacement?