Robert de Bath wrote:
Probably obvious but my normal cpio restore command is
cpio -ivdum
If I miss out the 'd' it doesn't automatically create directories,
is that what's happeninh here?
--
Rob. (Robert de Bath <robert$ @
debath.co.uk>)
<http://www.cix.co.uk/~mayday>
Google Homepage: http://www.google.com/search?btnI&q=Robert+de+Bath
On Wed, 29 Jan 2003, Tom Oehser wrote:
>
> > while restoring I have got the following kind of error messages:
> >
> > dev/pts: No such a file or directory
> > var/lib/xdm/authdir: No such a file or directory
> > usr/src/redhat/RPMS/athlon: No such a file or directory
> >
> > This is pointing to an empty directory on my system.
> > I have tryied to boot after having done the lilo stuff ...
> >
> > It seems that it is finding my boot and the boot program starts
but
> > after a while I have got the following error message while
checking the file
> > system:
> >
> > fsck.ext3: Exec format error
>
> I have not seen anything exactly like either of these. Does it
show
> an error if you just list the backup with cpio -itv? If so, what
is
> the behaviour of the tomsrtbt cpio -itv vs. the cpio you are
backing
> up with given -itv? I have done what I think is basically exactly
> what you are doing without problems, so I'm not sure where exactly
> to look for the problem.
>
> -Tom
>
>
Hello,
I think that I have found an answer to my cpio problem.
In fact, what was wrong was that I was using the -depth option in the
find command.
Now I have no more error messages during the recover using cpio.
Here is what I used for saving:
find . -xdev | cpio -o -H crc | dd of=/a/boot_agclust1-cpio.dd
and what I used used to restore:
dd if=/a/boot_agclust1-cpio.dd | cpio -iumd
Now, that I am able to restore my file systems whithout any problem I
cannot boot.
I still get the following error messages during the boot phase:
checking root file system
fsck.ext3: Exec format error
Can you help me please
Regards.
Giuseppe Angelini
