How to Fix Boot or Login Issues Due to Permission Changes on OS Files
Last updated on APRIL 04, 2017
Applies to:Solaris x64/x86 Operating System - Version 8 6/00 U1 and later
Solaris Operating System - Version 8.0 and later
A system may fail to boot properly if permissions, groups and owners are accidentally changed using the chmod and chown commands on operating system files or directories.
Possible errors reported include:
- permission denied errors
- cannot execute /usr/lib/ld.so.1 Killed
- Can't invoke init, error 13 (the system would then panic)
- Filesystem state in superblock wrong
Or it may not be possible to login into the system:
Dec 23 02:13:57 box login: open_pam_conf: /etc/pam.conf writable by group
This document details how to reset the Solaris Operating System permissions, groups and owners back to the default values to allow the system to boot again.
Make certain that you know the system's root file system type and configuration before beginning.
Is the system using UFS or ZFS root?
- If UFS root, you will need to know the system's file system configuration e.g. what OS file systems are configured and the /dev/dsk/c#t#d#s# for each OS file system.
These may include: /, /usr, /var, /opt
- If ZFS root, you will need to know the pool name for the root pool (the default root pool name is rpool)
Sign In with your My Oracle Support account
Don't have a My Oracle Support account? Click to get started
My Oracle Support provides customers with access to over a
Million Knowledge Articles and hundreds of Community platforms