help!

I had an mdadm device running fine, and had created my own scripts for
shutting it down and such. I upgraded my distro, and all of a sudden it
decided to start initializing md devices on it's own, which include one
that I want removed. The one that should be removed is throwing off the
numbering, otherwise I wouldn't care so much. There's nothing in
mdadm.conf, so I can only assume it's something with the kernel driver?
Any help would be appreciated.

Shane Bishop
-
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

Re: help!

Shane Bishop (sbishop@trinitybiblecollege.edu) wrote on 14 November 2005 11:20:
>I had an mdadm device running fine, and had created my own scripts for
>shutting it down and such. I upgraded my distro, and all of a sudden it
>decided to start initializing md devices on it's own, which include one
>that I want removed.

Probably the filesystem type in the partition table is set to raid
autodetect (fd). Try changing it to something else, for example 83.
Note that these are hexadecimal numbers.
-
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

Re: help!

Carlos Carvalho wrote:

>Shane Bishop (sbishop@trinitybiblecollege.edu) wrote on 14 November 2005 11:20:
> >I had an mdadm device running fine, and had created my own scripts for
> >shutting it down and such. I upgraded my distro, and all of a sudden it
> >decided to start initializing md devices on it's own, which include one
> >that I want removed.
>
>Probably the filesystem type in the partition table is set to raid
>autodetect (fd). Try changing it to something else, for example 83.
>Note that these are hexadecimal numbers.
>-
>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
>
>
They were indeed set to raid autodetect. I was unaware of what that
actually did, I think I must have followed that step in a how-to when I
originally set it up. The odd thing is that these are the partition
pairs that were being mounted:
sda sdb
sda1 sdb1
sdc1 sdd1
The last 2 are the ones I actually wanted, but the first one was
something I had done when I was first playing around with it, if memory
serves me correct. Is that possible, or does it point to some other issue?

Shane
-
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

Re: help!

>> >I had an mdadm device running fine, and had created my own scripts for
>> >shutting it down and such. I upgraded my distro, and all of a sudden it
>> >decided to start initializing md devices on it's own, which include one
>> >that I want removed.
>>
>They were indeed set to raid autodetect. I was unaware of what that
>actually did, I think I must have followed that step in a how-to when I
>originally set it up. The odd thing is that these are the partition
>pairs that were being mounted:
>sda sdb
>sda1 sdb1
>sdc1 sdd1
>The last 2 are the ones I actually wanted, but the first one was
>something I had done when I was first playing around with it, if memory
>serves me correct. Is that possible, or does it point to some other issue?

If changing the partition type does not work then you might try
zeroing the superblock with 'mdadm --zero-superblock /dev/sda'
etc.

AFAIK the superblock and the mdadm.conf file are mdadms only
information sources. Remove them both and it should be impossible
for the unwanted raid devices to start.

A funny thing here is that I believe the superblock for sda and
sda1 are in exactly the same place, at the end of the disk, so I
can't see how it would find two different raid devices. What
version superblocks are you using? I think v1 superblocks are at
the beginning of the device and I'm not sure if the first disk
block for sda is the same as the first block for sda1...

HTH (and it could be all 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

Re: Help!

what kernel version and mdadm version?




Jes=FAs Berm=FAdez said: (by the date of Fri, 22 Oct 2010 16:51:20 =
+0200 (CEST))

> Hello all,
>=20
> if you could help us, for we are completely desperated...
>=20
> We have a raid5 with 3 disks that got out of sync due to a power fail=
ure. After tried to assemble (with mdadm --assemble --force /dev/md0) i=
t says:
>=20
> md: md0 stopped mdbind sdb2 bind sda2 bind sdc2
>=20
> md: md0: array is not clean starting background reconstruction
>=20
> raid 5 device sdc2 operational as raid disk 0
> device sda2 operational as raid disk 2
> device sdb2 operational as raid disk 1
>=20
> allocated 32kb for md0
>=20
> raid level 5 set md0 active with 3 out 3 devices algorithm 0
>=20
> raid 5 conf printout
>=20
> rd:3 wd:3
>=20
> disk 0,0:1 /dev/sdc2
> disk 1,0:1 /dev/sdb2
> disk 2,0:1 /dev/sda2
>=20
> md0: bitmap file is out of date 892893
> forcing full recovery
>=20
> md0: bitmap file is out of date doing full recovery
>=20
> md0: bitmap initialisation failed: -5
>=20
> md0: failed to create bitmap (-5)
>=20
> md: pers->run() failed
>=20
> mdadm: failed to run _array /dev/md0: input / output error
>=20
> Tried to stop the array and reassemble it with:
>=20
> mdadm --assemble --force --scan
> mdadm --assemble --force --scan /dev/md0 /dev/sda2 /dev/sdb2 /dev/sdc=
2
> mdadm --assemble --force --run /dev/md0 /dev/sda2 /dev/sdb2
> mdadm --assemble --force --run /dev/md0 /dev/sda2 /dev/sdc2
> mdadm --assemble --force --run /dev/md0 /dev/sdb2 /dev/sdc2
>=20
> Tried to solve the bitmap problem with:
>=20
> mdadm --grow /dev/md0 --bitmap=3Dnone
> mdadm --grow /dev/md0 --bitmap=3Dinternal
> mdadm --grow /dev/md0 --bitmap=3Dnone --force
> mdadm --grow /dev/md0 --bitmap=3Dinternal --force
>=20
> Tried to fake the 'clean' status of the array with:
>=20
> echo "clean" > /sys/block/md0/md/array_state
>=20
> Tried to boot the array from grub with:
>=20
> md-mod.start_dirty_degraded=3D1
>=20
> None of these commands have worked. Here are the details of the array=
and everyone of the disks:
>=20
> ------------------------------------------------------------ ---------=
------------------------------------------------------------ --
> mdadm -D /dev/md0
>=20
> dev/md0
> version: 01.00.03
> creation time: august 28 18:58:39 2009
> raid level: raid5
> used dev size 83891328 (80:01 hid 85:90 gdb)
> raid devices: 3
> total drives: 3
> preferred minor: 0
> persistent: superblock is persistent
> update time: tue oct 19 15:09 2010
> Status: active, not started
> Active devices: 3
> Working devices: 3
> Failed devices: 0
> Spare device: 0
> layout: left assimetric
> chunk size: 128k
> name: 0
>=20
> UUID: ae9bd4fe:994ce882:4fa035e6:8094fc1a
> events: 893
>=20
> Number Major Minor RaidDevice State
> 0 8 34 0 active sync /dev/sdc2
> 1 8 18 1 active sync /dev/sdb2
> 3 8 2 2 active sync /dev/sda2
>=20
> ------------------------------------------------------------ ---------=
------------------------------------------------------------ --
> mdadm --examine /dev/sd[abc]2
>=20
>=20
> /dev/sda2:
>=20
> Magic:a92b4efc
> Version:1,0
> Featura Map:0x1
> Array UUID:ae9bd4fe:994ce882:4fa035e6:8094fc1a
> Name:0
> Creation Time:Fri Aug 28 18:58:39 2009
> Raid Level:Raid5
> Raid Devices:3:Avail Dev Size:167782712 (80,01GIB 85,90 GB)
> Array Size:335565312 (160,01 GIB 171,81 GB)
> Used Dev Size:167782656 (80,01 GIB 85,90GB)
> Super Offset:167782840 Sectors
> State:Active
> Device UUID:bbc156a7:6f3af82d:94714923:e212967a
> Internal Bitmap:-81 sectors from superblock
> Update Time:re Oct 19 15:49:08 2010
> Checksum:54a35562 - correct
> Events:893
> Layout:left-asymmetric
> Chunk Size:128K
> Array Slot:3 (0. 1, failed, 2)
> Array State:uuU 1 failed
>=20
>=20
>=20
> /dev/sdb2:
> =09
>=20
> Magic:a92b4efc
> Version:1,0
> Feature Map:0x1
> Array UUID:ae9bd4fe:994ce882:4fa035e6:8094fc1a
> Name:0
> Creation Time:Fri Aug 28 18:58:39 2009
> Raid Level:raid5
> Raid Devices:3
> Avail Dev Size:167782712 (80,01 GIB 85,90 GB)
> Array Size:335565312 (160,01 GIB 171,81 GB)
> Used Dev Size:167782656 (80,01 GIB 85,90 GB)
> Super Offset:167782840 sectors
> State:Active
> Device UUID:d067101e:19056fdd:6b6e58fc:92128788
> Internal Bimap:-81 sectors from superblock
> Update Time:Tue Oct 19 15:49:08 2010
> Checksum:61d3c2bf
> Events:893
> Layout:left-asymmetric
> Chunk Size:128k
> Array Slot:1 (0, 1, failed, 2)
> Array State:uUu 1 failed
>=20
> /dev/sdc2:
> =09
> Magic:a92b4efc
> Version:1,0
> Featura Map:0x1
> Array UUID:ae9bd4fe:994ce882:4fa035e6:8094fc1a
> Name:0
> Creation Time:Fri Aug 28 18:58:39 2009
> Raid Level:raid5
> Raid Devices:3
> Avail Dev Size:167782712 (80,01 GIB 85,90 GB)
> Array Size:335565312 (160,01 GIB 171,81 GB)
> Used Dev Size:167782656 (80,01 GIB 85,90 GB)
> Super Offset:167782840 sectors
> State:active
> Device UUID:0a1c2c74:04b9187f:6ab6b5cb:894d8b38
> Internal Bimap:-81 sectos from superblock
> Update Time:Tue Oct 19 15:49:08 2010
> Checksum:d8faadc0 - correct
> Events:893
> Layout:left-asymmetric
> Chunk Size:128K
> Array Slot:0 (0, 1, failed, 2)
> Array State:Uuu 1 failed
>=20
> ------------------------------------------------------------ ---------=
------------------------------------------------------------ --
>=20
> mdadm --examine-bitmap /dev/sd[abc]2
> =09
> Filename /dev/sda2
>=20
> Magic 6d746962
> Version 4
> UUID ae9bd4fe:994ce882:4fa035e6:8094fc1a
> Events 892
> Events Cleared 892
> State Out of date
> Chunksize 256KB
> Daemon 5s flush period
> Write Mode Normal
> Sync Size 83891328 (80,01 GIB 85,90 GB)
> Bitmap 327701 BITS (CHUNKS), 325633 DIRTY (99,4%)
>=20
> Filename /dev/sdb2
>=20
> Magic 6d746962
> Version 4
> UUID ae9bd4fe:994ce882:4fa035e6:8094fc1a
> Events 892
> Events Cleared 892
> State Out of date
> Chunksize 256KB
> Daemon 5s flush period
> Write Mode Normal
> Sync Size 83891328 (80,01 GIB 85,90 GB)
> Bitmap 327701 BITS (CHUNKS), 325633 DIRTY (99,4%)
>=20
> Filename /dev/sdc2
> Magic 6d746962
> Version 4
> UUID ae9bd4fe:994ce882:4fa035e6:8094fc1a
> events 892
> Events Cleared 892
>=20
> State Out of date
> Chunksize 256 KB
> Daemon 5s flush period
> Write Mode Normal
> Sync Size 83891328 (80,01 GIB 85,90 GB)
> Bitmap 327701 BITS (CHUNKS), 325633 DIRTY (99,4%)
>=20
> ------------------------------------------------------------ ---------=
------------------------------------------------------------ --
>=20
> cat /sys/bplock/md0/md/array_state
>=20
> inactive
>=20
>=20
> cat /sys/block/md0/md/degraded
>=20
> cat /sys/block/md0/md/degraded: No such file or directory
>=20
>=20
> cat /sys/block/md0/md/dev-sda2/errors
>=20
> 0
>=20
> cat /sys/block/md0/md/dev-sda2/state
>=20
> in_sync
>=20
>=20
> cat /sys/block/md0/md/dev-sdb2/errors
>=20
> 24
>=20
>=20
> cat /sys/block/md0/md/dev-sdb2/state
>=20
> in_sync
>=20
>=20
> cat /sys/block/md0/md/dev-sdc2/errors
>=20
> 0
>=20
>=20
> cat /sys/block/md0/md/dev-sdc2/state
>=20
> in_sync
> ------------------------------------------------------------ ---------=
------------------------------------------------------------ --
>=20
> Thanks in advance.
>=20
> --=20
> Jesus Bermudez Riquelme=20
>=20
>=20
> Iten, S.L.=20
> --
> 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
>=20


--=20
Janek Kozicki http://janek.kozicki.pl/ |
--
To unsubscribe from this list: send the line "unsubscribe linux-raid" i=
n
the body of a message to majordomo@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html

Re: Help!

On Fri, 22 Oct 2010 16:51:20 +0200 (CEST)
Jes=FAs Berm=FAdez wrote:

> Hello all,
>=20
> if you could help us, for we are completely desperated...
>=20
> We have a raid5 with 3 disks that got out of sync due to a power fail=
ure. After tried to assemble (with mdadm --assemble --force /dev/md0) i=
t says:
>=20
> md: md0 stopped mdbind sdb2 bind sda2 bind sdc2
>=20
> md: md0: array is not clean starting background reconstruction
>=20
> raid 5 device sdc2 operational as raid disk 0
> device sda2 operational as raid disk 2
> device sdb2 operational as raid disk 1
>=20
> allocated 32kb for md0
>=20
> raid level 5 set md0 active with 3 out 3 devices algorithm 0
>=20
> raid 5 conf printout
>=20
> rd:3 wd:3
>=20
> disk 0,0:1 /dev/sdc2
> disk 1,0:1 /dev/sdb2
> disk 2,0:1 /dev/sda2
>=20
> md0: bitmap file is out of date 892893
> forcing full recovery
>=20
> md0: bitmap file is out of date doing full recovery
>=20
> md0: bitmap initialisation failed: -5

This (the "-5") strongly suggests that we got an error when trying to w=
rite to
the bitmap. But such errors normally appear in the kernel logs, yet yo=
u
don't report any.

Is this still a problem for you or have you found a solution?

You probably need to assemble the array without the device which is suf=
fering
the write errors.

NeilBrown


>=20
> md0: failed to create bitmap (-5)
>=20
> md: pers->run() failed
>=20
> mdadm: failed to run _array /dev/md0: input / output error
>=20
> Tried to stop the array and reassemble it with:
>=20
> mdadm --assemble --force --scan
> mdadm --assemble --force --scan /dev/md0 /dev/sda2 /dev/sdb2 /dev/sdc=
2
> mdadm --assemble --force --run /dev/md0 /dev/sda2 /dev/sdb2
> mdadm --assemble --force --run /dev/md0 /dev/sda2 /dev/sdc2
> mdadm --assemble --force --run /dev/md0 /dev/sdb2 /dev/sdc2
>=20
> Tried to solve the bitmap problem with:
>=20
> mdadm --grow /dev/md0 --bitmap=3Dnone
> mdadm --grow /dev/md0 --bitmap=3Dinternal
> mdadm --grow /dev/md0 --bitmap=3Dnone --force
> mdadm --grow /dev/md0 --bitmap=3Dinternal --force
>=20
> Tried to fake the 'clean' status of the array with:
>=20
> echo "clean" > /sys/block/md0/md/array_state
>=20
> Tried to boot the array from grub with:
>=20
> md-mod.start_dirty_degraded=3D1
>=20
> None of these commands have worked. Here are the details of the array=
and everyone of the disks:
>=20
> ------------------------------------------------------------ ---------=
------------------------------------------------------------ --
> mdadm -D /dev/md0
>=20
> dev/md0
> version: 01.00.03
> creation time: august 28 18:58:39 2009
> raid level: raid5
> used dev size 83891328 (80:01 hid 85:90 gdb)
> raid devices: 3
> total drives: 3
> preferred minor: 0
> persistent: superblock is persistent
> update time: tue oct 19 15:09 2010
> Status: active, not started
> Active devices: 3
> Working devices: 3
> Failed devices: 0
> Spare device: 0
> layout: left assimetric
> chunk size: 128k
> name: 0
>=20
> UUID: ae9bd4fe:994ce882:4fa035e6:8094fc1a
> events: 893
>=20
> Number Major Minor RaidDevice State
> 0 8 34 0 active sync /dev/sdc2
> 1 8 18 1 active sync /dev/sdb2
> 3 8 2 2 active sync /dev/sda2
>=20
> ------------------------------------------------------------ ---------=
------------------------------------------------------------ --
> mdadm --examine /dev/sd[abc]2
>=20
>=20
> /dev/sda2:
>=20
> Magic:a92b4efc
> Version:1,0
> Featura Map:0x1
> Array UUID:ae9bd4fe:994ce882:4fa035e6:8094fc1a
> Name:0
> Creation Time:Fri Aug 28 18:58:39 2009
> Raid Level:Raid5
> Raid Devices:3:Avail Dev Size:167782712 (80,01GIB 85,90 GB)
> Array Size:335565312 (160,01 GIB 171,81 GB)
> Used Dev Size:167782656 (80,01 GIB 85,90GB)
> Super Offset:167782840 Sectors
> State:Active
> Device UUID:bbc156a7:6f3af82d:94714923:e212967a
> Internal Bitmap:-81 sectors from superblock
> Update Time:re Oct 19 15:49:08 2010
> Checksum:54a35562 - correct
> Events:893
> Layout:left-asymmetric
> Chunk Size:128K
> Array Slot:3 (0. 1, failed, 2)
> Array State:uuU 1 failed
>=20
>=20
>=20
> /dev/sdb2:
> =09
>=20
> Magic:a92b4efc
> Version:1,0
> Feature Map:0x1
> Array UUID:ae9bd4fe:994ce882:4fa035e6:8094fc1a
> Name:0
> Creation Time:Fri Aug 28 18:58:39 2009
> Raid Level:raid5
> Raid Devices:3
> Avail Dev Size:167782712 (80,01 GIB 85,90 GB)
> Array Size:335565312 (160,01 GIB 171,81 GB)
> Used Dev Size:167782656 (80,01 GIB 85,90 GB)
> Super Offset:167782840 sectors
> State:Active
> Device UUID:d067101e:19056fdd:6b6e58fc:92128788
> Internal Bimap:-81 sectors from superblock
> Update Time:Tue Oct 19 15:49:08 2010
> Checksum:61d3c2bf
> Events:893
> Layout:left-asymmetric
> Chunk Size:128k
> Array Slot:1 (0, 1, failed, 2)
> Array State:uUu 1 failed
>=20
> /dev/sdc2:
> =09
> Magic:a92b4efc
> Version:1,0
> Featura Map:0x1
> Array UUID:ae9bd4fe:994ce882:4fa035e6:8094fc1a
> Name:0
> Creation Time:Fri Aug 28 18:58:39 2009
> Raid Level:raid5
> Raid Devices:3
> Avail Dev Size:167782712 (80,01 GIB 85,90 GB)
> Array Size:335565312 (160,01 GIB 171,81 GB)
> Used Dev Size:167782656 (80,01 GIB 85,90 GB)
> Super Offset:167782840 sectors
> State:active
> Device UUID:0a1c2c74:04b9187f:6ab6b5cb:894d8b38
> Internal Bimap:-81 sectos from superblock
> Update Time:Tue Oct 19 15:49:08 2010
> Checksum:d8faadc0 - correct
> Events:893
> Layout:left-asymmetric
> Chunk Size:128K
> Array Slot:0 (0, 1, failed, 2)
> Array State:Uuu 1 failed
>=20
> ------------------------------------------------------------ ---------=
------------------------------------------------------------ --
>=20
> mdadm --examine-bitmap /dev/sd[abc]2
> =09
> Filename /dev/sda2
>=20
> Magic 6d746962
> Version 4
> UUID ae9bd4fe:994ce882:4fa035e6:8094fc1a
> Events 892
> Events Cleared 892
> State Out of date
> Chunksize 256KB
> Daemon 5s flush period
> Write Mode Normal
> Sync Size 83891328 (80,01 GIB 85,90 GB)
> Bitmap 327701 BITS (CHUNKS), 325633 DIRTY (99,4%)
>=20
> Filename /dev/sdb2
>=20
> Magic 6d746962
> Version 4
> UUID ae9bd4fe:994ce882:4fa035e6:8094fc1a
> Events 892
> Events Cleared 892
> State Out of date
> Chunksize 256KB
> Daemon 5s flush period
> Write Mode Normal
> Sync Size 83891328 (80,01 GIB 85,90 GB)
> Bitmap 327701 BITS (CHUNKS), 325633 DIRTY (99,4%)
>=20
> Filename /dev/sdc2
> Magic 6d746962
> Version 4
> UUID ae9bd4fe:994ce882:4fa035e6:8094fc1a
> events 892
> Events Cleared 892
>=20
> State Out of date
> Chunksize 256 KB
> Daemon 5s flush period
> Write Mode Normal
> Sync Size 83891328 (80,01 GIB 85,90 GB)
> Bitmap 327701 BITS (CHUNKS), 325633 DIRTY (99,4%)
>=20
> ------------------------------------------------------------ ---------=
------------------------------------------------------------ --
>=20
> cat /sys/bplock/md0/md/array_state
>=20
> inactive
>=20
>=20
> cat /sys/block/md0/md/degraded
>=20
> cat /sys/block/md0/md/degraded: No such file or directory
>=20
>=20
> cat /sys/block/md0/md/dev-sda2/errors
>=20
> 0
>=20
> cat /sys/block/md0/md/dev-sda2/state
>=20
> in_sync
>=20
>=20
> cat /sys/block/md0/md/dev-sdb2/errors
>=20
> 24
>=20
>=20
> cat /sys/block/md0/md/dev-sdb2/state
>=20
> in_sync
>=20
>=20
> cat /sys/block/md0/md/dev-sdc2/errors
>=20
> 0
>=20
>=20
> cat /sys/block/md0/md/dev-sdc2/state
>=20
> in_sync
> ------------------------------------------------------------ ---------=
------------------------------------------------------------ --
>=20
> Thanks in advance.
>=20

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