/etc/crypttab doesn't create /dev/mapper/swap

I'm not lucky with encryption these days: keyfile on USB stick doesn't work ( http://bbs.archlinux.org/viewtopic.php?id=52507 ), so revert to the passphrase thing.
I had swap encryption working using the old rc.local way etc. now there's a new way... "SWAP" keyword inside /etc/crypttab and no rc.local changes, wonderful right? Wrong. It doesn't work, if you put (example)
swap /dev/sda3 SWAP -c aes-xts-plain -h whirlpool -s 512
inside /etc/crypttab and reboot, it doesn't create any /dev/mapper/swap device (so it can't swapon).
Where's the issue?
Last edited by ekerazha (2008-08-20 13:22:35)

dw wrote:
hi ekerazha.
i am playing around with system encryption a bit lately and i am experiencing exactly the same. my question. were you able to solve this?
No... maybe reverting to the "old" way (no SWAP keyword etc.)
Last edited by ekerazha (2008-08-23 16:36:41)

Similar Messages

(SOLVED) uinput doesn't create "/dev/misc/uinput"

Hello !
After closely following the Wiimote connection guide for the third time, I decided to ask you gurus here on the forums about the issue.
The instructions say:
First you need to make sure to load the uinput module:
$ sudo modprobe uinput
You should have a device in /dev/misc/uinput now.
However, the "/dev/misc" folder NEVER gets created, even after a reboot with "uinput" placed in the modules section of the rc.conf.
Therefore later, when I try to make the Wiimote function as an input device (with the "wminput" command), it gives out the error:
"unable to open uinput".
Is this a kernel error?
Does anyone know a way around it?
I found this information about a similar problem being resolved by using mknod here:
https://bugzilla.redhat.com/show_bug.cgi?id=213854
To summarize, the idea of this bug on Redhat is:
module loads but device node is not created.
If created manually with mknod everything works fine.
Expected results:
udev should create the device node
Thank you for all your help in advance,
UFOKatarn
Last edited by UFOKatarn (2010-09-05 20:12:45)

Thanks for the tip!
All I had to do was to allow non-root users access to uinput.
For all that might be ssearching the forum and stumble upon the same problem, this is done like this:
1.)
create a new file in the folder /etc/udev/rules.d
I named it user.rules, but the name and/or its extension don't matter
2.)
paste the following line into it
KERNEL=="uinput", GROUP="wheel", MODE:="0660"
I think MODE:="0660" allows all users to use uinput, but I'm not sure.
Solely having my user in the "wheel" group and NOT having the "MODE:="0660" in the rule didn't allow my user to access uinput.
3.)
reboot
4.)
start the command "wminput" as a normal user
Regards,
UFOKatarn

Not prompted for encrytion key for /dev/mapper/home

I never had a problem setting up encryption on my last laptop, but for some reason on this new laptop I am having the hardest time with this...
I tried installing about four times because I thought I missed something. I have 3 partitions /boot , / and /home, during boot / prompts me for a key and works fine, but it doesnt bother asking me for a key for /home
In my /etc/crypttab i have
home /dev/mapper/home ASK
in my /etc/fstab i have
/dev/mapper/home /home ext4 defaults 0 1
during the install I did everything I thought necessary from the various archlinux wiki pages on encryption.
am I missing something?(obviously I am)

Here try this:
If you using WZC or the built-in wireless utlity of windows.
Go to network connections > right click the wireless network connections >
Go to the wireless network tab > delete all the prefered networks >
Try to reconnect to the wireless network again
If your using Linksys wireless utility or WLAN
Open the software > Go to the profile tab and delete all that you dont need
Try to reconnect to the network again
The profile or the prefered networks are lists of all the networks you have ever connectec to. I believe you did not change the SSID of your network when you secured thus your computer detects it still as an unsecured network
hope this help
"Give them nothing... But take from them everything..."
-Leonidas "300"

[solved] how to run /etc/crypttab

I've created an /etc/crypttab file, now how do I run it? What is the equivalent of typing `mount -a` to activate /etc/fstab but to activate /etc/crypttab?
Thanks
Last edited by spotshot6544 (2013-08-03 18:58:04)

I can open the drive with
cryptsetup open /dev/sdb1 driveName --key-file myKeyfile
and `crypttab status driveName` reports:
/dev/mapper/driveName is active and is in use.
type: LUKS1
cipher: aes-xts-plain64
keysize: 512 bits
device: /dev/sdb1
offset: 4096 sectors
size: 5860526080 sectors
mode: read/write
And then I could certainly mount it with `mount /dev/mapper/driveName /mnt` but I'd prefer to have this setup to happen at boot (before login). I suppose I could add these commands to a custom systemd script, but that doesn't seem the proper way to go.
I tried `pacman -S systemd` and was told that it would be reinstalling.
The problem I might be having is that I am not familiar with systemd, and I have only recently moved to Arch.
(Note, "myKeyfile" exists on my system drive which is encrypted too (with a passphrase), so, for my goals, there is no passphrase and that is fine)

/etc/init.d/oracleasm configure do not create /dev/oracleasm mountpoint

Dear All,
I have to put my question like this, I am following humter_rac10gr2_iscsi. I have done everything as per documentation and the results so far have been ok. When i come to the part where we have to create ASM volumes and when i after installing asm library give the following command:
/etc/init.d/oracleasm configure
The commd runs sucessfully but misses the folling line that is in documentation:
Creating /dev/oracleasm mount point: [OK]
Because of this miss I guess last time when i reached the poing during dbca database creation where it shows ASM volumes, it did not discover any ASM volumes and i was stuck at this point.
Kindly help me on this?
Regards, Imran baig

Hello,
Well i run /etc/init.d/oracleasm configure command as root user.
Yesh I have just checked i can cd to /dev/oracleasm/disks and can find
VOLl VOL2 VOL3 VOL4 there
I have delete first and then create ASM volumes and now i can scan and list then from both nodes.
/etc/init.d/oracleasm status says that
Checking if ASM is loaded: [OK]
Checking if /dev/oracleasm is mounted: [OK] :)
But id did not show it during configuration and similary when i run dbca at the screen where to specify volumes, nothing is there even when i cange disk path to ORCL:VOL* there is nothing....
Kindly help with the dbca configurations so that it pick up the ASM VOLUMES.
Regards,
Imran

LVM /dev/mapper is empty, + systemd boot hangs

Hi!
1st problem:
I have 2 vgs with 1 lv each -- called Sys/Linux and Sys2/Var. Booting the kernel with root=/dev/mapper/Sys-Linux works, but after mounting the root fs, /dev/mapper is empty:
$ ls /dev/mapper
control
2nd problem:
I changed UUID= to /dev/dm-1 for /var for testing purposes, but systemd will timeout on mounting /var. Note: after entering the emergency console, I can just type mount /var and it will mount.
The system is was quite old and I changed to systemd-only right now, because I upgraded the filesystem package (that removes /bin, /sbin, /usr/sbin and required me to remove outdated packages). ((Yes, I'm late )).
I hope anyone has some pointers; please tell me, which config files you need to see if any, to help out.
Thanks,
Andy
Last edited by Black Sliver (2013-08-12 20:14:40)

[2013-08-12 19:33] [ALPM-SCRIPTLET] >>> Updating module dependencies. Please wait ...
[2013-08-12 19:33] [ALPM-SCRIPTLET] >>> Generating initial ramdisk, using mkinitcpio. Please wait...
[2013-08-12 19:33] [ALPM-SCRIPTLET] ==> Building image from preset: /etc/mkinitcpio.d/linux.preset: 'default'
[2013-08-12 19:33] [ALPM-SCRIPTLET] -> -k /boot/vmlinuz-linux -c /etc/mkinitcpio.conf -g /boot/initramfs-linux.img
[2013-08-12 19:33] [ALPM-SCRIPTLET] ==> Starting build: 3.10.5-1-ARCH
[2013-08-12 19:33] [ALPM-SCRIPTLET] -> Running build hook: [base]
[2013-08-12 19:33] [ALPM-SCRIPTLET] -> Running build hook: [udev]
[2013-08-12 19:33] [ALPM-SCRIPTLET] -> Running build hook: [autodetect]
[2013-08-12 19:33] [ALPM-SCRIPTLET] -> Running build hook: [block]
[2013-08-12 19:33] [ALPM-SCRIPTLET] -> Running build hook: [keyboard]
[2013-08-12 19:33] [ALPM-SCRIPTLET] -> Running build hook: [lvm2]
[2013-08-12 19:33] [ALPM-SCRIPTLET] ==> ERROR: file not found: `/usr/sbin/dmsetup'
[2013-08-12 19:33] [ALPM-SCRIPTLET] -> Running build hook: [resume]
[2013-08-12 19:33] [ALPM-SCRIPTLET] -> Running build hook: [filesystems]
[2013-08-12 19:33] [ALPM-SCRIPTLET] -> Running build hook: [shutdown]
[2013-08-12 19:33] [ALPM-SCRIPTLET] ==> Generating module dependencies
[2013-08-12 19:33] [ALPM-SCRIPTLET] ==> Creating lzma initcpio image: /boot/initramfs-linux.img
[2013-08-12 19:33] [ALPM-SCRIPTLET] ==> WARNING: errors were encountered during the build. The image may not be complete.
[2013-08-12 19:33] [ALPM-SCRIPTLET] ==> Building image from preset: /etc/mkinitcpio.d/linux.preset: 'fallback'
[2013-08-12 19:33] [ALPM-SCRIPTLET] -> -k /boot/vmlinuz-linux -c /etc/mkinitcpio.conf -g /boot/initramfs-linux-fallback.img -S autodetect
[2013-08-12 19:33] [ALPM-SCRIPTLET] ==> Starting build: 3.10.5-1-ARCH
[2013-08-12 19:33] [ALPM-SCRIPTLET] -> Running build hook: [base]
[2013-08-12 19:33] [ALPM-SCRIPTLET] -> Running build hook: [udev]
[2013-08-12 19:33] [ALPM-SCRIPTLET] -> Running build hook: [block]
[2013-08-12 19:33] [ALPM-SCRIPTLET] ==> WARNING: Possibly missing firmware for module: bfa
[2013-08-12 19:33] [ALPM-SCRIPTLET] ==> WARNING: Possibly missing firmware for module: aic94xx
[2013-08-12 19:33] [ALPM-SCRIPTLET] ==> WARNING: Possibly missing firmware for module: smsmdtv
[2013-08-12 19:33] [ALPM-SCRIPTLET] -> Running build hook: [keyboard]
[2013-08-12 19:33] [ALPM-SCRIPTLET] -> Running build hook: [lvm2]
[2013-08-12 19:33] [ALPM-SCRIPTLET] ==> ERROR: file not found: `/usr/sbin/dmsetup'
[2013-08-12 19:33] [ALPM-SCRIPTLET] -> Running build hook: [resume]
[2013-08-12 19:33] [ALPM-SCRIPTLET] -> Running build hook: [filesystems]
[2013-08-12 19:33] [ALPM-SCRIPTLET] -> Running build hook: [shutdown]
[2013-08-12 19:33] [ALPM-SCRIPTLET] ==> Generating module dependencies
[2013-08-12 19:33] [ALPM-SCRIPTLET] ==> Creating lzma initcpio image: /boot/initramfs-linux-fallback.img
[2013-08-12 19:34] [ALPM-SCRIPTLET] ==> WARNING: errors were encountered during the build. The image may not be complete.
Note that initial mounting of root=/dev/mapper/Sys-Linux works. Can this be the problem anyway? I rebuilt the initrd, I'll try to boot it tomorrow.
[2013-08-12 19:42] [PACMAN] Running 'pacman -R initscripts sysvinit' # NOTE: this was required for the filesystem upgrade to work (/sbin)
[2013-08-12 19:42] [ALPM] warning: /etc/rc.conf saved as /etc/rc.conf.pacsave
[2013-08-12 19:42] [ALPM] warning: /etc/inittab saved as /etc/inittab.pacsave
Theese are not required with systemd ?
Everything else is just upgrade/install/remove or uninteresting. Or do you want to see everything?
Last edited by Black Sliver (2013-08-12 22:48:32)

Installing OVS 3.3.1 for use without the VM Manager and /dev/mapper

Hello,
I've done an install of OVS 3.3.1 on to a standalone server with a local disk.
When I do an fdisk -l I see the following output
[root@SYS-VMServer1 ~]# fdisk -l
Disk /dev/sda: 1000.2 GB, 1000204886016 bytes
255 heads, 63 sectors/track, 121601 cylinders
Units = cylinders of 16065 * 512 = 8225280 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 512 bytes / 512 bytes
Disk identifier: 0x0001e3a5
   Device Boot      Start         End      Blocks   Id System
/dev/sda1   *           1          64      512000   83 Linux
Partition 1 does not end on cylinder boundary.
/dev/sda2              64        6591    52428800   83 Linux
/dev/sda3            6591        7063     3784704   82 Linux swap / Solaris
/dev/sda4            7063      121602   920035328   83 Linux
Disk /dev/mapper/OVM_SYS_REPO_PART_350024e9003518d34: 942.1 GB, 942116175872 bytes
255 heads, 63 sectors/track, 114539 cylinders
Units = cylinders of 16065 * 512 = 8225280 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 512 bytes / 512 bytes
Disk identifier: 0x00000000
What I'd like to do is remove the /dev/mapper/OVM_SYS_REPO_PART_350024e9003518d34 partition (I think this is using the /dev/sda4 partition)
I tried deleting the partition /dev/sda4
then
kpartx -d /dev/mapper/OVM_SYS_REPO_PART_350024e9003518d34
However when I re-create the /dev/sda4 partition and then reboot the /dev/mapper/OVM_SYS_REPO_PART_350024e9003518d34 re-appears!!
I want to create a standard partition formatted as an EXT4 file-system and start/stop vm's from using the xm command's (we create our VM's on another OVS 3.3.1 + VM Manager that's on another server).
The reason for this is that we want to use DRBD + REMUS which is included with OVS 3.3.1 (just type modinfo drbd)
I know I could probably download xen on to an appropriate OEL Distro but I like using OVS as it's simple, straight-forward and it works!
Thanks for your help

Suggestions…? Well yes… simply forget about that! Oracle treats OVM server as an appliance - or least they'd like to and sell us the hardware as well. Since they can't do that, they decided to "craft" the system to their likings and omit lots of things one might consider either necessary or nice to have.
Oralce did intentionally leave out all the gcc stuff and a lot of the other tools as well, to make sure mortals don't mess around with the system. If you want to use OVM then you will have to live with that or risk breaking any part of OVM and rendering your installation unsupported by Oracle.
Besides, I don't actually see, why one would need to install libvirt/virt-install on a OVM server?

Is it possible to mount a physical disk (/dev/mapper/ disk) on one of my Oracle VM server

I have a physical disk that I can see from multipath -ll that shows up as such
# multipath -ll
3600c0ff00012f4878be35c5401000000 dm-115 HP,P2000G3 FC/iSCSI
size=410G features='1 queue_if_no_path' hwhandler='0' wp=rw
|-+- policy='round-robin 0' prio=50 status=active
| `- 7:0:0:49 sdcs 70:0   active ready running
`-+- policy='round-robin 0' prio=10 status=enabled
`- 10:0:0:49 sdcr 69:240 active ready running
That particular is visible in the OVMM Gui as a physical disk that I can present to one of my VMs but currently its not presented to any of them.
I have about 50 physical LUNs that my Oracle VM server can see. I believe I can see all of them from a fdisk -l, but "dm-115" (which is from the multipath above) doesnt show up.
This disk has 3 usable partitions on it, plus a Swap.
I want to mount the 3rd partition temporarily on the OVM server itself and I receive
# mount /dev/mapper/3600c0ff00012f4878be35c5401000000p3 /mnt
mount: you must specify the filesystem type
If I present the disk to a VM and then try to mount the /dev/xvdx3 partition -it of course works. (x3 - represents the 3rd partition on what ever letter position the disk shows up as)
Is this possible?

Its more of the correct syntax. Like I can not seem to figure out how to translate the /dev/mapper path above into what fdisk -l shows. Perhaps if I knew how fdisk and multipath can be cross referenced I could mount the partition.
I had already tried what you suggested. Here is the output if I present the disk to a VM and then mount the 3rd partition.
# fdisk -l
Disk /dev/xvdh: 439.9 GB, 439999987712 bytes
255 heads, 63 sectors/track, 53493 cylinders
Units = cylinders of 16065 * 512 = 8225280 bytes
    Device Boot      Start         End      Blocks   Id System
/dev/xvdh1   *           1          13      104391   83 Linux
/dev/xvdh2              14        2102    16779892+ 82 Linux swap / Solaris
/dev/xvdh3            2103       27783   206282632+ 83 Linux
/dev/xvdh4           27784       30394    20972857+   5 Extended
/dev/xvdh5           27784       30394    20972826   83 Linux
# mount /dev/xvdh3 /mnt <-- no error
# df -h
Filesystem            Size Used Avail Use% Mounted on
/dev/xvda3            197G 112G   75G 60% /
/dev/xvda5             20G 1011M   18G   6% /var
/dev/xvda1             99M   32M   63M 34% /boot
tmpfs                 2.0G     0 2.0G   0% /dev/shm
/dev/xvdh3            191G   58G 124G 32% /mnt <-- mounted just fine
Its ext3 partition
# df -T
/dev/xvdh3
ext3   199822096 60465024 129042944 32% /mnt
Now if I go to my vm.cfg file, I can see the disk that is presented.
My disk line contains
disk = [...'phy:/dev/mapper/3600c0ff00012f4878be35c5401000000,xvdh,w', ...]
Multipath shows that disk and says "dm-115" but that does not translate on fdisk
# multipath -ll
3600c0ff00012f4878be35c5401000000 dm-115 HP,P2000G3 FC/iSCSI
size=410G features='1 queue_if_no_path' hwhandler='0' wp=rw
|-+- policy='round-robin 0' prio=50 status=active
| `- 7:0:0:49 sdcs 70:0   active ready running
`-+- policy='round-robin 0' prio=10 status=enabled
`- 10:0:0:49 sdcr 69:240 active ready running
I have around 50 disks on this server, but the ones of the same size from fdisk -l from the server shows me many.
# fdisk -l
Disk /dev/sdp: 439.9 GB, 439999987712 bytes
255 heads, 63 sectors/track, 53493 cylinders
Units = cylinders of 16065 * 512 = 8225280 bytes
   Device Boot      Start         End      Blocks   Id System
/dev/sdp1   *           1          13      104391   83 Linux
/dev/sdp2              14        2102    16779892+ 82 Linux swap / Solaris
/dev/sdp3            2103       27783   206282632+ 83 Linux
/dev/sdp4           27784       30394    20972857+   5 Extended
/dev/sdp5           27784       30394    20972826   83 Linux
Disk /dev/sdab: 439.9 GB, 439956406272 bytes
255 heads, 63 sectors/track, 53488 cylinders
Units = cylinders of 16065 * 512 = 8225280 bytes
    Device Boot      Start         End      Blocks   Id System
/dev/sdab1   *           1          13      104391   83 Linux
/dev/sdab2              14        1318    10482412+ 82 Linux swap / Solaris
/dev/sdab3            1319       27783   212580112+ 83 Linux
/dev/sdab4           27784       30394    20972857+   5 Extended
/dev/sdab5           27784       30394    20972826   83 Linux
Disk /dev/sdac: 439.9 GB, 439956406272 bytes
255 heads, 63 sectors/track, 53488 cylinders
Units = cylinders of 16065 * 512 = 8225280 bytes
    Device Boot      Start         End      Blocks   Id System
/dev/sdac1   *           1          13      104391   83 Linux
/dev/sdac2              14        2102    16779892+ 82 Linux swap / Solaris
/dev/sdac3            2103       27783   206282632+ 83 Linux
/dev/sdac4           27784       30394    20972857+   5 Extended
/dev/sdac5           27784       30394    20972826   83 Linux
Disk /dev/sdad: 439.9 GB, 439956406272 bytes
255 heads, 63 sectors/track, 53488 cylinders
Units = cylinders of 16065 * 512 = 8225280 bytes
    Device Boot      Start         End      Blocks   Id System
/dev/sdad1   *           1          13      104391   83 Linux
/dev/sdad2              14        1318    10482412+ 82 Linux swap / Solaris
/dev/sdad3            1319       27783   212580112+ 83 Linux
/dev/sdad4           27784       30394    20972857+   5 Extended
/dev/sdad5           27784       30394    20972826   83 Linux
Disk /dev/sdae: 439.9 GB, 439956406272 bytes
255 heads, 63 sectors/track, 53488 cylinders
Units = cylinders of 16065 * 512 = 8225280 bytes
    Device Boot      Start         End      Blocks   Id System
/dev/sdae1   *           1          13      104391   83 Linux
/dev/sdae2              14        2102    16779892+ 82 Linux swap / Solaris
/dev/sdae3            2103       27783   206282632+ 83 Linux
/dev/sdae4           27784       30394    20972857+   5 Extended
/dev/sdae5           27784       30394    20972826   83 Linux
Disk /dev/sdaf: 439.9 GB, 439999987712 bytes
255 heads, 63 sectors/track, 53493 cylinders
Units = cylinders of 16065 * 512 = 8225280 bytes
    Device Boot      Start         End      Blocks   Id System
/dev/sdaf1   *           1          13      104391   83 Linux
/dev/sdaf2              14        2102    16779892+ 82 Linux swap / Solaris
/dev/sdaf3            2103       27783   206282632+ 83 Linux
/dev/sdaf4           27784       30394    20972857+   5 Extended
/dev/sdaf5           27784       30394    20972826   83 Linux
Disk /dev/sdag: 439.9 GB, 439999987712 bytes
255 heads, 63 sectors/track, 53493 cylinders
Units = cylinders of 16065 * 512 = 8225280 bytes
    Device Boot      Start         End      Blocks   Id System
/dev/sdag1   *           1          13      104391   83 Linux
/dev/sdag2              14        2102    16779892+ 82 Linux swap / Solaris
/dev/sdag3            2103       27783   206282632+ 83 Linux
/dev/sdag4           27784       30394    20972857+   5 Extended
/dev/sdag5           27784       30394    20972826   83 Linux
Disk /dev/dm-13: 439.9 GB, 439999987712 bytes
255 heads, 63 sectors/track, 53493 cylinders
Units = cylinders of 16065 * 512 = 8225280 bytes
      Device Boot      Start         End      Blocks   Id System
/dev/dm-13p1   *           1          13      104391   83 Linux
/dev/dm-13p2              14        2102    16779892+ 82 Linux swap / Solaris
/dev/dm-13p3            2103       27783   206282632+ 83 Linux
/dev/dm-13p4           27784       30394    20972857+   5 Extended
/dev/dm-13p5           27784       30394    20972826   83 Linux
Disk /dev/dm-25: 439.9 GB, 439956406272 bytes
255 heads, 63 sectors/track, 53488 cylinders
Units = cylinders of 16065 * 512 = 8225280 bytes
      Device Boot      Start         End      Blocks   Id System
/dev/dm-25p1   *           1          13      104391   83 Linux
/dev/dm-25p2              14        1318    10482412+ 82 Linux swap / Solaris
/dev/dm-25p3            1319       27783   212580112+ 83 Linux
/dev/dm-25p4           27784       30394    20972857+   5 Extended
/dev/dm-25p5           27784       30394    20972826   83 Linux
Disk /dev/dm-26: 439.9 GB, 439956406272 bytes
255 heads, 63 sectors/track, 53488 cylinders
Units = cylinders of 16065 * 512 = 8225280 bytes
      Device Boot      Start         End      Blocks   Id System
/dev/dm-26p1   *           1          13      104391   83 Linux
/dev/dm-26p2              14        2102    16779892+ 82 Linux swap / Solaris
/dev/dm-26p3            2103       27783   206282632+ 83 Linux
/dev/dm-26p4           27784       30394    20972857+   5 Extended
/dev/dm-26p5           27784       30394    20972826   83 Linux
Disk /dev/dm-27: 439.9 GB, 439956406272 bytes
255 heads, 63 sectors/track, 53488 cylinders
Units = cylinders of 16065 * 512 = 8225280 bytes
      Device Boot      Start         End      Blocks   Id System
/dev/dm-27p1   *           1          13      104391   83 Linux
/dev/dm-27p2              14        1318    10482412+ 82 Linux swap / Solaris
/dev/dm-27p3            1319       27783   212580112+ 83 Linux
/dev/dm-27p4           27784       30394    20972857+   5 Extended
/dev/dm-27p5           27784       30394    20972826   83 Linux
Disk /dev/dm-28: 439.9 GB, 439956406272 bytes
255 heads, 63 sectors/track, 53488 cylinders
Units = cylinders of 16065 * 512 = 8225280 bytes
      Device Boot      Start         End      Blocks   Id System
/dev/dm-28p1   *           1          13      104391   83 Linux
/dev/dm-28p2              14        2102    16779892+ 82 Linux swap / Solaris
/dev/dm-28p3            2103       27783   206282632+ 83 Linux
/dev/dm-28p4           27784       30394    20972857+   5 Extended
/dev/dm-28p5           27784       30394    20972826   83 Linux
Disk /dev/dm-29: 439.9 GB, 439999987712 bytes
255 heads, 63 sectors/track, 53493 cylinders
Units = cylinders of 16065 * 512 = 8225280 bytes
      Device Boot      Start         End      Blocks   Id System
/dev/dm-29p1   *           1          13      104391   83 Linux
/dev/dm-29p2              14        2102    16779892+ 82 Linux swap / Solaris
/dev/dm-29p3            2103       27783   206282632+ 83 Linux
/dev/dm-29p4           27784       30394    20972857+   5 Extended
/dev/dm-29p5           27784       30394    20972826   83 Linux
Disk /dev/dm-30: 439.9 GB, 439999987712 bytes
255 heads, 63 sectors/track, 53493 cylinders
Units = cylinders of 16065 * 512 = 8225280 bytes
      Device Boot      Start         End      Blocks   Id System
/dev/dm-30p1   *           1          13      104391   83 Linux
/dev/dm-30p2              14        2102    16779892+ 82 Linux swap / Solaris
/dev/dm-30p3            2103       27783   206282632+ 83 Linux
/dev/dm-30p4           27784       30394    20972857+   5 Extended
/dev/dm-30p5           27784       30394    20972826   83 Linux
How to translate the /dev/mapper address into the correct fdisk, I think I can then mount it.
If I try the same command as before with the -t option it gives me this error.
# mount -t ext3 /dev/mapper/3600c0ff00012f48791975b5401000000p3 /mnt
mount: special device /dev/mapper/3600c0ff00012f48791975b5401000000p3 does not exist
I know I am close here, and feel it should be possible, I am just missing something.
Thanks for any help

QSynth doesn't create jack port.

I have a problem with QSynth - it doesn't create jack port, so i can't connect it to output. When i run fluidsynth from console it works properly - it creates output, I connect it to "system" port using QJackCtl and i can hear midi sound, but i really ned QSynth. Please help me.
Messages from QSynth:
15:11:57.027 Qsynth1: Creating synthesizer engine...
15:11:57.058 Qsynth1: Loading soundfont: "/usr/share/soundfonts/fluidr3/FluidR3GM.SF2" (bank offset 0)...
15:11:57.281 Qsynth1: Creating audio driver (jack)...
15:11:57.294 Qsynth1: Creating MIDI router (alsa_seq)...
15:11:57.295 Qsynth1: Creating MIDI driver (alsa_seq)...
15:11:57.296 Qsynth1: Creating MIDI player...
15:11:57.298 Qsynth1: Synthesizer engine started.
15:11:57.298 Qsynth1: fluid_synth_set_gain(0.97)
15:11:57.299 Qsynth1: fluid_synth_set_reverb(0.2,0.5,10,0.1)
15:11:57.299 Qsynth1: fluid_synth_set_chorus(3,1,0.3,8,0)
fluidsynth: warning: Failed to pin the sample data to RAM; swapping is possible.
fluidsynth: prog 0 0 0
fluidsynth: prog 1 0 0
//............. some lines like above and bellow
fluidsynth: prog 14 0 14
fluidsynth: prog 15 0 15
zombified - calling shutdown handler
fluidsynth: error: Help! Lost the connection to the JACK server
Last edited by dawidmt (2011-08-26 13:20:17)

Sorry about the necro, but did you ever figure this out? I'm running into the same issue. I think *something* is being written because when I do "efibootmgr -c blahblah", and then I do an efibootmgr -v afterward, I can see the device path that shows up in the verbose options. Then, when I reboot, I don't see the new boot option in the menu, and when I check again via a livecd (which boots via UEFI, by the way), efibootmgr -v shows "Vendor(99e275e7-75a0-4b37-a2e6-c5385e6c00cb,)" in the extra info next to the boot option I had previously created. That vendor and GUID seem to show up when there's no path, as I've googled it and have seen similar readouts that imply such based on the context of where I saw them.
Anyway, help.
Thanks.
-TJ

Adding a USB HDD to a VM via OVM - /dev/mapper Error

Hey all,
we're trying to hook up a USB HDD to a virtualized database server for a one time backup.
So after connecting it to the OVS, i formatted it to ext3, mounted it and voila. When i edit the database VM via OVM i can add a Physical Disk.
I am getting an error though:
Status: org.apache.xmlrpc.XmlRpcException: exceptions.RuntimeError:disk:setup_error:Command: ['xm', 'block-attach', '0004fb000006000056a65a591c902757', 'phy:/dev/mapper/35000000000000001', 'xvdd', 'w'] failed (1): stderr: Error: Device 51760 (vbd) could not be connected. /dev/mapper/35000000000000001 does not exist.stdout: Usage: xm block-attach [BackDomain]
...and he is right. There is no /dev/mapper/35000000000000001
But where does it get that information from?!
Any ideas?

OVM will only make use of volumes that are accessible through /dev/mapper. USB volumes are, as you already know, not available in /dev/mapper and thus can't be mapped to virtiual machines as volumes.
This is a limitation, but I think Oracle decided for this, because a USB drive really doesn't make a good choice for a virtual drive, as is introduces a lot of latency and other potential I/O issues, you don't want to have in a virtualized environment.
It would be better to map the backup drive in thge guest itself using other protocols like NFS.
Cheers,
budy

OVM 3.1.1 Repository Being Mapped with Diffferent /dev/mapper/ address

Hello,
I'm running OVM 3.1 on a Dell T420 server with onboard storage. The RAID 5 virtual disk that was housing my repository was inadvertently deleted. I was able to recreate a new VD and the server can now see the original ocsf2 partition that the repository lived on. However, it obtained a new /dev/mapper/ address and OVM manager will not mount the repository. Is there a way to rename the /dev/mapper address to the old address that OVM manager is looking for? Thanks!

No, the ID in /dev/mapper is generated from the SCSI-83-page and that one is created on the storage and it cannot be changed. You can find some howto on the net, that deals with such an issue where, but it's not for the faint-hearted. A lot of information are in this post, which deals with howto get an existing storage repo up on a remote site, but some of the concepts also apply to your situation:
https://oraclenz.wordpress.com/2013/06/13/oracle-vm-3-1-disaster-recovery-ha/
That one helped me as well…
https://community.oracle.com/thread/3596198
Cheers,
budy

Failed mount /dev/mapper/oradata

Hello experts!
After reboot OS failed mount /dev/mapper/oradata
OS: SUSE 10 sp4 ppc64
SAN: DS5300
My steps how i add the LUN:
1) rescan-scsi-bus.sh
2) vi /etc/multipath.conf
defaults
user_friendly_names no
multipaths {
multipath {
wwid 3600a0b80006e6a66000040a95066a18b
alias oradata
3) fdisk /dev/dm-2
4) echo 'add' > /sys/block/dm-2/uevent
5) /sbin/mkfs.reiserfs /dev/dm-2
6) mkdir /oradata
7) vi /etc/fstab
/dev/mapper/oradata /oradata reiserfs acl,user_xattr 1 2
8) mount a
C01-OraDB-02:~ # multipath -ll
oradata (3600a0b80006e6a66000040a95066a18b) dm-2 IBM,1818 FAStT
[size=100G][features=0][hwhandler=0]
\_ round-robin 0 [prio=0][enabled]
\_ 2:0:1:0 sdf 8:80 [failed][faulty]
\_ round-robin 0 [prio=1][active]
\_ 2:0:0:0 sde 8:64 [active][ready]
\_ round-robin 0 [prio=0][enabled]
\_ 1:0:1:0 sdd 8:48 [failed][faulty]
\_ round-robin 0 [prio=1][enabled]
\_ 1:0:0:0 sdc 8:32 [active][ready]
In logs /var/log/messages
end_request: I/O error, dev sdd, sector 0
end_request: I/O error, dev sdf, sector 0
end_request: I/O error, dev sdd, sector 0
end_request: I/O error, dev sdf, sector 0
end_request: I/O error, dev sdd, sector 0
end_request: I/O error, dev sdf, sector 0
end_request: I/O error, dev sdd, sector 0

ostapv,
It appears that in the past few days you have not received a response to your
posting. That concerns us, and has triggered this automated reply.
Has your problem been resolved? If not, you might try one of the following options:
- Visit http://support.novell.com and search the knowledgebase and/or check all
the other self support options and support programs available.
- You could also try posting your message again. Make sure it is posted in the
correct newsgroup. (http://forums.novell.com)
Be sure to read the forum FAQ about what to expect in the way of responses:
http://forums.novell.com/faq.php
If this is a reply to a duplicate posting, please ignore and accept our apologies
and rest assured we will issue a stern reprimand to our posting bot.
Good luck!
Your Novell Product Support Forums Team
http://forums.novell.com/

[SOLVED] filesystem package: list by label in /etc/crypttab

Reading about Persistent Device Naming, using labels in /etc/fstab rather than UUIDs has some advantages. But /etc/crypttab seems to support only /dev/sdXY and UUID notation. Since flesystem is listed as an Arch Linux package, is there any chance of adding support for naming devices with labels in /etc/crypttab?
Last edited by Konkorde (2014-12-15 01:28:42)

falconindy wrote:You cannot identify an encrypted filesystem by LABEL, because the label itself is a property of the unencrypted filesystem. You're asking to solve a chicken/egg problem.
I apologize for misspeaking: I want to identify a partition containing an encrypted filesystem by label in /etc/crypttab. While /dev/disk/sdXY works, /dev/disk/by-label/foo did not work.
falconindy wrote:You can identify an encrypted filesystem by its PARTLABEL (or PARTUUID), assuming you've partitioned your disks with GPT. I added support, implicitly, for this to /etc/crypttab 2 years ago.
Thanks Dave: I am using GPT and although I'm new to PARTLABEL, I'll look into it. Looking at the code you linked, though, I think I probably just want to use the
if (startswith(p, "LABEL="))
branch, rather than
/dev/disk/by-label
Last edited by Konkorde (2014-11-16 16:26:39)

Systemd: mounting /dev/mapper/... fails

Since some recent update one of my LUKS-encrypted volumes is not being mounted correctly.
I used to have this .mount file as the volume actually is a multi-device btrfs volume:
[Unit]
Description=/mnt/archive
Wants=cryptsetup.target
After=cryptsetup.target
[Mount]
What=/dev/mapper/archive1
Where=/mnt/archive
Type=btrfs
Options=defaults,noatime,nodiratime
The error I get when I try to manually start this service is:
systemd[1]: Expecting device dev-mapper-archive1.device...
thor systemd[1]: Job dev-mapper-archive1.device/start timed out.
thor systemd[1]: Timed out waiting for device dev-mapper-archive1.device.
thor systemd[1]: Dependency failed for /mnt/archive.
thor systemd[1]: Job mnt-archive.mount/start failed with result 'dependency'.
thor systemd[1]: Job dev-mapper-archive1.device/start failed with result 'timeout'.
I double-checked /dev/mapper and there definitely is the device node in question, which I can manually mount without any problem.
Any idea why my .mount file stopped working or why systemd doesn't find the existing /dev/mapper/archive1?

Thanks for the quick response, WonderWoofy ( by the way, great username! )!
When I removed or modified the the mount options in the bootloader kernel command line, there was no change to the status of the fs after boot-up. I had changed it at one point from 'ro', to 'rw'; but doing so had no affect on the output of the mount command.
However, I did finally identify the cause: turns out if I specify 'data=writeback', in fstab for the root partition, then systemd-remount-fs.service fails, as per my OP - leaving me with a 'ro'-mounted root filesystem. Simply removing that, or changing it to 'data=ordered', solved the issue: when I rebooted, the root partition was mounted as per my fstab config.
So, my fstab now looks like this:
# /dev/sda5
UUID=a09ff37e-ce60-4173-b95a-4b71a53c01d3 / ext4 rw,noatime,discard 0 1
# /dev/sda6
UUID=f4ab3551-c4f8-4e77-97bb-cc754c81af24 /usr ext4 defaults,ro,noatime,discard,data=writeback 0 0
# /dev/sda7
UUID=c8d2776b-faaa-4a9d-ad49-4b09489faaaa /var ext4 defaults,rw,noatime,discard 0 2
# /dev/sda8
UUID=3dff3fa5-3291-4227-907a-258f12e1b3cf /home ext4 defaults,rw,relatime,discard 0 2
... and all is now well.
I'll mark this as solved, but I'll also ask: why does specifying 'data=writeback' on my root partition cause the systemd-remount-fs.service to fail? Any experts out there know?
Last edited by corey_s (2012-12-02 06:46:32)

[SOLVED] Cannot create /dev/loop0

I am trying to create an encrypted loopback device.
Firstly, I created a file using
dd if=/dev/urandom of=./bigsecret bs=1M count=200
Then, created a /dev/loop0 using
losetup /dev/loop0 ./bigsecret
Then these two commands:
cryptsetup luksFormat /dev/loop0
cryptsetup luksOpen /dev/loop0 secret
After that the expected behavior is to see a new file secret in /dev/mapper but I am not getting that. I am following the wiki https://wiki.archlinux.org/index.php/Sy … filesystem
EDIT: It seems like the loop0 was not being created and the losetup command was failing silently. Fixed now.
Last edited by shadyabhi (2012-06-15 14:20:59)

Something really bizarre is happening, when I run strace ln ../file file then it creates a hard link, but when I just run ln ../file file then it creates a soft link.
Perhaps there is an alias somewhere? I think that is the case.
Yes, that is correct.
I feel dumb now
But there's the answer to anyone who ever wants to know!

/etc/crypttab doesn't create /dev/mapper/swap

Similar Messages

Maybe you are looking for