Midwan
Dabbler
- Joined
- Dec 16, 2013
- Messages
- 15
Hi everyone,
I've been using NAS4Free (v9.1.x) for a few years now, running a ZFS pool with 4 disks on a RAIDZ-1 configuration without problems.
I decided to give FreeNAS a try now that the latest version runs on FreeBSD 9.x and the latest ZFS version as well. Since the ZFS version is the same as NAS4Free (v28) I didn't expect to have any problems importing the pool. Note: the ZFS pool is not encrypted.
Unfortunately, when I try the auto-import volumes function from FreeNAS, though it does find the Pool correctly it doesn't import it. Running "zpool import" from the shell gave me the reason why:
Now the interesting thing is that the pool is actually fine, since if I boot back into NAS4Free and run a "zpool status" it shows up without problems:
And of course I can still access all the data there. I tried exporting the pool from NAS4Free to see if that would make a difference (zpool -f export KoulaOne) but the results were the same. I even run a scrub just in case, which came back without any problems mentioned.
So what am I missing here? Is there any difference between the two systems that could cause this specifically?
edit: Forgot to mention, I'm testing FreeNAS version 9.2.0-RC-x64.
I've been using NAS4Free (v9.1.x) for a few years now, running a ZFS pool with 4 disks on a RAIDZ-1 configuration without problems.
I decided to give FreeNAS a try now that the latest version runs on FreeBSD 9.x and the latest ZFS version as well. Since the ZFS version is the same as NAS4Free (v28) I didn't expect to have any problems importing the pool. Note: the ZFS pool is not encrypted.
Unfortunately, when I try the auto-import volumes function from FreeNAS, though it does find the Pool correctly it doesn't import it. Running "zpool import" from the shell gave me the reason why:
Code:
[root@koula ~]# zpool import pool: KoulaOne id: 1976880193882533230 state: UNAVAIL status: One or more devices contains corrupted data. action: The pool cannot be imported due to damaged devices or data. see: http://illumos.org/msg/ZFS-8000-5E config: KoulaOne UNAVAIL insufficient replicas raidz1-0 UNAVAIL insufficient replicas 14963642313260917131 UNAVAIL corrupted data 15112354759630307751 UNAVAIL corrupted data 18090732378555764694 UNAVAIL corrupted data 17259236641428954265 UNAVAIL corrupted data
Now the interesting thing is that the pool is actually fine, since if I boot back into NAS4Free and run a "zpool status" it shows up without problems:
Code:
zpool status pool: KoulaOne state: ONLINE scan: scrub repaired 40K in 6h44m with 0 errors on Mon Dec 9 05:22:44 2013 config: NAME STATE READ WRITE CKSUM KoulaOne ONLINE 0 0 0 raidz1-0 ONLINE 0 0 0 ada0.nop ONLINE 0 0 0 ada1.nop ONLINE 0 0 0 ada2.nop ONLINE 0 0 0 ada3.nop ONLINE 0 0 0 errors: No known data errors
And of course I can still access all the data there. I tried exporting the pool from NAS4Free to see if that would make a difference (zpool -f export KoulaOne) but the results were the same. I even run a scrub just in case, which came back without any problems mentioned.
So what am I missing here? Is there any difference between the two systems that could cause this specifically?
edit: Forgot to mention, I'm testing FreeNAS version 9.2.0-RC-x64.