YourLocalGP
Cadet
- Joined
- Feb 9, 2014
- Messages
- 2
Hi all.
I am running FreeNAS 9.1 at home in an amateurish PC-case. Recently I had to change a component in the machine, and in doing so I managed to damage one of the SATA ports of a PCIe SATA card. It had a sata cable attached before the clumsiness, and now the cable won't stay attached.
That same card has a spare SATA port on it, so I plugged the SATA lead into that one instead, admitting defeat with the broken connector.
The problem is that I can't bring the drive back online using zpool, because as far as ZFS is concerned there's no drive in that port. I have tried offlining and onlining the pool, thinking that if I moved the disks to new hardware then logically ZFS would need to accept different interfaces. This just resulted in the online operation bringing about the same situation before - one of the disks being marked "UNAVAIL".
I don't think I can use the "replace" command either as it too is for replacing a failed drive on the same port and interface as the failed drive.
Anyone's advice on how to solve this would be very appreciated.
Thanks
YLGP
I am running FreeNAS 9.1 at home in an amateurish PC-case. Recently I had to change a component in the machine, and in doing so I managed to damage one of the SATA ports of a PCIe SATA card. It had a sata cable attached before the clumsiness, and now the cable won't stay attached.
That same card has a spare SATA port on it, so I plugged the SATA lead into that one instead, admitting defeat with the broken connector.
The problem is that I can't bring the drive back online using zpool, because as far as ZFS is concerned there's no drive in that port. I have tried offlining and onlining the pool, thinking that if I moved the disks to new hardware then logically ZFS would need to accept different interfaces. This just resulted in the online operation bringing about the same situation before - one of the disks being marked "UNAVAIL".
I don't think I can use the "replace" command either as it too is for replacing a failed drive on the same port and interface as the failed drive.
Anyone's advice on how to solve this would be very appreciated.
Thanks
YLGP