|
From: | Felix Ehlermann |
Subject: | Re: [Bug-ddrescue] ddrescue of a ddrescue |
Date: | Thu, 17 Oct 2013 21:32:06 +0200 |
User-agent: | Mozilla/5.0 (Windows NT 5.1; rv:17.0) Gecko/20130801 Thunderbird/17.0.8 |
Dear Jonathan Joseph,
one thing is not quite clear to me: Is your RAID5- array "failed" (more than 1 disk is dead) or "degraded" (1 disk dead)? If the array is "degraded" you should be fine by just replacing the faulty disk with a working one (same size or larger should not matter. The array should be able to rebuild onto the new drive (if it doesn't => something else is wrong). There is no need for ddrescue in this situation. In this case I would do a backup first anyway. Your array should still be able to start and therefore the filesystem on it should be accessible just fine. No data lost yet. If the array has indeed "failed" you're looking at a rather complicated situation as you basically have an even more ugly situation than a failed raid-0 would be. In that case just copying the sectors 1:1 onto a working drive will NOT resolve your issue. If the data on the array is important / valuable and you don't have a backup of it I suggest that you hand this over to someone with some experience in this field. This is not meant as an offense, I just know how much we charge our customers with their "we already tried to fix it before we asked for help" kind of administrators - sometimes just to find out that their data could have been salvaged if it had not been destroyed by improper handling of the situation by their admin :-( Regarding your actual question: If the new 1.5TB-drive is exactly the same size as the failed drive, you should be fine writing the data from the 2TB disk onto it with ddrescue or even dd. It will of course abort at a certain point because the new 1.5TB disk will run "out of space" - but the remaining data from the 2TB drive does not originate from your failed 1.5TB disk anyway, so this doesn't matter. However as written above this is very likely not going to resolve the issue with your array. Probably the meta information on the drives are out of sync (if you really have a "failed" array). This can be fixed, but it is very specific to what kind of raid you are using. Kind Regards Felix On 17.10.2013 18:57, Jonathan Joseph wrote:
|
[Prev in Thread] | Current Thread | [Next in Thread] |