| View previous topic :: View next topic |
| Author |
Message |
ScRaTcHi
n00b
Joined: 21 Dec 2004
Posts: 62
|
 Posted: Sat Jan 22, 2005 8:17 pm Post subject: Broken software RAID5 problem [SOLVED!] |
 |
|
I've created a software RAID5 array with 3 discs (in this order):
/dev/hda4 (type "FD" 60/80 GB)
/dev/hdc1 (type "FD" 60/60 GB)
/dev/hdd1 (type "FD" 60/60 GB)
using mdadm --create ... . Formated with Reiser4.
All worked fine but after few weeks the array went off and after
reboot did not start again. When I run mdadm -E on those discs
i get this:
| Code: |
/dev/hda4:
Magic : a92b4efc
Version : 00.90.00
UUID : 45ce5e36:0e04965a:d372c73b:194705b2
Creation Time : Mon Dec 27 13:55:39 2004
Raid Level : raid5
Device Size : 58593408 (55.88 GiB 59.100 GB)
Raid Devices : 3
Total Devices : 3
Preferred Minor : 0
Update Time : Fri Jan 21 18:22:07 2005
State : clean
Active Devices : 1
Working Devices : 1
Failed Devices : 4
Spare Devices : 0
Checksum : 70f8b963 - correct
Events : 0.11104
Layout : left-symmetric
Chunk Size : 64K
Number Major Minor RaidDevice State
this 0 3 4 0 active sync /dev/hda4
0 0 3 4 0 active sync /dev/hda4
1 1 0 0 1 faulty removed
2 2 0 0 2 faulty removed
|
| Code: |
/dev/hdc1:
Magic : a92b4efc
Version : 00.90.00
UUID : 45ce5e36:0e04965a:d372c73b:194705b2
Creation Time : Mon Dec 27 13:55:39 2004
Raid Level : raid5
Device Size : 58593408 (55.88 GiB 59.100 GB)
Raid Devices : 3
Total Devices : 3
Preferred Minor : 0
Update Time : Fri Jan 21 17:17:11 2005
State : dirty
Active Devices : 3
Working Devices : 3
Failed Devices : 0
Spare Devices : 0
Checksum : 70f87ebe - correct
Events : 0.11096
Layout : left-symmetric
Chunk Size : 64K
Number Major Minor RaidDevice State
this 1 22 1 1 active sync /dev/hdc1
0 0 3 4 0 active sync /dev/hda4
1 1 22 1 1 active sync /dev/hdc1
2 2 22 65 2 active sync /dev/hdd1
|
| Code: |
/dev/hdd1:
Magic : a92b4efc
Version : 00.90.00
UUID : 45ce5e36:0e04965a:d372c73b:194705b2
Creation Time : Mon Dec 27 13:55:39 2004
Raid Level : raid5
Device Size : 58593408 (55.88 GiB 59.100 GB)
Raid Devices : 3
Total Devices : 3
Preferred Minor : 0
Update Time : Fri Jan 21 17:17:11 2005
State : dirty
Active Devices : 3
Working Devices : 3
Failed Devices : 0
Spare Devices : 0
Checksum : 70f87f00 - correct
Events : 0.11096
Layout : left-symmetric
Chunk Size : 64K
Number Major Minor RaidDevice State
this 2 22 65 2 active sync /dev/hdd1
0 0 3 4 0 active sync /dev/hda4
1 1 22 1 1 active sync /dev/hdc1
2 2 22 65 2 active sync /dev/hdd1
|
If I try to run
mdadm --assemble --uuid=45ce5e36:0e04965a:d372c73b:194705b2 --force /dev/hda4 /dev/hdc1 /dev/hdd1
i get this:
| Code: |
mdadm: /dev/hda4 does not appear to be an md device |
If I try to run
mdadm --assemble /dev/md0 /dev/hda4 /dev/hdc1 /dev/hdd1
i get Segmentation fault error.
mdadm says that /dev/md0 does not appear to be active
but /dev/md0 does exist.
I tried to recompile mdadm, kernel then whole world and even
my system but nothing helped.
Can You help me get my RAID working again?
Thanx in advance 4 your advices.
ScRaTcHi.
Last edited by ScRaTcHi on Tue Jan 25, 2005 7:09 pm; edited 1 time in total |
|
| Back to top |
|
 |
Gherald
Veteran
Joined: 23 Aug 2004
Posts: 1399
Location: CLUAConsole
|
| Posted: Sat Jan 22, 2005 8:23 pm Post subject: |
|
|
| Hmm. What does cat /proc/mdstat show? |
|
| Back to top |
|
|
ScRaTcHi
n00b
Joined: 21 Dec 2004
Posts: 62
|
| Posted: Sun Jan 23, 2005 4:48 pm Post subject: cat /proc/mdstat |
|
|
it says:
| Code: |
Personalities : [raid5]
Event: 24
unused devices: <none>
|
I don't know what does it mean, but if it would be possible I'd like to
assemble this array instead of creating it again.
Thank You. |
|
| Back to top |
|
|
Gherald
Veteran
Joined: 23 Aug 2004
Posts: 1399
Location: CLUAConsole
|
| Posted: Sun Jan 23, 2005 7:10 pm Post subject: |
|
|
| Code: | mdadm --assemble /dev/md0 /dev/hda4 /dev/hdc1 /dev/hdd1
i get Segmentation fault error. |
That is the part that worries me the most... though the fact that 2 are marked dirty and 1 is clean is also strange.
Well I would try the following:
1) Hopefuly your system isn't overclocked, but if it is, revert to stock.
2) Asumming your other partitions aren't Reiser4, compile a new kernel using standard gentoo-sources or kernel.org. Use the same config as before, but in make menuconfig go to Kernel Hacking and enable Debug Info and Frame Pointers.
You won't be able to mount the Reiser4 of course, but this is just a test to rule out your unsupported kernel as being the source of the mdadm segfault.
3) While the CCs are floating by, pray.
4) Execute: | Code: | | # CFLAGS="-march=i386 -pipe" emerge mdadm |
5) If none of that works, try an earlier kernel and earlier version of mdadm
6) Try using the package raidtools instead of mdadm |
|
| Back to top |
|
|
Gherald
Veteran
Joined: 23 Aug 2004
Posts: 1399
Location: CLUAConsole
|
| Posted: Mon Jan 24, 2005 3:17 am Post subject: |
|
|
| see also this thread. |
|
| Back to top |
|
|
ScRaTcHi
n00b
Joined: 21 Dec 2004
Posts: 62
|
| Posted: Mon Jan 24, 2005 7:36 am Post subject: |
|
|
YEs, You're right, my kernel is a little bit experimental (2.6.11-rc1-mm1).
I can try to run mdadm from lxnay's Reiser4 LiveCD but I don't know if that
will solve the problem on my system.
Some info about my system:
ABIT SA7 Mainboard with FailSafe defaults loaded in BIOS
no overclocking (PIII Cel'r'n 1100MHz)
512 MB DIMM 133MHz CL2.5 @ 100MHz CL3
no memory shadowing, bios caching
HDD block mode: off
S.M.A.R.T. enabled
I'll try what You suggested and let You know.
Thank You. |
|
| Back to top |
|
|
ScRaTcHi
n00b
Joined: 21 Dec 2004
Posts: 62
|
| Posted: Tue Jan 25, 2005 7:08 pm Post subject: Yeah!!! |
|
|
| Code: | | CFLAGS="-march=i386 -pipe" emerge mdadm |
It worked very well!
Back to normal, thank You very much!
You're a real RAID guru! |
|
| Back to top |
|
|
|
Kernel & Hardware
