There's definately something strange going on as these are the only uberblocks
I can find by scanning /dev/dsk/c0t0d0s7 - nothing to conflict with my theory
so far:
TXG: 106052 TIME: 2009-01-04:11:06:12 BLK: 0e29000 (14848000) VER: 10 GUID_SUM:
9f8d9ef301489223 (11497020190282519075)
TXG: 10605
After having a think I've come up with the following hypothesis:
1) When I was on Solaris 10u4 things were working fine.
2) When I re-installed with Solaris 10u6 and imported the zpool (with zpool
import -f), it created a zpool.cache file and didn't update the on disk data
structures for some re
I wonder if your problem is related to mine:
(can't import zpool after upgrade to solaris 10u6 -
http://www.opensolaris.org/jive/thread.jspa?messageID=324994#324994).
What does zdb -l give you?
zdb -l /dev/dsk/c1d1
zdb -l /dev/dsk/c2d0
zdb -l /dev/dsk/c2d1
-Steve
--
This message posted from op
Here's what I did:
* had a t1000 with a zpool under /dev/dsk/c0t0d0s7 on solaris 10u4
* re-installed with solaris 10u6 (disk layout unchanged)
* imported zpool with zpool import -f (I'm forever forgetting to export them
first) - this was ok
* re-installed with solaris 10u6 and more up-to-date patc
