* Is my RAID 5 array working OK?
@ 2004-07-04 19:50 Robin Bowes
2004-07-04 20:51 ` Robin Bowes
2004-07-04 23:38 ` Daniel Pittman
0 siblings, 2 replies; 4+ messages in thread
From: Robin Bowes @ 2004-07-04 19:50 UTC (permalink / raw)
To: linux-raid
Hi,
I'm running 6 x 250GB SATA disks on 2 x Promise SATA150TX4 controllers.
I've partitioned all disks identically with two partitions, one of 1.5GB and the other with the rest of the space.
I've created 3 x 1.5GB RAID1 mirrors from the 6 x 1.5GB paritions. I've installed Fedora Core 2 onto md0, and used md2 and md3 as swap.
I'm now attempting to create a large RAID5 array from the 6 x "big" partitions.
I'm using the command:
# mdadm -v --create /dev/md5 --chunk=128 --level=raid5 --raid-devices=6 --spare-devices=0 /dev/sda2 /dev/sdb2 /dev/sdc2 /dev/sdd2 /dev/sde2 /dev/sdf2
When I look at the array to see what's happening, this is what I see:
# mdadm --detail /dev/md5
/dev/md5:
Version : 00.90.01
Creation Time : Sun Jul 4 20:48:07 2004
Raid Level : raid5
Array Size : 1218208000 (1161.77 GiB 1247.44 GB)
Device Size : 243641600 (232.35 GiB 249.49 GB)
Raid Devices : 6
Total Devices : 6
Preferred Minor : 5
Persistence : Superblock is persistent
Update Time : Sun Jul 4 20:48:07 2004
State : clean, no-errors
Active Devices : 5
Working Devices : 6
Failed Devices : 0
Spare Devices : 1
Layout : left-symmetric
Chunk Size : 128K
Rebuild Status : 2% complete
Number Major Minor RaidDevice State
0 8 2 0 active sync /dev/sda2
1 8 18 1 active sync /dev/sdb2
2 8 34 2 active sync /dev/sdc2
3 8 50 3 active sync /dev/sdd2
4 8 66 4 active sync /dev/sde2
5 0 0 -1 removed
6 8 82 5 spare /dev/sdf2
UUID : 2950b4e7:893db3f0:090135ec:f9ca1574
Events : 0.177301
Why do I appear to have 7 devices? Why is device number 6 marked as spare? Is this normal while the array is being built? Do I just need to leave it working away until it finishes, or is something wrong?
Thanks,
R.
--
http://robinbowes.com
^ permalink raw reply [flat|nested] 4+ messages in thread
* Re: Is my RAID 5 array working OK?
2004-07-04 19:50 Is my RAID 5 array working OK? Robin Bowes
@ 2004-07-04 20:51 ` Robin Bowes
2004-07-04 22:26 ` maarten van den Berg
2004-07-04 23:38 ` Daniel Pittman
1 sibling, 1 reply; 4+ messages in thread
From: Robin Bowes @ 2004-07-04 20:51 UTC (permalink / raw)
To: linux-raid
On Sun, July 4, 2004 20:50, Robin Bowes said:
> Number Major Minor RaidDevice State
> 0 8 2 0 active sync /dev/sda2 1 8 18 1
> active sync /dev/sdb2 2 8 34 2 active sync /dev/sdc2
> 3 8 50 3 active sync /dev/sdd2
> 4 8 66 4 active sync /dev/sde2
> 5 0 0 -1 removed
> 6 8 82 5 spare /dev/sdf2
> UUID : 2950b4e7:893db3f0:090135ec:f9ca1574
> Events : 0.177301
OK, so I guess I just need to wait until it finishes!
Unfortunately, I now see this:
# mdadm --detail /dev/md5
/dev/md5:
Version : 00.90.01
Creation Time : Sun Jul 4 21:24:57 2004
Raid Level : raid5
Array Size : 1218208000 (1161.77 GiB 1247.44 GB)
Device Size : 243641600 (232.35 GiB 249.49 GB)
Raid Devices : 6
Total Devices : 6
Preferred Minor : 5
Persistence : Superblock is persistent
Update Time : Sun Jul 4 21:57:13 2004
State : clean, no-errors
Active Devices : 4
Working Devices : 5
Failed Devices : 1
Spare Devices : 1
Layout : left-symmetric
Chunk Size : 128K
Number Major Minor RaidDevice State
0 8 2 0 active sync /dev/sda2
1 0 0 -1 removed
2 8 34 2 active sync /dev/sdc2
3 8 50 3 active sync /dev/sdd2
4 8 66 4 active sync /dev/sde2
5 0 0 -1 removed
6 8 82 5 spare /dev/sdf2
7 8 18 -1 faulty /dev/sdb2
UUID : 2464f7cb:7f57ffdb:fe2dcd80:fc896946
Events : 0.819771
Checking the logs shows this in /var/log/messages:
Jul 4 21:43:09 dude kernel: scsi1: ERROR on channel 0, id 0, lun 0, CDB: Read (
10) 00 01 c6 1f f7 00 03 00 00
Jul 4 21:43:09 dude kernel: Current sdb: sense key Medium Error
Jul 4 21:43:09 dude kernel: Additional sense: Unrecovered read error - auto rea
llocate failed
Jul 4 21:43:09 dude kernel: end_request: I/O error, dev sdb, sector 29761527
Jul 4 21:43:10 dude kernel: scsi1: ERROR on channel 0, id 0, lun 0, CDB: Read (
10) 00 01 c6 1f f8 00 02 ff 00
Jul 4 21:43:10 dude kernel: Current sdb: sense key Medium Error
Jul 4 21:43:10 dude kernel: Additional sense: Unrecovered read error - auto rea
llocate failed
Jul 4 21:43:10 dude kernel: end_request: I/O error, dev sdb, sector 29761528
Jul 4 21:43:11 dude kernel: scsi1: ERROR on channel 0, id 0, lun 0, CDB: Read (
10) 00 01 c6 1f f9 00 02 fe 00
Jul 4 21:43:11 dude kernel: Current sdb: sense key Medium Error
Jul 4 21:43:11 dude kernel: Additional sense: Unrecovered read error - auto rea
llocate failed
Jul 4 21:43:11 dude kernel: end_request: I/O error, dev sdb, sector 29761529
Jul 4 21:43:13 dude kernel: scsi1: ERROR on channel 0, id 0, lun 0, CDB: Read (
10) 00 01 c6 1f fa 00 02 fd 00
Jul 4 21:43:13 dude kernel: Current sdb: sense key Medium Error
Jul 4 21:43:13 dude kernel: Additional sense: Unrecovered read error - auto rea
llocate failed
Jul 4 21:43:13 dude kernel: end_request: I/O error, dev sdb, sector 29761530
Jul 4 21:43:14 dude kernel: scsi1: ERROR on channel 0, id 0, lun 0, CDB: Read (
10) 00 01 c6 1f fb 00 02 fc 00
Jul 4 21:43:14 dude kernel: Current sdb: sense key Medium Error
Jul 4 21:43:14 dude kernel: Additional sense: Unrecovered read error - auto rea
llocate failed
Jul 4 21:43:14 dude kernel: end_request: I/O error, dev sdb, sector 29761531
Jul 4 21:43:15 dude kernel: scsi1: ERROR on channel 0, id 0, lun 0, CDB: Read (
10) 00 01 c6 1f fc 00 02 fb 00
Jul 4 21:43:15 dude kernel: Current sdb: sense key Medium Error
Jul 4 21:43:15 dude kernel: Additional sense: Unrecovered read error - auto rea
llocate failed
Jul 4 21:43:15 dude kernel: end_request: I/O error, dev sdb, sector 29761532
Jul 4 21:43:17 dude kernel: scsi1: ERROR on channel 0, id 0, lun 0, CDB: Read (
10) 00 01 c6 1f fd 00 02 fa 00
Jul 4 21:43:17 dude kernel: Current sdb: sense key Medium Error
Jul 4 21:43:17 dude kernel: Additional sense: Unrecovered read error - auto rea
llocate failed
Jul 4 21:43:17 dude kernel: end_request: I/O error, dev sdb, sector 29761533
Jul 4 21:43:18 dude kernel: scsi1: ERROR on channel 0, id 0, lun 0, CDB: Read (
10) 00 01 c6 1f fe 00 02 f9 00
Jul 4 21:43:18 dude kernel: Current sdb: sense key Medium Error
Jul 4 21:43:18 dude kernel: Additional sense: Unrecovered read error - auto rea
llocate failed
Jul 4 21:43:18 dude kernel: end_request: I/O error, dev sdb, sector 29761534
Jul 4 21:43:18 dude kernel: raid5: Disk failure on sdb2, disabling device. Oper
ation continuing on 4 devices
Jul 4 21:43:20 dude kernel: scsi1: ERROR on channel 0, id 0, lun 0, CDB: Read (
10) 00 01 c6 1f ff 00 02 f8 00
Jul 4 21:43:20 dude kernel: Current sdb: sense key Medium Error
Jul 4 21:43:20 dude kernel: Additional sense: Unrecovered read error - auto rea
llocate failed
Jul 4 21:43:20 dude kernel: end_request: I/O error, dev sdb, sector 29761535
Jul 4 21:43:21 dude kernel: scsi1: ERROR on channel 0, id 0, lun 0, CDB: Read (
10) 00 01 c6 20 00 00 02 f7 00
Jul 4 21:43:21 dude kernel: Current sdb: sense key Medium Error
Jul 4 21:43:21 dude kernel: Additional sense: Unrecovered read error - auto rea
llocate failed
Jul 4 21:43:21 dude kernel: end_request: I/O error, dev sdb, sector 29761536
Jul 4 21:43:23 dude kernel: md: md5: sync done.
Jul 4 21:43:23 dude kernel: RAID5 conf printout:
Jul 4 21:43:23 dude kernel: --- rd:6 wd:4 fd:2
Jul 4 21:43:23 dude kernel: disk 0, o:1, dev:sda2
Jul 4 21:43:23 dude kernel: disk 1, o:0, dev:sdb2
Jul 4 21:43:23 dude kernel: disk 2, o:1, dev:sdc2
Jul 4 21:43:23 dude kernel: disk 3, o:1, dev:sdd2
Jul 4 21:43:23 dude kernel: disk 4, o:1, dev:sde2
Jul 4 21:43:23 dude kernel: disk 5, o:1, dev:sdf2
Jul 4 21:43:23 dude kernel: RAID5 conf printout:
Jul 4 21:43:23 dude kernel: --- rd:6 wd:4 fd:2
Jul 4 21:43:23 dude kernel: disk 0, o:1, dev:sda2
Jul 4 21:43:23 dude kernel: disk 2, o:1, dev:sdc2
Jul 4 21:43:23 dude kernel: disk 3, o:1, dev:sdd2
Jul 4 21:43:23 dude kernel: disk 4, o:1, dev:sde2
Jul 4 21:43:23 dude kernel: disk 5, o:1, dev:sdf2
Is this likely to be anything other than a bad disk?
R.
--
http://robinbowes.com
^ permalink raw reply [flat|nested] 4+ messages in thread
* Re: Is my RAID 5 array working OK?
2004-07-04 20:51 ` Robin Bowes
@ 2004-07-04 22:26 ` maarten van den Berg
0 siblings, 0 replies; 4+ messages in thread
From: maarten van den Berg @ 2004-07-04 22:26 UTC (permalink / raw)
To: linux-raid
On Sunday 04 July 2004 22:51, Robin Bowes wrote:
> On Sun, July 4, 2004 20:50, Robin Bowes said:
> Unfortunately, I now see this:
> Number Major Minor RaidDevice State
> 0 8 2 0 active sync /dev/sda2
> 1 0 0 -1 removed
> 2 8 34 2 active sync /dev/sdc2
> 3 8 50 3 active sync /dev/sdd2
> 4 8 66 4 active sync /dev/sde2
> 5 0 0 -1 removed
> 6 8 82 5 spare /dev/sdf2
> 7 8 18 -1 faulty /dev/sdb2
> UUID : 2464f7cb:7f57ffdb:fe2dcd80:fc896946
> Events : 0.819771
This is weird, if you ask me. When sdb was set faulty, the spare sdf should
have kicked in, and should now be syncing. In your previous mail, you
mentioned you did not expect there to be a spare. And I notice the missing
(removed) device number 5. So something went wrong, the spare was unwanted
according to you, and is not doing what it's supposed to do anyway.
Maybe someting is botched in the config...?
I'm not exactly sure where the fault lies, though.
Apart from that, yes, sdb sure sounds like it's broken...
Maarten
--
When I answered where I wanted to go today, they just hung up -- Unknown
^ permalink raw reply [flat|nested] 4+ messages in thread
* Re: Is my RAID 5 array working OK?
2004-07-04 19:50 Is my RAID 5 array working OK? Robin Bowes
2004-07-04 20:51 ` Robin Bowes
@ 2004-07-04 23:38 ` Daniel Pittman
1 sibling, 0 replies; 4+ messages in thread
From: Daniel Pittman @ 2004-07-04 23:38 UTC (permalink / raw)
To: linux-raid
On 5 Jul 2004, Robin Bowes wrote:
[...]
> # mdadm -v --create /dev/md5 --chunk=128 --level=raid5 --raid-devices=6
> --spare-devices=0 /dev/sda2 /dev/sdb2 /dev/sdc2 /dev/sdd2 /dev/sde2
> /dev/sdf2
>
> When I look at the array to see what's happening, this is what I see:
>
> # mdadm --detail /dev/md5
> /dev/md5:
> Version : 00.90.01
> Creation Time : Sun Jul 4 20:48:07 2004
> Raid Level : raid5
> Array Size : 1218208000 (1161.77 GiB 1247.44 GB)
> Device Size : 243641600 (232.35 GiB 249.49 GB)
> Raid Devices : 6
> Total Devices : 6
> Preferred Minor : 5
> Persistence : Superblock is persistent
>
> Update Time : Sun Jul 4 20:48:07 2004
> State : clean, no-errors
> Active Devices : 5
> Working Devices : 6
> Failed Devices : 0
> Spare Devices : 1
>
> Layout : left-symmetric
> Chunk Size : 128K
>
> Rebuild Status : 2% complete
>
> Number Major Minor RaidDevice State
> 0 8 2 0 active sync /dev/sda2
> 1 8 18 1 active sync /dev/sdb2
> 2 8 34 2 active sync /dev/sdc2
> 3 8 50 3 active sync /dev/sdd2
> 4 8 66 4 active sync /dev/sde2
> 5 0 0 -1 removed
> 6 8 82 5 spare /dev/sdf2
> UUID : 2950b4e7:893db3f0:090135ec:f9ca1574
> Events : 0.177301
>
> Why do I appear to have 7 devices? Why is device number 6 marked as
> spare? Is this normal while the array is being built? Do I just need
> to leave it working away until it finishes, or is something wrong?
As you worked out, this is part of the creation process. The reason it
is done this way is that this will apparently resync faster than just
sticking all six disks in place.
I asked the same question the first time I used the RAID-5 system. :)
Daniel
--
Keep a diary and one day it'll keep you.
-- Mae West
^ permalink raw reply [flat|nested] 4+ messages in thread
end of thread, other threads:[~2004-07-04 23:38 UTC | newest]
Thread overview: 4+ messages (download: mbox.gz follow: Atom feed
-- links below jump to the message on this page --
2004-07-04 19:50 Is my RAID 5 array working OK? Robin Bowes
2004-07-04 20:51 ` Robin Bowes
2004-07-04 22:26 ` maarten van den Berg
2004-07-04 23:38 ` Daniel Pittman
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).