All, Today I completed a maintenance of our big fileserver (345TB). This was caused by an earlier maintenance going bad and trying to get back to a stable/reliable configuration. Long story short - do NOT do a zpool upgrade on your rpool (I think I've mentioned this before but it bears repeating). This caused our system to not reboot without manual intervention that was deep and unreliable. The benefits of a zpool upgrade on your rpool are minuscule at best and not worth the risk. In fixing that issue I've learned another lesson - make certain that your operating system (boot) drives are either 1) attached to the motherboard ports OR 2) sized differently than your data drives. Let me explain. In attempting to fix the "system won't boot past grub command line problem" I tried pretty much everything to be found in google. Nothing worked. Since our data is on a different pool (and different disks) than the OS plan D (yes, 3 times failed) was to simply replace the OS drives and reinstall the os. Did that and would you know- you can't tell the damn data drives from the os drives if they're on the same controller(s) and the same size. Openindiana helpfully displays the device id - but only the first 8 or 10 chars. For SATA disks attached to pci hba cards thats .... all 178 of them. And remember - solaris can't tell you which are the boot drives anyway. Only the BIOS can do that. So - either make them sized differently (I'm using 1TB os drives in a system with 2,3 and 4TB data drives) or attach them direct to the motherboard. My personal preference is to go direct to the motherboard but thats not always an option and not critical. -- Hunter Matthews Unix Administrator Office: Bldg 240 Room 2139 Argonne National Labs, MCS Key: F0F88438 / FFB5 34C0 B350 99A4 BB02 9779 A5DB 8B09 F0F8 8438 Never take candy from strangers. Especially on the internet.