From: Roman Mamedov <rm@romanrm.net>
To: Adam Thompson <athompso@athompso.net>
Cc: MUUG Roundtable <roundtable@muug.ca>, linux-raid@vger.kernel.org
Subject: Re: Big-endian RAID5 recovery problem
Date: Tue, 2 May 2017 13:59:34 +0500 [thread overview]
Message-ID: <20170502135934.59548e17@natsu> (raw)
In-Reply-To: <5c6e6e5d93d4056839e4f370e00a8e08@mail.athompso.net>
On Mon, 01 May 2017 16:39:07 -0500
Adam Thompson <athompso@athompso.net> wrote:
> I can't find any modern big-endian Linux systems... looks like all the
> ARM distros run in little-endian mode.
Here are QEMU images for debian-mips (should be big-endian, as opposed to
debian-mipsel): https://people.debian.org/~aurel32/qemu/mips/
Of course it will run purely in software, but most likely more than fast enough
to copy away the data.
Not entirely sure that particular emulated MIPS system support more than 4
drives), but it appears that a starting point could be (man qemu-system):
Instead of -hda, -hdb, -hdc, -hdd, you can use:
qemu-system-i386 -drive file=file,index=0,media=disk
qemu-system-i386 -drive file=file,index=1,media=disk
qemu-system-i386 -drive file=file,index=2,media=disk
qemu-system-i386 -drive file=file,index=3,media=disk
with indexes 0..5, as you need the boot disk, all 4 drives, and one more as
the backup destination.
May or may not be the best way, but IMO beats trying to hex-edit the
superblock right away.
--
With respect,
Roman
next prev parent reply other threads:[~2017-05-02 8:59 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-05-01 21:39 Big-endian RAID5 recovery problem Adam Thompson
2017-05-01 21:59 ` Anthony Youngman
2017-05-01 22:33 ` Adam Thompson
2017-05-02 2:47 ` Phil Turmel
2017-05-02 7:29 ` [RndTbl] " Trevor Cordes
2017-05-02 8:59 ` Roman Mamedov [this message]
2017-05-05 19:22 ` Adam Thompson
2017-05-06 5:57 ` NeilBrown
2017-05-06 6:41 ` [RndTbl] " Trevor Cordes
2017-05-07 23:40 ` [mdadm PATCH] Mention "endian" in documentation for --update=byte-order NeilBrown
2017-05-08 17:42 ` Jes Sorensen
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=20170502135934.59548e17@natsu \
--to=rm@romanrm.net \
--cc=athompso@athompso.net \
--cc=linux-raid@vger.kernel.org \
--cc=roundtable@muug.ca \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.