linux-raid.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Bill Davidsen <davidsen@tmr.com>
To: Neil Brown <neilb@suse.de>
Cc: colli419@umn.edu, linux-raid@vger.kernel.org
Subject: Re: RAID Problem
Date: Sat, 20 Mar 2010 12:55:19 -0400	[thread overview]
Message-ID: <4BA4FDF7.8000401@tmr.com> (raw)
In-Reply-To: <20100317110943.793c8e7b@notabene.brown>

Neil Brown wrote:
> On 16 Mar 2010 18:32:39 -0500
> colli419@umn.edu wrote:
>
>   
>> Hello, I am having problems with my RAID as follows:
>>
>> I installed the drives in an old computer and created the RAID and it 
>> worked great. When I tried to install the same RAID set in a new computer I 
>> could get it to mount manually with some messing around but couldn't get it 
>> to mount automatically as in the old machine. I was wondering if zeroing 
>> the superblocks and trying to re-create the RAID would be a good idea. The 
>> data that is stored on the drives should otherwise be intact because I had 
>> it running just fine the other day. Any help at all would be most 
>> appreciated.
>>
>>     
>
> You haven't provides a lot of concrete information, like error messages
> during boot or "mdadm -E" output of devices or even kernel/mdadm versions, so
> I can only guess, but my guess would be that you can fix it by assembling
> the array with "--update=homehost"
>
> i.e.
>    mdadm --assemble /dev/mdwhatever  \
>    --update=homehost /dev/device1 /dev/device2 ....
>
>   

My take on hostname is that it causes more users problems than it helps, 
and that it would have been better as an option to the assemble function 
for those who actually need that checking. More people have little RAID 
USB boxes than have some shared storage.

Do *NOT* read this as a suggestion to change, just a comment on it as an 
example of "unintended results."

-- 
Bill Davidsen <davidsen@tmr.com>
  "We can't solve today's problems by using the same thinking we
   used in creating them." - Einstein


  reply	other threads:[~2010-03-20 16:55 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-03-16 23:32 RAID Problem colli419
2010-03-17  0:09 ` Neil Brown
2010-03-20 16:55   ` Bill Davidsen [this message]
  -- strict thread matches above, loose matches on Subject: below --
2013-08-14 20:49 RAID problem fixitdad5
2013-08-14 23:42 ` NeilBrown

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=4BA4FDF7.8000401@tmr.com \
    --to=davidsen@tmr.com \
    --cc=colli419@umn.edu \
    --cc=linux-raid@vger.kernel.org \
    --cc=neilb@suse.de \
    /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).