Don't touch your failing drive - I scrolled all the back to the beginning of the thread and it looks like you don't have any redundancy.
If you try to replace the drive it will kill your pool.
It looks like you have talked about 2 servers (home and office) and I thought you were trying to replace a drive that's part of a mirror (office server).
I won't touch the failing drive, I won't try to replace it.
But thanks for the heads up, you confirmed what I was thinking :)
I bought 5 new 4 TB drives and a LSI Internal SAS SATA 9211-8i card.
So it's all new stuff, not touching anything that's already there.
The server has two "roles"... there is one pool that is used for replicating my office data... this pool is alright... no failing drive or anything.
But the other pool is my personal stuff... and that's the pool that has a drive failing.
It has the system dataset, jails, plugins, shares, etc......
My plan is to :
- set up a new RAID-Z2 vdev of 5 drives first.
- Then I want to copy all the files from the existing volume (with the failing drive) to this new volume. I'm thinking to use RSYNC for that. I'm still wondering how to deal with jails and plugins too.
- Then once everything seems OK, I wanted to destroy the pool with the failing drive.
- Then take out the failing drive (that's why I needed the "Display drives identification infos" thing.)
- Then everything is done and my stuff is on the new RAID-Z2 volume... I wanted to re-use the 2 OK drives for something else (I don't know what yet though... because it appears I won't be able to add them to my RAID-Z2 vdev and keep redundancy).