LVM problems

Hi,

I've just brought my Debian Linux box back up after a power failure and now my LVM set up seems to be non-functional.

I'm not very clued up on LVM tbh, but it has worked so far fine for ages.

I get the following error if I try to run 'vgchange -a y 3diskvolume:

device-mapper ioctl cmd 11 failed: Invalid argument
_deps: task run failed for (254:0)
Failed to add device (254:0) to dtree
1 logical volume(s) in volume group "3diskvolume" now active

It obviously won't mount after that as mount tells me it can't find the superblock etc.

any ideas? is one of the discs dead?

Thanks,

Kelly

begin:vcard
fn:Miss Kelly Harding
n:Harding;Kelly
adr:;;;;;;UK
email;internet:[email protected]
x-mozilla-html:FALSE
version:2.1
end:vcard

Hi again,

Forgot to add details:

PC: dual PII/350mhz (p/pro overdrive), 512mb ram, SCSI LVD 80mb/s.

The VG is across 3 36gb scsi drives attached to an adaptect 2940U2W card.

I'm running kernel version 2.4.27 (2.6 doesn't seem to like this system).

I noticed from the dmesg output the following:

device-mapper: one of name or uuid must be supplied, cmd(11)

This appears when the previously mentioned command is run.

I've no idea what this means or if it isa case of a re-install of the base system might fix this? maybe something with the base system has gone a bit fubar?

any help or advice on this would be greatly appreciated.

If it comes ot it that I lose the data and have to format and star the LVM VG over again it won't be ideal but it won't be losing anything vital either (just video files, etc).

Kelly

begin:vcard
fn:Miss Kelly Harding
n:Harding;Kelly
adr:;;;;;;UK
email;internet:[email protected]
x-mozilla-html:FALSE
version:2.1
end:vcard

Recently I also suffered problems with LVM(2)

These are very basic things I presume U might have already done but just in case if not ...

imho pl boot with rescue disk (or mode)
As a precaution select read-only mount of file system if required chroot to /mnt/sysimage

# mount  ! look for lvm things specifically a word - mapper
# pvdisplay
# vgdisplay
# lvdisplay
# pvscan
# vgscan
# lvscan

thiese will tell status of lvm things
Then check /etc/fstab (carefully)

U may then "very very carefully" use e2fsck or fsck [{("after dismounting the volumes")}] as you may you deem fit.
"very very carefully" means, as a minimum, first read both manpages, try these commands in read-only mode + do not modify anything + verbose.

### use vgck with caution and also checkout /etc/lvm/lvm.conf

U may try in init 1 mode also but more caution requested.

good luck & Pl post if U get it right this way or anyway.

--
Anil Kumar Shrama

This development version of LVM2 requires a 2.6 kernel - it relies on patches added to 2.6 upstream about a year ago.

Either upgrade to a 2.6 kernel or downgrade your lvm2 & device-mapper packages.

It would be straightforward to backport the changes to 2.4 but nobody's done it yet. Patches welcome!

ftp://sources.redhat.com/pub/dm/patches/2.6-unstable/2.6.9-rc3/2.6.9-rc3-udm1/00004.patch

Alasdair

[email protected]