From: Wols Lists <antlists@youngman.org.uk>
To: Daniel Sanabria <sanabria.d@gmail.com>
Cc: linux-raid@vger.kernel.org
Subject: Re: Inactive arrays
Date: Wed, 3 Aug 2016 22:31:31 +0100 [thread overview]
Message-ID: <57A262B3.70103@youngman.org.uk> (raw)
In-Reply-To: <CAHscji3CMO=ZREJypdUhsyKN0TmHWsEybdVLwWCbMZqWGdngOA@mail.gmail.com>
On 03/08/16 20:18, Daniel Sanabria wrote:
> Ok,
>
> Unfortunately the PSU replacement didn't help and I could be facing a
> failed motherboard/cpu :( My question now is, is it possible to
> restore the arrays in a new machine?
Your comment about the system starting up and shutting down almost
immediately implies to me a faulty on/off switch. It could be that
simple. Or of course, it could be worse. Like so many things nowadays,
on/off is controlled by software and if the switch is stuck ...
You might find all it needs is a new case. Or you might not.
But yes, if it's all linux software raid, then sticking the disks into a
new machine should work fine - the new machine should just come straight
up unless you're running an optimised kernel.
(That doesn't imply the arrays will :-( you might need a bit of fixing
for them, but if the machine boots successfully you're most of the way
there.)
Cheers,
Wol
next prev parent reply other threads:[~2016-08-03 21:31 UTC|newest]
Thread overview: 37+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-08-02 7:36 Inactive arrays Daniel Sanabria
2016-08-02 10:17 ` Wols Lists
2016-08-02 10:45 ` Daniel Sanabria
2016-08-03 19:18 ` Daniel Sanabria
2016-08-03 21:31 ` Wols Lists [this message]
2016-09-11 18:48 ` Daniel Sanabria
2016-09-11 20:06 ` Daniel Sanabria
2016-09-12 19:41 ` Daniel Sanabria
2016-09-12 21:13 ` Daniel Sanabria
2016-09-12 21:37 ` Chris Murphy
2016-09-13 6:51 ` Daniel Sanabria
2016-09-13 15:04 ` Chris Murphy
2016-09-12 21:39 ` Wols Lists
2016-09-13 6:56 ` Daniel Sanabria
2016-09-13 7:02 ` Adam Goryachev
2016-09-13 15:20 ` Chris Murphy
2016-09-13 19:43 ` Daniel Sanabria
2016-09-13 19:52 ` Chris Murphy
2016-09-13 20:04 ` Daniel Sanabria
2016-09-13 20:13 ` Chris Murphy
2016-09-13 20:29 ` Daniel Sanabria
2016-09-13 20:36 ` Daniel Sanabria
2016-09-13 21:10 ` Chris Murphy
2016-09-13 21:46 ` Daniel Sanabria
2016-09-13 21:26 ` Wols Lists
2016-09-14 4:33 ` Chris Murphy
2016-09-14 10:36 ` Daniel Sanabria
2016-09-14 14:32 ` Chris Murphy
2016-09-14 14:57 ` Daniel Sanabria
2016-09-14 15:15 ` Chris Murphy
2016-09-14 15:47 ` Daniel Sanabria
2016-09-14 16:10 ` Chris Murphy
2016-09-14 16:13 ` Chris Murphy
2016-09-14 18:16 ` Daniel Sanabria
2016-09-14 18:37 ` Chris Murphy
2016-09-14 18:42 ` Wols Lists
2016-09-15 9:21 ` Brad Campbell
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=57A262B3.70103@youngman.org.uk \
--to=antlists@youngman.org.uk \
--cc=linux-raid@vger.kernel.org \
--cc=sanabria.d@gmail.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 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.