On Tue, Sep 18, 2007 at 02:49:52PM -0700, Lan Barnes wrote: > > On Tue, September 18, 2007 2:43 pm, John Oliver wrote: > > I'm working on virtualizing an old Red Hat 7.3 box. I replicated the > > contents of the physical machine to the virtual disk, built a kernel > > with the right drivers, and can boot the virtual machine. But I get: > > > > (Repair filesystem) 1 # fsck /dev/sda1 > > fsck 1.27 (8-Mar-2002) > > e2fsck 1.27 (8-Mar-2002) > > fsck.ext3: No such file or directory while trying to open /dev/sda1 > > > > The superblock could not be read or does not describe a correct ext2 > > filesystem. If the device is valid and it really contains an ext2 > > filesystem (and not swap or ufs or something else), then the superblock > > is corrupt, and you might try running e2fsck with an alternate > > superblock: > > e2fsck -b 8193 <device> > > > > > > dumpe2fs says: > > > > dumpe2fs 1.32 (09-Nov-2002) > > dumpe2fs: No such file or directory while trying to open /dev/sda1 > > Couldn't find valid filesystem superblock. > > > > > > If I look at the virtual disk from a Ubuntu LiveCD, it's fine... fsck > > reports no problems. The filesystem is ext3, I can mount the virtual > > disk, chroot into it, edit files, do whatever. > > > > Ideas? > > > > Have you tried taking it at its word and fixing the superblock? I had to > puzzle through it last night on a FC6 physical drive. IIRC, I used > > mke2fs -n /dev/hda1 > > to get a list of alternate superblock locations (PLEASE do NOT leave out > the "-n"!), and then had to manually run > > fsck -y -b <alt superblock> /dev/hda1
Tried that. It gives the exact same error when I specify an alternate superblock. But since the filesystem is just fine under the LiveCD, there has to be something else going on. -- *********************************************************************** * John Oliver http://www.john-oliver.net/ * * * *********************************************************************** -- [email protected] http://www.kernel-panic.org/cgi-bin/mailman/listinfo/kplug-list
