Ok, that doesn't seem to have worked so well ...

I took one of the drives offline, rebooted and it just hangs at the splash 
screen after prompting for which BE to boot into.   
It gets to 
hostname: blah
and just sits there.

Um ...

I read some doco that says :

The boot process can be slow if the boot archive is updated or a dump device 
has changed. Be patient.

(from 
http://www.solarisinternals.com/wiki/index.php/ZFS_Troubleshooting_Guide#Disk_Replacement_Example)
DO I need to just wait and it'll come up eventually or do I need to do 
something more constructive?  There's no drive activity after an initial flurry 
for ~1-2 mins or so. It's just hanging.

I kinda need this box up, nothing on it is irreplaceable but it'll be a major 
PITA if I lose it.  Can the root pool be mounted in some form on another box 
and the data from it be retreived?  It's running a more current zpool version 
than 200906 (whatever's current in b134) - maybe if I crank up an openIllumos 
or whatever it's called and see if that can mount the drives somehow?
-- 
This message posted from opensolaris.org
_______________________________________________
zfs-discuss mailing list
zfs-discuss@opensolaris.org
http://mail.opensolaris.org/mailman/listinfo/zfs-discuss

Reply via email to