My apologies for asking a question that was in the FAQ. I thought the not-fresh attribute was perhaps recoverable with something less scary than mkraid --force. Turns out this was the correct solution, and my data is recovered, safe and sound. Thank you very much. -Titus On (06/19 01:37), Jakob Oestergaard wrote: > On Tue, Jun 18, 2002 at 04:28:13PM -0700, Titus Winters wrote: > > Please help my poor file server: > > > > I've got 4 scsi drives on two controllers running RAID-5 in software. > > > > So as near as I can tell I've got one drive that failed and cut off > > communications with the other disk on the SCSI controller (or something) > > which made that second drive become not-fresh before the kernel panicked. > > > > dmseg says that one is not-fresh, and the other is faulty. How do I > > proceed without data loss? I've tried raidhotadd to bring up the > > not-fresh drive, but the raid device can't start up and thus I can't > > hot add it. > > Section 6.1 in the Software RAID HOWTO: > > http://unthought.net/Software-RAID.HOWTO/Software-RAID.HOWTO-6.html#ss6.1 > > -- > ................................................................ > : jakob@unthought.net : And I see the elder races, : > :.........................: putrid forms of man : > : Jakob Østergaard : See him rise and claim the earth, : > : OZ9ABN : his downfall is at hand. : > :.........................:............{Konkhra}...............: - 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
