linux-raid.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Harry Mangalam <harry.mangalam@uci.edu>
To: Nagilum <nagilum@nagilum.org>
Cc: linux-raid <linux-raid@vger.kernel.org>
Subject: Re: rescue an alien md raid5
Date: Mon, 2 Mar 2009 08:57:58 -0800	[thread overview]
Message-ID: <200903020857.58595.harry.mangalam@uci.edu> (raw)
In-Reply-To: <20090302122238.67785n3th69tw4w8@cakebox.home>

that's a good idea...if we can subvert the NAS box to boot an 
alternative system.  There's no CD, but there is a USB port, so we 
could try to boot a USB ARM distro.  One problem with this is that 
there's no video system so it's all blind until we can log into it, 
unless there's some hidden video tap on the mobo.

I'll check into that - thank you for the idea.

Harry

On Monday 02 March 2009, Nagilum wrote:
> >> The docs and files on the USR web site imply that the native
> >> filesystem was originally XFS, but when i try to mount it as
> >> such, I can't:
> >
> > I heard Dave Chinner talking about this during LCA-2009.
> > If I remember correctly, there is something a bit funny about
> > structure layout and padding on the ARM and it affects XFS is
> > some strange way, and some NAS vendors 'fixed' it the wrong way,
> > so they are incompatible with mainline..... or something like
> > that.  What I really remember is ARM + XFS + NAS == BAD Vendor
> >
> > I suggest asking at xfs@oss.sgi.com
> >
> > No, those other partitions are relevant.  One was clearly for
> > swap.  The other was probably /boot.
>
> Maybe it can be salvaged using QEMU?
> There are even preconfigured ARM environments available:
> http://www.scratchbox.org/
>
>
>
>
> ===================================================================
>===== #    _  __          _ __     http://www.nagilum.org/ \n
> icq://69646724 # #   / |/ /__ ____ _(_) /_ ____ _ 
> nagilum@nagilum.org \n +491776461165 # #  /    / _ `/ _ `/ / / // /
>  ' \  Amiga (68k/PPC): AOS/NetBSD/Linux   # # /_/|_/\_,_/\_,
> /_/_/\_,_/_/_/_/   Mac (PPC): MacOS-X / NetBSD /Linux # #          
> /___/     x86: FreeBSD/Linux/Solaris/Win2k  ARM9: EPOC EV6 #
> ===================================================================
>=====
>
>
> ----------------------------------------------------------------
> cakebox.homeunix.net - all the machine one needs..



-- 
Harry Mangalam - Research Computing, NACS, E2148, Engineering Gateway, 
UC Irvine 92697  949 824-0084(o), 949 285-4487(c)
---
Good judgment comes from experience; 
Experience comes from bad judgment. [F. Brooks.]

  reply	other threads:[~2009-03-02 16:57 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-02-23 18:13 rescue an alien md raid5 Harry Mangalam
2009-02-23 18:58 ` Joe Landman
2009-02-23 19:59   ` Harry Mangalam
2009-02-23 19:14 ` NeilBrown
2009-02-23 20:04   ` Harry Mangalam
2009-03-02 11:22   ` Nagilum
2009-03-02 16:57     ` Harry Mangalam [this message]
2009-02-24  0:56 ` hgichon
2009-02-24 21:11   ` Harry Mangalam
2009-03-14 14:12     ` Ryan Wagoner
2009-03-14 18:15       ` Harry Mangalam

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=200903020857.58595.harry.mangalam@uci.edu \
    --to=harry.mangalam@uci.edu \
    --cc=linux-raid@vger.kernel.org \
    --cc=nagilum@nagilum.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).