Solaris 10: Boot Archive

Fixing a boot archive Solaris 10

The procedure in short:
1) Start failsafe boot:
ok boot -F failsafe
when system ask for boot drive selection answer with 'q'
...
Please select a device to be mounted (q for none) [?,??,q]: q
and a shell is starting

2) Mount the single root drive read-only! (use format if not know the root drive)
# mount -o ro /dev/dsk/c0t0d0s0 /a
3) Copy the md.conf file from the root drive to the active boot environment
# cp /a/kernel/drv/md.conf /kernel/drv/
4) Umount the single root drive
# umount /a
5) Update the md driver information
# update_drv -f md
devfsadm: mkdir failed for /dev 0x1ed: Read-only file system
#
6) Important: Wait a minute, it could take some time to configure the md devices!
7) Sync meta information (if not know the SVM root mirror then run metastat)
# metasync d0
8) Mount the SVM mirror
# mount /dev/md/dsk/d0 /a
9) Update the boot archive on the SVM mirror
# bootadm update-archive -v -R /a
some output will be shown
10) Umount SVM root mirror
# umount /a
11) reboot the system from repaired SVM mirror
# init 6

Solaris 10: Open File Handle

Find large files moved or deleted and held open by a process

find /zones/vasuapp013i/root/proc/*/fd -links 0 -type f -size +2000 -ls


This is very helpful in a zones environment when you can't get lsof to work due to security limitations inside a zone.

Solaris 10: Zones IP error

ZONES: The IP address previously set on the network interface is no longer available


If you receive this error message when creating a new zone it indicates that the zones IP is already active on the network. Either change the IP in the zone via zonecfg or resolve the conflict on the network. Once the conflict no longer exists this error should go away inside the zone.