failed to RUN_ARRAY, input/output error

Hello all

I just ran into a problem with my RAID5 array. Everything seemed to run
fine, but then suddenly froze and upon reboot the boot process wouldn't
start from the array and panic'ed after a while.

Here's the data I've been able to gather from my FC 5 linux rescue session:

My partitions: /dev/hda2, /dev/hdc2, /dev/hde1, /dev/hdg1
/dev/hde is not working - lots of DriveReady SeekComplete Error and others

# mdadm -V
mdadm - v2.3.1

# mdadm -E /dev/hda2, /dev/hdc2 and /dev/hdg1 yields:
Same on all:
Magic: a92b4efc
Version: 00.90.01
UUID :
Raid Level: raid5
Raid Devices: 4
Total Devices: 4
Preferred Minor: 0
State: active
Active Devices: 3
Working Devices: 3
Failed Devices: 2
Events: 0.4188000
Layout: left-symmetric
Chunk size: 256K

Number Major Minor RaidDevice State
0 3 2 0 active sync /dev/hda2
1 22 2 1 active sync /dev/hdc2
2 0 0 2 faulty removed
3 34 1 3 active sync /dev/hdg1

Different on all:
Checksum

# mdadm --assemble /dev/md0 /dev/hda2 /dev/hdc2 /dev/hdg1
mdadm: failed to RUN_ARRAY /dev/md0: Input/output error

# cat /proc/mdstat
md0: inactive hda2[0] hdg1[3] hdc2[1]

# mdadm --detail /dev/md0
Persistence: Superblock is persistent
State: active, degraded
Active Devices: 3
Working Devices: 3
Failed Devices: 0

Number Major Minor RaidDevice State
0 3 2 0 active sync /dev/hda2
1 22 2 1 active sync /dev/hdc2
0 0 0 2311520 removed
3 34 1 3 active sync /dev/hdg1

I'm off to buy another 200GiB disk now, but is my current array doomed or
do I have a chance?
Any inputs would be highly welcome!

thanks
Johnny Ljunggren


-
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: failed to RUN_ARRAY, input/output error

On Tuesday April 11, johnny@navtek.no wrote:
> State: active

> Number Major Minor RaidDevice State
> 0 3 2 0 active sync /dev/hda2
> 1 22 2 1 active sync /dev/hdc2
> 2 0 0 2 faulty removed
> 3 34 1 3 active sync /dev/hdg1

active and degraded is a bad combination. There is a small
possibility of undetectable data corruption.
I wonder why the system froze - that would contribute to the 'active'.

Add a '--force' to the '--assemble' and it will start the array for
you.

NeilBrown
-
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: failed to RUN_ARRAY, input/output error

>> State: active
>
>> Number Major Minor RaidDevice State
>> 0 3 2 0 active sync /dev/hda2
>> 1 22 2 1 active sync /dev/hdc2
>> 2 0 0 2 faulty removed
>> 3 34 1 3 active sync /dev/hdg1
>
> active and degraded is a bad combination. There is a small
> possibility of undetectable data corruption.
> I wonder why the system froze - that would contribute to the 'active'.

I'm not quite sure, but I noticed a looong list of smbd processes running
so I tried to do a smb restart command, but that led to the freeze. I
could ping it but not log in.

> Add a '--force' to the '--assemble' and it will start the array for you.

I've tried that but it gives a Input/output error as well.
No luck trying to mount it either, but I guess that doesn't come as a
surprise.

Johnny





-
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: failed to RUN_ARRAY, input/output error

Neil Brown wrote:
> Add a '--force' to the '--assemble' and it will start the array for
> you.
>

Just an update (happy one) to the problem. This is what I did (from memory):
-Replaced the failed harddrive
-Used FC5 disc 1 to start in rescue mode
-Used fdisk to partition the new hard drive
-# mdadm -A /dev/md0 /dev/hda2 /dev/hdc2 /dev/hdg1
-# mdadm /dev/md0 -a /dev/hde1
-# mdadm -S /dev/md0
-# mdadm -A --force /dev/md0 /dev/hda2 /dev/hdc2 /dev/hde1 /dev/hdg1
I did some tests with 'mdadm -A --force /dev/md0 /dev/hda2 /dev/hdc2
/dev/hde1 /dev/hdg1 --update=summaries/resync' as well but I'm not sure
if that had anything to do with it.
Anyway, I'm up and running.

--
Johnny Ljunggren, Navtek AS
Tlf: 918 50 411, 33 07 10 77

-
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