All of lore.kernel.org
 help / color / mirror / Atom feed
From: drtebi@drtebi.com
To: Neil Brown <neilb@cse.unsw.edu.au>
Cc: linux-raid@vger.kernel.org
Subject: Re: RAID1 always resyncs at boot???
Date: Thu, 27 Nov 2003 20:33:07 -0800	[thread overview]
Message-ID: <hp1on7.90c5en@mail.drtebi.com> (raw)
In-Reply-To: <16326.36888.900928.183987@notabene.cse.unsw.edu.au>

Well,
I thought it was fixed, but I suppose I was wrong... 

OK, I admit I was a bit brutal, but anyway.
The problem is that I have power outages here once in a while, it's something
with the wiring in this appartment (yes, I am running this server at home,
have an UPS, but it only lasts 40 min.).
 
So I pulled the plug of the server to give it a test, to see if it comes back
up fine and will reconstruct the array right.

Everything comes back up fine, the RAID array starts reconstructing. But after
an hour or so I find this:

/proc/mdstat:
Nov 28 04:41:56 [kernel] md: md_do_sync() got signal ... exiting
Nov 28 04:41:56 [kernel] raid1: mirror resync was not fully finished,
restarting next time.

.
/bus1/target0/lun0/part1


in my log:
Nov 28 04:41:44 [kernel] hda: dma_intr: status=0x51 { DriveReady SeekComplete
Error }
Nov 28 04:41:44 [kernel] md: (skipping faulty
ide/host0/bus0/target0/lun0/part1 )
Nov 28 04:41:45 [kernel] hda: dma_intr: status=0x51 { DriveReady SeekComplete
Error }
                - Last output repeated 8 times -
Nov 28 04:41:56 [kernel] md: md_do_sync() got signal ... exiting
Nov 28 04:41:56 [kernel] raid1: mirror resync was not fully finished,
restarting next time.

Does this mean one of the drives is bad?

Here is some more info from mdadm:
bully@drtebi: mdadm --detail /dev/md0
/dev/md0:
        Version : 00.90.00
  Creation Time : Thu Nov 27 01:46:27 2003
     Raid Level : raid1
     Array Size : 120053632 (114.49 GiB 122.93 GB)
    Device Size : 120053632 (114.49 GiB 122.93 GB)
   Raid Devices : 2
  Total Devices : 2
Preferred Minor : 0
    Persistence : Superblock is persistent

    Update Time : Fri Nov 28 04:41:44 2003
          State : dirty, no-errors
 Active Devices : 1
Working Devices : 1
 Failed Devices : 1
  Spare Devices : 0


    Number   Major   Minor   RaidDevice State
       0       3        1        0      faulty  
/dev/ide/host0/bus0/target0/lun0/part1
       1      22        1        1      active sync  
/dev/ide/host0/bus1/target0/lun0/part1
           UUID : 96c32ab9:7f492b81:623580da:29d8a727
         Events : 0.16

------------
bully@drtebi: mdadm --examine /dev/hda1
/dev/hda1:
          Magic : a92b4efc
        Version : 00.90.00
           UUID : 96c32ab9:7f492b81:623580da:29d8a727
  Creation Time : Thu Nov 27 01:46:27 2003
     Raid Level : raid1
    Device Size : 120053632 (114.49 GiB 122.93 GB)
   Raid Devices : 2
  Total Devices : 2
Preferred Minor : 0

    Update Time : Fri Nov 28 04:32:17 2003
          State : dirty, no-errors
 Active Devices : 2
Working Devices : 2
 Failed Devices : 0
  Spare Devices : 0
       Checksum : d1fbb8ef - correct
         Events : 0.15


      Number   Major   Minor   RaidDevice State
this     0       3        1        0      active sync  
/dev/ide/host0/bus0/target0/lun0/part1
   0     0       3        1        0      active sync  
/dev/ide/host0/bus0/target0/lun0/part1
   1     1      22        1        1      active sync  
/dev/ide/host0/bus1/target0/lun0/part1

bully@drtebi: mdadm --examine /dev/hda1
/dev/hda1:
          Magic : a92b4efc
        Version : 00.90.00
           UUID : 96c32ab9:7f492b81:623580da:29d8a727
  Creation Time : Thu Nov 27 01:46:27 2003
     Raid Level : raid1
    Device Size : 120053632 (114.49 GiB 122.93 GB)
   Raid Devices : 2
  Total Devices : 2
Preferred Minor : 0

    Update Time : Fri Nov 28 04:32:17 2003
          State : dirty, no-errors
 Active Devices : 2
Working Devices : 2
 Failed Devices : 0
  Spare Devices : 0
       Checksum : d1fbb8ef - correct
         Events : 0.15


      Number   Major   Minor   RaidDevice State
this     0       3        1        0      active sync  
/dev/ide/host0/bus0/target0/lun0/part1
   0     0       3        1        0      active sync  
/dev/ide/host0/bus0/target0/lun0/part1
   1     1      22        1        1      active sync  
/dev/ide/host0/bus1/target0/lun0/part1

-------------
bully@drtebi: mdadm --query /dev/md0
/dev/md0: 114.49GiB raid1 2 devices, 0 spares. Use mdadm --detail for more
detail.
/dev/md0: No md super block found, not an md component.

The last message is weird... no md super block?

Thanks,
DrTebi

P.S.: I don't really like IDE drives :(



  reply	other threads:[~2003-11-28  4:33 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-11-27 15:13 RAID1 always resyncs at boot??? drtebi
2003-11-27 23:14 ` Neil Brown
2003-11-27 23:29   ` drtebi
2003-11-28  0:00     ` Neil Brown
2003-11-28  4:33       ` drtebi [this message]
2003-11-28  4:40         ` Neil Brown
2003-11-28  4:57           ` drtebi
2003-11-30  3:31             ` Ricky Beam
2003-11-30  6:19               ` drtebi

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=hp1on7.90c5en@mail.drtebi.com \
    --to=drtebi@drtebi.com \
    --cc=linux-raid@vger.kernel.org \
    --cc=neilb@cse.unsw.edu.au \
    /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.