1. Replace and partition the disk if it has failed.

2. Because the system cannot be booted from the boot disk, boot from the CD-ROM and re-create the failed file system by issuing the newfs command:

newfs /dev/rdsk/

is the name of the raw disk partition that contains the corrupted file system.

3. Check the new file system by using fsck:

fsck /dev/rdsk/

4. Mount the new file system on a temporary mount point:

mount /dev/dsk//mnt

5. Change to the /mnt directory:

cd /mnt

6. Write protect the tapes so that you don’t accidentally overwrite them.

7. Load the tape and issue the following command:

ufsrestore rf /dev/rmt/0

The entire content of the tape is restored to the file system. All permissions, ownerships, and dates remain as they were when the last incremental tape was created.

8. Verify that the file system is restored:

ls

9. Remove the restoresymtable file that is created and used by ufsrestore to checkpoint the restoration:

rm restoresymtable

10. Change to the root (/) directory:

cd /

11. Unmount the newly created file system:

umount /mnt

12. Check the new file system with fsck:

fsck /dev/rdsk/

The restored file system is checked for consistency.

13. If you are recovering the root (/) file system, create the boot blocks on the root partition by using the installboot command:

installboot /usr/platform/’uname-I’/lib/fs/ufs/bootblk\
/dev/rdsk/

The installboot command installs the boot blocks onto the boot disk. Without the boot blocks, the disk cannot boot.

14. Insert a new tape into the tape drive and back up the new file system:

ufsdump 0uf /dev/rmt/n /dev/rdsk/

A level 0 backup is performed. You should immediately make a backup of a newly created file system because ufsrestore repositions the files and changes the inode allocation.

15. Reboot the system with a reconfiguration reboot:

# shutdown -y -g0 -i0
ok boot -r

The system is rebooted.

Extra Notes on UFSrestore

When you restore files in a directory other than the root directory of the file system, ufsrestore re-creates the file hierarchy in the current directory. For example, if you restore to /home files that were backed up from /users/bcalkins/files, the files are restored in the directory /home/users/bcalkins/files.

When you restore individual files and directories, it’s a good idea to restore them to a temporary directory such as /var/tmp. After you verify that you’ve retrieved the correct files, you can move them to their proper locations. You can restore individual files and directories to their original locations; however, if you do so, you should be sure that you do not overwrite newer files with older versions from the backup tape.

You should not forget to make regular backups of your operating system. Losing all the customization you dosuch as adding user accounts, setting up printers, and installing application softwarewould be disastrous. Whenever you make modifications that affect the root (/),/usr, /opt, or other operating system directories, you should bring down the system into single-user mode and perform a level 0 dump.

you can edit the entries in the /etc/syslog.conf to direct to another file eg /var/log/syslog instead of /dev/console. After that, issue kill -HUP to “reinitialize” the config

or if you want to stop syslog process/daemon in Solaris 10, (not /etc/init.d/syslog stop)

it should be

svcadm disable svc:/system/system-log:default

svcadm disable svc:/system/system-log:default turned syslog off you need to also run svcadm enable svc:/system/system-log:default to turn it back on, after you made the right changes to /etc/syslog.conf so it does what you want. You can probably just comment out the line as it is also logged to file in /var/adm/messages.log

Turning syslog off is not a good idea.

That’s is How to Stop syslog Messages to Write Console on Solaris.

To be honest, this is the steps that really made me understood the steps and procedure and the concept behind the 10_Recommended patch for solaris kernel.

So, here it is:

Check Boot Disk

This step is to check which disks are the member of the boot mirror. We can say that this is the check disk mirror / disk membership step


# df -h /
Filesystem size used avail capacity Mounted on
/dev/md/dsk/d0 33G 7.3G 25G 23% /
#
# metastat -c d0
d0 m 33GB d10 d20
d10 s 33GB c1t0d0s0
d20 s 33GB c1t1d0s0

As you can see, there are two disk that comprise the boot mirror (d0), 33GB c1t0d0s0 and c1t1d0s0, which is named d10 and d20 respectively

Check which disk is booting up

In this step, we will determine which of the disk are the one being use as the boot default boot disk.

Usually it’s the default ‘disk’ or ‘disk0′, but there are times, very rare, that ‘disk1′ is set as the default boot disk.

To know which disk is the one that boot up the system, you can use the eeprom command in the system shell:


# eeprom boot-device
boot-device=disk0


In this case, it’s the most common disk that is used as the boot disk – disk0. That means, when can detach the other disk as backup just in case the patching screw up.

Check The Bootability of the Backup Disk

Prior to patching, check if the other disk is booting. This is a precaution. Just in case the patching went sour, we know that we can always revert to a good disk, revert to the previous good booting condition of the server.

Since from the previous step, we know that the default boot disk is ‘disk0′, we will switch to ‘disk1′ and try to reboot the server and see if it will come up.

Now, there are two ways to set the value of the ‘boot-device’ paramter of the server. You can either set it at the system shell, or through the Boot PROM, depending on where you are at the moment.

Now, set the default boot disk to ‘disk1′

eeprom boot-device=disk1

or

set boot-device=disk1

After setting it up, reboot the server:

init 0 then boot

or

init 6

If you’re successfull, you just booted on the ‘other half’ of the bootdisk.

Now, don’t forget to switch back to disk0 !!!

Next, (optional… can differ from company to company)

# untar the patch file
cd /var/tmp
rm -rf PatchDir
mkdir PatchDir
mv S10KernelUpdate4.0.tar.gz PatchDir
cd PatchDir
gunzip -c S10KernelUpdate4.0.tar.gz|tar xf -

Splitting the Mirror

The next steps are the meat of the procedure. This is the patching of the kernel itself.. But of course, after checking the boot disk – whether the both disks are good- it’s time to break the mirror and patch one disk.

sync;metadeatch

detach the backup disk

metadetach d0 d20

# mount the detached root file system to root and modify these

mount /dev/dsk/c1t1d0s0 /mnt

vi /mnt/etc/vfstab
vi /mnt/etc/system

Modifying vsfstab and /etc/system of the detached disk will make sure that if the patching fail, we can alyas boot up to the backup disk.

Start Patching

# go to single user mode
sync;sync;init 0

init -s

Rebooting with command: boot -s
Boot device: /pci@8,600000/SUNW,qlc@4/fp@0,0/disk@0,0 File and args: -s
SunOS Release 5.10 Version Generic_141414-02 64-bit
Copyright 1983-2009 Sun Microsystems, Inc. All rights reserved.
Use is subject to license terms.

… You then follow the ReadMe document that comes with the Patch here.

Once the patching is done, you’ll see the difference of the patch level of the kernel.

Boot device: disk0 File and args:
SunOS Release 5.10 Version Generic_142900-02 64-bit
Copyright 1983-2009 Sun Microsystems, Inc. All rights reserved.
Use is subject to license terms.

Optional
=——————–
For more installation messages refer to the installation logfile:
/var/sadm/install_data/PMGT:_TLP-Set_Solaris_10_SOE_S10KernelUpdate4.1_A1_04_27_10

Use ‘/usr/bin/showrev -p’ or ‘/usr/sbin/patchadd -p’ to verify
installed patch-ids.
Refer to individual patch README files for more patch detail.
Rebooting the system is usually necessary after installation.
svc.startd: The system is coming down. Please wait.
svc.startd: 20 system services are now being stopped.

!!! Please read the logfile for any required action before rebooting !
————–

reboot:! for the bank, it’s automatic

If all is good, you can reattach the other disk

metattach d0 d20

And you’re done.

Got a page.. something like “Fault found by metastat” in short description in Remedy…

# metastat | grep Need
State: Needs maintenance
State: Needs maintenance

Which disk?

# metastat d9
d9: Mirror
Submirror 0: d19
State: Needs maintenance
Submirror 1: d29
State: Okay
Pass: 1
Read option: roundrobin (default)
Write option: parallel (default)
Size: 134221440 blocks (64 GB)

Device Relocation Information:
Device Reloc Device ID
c0t2d0 Yes id1,sd@SSEAGATE_ST373307LSUN72G_3HZ6Y1EN000074312CVW
c0t3d0 Yes id1,sd@SSEAGATE_ST373307LSUN72G_3HZ6Y46Y0000743249BK


Check for hard errors to verify if this disk can really be replaced… if it passed (on your criteria), you can try re-syncing it…

c# metareplace -e d9 c0t2d0s5
d9: device c0t2d0s5 is enabled

Verify that it’s doing what it is expected..

# metastat d9
d9: Mirror
Submirror 0: d19
State: Resyncing
Submirror 1: d29
State: Okay
Resync in progress: 0 % done
Pass: 1
Read option: roundrobin (default)
Write option: parallel (default)
Size: 134221440 blocks (64 GB)

And we wait…..

“->” = ILOM
“sc>” = ALOM

.. and since this particular server has the “->” prompt we’re using the ILOM.

From ILOM to Solaris:
-> start /SP/console

From ALOM to Solaris:
sc> console

And of course.. Enter “#.” to return to ALOM / ILOM !!

Send Break on ILOM

set /HOST send_break_action=break
and then
start /SP/console

c)ontinue, s)ync, r)eset? s

bada bing! bada boom!

Will be installing Ruby on Rails using Cool Stack… this is the first of sets of post.. Now downloading the packages from Sun.com

Optimized Open Source Software Stack (Cool Stack) for the Sun Solaris Operating System(TM). Cool Stack is a collection of some of the most commonly used open source applications optimized for the Sun Solaris OS. By using these binaries you will enjoy the best levels of performance from your system, while also reducing your time-to-service.

Instructions: Select the files you want, then click the “Download Selected with Sun Download Manager” (SDM) button below to automatically install and use SDM (learn more). Alternately, click directly on file names to download with your browser. (Use of SDM is recommended but not required.)

To connect to the console of a Solaris 10 zone called testzone, use the following command as root or the equivalent on the global zone:

zlogin -C testzone

The -C option specifies a console login. The console login will persist when the zone is rebooted.
To exit zlogin, use the escape sequence ~. on a new line (the tilde must follow a carriage return, not any other character). If this escape character is inappropriate (because you are connected using software like tip that also uses this escape sequence), you can specify a different escape character on the command line. For example, to use the @ symbol, use:

zlogin -C -e @ testzone

In this case, to exit the zlogin console session, type @. on a new line

Just a note of reference, if you are using tip and forget to change the escape character above. you can do the following to get out

~~.

This will force it to disconnect the local zlogin instead of the tip…
—-
However, let’s go deeper….

If you logged into a container’s console (via chs000xx —> ILOM —> then to a serial console)..

#. – will exit to ILOM (but once you logged in again.. you’re in container’s console)
~. – will exit to chs000xx (but once you logged in again.. you’re in container’s console)
~~. – WILL EXIT from the Container!!

It’s a like an hierarchy thingy..

(first part was taken from a website… later part was from me.. of course if you didn’t read all of it, you wont see this note.. )

http://sysadmindayph.com/

You may set your search path automatically each time you log in, by placing the appropriate “set path” command in your “.login” file.

(To learn more about the .login file, type “help dotlogin”.) Here is a sample of a command line that you might put in your .login file to set a non-standard search path:

set path = ( $path /usr/ucb /bin /usr/bin /usr/new .)

This How-To Guide instructs users, system administrators, and developers unfamiliar with Solaris 10 OS on consolidating applications onto a single server using Solaris Containers technology. The guide starts with a brief overview of Solaris Containers and follows with an example of using Solaris Containers to consolidate two Web server applications and an email server application onto a single server. Users are guided step-by-step through the consolidation process, with code examples and illustrations.

After using this guide, a user should be able to create Solaris Containers by:

* Creating a resource pool
* Defining Solaris Zones
* Assigning CPU usage with the Fair Share Scheduler (FSS)
* Installing and booting a zone
* Configuring access to raw devices from the zone

I wont be able to post every info from the PDF file here.. But I can however maybe put a part so that it will entice you more to download the paper:

Solaris Zones
As part of the consolidation effort, it is important to
evaluate the needs of the applications that will share the
consolidated system. In this example, the email server and
Web server applications need to run in isolated
environments that make it appear as if they are running on
physically separate machines. This is made possible by a
Solaris Container technology called Solaris Zones, which
provides separate environments on a machine and logically
isolates applications from one another. Each application
receives a dedicated namespace in which to run, and
cannot see, monitor, or affect applications running in
another zone

Dynamic Resource Pools
In this example there are two types of applications, one
that needs a fully dedicated CPU—an email server, and
another that is more flexible and can share CPUs—the two
Web servers. To accomplish these different levels of
isolation we use a Solaris Container technology called
Dynamic Resource Pools that enables CPU resources to be
dedicated to specific applications. In this example, the
email server needs a separate resource pool, while the Web
servers can share another

Fair Share Scheduler
While the two Web servers are capable of sharing the
remaining CPUs on the system, they each need a minimum
guarantee of CPU resources that will be available to them.
This is made possible by another Solaris Container
technology called the Fair Share Scheduler (FSS). This
software enables CPU resources to be allocated
proportionally to applications. That is, each application
gets assigned a number of the available “shares” of the
total CPU.

And many more! Excited yet? here’s the link for download:

https://www.sun.com/offers/details/solaris_containers.xml?cid=927534

Yesterday we had to replace a failed disk that belongs to a mirror. The disk is running in a Sparc Solaris 10 box. It’s a 72GB from Fujitsu

c1t1d0           Soft Errors: 440 Hard Errors: 12 Transport Errors: 124
Vendor: FUJITSU  Product: MAY2073RCSUN72G  Revision: 0501 Serial No: 0711S0935R
Size: 73.40GB <73400057856 bytes>

As you can see from the iostat -En command, the disk is spitting hard errors and must be replaced before it can cause a lot more headache. It’s in c1t1, right.

Here’s what we’re supposed to do:

• we could delete the meta data base that corresponds to the failed disk
• detached the failed disk/slices to the mirror
• clear it
• unconfigure the disk
• replace the disk
• configure the disk
• create new meta device database
• Initialize the disk
• Attached it to mirror
• and sync

Here’s the detailed job:

Info:
metadb | grep c1t1
metadb –d c1t1d0s7

Detach:
metadetach d30 d32
metadetach d40 d42
metadetach d20 d22
metadetach d10 d12

metaclear d32
metaclear d42
metaclear d22
metaclear d12

Verify:
metastat -p | grep c1t1d0
metadb | grep c1t1d0
[root@localhost] /> cfgadm -al
Ap_Id Type Receptacle Occupant Condition
c0 scsi-bus connected configured unknown
c0::dsk/c0t0d0 CD-ROM connected configured unknown
c1 scsi-bus connected configured unknown
c1::dsk/c1t0d0 disk connected configured unknown
c1::dsk/c1t1d0 disk connected configured unknown
c1::dsk/c1t2d0 disk connected configured unknown
c1::dsk/c1t3d0 disk connected configured unknown
usb0/1 unknown empty unconfigured ok
usb0/2 unknown empty unconfigured ok
usb1/1.1 unknown empty unconfigured ok
usb1/1.2 unknown empty unconfigured ok
usb1/1.3 unknown empty unconfigured ok
usb1/1.4 unknown empty unconfigured ok
usb1/2 unknown empty unconfigured ok

Unconfigure:
cfgadm -c unconfigure c1::dsk/c1t1d0

Verify ulit, note the red text above:
cfgadm –al
SWAP DISK

Undo what has been done….

Configure:
cfgadm -c configure c1::dsk/c1t1d0

format (to label disk)

prtvtoc /dev/rdsk/c1t0d0s2 | fmthard -s – /dev/rdsk/c1t1d0s2

metadb -a –c 2 c1t1d0s7

Attach!!

metainit d32 1 1 c1t1d0s6
metainit d42 1 1 c1t1d0s4
metainit d22 1 1 c1t1d0s1
metainit d12 1 1 c1t1d0s0
metattach d30 d32
metattach d40 d42
metattach d20 d22
metattach d10 d12
metastat -p
metadevadm -u c1t1d0

And you’re done! Grab a cup of coffee and wait till the synchronization is done.