I have 4 of these messages being reported on my UNRAID Dashboard this morning:

 

 

I presume that this means the SSD is failing and needs to be replaced immediately, or is it possible that it's just a cable gone bad?

 

nas-diagnostics-20211022-0649.zip

 

That's not cable related, a SMART attribute is failing now, so yes, it should be replaced.

That's not cable related, a SMART attribute is failing now, so yes, it should be replaced.

Happy Halloween to me then. I guess I get to go shopping.

Now I need to figure out when I bought that drive and see if there's any warranty left on it.

Thanks

Sent from my moto g(7) using Tapatalk

@JorgeB now that I've got my replacement SSD, just to confirm:

 

1. Set all shares using this cache pool to "yes" (from "Prefer" or "Only")

2. Stop all dockers (appdata is the main thing on the cache and I don't want dockers trying to write there while the rest of this happens)

3. Run the mover to get everything off the cache

4. Physically swap out the drive

5. Rebuild the cache pool (since a drive will have been removed, it won't recognize it properly and will want to do that, right?)

6. Set all shares using the pool back to cache: "Prefer" or "Only", as they were originally

7. Run the mover to get everything back to the pool

7. Restart dockers.

Just now, FreeMan said:

@JorgeB now that I've got my replacement SSD, just to confirm:

 

1. Set all shares using this cache pool to "yes" (from "Prefer" or "Only")

2. Stop all dockers (appdata is the main thing on the cache and I don't want dockers trying to write there while the rest of this happens)

3. Run the mover to get everything off the cache

4. Physically swap out the drive

5. Rebuild the cache pool (since a drive will have been removed, it won't recognize it properly and will want to do that, right?)

6. Set all shares using the pool back to cache: "Prefer" or "Only", as they were originally

7. Run the mover to get everything back to the pool

7. Restart dockers.

In step 2 you need to actual stop the docker and VM services as otherwise they will keep file open that mover is then unable to move.

2 minutes ago, itimpi said:

In step 2 you need to actual stop the docker and VM services as otherwise they will keep file open that mover is then unable to move.

Ah, gotcha, the service itself, not just the dockers.

 

Thank you!

 

And this is why I double check... Happily, UNRAID and my hardware are stable enough that I don't often deal with these things...