Return to BSD News archive
Path: sserve!newshost.anu.edu.au!munnari.oz.au!constellation!aardvark.ucs.uoknor.edu!ns1.nodak.edu!plains.NoDak.edu!ortmann Newsgroups: comp.os.386bsd.questions Subject: Re: 386BSD Refuses to mount drives; mount failure Message-ID: <C6J4nE.L4A@ns1.nodak.edu> From: ortmann@plains.NoDak.edu (Daniel Ortmann) Date: Wed, 5 May 1993 01:11:38 GMT Sender: usenet@ns1.nodak.edu (Usenet login) References: <1s6dcuINN3o7@life.ai.mit.edu> Organization: North Dakota Higher Education Computing Network Keywords: mount drive help confusion mattresses-on-the-walls white-rooms Nntp-Posting-Host: plains.nodak.edu Lines: 19 Calvin@hal.gnu.ai.mit.edu (Eric John Vette) writes: : )it tried to "mount -a" from the rc. A host of other errors appropriately )followed, claiming the the device was read only (root_device before it's )remounted as wd0a). I've been goofing with this, threatening it with fates )worse than being outdated, whispered sweet nothings inot its PC speaker, etc. )I even re-disklabeled from the Fixit Disk, thinking maybe there was a freaky, )invisible Write-only bit in the disklabel (yes, I disklabelled -r first to )check the visible Write-only bit). I can think of three possibilities: 1) mount might be corrupt 2) file ownership and/or permissions might have changed on mount, /etc, or /etc/fstab 3) one of the patches you applied might have changed (something???) -- Daniel "un?X" Ortmann (talmidim) NDSU Electrical Engineering ortmann@plains.nodak.edu shalom Fargo, North Dakota