Solaris 11.4 Beta released!

I read about the Solaris 11.4 release. It’s strange, I tought Solaris was dead. it seems not yet!!

It’s long time I don’t play with Solaris 11, I think the last time was in 2013.
I hope to play with it again!

This link contains the new features within Solaris 11.4


Solaris QFS

Recently the customer I’m working for, asked to support him for a storage refresh project.
Host side he has multiple Vmware farms, Linux systems and three Solaris clusters running:

  • Solaris 10 on Sparc
  • QFS shared filesystem
  • Oracle RAC

I sincerely forgot tons of things about Solaris but I was happy to run “clq status” again, it was exciting 🙂

I also have the opportunity to play with QFS, I never saw it before. I’m dealing with an old version but I can’t wait to play more with sam* commands!!
I finally understand mcf file syntax and hosts file under /etc/opt/SUNWsamfs directory.
At same time I’m dealing with SRDF tasks, and I need to lear more about storage, EMC VMAX in this case 😀

Oracle S7 Processor!

Yesterday I have been in Oracle, following a workshop about new Oracle S7 and Minicluster systems.
I was impressed about the security focus from Oracle about each technical scenario ( Databse , Analytics , OLTP , … ) and the performances! They used multiple open source benchmark tools , and currently they have a super power compared to actual more powerful 86 processors.

Can’t wait about to work on these new systems !!:D

How to check GRUB installation on a specific disk under Linux or Solaris

It’s long time from my last post,
I worked a lot as LPIC traineer , with Redhat Cloud products and I sometimes help my colleagues with Redhat and Solaris patching tasks.

Due to patching tasks I tought about how to check if a specific disk does have GRUB installed?
For what I know there is not any command , so I studied and looking on Internet I found these commands:

Redhat box: ( with /dev/sda as example )
# dd bs=512 count=1 if=/dev/hda | od -Ax -tx1z -v

Solaris box: ( with c0t0d0 as example )
# dd bs=512 count=1 if=/dev/rdsk/c0t0d0s2 | od -c

This is nice!!
I also played on Solaris box with installgrub command , checking the disk before and after the GRUB installation 🙂

Why should I verify this? Because I love to know more as possible I can about any task I do 🙂
Have fun 😀

Solaris 10: svc:/system/sysidtool:net offline* transitioning to online

Recently I patched a Solaris 10 system with few local zones.
After attach phase, I booted the zones and checked their status with svcs -xv command.
I saw something strange… the manifest svc:/system/sysidtool:net was in the following state:

offline* transitioning to online

I tried to wait a couple of minutes but nothing changed!!
After some investigation I found that there was the file /root/etc/.UNCONFIGURED , so I figured that if that file exist the manifest waits a user configuration ( via zlogin -C ) or it will be offline forever !!

So, the correct patching procedure for avoid this issue is:

– detach the zone
– attach the zone via zoneadm attach -u
– check and remove /root/etc/.UNCONFIGURED file
– boot the zone

Another solution could be make a configuration via zlogin console ( It’s the post-install configuration where u must insert hostname, network, etc.etc. )

Happy Patching 🙂

Oracle T5-2 server: how to make hardware raid

Make an hardware RAID on T5-2 server is very fun 🙂
The first important thing is to locate which disk must be used for the raid.
If you have more than two disks on the server you have the question: “which disk I’m selecting for the raid?”

It’s simple to answer this question. Just following the official ORACLE documentation:

0) Go to OK prompt
1) Get the physical devices list

ok show-devs



2) Select a controller

ok select /pci@300/pci@1/pci@0/pci@4/scsi@0

3)Go in front of the server and you will see the disks blinking!!! So it’s easy to identify which disks we are using.
4) Get the targets

{0} ok show-children

FCode Version 1.00.63, MPT Version 2.00, Firmware Version

Target 9
Unit 0 Disk HITACHI H109030SESUN300G A690 585937500 Blocks, 300 GB
SASDeviceName 5000cca0546f7da4 SASAddress 5000cca0546f7da5 PhyNum 0
Target a
Unit 0 Removable Read Only device TEAC DV-W28S-A 9.2A
SATA device PhyNum 3
Target b
Unit 0 Disk HITACHI H109030SESUN300G A690 585937500 Blocks, 300 GB
SASDeviceName 5000cca0546f5d48 SASAddress 5000cca0546f5d49 PhyNum 1

5) Make the raid ( in my case I maid raid-1 ) between the targets

{0} ok 9 b create-raid1-volume
Target 9 size is 583983104 Blocks, 298 GB
Target b size is 583983104 Blocks, 298 GB
The volume can be any size from 1 MB to 285148 MB
What size do you want? [285148]
Volume size will be 583983104 Blocks, 298 GB
Enter a volume name: [0 to 15 characters] boot
Volume has been created

6) Check the volume info

{0} ok show-volumes
Volume 0 Target 143 Type RAID1 (Mirroring)
Name boot WWID 00de54d908dba3cb
Optimal Enabled Background Init In Progress
2 Members 583983104 Blocks, 298 GB
Disk 0
Primary Optimal
Target 9 HITACHI H109030SESUN300G A690 PhyNum 0
Disk 1
Secondary Optimal
Target b HITACHI H109030SESUN300G A690 PhyNum 1

7) Unselect the controller ( disks are still blinking! )

unselect-dev /pci@300/pci@1/pci@0/pci@4/scsi@0

At this point you can boot the server and watch the device via format command.
For the maintenance you can manage the volumes directly from Solaris! This is due to sas2ircu utility.