A word to the wise regarding failed fedup upgrades
Gary Stainburn
gary.stainburn at ringways.co.uk
Thu Jun 5 14:24:13 UTC 2014
On Thursday 05 June 2014 14:41:57 Trever L. Adams wrote:
> Wow. If you are missing glibc, I am not sure I can help you. You need to
> find a static mount command and cp (possibly on rescue images). If you
> can do that, just suck the glibc stuff onto a flash drive with those and
> move them over. From there, you should be able to start rebuilding.
>
> Otherwise, you are correct, likely just better to copy data and
> configuration information off the system and reload.
>
> Good luck,
> Trever
Thanks for your help Trevor
I have managed to
a) start a new server install with the software RAID I wanted - although I do
get a worrying error on boot as posted in another thread, but it seems to
work perfectly, even headless.
b) used sysresccd to boot the old server and using advice elsewhere on this
list got the mount commands out of anaconda.program.log and mounted the old
RAID partitions.
I've managed to successfully rsync off /home /etc and /root and I'm in the
process of rsyncing the Bacula storage contents (long job as over 2TB)
The Postgresql backup and an old tgz I already had on my backup backup
server :-)
Now it's just a case of working through each service and configuring it
correctly. My only concern is version dependencies on the postgresql database
and the Bacula Director config files but they're doable.
More information about the users
mailing list