Chris Cantwell
Cadet
- Joined
- Apr 3, 2012
- Messages
- 2
I have two SATA hard drives that had a FreeBSD 8.1 installation on them (UFS, geom mirror), and I wanted to reuse them for FreeNAS. On my system, the CF reader, the DVD drive and the two hard drives are installed on separate SATA ports.
I downloaded and installed FreeNAS 8.0.4 on a 4GB CF card. I successfully accessed the FreeNAS web GUI from another computer on my network. I then tried to create a ZFS mirrored disk volume using the two SATA hard drives using the volume name "test". At first it looked like it worked, and the volume was displayed on the left side under "Volumes" as /mnt/test, but the volume was not displayed on the right side, and an error message on the top menu bar said "An error occurred!" I tried creating different ZFS volume configurations, and different UFS volume configuration, with identical results. I then connected a blank hard drive to the system, and was able to create a ZFS volume right away with no errors.
It appears that FreeNAS will not erase an existing FreeBSD UFS configuration when creating a new disk volume. Has anyone else seen this error? I imagine it would work if I erased the disk first, but I shouldn't have to do that.
Thanks,
Chris
I downloaded and installed FreeNAS 8.0.4 on a 4GB CF card. I successfully accessed the FreeNAS web GUI from another computer on my network. I then tried to create a ZFS mirrored disk volume using the two SATA hard drives using the volume name "test". At first it looked like it worked, and the volume was displayed on the left side under "Volumes" as /mnt/test, but the volume was not displayed on the right side, and an error message on the top menu bar said "An error occurred!" I tried creating different ZFS volume configurations, and different UFS volume configuration, with identical results. I then connected a blank hard drive to the system, and was able to create a ZFS volume right away with no errors.
It appears that FreeNAS will not erase an existing FreeBSD UFS configuration when creating a new disk volume. Has anyone else seen this error? I imagine it would work if I erased the disk first, but I shouldn't have to do that.
Thanks,
Chris