Your logs indicate that the Raid code decided to look at hdh2 as gospel and
dismiss all of the rest.  The easiest solution is to temporarily disconnect
or disable hdh2, then restart the system.  It will accept the data on all of
the other drives as OK now and start up the array in "degraded" mode due to
the missing hdh2 drive.  Shut the system down once more, reattach hdh2 and
start it up one more time.  This time, all of the drives should be there,
but with hdh2 listed as out of step.  Now you should be able to do a
"raidhotadd /dev/md0 /dev/hdh2" to start reconstruction with hdh2 included.

Good luck!
Rich B
----- Original Message -----
From: "Pavel Kucera" <[EMAIL PROTECTED]>
To: <[EMAIL PROTECTED]>
Sent: Thursday, May 18, 2000 9:46 AM
Subject: Help with RAID5 damage please


> Hello,
>
> I have all my backup on server with 8 EIDE disk in RAID5 array. This
> server was cold rebooted and now RAID5 has unconsistent superblock. Is
> there any posibility to get my data back from RAID ?
>
> Thanks,
>
> Pavel
>
> This is what happens when I try to start raid (raidstart):
>
>
> May 18 16:38:27 backup kernel: (read) hda2's sb offset: 36363008
> [events: 00000008]
> May 18 16:38:27 backup kernel: (read) hdb2's sb offset: 36363008
> [events: 00000008]
> May 18 16:38:27 backup kernel: (read) hdc2's sb offset: 36363008
> [events: 00000008]
> May 18 16:38:27 backup kernel: (read) hdd2's sb offset: 36363008
> [events: 00000008]
> May 18 16:38:27 backup kernel: (read) hde2's sb offset: 36363008
> [events: 00000008]
> May 18 16:38:27 backup kernel: (read) hdf2's sb offset: 36363008
> [events: 00000008]
> May 18 16:38:27 backup kernel: (read) hdg2's sb offset: 36363008
> [events: 00000008]
> May 18 16:38:27 backup kernel: (read) hdh2's sb offset: 36363008
> [events: 0000000a]
> May 18 16:38:27 backup kernel: autorun ...
> May 18 16:38:27 backup kernel: considering hdh2 ...
> May 18 16:38:27 backup kernel:   adding hdh2 ...
> May 18 16:38:27 backup kernel:   adding hdg2 ...
> May 18 16:38:27 backup kernel:   adding hdf2 ...
> May 18 16:38:27 backup kernel:   adding hde2 ...
> May 18 16:38:27 backup kernel:   adding hdd2 ...
> May 18 16:38:27 backup kernel:   adding hdc2 ...
> May 18 16:38:27 backup kernel:   adding hdb2 ...
> May 18 16:38:27 backup kernel:   adding hda2 ...
> May 18 16:38:27 backup kernel: created md0
> May 18 16:38:27 backup kernel: bind<hda2,1>
> May 18 16:38:27 backup kernel: bind<hdb2,2>
> May 18 16:38:27 backup kernel: bind<hdc2,3>
> May 18 16:38:27 backup kernel: bind<hdd2,4>
> May 18 16:38:27 backup kernel: bind<hde2,5>
> May 18 16:38:27 backup kernel: bind<hdf2,6>
> May 18 16:38:27 backup kernel: bind<hdg2,7>
> May 18 16:38:27 backup kernel: bind<hdh2,8>
> May 18 16:38:27 backup kernel: running:
> <hdh2><hdg2><hdf2><hde2><hdd2><hdc2><hdb2><hda2>
> May 18 16:38:27 backup kernel: now!
> May 18 16:38:27 backup kernel: hdh2's event counter: 0000000a
> May 18 16:38:27 backup kernel: hdg2's event counter: 00000008
> May 18 16:38:27 backup kernel: hdf2's event counter: 00000008
> May 18 16:38:27 backup kernel: hde2's event counter: 00000008
> May 18 16:38:27 backup kernel: hdd2's event counter: 00000008
> May 18 16:38:27 backup kernel: hdc2's event counter: 00000008
> May 18 16:38:27 backup kernel: hdb2's event counter: 00000008
> May 18 16:38:27 backup kernel: hda2's event counter: 00000008
> May 18 16:38:27 backup kernel: md: superblock update time inconsistency
> -- using the most recent one
> May 18 16:38:27 backup kernel: freshest: hdh2
> May 18 16:38:27 backup kernel: md: kicking non-fresh hdg2 from array!
> May 18 16:38:27 backup kernel: unbind<hdg2,7>
> May 18 16:38:27 backup kernel: export_rdev(hdg2)
> May 18 16:38:27 backup kernel: md: kicking non-fresh hdf2 from array!
> May 18 16:38:27 backup kernel: unbind<hdf2,6>
> May 18 16:38:27 backup kernel: export_rdev(hdf2)
> May 18 16:38:27 backup kernel: md: kicking non-fresh hde2 from array!
> May 18 16:38:27 backup kernel: unbind<hde2,5>
> May 18 16:38:27 backup kernel: export_rdev(hde2)
> May 18 16:38:27 backup kernel: md: kicking non-fresh hdd2 from array!
> May 18 16:38:27 backup kernel: unbind<hdd2,4>
> May 18 16:38:27 backup kernel: export_rdev(hdd2)
> May 18 16:38:27 backup kernel: md: kicking non-fresh hdc2 from array!
> May 18 16:38:27 backup kernel: unbind<hdc2,3>
> May 18 16:38:27 backup kernel: export_rdev(hdc2)
> May 18 16:38:27 backup kernel: md: kicking non-fresh hdb2 from array!
> May 18 16:38:27 backup kernel: unbind<hdb2,2>
> May 18 16:38:27 backup kernel: export_rdev(hdb2)
> May 18 16:38:27 backup kernel: md: kicking non-fresh hda2 from array!
> May 18 16:38:27 backup kernel: unbind<hda2,1>
> May 18 16:38:27 backup kernel: export_rdev(hda2)
> May 18 16:38:27 backup kernel: md0: former device hda2 is unavailable,
> removing from array!
> May 18 16:38:27 backup kernel: md0: former device hdb2 is unavailable,
> removing from array!
> May 18 16:38:27 backup kernel: md0: former device hdc2 is unavailable,
> removing from array!
> May 18 16:38:27 backup kernel: md0: former device hdd2 is unavailable,
> removing from array!
> May 18 16:38:27 backup kernel: md0: former device hde2 is unavailable,
> removing from array!
> May 18 16:38:27 backup kernel: md0: former device hdf2 is unavailable,
> removing from array!
> May 18 16:38:27 backup kernel: md0: former device hdg2 is unavailable,
> removing from array!
> May 18 16:38:27 backup kernel: md: md0: raid array is not clean --
> starting background reconstruction
> May 18 16:38:27 backup kernel: md0: max total readahead window set to
> 896k
> May 18 16:38:27 backup kernel: md0: 7 data-disks, max readahead per
> data-disk: 128k
> May 18 16:38:27 backup kernel: raid5: device hdh2 operational as raid
> disk 7
> May 18 16:38:27 backup kernel: raid5: not enough operational devices for
> md0 (7/8 failed)
> May 18 16:38:27 backup kernel: RAID5 conf printout:
> May 18 16:38:27 backup kernel:  --- rd:8 wd:1 fd:7
> May 18 16:38:27 backup kernel:  disk 0, s:0, o:0, n:0 rd:0 us:1 dev:[dev
> 00:00]
> May 18 16:38:27 backup kernel:  disk 1, s:0, o:0, n:1 rd:1 us:1 dev:[dev
> 00:00]
> May 18 16:38:27 backup kernel:  disk 2, s:0, o:0, n:2 rd:2 us:1 dev:[dev
> 00:00]
> May 18 16:38:27 backup kernel:  disk 3, s:0, o:0, n:3 rd:3 us:1 dev:[dev
> 00:00]
> May 18 16:38:27 backup kernel:  disk 4, s:0, o:0, n:4 rd:4 us:1 dev:[dev
> 00:00]
> May 18 16:38:27 backup kernel:  disk 5, s:0, o:0, n:5 rd:5 us:1 dev:[dev
> 00:00]
> May 18 16:38:27 backup kernel:  disk 6, s:0, o:0, n:6 rd:6 us:1 dev:[dev
> 00:00]
> May 18 16:38:27 backup kernel:  disk 7, s:0, o:1, n:7 rd:7 us:1 dev:hdh2
>
> May 18 16:38:27 backup kernel:  disk 8, s:0, o:0, n:0 rd:0 us:0 dev:[dev
> 00:00]
> May 18 16:38:27 backup kernel:  disk 9, s:0, o:0, n:0 rd:0 us:0 dev:[dev
> 00:00]
> May 18 16:38:27 backup kernel:  disk 10, s:0, o:0, n:0 rd:0 us:0
> dev:[dev 00:00]
> May 18 16:38:27 backup kernel:  disk 11, s:0, o:0, n:0 rd:0 us:0
> dev:[dev 00:00]
> May 18 16:38:27 backup kernel: raid5: failed to run raid set md0
> May 18 16:38:27 backup kernel: pers->run() failed ...
> May 18 16:38:27 backup kernel: do_md_run() returned -22
> May 18 16:38:27 backup kernel: unbind<hdh2,0>
> May 18 16:38:27 backup kernel: export_rdev(hdh2)
> May 18 16:38:27 backup kernel: md0 stopped.
> May 18 16:38:27 backup kernel: ... autorun DONE.
>
>
>

Reply via email to