Hi,
I am running FreeNAS-9.3-STABLE-201512121950 on an AsRock motherboard with 16 GB ECC RAM and Intel(R) Atom(TM) CPU C2550 @ 2.40GHz. I had an encrypted RAID-10 zpool consisting of 4 SSDs (Samsung 256 GB). However, the disks were giving problems (one of them got the pool degraded, others gave CAM errors) so I decided to replace them one by one with traditional HDDs (WD 2TB). I did this by first matching the geli GUID with the serial number of the disk (using), taking one of the disks offline, shutting down the server, checking which serial number matched the geli GUID, and when I found the correct disk, replace it by a fresh HDD. After bringing up the server, I unlocked the zpool, then replaced the disk on the CLI (using ).
After this, the zpool was resilvered automatically and was working fine after that. Over a period of a few days it did this four times, which involved lots of reboots/shutting down the server, without any problem. I did notice that no longer specified geli devices, but /dev/ada0 to /dev/ada3. But I did not realize I had made a big mistake by not following the correct procedure for disk replacement of encrypted zpools; I didn't know that there was a special procedure for this.
However, all was fine until I decided to apply the latest updates. After reboot, the GUI told me underneath the tab 'Storage' that my pool said "0 (error)" under 'used' and "Error getting available space" under 'Available'. Status is LOCKED. I tried to detach the volume, import and export it in the CLI, but it does not appear in the GUI anymore. When I try to import it in the GUI, it cannot find encrypted disks so it blocks on step 2.
in sqlite3 returns nothing.
Since the zpool survived lots of shutdowns before the upgrade, I tried rebooting the previous freenas version, but that didn't resolve the situation.
My data is not accessible now. Is there any way I can fix this issue (that I have caused myself, I know...)?
I have included the debug.log (my nas is called "nas3" and the zpool is called "ssds"). The HDDs are recognized in freenas; see CAMCONTROL output.txt.
Thanks a lot,
Edwin.
I am running FreeNAS-9.3-STABLE-201512121950 on an AsRock motherboard with 16 GB ECC RAM and Intel(R) Atom(TM) CPU C2550 @ 2.40GHz. I had an encrypted RAID-10 zpool consisting of 4 SSDs (Samsung 256 GB). However, the disks were giving problems (one of them got the pool degraded, others gave CAM errors) so I decided to replace them one by one with traditional HDDs (WD 2TB). I did this by first matching the geli GUID with the serial number of the disk (using
Code:
glabel -status
Code:
zpool replace <zpool name> <device name>
After this, the zpool was resilvered automatically and was working fine after that. Over a period of a few days it did this four times, which involved lots of reboots/shutting down the server, without any problem. I did notice that
Code:
zpool status
However, all was fine until I decided to apply the latest updates. After reboot, the GUI told me underneath the tab 'Storage' that my pool said "0 (error)" under 'used' and "Error getting available space" under 'Available'. Status is LOCKED. I tried to detach the volume, import and export it in the CLI, but it does not appear in the GUI anymore. When I try to import it in the GUI, it cannot find encrypted disks so it blocks on step 2.
Code:
select * from storage_encrypteddisk;
Since the zpool survived lots of shutdowns before the upgrade, I tried rebooting the previous freenas version, but that didn't resolve the situation.
My data is not accessible now. Is there any way I can fix this issue (that I have caused myself, I know...)?
I have included the debug.log (my nas is called "nas3" and the zpool is called "ssds"). The HDDs are recognized in freenas; see CAMCONTROL output.txt.
Thanks a lot,
Edwin.