Home > Init Cannot > Init Cannot Access /var/adm/ Wtmp Remaining In Single User Mode

Init Cannot Access /var/adm/ Wtmp Remaining In Single User Mode

Please try the request again. Example: # /usr/bin/file /a/sbin/sh /a/sbin/sh: ELF 32-bit MSB executable SPARC Version 1, statically linked, stripped #/usr/bin/file /bin/sh /bin/sh: ELF 32-bit MSB executable SPARC Version 1, dynamically linked, stripped If /a/sbin/sh is The superblock was corrupted so I had to creata a new /var filesystem giving an alternate super block. 4) Ask the backup team to restore the /varfile system. 5) Reboot the Some other messages follow, and the system usually comes up single-user. his comment is here

Talk to us Home > Articles > Operating Systems, Server > Solaris Solaris Operating Environment Security: Updated for Solaris 9 Operating Environment By Sun Microsystems Apr 18, 2003 📄 Contents ␡ thanks in advance. Here are the messages I see on console mount: mount-point /var/run does not exist. Please try the request again.

Example:   #!/sbin/sh set -x     Cause 5 :  Invalid hostname files exists in /etc directory  /etc/hostname.hme0.bakcup.   Solution :  The startup script /etc/init.d/network will fail to parse these file This article is current as of Solaris 9 OE (5/02), which was released on May, 2002. Since the files may be corrupted, clear their contents and again check permissions and ownership. Make sure the / and /var filesystems are not full.

The /etc/name_to_major file should also have a cn device listed with major number zero. This will enable verbose output from the script as it runs, which may help pinpoint the problem or its source. Kind regards / Mit freundlichen Grüßen / Met vriendelijke groeten Andy Wyatt Level 2 Technical engineer Top Best Answer 0 Mark this reply as the best answer?(Choose carefully, this can't be All product names are trademarks of their respective companies.

After making a backup copy, edit /etc/init.d/standardmounts, modify the file so that the file system which contains /var is mounted. See bugs 4943782 and 4865207. Root Filesystem is in  Read-Only Mount State due to filesystem inconsistency. Solution :  For troubleshooting, boot from CD-ROM (the same Solaris[TM] version that the system is running if possible) into single user mode, and mount the core Solaris filesystems under /a ok

Example of problem filename: /etc/hostname.hme0.9mar2005 5. If the file system containing /var is mounted read-only, remount it read-write with a command similar to this: # mount -o rw,remount / Then type Control-D and try to bring up Some other messages follow, and the system usually comes up single-user. Top This thread has been closed due to inactivity.

The files here should be hard linked to files in /a/etc/init.d Example: #/usr/bin/ls -i /a/etc/rcS.d/S30rootusr.sh 327078 /etc/rcS.d/S30rootusr.sh #/usr/bin/ls -i /a/etc/init.d/rootusr 327078 /etc/init.d/rootusr.sh 10. https://www.auscert.org.au/resources/publications/guidelines/unix-linux/unix-and-linux-security-checklist-v3.0 Kernel corruption causing init to fail. Toolbox.com is not affiliated with or endorsed by any company listed at this site. Differences between the Solaris OE versions 2.5.1 through 9 are discussed in this article and noted where appropriate.

Arif (Alex ) Join this group Popular White Paper On This Topic Performance and Flexibility Serve the Enterprise: Research Reveals Path To Maximize Linux Performance 3Replies Best Answer 0 Mark this this content The changes outlined in this article address the majority of the methods that intruders use to gain unauthorized or privileged access to an improperly configured system. Implementing the changes recommended in this article requires planning, testing, and documentation to be successful in securing a computing environment. Goff Book $35.99 J2EE Platform Web Services By Ray Lai Book $43.99 Secure Shell in the Enterprise By Jason Reid Book $39.94 See All Related Store Items the trusted technology learning

Close   Our next learning article is ready, subscribe it in your email Name(required) Email(required) Learning Request(required) Are you Looking for (required) Paid Training Free Training What is your Learning Goal for Your cache administrator is webmaster. The /etc/name_to_major file should also have a cn device listed with major number zero. http://urldt.com/init-cannot/init-cannot-execute-etc-init-d-rcs.html Example: #!/sbin/sh set -x 4.

The problem is often that / or /var is mounted read-only. Mount them to /a/usr, /a/var, and /a/opt, respectively. Make a backup of /a/etc/mnttab and cat /dev/null to the original. 12.

The following is an example where /var resides in /export/home/var: exec < ${vfstab}; readvfstab "/export/home" if [ "${mountp}" -a -d /export/home ] then /sbin/mount -m /export/home > /dev/null 2>&1 mntlist="${mntlist}/export/home /export/home"

mshivhare replied May 22, 2007 Hello, I had faced the same problem a month back and I had done the below mentioned steps: 1) Ensure that the backup of /var is Do the following: # /usr/bin/cp /dev/null /a/var/adm/utmpx # /usr/bin/cp /dev/null /a/var/adm/wtmpx # /usr/bin/chown root:bin /a/var/adm/utmpx # /usr/bin/chmod 644 /a/var/adm/utmpx # /usr/bin/chown adm:adm /a/var/adm/wtmpx # /usr/bin/chmod 644 /a/var/adm/wtmpx There should also be Your cache administrator is webmaster. Buy the Full Version SunOS_Commands by GhulamNabi73 viewsEmbedDownloadRead on Scribd mobile: iPhone, iPad and Android.Copyright: Attribution Non-Commercial (BY-NC)List price: $0.00Download as PDF, TXT or read online from ScribdFlag for inappropriate contentMore

Kernel corruption. You're now being signed in. Restore Solaris from a known good backup. 16. check over here Sometimes a brief power outage leaves the system believing that many file systems are still mounted.

If /etcd/inittab is corrupt, copy one the one from /cdrom//Product/SUNWcsr/reloc/etc to /a/etc. 8. When I try to boot with boot -rs, I don't get any error, but after successful boot, I tried to boot again without specifying boot arguments I end up with same If /etc/inittab is corrupt, copy one the one from /cdrom//Product/SUNWcsr/reloc/etc to /a/etc.      Cause 8 :  Missing  Console Device files  i.e.  /dev/console linked to devices/pseudo/[email protected]:console    Solution :   Make sure /dev/console Implementing the changes recommended in this article requires planning, testing, and documentation to be successful in securing a computing environment.

Leave a Reply Cancel reply Disclaimer : Procedures posted in this site had no guarantee to work in your Environment, use it on your own Risk when you use it for And confirm the path and device exists.     Cause 3 :  / and /var filesystem are full Solutions :   For troubleshooting, boot from CD-ROM (the same Solaris[TM] version that INIT: Cannot create /var/adm/utmpx alex asked May 21, 2007 | Replies (3) Good Day, Can someone pls help me on the message I'm getting while booting the server? Make sure /dev/console exists.

Like this article? The wtmpx database contains the history of user access and accounting information for the utmpx database. We occasionally see following error in solaris during system startup,  INIT: Cannot create /var/adm/utmp or /var/adm/utmpx Verify that there are not files in /a/etc with filenames in the format: hostname.. Run fsck(1M) on the root file system, halt the machine, power cycle the CPU, and wait for the system to reboot.

We recommend  Enterprise Security: Solaris Operating Environment, Security Journal, Solaris OEv2.51, 2.6, 7, and 8 Learn More Buy Updated for Solaris 9 Operating Environment This article provides recommendations on how Make sure /a/sbin/sh is the statically linked form of the command. This is a common one if the error started after a patch installation (possibly in multi-user mode). Solve problems - It's Free Create your account in seconds E-mail address is taken If this is your account,sign in here Email address Username Between 5 and 30 characters.

Home | Invite Peers | More UNIX Groups Your account is ready. The minor numbers for the entry in the /devices entry should follow the convention in the example, 0 for the sysmsg device, and 1 for the msglog device. Example: # /usr/bin/ls -al /a/dev/console lrwxrwxrwx 1 root other 30 Aug 15 2001 /a/dev/console -> ../devices/pseudo/[email protected]:console     Cause 9 :  Corrupted /etc/mnttab   Solution : For troubleshooting, boot from CD-ROM (the If the core Solaris OE filesystems are mounted from physical disk slices, not Veritas Volume Manager or Solstice DiskSuite[TM] volumes, then make sure the devices in /a/etc/vfstab point to valid entries

The /etc/inittab file should not be used for comparison while booted from CD-ROM, as its configuration is geared toward the installation process not system recovery. this can be one of the reasons to get this error Top Best Answer 0 Mark this reply as the best answer?(Choose carefully, this can't be changed) Yes | No Saving... We recommend Enterprise Security: Solaris Operating Environment, Security Journal, Solaris OEv2.51, 2.6, 7, and 8 Learn More Buy Like this article?