Re: VINUM: Disk crash with striped raid
Greg 'groggy' Lehey wrote: On Thursday, 7 October 2004 at 18:11:52 +0200, Paul Everlund wrote: Hi Greg and list! Thank you for your reply! I did have two 120 GB's disk drives in vinum as a striped raid. Can you be more specific? My vinum.conf looks like this, if this is to be more specific: drive ad5 device /dev/ad5s1e drive ad6 device /dev/ad6s1e volume raid0 plex org striped 127k sd length 0 drive ad5 sd length 0 drive ad6 I did contact a data recovery company and they say they need both disks to restore the raid, because of that the raid initializing might be corrupted. My questions is: Do they need both disks? That depends on your configuration. That is as above. Isn't it enough if they make a disk image of the failed drive, and I will then be able to restore the raid data initialization in vinum by a vinum create, or something similar? The command will be 'vinum start'. Thank you! Will they be able to recreate the raid data without using vinum anyway? Who knows? You at least know from this mail that I don't... :-) The real issue is the configuration of your volume (not raid). Sorry. If it only has a single plex, you're in trouble. Well, then I'm in trouble. In that case, you need your recovery company to get an image of the failed disk. Then you should put it on a similar disk, create a configuration entry and perform some other incantations, and you should be up and running again. Can you please be more specific? Is the configuration entry the one above, vinum.conf? Perform other incantations? If you have two or more plexes, you shouldn't need to do any of this. As I don't have two or more plexes it seems I have to do all of it. :-) Thank you for a reply in advance! Best regards, Paul ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: VINUM: Disk crash with striped raid
On Friday, 8 October 2004 at 14:52:48 +0200, Paul Everlund wrote: Greg 'groggy' Lehey wrote: On Thursday, 7 October 2004 at 18:11:52 +0200, Paul Everlund wrote: Can you be more specific? My vinum.conf looks like this, if this is to be more specific: drive ad5 device /dev/ad5s1e drive ad6 device /dev/ad6s1e volume raid0 plex org striped 127k sd length 0 drive ad5 sd length 0 drive ad6 It's a *very* bad idea to name Vinum drives after their current location. You can take the (physical) drives out and put them elsewhere, and Vinum will still find them. The naming is then very confusing. If it only has a single plex, you're in trouble. Well, then I'm in trouble. In that case, you need your recovery company to get an image of the failed disk. Then you should put it on a similar disk, create a configuration entry and perform some other incantations, and you should be up and running again. Can you please be more specific? Is the configuration entry the one above, vinum.conf? Perform other incantations? The easiest way is to recover the exact Vinum partition (drive) and copy it as it is onto a new Vinum drive with the same name. Then just do a 'setstate up' on the plex and subdisks. Greg -- When replying to this message, please copy the original recipients. If you don't, I may ignore the reply or reply to the original recipients. For more information, see http://www.lemis.com/questions.html See complete headers for address and phone numbers. pgpmm9KgDqqZx.pgp Description: PGP signature
VINUM: Disk crash with striped raid
Hi Greg and list! I did have two 120 GB's disk drives in vinum as a striped raid. One disk crashed, and is not found during boot. It starts up and makes the usual noises, but then it stalls with a katjing, katjing and so on. It seems like either the steering electronics, or the read/write-heads mechanics, have failed. I did contact a data recovery company and they say they need both disks to restore the raid, because of that the raid initializing might be corrupted. My questions is: Do they need both disks? Isn't it enough if they make a disk image of the failed drive, and I will then be able to restore the raid data initialization in vinum by a vinum create, or something similar? Will they be able to recreate the raid data without using vinum anyway? Thank you in advance for an answer! Best regards, Paul ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: VINUM: Disk crash with striped raid
On Thursday, 7 October 2004 at 18:11:52 +0200, Paul Everlund wrote: Hi Greg and list! I did have two 120 GB's disk drives in vinum as a striped raid. Can you be more specific? One disk crashed, and is not found during boot. It starts up and makes the usual noises, but then it stalls with a katjing, katjing and so on. It seems like either the steering electronics, or the read/write-heads mechanics, have failed. I did contact a data recovery company and they say they need both disks to restore the raid, because of that the raid initializing might be corrupted. My questions is: Do they need both disks? That depends on your configuration. Isn't it enough if they make a disk image of the failed drive, and I will then be able to restore the raid data initialization in vinum by a vinum create, or something similar? The command will be 'vinum start'. Will they be able to recreate the raid data without using vinum anyway? Who knows? The real issue is the configuration of your volume (not raid). If it only has a single plex, you're in trouble. In that case, you need your recovery company to get an image of the failed disk. Then you should put it on a similar disk, create a configuration entry and perform some other incantations, and you should be up and running again. If you have two or more plexes, you shouldn't need to do any of this. Greg -- When replying to this message, please copy the original recipients. If you don't, I may ignore the reply or reply to the original recipients. For more information, see http://www.lemis.com/questions.html See complete headers for address and phone numbers. pgp6exUJmpN6n.pgp Description: PGP signature
