linux-raid.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Maurice Hilarius <maurice@harddata.com>
To: linux-raid@vger.kernel.org
Subject: Question: how to identify failing disk in a RAID1
Date: Sun, 13 Apr 2008 13:14:21 -0600	[thread overview]
Message-ID: <48025B8D.2030803@harddata.com> (raw)

Hi there.

Recently I have been frequently seeing a damaged filesystem on a RAID1 
on boot.
a lengthy fsck does get it working, but I am seeing files disappearing 
as a result.

I am pretty sure that one of the drives has developed some issues and 
needs to be replaced.

How does one identify which of the 2 disks is the one that is failing?

The system has 2 identical disks, and  / is on md0

fstab:
/dev/md0                /                       ext3    defaults        1 1
LABEL=/boot1            /boot                   ext2    defaults        1 2
tmpfs                   /dev/shm                tmpfs   defaults        0 0
devpts                  /dev/pts                devpts  gid=5,mode=620  0 0
sysfs                   /sys                    sysfs   defaults        0 0
proc                    /proc                   proc    defaults        0 0
LABEL=/boot11           /boot1                  ext2    defaults        1 2
LABEL=SWAP-sdb3         swap                    swap    defaults        0 0
LABEL=SWAP-sda2         swap                    swap    defaults        0 0

fdisk -l shows me:
Disk /dev/sda: 400.0 GB, 400088457216 bytes
255 heads, 63 sectors/track, 48641 cylinders
Units = cylinders of 16065 * 512 = 8225280 bytes

   Device Boot      Start         End      Blocks   Id  System
/dev/sda1   *           1          13      104391   83  Linux
/dev/sda2              14         535     4192965   82  Linux swap / Solaris
/dev/sda3             536       48641   386411445   fd  Linux raid 
autodetect

Disk /dev/sdb: 400.0 GB, 400088457216 bytes
255 heads, 63 sectors/track, 48641 cylinders
Units = cylinders of 16065 * 512 = 8225280 bytes

   Device Boot      Start         End      Blocks   Id  System
/dev/sdb1   *           1          13      104391   83  Linux
/dev/sdb2              14       48118   386403412+  fd  Linux raid 
autodetect
/dev/sdb3           48119       48640     4192965   82  Linux swap / Solaris

Disk /dev/md0: 395.6 GB, 395677007872 bytes
2 heads, 4 sectors/track, 96600832 cylinders
Units = cylinders of 8 * 512 = 4096 bytes

Anyone have a suggestion, please?
Responses off list are probably most appropriate.

Thanks for any help.

-- 
Regards, Maurice
mhilarius@gmail.com




             reply	other threads:[~2008-04-13 19:14 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-04-13 19:14 Maurice Hilarius [this message]
2008-04-13 19:29 ` Question: how to identify failing disk in a RAID1 Justin Piszcz
2008-04-14  1:14   ` Bill Davidsen
     [not found]     ` <4802CDA2.605@harddata.com>
2008-04-14 16:38       ` Bill Davidsen
     [not found]         ` <4804CD4F.7080303@harddata.com>
2008-04-15 18:14           ` Bill Davidsen
     [not found]             ` <48050DD6.7020404@harddata.com>
     [not found]               ` <48055EFA.8060505@tmr.com>
     [not found]                 ` <480607F2.3060504@harddata.com>
2008-04-17 13:12                   ` Bill Davidsen
     [not found]                     ` <48076096.2020804@harddata.com>
2008-04-18 13:17                       ` Bill Davidsen
     [not found]     ` <480F7105.9030405@harddata.com>
2008-04-23 18:54       ` Justin Piszcz
     [not found]         ` <480F8830.6020207@harddata.com>
2008-04-23 19:26           ` Justin Piszcz
2008-04-27 17:03             ` Keith Roberts
2008-04-27 19:28               ` Richard Scobie
2008-04-28  5:29                 ` Keith Roberts
2008-04-28  6:06                   ` Michael Tokarev
2008-04-28  7:01                   ` Richard Scobie
2008-04-27 21:53               ` Mark Hahn
  -- strict thread matches above, loose matches on Subject: below --
2008-04-18 17:36 David Lethe

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=48025B8D.2030803@harddata.com \
    --to=maurice@harddata.com \
    --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 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).