On Tuesday 13 September 2005 15:19, Aleksandar Milivojevic wrote:
> Quoting Trevor Morrison <[EMAIL PROTECTED]>:
> > Hi,
> >
> > I just got Bacula up and running on a FC 4 box and I am backing up a
> > FC 3 and a RH 9 box. This is a great program with excellent
> > documentation. My question is I can make the rescue cd for both the
> > FC 3 and RH 9 boxes, but not for the FC 4 box. I get the following
> > error:
>
> ...
>
> > ./make_rescue_disk
> > Tarring /etc files to current directory
> > tar: Removing leading `/' from member names
> > tar: /etc/modules.conf: Cannot stat: No such file or directory
> > tar: Removing leading `/' from hard link targets
> > tar: Error exit delayed from previous errors
> > make[1]: *** [all] Error 2
> > make[1]: Leaving directory
> > `/var/tmp/bacula-1.36.3.tar.gz_FILES/bacula-1.36.3/rescue/linux/cdrom/bac
> >ula' make: *** [bacula] Error 2
>
> It's the modules.conf file that doesn't exist on newer Red Hat
> distributions (they switched to modprobe.conf). You can edit the makefiles
> and/or scripts and remove modules.conf from tar list. After that, you'll
> get ISO image. However, it will not boot (the kernel gets loaded and than
> panics that it can't
> find root file system). Or at least that was what happened to me. At
> the end,
> I simply gave up on Bacula rescue CD. My guess is that the problem was
> modules
> not being loaded (since scripts that created rescue CD probably attempted
> to parse modules.conf to find list of modules to load on boot, instead of
> parsing modprobe.conf). What I did was to simply use Fedora (or RHEL)
> installation CD,
> booted into rescue mode from it, copied over bacula-fd and
> bacula-fd.conf files
> (which is really all you need in addition to the stuff you have in rescue
> mode), created /var/bacula directory (or maybe I could have simply edited
> bacula-fd.conf), and performed restore manually (created my mirrors,
> logical volumes, file systems, mounted them under /tmp/system, restored
> there, reinstalled LILO into MBR, reboot, it works). I did have some
> trouble with Bacula not restoring file permissions correctly (see thread
> "strange file permissions"), but I solved it by first restoring /etc/passwd
> and /etc/group files, and placing them into what rescue CD sees as /etc
> (you'll need to remove
> /etc/group first, since it points to copy on a CD, /etc/passwd is in ramfs,
> so you can just overwrite it). It was rather strange problem which is most
> likely
> a nasty bug in Bacula's restore code, which I hope will be fixed soon.
As far as I know, this is not a bug with Bacula, and there is nothing I can do
to fix it. Bacula does not restore file permissions with user/group names,
but rather uses the Ids. As noted in the document, if you try to restore
files to a different system with a different /etc/passwd configuration, your
permissions are going to be all screwed up. This is, in fact, what happens
when you try to do a restore on an OS booted by a non-Bacula rescue disk.
I don't think I am wrong in what I say above. However, if for some reason, I
am, someone is going to have to show me the details of how one can do a
correct restore without the correct /etc/passwd ... files.
--
Best regards,
Kern
(">
/\
V_V
-------------------------------------------------------
SF.Net email is sponsored by:
Tame your development challenges with Apache's Geronimo App Server.
Download it for free - -and be entered to win a 42" plasma tv or your very
own Sony(tm)PSP. Click here to play: http://sourceforge.net/geronimo.php
_______________________________________________
Bacula-users mailing list
Bacula-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/bacula-users
