linux-raid.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Bill Davidsen <davidsen@tmr.com>
To: jeff sacksteder <jsacksteder@gmail.com>
Cc: john <john4lists@gmail.com>,
	Mario 'BitKoenig' Holbe <Mario.Holbe@tu-ilmenau.de>,
	linux-raid@vger.kernel.org
Subject: Re: emergency recovery
Date: Fri, 11 Apr 2008 10:35:02 -0400	[thread overview]
Message-ID: <47FF7716.7010306@tmr.com> (raw)
In-Reply-To: <51c8a7be0804101645k207bc08bu45ecc16a589e7b27@mail.gmail.com>

jeff sacksteder wrote:
> I should also note that I'm doing this from a liveCD and though I have
> modprobe-ed the appropriate modules, I still don't see the node in
> /dev for md0.

You can try doing an assemble with force after backing up whatever you 
feel you should (or can). Assuming you get an array at that point, you 
can do an information only file system check (fsck -n) to see what the 
state of the f/s might be. You can also run the 'check' action to see 
how unhappy mdadm thinks things are.

By that time you will have information to use or report back to the list 
for more ideas.

-- 
Bill Davidsen <davidsen@tmr.com>
  "Woe unto the statesman who makes war without a reason that will still
  be valid when the war is over..." Otto von Bismark 



      reply	other threads:[~2008-04-11 14:35 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-04-10  6:29 emergency recovery jeff sacksteder
2008-04-10  6:38 ` Mario 'BitKoenig' Holbe
2008-04-10 13:08   ` john
2008-04-10 13:17     ` Mario 'BitKoenig' Holbe
2008-04-10 16:09   ` john
2008-04-10 23:13     ` jeff sacksteder
2008-04-10 23:45       ` jeff sacksteder
2008-04-11 14:35         ` Bill Davidsen [this message]

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=47FF7716.7010306@tmr.com \
    --to=davidsen@tmr.com \
    --cc=Mario.Holbe@tu-ilmenau.de \
    --cc=john4lists@gmail.com \
    --cc=jsacksteder@gmail.com \
    --cc=linux-raid@vger.kernel.org \
    /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;
as well as URLs for NNTP newsgroup(s).