--- Begin Message ---Robert de Bath wrote:On Mon, 10 Feb 2003, Tom Oehser wrote:>
> What command did you use to create the filesystem before the cpio restore?
>
> It sounds more like a problem with the filesystem creation options. For
> ext3, you should be using at least the -j option on mke2fs.
>
> -TomAt this point in time (file system mounted read only) there is no
difference what so ever between ext2 and ext3. _While_ an ext3 fs
is being mounted there may be a journal replay but once that's done
they are the same until the root-fs is remounted read-write. Also
an ext3 filesystem can be mounted (rw) as an ext2 and an ext2 can
be simply promoted to an ext3.So at this point in time the fs being ext2 or ext3 is irrelevent.
By Angelini Giuseppe <[EMAIL PROTECTED]>
> 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 errorThis seems to point to a corruption of the executable, it's unlikely
to be a shared library problem 'cause there suld have been a lot of
other programs that have already been run.I would try replacing /sbin/fsck.ext3 by a copy of the fsck.ext2 executable,
they should be identical but probably aren't actually links.If they're both corrupt (or the same file) I'd just use a 'null' file
to get booted.Eg from Toms disk:
echo '#!/bin/sh' > /mnt/sbin/fsck.ext3
chmod 755 /mnt/sbin/fsck.ext3And fix it for real when you get your package manager back.
By Angelini Giuseppe <[EMAIL PROTECTED]>
> 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.It doesn't make any difference when you're running as root, but you
actually should use the -depth option for find and the "-d" option
to cpio when you're running as a different user. This is so cpio
can create the files in a directory before it changes the directory
mode bits to read-only. If you don't use -depth cpio will create the
directory with the original permissions (possibly read-only) and may
not be able to populate it afterwards. (I think gnu-cpio has a work
around, but I don't know about pax)--
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+BathThanks for your help,
In fact, I had to force the boot with echo '#!/bin/sh' > /mnt/sbin/fsck.ext3
chmod 755 /mnt/sbin/fsck.ext3
My problem is that fsck.ext2 and fsck.ext3 are empty.
Now, I have noticed that fsck.ext3 is a link to fsck.ext2.
I think that my problem is to tell cpio to restore the links.Can you help me please.
Regards.
Giuseppe Angelini
--- End Message ---
