On 9/19/07, John Oliver <[EMAIL PROTECTED]> wrote:
> On Tue, Sep 18, 2007 at 06:02:37PM -0700, Carl Lowenstein wrote:
> > On 9/18/07, John Oliver <[EMAIL PROTECTED]> wrote:
> > >
> > > Yes, I can mount, unmount, fsck, ls, etc. under Ubuntu. But the kernel
> > > loaded in the VM cannot. And I've tried several different kernels...
> > > I've gone back and compiled ext2 and ext3 statically and as modules,
> > > etc.
> > >
> > > > I am not aware of any strange changes made to ext2 that would make a
> > > > newer version unreadable by a far older kernel (2.4.18).
> > >
> > > Someone had suggested that an ext2 or ext3 filesystem created by a newer
> > > Linux wouldn't work under an older Red Hat, so I even created and
> > > formatted the partition with a Red Hat 7.3 rescue CD.
> > >
> > > And I'm having the exact same problem with a Red Hat 9 VM. If I keep
> > > screwing around, I can get it to kernel panic: VFS: Unable to mount root
> > > fs on 08:02 Like http://www.john-oliver.net/nllnk01-2.GIF We can see
> > > that /dev/sda is seen just fine, and that /dev/sda1 and /dev/sda2 are
> > > seen as well. This may be the result of not having the right
> > > combination of ext2 and/or ext3 compiled as a module or statically or
> > > whatever the heck it wants so it will start to bomb out with the
> > > superblock error again.
> >
> > Step back and reconsider what your real goal is.
> >
> > If you can read the original file system using a live CD, then just
> > copy it all to a clean file system on another drive. Using your
> > choice of command-line tools. Note that mkisofs will gladly make
> > multi-gigabyte ISO files that can be loop mounted.
>
> My goal is to successfully boot the VMs with these filesystems. I
> created the VMs, created filesystems, and rsynced the contents of the
> live machines. What is copying everything again going to accomplish?
Replace whatever is wrong with the file system metadata that keeps
fsck from working?
Perhaps you have a bad copy of fsck on the system you are trying to
run. Possibly you should try a clean install of the OS, followed by
fsck, followed by copying over everything that isn't the OS.
carl
--
carl lowenstein marine physical lab u.c. san diego
[EMAIL PROTECTED]
--
[email protected]
http://www.kernel-panic.org/cgi-bin/mailman/listinfo/kplug-list
