On Tue, 2006-11-21 at 12:10 -0500, Tony Nelson wrote: > At 1:42 PM +0000 11/21/06, Nigel Wade wrote: > ... > >In order to fix my system I used the following steps. > > > >The first step is to take the offending filesystem offline. Then I copied the > >existing partition onto the good disk using dd, with the noerror option so it > >would continue past read errors. In my case I knew that the read error was not > >part of the actual filesystem in use because it passed fsck. ... > ... > > The read error may have been in free space, or it may have been in file > data. Some of the files may be corrupt now. So, I'm dealing with 2 problems then. 1. There are errors on my "good" drive (sda) that were being ignored by the user (me) and now md is trying to be nice about it and let me know that there is a problem. I will attempt to resolve this by using Nigel's work around. 2. When reading instructions off the internet, always follow them. I.e. I created the partitions using fdisk on the replacement disk, but I didn't set the partition type to S/W Raid. Duh! This resolved the issue where rebooting the machine set sdb1 and sdb2 offline when I rebooted. I'll follow up with more if I can restore my S/W Raid tonight. Sean
