public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Jim Roland <jroland@roland.net>
To: root@chaos.analogic.com
Cc: Venkatesh Ramachandran <rvenky@cisco.com>,
	linux-users@cisco.com, linux-kernel@vger.kernel.org,
	linux-alpha@vger.kernel.org, brussels-linux@cisco.com,
	Mathangi Kuppusamy <mathangi@cisco.com>
Subject: Re: Linux Mounting problem
Date: Thu, 30 Aug 2001 16:23:12 -0500	[thread overview]
Message-ID: <3B8EAEC0.4090905@roland.net> (raw)
In-Reply-To: <Pine.LNX.3.95.1010830112028.1525A-100000@chaos.analogic.com>

He is getting these errors because his /etc/rc.d/rc.sysinit is shuttling 
all output from the commands in the script to be written to /dev/null 
and his FS is mounted as read-only.  It never gets mounted as read-write 
because of fsck failing to approve the check with an OK status.  If 1-2 
boots in rescue mode (or as "linux single") don't fix the errors, the 
last step (e2fsck) should be run and should fix the error, unless there 
is serious drive corruption.

Regards,
Jim Roland, RHCE


Richard B. Johnson wrote:

>On Thu, 30 Aug 2001, Venkatesh Ramachandran wrote:
>
>>Hello,
>>   I am using Redhat Linux 7.1
>>   During reboot, i get the message " Mounting / as readonly"
>>   And, it enters into maintenance mode...( & all other steps fail -
>>/proc not mounted, swap not mounted, fsck fails)
>>   I did the following :
>>   mount -t proc proc /proc
>>   fsck /dev/hda1
>>   The following error messages : ERROR : Couldn't open /dev/null
>>(Read-only file system)
>>
>
>First, verify that /dev/null is a character device, major=1, minor=3.
>`file /dev/null`.
>It may have gotten changed to some real file because of some errors.
>
>In maintenance mode do:
>
>/sbin/mount -n -o remount /dev/hda1 # Mount r/w, no write to /etc/mtab
>/bin/rm /dev/null             # Delete it
>/bin/mknod /dev/null c 1 3    # Make a new one
>/bin/chmod 777 /dev/null      # Accessible by everyone in all modes
>/bin/chown root.sys /dev/null # Standard ownership
>/sbin/umount /dev/hda1        # Now unmount it
>/sbin/mount /proc /proc -t proc # You can mount it if you want
>/sbin/e2fsck -f /dev/hda1     # Fix the disk
>... After you fix the errors ...
>`exec /sbin/init auto`  (or exit if from a startup script)
>
>Cheers,
>Dick Johnson
>
>Penguin : Linux version 2.4.1 on an i686 machine (799.53 BogoMips).
>
>    I was going to compile a list of innovations that could be
>    attributed to Microsoft. Once I realized that Ctrl-Alt-Del
>    was handled in the BIOS, I found that there aren't any.
>
>
>-
>To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
>the body of a message to majordomo@vger.kernel.org
>More majordomo info at  http://vger.kernel.org/majordomo-info.html
>Please read the FAQ at  http://www.tux.org/lkml/
>



  reply	other threads:[~2001-08-30 21:21 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2001-08-30 15:11 Linux Mounting problem Venkatesh Ramachandran
2001-08-30 15:37 ` Richard B. Johnson
2001-08-30 21:23   ` Jim Roland [this message]
2001-08-31 12:08     ` Richard B. Johnson
2001-08-30 21:19 ` Jim Roland
2001-08-30 21:50 ` Mike Fedyk

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=3B8EAEC0.4090905@roland.net \
    --to=jroland@roland.net \
    --cc=brussels-linux@cisco.com \
    --cc=linux-alpha@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-users@cisco.com \
    --cc=mathangi@cisco.com \
    --cc=root@chaos.analogic.com \
    --cc=rvenky@cisco.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox