>
> zpool import -fF -R / tank
>
As above victor managed to mock up a log device and get the pool to a state
where it could be imported again. Awesome stuff. I'm also interested in how if
its not too complex. :)
Unfortunately though it looks like something is still not quite right. Even
thou
Hi George,
I think you are right. The log device looks to have suffered a complete loss,
there is no data on the disk at all. The log device was a "acard" ram drive
(with battery backup), but somehow it has faulted clearing all data.
--victor gave me this advice, and queried about the zpool.c
I'm at a loss, I've managed to get myself into a fix. I'm not sure where the
problem is, but essentially i have a zpool i cannot import. This particular
pool used to have a two drives (not shown below), one for cache and another for
log. I'm unsure why they are no longer detected on zpool import
i have re run zdb -l /dev/dsk/c9t4d0s0 as i should have the first time (thanks
Nicolas).
Attached output.
--
This message posted from opensolaris.org# zdb -l /dev/dsk/c9t4d0s0
LABEL 0
version=14
nam
Hi Victor, i have tried to re-attach the detail from /var/adm/messages
--
This message posted from opensolaris.orgOct 11 17:16:55 opensolaris unix: [ID 836849 kern.notice]
Oct 11 17:16:55 opensolaris ^Mpanic[cpu0]/thread=ff000b6f7c60:
Oct 11 17:16:55 opensolaris genunix: [ID 361072 kern.noti
Hi Ian, I'm currently downloading build 124 to see if that helps... the
download is running a bit slow so wont know until later tomorrow.
Just an update that i have also tried; (forgot to mention above)
* Pulling out each disk - tried mounting in degraded state - same kernel
panic
*
I have searched the forums and google wide, but cannot find a fix for the issue
I'm currently experiencing. Long story short - I'm now at a point where I
cannot even import my zpool (zpool import -f tank) without causing a kernel
panic
I'm running OpenSolaris snv_111b and the zpool is version 1
