Re: /dev/md0 don't start after controller change
On 12/11/06, michael [EMAIL PROTECTED] wrote: Perhaps partitions from sdd and sde need to be re-added as well? Surely I must add sdd, sde and sdf, but my problem is another: If I add those partitions (sdc included) after reboot /dev/md0 lost information about them, and it shows raid schema with two working disks and three set as removed. I don't know what to do. -- Openclose.it - Idee per il software libero http://www.openclose.it -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: /dev/md0 don't start after controller change
On Tue, 2006-12-12 at 09:33 +0100, Andrea Ganduglia wrote: Surely I must add sdd, sde and sdf, but my problem is another: If I add those partitions (sdc included) after reboot /dev/md0 lost information about them, and it shows raid schema with two working disks and three set as removed. I don't know what to do. Sometimes i have experienced oddities with raid sets at boot it helps to 1 configure them the way you want them. 2 let them sync fully. 3 recreate the initrd with dpkg-reconfigure kernel-image-(version) Ronny -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: /dev/md0 don't start after controller change
also sprach Andrea Ganduglia [EMAIL PROTECTED] [2006.12.07.1225 +0100]: Surely I must add sdd, sde and sdf, but my problem is another: If I add those partitions (sdc included) after reboot /dev/md0 lost information about them, and it shows raid schema with two working disks and three set as removed. I don't know what to do. Can you try to zero the /dev/sdc1 partition (dd if=/dev/zero of=/dev/sdc1) and readding it, then rebooting? -- Please do not send copies of list mail to me; I read the list! .''`. martin f. krafft [EMAIL PROTECTED] : :' : proud Debian developer, author, administrator, and user `. `'` http://people.debian.org/~madduck - http://debiansystem.info `- Debian - when you have better things to do than fixing systems NP: Iron Maiden / Piece of Mind signature.asc Description: Digital signature (GPG/PGP)
Re: /dev/md0 don't start after controller change
On 12/12/06, martin f krafft [EMAIL PROTECTED] wrote:
also sprach Andrea Ganduglia [EMAIL PROTECTED] [2006.12.07.1225 +0100]:
Surely I must add sdd, sde and sdf, but my problem is another: If
I add those partitions (sdc included) after reboot /dev/md0 lost
information about them, and it shows raid schema with two working
disks and three set as removed. I don't know what to do.
Can you try to zero the /dev/sdc1 partition (dd if=/dev/zero
of=/dev/sdc1) and readding it, then rebooting?
Are you sure? I think that the problem do not depend by sd{c,d,e,f}
but by sd{a,b}. Please: look mdadm -E output from previous messages.
--
Openclose.it - Idee per il software libero
http://www.openclose.it
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: /dev/md0 don't start after controller change
also sprach Andrea Ganduglia [EMAIL PROTECTED] [2006.12.12.1231 +0100]:
Are you sure? I think that the problem do not depend by
sd{c,d,e,f} but by sd{a,b}. Please: look mdadm -E output from
previous messages.
I am not sure what the problem is. Thus I am trying to work through
various possibly scenarios with you.
If you think the problem is /dev/sd{a,b} and it's a RAID1, why not
add /dev/sdc1, fail-remove /dev/sda1, hot-add it, then do the same
with /dev/sdb1 and see if that fixes the problem.
--
Please do not send copies of list mail to me; I read the list!
.''`. martin f. krafft [EMAIL PROTECTED]
: :' : proud Debian developer, author, administrator, and user
`. `'` http://people.debian.org/~madduck - http://debiansystem.info
`- Debian - when you have better things to do than fixing systems
... the ravenous bugblatter beast of traal (a mind-bogglingly stupid
animal, it assumes that if you can't see it, it can't see you --
daft as a bush, but very very ravenous);
-- douglas adams, the hitchhiker's guide to the galaxy
signature.asc
Description: Digital signature (GPG/PGP)
Re: /dev/md0 don't start after controller change
On Mon, 11 Dec 2006 08:56:39 +0100, Andrea Ganduglia wrote pro:~# mdadm --detail --scan ARRAY /dev/md1 level=raid5 num-devices=5 spares=1 UUID=04a39ca8:0f07922a:5eb2e3a1:851b13b9 devices=/dev/sda2,/dev/sdf2,/dev/sdd2,/dev/sdc2,/dev/sde2, /dev/sdb2 ARRAY /dev/md0 level=raid1 num-devices=5 UUID=fc7dc246:3f029459:8ede4b05:519a9a8f devices=/dev/sda1,/dev/sdb1,/dev/sdc1 Your md0 doesn't seem right. The scan shows a 5 device raid 5, and yet only 3 show up. Perhaps partitions from sdd and sde need to be re-added as well? -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: /dev/md0 don't start after controller change
On 12/7/06, michael [EMAIL PROTECTED] wrote: On Thu, 7 Dec 2006 12:25:40 +0100, Andrea Ganduglia wrote In some way /dev/sda1 and /dev/sdb1 lost information about --add option after any reboot. :-( After you add your partition, how does mdadm --detail --scan compare to /etc/mdadm/mdadm.conf ? There are important differences pro:~# mdadm --add /dev/md0 /dev/sdc1 pro:~# cat /etc/mdadm/mdadm.conf DEVICE partitions ARRAY /dev/md1 level=raid5 num-devices=5 spares=1 UUID=04a39ca8:0f07922a:5eb2e3a1:851b13b9 devices=/dev/sda2,/dev/sdb2,/dev/sdc2,/dev/sdd2,/dev/sde2,/dev/sdf2 ARRAY /dev/md0 level=raid1 num-devices=5 spares=1 UUID=fc7dc246:3f029459:8ede4b05:519a9a8f devices=/dev/sda1,/dev/sdb1,/dev/sdc1,/dev/sdd1,/dev/sde1,/dev/sdf1 pro:~# mdadm --detail --scan ARRAY /dev/md1 level=raid5 num-devices=5 spares=1 UUID=04a39ca8:0f07922a:5eb2e3a1:851b13b9 devices=/dev/sda2,/dev/sdf2,/dev/sdd2,/dev/sdc2,/dev/sde2,/dev/sdb2 ARRAY /dev/md0 level=raid1 num-devices=5 UUID=fc7dc246:3f029459:8ede4b05:519a9a8f devices=/dev/sda1,/dev/sdb1,/dev/sdc1 -- Openclose.it - Idee per il software libero http://www.openclose.it -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: /dev/md0 don't start after controller change
also sprach Andrea Ganduglia [EMAIL PROTECTED] [2006.12.05.1557 +0400]:
But if I do this command onto RAID1 it said that md0 is still in use
(sure! is root's partition!). If I add manually others disk (mdadm
--add /dev/md0 /dev/sdc1) it works, but on reboot only sda1 and sdb1
are parts of this raid, while sd{c,d,e,f}1 are mark as removed!
Please post the contents of /proc/mdstat after adding the
sd{c,d,e,f}1 components.
--
Please do not send copies of list mail to me; I read the list!
.''`. martin f. krafft [EMAIL PROTECTED]
: :' : proud Debian developer, author, administrator, and user
`. `'` http://people.debian.org/~madduck - http://debiansystem.info
`- Debian - when you have better things to do than fixing systems
one should never trust a woman who tells her real age.
if she tells that, she will tell anything.
-- oscar wilde
signature.asc
Description: Digital signature (GPG/PGP)
Re: /dev/md0 don't start after controller change
On 12/7/06, martin f krafft [EMAIL PROTECTED] wrote:
also sprach Andrea Ganduglia [EMAIL PROTECTED] [2006.12.05.1557 +0400]:
But if I do this command onto RAID1 it said that md0 is still in use
(sure! is root's partition!). If I add manually others disk (mdadm
--add /dev/md0 /dev/sdc1) it works, but on reboot only sda1 and sdb1
are parts of this raid, while sd{c,d,e,f}1 are mark as removed!
Please post the contents of /proc/mdstat after adding the
sd{c,d,e,f}1 components.
Hi martin, and thanks for your reply.
This is /proc/mdstat after mdadm --add /dev/md0 sd{c,d,e,f}1
Personalities : [raid0] [raid1] [raid5]
md1 : active raid5 sda2[0] sdb2[5] sde2[4] sdc2[3] sdd2[2] sdf2[1]
839845632 blocks level 5, 64k chunk, algorithm 2 [5/5] [U]
md0 : active raid1 sda1[0] sdf1[5] sde1[4] sdd1[3] sdc1[2] sdb1[1]
29294400 blocks [5/5] [U]
unused devices: none
This is after reboot!
Personalities : [raid0] [raid1] [raid5]
md1 : active raid5 sda2[0] sdb2[5] sde2[4] sdc2[3] sdd2[2] sdf2[1]
839845632 blocks level 5, 64k chunk, algorithm 2 [5/5] [U]
md0 : active raid1 sda1[0] sdb1[1]
29294400 blocks [5/2] [UU___]
unused devices: none
--
Openclose.it - Idee per il software libero
http://www.openclose.it
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: /dev/md0 don't start after controller change
also sprach Andrea Ganduglia [EMAIL PROTECTED] [2006.12.07.1249 +0400]: md0 : active raid1 sda1[0] sdb1[1] 29294400 blocks [5/2] [UU___] I am led to believe that there must be some outdated information in the superblocks. Can you please post the output of mdadm -E /dev/sd[acde]1 , or even better: compare the output of [cde] to the output of [a] and tell me any divergencies you see. -- Please do not send copies of list mail to me; I read the list! .''`. martin f. krafft [EMAIL PROTECTED] : :' : proud Debian developer, author, administrator, and user `. `'` http://people.debian.org/~madduck - http://debiansystem.info `- Debian - when you have better things to do than fixing systems save the plankton - eat a whale. signature.asc Description: Digital signature (GPG/PGP)
Re: /dev/md0 don't start after controller change
On 12/7/06, martin f krafft [EMAIL PROTECTED] wrote:
also sprach Andrea Ganduglia [EMAIL PROTECTED] [2006.12.07.1249 +0400]:
md0 : active raid1 sda1[0] sdb1[1]
29294400 blocks [5/2] [UU___]
I am led to believe that there must be some outdated information in
the superblocks. Can you please post the output of
mdadm -E /dev/sd[acde]1
, or even better: compare the output of [cde] to the output of [a]
and tell me any divergencies you see.
Martin: thanks for all you do! I agree that the problem is in superblocks
information. I lauched your command on all disk and I report below
divergencies. As you see /dev/sd{c,d,e,f}1 look all active devices on /dev/md0,
instead /dev/sd{a,b}1 look only two devices at same raid.
Summary:
/dev/sd{a,b}1 looks 2 working devices and 3 failed devices
/dev/sd{c,d,e}1 looks 5 working devices and 0 failed devices
/dev/sdf1 looks 5 working devices, 1 spare device (/dev/sdd) and 0
failed devices
How can I fix superblocks informations? Consider that /dev/md0 is mounted on
root partitions (/).
~# mdadm -E /dev/sda1 (same result for /dev/sdb1)
/dev/sda1:
Magic : a92b4efc
Version : 00.90.00
UUID : fc7dc246:3f029459:8ede4b05:519a9a8f
Creation Time : Mon Sep 18 15:42:25 2006
Raid Level : raid1
Raid Devices : 5
Total Devices : 2
Preferred Minor : 0
Update Time : Thu Dec 7 11:15:25 2006
State : clean
Active Devices : 2
Working Devices : 2
Failed Devices : 3
Spare Devices : 0
Checksum : 51812ec0 - correct
Events : 0.756669
Number Major Minor RaidDevice State
this 0 810 active sync /dev/sda1
0 0 810 active sync /dev/sda1
1 1 8 171 active sync /dev/sdb1
2 2 002 faulty removed
3 3 003 faulty removed
4 4 004 faulty removed
:~# mdadm -E /dev/sdc1 (same result for sdd1 and sde1)
/dev/sdc1:
Magic : a92b4efc
Version : 00.90.00
UUID : fc7dc246:3f029459:8ede4b05:519a9a8f
Creation Time : Mon Sep 18 15:42:25 2006
Raid Level : raid1
Raid Devices : 5
Total Devices : 5
Preferred Minor : 0
Update Time : Tue Dec 5 12:38:11 2006
State : clean
Active Devices : 5
Working Devices : 5
Failed Devices : 0
Spare Devices : 0
Checksum : 517e38ba - correct
Events : 0.743457
Number Major Minor RaidDevice State
this 2 8 332 active sync /dev/sdc1
0 0 810 active sync /dev/sda1
1 1 8 171 active sync /dev/sdb1
2 2 8 332 active sync /dev/sdc1
3 3 8 653 active sync /dev/sde1
4 4 8 494 active sync /dev/sdd1
~# mdadm -E /dev/sdf1 (NOTE: It looks /dev/sdd as sparedisk, It's
congruent with my installation).
/dev/sdf1:
Magic : a92b4efc
Version : 00.90.00
UUID : fc7dc246:3f029459:8ede4b05:519a9a8f
Creation Time : Mon Sep 18 15:42:25 2006
Raid Level : raid1
Raid Devices : 5
Total Devices : 6
Preferred Minor : 0
Update Time : Mon Dec 4 15:37:57 2006
State : clean
Active Devices : 5
Working Devices : 6
Failed Devices : 0
Spare Devices : 1
Checksum : 517cd246 - correct
Events : 0.735306
Number Major Minor RaidDevice State
this 3 8 813 active sync /dev/sdf1
0 0 810 active sync /dev/sda1
1 1 8 171 active sync /dev/sdb1
2 2 8 332 active sync /dev/sdc1
3 3 8 813 active sync /dev/sdf1
4 4 8 654 active sync /dev/sde1
5 5 8 495 spare /dev/sdd1
--
Openclose.it - Idee per il software libero
http://www.openclose.it
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: /dev/md0 don't start after controller change
also sprach Andrea Ganduglia [EMAIL PROTECTED] [2006.12.07.1432 +0400]: How can I fix superblocks informations? Consider that /dev/md0 is mounted on root partitions (/). mdadm --add /dev/md0 /dev/sd[cde]1 should work. Your components got bumped from the array after they were marked failed and the superblock went out of date. Hence, just readd them. -- Please do not send copies of list mail to me; I read the list! .''`. martin f. krafft [EMAIL PROTECTED] : :' : proud Debian developer, author, administrator, and user `. `'` http://people.debian.org/~madduck - http://debiansystem.info `- Debian - when you have better things to do than fixing systems imagination is a quality given a man to compensate him for what he is not, and a sense of humour was provided to console him for what he is. -- oscar wilde signature.asc Description: Digital signature (GPG/PGP)
Re: /dev/md0 don't start after controller change
On 12/7/06, martin f krafft [EMAIL PROTECTED] wrote: also sprach Andrea Ganduglia [EMAIL PROTECTED] [2006.12.07.1432 +0400]: How can I fix superblocks informations? Consider that /dev/md0 is mounted on root partitions (/). mdadm --add /dev/md0 /dev/sd[cde]1 should work. Your components got bumped from the array after they were marked failed and the superblock went out of date. Hence, just readd them. Mumble... It's the first thing that I do, but after reboot informations are lost. Now I done: mdadm --add /dev/md0 /dev/sdc1 and operations was completed without errors. If I type mdadm -E /dev/sdc1 0 0 810 active sync /dev/sda1 1 1 8 171 active sync /dev/sdb1 2 2 8 332 active sync /dev/sdc1 3 3 003 faulty removed 4 4 004 faulty removed before and AFTER reboot while same command on /dev/sda1 said same result before reboot but this AFTER reboot 0 0 810 active sync /dev/sda1 1 1 8 171 active sync /dev/sdb1 2 2 002 faulty removed 3 3 003 faulty removed 4 4 004 faulty removed In some way /dev/sda1 and /dev/sdb1 lost information about --add option after any reboot. :-( -- Openclose.it - Idee per il software libero http://www.openclose.it -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: /dev/md0 don't start after controller change
On Thu, 7 Dec 2006 12:25:40 +0100, Andrea Ganduglia wrote In some way /dev/sda1 and /dev/sdb1 lost information about --add option after any reboot. :-( After you add your partition, how does mdadm --detail --scan compare to /etc/mdadm/mdadm.conf ? Mike -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
/dev/md0 don't start after controller change
Hi. Some days ago I have change my PCI SATA controller. My machine
have 6 disk, 2 on motherboad controllers and 4 onto PCI SATA
controller. I have 2 RAID software, one for system (RAID1) and one for
data (RAID5).
Before remove old PCI SATA controller I have mark as faulty all disk
on PCI SATA controller, and leave from /etc/fstab RAID5 references
(preserving data).
Now, I have change PCI SATA controller and it works perfetly, but
/dev/md0 (RAID1) do not start correctly.
For resync and active RAID5 I done:
~# mdadm --assemble --scan /dev/md1
But if I do this command onto RAID1 it said that md0 is still in use
(sure! is root's partition!). If I add manually others disk (mdadm
--add /dev/md0 /dev/sdc1) it works, but on reboot only sda1 and sdb1
are parts of this raid, while sd{c,d,e,f}1 are mark as removed!
Can you help me?
--
Openclose.it - Idee per il software libero
http://www.openclose.it
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
