<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">
<HTML><HEAD>
<META content="text/html; charset=windows-1252" http-equiv=Content-Type><BASE
href="file://C:\Program Files\Common Files\Microsoft Shared\Stationery\">
<STYLE>BODY {
BACKGROUND-REPEAT: no-repeat; FONT-FAMILY: Arial; BACKGROUND-POSITION: left top; COLOR: #000000; FONT-SIZE: 10pt
}
</STYLE>
<META name=GENERATOR content="MSHTML 8.00.6001.19258"></HEAD>
<BODY bgColor=#ffffff>
<DIV>Hi</DIV>
<DIV> </DIV>
<DIV>I've got a bit of a problem with disks. It was reporting a disk
failure, but when I replaced the faulty disk last week it didn't do the RAID
rebuild.</DIV>
<DIV> </DIV>
<DIV>I run: cat /proc/mdstat</DIV>
<DIV> </DIV>
<DIV>---<BR>Personalities : [raid1] <BR>md0 : active raid1
sda1[0]<BR> 511988 blocks super 1.0 [2/1]
[U_]<BR> <BR>md1 : active raid1
sda2[0]<BR> 243625852 blocks super 1.1 [2/1]
[U_]<BR> bitmap: 2/2 pages [8KB], 65536KB
chunk</DIV>
<DIV> </DIV>
<DIV>unused devices: <none></DIV>
<DIV>---</DIV>
<DIV> </DIV>
<DIV>To back that up, mdadm is showing it's removed from the array. I run:
mdadm -D /dev/md0</DIV>
<DIV> </DIV>
<DIV>---<BR>/dev/md0:<BR> Version :
1.0<BR> Creation Time : Thu Mar 1 17:48:50
2012<BR> Raid Level : raid1<BR>
Array Size : 511988 (500.07 MiB 524.28 MB)<BR> Used Dev Size : 511988
(500.07 MiB 524.28 MB)<BR> Raid Devices : 2<BR> Total Devices
: 1<BR> Persistence : Superblock is persistent</DIV>
<DIV> </DIV>
<DIV> Update Time : Mon Aug 13 06:00:56
2012<BR> State : clean,
degraded <BR> Active Devices : 1<BR>Working Devices : 1<BR> Failed
Devices : 0<BR> Spare Devices : 0</DIV>
<DIV> </DIV>
<DIV> Name :
localhost.localdomain:0<BR>
UUID :
1b0e89cf:e18f09e5:88ce2215:a0099d63<BR>
Events : 160</DIV>
<DIV> </DIV>
<DIV> Number Major Minor
RaidDevice State<BR>
0
8
1 0
active sync /dev/sda1<BR>
1
0
0 1
removed</DIV>
<DIV>---</DIV>
<DIV> </DIV>
<DIV>Now here's the point: the fdisk command is showing a sector problem on
/dev/sda - maybe it's nothing to do with /dev/sdb.</DIV>
<DIV> </DIV>
<DIV>I run: fdisk /dev/sda, the 'p' to print the partition table. I
get:</DIV>
<DIV> </DIV>
<DIV>---</DIV>
<DIV>Disk /dev/sda: 250.0 GB, 250000000000 bytes<BR>255 heads, 63 sectors/track,
30394 cylinders<BR>Units = cylinders of 16065 * 512 = 8225280 bytes<BR>Sector
size (logical/physical): 512 bytes / 512 bytes<BR>I/O size (minimum/optimal):
512 bytes / 512 bytes<BR>Disk identifier: 0x0006751a</DIV>
<DIV> </DIV>
<DIV> Device Boot
Start
End Blocks Id
System<BR>/dev/sda1
*
1
64 512000 fd Linux raid
autodetect<BR>Partition 1 does not end on cylinder
boundary.<BR>/dev/sda2
64 30395 243627008
fd Linux raid autodetect</DIV>
<DIV>---</DIV>
<DIV> </DIV>
<DIV>As you can see sector 64 is used by two partitions. Is this a problem
and how do I rectify it? Is this what is stopping the RAID rebuild?</DIV>
<DIV> </DIV>
<DIV>Apologies for the long post, but I had to provide some background.
Many thanks indeed for the answers.</DIV>
<DIV> </DIV>
<DIV>Regards, Richard</DIV></BODY></HTML>