# grep Solaris /etc/release Solaris 10 6/06 s10x_u2wos_09a X86 # uname -a Sun OS salsa 5.10 Generic_125101-10 i86pc i386 i86pc # df -kh / /opt Filesystem size used avail capacity Mounted on /dev/md/dsk/d20 7.9G 4.5G 3.3G 59% / /dev/md/dsk/d23 7.9G 369M 7.4G 5% /opt # metastat -p d20 d20 -m d10 d30 1 d10 1 1 c0d0s0 d30 1 1 c1d0s0 # metastat -p d23 d23 -m d13 d33 1 d13 1 1 c0d0s3 d33 1 1 c1d0s3 filesystem (as all production systems should), we'd take care of that as well.
There are ditches to dig, outbuildings to erect, trees to fell, slash to burn, livestock to husband, fences to string, game to hunt, and garden plots to dig, plant, and harvest, to say nothing of the ordinary joys of home ownership and the added labours of independent off-grid living.I let it sit for a moment, then began to power up the system. y FRAG BITMAP WRONG (CORRECTED) CORRECTED SUMMARY FOR CG 4 CORRECTED SUMMARY FOR CG 12 CORRECTED SUMMARY FOR CG 30 CORRECTED SUMMARY FOR CG 70 CORRECT GLOBAL SUMMARY SALVAGE? A further delve into google reveals that I need to recreate the ramdisks for boot. To manually recover the boot archive on a root mirror,mount the first side (the one that the system boots from) and run: bootadm update-archive -R umount: /a busy No installed OS instance found. y UNREF FILE I=1458 OWNER=root MODE=100644 SIZE=675 MTIME=May 15 2008 RECONNECT?y Log was discarded, updating cyl groups 46737 files, 1720899 used, 24099860 free (21460 frags, 3009800 blocks, 0.1% fragmentation) ***** FILE SYSTEM WAS MODIFIED ***** CRAP! A boot into failsafe mode again, allows me to fsck c2t0d0s0, which is mounted on /a, and remount it -o rw.bootadm update-archive fails, due to fs inconsistency.Another fcsk, we're in single user, nothing is using that disk, so I just ran the fsck without remounting -o ro.