Results 1 to 1 of 1
Enjoy an ad free experience by logging in. Not a member yet? Register.
- Join Date
- Aug 2009
partimage + software RAID = broken
I recently backed up a software RAID file system with partimage. It was laid out with /boot in sd[ab]1, swap in sd[ab]2, and / in sd[ab]3. I saved sda1 and sda3 with partimage.
When it comes time to restore the partimage files onto a new system with two clean disks... Everything works fine restoring the master boot record, as well as the original sda1 and sda3 images onto the fresh sd[ab]1 and sd[ab]2. After restoring everything with partimage, I ran the following commands to re-link sda1/sdb1 and sda3/sdb3 with software raid:
mdadm --create /dev/md0 --level=mirror --raid-devices=2 /dev/sda1 /dev/sdb1
mdadm --create /dev/md1 --level=mirror --raid-devices=2 /dev/sda3 /dev/sdb3
Then I rebooted... and ran into the following errors:
mdadm: no devices found for /dev/md1
Unable to access resume device (UUID=1dc07df1-2ea4-4642-8907-16d92d6ed89e)
mount: error mounting /dev/root on sysroot as ext3: Invalid argument
My /etc/fstab file on /dev/md1 looks like this while booting up with SystemRecoveryCD:
/dev/md1 / ext3 defaults 1 1
/dev/md0 /boot ext3 defaults 1 2
tmpfs /dev/shm tmpfs defaults 0 0
devpts /dev/pts devpts gid=5,mode=620 0 0
sysfs /sys sysfs defaults 0 0
proc /proc proc defaults 0 0
UUID=1dc07df1-2ea4-4642-8907-16d92d6ed89e swap swap defaults 0 0
UUID=3f379a02-4b94-1078-3009-37be987fac98f swap swap defaults 0 0
I most definitely forgot some step to update the swap partitions. However, I have spent the past few hours trying to figure out what I need to do and have been unsuccessful. All the results on Google are either for restoring an image with partimage that does not use software RAID, or creating a software RAID image from scratch instead of restoring it with partimage. Any help would be greatly appreciated.