System unbootable after installing Solaris 10 Kernel Patch

Solaris 10 Kernel Patches are primarily installed to remove all the firmware problems and software bugs. In most cases, you are benefited with installation of Solaris Kernel Patches. However, there can be instances where your system becomes unbootable after installing these patches. Furthermore, your hard drive data becomes inaccessible once your system becomes unbootable. For complete recovery of inaccessible data after such instances, you will need to restore the data from an updated backup. However, if no backup is available or backup falls short to restore the desired information, then you will need to opt for advanced Solaris Intel Recovery Software that can systematically recover your data.

Consider a practical scenario, where you install a patch 120586-04 (MP1) on Solaris 10 systems running VXVM 4.1 patch. However, after you install the new patch and restart your system, you view that your system hangs every time during a boot up. In addition, you encounter the below error message:

Boot device: disk File and args:
Loading ufs-file-system package 1.4 04 Aug 1995 13:02:54.
FCode UFS Reader 1.12 00/07/17 15:48:16.
Loading: /platform/SUNW,Sun-Fire-V490/ufsboot
Loading: /platform/sun4u/ufsboot
SunOS Release 5.10 Version Generic_118833-36 64-bit
Copyright 1983-2006 Sun Microsystems, Inc. All rights reserved.
Use is subject to license terms.
Hostname: xxxxxx

Cause:

The above error message primarily occurs when svccfg(1M) removes the External Dependencies.

Resolution:

To resolve the above error message and access the hard drive data, you will need to manually re-import the “/var/svc/manifest/system/emcpower/powerpath_services.xml” manifest. You will also need to complete the below steps:

svcadm disable -s powerconfigcgs
svcadm disable -s powershift
svcadm disable -s powerstartup
svccfg delete powerconfigcgs
svccfg delete powershift
svccfg delete powerstartup
svccfg import /var/svc/manifest/system/emcpower/powerpath_services.xml
svcadm enable powerstartup
svcadm enable powershift
svcadm enable powerconfigcgs

But, if the above resolution fails to remove the issue and your system still remains unbootable, then you will need to use advanced Solaris Intel Recovery Software. These Sun Solaris Data Recovery tools use effective scanning methods to recover your lost data after serious corruption scenarios like superblock corruption, inode structure damage, etc. With highly graphical user-interface, to the point documentation, these tools are easily understandable without former data recovery experience.

Stellar Phoenix (Solaris - Intel) Data Recovery is an efficient Sun Solaris Data Recovery software. This non destructive recovery application is compatible with UFS file systems. It gets installed on Windows (XP, 2003, 2000, NT, ME, 98 and 95) and the affected Sun Solaris hard drive is connected as slave.

Data Loss after removing Kernel Patches using “svccfg delete”command

An unmountable or inconsistent state in Sun Solaris Sparc operating system primarily occurs due to file system damage, operating system malfunctioning, Kernel damage (completely or partially), virus infection, and more. Data stored on your hard drive becomes inaccessible after you your system comes into an unmountable state. To overcome such situations, an easy way is to restore data from a complete backup. But if in case, you have not maintained any backup or backup file is unable to restore the required data, then you will need to use advanced Sun Solaris Sparc Data Recovery Software to recover your lost data.

Consider a practical scenario, where you removed a Solaris 10 Kernel patch118833-36 for SPARC using “svccfg delete” command when the “milestone” parameter is set to null. However, when you attempt to restart your system, it does not boot making all the hard drive inaccessible. Furthermore, when you attempt to reboot your system (Single User Mode), you encounter below error message:

“booting with command: boot
Boot device: rootdisk File and args:
not found: get_cpu_pagesizes
do_relocations: /platform/sun4v/kernel/cpu/sparcv9/SUNW,
UltraSPARC-T1 do_relocate failed
krtld: error during initial load/link phase
panic - boot: exitto64 returned from client program
Program terminated
{0} ok”

The system becomes unusable after the above error message appears.

Cause:

The above issue primarily occurs when both the below conditions are true:

  • A patch is being deleted using the “svccfg delete” command.
  • The “milestone” parameter is not assigned “all” value.

Resolution:

To resolve the above issue, you will need to reinstall Sun Solaris Sparc operating system. Data stored in the hard drive partition gets completely erased after you perform a clean reinstall. For complete recovery of lost data in such situations, you will need to use effective Sun Solaris Sparc Data Recovery Software. Such recovery applications use high end scanning procedures to recover lost data to recover data from formatted hard drive. These Sun Solaris Sparc Data Recovery applications perform recovery after fsck command fails to repair the system data structures.

Stellar Phoenix Solaris Sparc software is a efficient Sun Solaris Sparc Data Recovery application that recovers all lost, missing, and deleted data from Solaris operating system on Sparc platform. This non destructive recovery application is compatible with UFS file systems. It gets installed on Windows (2003, XP, 2000, NT, ME, 98, and 95) and the affected UNIX hard drive should be connected as slave.

Superblock Corruption in Sun Solaris

A superblock in UFS (Unix File System) volume is the most critical part that contains vital information about the file system’s geometry and behavior tuning parameters. Corruption of superblock primarily occurs due to overlapping disk partitions, operating system malfunctioning, unexpected system shutdown, virus infections and more. Once the superblock gets corrupted, the file system can not be mounted. This results in inaccessibility of data stored in the hard drive. To overcome such data loss situations, you need to restore the data from an updated backup. However, if no backup is available or backup fails to restore the required information, Sun Solaris Intel Recovery Software comes to rescue.

As a practical scenario, when you attempt to boot Sun Solaris Intel operating system, you encounter the below error message:

“BAD SUPER BLOCK: variable”

The above error message indicates that the system is unable to read the superblock. After the above error message appears, the data saved in the hard drive becomes inaccessible. In addition, you encounter the same error message each time you attempt to start your system.

Cause:
The root cause for the occurrence of the above error message is the corruption of superblock.

Resolution:
To resolve the above error message and access the data, you will need to follow these steps:

  • Run the format command, select the disk involved, and print out the partition information.
  • format : N > partition > print

  • Run newfs command with the -N option to print out the file system parameters, including the location of backup super-blocks.
  • newfs -N /dev/dsk/device

  • Select a super-block from a non-overlapping area of the disk and run
    fsck command with the new master super-block number.
  • fsck -o b=NNNN /dev/dsk/device

However, if both the procedure falls short to resolve the issue and you still encounter the same error message, then you will need to use powerful Sun Solaris Intel Data Recovery Software to recover the lost data. Such Sun Solaris Intel Recovery tools use advanced scanning mechanisms to recover your lost files and folders. With highly interactive user interface and advanced features, these tools are easy to understand without any prior technical knowledge. Such recovery applications recover the lost data after fsck is unable to repair the system data structures.

Stellar Phoenix (Solaris - Intel) software is a powerful Sun Solaris Data Recovery that recovers data from Solaris operating system on Intel platform. This non destructive recovery application is compatible with UFS file systems. It gets installed on Windows (XP, 2003, 2000, NT, ME, 98 and 95) and the affected UNIX hard drive should be connected as slave.