Encrypted lvm error messages at boot

2020-02-21 Thread john doe
Hi all,

I just installed Debian buster with encrypted LVM, when starting Debian
I see the following:

"  Volume group "debian-buster-vg" not found
  Cannot process volume group debian-buster-vg
  Volume group "debian-buster-vg" not found
  Cannot process volume group debian-buster-vg"

It works but I would like to get rid of those error messages.

Any thoughts on how to do that is appriciated?

--
John Doe



Re: lvm: error whilst loading shared libraries

2011-02-14 Thread Boyd Stephen Smith Jr.
On Monday 14 February 2011 09:56:55 Glyn Astill wrote:
> "lvm: error whilst loading shared libraries: libgcc_s.so.1: cannot open
> shared object file: no such file or directory"

Sounds like something got way too aggressive when removing packages.  Can you 
get into the system environment another way?  E.g. boot from a live CD mount 
up your filesystems and chroot.

That file should be provided by libgcc1, which a a Depend of libc6, which is a 
Depend of lvm2.  Check the status of those packages to make sure they are 
healthy.  If not, use aptitude, apt-get, or dpkg to repair them.  If so, I'd 
try a reinstall of those 3 packages, anyway.

Once that is straightened out, backup and rebuild your initrd, then try to get 
the system to boot under its own power again.

I'm using an LVM root volume on both a laptop and a desktop, so I know it 
works, but both of them were upgraded to squeeze rather incrementally.  The 
Lenny -> Squeeze jump for both of the VPSes was a bit more rocky.

> http://www.howtoforge.com/upgrade-debian-lenny-to-squeeze-in-a-few-simple-s
> teps

I think the release notes were much more informative and the actual upgrade 
procedures documented there are not much longer than the article.

The article starts with lenny-volatile enabled, but doesn't end with squeeze-
updates enabled, which seems a bit wrong, too.
-- 
Boyd Stephen Smith Jr.   ,= ,-_-. =.
b...@iguanasuicide.net  ((_/)o o(\_))
ICQ: 514984 YM/AIM: DaTwinkDaddy `-'(. .)`-'
http://iguanasuicide.net/\_/


signature.asc
Description: This is a digitally signed message part.


lvm: error whilst loading shared libraries

2011-02-14 Thread Glyn Astill
Hi Guys,

I've just had an attempt at upgrading a machine from lenny to squeeze, however 
this machine as an lvm root volume.

Upon booting I now see the message:

"lvm: error whilst loading shared libraries: libgcc_s.so.1: cannot open shared 
object file: no such file or directory"

I'm guessing I'm missing some dependancy here, so far I can only boot to the 
initramfs userspace. Any ideas how I can move forward here?


I followed a "guide" at the url below on this machine that isn't vital, however 
I'm beginnig to wish I'd not bothered following that advice now.

http://www.howtoforge.com/upgrade-debian-lenny-to-squeeze-in-a-few-simple-steps








--
To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Archive: http://lists.debian.org/419024.38995...@web26003.mail.ukl.yahoo.com



LVM error

2005-07-20 Thread Bernard Fay
Hello,

I have installed Debian Sarge on a system with 2 sata drives and LVM.

For every LVM command I run, I have the error:

Incorrect metadata area header checksum

Does someone know the meaning of this error and how to fix it?


Thanks,
Bern


-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED] 
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]



Re: Installing custom kernel-image fails on LVM error - I'm lost :/

2005-06-22 Thread Benedict Verheyen

Andreas Janssen wrote:

Hello

Mart Frauenlob (<[EMAIL PROTECTED]>) wrote:



What i'm trying to do:
Install a custom kernel-image build with debian kernel-source and
make-dpkg. I try to trimm down the kernel to hold only what is
absolutely necessary. Also i try to compile directly into the kernel
whatever i think of useful (performance).

When i set in menuconfig to compile RAID and LVM support directly into
the kernel, the 'dpkg -i' process ends with the following error
message:

[...]
(2005.06.22.00.00) ... File descriptor 3 left open File descriptor 4
left open File descriptor 5 left open
File descriptor 6 left open
File descriptor 7 left open
Finding all volume groups
Finding volume group "vg0"
/usr/sbin/mkinitrd: /dev/mapper/vg0-lv_swap: Kernel does not support
LVM Failed to create initrd image.


It's a bug:
#293508: initrd-tools refuses to make an initrd when lvm support is 
compiled in the kernel



When raid and lvm are compiled as loadable kernel modules, this does
not happen.


Indeed it doesn't.
Running the command mkinitrd from the command line doesn't solve it either.


My make-kpkg command is:
make-kpkg --initrd --config=menuconfig --append-to-version
-16-i386-smp-$(hostname) --revision $(date +'%Y.%m.%d.%H.%M')
kernel_image


As Andreas suggested, if raid and lvm is compiled into the kernel and if 
those are the only reasons you want an initrd (because you've got raid & 
lvm on your systel), try it without then.


Regards,
Benedict

--
Benedict Verheyen   Debian User
http://www.heimdallitservices.bePublic Key 0x712CBB8D


--
To UNSUBSCRIBE, email to [EMAIL PROTECTED] 
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]




Re: Installing custom kernel-image fails on LVM error - I'm lost :/

2005-06-22 Thread Andreas Janssen
Hello

Mart Frauenlob (<[EMAIL PROTECTED]>) wrote:

> What i'm trying to do:
> Install a custom kernel-image build with debian kernel-source and
> make-dpkg. I try to trimm down the kernel to hold only what is
> absolutely necessary. Also i try to compile directly into the kernel
> whatever i think of useful (performance).
> 
> When i set in menuconfig to compile RAID and LVM support directly into
> the kernel, the 'dpkg -i' process ends with the following error
> message:
> 
> [...]
> (2005.06.22.00.00) ... File descriptor 3 left open File descriptor 4
> left open File descriptor 5 left open
> File descriptor 6 left open
> File descriptor 7 left open
>  Finding all volume groups
>  Finding volume group "vg0"
> /usr/sbin/mkinitrd: /dev/mapper/vg0-lv_swap: Kernel does not support
> LVM Failed to create initrd image.
> 
> When raid and lvm are compiled as loadable kernel modules, this does
> not happen.
> 
> My make-kpkg command is:
> make-kpkg --initrd --config=menuconfig --append-to-version
> -16-i386-smp-$(hostname) --revision $(date +'%Y.%m.%d.%H.%M')
> kernel_image

If you compile all of the drivers you need to boot (RAID/LVM, root file
system, hard disk, disk controller) into the kernel, you do not need
the initrd. Did you try to run make-kpkg without --initrd?

best regards
Andreas Janssen

-- 
Andreas Janssen <[EMAIL PROTECTED]>
PGP-Key-ID: 0xDC801674 ICQ #17079270
Registered Linux User #267976
http://www.andreas-janssen.de/debian-tipps-sarge.html


-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED] 
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]



Installing custom kernel-image fails on LVM error - I'm lost :/

2005-06-21 Thread Mart Frauenlob

Hello,

I'm really stuck on this problem. I already spent 1,5 days on it :/

What i'm trying to do:
Install a custom kernel-image build with debian kernel-source and make-dpkg.
I try to trimm down the kernel to hold only what is absolutely 
necessary. Also i try to compile directly into the kernel whatever i 
think of useful (performance).


When i set in menuconfig to compile RAID and LVM support directly into 
the kernel, the 'dpkg -i' process ends with the following error message:



dpkg -i ../kernel-image-2.6.8-16-i386-smp-hostname_2005.06.22.00.00_i386.deb
Selecting previously deselected package 
kernel-image-2.6.8-16-i386-smp-hostname.

(Reading database ... 18598 files and directories currently installed.)
Unpacking kernel-image-2.6.8-16-i386-smp-hostname (from 
.../kernel-image-2.6.8-16-i386-smp-hostname_2005.06.22.00.00_i386.deb) ...

Setting up kernel-image-2.6.8-16-i386-smp-hostname (2005.06.22.00.00) ...
File descriptor 3 left open
File descriptor 4 left open
File descriptor 5 left open
File descriptor 6 left open
File descriptor 7 left open
Finding all volume groups
Finding volume group "vg0"
/usr/sbin/mkinitrd: /dev/mapper/vg0-lv_swap: Kernel does not support LVM
Failed to create initrd image.
dpkg: error processing kernel-image-2.6.8-16-i386-smp-hostname (--install):
 subprocess post-installation script returned error exit status 9
Errors were encountered while processing:
 kernel-image-2.6.8-16-i386-smp-hostname


When raid and lvm are compiled as loadable kernel modules, this does not 
happen.


My make-kpkg command is:
make-kpkg --initrd --config=menuconfig --append-to-version 
-16-i386-smp-$(hostname) --revision $(date +'%Y.%m.%d.%H.%M') kernel_image


As this error occured the first time i tried to build the kernel-image 
with everything set as i thought to be cool, i started building the 
package step by step, reducing the amount of used components at each 
step (has been 8 compiles now, which take an average time of 2 hours).
I did this until i got all set ok for me, only the raid and lvm still 
set as LKMs. This package works quite well from what i can tell.
BUT as soon i set lvm and raid to be compiled into the kernel, the 
installation of the kernel-image fails ://


I wonder why it seems to fails on the swap volume?
From my point of view all seems to be working.
System is already running with raid1 and lvm (created on debian setup).
I have lvm2 installed.

You can find information about my setup below.
I also attached the failing kernel .config.
If i missed anything relevant, please tell me so.

Please, i'm really lost here. Any help is greatly appreciated!

Best regards,

Mart

-

uname -r
2.6.8-2-686-smp
-

mdadm -Q -D /dev/md0
/dev/md0:
Version : 00.90.01
  Creation Time : Mon Jun 20 14:12:52 2005
 Raid Level : raid1
 Array Size : 4787264 (4.57 GiB 4.90 GB)
Device Size : 4787264 (4.57 GiB 4.90 GB)
   Raid Devices : 2
  Total Devices : 2
Preferred Minor : 0
Persistence : Superblock is persistent

Update Time : Wed Jun 22 01:31:28 2005
  State : clean
 Active Devices : 2
Working Devices : 2
 Failed Devices : 0
  Spare Devices : 0

   UUID : f591f311:dcc674f0:84679fa6:d17d7726
 Events : 0.51488

Number   Major   Minor   RaidDevice State
   0   310  active sync   /dev/hda1
   1  2211  active sync   /dev/hdc1
-

mdadm -Q -D /dev/md1
/dev/md1:
Version : 00.90.01
  Creation Time : Mon Jun 20 14:13:52 2005
 Raid Level : raid1
 Array Size : 11719296 (11.18 GiB 12.00 GB)
Device Size : 11719296 (11.18 GiB 12.00 GB)
   Raid Devices : 2
  Total Devices : 2
Preferred Minor : 1
Persistence : Superblock is persistent

Update Time : Wed Jun 22 01:32:08 2005
  State : clean
 Active Devices : 2
Working Devices : 2
 Failed Devices : 0
  Spare Devices : 0

   UUID : 04a24be0:3a9428ee:06e3315c:458ce791
 Events : 0.36616

Number   Major   Minor   RaidDevice State
   0   350  active sync   /dev/hda5
   1  2251  active sync   /dev/hdc5


pvs
  PV VG   Fmt  Attr PSize  PFree
  /dev/md1   vg0  lvm2 a-   11.18G 4.19G
-

pvdisplay
  --- Physical volume ---
  PV Name   /dev/md1
  VG Name   vg0
  PV Size   11.18 GB / not usable 0
  Allocatable   yes
  PE Size (KByte)   4096
  Total PE  2861
  Free PE   1072
  Allocated PE  1789
  PV UUID   rW7bHs-tkX9-OATv-H01Q-h0eO-2lBt-8