Example to update the boot archive via failsafe boot on sparc systems with conf igured SVM root

mirror. 1.) Start failsafe boot: {1} o boot -F failsafe Boot device: /pci@1f,700000/scsi@2/dis @0,0:a File and args: -F failsafe SunOS Release 5.10 Version Generic_137137-09 64-bit Copyright 1983-2008 Sun Microsystems, Inc. All rights reserved. Use is subject to license terms. Hardware watchdog enabled Configuring devices. Searching for installed OS instances... SUNW,qfe0: 100 Mbps full duplex lin up - internal transceiver SUNW,qfe1: 100 Mbps full duplex lin up - internal transceiver /dev/ds /c3t0d0s0 is under md control, s ipping. 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 <mount_point> /dev/ds /c3t2d0s0 is under md control, s ipping. 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 <mount_point> Multiple OS instances were found. To chec and mount one of them read-write under /a, select it from the following list. To not mount any, select 'q'. 1 /dev/ds /c0t256000C0FFC048BDd0s0 2 /dev/ds /c1t216000C0FF8048BDd0s0

Please select a device to be mounted (q for none) [?,??,q]: q Note: Be careful at this state. Maybe the displayed the boot devices are NOT the boot devices from the used root mirror. The output of the failsafe boot can be confusing at this state. Answer the question with 'q' to jump into the shell... Starting shell. #

2.) Mount the single root drive read-only! (use format if not now the root driv e)

AVAILABLE DISK SELECTIONS: ... 41. c1t216000C0FF8048BDd20 <SUN-StorEdge3510-415F cyl 6380 alt 2 hd 64 sec 32> /pci@1d,700000/SUNW,qlc@1,1/fp@0,0/ssd@w216000c0ff8048bd,14

Run format to find root dis # format Searching for dis s...done

if not already nown...

Solaris 10 10/09 s10s_u8wos_08a SPARC Solaris 10 10/09 s10s_u8wos_08a SPARC

42. c3t0d0 <SUN72G cyl 14087 alt 2 hd 24 sec 424> /pci@1f,700000/scsi@2/sd@0,0 43. c3t2d0 <SUN72G cyl 14087 alt 2 hd 24 sec 424> /pci@1f,700000/scsi@2/sd@2,0 44. c3t3d0 <SEAGATE-ST373307LC-0007-68.37GB> /pci@1f,700000/scsi@2/sd@3,0 Specify dis (enter its number): ^D Mount one of the root drive read-only... # mount -o ro /dev/ds /c3t0d0s0 /a Chec release if the correct devices is used... # more release Solaris 10 10/08 s10s_u6wos_07b SPARC Copyright 2008 Sun Microsystems, Inc. All Rights Reserved. Use is subject to license terms. Assembled 27 October 2008

3.) Copy the md.conf file from the root drive to the active boot environment If li e chec entries of md.conf file... # more /a/ ernel/drv/md.conf Copy md.conf to active boot environment... # cp /a/ ernel/drv/md.conf / ernel/drv/

4.) Umount the single root drive # umount /a

5.) Update the md driver information # update_drv -f md devfsadm: m dir failed for /dev 0x1ed: Read-only file system

6.) Important: Wait a minute, it could ta e some time to configure the md device s! If not wait the following can came up... # metasync d10 metasync: d10: No such file or directory

7.) Sync meta information (if not now the SVM root mirror run metastat) # metasync d10

Verify/Chec # metadb # metastat

SVM config by using, or if not now the md mirror device number...

8.) Mount the SVM mirror # mount /dev/md/ds /d10 /a

9.) Update the boot archive on the SVM mirror Chec size of boot_archive file... # ls -l /a/platform/sun4u/boot_archive -rw-r--r-- 1 root root 125140992 Jun 25 07:52 boot_archive # bootadm update-archive -v -R /a new /a/platform/sun4v/ ernel/crypto/sparcv9/arcfour2048 cannot find: /a/etc/mach: No such file or directory Creating boot_archive for /a updating /a/platform/sun4u/boot_archive 15+0 records in 15+0 records out Chec if size of boot_archive file have changed... # ls -l /a/platform/sun4u/boot_archive -rw-r--r-- 1 root root 221184000 Jul 1 09:02 boot_archive Note: If problem within the update the option -f is possible to force the update e.g.: 'bootadm update-archive -v -f -R /a' 10.) Umount SVM root mirror # umount /a

11.) reboot the system from repaired SVM mirror # init 6 # The system is being restarted. syncing file systems... done rebooting...

-This page is from http://blogs.sun.com/js/category/Solaris =========================================== Example to update the boot archive via failsafe boot on sparc systems with conf igured SVM root mirror By JuergenS on Jul 05, 2010 Since Solaris 10 10/08 update6 the boot archive feature was implemented into Sol aris 10 for sparc. When the system is configured with Solaris Volume Manager (SV M) root mirror then attention is necessary if using the failsafe boot (boot -F f ailsafe) on the 'o prompt' environment.

In case of the following or similar message it could be necessary to use the Sol aris failsafe boot: Rebooting with command: boot Boot device: dis :a File and args: SunOS Release 5.10 Version Generic_141414-07 64-bit Copyright 1983-2009 Sun Microsystems, Inc. All rights reserved. Use is subject to license terms. Hardware watchdog enabled Hostname: scnode1 WARNING: The following files in / differ from the boot archive: changed / ernel/drv/did.conf The recommended action is to reboot to the failsafe archive to correct the above inconsistency. To accomplish this, on a GRUB-based platform, reboot and select the "Solaris failsafe" option from the boot menu. On an OBP-based platform, reboot then type "boot -F failsafe". Then follow the prompts to update the boot archive. Alternately, to continue booting at your own ris , you may clear the service by running: "svcadm clear system/boot-archive" Jun 29 15:51:28 svc.startd[8]: svc:/system/boot-archive:default: Method "/lib/sv c/method/boot-archive" failed with exit status 95. Jun 29 15:51:28 svc.startd[8]: system/boot-archive:default failed fatally: trans itioned to maintenance (see 'svcs -xv' for details) Requesting System Maintenance Mode (See /lib/svc/share/README for more information.) Console login service(s) cannot run Root password for system maintenance (control-d to bypass): Normally after this message the issue can be solved by a) login into system b) run "svcadm clear system/boot-archive" c) wait until system continuing the boot up The system is already booted from the SVM root mirror and the svcadm clear comma nd goes to all used devices within the root mirror. But when this is not successful then it's necessary to do a Solaris failsafe boo t. Now the issue is that the failsafe boot is not mounting the SVM root mirror a nd manual intervention is necessary to update the boot archive on all devices wi thin the SVM root mirror. This procedure does NOT require to unmirror the SVM ro ot mirror to update the boot archive. The procedure in short: 1) Start failsafe boot: o boot -F failsafe when system as 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 now the root drive ) # mount -o ro /dev/ds /c0t0d0s0 /a 3) Copy the md.conf file from the root drive to the active boot environment # cp /a/ ernel/drv/md.conf / ernel/drv/

4) Umount the single root drive # umount /a 5) Update the md driver information # update_drv -f md devfsadm: m dir failed for /dev 0x1ed: Read-only file system # 6) Important: Wait a minute, it could ta e some time to configure the md devices ! 7) Sync meta information (if not now the SVM root mirror then run metastat) # metasync d0 8) Mount the SVM mirror # mount /dev/md/ds /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