Re: Replacing failed drive in software RAID
On Thu, Oct 31, 2013 at 02:41:01PM -0600, Bob Proulx wrote:
> But if you are concerned about writes to sdb
> then I would simply plan to boot from the debian-installer image in
> rescue mode, assemble the raid, sync, then replace sdb, and repeat.
> You can always install grub to the boot sectors after replacing the
> suspect disks. Hopefully this makes sense.
I replaced sdd drive and that went without problem, but after replacing sda,
the drive with boot partition and MBR, system stalled at "veryfying dmi pool
data". So I inserted debian CD and went with rescue mode. I haven't used it so
I have some questions.
I'm offered to reassemble RAID. Is it safe to use auto reconfigure option or
should I assemble all three manually?
If I should go with manually, what to do with md0? It's RAID1 for boot
partition and now there is only one drive.
Should I recreate md1 and md2 with three drives? Would that work?
After this is done successfully, I assume I should go with:
# vgscan
# vgchange -a y volume_group_name
and mount manually all partitions (there is root and swap, so I guess I only
need to mount root). Am I right?
Then, after creating partition table and adding new drive into RAID, would
simple:
# grub-install /dev/sda
do the job?
Anything else to think about?
Regards,
Veljko
Reply to: