Re: mounting LVM partitions fails after etch upgrade

On Sun, May 06, 2007 at 07:27:26PM +0200, David Fuchs wrote:
I mounted (read-only) some of the virtual volumes, to see if the data is
still there... it seems as if there is some 'offset' on the file system,
i.e.
when looking at some file it contains stuff that should be in a completely
different file... or it tells me attempt to access beyond end of device.

I gues this confirms that these filesystems are corrupted.

during the 'normal' boot process (i.e. init=/bin/sh not set) this is the
exact error I get:

[/sbin/fsck.ext3 (1) -- /var ] fsck.ext3 -a -C0 /dev/mapper/volg1-b
fsck.ext3: no such file or directory while trying to open
/dev/mapper/volg1-b
/dev/mapper/volg1-b:
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 filsystem
(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 8192 <device>

What happens if you now boot single? Does your root filesystem get
fsck'd cleanly? This is the first step. Once you can cleanly get into
a single-user root shell life is much better. From here you can again
verify that the md arrays and lvs are in good shape automatically and
from there you can fsck the filesystems without having them mounted at
all.

Note that e2fsck can take several passes. Also, you don't want the -a
option (which is the backward-compatible version of -p) which exists
with error code 4 if a problem would require human intervention, since
you are there to intervene and don't want it to exit.

Let us know how you progress.

Doug.


--
To UNSUBSCRIBE, email to debian-user-REQUEST@xxxxxxxxxxxxxxxx
with a subject of "unsubscribe". Trouble? Contact listmaster@xxxxxxxxxxxxxxxx

Relevant Pages

  • Re: Weird Apache problem, hanging on particular data patterns
    ... I have checked ALL filesystems. ... When I split one of the two "weird" files up into 1k chunks only the ... This file when assembled hangs at exactly 1,130bytes, ... > with a subject of "unsubscribe". ...
    (Debian-User)
  • Re: BTRFS partition usage...
    ... be interpreted as correct by other filesystems. ... The reason why we don't put the superblock at 0 is not because it ... screws over the sparc, but because on many systems the ... This is the best of all words; it makes sparc happy; it allows boot ...
    (Linux-Kernel)
  • Re: [REGRESSION] nfs client: Read-only file system (2.6.19-rc1,2)
    ... NFS is now doing the exact same thing that local filesystems ... represented by the same superblock. ... more than one partition, then different partitions will be represented ...
    (Linux-Kernel)
  • Re: LVM and disk failure
    ... > or RAID5. ... A single disk failure is harmless. ... > are some of the filesystems which they can contain. ... To UNSUBSCRIBE, email to debian-user-REQUEST@xxxxxxxxxxxxxxxx ...
    (Debian-User)
  • Re: find the blocksize of a FS
    ... else that doesn't rely on the utils (dumpe2fs, ... /proc/filesystems only gives what filesystems the kernel supports. ... if all else fails I think the python ctypes module should be able to get ... To UNSUBSCRIBE, email to debian-user-REQUEST@xxxxxxxxxxxxxxxx ...
    (Debian-User)