Red Hat :: /dev/mapper/device_name Missing For Luks?
Mar 31, 2011
I am using Centos 5.5. I have a luks partition that I can successfully open and mount manually. But the problem is upon boot up, the device is missing from /dev/mapper/device_name until I manually luksOpen it..then it appears as it has before. This makes it a problem for me to have it open and mounted automatically upon boot up. Why is the /dev/mapper/device_name missing untill I manually luksOpen it?
Slackware 13 Kernel 2.6.29.6 have three hard drives. Root is on own drive sda1. sdb and sdc are raid via mdadm with two partitions. one for /home raid0 md0 one for swap raid1 md1. md0 is encrypted vi cryptsetup. md1 is encrypted vi fstab. everything boots fine and is accessible. However, /dev/mapper/* shows sda1 as block device connected to the raid md0. swap crypted device is correct in /dev/mapper/*. fstab is set correctly. problem seems to be with initrd. I would like the correct device in /dev/mapper so that I can access drive info; size, available space, etc. now info shows only sda1 info
Dell PowerEdge R610 with QLogic HBA card connected to HP EVA6000 SAN through a pair of switches.When I present space to the server, device mapper doesn't see it unless I restart the multipathd service. Same thing with unpresenting - the /dev/mapper/mpatha does not go away unless I restart multipathd.Here's what it looks like in 'multipath -ll' before and after I unpresent the LUN (without restarting multipathd)...
== BEFORE == # multipath -ll mpathb (3600508b40010716b0000900001a40000) dm-8 HP,HSV200
I am using CentOS 5.2. I am installing from disc on a machine with Intel Embedded Server Raid Technology. It has two 500 GB SATA drives. During the initial boot process, it sees that these two devices exist. However, after getting into the screen to partition and configure RAID, it just shows this:
Drive /dev/mapper/ddf1_MegaSR R! #0 (475879 MB) (Model: Linux device-mapper)
I want to do a RAID1 so that the disks are mirrored. However, I would expect to see both drives listed. I can select RAID to create RAID partitions, but I think I need to be able to see both drives in order to do this correctly.
im facing problem in mailserver which gives me insufficient space error, when i see details it showAug 3 12:10:02 3dserver zimbramon[17013]: 17013:crit: Disk warning: 3dserver.3dbp.in /dev/mapper/ddf1_3draidp1 at 93%how can i set the frequency on mail threshold warning which is at 10 minutes.
Well as you can see from my sig I am running Slack 13 and unfortunately did not discover the readme_crypt.txt on the installation cd until it was far too late. Not to worry, many hours burned and things learned.So I compiled and installed cryptsetup and for my test encryption I am using an external usb harddrive (sdb3).First off cryptsetup kept segfaulting with the luksFormat command and this seems to be a know bug. The workaround it to pass USE="dynamic" to config before you build the package. Then
We had this problem a while back but it went away with whatever updates lvm/cryptsetup have been through, but it's back again as of the latest update. Instead of symlinks to the /dev/dm-* devices, lvm and cryptsetup are both creating duplicate device nodes under /dev/mapper for already existing devices.
e.g. Code: gazl@slack:~$ ls -l /dev/mapper total 0 crw------- 1 root root 10, 61 Jan 23 16:48 control brw-rw-r-- 1 root disk 253, 0 Jan 23 16:48 lukssda5 brw-rw-r-- 1 root disk 253, 9 Jan 23 16:48 rootvg-lvhome
I am trying to setup a H/W RAID-1 matrix but I am unsuccessful. I am trying to get partitions installed as /dev/md0, /dev/md1 but it keeps going for /dev/mapper/isw...The reason is that I have R1Soft backup and it needs to hook the partitions as seen in /proc/partitions from /dev not /dev/mapper/isw. I have tried to boot the installation with various options but nothing!
I am trying to prevent the dm_mod and friends from loading during install.I am installing by PXE boot with NFS and kickstart files over http. This works fine for other machines.Ok, I have a Dell PowerEdge 2900 III with 8gig ram, PERC 6/i raid controller.The raid has 8 1TB drives in it, so the total size of the device is >2TB.There is also an SATA drive, which is NOT on the raid controller.
The problem is, I want to install CentOS on the SATA drive. The SATA drive comes up as a device-mapper drive, with a big crazy device name.This is ok, but the problem is, when the system goes to boot, it just says 'missing operating system'.I can't boot from the raid because it is large enough to require a GPT partition, and CentOS says it can't boot from a GPT partition.The SATA drive would work FINE if I could just prevent the damn device mapper from loading, so that I could install on the SATA drive in ordinary SATA mode.
I have tried re-squashing the stage2.img with /etc/modprobe.conf with alias dm_mod off and such, no luck.I also tried adding an /etc/modprobe.d/blacklist file, that did not work either.I also tried putting blacklist= dm_mod in the kickstart file, but that seems to be a fedora-only option and it kills my install. any ideas on preventing the dm_mod et. al. from loading at install time??
Greetings Fellow Knights Of The Penguin Clan....!I am having issues with device mapper seeing a 275GB Raid5 Lun from my SAN storage.I'm using IBM 2145 San Volume Controller.I am able to see a 40 GB Raid 10 device though..
I have a linux machine, attached to a fibre channel SAN.
We're in the testing phases and we're attempting to get all of the bugs worked out before this goes live.
If i have my host streaming data to the storage device on the san (or from the device on the san) and simulate a path failure (by shutting down one of the host's ports on the FC switch), multipath does not pick up on another path until about 45 seconds have passed.
I can verify this by watching the statistic graph (which updates once per second) on the storage system.
I see iops running along rather nicely, and then they drop to 0 for 45 seconds, then pick right up to normal again.
This is a RehHat EL 5.5 system, with qlogic HBA's.
Am i being too picky? I'd expect multipath to recover in under 30 seconds, so as to not alarm host applications running on the linux host... 45 seconds seems like a long time to wait for a disk operation to complete.
Any tips on tuning Multipath, or the qlogic card? As it is, i've got the following options in my modprobe.conf.
I've encrypted the /home partition. I've been successful in doing this by following the instructions here:slackware64-current/README_CRYPT.TXTBut after upgrade to cryptsetup-1.2.0-x86_64, when I boot up I get 'no such file or directory while trying to open /dev/mapper/crypthome'I have to manually type 'cryptsetup luksOpen /dev/sda9 crypthome' and mount each time to get into the encrypted partition.I expect to be prompted for the password on boot but I just get that error, what is wrong?my config files:
Trying to do a yum update to get everything to latest, towards the end it says this:
[Code]...
how to get around this? I tried yum clean all, then yum update, again but it did the same. I had other deps missing on other servers but yum clean all fixed them -- can't find anyone else who's had this specific issue either, nor an rpm called 'device-mapper-event' or the other things that are missing - am kinda stuck!
I'm having some difficulities with truecrypt and cannot figure out what's wrong since this is my first attempt to create hidden encrypted partition. I'm using ubuntu 9.10 64b with latest 6.3a truecrypt. After using truecrypt gui (just command truecrypt) I've tried: create volume-->create volumne within a partition/drive-->hidden trucrypt volume --> select some /dev/sdX by my choice --> select aes & sha512 --> password --> and format it.
when formating finished message "wrong ss, swith or wrong superblock of /dev/loop0" appeared. I've got no idea what could I do with it neither know whats program trying to do! Ok formating's done, then if you're trying to mount that partition then I would expect prompt for password, but that did not happen ...
EDIT: sudo mount /dev/loop0 /media/tmp/ also complaint about wrong superblock, but that does not ring any bell since i've got no idea what /dev/loop0 is or is for...
Anyone know how device-mapper works, or can someone point me to any docco (other than the man page)?
Couple years ago I wrote a TrueCrypt wrapper script for use on Puppy Linux, and am reworking it for Ubuntu. Puppy sometimes didn't have the 'dmsetup' device-mapper utility available, but TrueCrypt still works without this when the '-m nokernelcrypto' option is used.
My script notices when dmsetup is available and skips this option. When the TC volume gets mounted (somehow using dmsetup), the Desktop icon is labled with the leaf name of the /media/mount_point -- so far, so good.
However, if I force the script to add the no-kernel-crypto option, and the TC volume is mounted without using dmsetup, the Desktop icon ls labled with the size of the volume. Say what?
Running df shows the difference between the two mounts is whether /dev/mapper is used. So *how is* dmsetup making this happen? The manpage isn't much help. Is it just the 'rename' sub-command? I am unable to find any details about this mechanism.
I installed NFS and portmap for export a folder to another PC. /usr/local. ftp is server's hostname and ws01 is client's hostname. I edited file /etc/exports with next text: /usr/local ws01(rw,root_squash) *(ro)
I restarted service portmap and nfs. From client, I try check connection with server with command: showmount -e ftp and result is: mount clntudp_create: RPC: Port mapper failure - RPC: Unable to receive
I run many 5.2 virtual machines inside of VMWare ESX3.5 I've updated a couple of test VMs from 5.2 to 5.3. The thing that stands out is that during boot time, the sequence gets to this stage:
device-mapper: dm-raid45: intialized v0.2429 Waiting for driver initialization.
Here it takes about 3 times longer than the previous Centos 5.2 (about 9 seconds instead of 3). Whereas inside a physical box the wait in 5.3 is the same as it was in 5.2
Today, I was trying to compile and install a minecraft mapper with the program "make". I navigated to the directory in terminal and ran make. It found the make file and begins to work, then spits an error and stops. To be specific, this was the error:
Code: cats4gold@computer:~/Downloads/cartograph-linux$ make make -C src/ make[1]: Entering directory `/home/cats4gold/Downloads/cartograph-linux/src' g++ -c -pipe -O2 -Wall main.cpp -o main.o In file included from main.cpp:16:
Recently, I created a device sc0 through device mapper. The divice could be found in /dev/mapper/sc0. My problem is that the device doesn't exist in /dev/partitions which will block my following test.BTW, I found dm-0 in /dev/partitions. Is it the same as /dev/mapper/sc0? But the device /dev/dm-0 doesn't exist!
A few months ago I have setup a server with three hard disks. The partition mapping the disks as follows:
Disk /dev/sda: 1000.2 GB, 1000204886016 bytes 255 heads, 63 sectors/track, 121601 cylinders Units = cylinders of 16065 * 512 = 8225280 bytes Disk identifier: 0x7ca36fee
[code]....
Now I have the following problem the LVM file system don't mount properly.If I open the mount point I see only a few files of the LVM disk. If I want to unmount the disk I get the following error:
umount /data/ umount: /data/: not mounted
If I want to mount the volume I get the following error:
mount -a mount: /dev/mapper/gegevens-Data already mounted or /data busy
I need to resize (increase) LUKS partition. I have found a lot of manuals, but they are just for LVM volumes(I dont use LVM and I dont plan to use it). I have HDD splited to the 4 parts:
sda1(/) sda2(LUKS) unalocated swap
I want to increase LUKS partition, by using the part of unalocated space.
BUT I dont want to do the following: Backup data from LUKS partition Delete LUKS partition Create new bigger LUKS partition Restore data to the LUKS partition
Is there any way to only have one passphrase prompt when using multiple LUKS partitions? Well there must be, as that's how Fedora does it - it asks you once, and tries that passphrase on every LUKS volume (with a nice plymouth prompt), I just don't know how to do that on Wheezy. Don't say I have to nuke my install and use LVM instead of regular partitions or put a keyfile on a USB stick. My partition layout is:
I am trying to decide whether or not to use LUKS with LVM install for NAS Box, mysql, postfix, ddns, bind, NFS, sshd, Appletalk, maybe samba. I have decided to give LVMs a try but not sure how LUKS will affect access to services. LAN includes Standalone headless web server(not on LVM, no LUKS). Aren't permissions,iptables and firewalls sufficient? Not sure how services are supose to interract if everything is encrypted especially root?
So far what I have read recommends vgOS /, swap, /var, /tmp encription and vgdata /home encryption but no one tells how they did it. The 2 servers I'm working on only have small /home for admin stuff and considering making NAS headless, except i read somewhere that some gui would make it easier to manage mysql which brings me to the question if I don't install X on NAS can I ssh in with my desktop using its gui? I am experimenting with minimal server tagfiles. LUKS and LVMs are new to me. Decided to use LVMs to seperate OS from data, different data types and resizing flexibility. I have read some material on LUKS just wonder if its more complicated than my needs require. Certainly i don't want to leave myself open to someone just distroying my setup for kicks.
first i make one partiton ten format it add mount point and fire luksopen command and create secert file and enter this in crypttab but when i rebbot it showes scert file not found and partion remain unlocked
I have recently installed CentOS 5.4. I went ahead and enabled encryption for the root partition. everything was fine for the first few days, but today it started refusing my password on boot. The weird thing is after refusing the password several times it accepted it once, then when I rebooted to test refused the password it had accepted moments earlier. I guessed the password file got corrupt or something so I did a clean install. During the install it asked for the password to access the partition and accepted (!) the password. I went ahead and deleted the old partition and reinstalled from scratch just to be sure. And I made extra certain I put in the correct password with no fumble fingers. Sure enough the blasted thing refuses the password I just created during boot. However, if I input the password into the setup it accepts it. What the hell is going on here?
1.) I am wondering how to enable the lock to an encrypted partition which has been unlocked, using luks? On boot, I am been asked automatically for the pass phrase to unlock my partitions. After doing a back up, I want lock the encrypted partition again, but I don't know the command?! I umounted the partition but after mounting it again, I was not asked for the pass phrase but had access to my data.
2.) How secure is the default fedora version of luks? Is truecrypt better?
I can't seem to get an encrypted partition to recognize a keyfile. It is a backup partition that I would like to keep unmounted until a cron-script runs once a week to backup my sensitive data. In order for the script to run without my assistance, I thought I'd use a keyfile to authorize the mount.
So far I've created a keyfile and have added it to the partition using "luksKeyAdd". It didn't really say it was successful, but when I do a luksdump, it shows that another key slot has been enabled, so I believe it worked. After that I created a /etc/crypttab file with the following:
Code: backup_sdd1 /dev/sdd1 /root/backup luks /dev/sdd1 being the backup partition, and /root/backup being the keyfile
After rebooting, I am still prompted for a password when trying to mount the encrypted partition (sdd1), and there is no device "/dev/mapper/backup_sdd1" created like I believe there should be. I haven't added any entries to fstab, as I don't want this partition to mount at boot.
I've got some old drives using pre-LUKS loopback encryption, and I'm having problems mounting them on OpenSUSE 11.3. What I expected to work, based on past experiences with other distributions, is something along the lines of:
mount -t ext3 /dev/sdc11 tmp -o loop=/dev/loop1,encryption=AES256. When I try this I'm asked for the password, but then get the message "ioctl: LOOP_SET_STATUS: Invalid argument". Anyone have a clue what could be going wrong, or how I can best access these drives from OpenSUSE?