Hi Paul,
> # fdisk -E /dev/rdsk/c7t0d0s2
then
> # zpool create -f Radical-Vol /dev/dsk/c7t0d0
should work. The warnings you see are just there to double-check you don't
overwrite any previously used pool which you may regret. -f overrules that.
Hope this helps,
Constantin
--
Constantin G
I did some work over the weekend. Still is having some trouble.
# fdisk -E /dev/rdsk/c7t0d0s2
# zpool create Radical-Vol /dev/dsk/c7t0d0
invalid vdev specification
use '-f' to override the following errors:
/dev/dsk/c7t0d0s0 is part of exported or potentially active ZFS pool
Radical-Vol. Please
Hello Paul,
Wednesday, December 5, 2007, 10:34:47 PM, you wrote:
PG> Constantin Gonzalez wrote:
>> Hi Paul,
>>
>> yes, ZFS is platform agnostic and I know it works in SANs.
>>
>> For the USB stick case, you may have run into labeling issues. Maybe
>> Solaris SPARC did not recognize the x64 type l
Hi,
> # /usr/sbin/zpool import
> pool: Radical-Vol
> id: 3051993120652382125
> state: FAULTED
> status: One or more devices contains corrupted data.
> action: The pool cannot be imported due to damaged devices or data.
>see: http://www.sun.com/msg/ZFS-8000-5E
> config:
>
> Radi
Constantin Gonzalez wrote:
> Hi Paul,
>
> yes, ZFS is platform agnostic and I know it works in SANs.
>
> For the USB stick case, you may have run into labeling issues. Maybe
> Solaris SPARC did not recognize the x64 type label on the disk (which
> is strange, because it should...).
>
> Did you try
Hi Paul,
yes, ZFS is platform agnostic and I know it works in SANs.
For the USB stick case, you may have run into labeling issues. Maybe
Solaris SPARC did not recognize the x64 type label on the disk (which
is strange, because it should...).
Did you try making sure that ZFS creates an EFI label
