In message <ds0pr08mb91402c336b23aa3985ebb172ed...@ds0pr08mb9140.namprd08.prod. outlook.com>, "Mooney, Tim via openindiana-discuss" writes: > > zpool import -f rpool -R /mnt/rpool/ > >That did succeed and I could see the non-OS datasets for /usr/local , the home > dir filesystem and one other, but what I didn't see was /, /usr, or /var.
If you wish to inspect the BEs, you should mount them: <URL:https://docs.openindiana.org/handbook/getting-started/?h=beadm#beadm-command-reference> >One other thing stuck out about the boot environments. I'm not great about cl >eaning up old boot environments so I have a bunch of them. Most of them are i >n the 50-250 MB range in size. The boot environment that got created as part >of the 'pkg update' that preceded this mess says its 575 GB (not MB, GB). Tha >t seems suspicious. Once your scrub completes, check if the pool is full. If it is, maybe activate an earlier BE, boot it milestone=none and then destroy the errant, latest BE. John groenv...@acm.org _______________________________________________ openindiana-discuss mailing list openindiana-discuss@openindiana.org https://openindiana.org/mailman/listinfo/openindiana-discuss
