Linux MIPS Architecture development
 help / color / mirror / Atom feed
From: Eric Kimminau <eak@detroit.sgi.com>
To: mdhill@interlog.com
Cc: linux@cthulhu.engr.sgi.com
Subject: Re: Evidence of Drive Activity to Report
Date: Sun, 10 May 1998 23:19:23 -0400	[thread overview]
Message-ID: <35566E3B.109CCAA3@detroit.sgi.com> (raw)
In-Reply-To: 13653.59491.302730.251578@mdhill.interlog.com

I had the exact same problem - I needed to re-make the ext2fs
filesystem on the drive and re-perform the install for it to get
further.

Eric.


Michael Hill wrote:
> 
> Okay, let's say it was just fsck that got hung up, and not the entire
> boot process.  When it stops with '[/sbin/fsck.ext2] fsck.ext2 -a /'
> and I press Ctrl-C, more information comes to light:
> 
> The superblock could not be read or does not describe a correct ext2
> filesystem.  If the device is valid and it really contains an ext2
> filesystem (and not swap or ufs or something else, the the superblock
> is corrupt, and you might try running e2fsck with an alternate superblock:
>     e2fsck -b 8193 <device>
> *** An error occurred during the file system check.
> *** Dropping you to a shell; the system will reboot
> *** when you leave the shell.
> Give root password for maintenance.
> INIT: entering runlevel: 0mal startup):
> while opening UTMP file: No such file or directory
> 
> ...then I get the SGI maintenance screen back.  There's no evidence of
> a shell when it tells me it's dropping me to a shell.  From IRIX I ran
> 'e2fsck -b 8193 drive' on the drive (with no improvement) but I don't
> think that's the appropriate context.  Suggestions?
> 
> Thanks,
> 
> Mike
> --
> Michael Hill
> Toronto, Canada
> mdhill@interlog.com

-- 
---------1---------2---------3---------4---------5---------6---------7
Eric Kimminau                           RTA/RSA
eak@detroit.sgi.com                     Silicon Graphics, Inc
Voice: (248) 848-4455                   39001 West 12 Mile Rd.
Fax:   (248) 848-5600                   Farmington, MI 48331-2903

                 VNet Extension - 6-327-4455
              "I speak my mind and no one else's."
       http://www.dcs.ex.ac.uk/~aba/rsa/perl-rsa-sig.html

    When confronted by a difficult problem, solve it by reducing 
    it to the question, "How would the Lone Ranger handle this?"
	
         "I am the great supportfolio, do you have http?"

        Copyright 1998, Silicon Graphics Computer Systems
        Confidential to Silicon Graphics Computer Systems
                ** -- not for redistribution -- **

  reply	other threads:[~1998-05-11  3:26 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
1998-05-10  3:05 Evidence of Drive Activity to Report Michael Hill
1998-05-10 19:20 ` Michael Hill
1998-05-11  3:19   ` Eric Kimminau [this message]
1998-05-11  7:33     ` ralf
1998-05-16 19:43       ` Michael Hill
1998-05-18  8:35         ` Leon Verrall
1998-05-18  9:12           ` ralf

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=35566E3B.109CCAA3@detroit.sgi.com \
    --to=eak@detroit.sgi.com \
    --cc=linux@cthulhu.engr.sgi.com \
    --cc=mdhill@interlog.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