title: “LVM Verschlüsselte Partition kopieren”
date: 2018-10-15T09:07:14
slug: lvm-verschlusselte-partition-kopieren

Verschlüsselte Partition öffnen und neue Partition anlegen

sudo cryptsetup luksOpen /dev/sdc5 crypt
sudo vgcreate crypt-lvm /dev/mapper/crypt
sudo lvcreate -l100%FREE -nroot crypt-lvm

mount: unknown filesystem type LVM2_member

9 December, 2016

So I’m planning on making a series, “mount: unknown file-system type $TYPE”. I already have how to mount a ntfs partition, also how to mount a nfs on proxmox, now to be continued by another fun file-system. I was going through old disks, so I came across one that had LVM2_member.

• root@svennd:~# mount /dev/sdd2 /mnt/disk

• mount: unknown filesystem type ‘LVM2_member’

The fdisk -l already told me its a LVM :

• root@svennd:~# fdisk -l /dev/sdd

• Disk /dev/sdd: 233.8 GiB, 251000193024 bytes, 490234752 sectors

• Units: sectors of 1 * 512 = 512 bytes

• Sector size (logical/physical): 512 bytes / 512 bytes

• I/O size (minimum/optimal): 512 bytes / 512 bytes

• Disklabel type: dos

• Disk identifier: 0x0009345d

• Device Boot Start End Sectors Size Id Type

• /dev/sdd1 * 63 208844 208782 102M 83 Linux

• /dev/sdd2 208845 488247479 488038635 232.7G 8e Linux LVM

*(/dev/sdi1 is /boot partition, /dev/sdi2 is where the /home data resides)
*

Seems lvm2 tools also provide a way to check if its lvm or not, using lvmdiskscan(/dev/sdd2 here)

• root@svennd:~# lvmdiskscan

• /dev/sdb1 [ 1.82 TiB]

• /dev/sdc2 [ 149.04 GiB]

• /dev/sdd1 [ 101.94 MiB]

• /dev/sdd2 [ 232.71 GiB] LVM physical volume

• 0 disks

• 4 partitions

• 0 LVM physical volume whole disks

• 1 LVM physical volume

Fine, now lets scan what lv’s are to be found using lvscan

• root@svennd:~# lvscan

• inactive ‘/dev/VolGroup00/LogVol00’ [230.75 GiB] inherit

• inactive ‘/dev/VolGroup00/LogVol01’ [1.94 GiB] inherit

Since this is a old disk in an enclosure, its not activated on system boot. So we need to “activate” this lvm volume.

• root@svennd:~# vgchange -ay

• 2 logical volume(s) in volume group “VolGroup00” now active

and bam, ready to mount :

• root@svennd:~# lvscan

• ACTIVE ‘/dev/VolGroup00/LogVol00’ [230.75 GiB] inherit

• ACTIVE ‘/dev/VolGroup00/LogVol01’ [1.94 GiB] inherit

now to mount :

• mount /dev/VolGroup00/LogVol00 /mnt/disk

succes !

title: “ssh gateway”
date: 2018-04-17T09:19:35
slug: ssh-gateway

cat .ssh/config

Other stuff you’d like goes here

Host muc-deploy
ForwardAgent yes

Host *.ampua.server.lan
ControlMaster auto
ControlPath ~/.ssh/connections/%r_%h_%p
ControlPersist yes
ProxyCommand none
PasswordAuthentication Yes

Uncomment this in case you want to use sshgw by dc

Host *-bs*

ProxyCommand /usr/bin/ssh ampua-bs-sshgw.ampua.server.lan %h

Host *-ba*

ProxyCommand /usr/bin/ssh ampua-bap-sshgw.ampua.server.lan %h

Host *-lx*

ProxyCommand /usr/bin/ssh ampua-lxa-sshgw.ampua.server.lan %h

Exceptions which do not pass the sshgw (e.g. git, jenkins)

You need to pass User and ProxyCommand none

Host github0*.server.lan github.com git.mamdev.server.lan puppet-repo*
User git
ProxyCommand none
Host ndcli.server.lan 46.165.253.99 35.156.56.25 46.165.253.133 dev.asanger.biz hsp-gmx-pre01.server.lan *cinetic.de logservice* unitix-repo01* reposrv-deb* lxjumper* osum-home-master *.united.domain
User tasanger
ProxyCommand none
Host *
User juxxpd
ProxyCommand /usr/bin/ssh ampua-bs-sshgw.ampua.server.lan %h

title: “Glusterfs single server”
date: 2018-03-23T13:54:23
slug: glusterfs-single-server

mkdir /data
apt-get install glusterfs-server
gluster volume create k8s_prometheus vmd25840.contaboserver.net:/data/k8s_prometheus force
gluster volume start k8s_prometheus

title: “Maus im VI abschalten”
date: 2018-02-09T10:23:08
slug: maus-im-vi-abschalten

echo "set mouse-=a" > ~/.vimrc

title: “UTF-8 Terminal charset”
date: 2017-01-25T19:47:41
slug: utf-8-terminal-charset

dpkg-reconfigure locales

vi ~/.bashrc

export LC\_ALL=en\_US.UTF-8
export LANG=en\_US.UTF-8
export LANGUAGE=en\_US.UTF-8

Sofort übernehmen

source ~/.bashrc