Home > Cannot Open > Cannot Open Etc Mnttab

Cannot Open Etc Mnttab

If the user is not supposed to know the root password, ask why he or she is attempting to become superuser. You must run the baove command as root. Because each disk slice is independent, multiple file systems can be mounted on a single disk. CALL US: 1 (866) 837-4827 Solutions Unstructured Data Growth Multi-Vendor Hybrid Cloud Healthcare Government Products Backup and Recovery Business Continuity Storage Management Information Governance Products A-Z Services Education Services Business Critical Source

For example, the final colon-separated field in /etc/passwd could have been changed from /sbin/sh to/usr/bin/bash, which does not exist in that location. ROOT LOGIN /dev/console 184. Make sure that external and secondary disk drives are targeted to 1, 2, or 0, and do not conflict with each other.  Also make sure that tape drives are targeted to Go to Solution. 0 Kudos Reply All Forum Topics Previous Topic Next Topic 8 REPLIES A.

This amounts to a request for an unsupported type of socket. During system reboot, this message might appear and theboot seems to hang. Showing results for  Search instead for  Do you mean  Menu Categories Solutions IT Transformation Internet of Things Topics Big Data Cloud Security Infrastructure Strategy and Technology Products Cloud Integrated Systems Networking Powered by Blogger.

Note that SPARC systems do not always support third party CDROM drives, and might generate a similar "unknown vendor" error message. Using mail(1), the recipient's address might have been specified using spaces or non-alphanumeric characters. How to Recover From a Boot Device Failure If you have a root (/) mirror and your boot device fails, you need to set up an alternate boot device. Verify that the /etc/vfstab file contains the correct volume entries.

The procedures in this section provide solutions to such potential problems. If the targeting of the internal disk drive is in question, power off the machine, remove all external drives, turn the power on, and from the PROM monitor run the probe-scsi-all First clean the tape head with a cleaning tape as recommended by the manufacturer. It is followed by the advisory "Periodic head cleaning required and/or replace tape cartridge" message.

These problems can arise either through hardware failures or operator error. CALL US: 1 (866) 837-4827 Solutions Unstructured Data Growth Multi-Vendor Hybrid Cloud Healthcare Government Products Backup and Recovery Business Continuity Storage Management Information Governance Products A-Z Services Education Services Business Critical The issue was due to the Mount VCS Agent unable to create a new file descriptor, as it had already reached the 256 Solaris default soft limit, and more than 1000 such Some SCSI devices for thePC market do not meet the high I/O speed requirements for the UNIX market.  Other possible causes of this problem are improper cabling or termination, and power

Anything else that might I might do to delay the reboot until the weekend?Marty The only thing that always remain the same are the changes. 0 Kudos Reply Pete Randall Outstanding The only solution is to reboot the system from another source, then edit the password file to correct this problem. Close Sign In Print Article Products Article Languages Subscribe to this Article Manage your Subscriptions Problem VCS WARNING V-16-10001-5564 Mount:mount_vol_1_81:monitor:Cannot open /etc/mnttab for read Solution If the  maximum open file Then verify that all cables are no longer than six meters, total, and that all SCSI connections are properly terminated.

su: ‘su root' failed for variable on /dev/pts/N 199. this contact form Read-only file system Files and directories on filesystems that are mounted read-only cannot be changed. If you are writing a program that produces this message while calling a system library, try to find and use an alternative library function. It is also possiblethat fsck will copy this file to the lost+found directory in a later phase.

  • Then, the system fails.
  • template.
  • Ensure that high-capacity memory chips (such as 4MB SIMMs) are in lower banks, while lower-capacity memory chips (such as 1MB SIMMs) are in the upper banks.
  • If that doesn't work, replace the tape cartridge.
  • Mount them on another directory, such as /disk2, which on most systems you will have to create.You could also change the automounter auto_home entry, but that is a more difficult solution.
  • p 166.
  • Please comment if you can provide some more details about these errors.
  • If you only modify these files and directoriesoccasionally, rlogin(1) to the servers from which the filesystems are mounted and change the files or directories there.
  • ok boot ... # format /dev/rdsk/c0t3d0s0 Reboot the system.

share_nfs: /home: Operation not applicable This message usually indicates that the system has a local filesystem mounted on /home, which is where the automounter usually mounts users' home directories. After a user has removed or modified a host in the hosts database, statd might not properly purge files in these directories, which results in its trying to communicate with a The value had to be raised to 2048 to suppress the error (lower values may be more appropriate, depending upon the rate of consumption of file descriptors) Set the following in have a peek here This message is purely informational.

My Name is Gopi.  I like to share the knowledge with people what I know. Read-only file system 177. Fill in your details below or click an icon to log in: Email (required) (Address never made public) Name (required) Website You are commenting using your WordPress.com account. (LogOut/Change) You are

If there is at least one valid recipient, each invalid recipient address will generate a "User unknown" message.

In this example, disk2 is that alternate boot device. Then, follow these steps: Boot from another root (/) submirror. Protocol wrong type for socket This message indicates either application programming error, or badly configured protocols. Hope this helps.-Amit 0 Kudos yuli_3 Advisor Options Mark as New Bookmark Subscribe Subscribe to RSS Feed Highlight Print Email to a Friend Report Inappropriate Content ‎07-03-2005 09:37 PM ‎07-03-2005 09:37

rmdir: variable: Directory not empty The rmdir(1) command can remove empty directories, only. The message indicates that statd has left old references in the /var/statmon/sm and /var/statmon/sm.bak directories. See the message "Not enough space" for details. Check This Out You could also change the automounter auto_home entry, but that is a more difficult solution.

Here is a list of Solaris / Unix error messages for your reference, most of the error messages are generic Unix error messages but many are specific Solaris Error Messages. statd: cannot talk to statd at variable This message comes from the NFS status monitor daemon statd, which provides crash recovery services for the NFS lock daemon lockd. Ferguson Acclaimed Contributor [Founder] Options Mark as New Bookmark Subscribe Subscribe to RSS Feed Highlight Print Email to a Friend Report Inappropriate Content ‎10-09-2006 02:53 AM ‎10-09-2006 02:53 AM Re: Error: For security reasons, it is a bad idea to allow root logins from anywhere besides the console.

Try remounting the filesystem on top of itself or shutting down any client processes that refer to stale file handles.