search for: rpool2

...around for the problem described in Unable to mount root pool dataset http://opensolaris.org/jive/thread.jspa?messageID=492460 Since the Blade 1500''s rpool is mirrored, I''ve decided to detach the second half of the mirror, relabel the disk, create an alternative rpool (rpool2) there, copy the current BE (snv_134) using beadm create -p rpool2 snv_be-pkg143, activate the new BE and boot from the second disk. Unfortunately, this doesn''t work: the kernel panics with Can not read the pool label from <device> spa_import_rootpool: Error 5 I''...

Hi, I have a zfs root Solaris 10 running on my home server. I created an ISCSI target in the following way: # zfs create -V 1g rpool2/iscsivol Turned on the shareiscsi property # zfs set shareiscsi=on rpool2/iscsivol # zfs list rpool2/iscsivol NAME USED AVAIL REFER MOUNTPOINT rpool2/iscsivol 18K 19.9G 18K rpool2/iscsivol I am run...

I had the rpool with two sata disks in the miror. Solaris 10 5.10 Generic_141415-08 i86pc i386 i86pc Unfortunately the first disk with grub loader has failed with unrecoverable block write/read errors. Now I have the problem to import rpool after the first disk has failed. So I decided to do: "zpool import -f rpool" only with second disk, but it''s hangs and the system is

Hello, I have a situation where a host, which is booted off its ''rpool'', need to temporarily import the ''rpool'' of another host, edit some files in it, and export the pool back retaining its original name ''rpool''. Can this be done ? Here is what I am trying to do: # zpool import -R /a rpool temp-rpool # zfs set mountpoint=/mnt

...2. Can anyone advise .. why I am unable to read the third and forth vdev labels once the start and end files are combined? Is there another approach that may prove more fruitful? Once I have the file (with labels being in the correct places) I was intending to attempt to import the vdev zpool as rpool2 or attempt any repair procedures I could locate (as far as was possible anyway) to see what data could be recovered (besides it was an opportunity to get another close look at ZFS). Incidentally *only* the c7t0d0s0 slice appeared to have bad sectors (I do wonder what the significance is of this?)....