All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Marcin M. Jessa" <lists@yazzy.org>
To: linux-raid@vger.kernel.org
Subject: Linux raid autodetect partition disappears after RAID degrade
Date: Sun, 02 Oct 2011 12:05:29 +0200	[thread overview]
Message-ID: <4E883769.2080402@yazzy.org> (raw)


Hi guys.

My RAID array just kicked out one of the drives again at heavy activity
running:
  # ddrescue -n -f /dev/fridge/storage storage.img ddrescue.log
where the /dev/fridge/storage LV Size is 4.88 TiB

What's strange is the device is there:
   brw-rw---- 1 root disk 8, 144 Oct  2 11:48 /dev/sdj

But the /dev/sdj1 which should hold Linux raid autodetect partition just 
disappeared...

  # fdisk -l /dev/sdj

Disk /dev/sdj: 2000.4 GB, 2000398934016 bytes
255 heads, 63 sectors/track, 243201 cylinders, total 3907029168 sectors
Units = sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 512 bytes / 512 bytes
Disk identifier: 0x00000000

    Device Boot      Start         End      Blocks   Id  System
/dev/sdj1              63  3907029167  1953514552+  fd  Linux raid 
autodetect


Is this a normal behavior? I don't understand either why the heck is the 
RAID degrading all the time ?
I replaced all the cables with SATA3 cables, the BIOS is updated, both 
the motherboard and the drives are SATA3 and brand new.

I could not find anything about the RAID being degraded or the device 
having problems in dmesg, /var/log/messages, /var/log/syslog or 
/var/log/kern.log


I'm on Debian Wheezy
  # uname -a
  Linux odin 3.0.0-1-amd64 #1 SMP Sat Aug 27 16:21:11 UTC 2011 x86_64 
GNU/Linux


-- 

Marcin M. Jessa

             reply	other threads:[~2011-10-02 10:05 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-10-02 10:05 Marcin M. Jessa [this message]
2011-10-02 17:13 ` Linux raid autodetect partition disappears after RAID degrade Marcin M. Jessa

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=4E883769.2080402@yazzy.org \
    --to=lists@yazzy.org \
    --cc=linux-raid@vger.kernel.org \
    /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.