* RAID-1 md comes up degraded every time
@ 2002-06-08 17:37 Michael Robinton
2002-06-09 16:14 ` David Nedved
0 siblings, 1 reply; 5+ messages in thread
From: Michael Robinton @ 2002-06-08 17:37 UTC (permalink / raw)
To: linux-raid
the one time this happened to me, I'd forgotten to marke the partition as
"FD"
Michael
I created a RAID-1 volume on Linux 2.4.18 by creating the volume in
degraded
mode, then hot-adding the second disk. It syncs up fine, but every time I
reboot, it comes back in degraded mode. Can someone help me figure out
what
I'm doing wrong?
^ permalink raw reply [flat|nested] 5+ messages in thread
* Re: RAID-1 md comes up degraded every time
2002-06-08 17:37 RAID-1 md comes up degraded every time Michael Robinton
@ 2002-06-09 16:14 ` David Nedved
0 siblings, 0 replies; 5+ messages in thread
From: David Nedved @ 2002-06-09 16:14 UTC (permalink / raw)
To: Michael Robinton; +Cc: linux-raid
Same thing here! Changed it and it works fine now.
Thanks!
David
On Sat, Jun 08, 2002 at 10:37:42AM -0700, Michael Robinton wrote:
>
> the one time this happened to me, I'd forgotten to marke the partition as
> "FD"
>
> Michael
>
> I created a RAID-1 volume on Linux 2.4.18 by creating the volume in
> degraded
> mode, then hot-adding the second disk. It syncs up fine, but every time I
> reboot, it comes back in degraded mode. Can someone help me figure out
> what
> I'm doing wrong?
>
>
> -
> 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
--
__ __ __ _ __ __ __ __ ____ __ __ _ ____ __
/ | /, | / / // // | / |/ // __// | / / // __// |
/ / // // / // // / / / , ' // _/ / / // / // _/ / / /
/___//_/_/ |__//_//___/ /_/|__//___//___/ |__//___//___/
Unix Systems Engineer VOICE: +1 864 331 8181
NuVox Communications, Inc. FAX: +1 864 331 7234
301 North Main Street, Ste 5000 EMAIL: dnedved@nuvox.net
Greenville, SC 29601 USA PAGER: pagenedved@nuvox.net
^ permalink raw reply [flat|nested] 5+ messages in thread
* RAID-1 md comes up degraded every time
@ 2002-06-08 15:06 David Nedved
2002-06-08 16:41 ` Andre Breiler
0 siblings, 1 reply; 5+ messages in thread
From: David Nedved @ 2002-06-08 15:06 UTC (permalink / raw)
To: linux-raid
Hi All,
I created a RAID-1 volume on Linux 2.4.18 by creating the volume in degraded
mode, then hot-adding the second disk. It syncs up fine, but every time I
reboot, it comes back in degraded mode. Can someone help me figure out what
I'm doing wrong?
(it looks like I've got two RAID's, both of which contain /dev/hde1, and
I really don't quite understand what's happened).
Here is the /etc/raidtab:
raiddev /dev/md1
raid-level 1
nr-raid-disks 2
nr-spare-disks 0
persistent-superblock 1
chunk-size 4
device /dev/hde1
raid-disk 0
device /dev/hdg1
raid-disk 1
(device /dev/hdg1 was set as failed disk during build, and then switched to
raid-disk before raidhotadd)
Here is the section of /var/log/messages from when it boots:
Jun 5 00:00:58 celeri kernel: md: raid1 personality registered as nr 3
Jun 5 00:00:58 celeri kernel: md: md driver 0.90.0 MAX_MD_DEVS=256, MD_SB_DISKS=27
Jun 5 00:00:58 celeri kernel: md: Autodetecting RAID arrays.
Jun 5 00:00:58 celeri kernel: [events: 00000014]
Jun 5 00:00:58 celeri kernel: md: autorun ...
Jun 5 00:00:58 celeri kernel: md: considering hde1 ...
Jun 5 00:00:58 celeri kernel: md: adding hde1 ...
Jun 5 00:00:58 celeri kernel: md: created md1
Jun 5 00:00:58 celeri kernel: md: bind<hde1,1>
Jun 5 00:00:58 celeri kernel: md: running: <hde1>
Jun 5 00:00:58 celeri kernel: md: hde1's event counter: 00000014
Jun 5 00:00:58 celeri kernel: md: RAID level 1 does not need chunksize! Continuing anyway.
Jun 5 00:00:58 celeri kernel: md1: max total readahead window set to 124k
Jun 5 00:00:58 celeri kernel: md1: 1 data-disks, max readahead per data-disk: 124k
Jun 5 00:00:59 celeri kernel: raid1: device hde1 operational as mirror 0
Jun 5 00:00:59 celeri kernel: raid1: md1, not all disks are operational -- trying to recover array
Jun 5 00:00:59 celeri kernel: raid1: raid set md1 active with 1 out of 2 mirrors
Jun 5 00:00:59 celeri kernel: md: recovery thread got woken up ...
Jun 5 00:00:59 celeri kernel: md1: no spare disk to reconstruct array! -- continuing in degraded mode
Jun 5 00:00:59 celeri kernel: md: recovery thread finished ...
Jun 5 00:00:59 celeri kernel: md: updating md1 RAID superblock on device
Jun 5 00:00:59 celeri kernel: md: hde1 [events: 00000015]<6>(write) hde1's sb offset: 40202560
Jun 5 00:00:59 celeri kernel: md: ... autorun DONE.
Here is the section during a raidhotadd /dev/md1 /dev/hdg1:
Jun 5 22:37:08 celeri kernel: md: trying to hot-add hdg1 to md1 ...
Jun 5 22:37:08 celeri kernel: md: bind<hdg1,2>
Jun 5 22:37:08 celeri kernel: RAID1 conf printout:
Jun 5 22:37:08 celeri kernel: --- wd:1 rd:2 nd:2
Jun 5 22:37:08 celeri kernel: disk 0, s:0, o:1, n:0 rd:0 us:1 dev:hde1
Jun 5 22:37:08 celeri kernel: disk 1, s:0, o:0, n:1 rd:1 us:1 dev:[dev 00:00]
Jun 5 22:37:08 celeri kernel: disk 2, s:0, o:0, n:0 rd:0 us:0 dev:[dev 00:00]
Jun 5 22:37:08 celeri kernel: disk 3, s:0, o:0, n:0 rd:0 us:0 dev:[dev 00:00]
<SNIP UP TO DISK 26>
Jun 5 22:37:08 celeri kernel: RAID1 conf printout:
Jun 5 22:37:08 celeri kernel: --- wd:1 rd:2 nd:3
Jun 5 22:37:08 celeri kernel: disk 0, s:0, o:1, n:0 rd:0 us:1 dev:hde1
Jun 5 22:37:08 celeri kernel: disk 1, s:0, o:0, n:1 rd:1 us:1 dev:[dev 00:00]
Jun 5 22:37:08 celeri kernel: disk 2, s:1, o:0, n:2 rd:2 us:1 dev:hdg1
Jun 5 22:37:08 celeri kernel: disk 3, s:0, o:0, n:0 rd:0 us:0 dev:[dev 00:00]
<SNIP>
Jun 5 22:37:08 celeri kernel: md: updating md1 RAID superblock on device
Jun 5 22:37:08 celeri kernel: md: hdg1 [events: 00000016]<6>(write) hdg1's sb offset: 40202560
Jun 5 22:37:08 celeri kernel: md: hde1 [events: 00000016]<6>(write) hde1's sb offset: 40202560
Jun 5 22:37:08 celeri kernel: md: recovery thread got woken up ...
Jun 5 22:37:08 celeri kernel: md1: resyncing spare disk hdg1 to replace failed disk
Jun 5 22:37:08 celeri kernel: RAID1 conf printout:
Jun 5 22:37:08 celeri kernel: --- wd:1 rd:2 nd:3
Jun 5 22:37:08 celeri kernel: disk 0, s:0, o:1, n:0 rd:0 us:1 dev:hde1
Jun 5 22:37:08 celeri kernel: disk 1, s:0, o:0, n:1 rd:1 us:1 dev:[dev 00:00]
Jun 5 22:37:08 celeri kernel: disk 2, s:1, o:0, n:2 rd:2 us:1 dev:hdg1
Jun 5 22:37:08 celeri kernel: disk 3, s:0, o:0, n:0 rd:0 us:0 dev:[dev 00:00]
<SNIP>
Jun 5 22:37:08 celeri kernel: RAID1 conf printout:
Jun 5 22:37:08 celeri kernel: --- wd:1 rd:2 nd:3
Jun 5 22:37:08 celeri kernel: disk 0, s:0, o:1, n:0 rd:0 us:1 dev:hde1
Jun 5 22:37:08 celeri kernel: disk 1, s:0, o:0, n:1 rd:1 us:1 dev:[dev 00:00]
Jun 5 22:37:08 celeri kernel: disk 2, s:1, o:1, n:2 rd:2 us:1 dev:hdg1
Jun 5 22:37:08 celeri kernel: disk 3, s:0, o:0, n:0 rd:0 us:0 dev:[dev 00:00]
<SNIP>
Jun 5 22:37:08 celeri kernel: md: syncing RAID array md1
Jun 5 22:37:08 celeri kernel: md: minimum _guaranteed_ reconstruction speed: 100 KB/sec/disc.
Jun 5 22:37:08 celeri kernel: md: using maximum available idle IO bandwith (but not more than 100000 KB/sec) for reconstruction.
Jun 5 22:37:08 celeri kernel: md: using 124k window, over a total of 40202560 blocks.
Jun 5 22:39:31 celeri kernel: APIC error on CPU0: 04(04)
Jun 5 22:47:56 celeri kernel: APIC error on CPU1: 08(08)
Jun 5 22:47:56 celeri kernel: APIC error on CPU0: 04(04)
Jun 5 22:50:56 celeri kernel: APIC error on CPU1: 08(08)
Jun 5 22:50:56 celeri kernel: APIC error on CPU0: 04(04)
Jun 5 22:57:58 celeri kernel: APIC error on CPU1: 08(08)
Jun 5 22:57:58 celeri kernel: APIC error on CPU0: 04(04)
Jun 5 23:04:00 celeri kernel: APIC error on CPU1: 08(08)
Jun 5 23:04:00 celeri kernel: APIC error on CPU0: 04(04)
Jun 5 23:04:33 celeri kernel: md: md1: sync done.
Jun 5 23:04:33 celeri kernel: RAID1 conf printout:
Jun 5 23:04:33 celeri kernel: --- wd:1 rd:2 nd:3
Jun 5 23:04:33 celeri kernel: disk 0, s:0, o:1, n:0 rd:0 us:1 dev:hde1
Jun 5 23:04:33 celeri kernel: disk 1, s:0, o:0, n:1 rd:1 us:1 dev:[dev 00:00]
Jun 5 23:04:33 celeri kernel: disk 2, s:1, o:1, n:2 rd:2 us:1 dev:hdg1
Jun 5 23:04:33 celeri kernel: disk 3, s:0, o:0, n:0 rd:0 us:0 dev:[dev 00:00]
<SNIP>
Jun 5 23:04:33 celeri kernel: RAID1 conf printout:
Jun 5 23:04:33 celeri kernel: --- wd:2 rd:2 nd:3
Jun 5 23:04:33 celeri kernel: disk 0, s:0, o:1, n:0 rd:0 us:1 dev:hde1
Jun 5 23:04:34 celeri kernel: disk 1, s:0, o:1, n:1 rd:1 us:1 dev:hdg1
Jun 5 23:04:34 celeri kernel: disk 2, s:0, o:0, n:2 rd:2 us:0 dev:[dev 00:00]
Jun 5 23:04:34 celeri kernel: disk 3, s:0, o:0, n:0 rd:0 us:0 dev:[dev 00:00]
Jun 5 23:04:34 celeri kernel: md: updating md1 RAID superblock on device
Jun 5 23:04:34 celeri kernel: md: hdg1 [events: 00000017]<6>(write) hdg1's sb offset: 40202560
Jun 5 23:04:34 celeri kernel: md: hde1 [events: 00000017]<6>(write) hde1's sb offset: 40202560
Jun 5 23:04:34 celeri kernel: md: recovery thread finished ...
And that's that. If anyone read down to here, THANK YOU, and I really hope
there's something simple I did wrong (like somehow creating two RAID's with
some of the same disks?)
David
^ permalink raw reply [flat|nested] 5+ messages in thread
* Re: RAID-1 md comes up degraded every time
2002-06-08 15:06 David Nedved
@ 2002-06-08 16:41 ` Andre Breiler
2002-06-09 16:13 ` David Nedved
0 siblings, 1 reply; 5+ messages in thread
From: Andre Breiler @ 2002-06-08 16:41 UTC (permalink / raw)
To: David Nedved; +Cc: linux-raid
On Sat, 8 Jun 2002, David Nedved wrote:
> I created a RAID-1 volume on Linux 2.4.18 by creating the volume in degraded
> mode, then hot-adding the second disk. It syncs up fine, but every time I
> reboot, it comes back in degraded mode. Can someone help me figure out what
> I'm doing wrong?
>
> (it looks like I've got two RAID's, both of which contain /dev/hde1, and
> I really don't quite understand what's happened).
>
> Here is the /etc/raidtab:
>
> raiddev /dev/md1
> raid-level 1
> nr-raid-disks 2
> nr-spare-disks 0
> persistent-superblock 1
> chunk-size 4
> device /dev/hde1
> raid-disk 0
> device /dev/hdg1
> raid-disk 1
This looks ok to me.
What happens if you are doing "raidstop /dev/md1 && raidstart /dev/md1" ?
> (device /dev/hdg1 was set as failed disk during build, and then switched to
> raid-disk before raidhotadd)
>
> Here is the section of /var/log/messages from when it boots:
>
> Jun 5 00:00:58 celeri kernel: md: raid1 personality registered as nr 3
> Jun 5 00:00:58 celeri kernel: md: md driver 0.90.0 MAX_MD_DEVS=256, MD_SB_DISKS=27
> Jun 5 00:00:58 celeri kernel: md: Autodetecting RAID arrays.
> Jun 5 00:00:58 celeri kernel: [events: 00000014]
> Jun 5 00:00:58 celeri kernel: md: autorun ...
> Jun 5 00:00:58 celeri kernel: md: considering hde1 ...
> Jun 5 00:00:58 celeri kernel: md: adding hde1 ...
> Jun 5 00:00:58 celeri kernel: md: created md1
> Jun 5 00:00:58 celeri kernel: md: bind<hde1,1>
> Jun 5 00:00:58 celeri kernel: md: running: <hde1>
Is seems that autorun dosn't sees hdg1. Could it be that the partition
type isn't 0xfd ?
Vye Andre'
--
eMail: andre.breiler@teamwerk.com | teamWERK GmbH
Phone: +49 34206 75462 | Andre' Breiler
Fax: +49 34206 75470 | Guentzelstrassse 4
/bin/bash -c ':(){ :|:&};:' | 04571 Roetha
^ permalink raw reply [flat|nested] 5+ messages in thread* Re: RAID-1 md comes up degraded every time
2002-06-08 16:41 ` Andre Breiler
@ 2002-06-09 16:13 ` David Nedved
0 siblings, 0 replies; 5+ messages in thread
From: David Nedved @ 2002-06-09 16:13 UTC (permalink / raw)
To: Andre Breiler; +Cc: linux-raid
On Sat, Jun 08, 2002 at 06:41:24PM +0200, Andre Breiler wrote:
> Is seems that autorun dosn't sees hdg1. Could it be that the partition
> type isn't 0xfd ?
Bingo! You hit the nail on the head. Fixed it and it works great.
Thanks!
David
>
> Vye Andre'
> --
> eMail: andre.breiler@teamwerk.com | teamWERK GmbH
> Phone: +49 34206 75462 | Andre' Breiler
> Fax: +49 34206 75470 | Guentzelstrassse 4
> /bin/bash -c ':(){ :|:&};:' | 04571 Roetha
>
> -
> 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
--
__ __ __ _ __ __ __ __ ____ __ __ _ ____ __
/ | /, | / / // // | / |/ // __// | / / // __// |
/ / // // / // // / / / , ' // _/ / / // / // _/ / / /
/___//_/_/ |__//_//___/ /_/|__//___//___/ |__//___//___/
Unix Systems Engineer VOICE: +1 864 331 8181
NuVox Communications, Inc. FAX: +1 864 331 7234
301 North Main Street, Ste 5000 EMAIL: dnedved@nuvox.net
Greenville, SC 29601 USA PAGER: pagenedved@nuvox.net
^ permalink raw reply [flat|nested] 5+ messages in thread
end of thread, other threads:[~2002-06-09 16:14 UTC | newest]
Thread overview: 5+ messages (download: mbox.gz follow: Atom feed
-- links below jump to the message on this page --
2002-06-08 17:37 RAID-1 md comes up degraded every time Michael Robinton
2002-06-09 16:14 ` David Nedved
-- strict thread matches above, loose matches on Subject: below --
2002-06-08 15:06 David Nedved
2002-06-08 16:41 ` Andre Breiler
2002-06-09 16:13 ` David Nedved
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).