Linux RAID subsystem development
 help / color / mirror / Atom feed
From: Reindl Harald <h.reindl@thelounge.net>
To: linuxknight <linuxknight@gmail.com>, linux-raid@vger.kernel.org
Subject: Re: Linux software raid troubles
Date: Wed, 12 Apr 2017 17:29:17 +0200	[thread overview]
Message-ID: <cbadbdeb-7e6b-7784-e49c-dd2801903bb6@thelounge.net> (raw)
In-Reply-To: <CAAO=44bsG1yrmYbag1eruNA_tdXxqiJptnRyPB=4TW6r5771HQ@mail.gmail.com>

please no private-only respones

Am 12.04.2017 um 16:52 schrieb linuxknight:
> Thanks you for the reply.  I was just examining the hardward in my
> server and it looks like there is an LSI card in there.  If I create a
> new Hardware raid mirror in that controller, is it possible to use the
> ddrescue to get my current OS onto that mirror and boot from it?  Im
> unfamiliar with the ddrescue but will certainly read up more.

"ddrescue" is at the end of the day the same as "dd"

it reads the whole drive block-by-block and writes it to a image file, 
later you can do "dd if=image.mig of=/dev/sdX bs=1M" and you get a 100% 
identical state of the disk

so just put out that drive, connect it to a ordinary SATA adapter, take 
the image and be happy that you have a backup, if the RAID-controller 
has stored whatever metadata on begin of the drive it's also part of the 
image

and hence leave out that controller to get a 100% block-by-block copy of 
the whole drive

> On Wed, Apr 12, 2017 at 10:45 AM, Reindl Harald <h.reindl@thelounge.net> wrote:
>>
>>
>> Am 12.04.2017 um 16:31 schrieb linuxknight:
>>>
>>> Last weekend I was moving a server with a raid1 configuration,
>>> controlled by a Intel Corporation 82801 SATA RAID Controller.  Upon
>>> reboot I noticed the degraded message (server hadnt been rebooted in a
>>> couple years).
>>>
>>> The raid1 array was two 500gb black WD drives.  I wasnt able to locate
>>> an identical 500gb disk, but did find a 2TB just to get things
>>> mirrored again.  The bios screen accepted the replacement disk and
>>> said it would rebuild in the OS.  mdsync seemed to do its thing but I
>>> noticed mdmon process was taking 200% cpu.  I let it go a few days
>>> thinking it was just taking longer than normal to sync, then rebooted.
>>> It was in a complete failed state and wouldnt boot at all.  After
>>> removing the 2TB disk I was able to boot into the OS again.  I just
>>> assumed I needed a similar drive size for the second part of the
>>> mirror.
>>
>>
>> when you talk about a "SATA RAID Controller" and "The bios screen accepted
>> the replacement disk and said it would rebuild in the OS" this sadly is not
>> a "linux software raid" at it's own
>>
>> 197 Current_Pending_Sector  -O--CK   200   200   000    -    9
>> 198 Offline_Uncorrectable   ----CK   200   200   000    -    7
>>
>> i would strongly suggest https://www.gnu.org/software/ddrescue/ and make a
>> image of that disk because after 39646 Power_On_Hours it's likely that the
>> remaining disk fails completly in a short time and you could at least
>> restore the disk-image with "dd" to a new disk if that happens as well as
>> mount it with as loop-device


  parent reply	other threads:[~2017-04-12 15:29 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-04-12 14:31 Linux software raid troubles linuxknight
2017-04-12 14:45 ` Reindl Harald
     [not found]   ` <CAAO=44bsG1yrmYbag1eruNA_tdXxqiJptnRyPB=4TW6r5771HQ@mail.gmail.com>
2017-04-12 15:29     ` Reindl Harald [this message]
2017-04-12 15:36       ` linuxknight
2017-04-12 16:11         ` Reindl Harald
2017-04-14  4:43         ` David C. Rankin
2017-04-14 15:01           ` linuxknight
2017-04-14 15:52             ` Reindl Harald
2017-04-14 19:23             ` Anthony Youngman
  -- strict thread matches above, loose matches on Subject: below --
2017-04-12 14:06 linuxknight

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=cbadbdeb-7e6b-7784-e49c-dd2801903bb6@thelounge.net \
    --to=h.reindl@thelounge.net \
    --cc=linux-raid@vger.kernel.org \
    --cc=linuxknight@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox