[Wylug-help] Disc failure on a software RAID system has killed everything
Martyn Ranyard
ranyardm at gmail.com
Thu May 20 10:33:11 UTC 2010
Hi Gary,
Just on my way out, but sounds like the classic two drives have actually
failed, as sysresccd isn't recognising sde2.
Either : you've physically removed (or the bios is no longer seeing) the
dead disk (are you sure it's the dead one you've removed?) and therefore
there's a problem with one of the remaining disks as well, OR two of the
five disks are dead, in which case, it's data recovery uk time...
Remember, if you remove disk b from a 5 disk system, disk c becomes disk
b, disk d becomes c etc.
If you have removed the "dead" disk, try putting it back so you have abcde
(check with fdisk -l /dev/sda /dev/sdb ...) and try to assemble the array.
if it assembles degraded, you probably have removed the wrong disk.
If not, paste the output of fdisk -l /dev/sda /dev/sdb /dev/sdc /dev/sdd
/dev/sde and perhaps people here might have enough info to spot the problem.
--
Martyn
On 20 May 2010 11:15, Gary Stainburn <gary.stainburn at ringways.co.uk> wrote:
> On Thursday 20 May 2010 10:11:35 Gary Stainburn wrote:
> > Number Major Minor RaidDevice State
> > 0 0 0 0 removed
> > 1 0 0 1 removed
> > 2 0 0 2 removed
> > 3 8 34 3 active sync /dev/sdc2
> > 4 8 50 4 active sync /dev/sdd2
> > root at sysresccd /root %
>
> I'm trying to assemble the array as much as possible, but I can't because
> it
> complains about missing super blocks. Anyone got suggestions (/dev/sdb2 is
> on the dead drive)
>
> root at sysresccd /root %
> mdadm --assemble /dev/md2 /dev/sda2 /dev/sdb2 /dev/sdc2 /dev/sdd2 /dev/sde2
> mdadm: no RAID superblock on /dev/sdb2
> mdadm: /dev/sdb2 has no superblock - assembly aborted
> root at sysresccd /root %
> mdadm --assemble /dev/md2 /dev/sda2 /dev/sdc2 /dev/sdd2 /dev/sde2
> mdadm: cannot open device /dev/sde2: No such file or directory
> mdadm: /dev/sde2 has no superblock - assembly aborted
> root at sysresccd /root % mdadm --assemble /dev/md2 /dev/sda2 /dev/sdc2
> /dev/sdd2
> mdadm: /dev/md2 assembled from 2 drives - not enough to start the array.
> root at sysresccd /root % mdadm --manage --run /dev/md2
> mdadm: failed to run array /dev/md2: Input/output error
> root at sysresccd /root % mdadm --detail /dev/md2
> /dev/md2:
> Version : 0.90
> Creation Time : Fri Aug 29 12:29:18 2008
> Raid Level : raid5
> Used Dev Size : 483492096 (461.09 GiB 495.10 GB)
> Raid Devices : 5
> Total Devices : 2
> Preferred Minor : 2
> Persistence : Superblock is persistent
>
> Update Time : Thu May 13 20:27:51 2010
> State : active, degraded, Not Started
> Active Devices : 2
> Working Devices : 2
> Failed Devices : 0
> Spare Devices : 0
>
> Layout : left-symmetric
> Chunk Size : 256K
>
> UUID : 549f851d:f698831d:8e1f38fa:6d8d3a6f
> Events : 0.553056
>
> Number Major Minor RaidDevice State
> 0 0 0 0 removed
> 1 0 0 1 removed
> 2 0 0 2 removed
> 3 8 34 3 active sync /dev/sdc2
> 4 8 50 4 active sync /dev/sdd2
> root at sysresccd /root % mdadm --manage --stop /dev/md2
> mdadm: stopped /dev/md2
> root at sysresccd /root % mdadm --assemble /dev/md2 /dev/sda2
> mdadm: /dev/md2 assembled from 1 drive - not enough to start the array.
> root at sysresccd /root % mdadm --manage --run /dev/md2
> mdadm: failed to run array /dev/md2: Input/output error
> root at sysresccd /root % mdadm --detail /dev/md2
> /dev/md2:
> Version : 0.90
> Creation Time : Fri Aug 29 12:29:18 2008
> Raid Level : raid5
> Used Dev Size : 483492096 (461.09 GiB 495.10 GB)
> Raid Devices : 5
> Total Devices : 1
> Preferred Minor : 2
> Persistence : Superblock is persistent
>
> Update Time : Thu May 13 20:22:11 2010
> State : active, degraded, Not Started
> Active Devices : 1
> Working Devices : 1
> Failed Devices : 0
> Spare Devices : 0
>
> Layout : left-symmetric
> Chunk Size : 256K
>
> UUID : 549f851d:f698831d:8e1f38fa:6d8d3a6f
> Events : 0.553049
>
> Number Major Minor RaidDevice State
> 0 8 2 0 active sync /dev/sda2
> 1 0 0 1 removed
> 2 0 0 2 removed
> 3 0 0 3 removed
> 4 0 0 4 removed
> root at sysresccd /root %
>
>
> --
> Gary Stainburn
>
> This email does not contain private or confidential material as it
> may be snooped on by interested government parties for unknown
> and undisclosed purposes - Regulation of Investigatory Powers Act, 2000
>
> _______________________________________________
> Wylug-help mailing list
> Wylug-help at wylug.org.uk
> https://mailman.lug.org.uk/mailman/listinfo/wylug-help
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://mailman.lug.org.uk/pipermail/wylug-help/attachments/20100520/86a0a175/attachment-0001.htm
More information about the Wylug-help
mailing list