Home > Cannot Open > Cannot Open /etc/mnttab Permission Denied

Cannot Open /etc/mnttab Permission Denied

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 Do I need to change the file permissions of fstab? These, while they do not crash the system, are usually a signal that the memory chip in question needs to be replaced. Once we are done, we need to re-install the bootblock: cd /usr/platform/`arch -k`/lib/fs/ufs /usr/sbin/installboot ./bootblk /dev/rdsk/c#t#d#s# BAD TRAP: The causes for bad traps include system text errors, data access faults, data this contact form

These result in a watchdog reset. Look in the sender's dead.letter file for the automatically saved message, andhave the originator send it again, this time specifying a recipient. It is possible that the filesystem containing /etc is mounted read- only, or is not mounted at all. Ask the system vendor for an upgrade, or contact the vendor or author of the application for an update. https://community.hpe.com/t5/System-Administration/etc-mnttab-permission-denied/td-p/4910357

If the user is supposed to know the root password, wait to see if the correct password is supplied. Main Menu LQ Calendar LQ Rules LQ Sitemap Site FAQ View New Posts View Latest Posts Zero Reply Threads LQ Wiki Most Wanted Jeremy's Blog Report LQ Bug Syndicate Latest Event not found: The shell reports that a command matching the request cannot be found in the history buffer for the shell session.

But, interestingly the file /etc/mtab doesn't even exist (I even searched the entire computer for it and found nothing). unable to schedule enumeration: Initiator unable to enumerate the LUNs on the target. is not okay: The filesystem should either be mounted read-only or fsck-ed. Operation not supported on transport endpoint (EOPNOTSUPP): Tried to accept a connection on a datagram transport endpoint.

The card may need to be reseated. See the Device busy error message. What does /etc/mtab do anyway? If there is at least one valid recipient, each invalid recipient address will generate a "User unknown" message.

It may have been set to a nonexistent program or an illegal shell. Do I need to run 'reiserfsck --rebuild-tree' or something or would that only worsen the issue? And, no, I can't think of anything that would help in delaying the reboot.Pete Pete 1 Kudo Reply Marty Metras Super Advisor Options Mark as New Bookmark Subscribe Subscribe to RSS 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:

See the SCSI transport failed: reason 'reset' message as well. http://www.linuxquestions.org/questions/slackware-14/etc-mtab-problem-%3D-can't-mount-anything-cdrom-floppy-etc-355656/ This message indicates that no system support exists for an operation. This will not unmount telling me the NFS is not restopnding.syslog shows the nfs errors this morning from trying to 'pfs_umnount /CDROM'.And some of these when using SAM to look at But as it was booting, I think it did check the filesystem, but I'm not sure because it went so fast, like it does when it usually boots.

For PROM-based systems, set the boot-device properly in the PROM environment variables. http://scriptkeeper.net/cannot-open/cannot-open-output-file-permission-denied-dev-c.html Please specify a recipient. If not, restore it from a backup, or see Section 22.2.3, "Setting vfstab" and redefine it. Protocol not supported (EPROTONOSUPPORT): The protocol has not been configured for this system.

Oh yeah,... The reported error was: mount: can't open /etc/mtab for writing: Permission denied In Konsole as root, I get the same message when I try to mount something manually # mount /dev/hdc Well, I did just as you said and I found out that the permissions of /etc/fstab is read-write only for root. navigate here Find More Posts by Master Fox 08-22-2005, 03:53 PM #9 theo444 LQ Newbie Registered: Jul 2005 Location: Colorado Distribution: Slackware 10.2 Posts: 10 Original Poster Rep: Normally I do

I have another slack-box that I just got running and /etc/mtab exists on it and fstab is also set to read-write only for root on that computer. This indicates an attempt to evaluate a mathematical programming function at a point where its value would overflow or underflow. Stale NFS file handle (ESTALE): The file or directory on the NFS server is no longer available.

This may result from supplying the wrong device or option to a command, or it may be the result of a programming bug.

By using this site, you accept the Terms of Use and Rules of Participation. End of content United StatesHewlett Packard Enterprise International CorporateCorporateAccessibilityCareersContact UsCorporate ResponsibilityEventsHewlett Packard LabsInvestor RelationsLeadershipNewsroomSitemapPartnersPartnersFind a PartnerPartner Segmentation Fault 189. Use cfgadm to check the receptacle and its state. See Bus Error above.

Software caused connection abort (ECONNABORTED): The connection was aborted within the local host machine. Check it as,# ps -ef | grep syncerelse start it.# /usr/sbin/syncerhth. The history command shows the current contents of the history buffer. http://scriptkeeper.net/cannot-open/cannot-open-cvs-entries-static-permission-denied.html File name too long (ENAMETOOLONG): The referenced file name is longer than the limit specified in /usr/include/limits.h.

During phase 1, fsck(1M) found that the specified inode was neither allocated nor unallocated. E.5.18.25 {sfcquotaon|sfcquotaoff}: WARNING: line in mnttab has too many entries [Explanation] There was an illegal entry with too many fields of /etc/mnttab. [Action] Please check whether the entry of which file Error 88 (EILSEQ): This is an illegal byte sequence error. If that doesn't work, replace the tape cartridge.

May be on one of the servers the file is locked by a mistake.HTH Entities are not to be multiplied beyond necessity - RTFM 0 Kudos yuli_3 Advisor Options Mark as This may happen if globbing is applied to a large number of objects (eg rm * in a directory of more than 1706 objects). Well, I did just as you said and I found out that the permissions of /etc/fstab is read-write only for root. Verify the initiator discovery information and storage device configuration.

A reboot is recommended after we have figured out which process is hogging all the memory and/or swap, since the system may be in an unstable state. You must run the baove command as root. Find More Posts by Master Fox 08-22-2005, 11:16 PM #11 theo444 LQ Newbie Registered: Jul 2005 Location: Colorado Distribution: Slackware 10.2 Posts: 10 Original Poster Rep: Sorry, it didn't Examples include SIGSEGV, SIGPIPE and SIGSYS.

But the other is fine. Check for loose connections and otherwise check the network. Check for a typo and/or verify that the variable has been set. Soft errors are an indication that hard errors couldsoon occur, causing data corruption.

in security stage: Device responded with unsupported login information during login security phase. The symbolic name for this error is EACCES, errno=13. The kernel will block interrupts in a few exceptional circumstances, such as during the process of acquiring a mutex lock protecting a sleep queue. Find More Posts by NetRAVEN5000 08-22-2005, 01:06 AM #5 theo444 LQ Newbie Registered: Jul 2005 Location: Colorado Distribution: Slackware 10.2 Posts: 10 Original Poster Rep: The other box I

Make sure that the relevant filesystems are mounted and that the expected files and/or directories exist. target protocol group tag mismatch: Initiator and target had a Target Portal Group Tag (TPGT) mismatch. rebooting… 178. syncing file systems… 201.