On 20/10/19 01:06, Curtis Vaughan wrote: > > On 10/16/19 2:33 PM, Wol wrote: >> On 16/10/2019 22:15, Curtis Vaughan wrote: >>> Think I got it working, just want to make sure I did this right. Using >>> fdisk I recreated the exact same partitions on sda as on sdb. >>> >>> Then I ran the mdadm --re-add for each partition to each raid volume. So >>> now here are some outputs to various commands. Does everything look >>> right? >> >> Yup. Looks fine. >> >> Because we have two raids on one disk, the rebuild is throttled such >> that only one rebuild is proceeding at a time. >> >> md1 is rebuilding, as it says. Once that completes then all the status >> stuff will look normal, and md0 will start rebuilding. >> >> Don't know how long it will take, but because the raid doesn't know >> what bits of the disk are used and what are not, the complete rebuild >> will take however long it takes to read a 1gig drive from end to end, >> and that is quite a long time ... >> >> Cheers, >> Wol >> > Actually, I still seem to have a problem. > > After updates I decided to reboot, but it would never reboot until I > removed the new drive. I'm wondering if it has something to do with > needing to installl grub on the new drive? > > Anyhow, now that I've pulled the new drive out and started the server, > the old drive is now sda. So does that mean I should issue the commands > to add the new drive back to the raid but as sdb? > If you haven't modified the array, it should just sort itself out. If you *have* modified the array, I'm not sure if there's a re-add command. If you've got a bitmap file or journal or anything like that, it should just sort itself out. As for not rebooting because of grub, I suspect you're right. Because the two drives are mirrored, you probably mirrored grub on both drives. When the original sda failed and was removed, sdb became sda as the first drive found. When you replaced sda, that became the first drive and didn't have grub on it. Try moving sdb's cable to where sda was on the motherboard, and putting the new drive where sdb was. I guess your system will now boot fine, but you'll need to put grub on the new drive ready for the next failure ... :-) Cheers, Wol
