Re: [gentoo-user] LVM not accessible after reboot
Hi Paul, i added the rootdelay to kernelcmdline and after reboot machine lvm was fine and all Partitions mounted. I will See If this works next reboots too. Thanks for the tipp Am 10. August 2015 22:52:57 MESZ, schrieb Paul Tobias tobias@gmail.com: my ideas is that LVM2 is not ready at the time of mounting partitions. how can i do this? I had the same problem on a system where scsi initialization was very slow. Adding rootdelay=30 to the kernel command line fixed it. The 30 is how many seconds should the kernel wait before it starts mounting filesystems. There was an scsi-wait-scan module too, but I think that was removed from recent kernels. Maybe this is not the same problem you have, probably it's quite rare to have a slowly initializing disk subsystem. -- Diese Nachricht wurde von meinem Android-Mobiltelefon mit K-9 Mail gesendet.
[gentoo-user] LVM not accessible after reboot
hello list, Using grub2 i have gentoo box where i did a raid5 on 4 disks. On the raid i created a lvm partition and created some logical volumes. All is going fine. But when rebooting the machine sometimes the lvm is not available and the logic volumes did not get mounted. I have to reboot the machine several times since the partitions are mounted after reboot. In /etc/default/grub i set: GRUB_PRELOAD_MODULES=lvm xfs mdraid09 mdraid1x so it should work after reboot. Any ideas why i have to reboot the machine sometimes multiple to access my logical volumes again? my ideas is that LVM2 is not ready at the time of mounting partitions. how can i do this? thanks marko
Re: [gentoo-user] LVM logical volumes dont mount with kernel 4.1.1?
Am , schrieb Neil Bothwick: On Fri, 03 Jul 2015 12:31:35 +0200, Marko Weber | 8000 wrote: Have you tried diffing the configs for the two kernels to look for potentially relevant differences? i always use the same config. (make oldconfig) so, theres no big diff between the configs. It only takes a small change, look at every difference. i'll try with fresh package. and tell you the results.
Re: [gentoo-user] LVM logical volumes dont mount with kernel 4.1.1?
hi neil, Am , schrieb Neil Bothwick: On Thu, 02 Jul 2015 18:53:10 +0200, Marko Weber | 8000 wrote: i am on kernel 4.0.6 and all my logical volumes mount fine after reboot. when i reboot with kernel 4.1.1 they dont mount. Any ideas what is causing this? Can you mount them manually after booting? Do you use an initrd? Have you tried diffing the configs for the two kernels to look for potentially relevant differences? i always use the same config. (make oldconfig) so, theres no big diff between the configs. Stepped back to 4.0.6 after reboot all is fine. On Kernel 4.1.1 pvdisplay vgdisplay show nothing. I can retry that if you want. marko
[gentoo-user] LVM logical volumes dont mount with kernel 4.1.1?
hello, i am on kernel 4.0.6 and all my logical volumes mount fine after reboot. when i reboot with kernel 4.1.1 they dont mount. Any ideas what is causing this? Marko -- zbfmail - Mittendrin statt nur Datei!
[gentoo-user] After Updates System hang on system waits for uevents to be processed
i found 2 mails here in list, but they talk about other problems there. (nvidia cards etc). any ideas how to solve this? server starts up after reboot, then it hangs on waiting for uevents to be prcocessed. DEVTMPFS is set YES in Kernel. i have no idea why it hangs there. i need some help from you guys. thanks ,marko -- zbfmail - Mittendrin statt nur Datei! OpenDKIM, SPF, DSPAM, Greylisting, POSTSCREEN, AMAVIS, Mailgateways Mailfiltering, SMTP Service, Spam Abwehr, MX-Backup, Mailserver Backup Redundante Mailgateways, HA Mailserver, Secure Mailserver
Re: [gentoo-user] cryptsetup wont use aes-xts:plain64
Finally! Am 2015-04-18 12:27, schrieb Marko Weber | 8000: hello list, i try to crypt a partition with cryptsetup. Yes, in Kernel i had all need things i think. CONFIG_CRYPTO=y CONFIG_CRYPTO_ALGAPI=y CONFIG_CRYPTO_ALGAPI2=y CONFIG_CRYPTO_AEAD=m CONFIG_CRYPTO_AEAD2=y CONFIG_CRYPTO_BLKCIPHER=y CONFIG_CRYPTO_BLKCIPHER2=y CONFIG_CRYPTO_HASH=y CONFIG_CRYPTO_HASH2=y CONFIG_CRYPTO_RNG=m CONFIG_CRYPTO_RNG2=y CONFIG_CRYPTO_PCOMP=m CONFIG_CRYPTO_PCOMP2=y CONFIG_CRYPTO_MANAGER=y CONFIG_CRYPTO_MANAGER2=y CONFIG_CRYPTO_USER=m # CONFIG_CRYPTO_MANAGER_DISABLE_TESTS is not set CONFIG_CRYPTO_GF128MUL=m CONFIG_CRYPTO_NULL=m CONFIG_CRYPTO_PCRYPT=m CONFIG_CRYPTO_WORKQUEUE=y CONFIG_CRYPTO_CRYPTD=m CONFIG_CRYPTO_MCRYPTD=m CONFIG_CRYPTO_AUTHENC=m CONFIG_CRYPTO_TEST=m CONFIG_CRYPTO_ABLK_HELPER=m CONFIG_CRYPTO_GLUE_HELPER_X86=m CONFIG_CRYPTO_CCM=m CONFIG_CRYPTO_GCM=m CONFIG_CRYPTO_SEQIV=m CONFIG_CRYPTO_CBC=y CONFIG_CRYPTO_CTR=m CONFIG_CRYPTO_CTS=m CONFIG_CRYPTO_ECB=m CONFIG_CRYPTO_LRW=m CONFIG_CRYPTO_PCBC=m CONFIG_CRYPTO_XTS=m CONFIG_CRYPTO_CMAC=m CONFIG_CRYPTO_HMAC=m CONFIG_CRYPTO_XCBC=m CONFIG_CRYPTO_VMAC=m CONFIG_CRYPTO_CRC32C=y CONFIG_CRYPTO_CRC32C_INTEL=m CONFIG_CRYPTO_CRC32=m CONFIG_CRYPTO_CRC32_PCLMUL=m CONFIG_CRYPTO_CRCT10DIF=y CONFIG_CRYPTO_CRCT10DIF_PCLMUL=m CONFIG_CRYPTO_GHASH=m CONFIG_CRYPTO_MD4=m CONFIG_CRYPTO_MD5=y CONFIG_CRYPTO_MICHAEL_MIC=m CONFIG_CRYPTO_RMD128=m CONFIG_CRYPTO_RMD160=m CONFIG_CRYPTO_RMD256=m CONFIG_CRYPTO_RMD320=m CONFIG_CRYPTO_SHA1=m CONFIG_CRYPTO_SHA1_SSSE3=m CONFIG_CRYPTO_SHA256_SSSE3=m CONFIG_CRYPTO_SHA512_SSSE3=m CONFIG_CRYPTO_SHA1_MB=m CONFIG_CRYPTO_SHA256=m CONFIG_CRYPTO_SHA512=m CONFIG_CRYPTO_TGR192=m CONFIG_CRYPTO_WP512=m CONFIG_CRYPTO_GHASH_CLMUL_NI_INTEL=m CONFIG_CRYPTO_AES=y CONFIG_CRYPTO_AES_X86_64=m CONFIG_CRYPTO_AES_NI_INTEL=m CONFIG_CRYPTO_ANUBIS=m CONFIG_CRYPTO_ARC4=m CONFIG_CRYPTO_BLOWFISH=m CONFIG_CRYPTO_BLOWFISH_COMMON=m CONFIG_CRYPTO_BLOWFISH_X86_64=m CONFIG_CRYPTO_CAMELLIA=m CONFIG_CRYPTO_CAMELLIA_X86_64=m CONFIG_CRYPTO_CAMELLIA_AESNI_AVX_X86_64=m CONFIG_CRYPTO_CAMELLIA_AESNI_AVX2_X86_64=m CONFIG_CRYPTO_CAST_COMMON=m CONFIG_CRYPTO_CAST5=m CONFIG_CRYPTO_CAST5_AVX_X86_64=m CONFIG_CRYPTO_CAST6=m CONFIG_CRYPTO_CAST6_AVX_X86_64=m CONFIG_CRYPTO_DES=m CONFIG_CRYPTO_DES3_EDE_X86_64=m CONFIG_CRYPTO_FCRYPT=m CONFIG_CRYPTO_KHAZAD=m CONFIG_CRYPTO_SALSA20=m CONFIG_CRYPTO_SALSA20_X86_64=m CONFIG_CRYPTO_SEED=m CONFIG_CRYPTO_SERPENT=m CONFIG_CRYPTO_SERPENT_SSE2_X86_64=m CONFIG_CRYPTO_SERPENT_AVX_X86_64=m CONFIG_CRYPTO_SERPENT_AVX2_X86_64=m CONFIG_CRYPTO_TEA=m CONFIG_CRYPTO_TWOFISH=m CONFIG_CRYPTO_TWOFISH_COMMON=m CONFIG_CRYPTO_TWOFISH_X86_64=m CONFIG_CRYPTO_TWOFISH_X86_64_3WAY=m CONFIG_CRYPTO_TWOFISH_AVX_X86_64=m CONFIG_CRYPTO_DEFLATE=m CONFIG_CRYPTO_ZLIB=m CONFIG_CRYPTO_LZO=m CONFIG_CRYPTO_LZ4=m CONFIG_CRYPTO_LZ4HC=m CONFIG_CRYPTO_ANSI_CPRNG=m CONFIG_CRYPTO_DRBG_MENU=m CONFIG_CRYPTO_DRBG_HMAC=y # CONFIG_CRYPTO_DRBG_HASH is not set # CONFIG_CRYPTO_DRBG_CTR is not set CONFIG_CRYPTO_DRBG=m CONFIG_CRYPTO_USER_API=m CONFIG_CRYPTO_USER_API_HASH=m CONFIG_CRYPTO_USER_API_SKCIPHER=m CONFIG_CRYPTO_HASH_INFO=y # CONFIG_CRYPTO_HW is not set but when i try to use cryptsetup i get this: # cryptsetup -c aes-xts:plain64 -y -s 256 luksFormat /dev/mapper/VolGroup01-media2 WARNING! This will overwrite data on /dev/mapper/VolGroup01-media2 irrevocably. Are you sure? (Type uppercase yes): YES Enter passphrase: Verify passphrase: device-mapper: reload ioctl on failed: Invalid argument Failed to setup dm-crypt key mapping for device /dev/mapper/VolGroup01-media2. Check that kernel supports aes-xts:plain64 cipher (check syslog for more info). Any ideas? i built cryptsetup with this useflags: nls openssl python udev urandom cryptsetup --help shows me i am able to use the options Default compiled-in device cipher parameters: loop-AES: aes, Key 256 bits plain: aes-cbc-essiv:sha256, Key: 256 bits, Password hashing: ripemd160 LUKS1: aes-xts-plain64, Key: 256 bits, LUKS header hashing: sha1, RNG: /dev/random any help / ideas or knowledge welcome. best regards marko i got it working! cryptsetup -c aes-xts-plain -h sha256 -y -s 256 luksFormat /dev/mapper/VolGroup01-media2 But on writing a testfile of 4G with i get 22,9 Mb/sec. Is there a cipher/hash/keysize which alloows me a bit more write performance? marko
Re: [gentoo-user] cryptsetup wont use aes-xts:plain64
hi Heiko, Am 2015-04-18 17:41, schrieb Heiko Baums: Am 18.04.2015 um 12:27 schrieb Marko Weber | 8000: i try to crypt a partition with cryptsetup. Yes, in Kernel i had all need things i think. Sorry, but I forgot some more kernel modules you need: CONFIG_BLK_DEV_DM=y CONFIG_DM_CRYPT=y You didn't mention them, so I don't know if you have them already built into your kernel. i have them in config. with y marko
Re: [gentoo-user] cryptsetup wont use aes-xts:plain64
hi fernando, Am 2015-04-19 03:35, schrieb Fernando Rodriguez: On Saturday, April 18, 2015 12:27:15 PM Marko Weber | 8000 wrote: hello list, i try to crypt a partition with cryptsetup. Yes, in Kernel i had all need things i think. CONFIG_CRYPTO=y CONFIG_CRYPTO_ALGAPI=y CONFIG_CRYPTO_ALGAPI2=y CONFIG_CRYPTO_AEAD=m CONFIG_CRYPTO_AEAD2=y CONFIG_CRYPTO_BLKCIPHER=y CONFIG_CRYPTO_BLKCIPHER2=y CONFIG_CRYPTO_HASH=y CONFIG_CRYPTO_HASH2=y CONFIG_CRYPTO_RNG=m CONFIG_CRYPTO_RNG2=y CONFIG_CRYPTO_PCOMP=m CONFIG_CRYPTO_PCOMP2=y CONFIG_CRYPTO_MANAGER=y CONFIG_CRYPTO_MANAGER2=y CONFIG_CRYPTO_USER=m # CONFIG_CRYPTO_MANAGER_DISABLE_TESTS is not set CONFIG_CRYPTO_GF128MUL=m CONFIG_CRYPTO_NULL=m CONFIG_CRYPTO_PCRYPT=m CONFIG_CRYPTO_WORKQUEUE=y CONFIG_CRYPTO_CRYPTD=m CONFIG_CRYPTO_MCRYPTD=m CONFIG_CRYPTO_AUTHENC=m CONFIG_CRYPTO_TEST=m CONFIG_CRYPTO_ABLK_HELPER=m CONFIG_CRYPTO_GLUE_HELPER_X86=m CONFIG_CRYPTO_CCM=m CONFIG_CRYPTO_GCM=m CONFIG_CRYPTO_SEQIV=m CONFIG_CRYPTO_CBC=y CONFIG_CRYPTO_CTR=m CONFIG_CRYPTO_CTS=m CONFIG_CRYPTO_ECB=m CONFIG_CRYPTO_LRW=m CONFIG_CRYPTO_PCBC=m CONFIG_CRYPTO_XTS=m CONFIG_CRYPTO_CMAC=m CONFIG_CRYPTO_HMAC=m CONFIG_CRYPTO_XCBC=m CONFIG_CRYPTO_VMAC=m CONFIG_CRYPTO_CRC32C=y CONFIG_CRYPTO_CRC32C_INTEL=m CONFIG_CRYPTO_CRC32=m CONFIG_CRYPTO_CRC32_PCLMUL=m CONFIG_CRYPTO_CRCT10DIF=y CONFIG_CRYPTO_CRCT10DIF_PCLMUL=m CONFIG_CRYPTO_GHASH=m CONFIG_CRYPTO_MD4=m CONFIG_CRYPTO_MD5=y CONFIG_CRYPTO_MICHAEL_MIC=m CONFIG_CRYPTO_RMD128=m CONFIG_CRYPTO_RMD160=m CONFIG_CRYPTO_RMD256=m CONFIG_CRYPTO_RMD320=m CONFIG_CRYPTO_SHA1=m CONFIG_CRYPTO_SHA1_SSSE3=m CONFIG_CRYPTO_SHA256_SSSE3=m CONFIG_CRYPTO_SHA512_SSSE3=m CONFIG_CRYPTO_SHA1_MB=m CONFIG_CRYPTO_SHA256=m CONFIG_CRYPTO_SHA512=m CONFIG_CRYPTO_TGR192=m CONFIG_CRYPTO_WP512=m CONFIG_CRYPTO_GHASH_CLMUL_NI_INTEL=m CONFIG_CRYPTO_AES=y CONFIG_CRYPTO_AES_X86_64=m CONFIG_CRYPTO_AES_NI_INTEL=m CONFIG_CRYPTO_ANUBIS=m CONFIG_CRYPTO_ARC4=m CONFIG_CRYPTO_BLOWFISH=m CONFIG_CRYPTO_BLOWFISH_COMMON=m CONFIG_CRYPTO_BLOWFISH_X86_64=m CONFIG_CRYPTO_CAMELLIA=m CONFIG_CRYPTO_CAMELLIA_X86_64=m CONFIG_CRYPTO_CAMELLIA_AESNI_AVX_X86_64=m CONFIG_CRYPTO_CAMELLIA_AESNI_AVX2_X86_64=m CONFIG_CRYPTO_CAST_COMMON=m CONFIG_CRYPTO_CAST5=m CONFIG_CRYPTO_CAST5_AVX_X86_64=m CONFIG_CRYPTO_CAST6=m CONFIG_CRYPTO_CAST6_AVX_X86_64=m CONFIG_CRYPTO_DES=m CONFIG_CRYPTO_DES3_EDE_X86_64=m CONFIG_CRYPTO_FCRYPT=m CONFIG_CRYPTO_KHAZAD=m CONFIG_CRYPTO_SALSA20=m CONFIG_CRYPTO_SALSA20_X86_64=m CONFIG_CRYPTO_SEED=m CONFIG_CRYPTO_SERPENT=m CONFIG_CRYPTO_SERPENT_SSE2_X86_64=m CONFIG_CRYPTO_SERPENT_AVX_X86_64=m CONFIG_CRYPTO_SERPENT_AVX2_X86_64=m CONFIG_CRYPTO_TEA=m CONFIG_CRYPTO_TWOFISH=m CONFIG_CRYPTO_TWOFISH_COMMON=m CONFIG_CRYPTO_TWOFISH_X86_64=m CONFIG_CRYPTO_TWOFISH_X86_64_3WAY=m CONFIG_CRYPTO_TWOFISH_AVX_X86_64=m CONFIG_CRYPTO_DEFLATE=m CONFIG_CRYPTO_ZLIB=m CONFIG_CRYPTO_LZO=m CONFIG_CRYPTO_LZ4=m CONFIG_CRYPTO_LZ4HC=m CONFIG_CRYPTO_ANSI_CPRNG=m CONFIG_CRYPTO_DRBG_MENU=m CONFIG_CRYPTO_DRBG_HMAC=y # CONFIG_CRYPTO_DRBG_HASH is not set # CONFIG_CRYPTO_DRBG_CTR is not set CONFIG_CRYPTO_DRBG=m CONFIG_CRYPTO_USER_API=m CONFIG_CRYPTO_USER_API_HASH=m CONFIG_CRYPTO_USER_API_SKCIPHER=m CONFIG_CRYPTO_HASH_INFO=y # CONFIG_CRYPTO_HW is not set but when i try to use cryptsetup i get this: # cryptsetup -c aes-xts:plain64 -y -s 256 luksFormat /dev/mapper/VolGroup01-media2 WARNING! This will overwrite data on /dev/mapper/VolGroup01-media2 irrevocably. # cryptsetup -c aes-xts:plain64 -y -s 512 luksFormat /dev/mapper/VolGroup01-media2 WARNING! This will overwrite data on /dev/mapper/VolGroup01-media2 irrevocably. Are you sure? (Type uppercase yes): YES Enter passphrase: Verify passphrase: device-mapper: reload ioctl on failed: Invalid argument Failed to setup dm-crypt key mapping for device /dev/mapper/VolGroup01-media2. Check that kernel supports aes-xts:plain64 cipher (check syslog for more info). Are you sure? (Type uppercase yes): YES Enter passphrase: Verify passphrase: device-mapper: reload ioctl on failed: Invalid argument Failed to setup dm-crypt key mapping for device /dev/mapper/VolGroup01-media2. Check that kernel supports aes-xts:plain64 cipher (check syslog for more info). Any ideas? i built cryptsetup with this useflags: nls openssl python udev urandom cryptsetup --help shows me i am able to use the options Default compiled-in device cipher parameters: loop-AES: aes, Key 256 bits plain: aes-cbc-essiv:sha256, Key: 256 bits, Password hashing: ripemd160 LUKS1: aes-xts-plain64, Key: 256 bits, LUKS header hashing: sha1, RNG: /dev/random any help / ideas or knowledge welcome. best regards marko That message is incorrectly shown if something's wrong with the way you specified the cipher and key size. It threw me off for a while too. This is what I ended up using: cryptsetup -i 3 -c twofish-xts-essiv:sha256 -s 512 -h sha512 luksFormat file.img I don't remember where I was getting it wrong, I think I was using -s 256 but xts uses half the key
Re: [gentoo-user] cryptsetup wont use aes-xts:plain64
Am 2015-04-18 12:27, schrieb Marko Weber | 8000: hello list, i try to crypt a partition with cryptsetup. Yes, in Kernel i had all need things i think. CONFIG_CRYPTO=y CONFIG_CRYPTO_ALGAPI=y CONFIG_CRYPTO_ALGAPI2=y CONFIG_CRYPTO_AEAD=m CONFIG_CRYPTO_AEAD2=y CONFIG_CRYPTO_BLKCIPHER=y CONFIG_CRYPTO_BLKCIPHER2=y CONFIG_CRYPTO_HASH=y CONFIG_CRYPTO_HASH2=y CONFIG_CRYPTO_RNG=m CONFIG_CRYPTO_RNG2=y CONFIG_CRYPTO_PCOMP=m CONFIG_CRYPTO_PCOMP2=y CONFIG_CRYPTO_MANAGER=y CONFIG_CRYPTO_MANAGER2=y CONFIG_CRYPTO_USER=m # CONFIG_CRYPTO_MANAGER_DISABLE_TESTS is not set CONFIG_CRYPTO_GF128MUL=m CONFIG_CRYPTO_NULL=m CONFIG_CRYPTO_PCRYPT=m CONFIG_CRYPTO_WORKQUEUE=y CONFIG_CRYPTO_CRYPTD=m CONFIG_CRYPTO_MCRYP# cryptsetup -c aes-xts:plain64 -y -s 512 luksFormat /dev/mapper/VolGroup01-media2 WARNING! This will overwrite data on /dev/mapper/VolGroup01-media2 irrevocably. Are you sure? (Type uppercase yes): YES Enter passphrase: Verify passphrase: device-mapper: reload ioctl on failed: Invalid argument Failed to setup dm-crypt key mapping for device /dev/mapper/VolGroup01-media2. Check that kernel supports aes-xts:plain64 cipher (check syslog for more info).TD=m CONFIG_CRYPTO_AUTHENC=m CONFIG_CRYPTO_TEST=m CONFIG_CRYPTO_ABLK_HELPER=m CONFIG_CRYPTO_GLUE_HELPER_X86=m CONFIG_CRYPTO_CCM=m CONFIG_CRYPTO_GCM=m CONFIG_CRYPTO_SEQIV=m CONFIG_CRYPTO_CBC=y CONFIG_CRYPTO_CTR=m CONFIG_CRYPTO_CTS=m CONFIG_CRYPTO_ECB=m CONFIG_CRYPTO_LRW=m CONFIG_CRYPTO_PCBC=m CONFIG_CRYPTO_XTS=m CONFIG_CRYPTO_CMAC=m CONFIG_CRYPTO_HMAC=m CONFIG_CRYPTO_XCBC=m CONFIG_CRYPTO_VMAC=m CONFIG_CRYPTO_CRC32C=y CONFIG_CRYPTO_CRC32C_INTEL=m CONFIG_CRYPTO_CRC32=m CONFIG_CRYPTO_CRC32_PCLMUL=m CONFIG_CRYPTO_CRCT10DIF=y CONFIG_CRYPTO_CRCT10DIF_PCLMUL=m CONFIG_CRYPTO_GHASH=m CONFIG_CRYPTO_MD4=m CONFIG_CRYPTO_MD5=y CONFIG_CRYPTO_MICHAEL_MIC=m CONFIG_CRYPTO_RMD128=m CONFIG_CRYPTO_RMD160=m CONFIG_CRYPTO_RMD256=m CONFIG_CRYPTO_RMD320=m CONFIG_CRYPTO_SHA1=m CONFIG_CRYPTO_SHA1_SSSE3=m CONFIG_CRYPTO_SHA256_SSSE3=m CONFIG_CRYPTO_SHA512_SSSE3=m CONFIG_CRYPTO_SHA1_MB=m CONFIG_CRYPTO_SHA256=m CONFIG_CRYPTO_SHA512=m CONFIG_CRYPTO_TGR192=m CONFIG_CRYPTO_WP512=m CONFIG_CRYPTO_GHASH_CLMUL_NI_INTEL=m CONFIG_CRYPTO_AES=y CONFIG_CRYPTO_AES_X86_64=m CONFIG_CRYPTO_AES_NI_INTEL=m CONFIG_CRYPTO_ANUBIS=m CONFIG_CRYPTO_ARC4=m CONFIG_CRYPTO_BLOWFISH=m CONFIG_CRYPTO_BLOWFISH_COMMON=m CONFIG_CRYPTO_BLOWFISH_X86_64=m CONFIG_CRYPTO_CAMELLIA=m CONFIG_CRYPTO_CAMELLIA_X86_64=m CONFIG_CRYPTO_CAMELLIA_AESNI_AVX_X86_64=m CONFIG_CRYPTO_CAMELLIA_AESNI_AVX2_X86_64=m CONFIG_CRYPTO_CAST_COMMON=m CONFIG_CRYPTO_CAST5=m CONFIG_CRYPTO_CAST5_AVX_X86_64=m CONFIG_CRYPTO_CAST6=m CONFIG_CRYPTO_CAST6_AVX_X86_64=m CONFIG_CRYPTO_DES=m CONFIG_CRYPTO_DES3_EDE_X86_64=m CONFIG_CRYPTO_FCRYPT=m CONFIG_CRYPTO_KHAZAD=m CONFIG_CRYPTO_SALSA20=m CONFIG_CRYPTO_SALSA20_X86_64=m CONFIG_CRYPTO_SEED=m CONFIG_CRYPTO_SERPENT=m CONFIG_CRYPTO_SERPENT_SSE2_X86_64=m CONFIG_CRYPTO_SERPENT_AVX_X86_64=m CONFIG_CRYPTO_SERPENT_AVX2_X86_64=m CONFIG_CRYPTO_TEA=m CONFIG_CRYPTO_TWOFISH=m CONFIG_CRYPTO_TWOFISH_COMMON=m CONFIG_CRYPTO_TWOFISH_X86_64=m CONFIG_CRYPTO_TWOFISH_X86_64_3WAY=m CONFIG_CRYPTO_TWOFISH_AVX_X86_64=m CONFIG_CRYPTO_DEFLATE=m CONFIG_CRYPTO_ZLIB=m CONFIG_CRYPTO_LZO=m CONFIG_CRYPTO_LZ4=m CONFIG_CRYPTO_LZ4HC=m CONFIG_CRYPTO_ANSI_CPRNG=m CONFIG_CRYPTO_DRBG_MENU=m CONFIG_CRYPTO_DRBG_HMAC=y # CONFIG_CRYPTO_DRBG_HASH is not set # CONFIG_CRYPTO_DRBG_CTR is not set CONFIG_CRYPTO_DRBG=m CONFIG_CRYPTO_USER_API=m CONFIG_CRYPTO_USER_API_HASH=m CONFIG_CRYPTO_USER_API_SKCIPHER=m CONFIG_CRYPTO_HASH_INFO=y # CONFIG_CRYPTO_HW is not set but when i try to use cryptsetup i get this: # cryptsetup -c aes-xts:plain64 -y -s 256 luksFormat /dev/mapper/VolGroup01-media2 WARNING! This will overwrite data on /dev/mapper/VolGroup01-media2 irrevocably. Are you sure? (Type uppercase yes): YES Enter passphrase: Verify passphrase: device-mapper: reload ioctl on failed: Invalid argument Failed to setup dm-crypt key mapping for device /dev/mapper/VolGroup01-media2. Check that kernel supports aes-xts:plain64 cipher (check syslog for more info). Any ideas? i built cryptsetup with this useflags: nls openssl python udev urandom cryptsetup --help shows me i am able to use the options Default compiled-in device cipher parameters: loop-AES: aes, Key 256 bits plain: aes-cbc-essiv:sha256, Key: 256 bits, Password hashing: ripemd160 LUKS1: aes-xts-plain64, Key: 256 bits, LUKS header hashing: sha1, RNG: /dev/random any help / ideas or knowledge welcome. best regards marko # Ok, now i have built into Kernel. ALso CONFIG_BLK_DEV_DM_BUILTIN=y CONFIG_BLK_DEV_DM=y i set. Here is output of /proc/crypto = # cat /proc/crypto name : ghash driver : ghash-generic module : kernel priority : 100 refcnt : 1 selftest : passed type : shash blocksize: 16 digestsize : 16 name : stdrng driver : drbg_nopr_hmac_sha256 module : kernel priority : 107
[gentoo-user] cryptsetup wont use aes-xts:plain64
hello list, i try to crypt a partition with cryptsetup. Yes, in Kernel i had all need things i think. CONFIG_CRYPTO=y CONFIG_CRYPTO_ALGAPI=y CONFIG_CRYPTO_ALGAPI2=y CONFIG_CRYPTO_AEAD=m CONFIG_CRYPTO_AEAD2=y CONFIG_CRYPTO_BLKCIPHER=y CONFIG_CRYPTO_BLKCIPHER2=y CONFIG_CRYPTO_HASH=y CONFIG_CRYPTO_HASH2=y CONFIG_CRYPTO_RNG=m CONFIG_CRYPTO_RNG2=y CONFIG_CRYPTO_PCOMP=m CONFIG_CRYPTO_PCOMP2=y CONFIG_CRYPTO_MANAGER=y CONFIG_CRYPTO_MANAGER2=y CONFIG_CRYPTO_USER=m # CONFIG_CRYPTO_MANAGER_DISABLE_TESTS is not set CONFIG_CRYPTO_GF128MUL=m CONFIG_CRYPTO_NULL=m CONFIG_CRYPTO_PCRYPT=m CONFIG_CRYPTO_WORKQUEUE=y CONFIG_CRYPTO_CRYPTD=m CONFIG_CRYPTO_MCRYPTD=m CONFIG_CRYPTO_AUTHENC=m CONFIG_CRYPTO_TEST=m CONFIG_CRYPTO_ABLK_HELPER=m CONFIG_CRYPTO_GLUE_HELPER_X86=m CONFIG_CRYPTO_CCM=m CONFIG_CRYPTO_GCM=m CONFIG_CRYPTO_SEQIV=m CONFIG_CRYPTO_CBC=y CONFIG_CRYPTO_CTR=m CONFIG_CRYPTO_CTS=m CONFIG_CRYPTO_ECB=m CONFIG_CRYPTO_LRW=m CONFIG_CRYPTO_PCBC=m CONFIG_CRYPTO_XTS=m CONFIG_CRYPTO_CMAC=m CONFIG_CRYPTO_HMAC=m CONFIG_CRYPTO_XCBC=m CONFIG_CRYPTO_VMAC=m CONFIG_CRYPTO_CRC32C=y CONFIG_CRYPTO_CRC32C_INTEL=m CONFIG_CRYPTO_CRC32=m CONFIG_CRYPTO_CRC32_PCLMUL=m CONFIG_CRYPTO_CRCT10DIF=y CONFIG_CRYPTO_CRCT10DIF_PCLMUL=m CONFIG_CRYPTO_GHASH=m CONFIG_CRYPTO_MD4=m CONFIG_CRYPTO_MD5=y CONFIG_CRYPTO_MICHAEL_MIC=m CONFIG_CRYPTO_RMD128=m CONFIG_CRYPTO_RMD160=m CONFIG_CRYPTO_RMD256=m CONFIG_CRYPTO_RMD320=m CONFIG_CRYPTO_SHA1=m CONFIG_CRYPTO_SHA1_SSSE3=m CONFIG_CRYPTO_SHA256_SSSE3=m CONFIG_CRYPTO_SHA512_SSSE3=m CONFIG_CRYPTO_SHA1_MB=m CONFIG_CRYPTO_SHA256=m CONFIG_CRYPTO_SHA512=m CONFIG_CRYPTO_TGR192=m CONFIG_CRYPTO_WP512=m CONFIG_CRYPTO_GHASH_CLMUL_NI_INTEL=m CONFIG_CRYPTO_AES=y CONFIG_CRYPTO_AES_X86_64=m CONFIG_CRYPTO_AES_NI_INTEL=m CONFIG_CRYPTO_ANUBIS=m CONFIG_CRYPTO_ARC4=m CONFIG_CRYPTO_BLOWFISH=m CONFIG_CRYPTO_BLOWFISH_COMMON=m CONFIG_CRYPTO_BLOWFISH_X86_64=m CONFIG_CRYPTO_CAMELLIA=m CONFIG_CRYPTO_CAMELLIA_X86_64=m CONFIG_CRYPTO_CAMELLIA_AESNI_AVX_X86_64=m CONFIG_CRYPTO_CAMELLIA_AESNI_AVX2_X86_64=m CONFIG_CRYPTO_CAST_COMMON=m CONFIG_CRYPTO_CAST5=m CONFIG_CRYPTO_CAST5_AVX_X86_64=m CONFIG_CRYPTO_CAST6=m CONFIG_CRYPTO_CAST6_AVX_X86_64=m CONFIG_CRYPTO_DES=m CONFIG_CRYPTO_DES3_EDE_X86_64=m CONFIG_CRYPTO_FCRYPT=m CONFIG_CRYPTO_KHAZAD=m CONFIG_CRYPTO_SALSA20=m CONFIG_CRYPTO_SALSA20_X86_64=m CONFIG_CRYPTO_SEED=m CONFIG_CRYPTO_SERPENT=m CONFIG_CRYPTO_SERPENT_SSE2_X86_64=m CONFIG_CRYPTO_SERPENT_AVX_X86_64=m CONFIG_CRYPTO_SERPENT_AVX2_X86_64=m CONFIG_CRYPTO_TEA=m CONFIG_CRYPTO_TWOFISH=m CONFIG_CRYPTO_TWOFISH_COMMON=m CONFIG_CRYPTO_TWOFISH_X86_64=m CONFIG_CRYPTO_TWOFISH_X86_64_3WAY=m CONFIG_CRYPTO_TWOFISH_AVX_X86_64=m CONFIG_CRYPTO_DEFLATE=m CONFIG_CRYPTO_ZLIB=m CONFIG_CRYPTO_LZO=m CONFIG_CRYPTO_LZ4=m CONFIG_CRYPTO_LZ4HC=m CONFIG_CRYPTO_ANSI_CPRNG=m CONFIG_CRYPTO_DRBG_MENU=m CONFIG_CRYPTO_DRBG_HMAC=y # CONFIG_CRYPTO_DRBG_HASH is not set # CONFIG_CRYPTO_DRBG_CTR is not set CONFIG_CRYPTO_DRBG=m CONFIG_CRYPTO_USER_API=m CONFIG_CRYPTO_USER_API_HASH=m CONFIG_CRYPTO_USER_API_SKCIPHER=m CONFIG_CRYPTO_HASH_INFO=y # CONFIG_CRYPTO_HW is not set but when i try to use cryptsetup i get this: # cryptsetup -c aes-xts:plain64 -y -s 256 luksFormat /dev/mapper/VolGroup01-media2 WARNING! This will overwrite data on /dev/mapper/VolGroup01-media2 irrevocably. Are you sure? (Type uppercase yes): YES Enter passphrase: Verify passphrase: device-mapper: reload ioctl on failed: Invalid argument Failed to setup dm-crypt key mapping for device /dev/mapper/VolGroup01-media2. Check that kernel supports aes-xts:plain64 cipher (check syslog for more info). Any ideas? i built cryptsetup with this useflags: nls openssl python udev urandom cryptsetup --help shows me i am able to use the options Default compiled-in device cipher parameters: loop-AES: aes, Key 256 bits plain: aes-cbc-essiv:sha256, Key: 256 bits, Password hashing: ripemd160 LUKS1: aes-xts-plain64, Key: 256 bits, LUKS header hashing: sha1, RNG: /dev/random any help / ideas or knowledge welcome. best regards marko --
[gentoo-user] mysql upgrade 5.5 5.6 mysql_upgrade needed?
hello list, again i have to ask. Do i need to run mysql_upgrade after upgrading mysql 5.5 5.6 ? I ask because the post install text recommend this after an major upgrade. On the Mysql Website is a major upgrade 5.5 6.0, not 5.5 5.6 So i ask you guys. Any can help me? thank you marko
[gentoo-user] MySql Upgrade Question (Major Release)
Hi list, the dev-db/mysql will update from 5.5 to 5.6 At the end a post install text tells me i have to fire up mysql_upgrade when this is a major update. On the mysql site i found this 5.5.40 5.x.x is the major nr x.5.x is the release nr x.x.40 is the level of the release so, do i have to fire up mysql_upgrade on change from 5.5.40 5.6.40 at example. thank you marko -- zbfmail - Mittendrin statt nur Datei! OpenDKIM, SPF, DSPAM, Greylisting, POSTSCREEN, AMAVIS, Mailgateways Mailfiltering, SMTP Service, Spam Abwehr, MX-Backup, Mailserver Backup Redundante Mailgateways, HA Mailserver, Secure Mailserver
[gentoo-user] Problem with perl dependencies on emerge -uD world
Hi,
on one of my gentoo-servers i try to update the system with 'emerge -uD
world'.
i get the following output, and have no idea how to solve this
comnflicts.
Can anyone help me or guide me?
=
# emerge -uD world
* IMPORTANT: 10 news items need reading for repository 'gentoo'.
* Use eselect news to read news items.
Calculating dependencies... done!
[ebuild U ] virtual/libiconv-0-r2 [0-r1]
[ebuild U ] sys-devel/gnuconfig-20140728 [20140212]
[ebuild U ] app-admin/eselect-1.4.4 [1.4.3]
[ebuild U ] sys-apps/man-pages-3.79 [3.78]
[ebuild U ] dev-lang/perl-5.20.1-r4 [5.18.2-r2]
[ebuild U ] perl-core/File-Temp-0.230.400-r1 [0.230.0]
[ebuild U ] virtual/perl-File-Temp-0.230.400-r2 [0.230.0-r1]
[ebuild U ] virtual/perl-File-Spec-3.480.0 [3.400.0-r2]
[ebuild U ] virtual/perl-MIME-Base64-3.140.0-r1 [3.130.0-r4]
[ebuild U ] virtual/perl-CPAN-Meta-YAML-0.12.0 [0.8.0-r2]
[ebuild U ] virtual/perl-IO-1.310.0 [1.280.0-r1]
[ebuild U ] virtual/perl-Test-Simple-1.1.2 [0.980.0-r6]
[ebuild U ] virtual/perl-JSON-PP-2.272.30 [2.272.20-r1]
[ebuild U ] virtual/perl-version-0.990.900-r1 [0.990.200-r1]
[ebuild U ] virtual/perl-Scalar-List-Utils-1.380.0 [1.270.0-r2]
[ebuild U ] virtual/perl-Parse-CPAN-Meta-1.441.400 [1.440.400-r1]
[ebuild U ] virtual/perl-Compress-Raw-Zlib-2.65.0 [2.60.0-r2]
[ebuild U ] virtual/perl-IO-Compress-2.64.0 [2.60.0-r1]
[ebuild U ] virtual/perl-Test-Harness-3.330.0 [3.260.0-r2]
[ebuild U ] virtual/perl-Perl-OSType-1.7.0 [1.3.0-r1]
[ebuild U ] virtual/perl-CPAN-Meta-Requirements-2.125.0-r1
[2.122.0-r2]
[ebuild U ] virtual/perl-ExtUtils-MakeMaker-6.980.0 [6.660.0-r1]
[ebuild N ] virtual/perl-if-0.60.300
[ebuild U ] virtual/perl-Getopt-Long-2.420.0-r1 [2.390.0-r1]
[ebuild U ] virtual/perl-Digest-MD5-2.530.0-r2 [2.520.0-r2]
[ebuild U ] virtual/perl-Encode-2.600.0 [2.490.0-r2]
[ebuild N ] virtual/perl-Text-ParseWords-3.290.0-r1
[ebuild U ] virtual/perl-Module-Metadata-1.0.19 [1.0.11-r1]
[ebuild U ] virtual/perl-ExtUtils-ParseXS-3.240.0 [3.180.0-r2]
[ebuild N ] virtual/perl-ExtUtils-Manifest-1.630.0-r1
[ebuild N ] virtual/perl-ExtUtils-Install-1.670.0
[ebuild U ] virtual/perl-ExtUtils-CBuilder-0.280.217-r1
[0.280.210-r1]
[ebuild U ] virtual/perl-Archive-Tar-1.960.0 [1.900.0-r2]
[ebuild U ] virtual/perl-Storable-2.490.0 [2.410.0-r1]
[ebuild U ] virtual/perl-Sys-Syslog-0.330.0-r1 [0.320.0-r2]
[ebuild U ] virtual/perl-ExtUtils-Command-1.180.0-r2 [1.170.0-r6]
[ebuild U ] sys-kernel/linux-headers-3.18 [3.16]
[ebuild U ] virtual/perl-Time-HiRes-1.972.600-r1 [1.972.500-r3]
[ebuild U ] virtual/perl-Attribute-Handlers-0.960.0 [0.940.0-r1]
[ebuild U ] virtual/perl-CPAN-Meta-2.140.640 [2.120.921-r2]
[ebuild U ~] perl-core/CPAN-Meta-2.132.510-r1 [2.120.921-r1]
[ebuild U ] dev-python/setuptools-12.0.1 [7.0]
[ebuild U ] app-editors/nano-2.3.6 [2.3.2] USE=spell*
[ebuild U ] dev-db/mysql-5.6.22 [5.5.40] ABI_X86=(64%*) (-32)
(-x32)
[ebuild U ] virtual/mysql-5.6-r2 [5.5] ABI_X86=(64%*) (-32)
(-x32)
[ebuild U ] virtual/perl-Digest-SHA-5.880.0 [5.820.0]
[uninstall ] perl-core/Digest-SHA-5.820.0
[blocks b ] perl-core/Digest-SHA-5.880.0
(perl-core/Digest-SHA-5.880.0 is blocking
virtual/perl-Digest-SHA-5.880.0)
[ebuild U ] virtual/perl-IO-Socket-IP-0.290.0 [0.230.0]
[uninstall ] perl-core/IO-Socket-IP-0.230.0-r1
[blocks b ] perl-core/IO-Socket-IP-0.290.0
(perl-core/IO-Socket-IP-0.290.0 is blocking
virtual/perl-IO-Socket-IP-0.290.0)
[ebuild N ] perl-core/CGI-3.650.0 USE={-test}
[ebuild U ] virtual/perl-CGI-3.650.0-r1 [3.630.0-r2]
[blocks b ] perl-core/CGI-3.630.0-r999
(perl-core/CGI-3.630.0-r999 is blocking virtual/perl-CGI-3.630.0-r2)
[ebuild U ] perl-core/Module-Build-0.420.500 [0.400.300-r1]
[uninstall ] virtual/perl-Module-Build-0.400.300-r1
[blocks b ] perl-core/Module-Build-0.400.300-r999
(perl-core/Module-Build-0.400.300-r999 is blocking
virtual/perl-Module-Build-0.400.300-r1)
[blocks B ] perl-core/CPAN-Meta-2.140.640
(perl-core/CPAN-Meta-2.140.640 is blocking
virtual/perl-CPAN-Meta-2.140.640)
[blocks B ] perl-core/Module-Metadata-1.0.19
(perl-core/Module-Metadata-1.0.19 is blocking
virtual/perl-Module-Metadata-1.0.19)
!!! Multiple package instances within a single package slot have been
pulled
!!! into the dependency graph, resulting in a slot conflict:
dev-lang/perl:0
(dev-lang/perl-5.20.1-r4:0/5.20::gentoo, ebuild scheduled for merge)
pulled in by
=dev-lang/perl-5.20* required by
(virtual/perl-CPAN-Meta-Requirements-2.125.0-r1:0/0::gentoo, ebuild
scheduled for merge)
^ ^
(and 37 more with the same problem)
Re: [gentoo-user] Problem with perl dependencies on emerge -uD world
hi neil, Am 2015-03-10 21:05, schrieb Neil Bothwick: On Tue, 10 Mar 2015 17:07:32 +0100, Marko Weber | 8000 wrote: on one of my gentoo-servers i try to update the system with 'emerge -uD world'. i get the following output, and have no idea how to solve this comnflicts. Can anyone help me or guide me? = # emerge -uD world * IMPORTANT: 10 news items need reading for repository 'gentoo'. * Use eselect news to read news items. I'd start by reading these. Chances are one of them contains the answer to your problem. This is caused by the movement of some packages from perl-core into the main perl build. Make sure you have no perl-core packages in world. just want to say that your hint worked. i removed all perl-core packages and then 'emerge -pvuD world' worked again like a charm. marko
Re: [gentoo-user] Problem with perl dependencies on emerge -uD world
hi martin, Am 2015-03-10 19:03, schrieb Martin Jerabek: On 10.3.2015 17:07, Marko Weber | 8000 wrote: Hi, on one of my gentoo-servers i try to update the system with 'emerge -uD world'. i get the following output, and have no idea how to solve this comnflicts. Can anyone help me or guide me? = # emerge -uD world ... = thanks, marko `perl-cleaner --all` usually works for me perl-cleanner --reallyall wont work for me in that situation, cause the depencie problems are still present at this state.
Re: [gentoo-user] Re: world file - where has it gone?
Hi, tried 'regenworld' ? marko Am 2015-03-09 21:00, schrieb walt: On 01/04/2015 04:19 AM, Helmut Jarausch wrote: Hi, I discovered that the file /var/lib/portage/world contains only a few lines where it contained hundreds of files before. Same thing just happened to me two months later. Weird. I updated this machine early this morning but /var/lib/world is still dated yesterday afternoon, and contains only the packages I updated manually yesterday. Portage evidently had a major brainfart yesterday because I know I didn't edit the world file myself :/
