[rear-users] Restoring mdadm system to a single-disk destination fails
cal-s at blue-bolt.com
Wed Jul 25 22:46:11 CEST 2012
Same situation here, but i can't quite see how rear can know about manual mdX->sdaX edits in disklayout.conf without a mapping source, esp in the case of extended partitons, which is what i had referred to (inadequately) in an earlier posting. Can use of mappings/diskxxx (sorry - away from a machine at the moment) be expanded to accomplish this?
I've been having a ball converting mdadm servers to VMs today and i think i've hit most of the issues, so i'll try to get new issues into github and elaborate a bit on the experience here tomorrow.
I think disk mapping was put to Jeroen to evaluate possible solutions?
- cal sawyer
On 25 Jul 2012, at 21:04, Les Mikesell <lesmikesell at gmail.com> wrote:
> On Tue, Jul 24, 2012 at 4:34 PM, Dag Wieers <dag at wieers.com> wrote:
>>> 2) a reminder that /etc/fstab and grub.conf needed to be fixed
>> As I already explained, we already fix /etc/fstab and grub.conf. It may
>> not be sufficient, but that we don't know.
> Is that in a released version? The current epel package won't change
> md device references to sd? when you change the layout to not use
> software raid.
> Les Mikesell
> lesmikesell at gmail.com
> rear-users mailing list
> rear-users at lists.relax-and-recover.org
More information about the rear-users