All of lore.kernel.org
 help / color / mirror / Atom feed
From: Phil Turmel <philip@turmel.org>
To: Thomas MARCHESSEAU <marchesseau@gmail.com>, linux-raid@vger.kernel.org
Cc: Roger Heflin <rogerheflin@gmail.com>
Subject: Re: RAID 5 "magicaly" become a RAID0
Date: Thu, 16 Apr 2015 08:25:57 -0400	[thread overview]
Message-ID: <552FAA55.9010104@turmel.org> (raw)
In-Reply-To: <D1554172.8F19F%marchesseau@gmail.com>

Good morning Thomas,

On 04/16/2015 04:53 AM, Thomas MARCHESSEAU wrote:
> Hi Team ,
> 
>>
>> Very good to hear this.
> It crashed once , but after a reboot and re-assemble ,  i¹ve backuped
> _everything_
>  
> -> Thank you very much for you support !

You're welcome.

>> Yes, just --add a spare device to the array, then --grow --level=6 to
>> start a live reshape.
> 
> I tryed , but it failed with many buffer I/O error , ( mostly on the  last
> 4 drives , ( not sure , but seems hosted on the same chipset)
> And now , i have tons of :
> Buffer I/O error on device sdf , logical block 12
> Š  logical block 11 Š and so on
> 
> Same on SDH  

You mentioned a possibly loose sata cable causing the initial problem.
I'm not so sure.  I think you should check your power supply.

The smartctl reports you supplied eliminate the most common problem,
timeout mismatch, as you have nice raid-rated drives.  The next most
common problem I've seen is insufficient power, which is most apparent
when writing.

Add up all of the power consumption ratings of your hardware to make
sure a new power supply is suitable.  And if you have/get a multiple
rail supply, make sure you spread the load across the independent circuits.

Phil
--
To unsubscribe from this list: send the line "unsubscribe linux-raid" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html

      reply	other threads:[~2015-04-16 12:25 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-04-12 21:42 RAID 5 "magicaly" become a RAID0 Thomas MARCHESSEAU
2015-04-12 22:28 ` Roger Heflin
2015-04-13  0:18 ` Phil Turmel
2015-04-13  8:55   ` Thomas MARCHESSEAU
2015-04-13 10:57     ` Phil Turmel
2015-04-13 12:27       ` Thomas MARCHESSEAU
     [not found]         ` <D151DEA1.8EEA1%marchesseau@gmail.com>
2015-04-14 12:32           ` Phil Turmel
2015-04-16  8:53             ` Thomas MARCHESSEAU
2015-04-16 12:25               ` Phil Turmel [this message]

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=552FAA55.9010104@turmel.org \
    --to=philip@turmel.org \
    --cc=linux-raid@vger.kernel.org \
    --cc=marchesseau@gmail.com \
    --cc=rogerheflin@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.