[SOLVED] Cannot migrate to encrypted home partition

So I installed Arch to play around and familiarise myself with, and I'd now like to use it full time. My company require that either home dir or full disk encryption is used, so I need to migrate my home directory using ecryptfs. Followed the wiki (created a test user to break first though), but it fails as lsof seems to see its own process checking for open files as an open file: cue much
INFO: Checking disk space, this may take a few moments. Please be patient.
INFO: Checking for open files in /home/shw
INFO: The following files are in use:
COMMAND PID USER FD TYPE DEVICE SIZE/OFF NODE NAME
systemd 1 root 19r FIFO 0,8 0t0 8339 pipe
lsof 428 root 1w FIFO 0,8 0t0 10969 pipe
lsof 428 root 4w FIFO 0,8 0t0 9076 pipe
lsof 428 root 5r FIFO 0,8 0t0 9077 pipe
sed 429 root 0r FIFO 0,8 0t0 10969 pipe
lsof 430 root 3r FIFO 0,8 0t0 9076 pipe
lsof 430 root 6w FIFO 0,8 0t0 9077 pipe
ERROR: Cannot proceed.
Any suggestions?
Last edited by analbeard (2014-11-20 08:24:39)

I will give it try tomorrow and inform you about the outcome. I will use the guide  by anarxc http://sysphere.org/~anrxc/j/articles/e … index.html
Just to complete the information. When I logged in as root, (right after the boot) I got this
[root@notebook ~]$ ecryptfs-migrate-home -u user
INFO: Checking disk space, this may take a few moments. Please be patient.
INFO: Checking for open files in /home/shw
INFO: The following files are in use:
COMMAND PID USER FD TYPE DEVICE SIZE/OFF NODE NAME
systemd 1 root 22r FIFO 0,8 0t0 1196 pipe
systemd 1 root 23u FIFO 0,15 0t0 1198 /run/dmeventd-server
systemd 1 root 24u FIFO 0,15 0t0 1199 /run/dmeventd-client
systemd 1 root 26u FIFO 0,15 0t0 1203 /run/systemd/initctl/fifo
NetworkMa 258 root 20w FIFO 0,15 0t0 10093 /run/systemd/inhibit/1.ref
systemd-l 260 root 19r FIFO 0,15 0t0 10093 /run/systemd/inhibit/1.ref
systemd-l 260 root 26r FIFO 0,15 0t0 14800 /run/systemd/sessions/c2.ref
login 527 root 6w FIFO 0,15 0t0 14800 /run/systemd/sessions/c2.ref
ecryptfs- 669 root 1w FIFO 0,8 0t0 16695 pipe
tee 670 root 0r FIFO 0,8 0t0 16695 pipe
lsof 692 root 1w FIFO 0,8 0t0 16798 pipe
lsof 692 root 4w FIFO 0,8 0t0 15619 pipe
lsof 692 root 5r FIFO 0,8 0t0 15620 pipe
sed 693 root 0r FIFO 0,8 0t0 16798 pipe
sed 693 root 1w FIFO 0,8 0t0 16695 pipe
lsof 694 root 3r FIFO 0,8 0t0 15619 pipe
lsof 694 root 6w FIFO 0,8 0t0 15620 pipe
ERROR: cannot proceed
Last edited by macaco (2014-11-17 23:43:45)

Similar Messages

  • [SOLVED] Running Systemd service on login (encrypted home partition)

    Hi,
    I have a dm-crypt/LUKS encrypted home partition that's mounted via PAM on login. I'm trying to use a systemd service (profile-sync-daemon), but the service tries to start and access the home partition before the partition is mounted. The service does seem to start successfully, but it doesn't gain access to necessary files on the home partition and malfunctions later on. Is there a sane hack to somehow delay the start of the service until the relevant partition gets mounted (basically after login)? Manually starting the service after login works just as intended in this case - I'm just looking for a way to automate this process.
    I have an idea of starting the service via Openbox autostart, but I've currently failed in my attempts.
    Last edited by ggg377 (2015-05-28 18:31:10)

    Things got quite complicated and hacky as I researched this so I went out of the box a bit (or took the easy way out, whichever you prefer) and reinstalled Arch with a full disk encryption. All is fine now and I also expect to see less problems overall in the future. If anyone wants to continue researching this it would probably be a good idea to start a new thread.

  • [solved] how to easy encrypt HOME\USER folder?

    Hi Amigos!
    Can somone give me easy step by step guide how to easy encrypt home directory in Linux Arch please?
    I spent all day to try encrypt home directory (how I did it before in Debian) I used encyptfs-migrate-home -u [myusername] but after all encyption finished I'm unable to login to KDE to complete encyptfs-unwrap-passphrase script. I got error when KDE runing from xserver: call to lnusertemp failed (temporary directories full?)
    Realy approciate your help.
    Sławek
    Last edited by infoslaw (2013-08-09 20:17:44)

    mellowmaroon wrote:
    Here are some links to Arch Linux's great documentation:
    dm-crypt with LUKS
    Disk Encryption
    I found those two to be immensely helpful in learning about encryption on Arch Linux.
    Although it looks like you might actually want this (ECryptfs ArchWiki).  I use the dm-crypt/LUKS method, but the ArchWiki for ECryptfs looks like it has a good amount of info.
    Just as a heads up, be sure to search the ArchWiki thoroughly and look up what you're trying to do in general (encryption) first when you're trying to solve a problem.  The ArchWiki is very detailed and helpful.
    Thank you! Can I encrypt by use dm-crypt/LUKS method whole particion in few steps? Do you know does posible to clone hdd after full encryption?
    Regards,
    Sławek

  • [Solved]I accidentally erased my home partition.

    The name says it all. Long story short, I made an stupid error in Gparted and ended up with a completely blank home partition.  When I boot up, I get the normal Grub prompt, followed by the login prompt. I can successfully login to my user account, but when I try to start x, I get a black screen. If I try to start my window manager,enlightenment, with enlightenment_start, I get an error
    Enlightenment cannot initialize Ecore_X!
    And then it shuts down.  Argh!
    Last edited by AlecB (2013-05-30 02:38:17)

    Your $HOME has nothing to do with how your system runs, other than dole out required configurations for your specific user.  If you think that creating a directory is harder than reinstalling the system, then by all means, reinstall.  But you will not learn a damn thing from simply reinstalling the system.
    Just make your $HOME, set the right permissions and ownership, and then start to rebuild what you need.  I get the impression that your inability to go straight into a graphical environment implies an inability to boot.  This is not the case.
    Edit: In hindsight, this information was indeed something that you could have very easily figured out yourself with even the slightest bit of effort.  I think that we really have hit help vampirism.
    Last edited by WonderWoofy (2013-05-29 18:16:51)

  • [SOLVED] Arch Linux on encrypted luks partition on USB key

    Hi
    I've installed Arch Linux on a USB key following this Wiki page: https://wiki.archlinux.org/index.php/In … _a_USB_key
    I also used dm-crypt as described in this Wiki page: https://wiki.archlinux.de/title/Festpla … iante_1.29
    I installed Arch Linux on the USB key using VirtualBox.
    To do that, I created a "rawvmdk":
    vboxmanage internalcommands createrawvmdk -filename ./usb.vmdk -rawdisk /dev/sdd
    Everything works fine when I'm trying to start the system within VirtualBox.
    Syslinux loads Arch using the following kernel command:
    APPEND cryptdevice=UUID=6aa73872-3755-4bdf-bee3-d1cd7a3fe0bf:main root=/dev/mapper/main-root rw
    /etc/mkinitcpio.conf holds the following "HOOKS" configuration:
    HOOKS="base udev autodetect modconf block keyboard keymap encrypt lvm2 filesystems fsch resume"
    As already mentioned the configuration works within VirtualBox. When I'm trying to boot from the USB key on my real computer, I'm getting an error. Syslinux works fine and loads Linux, but Linux is complaining. Here's the log:
    :: running hoock [encrypt]
    Waiting 10 seconds for device /dev/disk/by-uuid/6aa73872-3755-4bdf-bee3-d1cd7a3fe0bf ...
    ERROR: device '/dev/mapper/main-root' not found. Skipping fschk.
    ERROR: Unable to find root device '/dev/mapper/main-root'.
    You are being dropped to a recovery shell
    I'm not getting prompted for the passphrase since the cryptdevice can not be found. But why? It can be found when I'm booting within VirtualBox. What might be different? I successfully installed other Linux distributions (but without encryption and using GRUB as bootloader) previously within VirtualBox and was able to boot from the USB key on a real machine afterwards.
    Some additional information that might help:
    Here's the "lsblk -f output" for the stick:
    sdd
    ├─sdd1 ext4 usbboot bb45e84e-842e-4209-8c44-1af3c7933389
    └─sdd2 crypto_L 6aa73872-3755-4bdf-bee3-d1cd7a3fe0bf
    When I'm running "lsblk" or "blkid" from the recovery shell after the failure, I'm getting no output. "ls /dev/sd*" returns nothing as well. The directory /dev/disk does not even exists in the recovery shell. (I'm not sure if this is normal or not.)
    Thanks for helping.
    Last edited by The Infinity (2014-08-14 20:26:06)

    I still haven't solved the problem:
    When starting the system on a machine with NVIDIA GTX 560Ti graphics card:
    - X doesn't start using startx or xinit and there are no log entries in /var/log/Xorg.*.log (as I haven't tried to start X).
    - I'm getting the message "Waiting for X server to begin accepting connections .. .. .. ..".
    - I already tried to uninstall xf86-video-nouveau and nouveau-dri with no effect.
    - Additionally: The "default terminals tty1/2/3/..." (which I'm using to start X) from have a poor resolution (I think 640x480 pixel).
    When starting the system on a virtual machine or a machine with an ATI Radeon (mobile) graphics card:
    - X starts and runs without any trouble the XFCE desktop environment.
    - Additionally: The default terminals have a proper resolution (I think the maximal resolution of the display).

  • [SOLVED]cannot share folder in home directory with SAMBA

    My problem is relatively small as I can use a workaround but I would like to be able to discern whether or not my troubles  stem from a bug or my own incompetence. 
    Basically it seems I can share just about anything I want EXCEPT for a file or folder in my home directory.  I  have two primary users on my box, root & dunce, and what I am unable to do is share "/home/dunce/shared".  I've tried quite a few different configs based on what I could find online but nothing works.  Initially I followed the SAMBA instrucions on the Arch Wiki and that was fine for other items I wanted to share.  I feel like I'm kinda'   makin' a mountain out of a molehill here but I would really like to understand WHY I can't share from "/home/dunce/shared".  I really don't think it's a problem in smb.conf but then again . . .  Any insight would be greatly appreciated.
    Last edited by Captain Dunce (2011-01-24 07:11:06)

    The option browseable if not defined is per default set to yes.
    Excerpt from The definitive guide to samba 3
    browseable: This parameter determines whether a share appears in browse lists on clients. The default value of YES causes a share to appear and is usually appropriate. You can hide a share by setting this parameter to NO; however, be aware that this setting doesn't make a share unavailable, only hidden from casual browsing.
    Another thing I stumbled upon is that samba can get confused if security=share is used. It will try different usernames until it finds one that can be used, or will deny access if none can be used. The following list is the order it tries to access the share:
    Guest, Client provided username, Prior login, Share name, Client name, User list (if defined).
    You can try to set
    guest ok = yes
    and see if that changes the behaviour. You will need
    guest account = nobody
    or something similar in you global configuration to make this work.
    Whatever user you set as guest need to exist in the samba database. And must be a existing linux username as well.
    Another option is to set the guest account in the share definition and only allow guest access.
    [share]
    path = /home/dunce/sharefolder
    browseable = yes
    writable = yes
    guest account = dunce
    guest ok = yes
    guest only = yes
    Again the username (dunce) need to exist in the samba database. Depending on your setup this can be set with the command pdbedit.
    There is a samba book available online from O'Reilly. It is a bit dated, but the info on shares should still be valid. I think chapter 6 is especially interesting for you in your scenario.
    http://oreilly.com/catalog/samba/chapte … index.html

  • Systemd doesn't umount (encrypted) /home and /tmp on shutdown

    Hi all,
    as this is my first post in this BBS, I hope I'm actually posting in the correct forum. I also did some research but couldn't really find answers.
    I have a problem with systemd on shutdown. It doesn't unmount my encrypted home partition (and does not close the LUKS partition) and the /tmp partition. The corresponding output from journalctl would be this:
    Oct 09 16:08:18 failenovo systemd[1]: Stopping Local File Systems.
    Oct 09 16:08:18 failenovo systemd[1]: Stopped target Local File Systems.
    Oct 09 16:08:18 failenovo systemd[1]: Unmounting /data...
    Oct 09 16:08:18 failenovo systemd[1]: Unmounting /boot...
    Oct 09 16:08:18 failenovo systemd[1]: Unmounting /home...
    Oct 09 16:08:18 failenovo umount[3995]: umount: /home: target is busy.
    Oct 09 16:08:18 failenovo umount[3995]: (In some cases useful info about processes that use
    Oct 09 16:08:18 failenovo umount[3995]: the device is found by lsof(8) or fuser(1))
    Oct 09 16:08:18 failenovo systemd[1]: Unmounting Temporary Directory...
    Oct 09 16:08:18 failenovo systemd[1]: home.mount mount process exited, code=exited status=32
    Oct 09 16:08:18 failenovo systemd[1]: Failed unmounting /home.
    Oct 09 16:08:18 failenovo systemd[1]: Stopping File System Check on /dev/disk/by-uuid/a9395b0a-e3f8-41d7-9feb-d433173fd5ab...
    Oct 09 16:08:18 failenovo systemd[1]: Stopped File System Check on /dev/disk/by-uuid/a9395b0a-e3f8-41d7-9feb-d433173fd5ab.
    Oct 09 16:08:18 failenovo systemd[1]: Stopping /sys/devices/virtual/block/dm-1.
    Oct 09 16:08:18 failenovo systemd[1]: Deactivated swap /dev/sda1.
    Oct 09 16:08:18 failenovo systemd[1]: Unmounted /boot.
    Oct 09 16:08:18 failenovo systemd[1]: Deactivated swap /dev/disk/by-partuuid/28e18189-6b46-40b5-82f8-d550ee3df47a.
    Oct 09 16:08:18 failenovo systemd[1]: Deactivated swap /dev/disk/by-partlabel/Linux\x20swap.
    Oct 09 16:08:18 failenovo systemd[1]: Deactivated swap /dev/disk/by-id/wwn-0x5000cca615e3f206-part1.
    Oct 09 16:08:18 failenovo systemd[1]: Deactivated swap /dev/disk/by-id/ata-HITACHI_HTS543232A7A384_E2434243JK29XK-part1.
    Oct 09 16:08:18 failenovo systemd[1]: Deactivated swap /dev/disk/by-uuid/4903864c-36f8-4f05-a722-ed726c9ae492.
    Oct 09 16:08:18 failenovo umount[3997]: umount: /tmp: target is busy.
    Oct 09 16:08:18 failenovo umount[3997]: (In some cases useful info about processes that use
    Oct 09 16:08:18 failenovo umount[3997]: the device is found by lsof(8) or fuser(1))
    Oct 09 16:08:18 failenovo systemd[1]: tmp.mount mount process exited, code=exited status=32
    Oct 09 16:08:18 failenovo systemd[1]: Failed unmounting Temporary Directory.
    Oct 09 16:08:18 failenovo systemd[1]: Unmounted /data.
    Oct 09 16:08:18 failenovo systemd[1]: Stopping Local File Systems (Pre).
    Oct 09 16:08:18 failenovo systemd[1]: Stopped target Local File Systems (Pre).
    Oct 09 16:08:18 failenovo systemd[1]: Stopping Remount Root and Kernel File Systems...
    Oct 09 16:08:18 failenovo systemd[1]: Stopped Remount Root and Kernel File Systems.
    Oct 09 16:08:18 failenovo systemd[1]: Starting Shutdown.
    Oct 09 16:08:18 failenovo systemd[1]: Reached target Shutdown.
    Oct 09 16:08:23 failenovo systemd-cryptsetup[3989]: Failed to deactivate: Device or resource busy
    Oct 09 16:08:23 failenovo systemd[1]: [email protected]: control process exited, code=exited status=1
    Oct 09 16:08:23 failenovo systemd[1]: Stopped Cryptography Setup for home.
    Oct 09 16:08:23 failenovo systemd[1]: Unit [email protected] entered failed state.
    Oct 09 16:08:23 failenovo systemd[1]: Starting Unmount All Filesystems.
    Oct 09 16:08:23 failenovo systemd[1]: Reached target Unmount All Filesystems.
    Now, with the usual sysv-init this wouldn't be a problem but with systemd (which I'm new to) this poses a problem. I don't know where to start debugging this issue, really. I haven't found a way to run a script directly before and after the umount.target units starts so I can't really see which files are open or what the problem is at this point.
    Is it possible to drop to a shell on such errors and inspect the problem manually? Or does anyone have a suggestion why systemd doesn't want to unmount these filesystems?
    Here's my /etc/fstab:
    # <file system> <dir> <type> <options> <dump> <pass>
    # /dev/mapper/root LABEL=ROOT
    UUID=27fed041-7765-4f63-a895-a7592113165b / ext4 rw,relatime,data=ordered,discard 0 1
    # /dev/mapper/home LABEL=HOME
    UUID=a9395b0a-e3f8-41d7-9feb-d433173fd5ab /home ext4 rw,relatime,data=ordered,discard 0 2
    # /dev/sdb1
    UUID=1573-8C74 /boot/ vfat rw,relatime,fmask=0022,dmask=0022,codepage=437,iocharset=iso8859-1,shortname=mixed,errors=remount-ro 0 2
    # /dev/sda1 LABEL=SWAP
    UUID=f5097167-6e12-4548-8bef-5f83942a1848 none swap defaults 0 0
    # /dev/sda2 LABEL=DATA
    UUID=dffd1518-d3b5-4d05-8b13-76e6fd841963 /data ext4 defaults 0 2
    and my /etc/crypttab:
    # <name> <device> <password> <options>
    home UUID=01f3da5d-1ca0-4bf2-b5a1-cfe69c597707 /etc/keys/home.key luks,discard
    If you need more information, please do tell! Thanks in advance.
    Cheers,
    gegenschall

    I think the /home part of the issue for me is at least partially due to how I have mpd configured.  I start it with my X session and it persists after I log out, keeping a few files in my home folder open.  If I make sure it is not running, log out to LightDM, and use its menu to reboot, I do not get a journal message about /home.  If I kill mpd, but instead issue a `systemctl reboot/poweroff` command from a terminal in X, the problem returns.  Is this normal?  I guess I expected everything to be automatically cleaned up.
    /tmp, on the other hand, remains a mystery.  If I remove it from my /etc/fstab - to use the default tmp.mount (tmpfs) systemd provides - the problem goes away.  But if I keep it as is, and do something silly like replace /bin/umount with this:
    #!/bin/sh
    /bin/test "$1" = "/tmp" && /bin/date -Ins >> /umount-tmp.log
    /bin/test "$1" = "/tmp" && /bin/lsof /tmp >> /umount-tmp.log
    /bin/umount.real "$@"
    all I get is a list of times.
    Also, I tried following the steps here (Shutdown Completes Eventually), but the output mostly mirrors what I get from journalctl:
    [ 219.132058] systemd[1]: Stopping Local File Systems.
    [ 219.132062] systemd[1]: local-fs.target changed active -> dead
    [ 219.132066] systemd[1]: Job local-fs.target/stop finished, result=done
    [ 219.132091] systemd[1]: Stopped target Local File Systems.
    [ 219.132103] systemd[1]: Unmounting /home...
    [ 219.132136] systemd[1]: About to execute: /bin/umount /home
    [ 219.132329] systemd[1]: Forked /bin/umount as 908
    [ 219.132402] systemd[1]: home.mount changed mounted -> unmounting
    [ 219.132427] systemd[1]: Unmounting /storage...
    [ 219.132480] systemd[1]: About to execute: /bin/umount /storage
    [ 219.132735] systemd[1]: Forked /bin/umount as 909
    [ 219.132805] systemd[1]: storage.mount changed mounted -> unmounting
    [ 219.132825] systemd[1]: Unmounting /tmp...
    [ 219.132872] systemd[1]: About to execute: /bin/umount /tmp
    [ 219.133047] systemd[1]: Forked /bin/umount as 910
    [ 219.133109] systemd[1]: tmp.mount changed mounted -> unmounting
    [ 219.133136] systemd[1]: Unmounting /boot...
    [ 219.133190] systemd[1]: About to execute: /bin/umount /boot
    [ 219.133355] systemd[909]: Executing: /bin/umount /storage
    [ 219.133388] systemd[1]: Forked /bin/umount as 911
    [ 219.133452] systemd[1]: boot.mount changed mounted -> unmounting
    [ 219.133676] systemd[1]: Got D-Bus request: org.freedesktop.DBus.Local.Disconnected() on /org/freedesktop/DBus/Local
    [ 219.134256] systemd[906]: Executing: /usr/lib/systemd/systemd-random-seed save
    [ 219.134550] systemd[908]: Executing: /bin/umount /home
    [ 219.135143] systemd[1]: Received SIGCHLD from PID 906 (systemd-random-).
    [ 219.135170] systemd[1]: Got SIGCHLD for process 906 (systemd-random-)
    [ 219.135222] systemd[1]: Child 906 died (code=exited, status=0/SUCCESS)
    [ 219.135226] systemd[1]: Child 906 belongs to systemd-random-seed.service
    [ 219.135235] systemd[1]: systemd-random-seed.service: control process exited, code=exited status=0
    [ 219.135292] systemd[907]: Executing: /sbin/swapoff /dev/dm-2
    [ 219.135462] systemd[910]: Executing: /bin/umount /tmp
    [ 219.135487] systemd[1]: systemd-random-seed.service got final SIGCHLD for state stop
    [ 219.135528] systemd[1]: systemd-random-seed.service changed stop -> dead
    [ 219.135582] systemd[911]: Executing: /bin/umount /boot
    [ 219.135622] systemd[1]: Job systemd-random-seed.service/stop finished, result=done
    [ 219.135666] systemd[1]: Stopped Load/Save Random Seed.
    [ 219.135695] systemd[1]: Unmounting /var...
    [ 219.135730] systemd[1]: About to execute: /bin/umount /var
    [ 219.135974] systemd[1]: Forked /bin/umount as 914
    [ 219.136050] systemd[1]: var.mount changed mounted -> unmounting
    [ 219.136290] systemd[1]: Accepted connection on private bus.
    [ 219.136332] systemd[1]: Accepted connection on private bus.
    [ 219.136529] systemd[1]: Got D-Bus request: org.freedesktop.systemd1.Agent.Released() on /org/freedesktop/systemd1/agent
    [ 219.136584] systemd[914]: Executing: /bin/umount /var
    [ 219.136890] systemd[1]: Got D-Bus request: org.freedesktop.systemd1.Agent.Released() on /org/freedesktop/systemd1/agent
    [ 219.137193] systemd[1]: Got D-Bus request: org.freedesktop.DBus.Local.Disconnected() on /org/freedesktop/DBus/Local
    [ 219.137222] systemd[1]: Got D-Bus request: org.freedesktop.DBus.Local.Disconnected() on /org/freedesktop/DBus/Local
    [ 219.175076] systemd[1]: Received SIGCHLD from PID 754 (sudo).
    [ 219.175102] systemd[1]: Got SIGCHLD for process 754 (sudo)
    [ 219.175155] systemd[1]: Child 754 died (code=exited, status=129/n/a)
    [ 219.200239] systemd[1]: Received SIGCHLD from PID 910 (umount).
    [ 219.200267] systemd[1]: Got SIGCHLD for process 908 (umount)
    [ 219.200338] systemd[1]: Child 908 died (code=exited, status=32/n/a)
    [ 219.200342] systemd[1]: Child 908 belongs to home.mount
    [ 219.200347] systemd[1]: home.mount mount process exited, code=exited status=32
    [ 219.200357] systemd[1]: home.mount changed unmounting -> mounted
    [ 219.200362] systemd[1]: Job home.mount/stop finished, result=failed
    [ 219.200407] systemd[1]: Failed unmounting /home.
    [ 219.200454] systemd[1]: Got SIGCHLD for process 910 (umount)
    [ 219.200524] systemd[1]: Child 910 died (code=exited, status=32/n/a)
    [ 219.200527] systemd[1]: Child 910 belongs to tmp.mount
    [ 219.200532] systemd[1]: tmp.mount mount process exited, code=exited status=32
    [ 219.200540] systemd[1]: tmp.mount changed unmounting -> mounted
    [ 219.200544] systemd[1]: Job tmp.mount/stop finished, result=failed
    [ 219.200571] systemd[1]: Failed unmounting /tmp.
    [ 219.200607] systemd[1]: Got SIGCHLD for process 914 (umount)
    [ 219.200666] systemd[1]: Child 914 died (code=exited, status=32/n/a)
    [ 219.200669] systemd[1]: Child 914 belongs to var.mount
    [ 219.200673] systemd[1]: var.mount mount process exited, code=exited status=32
    [ 219.200681] systemd[1]: var.mount changed unmounting -> mounted
    [ 219.200685] systemd[1]: Job var.mount/stop finished, result=failed
    [ 219.200711] systemd[1]: Failed unmounting /var.
    [ 219.200737] systemd[1]: Stopping File System Check on /dev/disk/by-uuid/98691163-fffa-4321-984c-3ba237083524...
    [ 219.200763] systemd[1]: systemd-fsck@dev-disk-by\x2duuid-98691163\x2dfffa\x2d4321\x2d984c\x2d3ba237083524.service changed exited -> dead
    [ 219.200769] systemd[1]: Job systemd-fsck@dev-disk-by\x2duuid-98691163\x2dfffa\x2d4321\x2d984c\x2d3ba237083524.service/stop finished, result=done
    [ 219.200797] systemd[1]: Stopped File System Check on /dev/disk/by-uuid/98691163-fffa-4321-984c-3ba237083524.
    [ 219.200816] systemd[1]: Redirecting stop request from dev-disk-by\x2duuid-98691163\x2dfffa\x2d4321\x2d984c\x2d3ba237083524.device to sys-devices-virtual-block-dm\x2d6.device.
    [ 219.200823] systemd[1]: Stopping /sys/devices/virtual/block/dm-6.
    [ 219.200876] systemd[1]: Accepted connection on private bus.
    [ 219.201099] systemd[1]: Got D-Bus request: org.freedesktop.systemd1.Agent.Released() on /org/freedesktop/systemd1/agent
    [ 219.201186] systemd[1]: Got D-Bus request: org.freedesktop.DBus.Local.Disconnected() on /org/freedesktop/DBus/Local
    [ 219.201483] systemd[1]: Accepted connection on private bus.
    [ 219.201642] systemd[1]: Got D-Bus request: org.freedesktop.systemd1.Agent.Released() on /org/freedesktop/systemd1/agent
    [ 219.201716] systemd[1]: Got D-Bus request: org.freedesktop.DBus.Local.Disconnected() on /org/freedesktop/DBus/Local
    [ 219.204043] systemd[1]: Accepted connection on private bus.
    [ 219.204142] systemd[1]: Got D-Bus request: org.freedesktop.systemd1.Agent.Released() on /org/freedesktop/systemd1/agent
    [ 219.204219] systemd[1]: Got D-Bus request: org.freedesktop.DBus.Local.Disconnected() on /org/freedesktop/DBus/Local
    [ 219.234497] systemd[1]: dev-mapper-linux\x2dswap.swap changed active -> dead
    [ 219.234606] systemd[1]: Job dev-mapper-linux\x2dswap.swap/stop finished, result=done
    [ 219.234657] systemd[1]: Deactivated swap /dev/mapper/linux-swap.
    [ 219.234674] systemd[1]: dev-linux-swap.swap changed active -> dead
    [ 219.234751] systemd[1]: Job dev-linux-swap.swap/stop finished, result=done
    [ 219.234805] systemd[1]: Deactivated swap /dev/linux/swap.
    [ 219.234815] systemd[1]: dev-disk-by\x2did-dm\x2duuid\x2dLVM\x2dDevEGGWf3oc8GE2g06c6XaLVUQEgo9cTTSwqNIhBSQfWKqAKYdL5kKqo0rCZ38xZ.swap changed active -> dead
    [ 219.234970] systemd[1]: Job dev-disk-by\x2did-dm\x2duuid\x2dLVM\x2dDevEGGWf3oc8GE2g06c6XaLVUQEgo9cTTSwqNIhBSQfWKqAKYdL5kKqo0rCZ38xZ.swap/stop finished, result=done
    [ 219.235007] systemd[1]: Deactivated swap /dev/disk/by-id/dm-uuid-LVM-DevEGGWf3oc8GE2g06c6XaLVUQEgo9cTTSwqNIhBSQfWKqAKYdL5kKqo0rCZ38xZ.
    [ 219.235017] systemd[1]: dev-disk-by\x2did-dm\x2dname\x2dlinux\x2dswap.swap changed active -> dead
    [ 219.235097] systemd[1]: Job dev-disk-by\x2did-dm\x2dname\x2dlinux\x2dswap.swap/stop finished, result=done
    [ 219.235126] systemd[1]: Deactivated swap /dev/disk/by-id/dm-name-linux-swap.
    [ 219.235135] systemd[1]: dev-disk-by\x2duuid-f8b1e59e\x2d9804\x2d44f0\x2daf79\x2d66810ee49206.swap changed active -> dead
    [ 219.235214] systemd[1]: Job dev-disk-by\x2duuid-f8b1e59e\x2d9804\x2d44f0\x2daf79\x2d66810ee49206.swap/stop finished, result=done
    [ 219.235244] systemd[1]: Deactivated swap /dev/disk/by-uuid/f8b1e59e-9804-44f0-af79-66810ee49206.
    [ 219.235297] systemd[1]: Received SIGCHLD from PID 907 (swapoff).
    [ 219.235323] systemd[1]: Got SIGCHLD for process 907 (swapoff)
    [ 219.235390] systemd[1]: Child 907 died (code=exited, status=0/SUCCESS)
    [ 219.235394] systemd[1]: Child 907 belongs to dev-dm\x2d2.swap
    [ 219.235399] systemd[1]: dev-dm\x2d2.swap swap process exited, code=exited status=0
    [ 219.235410] systemd[1]: dev-dm\x2d2.swap changed deactivating -> dead
    [ 219.235956] systemd[1]: Job dev-dm\x2d2.swap/stop finished, result=done
    [ 219.236044] systemd[1]: Deactivated swap /dev/dm-2.
    [ 219.236131] systemd[1]: Got SIGCHLD for process 911 (umount)
    [ 219.236192] systemd[1]: Child 911 died (code=exited, status=0/SUCCESS)
    [ 219.236196] systemd[1]: Child 911 belongs to boot.mount
    [ 219.236201] systemd[1]: boot.mount mount process exited, code=exited status=0
    [ 219.236210] systemd[1]: boot.mount changed unmounting -> dead
    [ 219.236294] systemd[1]: Job boot.mount/stop finished, result=done
    [ 219.236322] systemd[1]: Unmounted /boot.
    [ 219.236360] systemd[1]: Received SIGCHLD from PID 911 (n/a).
    [ 219.236413] systemd[1]: Accepted connection on private bus.
    [ 219.236551] systemd[1]: Got D-Bus request: org.freedesktop.systemd1.Agent.Released() on /org/freedesktop/systemd1/agent
    [ 219.237196] systemd[1]: Got D-Bus request: org.freedesktop.DBus.Local.Disconnected() on /org/freedesktop/DBus/Local
    [ 219.237321] systemd[1]: Accepted connection on private bus.
    [ 219.237463] systemd[1]: Got D-Bus request: org.freedesktop.systemd1.Agent.Released() on /org/freedesktop/systemd1/agent
    [ 219.237814] systemd[1]: Got D-Bus request: org.freedesktop.DBus.Local.Disconnected() on /org/freedesktop/DBus/Local
    [ 219.238324] systemd[1]: Received SIGCHLD from PID 909 (umount).
    [ 219.238348] systemd[1]: Got SIGCHLD for process 909 (umount)
    [ 219.238404] systemd[1]: Child 909 died (code=exited, status=0/SUCCESS)
    [ 219.238407] systemd[1]: Child 909 belongs to storage.mount
    [ 219.238412] systemd[1]: storage.mount mount process exited, code=exited status=0
    [ 219.238420] systemd[1]: storage.mount changed unmounting -> dead
    [ 219.238509] systemd[1]: Job storage.mount/stop finished, result=done
    [ 219.238540] systemd[1]: Unmounted /storage.
    [ 219.238556] systemd[1]: Stopping Local File Systems (Pre).
    [ 219.238562] systemd[1]: local-fs-pre.target changed active -> dead
    [ 219.238566] systemd[1]: Job local-fs-pre.target/stop finished, result=done
    [ 219.238592] systemd[1]: Stopped target Local File Systems (Pre).
    [ 219.238604] systemd[1]: Stopping Remount Root and Kernel File Systems...
    [ 219.238627] systemd[1]: systemd-remount-fs.service changed exited -> dead
    [ 219.238631] systemd[1]: Job systemd-remount-fs.service/stop finished, result=done
    [ 219.238656] systemd[1]: Stopped Remount Root and Kernel File Systems.
    [ 219.238673] systemd[1]: Starting Shutdown.
    [ 219.238676] systemd[1]: shutdown.target changed dead -> active
    [ 219.238679] systemd[1]: Job shutdown.target/start finished, result=done
    [ 219.238703] systemd[1]: Reached target Shutdown.
    [ 219.239263] systemd[1]: Accepted connection on private bus.
    [ 219.239382] systemd[1]: Got D-Bus request: org.freedesktop.systemd1.Agent.Released() on /org/freedesktop/systemd1/agent
    [ 219.239752] systemd[1]: Got D-Bus request: org.freedesktop.DBus.Local.Disconnected() on /org/freedesktop/DBus/Local
    [ 219.630816] systemd[1]: Received SIGCHLD from PID 486 (at-spi-bus-laun).
    [ 219.630840] systemd[1]: Got SIGCHLD for process 486 (at-spi-bus-laun)
    [ 219.630896] systemd[1]: Child 486 died (code=exited, status=0/SUCCESS)
    [ 219.668697] systemd[1]: Received SIGCHLD from PID 449 (X).
    [ 219.668725] systemd[1]: Got SIGCHLD for process 449 (X)
    [ 219.668781] systemd[1]: Child 449 died (code=exited, status=0/SUCCESS)
    [ 219.669379] systemd[1]: Accepted connection on private bus.
    [ 219.669545] systemd[1]: Got D-Bus request: org.freedesktop.systemd1.Agent.Released() on /org/freedesktop/systemd1/agent
    [ 219.669606] systemd[1]: lightdm.service: cgroup is empty
    [ 219.669636] systemd[1]: Got D-Bus request: org.freedesktop.DBus.Local.Disconnected() on /org/freedesktop/DBus/Local
    [ 220.420041] systemd[1]: Received SIGCHLD from PID 845 (sleep).
    [ 220.420064] systemd[1]: Got SIGCHLD for process 845 (sleep)
    [ 220.420103] systemd[1]: Child 845 died (code=exited, status=0/SUCCESS)
    [ 221.914117] systemd[1]: Received SIGCHLD from PID 545 (dbus-launch).
    [ 221.914141] systemd[1]: Got SIGCHLD for process 545 (dbus-launch)
    [ 221.914184] systemd[1]: Child 545 died (code=exited, status=0/SUCCESS)
    [ 221.914458] systemd[1]: Received SIGCHLD from PID 483 (dbus-launch).
    [ 221.914486] systemd[1]: Got SIGCHLD for process 483 (dbus-launch)
    [ 221.914529] systemd[1]: Child 483 died (code=exited, status=0/SUCCESS)
    [ 221.915102] systemd[1]: Accepted connection on private bus.
    [ 221.915222] systemd[1]: Got D-Bus request: org.freedesktop.systemd1.Agent.Released() on /org/freedesktop/systemd1/agent
    [ 221.915328] systemd[1]: Got D-Bus request: org.freedesktop.DBus.Local.Disconnected() on /org/freedesktop/DBus/Local
    [ 223.957616] systemd[1]: Received SIGCHLD from PID 904 (systemd-cryptse).
    [ 223.957639] systemd[1]: Got SIGCHLD for process 904 (systemd-cryptse)
    [ 223.957707] systemd[1]: Child 904 died (code=exited, status=1/FAILURE)
    [ 223.957712] systemd[1]: Child 904 belongs to systemd-cryptsetup@crypt\x2dhome.service
    [ 223.957720] systemd[1]: systemd-cryptsetup@crypt\x2dhome.service: control process exited, code=exited status=1
    [ 223.957782] systemd[1]: systemd-cryptsetup@crypt\x2dhome.service got final SIGCHLD for state stop
    [ 223.957818] systemd[1]: systemd-cryptsetup@crypt\x2dhome.service changed stop -> failed
    [ 223.957904] systemd[1]: Job systemd-cryptsetup@crypt\x2dhome.service/stop finished, result=done
    [ 223.957917] systemd[1]: Stopped Cryptography Setup for crypt-home.
    [ 223.957928] systemd[1]: Unit systemd-cryptsetup@crypt\x2dhome.service entered failed state.
    [ 223.958243] systemd[1]: Accepted connection on private bus.
    [ 223.958397] systemd[1]: Got D-Bus request: org.freedesktop.systemd1.Agent.Released() on /org/freedesktop/systemd1/agent
    [ 223.958509] systemd[1]: Got D-Bus request: org.freedesktop.DBus.Local.Disconnected() on /org/freedesktop/DBus/Local
    [ 224.016365] systemd[1]: Received SIGCHLD from PID 905 (systemd-cryptse).
    [ 224.016390] systemd[1]: Got SIGCHLD for process 905 (systemd-cryptse)
    [ 224.016447] systemd[1]: Child 905 died (code=exited, status=1/FAILURE)
    [ 224.016451] systemd[1]: Child 905 belongs to systemd-cryptsetup@crypt\x2dlinux.service
    [ 224.016457] systemd[1]: systemd-cryptsetup@crypt\x2dlinux.service: control process exited, code=exited status=1
    [ 224.016529] systemd[1]: systemd-cryptsetup@crypt\x2dlinux.service got final SIGCHLD for state stop
    [ 224.016565] systemd[1]: systemd-cryptsetup@crypt\x2dlinux.service changed stop -> failed
    [ 224.016661] systemd[1]: Job systemd-cryptsetup@crypt\x2dlinux.service/stop finished, result=done
    [ 224.016676] systemd[1]: Stopped Cryptography Setup for crypt-linux.
    [ 224.016687] systemd[1]: Unit systemd-cryptsetup@crypt\x2dlinux.service entered failed state.
    [ 224.016703] systemd[1]: Starting Unmount All Filesystems.
    [ 224.016707] systemd[1]: umount.target changed dead -> active
    [ 224.016711] systemd[1]: Job umount.target/start finished, result=done
    [ 224.016717] systemd[1]: Reached target Unmount All Filesystems.
    [ 224.016728] systemd[1]: Starting Final Step.
    [ 224.016731] systemd[1]: final.target changed dead -> active
    [ 224.016734] systemd[1]: Job final.target/start finished, result=done
    [ 224.016742] systemd[1]: Reached target Final Step.
    [ 224.016754] systemd[1]: Starting Reboot...
    [ 224.016866] systemd[1]: About to execute: /usr/bin/systemctl --force reboot
    [ 224.017057] systemd[1]: Forked /usr/bin/systemctl as 928
    [ 224.017193] systemd[1]: systemd-reboot.service changed dead -> start
    [ 224.018230] systemd[928]: Executing: /usr/bin/systemctl --force reboot
    [ 224.018328] systemd[1]: Accepted connection on private bus.
    [ 224.018435] systemd[1]: Got D-Bus request: org.freedesktop.systemd1.Agent.Released() on /org/freedesktop/systemd1/agent
    [ 224.018504] systemd[1]: Got D-Bus request: org.freedesktop.DBus.Local.Disconnected() on /org/freedesktop/DBus/Local
    [ 224.019495] systemd[1]: Accepted connection on private bus.
    [ 224.019712] systemd[1]: Got D-Bus request: org.freedesktop.systemd1.Manager.Reboot() on /org/freedesktop/systemd1
    [ 224.019734] systemd[1]: Shutting down.
    [ 224.023022] systemd[1]: Hardware watchdog 'NV_TCO', version 0
    [ 224.023031] systemd[1]: Failed to set timeout to 600s: Invalid argument
    [ 224.023033] nv_tco: Unexpected close, not stopping watchdog!
    [ 225.162099] systemd-journald[215]: Received SIGTERM
    [ 225.515048] EXT4-fs (dm-6): re-mounted. Opts: (null)
    [ 225.687382] EXT4-fs (dm-4): re-mounted. Opts: (null)
    [ 225.796081] EXT4-fs (dm-3): re-mounted. Opts: (null)
    [ 225.915129] EXT4-fs (dm-1): re-mounted. Opts: (null)
    [ 225.919881] EXT4-fs (dm-1): re-mounted. Opts: (null)
    [ 225.919911] EXT4-fs (dm-1): re-mounted. Opts: (null)
    [ 226.283469] EXT4-fs (dm-1): re-mounted. Opts: data=ordered

  • [solved] kernel 2.6.27 - open LUKS encrypted root partition fails

    Hi,
    after updating to kernel 2.6.27 the passphrase for my LUKS encrypted root partition does not work anymore.
    I get this error messages:
    Enter LUKS passphrase:
    device-mapper: table: 254:0 crypt: Error allocating crypto tfm
    device-mapper: ioctl: error adding target to table
    device-mapper: ioctl: device doesn't appear to be in the dev hash table.
    Command failed: No key available with this passphrase.
    Enter LUKS passphrase:
    With a old (2.6.25) vanilla kernel it works.
    any ideas?
    EDIT
    Solved.
    The Problem was that I had this line in my mkinitcpio.conf to get rid of the padlock-error-message at boot.
    #CRYPTO_MODULES="aes_i586 aes_generic sha256_generic"
    With kernel 2.6.27 there are new / more modules needed to open the LUKS encryptet root partition.
    So I removed the line from mkinitcpio.conf and deletet the padlock modules in /lib/modules/2.6.27-ARCH before regenarating the initrd image.
    Thanks to GerBra for the tip.
    Last edited by SiD (2008-10-22 11:41:56)

    I'm not shure, but think ... yes.

  • Solved: I cannot manage (bring online, initialize, partition, format, or write to) a VHDX hard drive once it has "Enable Virtual Hard Disk Sharing" enabled.

    Hello,
    Issue:
    On a Virtual Machine with a secondary VHDX attached, I cannot manage (bring online, initialize, partition, format, or write to) the VHDX hard drive once it has "Enable Virtual Hard Disk Sharing (VHD Sharing)" enabled.
    Questions:
    Should I be able to manage (bring online, initialize, partition, format, and write to) a VHDX hard drive once it has VHD Sharing enabled? If I should be able to manage it, what am I missing?
    Topography:
    One SuperMicro Cluster In a Box (CIB) with 2012 R2 Data Center on each node. Microsoft Failover Cluster installed and working on each node. The Failover Cluster Servers on each host passes all cluster validation tests. Two Hyper-V 2012 R2 Data Center Virtual
    Machine (VM) servers, one on each node. 1 common Cluster Shared Volume (CSV) and 1 Generation 2 Scale-Out File Server (SOFS) shared volume both Resilient File System (REFS) formatted. One 5 Gigabit (Gb) Virtual Hard Drive Type X (VHDX) file on the CSV and/or
    SOFS. Integrity bit and read only turned off on VHDX file.
    Each of the two Hyper-V VMs have one 127Gb VHDX Generation 2 primary hard drive and 1 VHDX secondary hard drive attached, both on SCSI Controller #1.
    Background:
    If I start VM1 without the VHD Sharing enabled on the secondary hard drive, I can bring the drive online, initialize, partition, format, and write to the drive.
    If I enable VHD Sharing, I can no longer modify the drive in Disk Management in any way. With or without VM2 running.
    Both VMs and the CSV and SOFS are on the same host cluster server, or not, no difference…
    The VHDX is referenced either by the CSV name C:\ClusterStorage\Volume1\TEST1.VHDX
     or a Shared Folder name
    \\sharedfolder\folder\Test1.VHDX .
    If I start VM1 with VHD Sharing disabled and I format the drive, then shut down and enable VHD Sharing, the drive is offline and requests initialization which fails with an "I/O device error", every other attempt to manage the drive fails with
    the same "I/O device error", error.
    Events:
    VDS fails to write boot code on a disk during clean operation. Error code: 8007045D@02070008
    Log Name:      System
    Source:        Virtual Disk Service
    Date:          3/3/2015 11:39:18 AM
    Event ID:      10
    Task Category: None
    Level:         Error
    Keywords:      Classic
    User:          N/A
    Computer:      Server1.Domain.local
    Description:
    VDS fails to write boot code on a disk during clean operation. Error code: 8007045D@02070008
    Event Xml:
    <Event xmlns="http://schemas.microsoft.com/win/2004/08/events/event">
      <System>
        <Provider Name="Virtual Disk Service" />
        <EventID Qualifiers="49664">10</EventID>
        <Level>2</Level>
        <Task>0</Task>
        <Keywords>0x80000000000000</Keywords>
        <TimeCreated SystemTime="2015-03-03T19:39:18.000000000Z" />
        <EventRecordID>27318</EventRecordID>
        <Channel>System</Channel>
        <Computer> Server1.Domain.local </Computer>
        <Security />
      </System>
      <EventData>
        <Data>8007045D@02070008</Data>
      </EventData>
    </Event>
    AND
    Log Name:      System
    Source:        disk
    Date:          3/3/2015 12:16:42 PM
    Event ID:      153
    Task Category: None
    Level:         Warning
    Keywords:      Classic
    User:          N/A
    Computer:      Server1.Domain.local
    Description:
    The IO operation at logical block address 0x0 for Disk 1 (PDO name: \Device\MPIODisk1) was retried.
    Event Xml:
    <Event xmlns="http://schemas.microsoft.com/win/2004/08/events/event">
      <System>
        <Provider Name="disk" />
        <EventID Qualifiers="32772">153</EventID>
        <Level>3</Level>
        <Task>0</Task>
        <Keywords>0x80000000000000</Keywords>
        <TimeCreated SystemTime="2015-03-03T20:16:42.017090000Z" />
        <EventRecordID>27333</EventRecordID>
        <Channel>System</Channel>
        <Computer>Server1.Domain.local</Computer>
        <Security />
      </System>
      <EventData>
        <Data>\Device\Harddisk1\DR1</Data>
        <Data>0x0</Data>
        <Data>1</Data>
        <Data>\Device\MPIODisk1</Data>
        <Binary>0F01040004002C00000000009900048000000000000000000000000000000000000000000000000000020488</Binary>
      </EventData>
    </Event>
    Thanks again for any help,
    Robert

    Hi All,
    I had to buy a Willy Wonka bar and spend a golden ticket to get an answer to this one.
    We found that the default LogicalSectorSizeBytes of a VHDX is 512b. It needs to be 4kb.
    The Host drive doesn't seem to matter CSV or SOFS. Below is a way to create a VHDX with the correct LogicalSectorSizeBytes.
    In Power Shell, type --> New-VHD -Path C:\ClusterStorage\Volume4\Cluster2DataDisks\Cluster2Disk1.vhdx -SizeBytes 200Gb -PhysicalSectorSizeBytes 4kb -LogicalSectorSizeBytes 4kb
    Attach the resulting file to your guest cluster servers and set the Enable Virtual Hard Disk Sharing option on both server. You should now be able to bring the drives on-line and initialize them. They will also add to the guest cluster pool.
    Change the size, path and file name above to fit your Cluster Servers configuration.
    Thank You 
    Sachin Kumar Support Engineer | Windows Server Setup Team | Microsoft Enterprise Platform for finding the answer to this one.
    Hope this helps others.
    Robert

  • [SOLVED] error when execute a python script in home partition

    Friends,
       After of install the Arch in my notebook (note: "/" and "/home" in separated partition) if I open a terminal/shell and try execute a python program/script in the /home partition I receive many erros and the program don't run:
    [leandro@professionalit ~]$ alacarte
    'import site' failed; use -v for traceback
    Traceback (most recent call last):
    File "/usr/bin/alacarte", line 22, in <module>
    from Alacarte.MainWindow import MainWindow
    ImportError: No module named Alacarte.MainWindow
    [leandro@professionalit ~]$
    [leandro@professionalit ~]$ dropbox start
    'import site' failed; use -v for traceback
    Traceback (most recent call last):
    File "/usr/bin/dropbox", line 26, in <module>
    import optparse
    File "/usr/lib/python2.6/optparse.py", line 75, in <module>
    import sys, os
    File "os.py", line 2, in <module>
    import socket
    File "/usr/lib/python2.6/socket.py", line 92, in <module>
    __all__.extend(os._get_exports_list(_socket))
    AttributeError: 'module' object has no attribute '_get_exports_list'
    But, if I go to another partition, for example, the folder opt in partition / (/opt) and try execute the program it run OK.
    Any idea ?
    Best regards,
    Leandro.
    Last edited by LeandroTiger (2010-05-21 23:02:29)

    [leandro@professionalit ~]$ pwd
    /home/leandro
    [leandro@professionalit ~]$ python
    'import site' failed; use -v for traceback
    Python 2.6.5 (r265:79063, Apr 1 2010, 05:22:20)
    [GCC 4.4.3 20100316 (prerelease)] on linux2
    Type "help", "copyright", "credits" or "license" for more information.
    >>> import sys
    >>> print sys.path
    ['', '', '/usr/lib/openoffice/basis-link/program/', '/usr/lib/python26.zip', '/usr/lib/python2.6/', '/usr/lib/python2.6/plat-linux2', '/usr/lib/python2.6/lib-tk', '/usr/lib/python2.6/lib-old', '/usr/lib/python2.6/lib-dynload']
    >>> import site
    Traceback (most recent call last):
    File "<stdin>", line 1, in <module>
    File "/usr/lib/python2.6/site.py", line 62, in <module>
    import os
    File "os.py", line 2, in <module>
    import socket
    File "/usr/lib/python2.6/socket.py", line 92, in <module>
    __all__.extend(os._get_exports_list(_socket))
    AttributeError: 'module' object has no attribute '_get_exports_list'
    >>> import Alacarte
    Traceback (most recent call last):
    File "<stdin>", line 1, in <module>
    ImportError: No module named Alacarte
    >>>

  • Home folder is 22.6 MB. Home partition is 30 GB. What canIdo[SOLVED]

    Hello every one.  I installed Arch on an old laptop.  The home partition is 30 GB.  I then created 2 user accounts.  Both have folder sizes of only 22.6 MB.  Yet the home partition is clearly bigger. I have confirmed the partition is mounted at the right location.  (Fstab and Gparted). Is there any way to expand them? I have searched the forums and have found nothing.
    Last edited by ryanvade (2013-02-24 02:19:14)

    I don't really know of a way (short of creating separate partitions) to limit each user to 15GB a piece.  I just don't that you can simply impose limitations like that on a given subdirectory.
    So on your /home partition, can you create a new directory (folder in your parlance) and put some crap in there that exceeds this magical 22.6MB?  Maybe create a directory like /home/test as root, and then again as root try and put some stuff there that exceeds this limitation?  If you can do it as UID 0, then you are running into a permissions problem of some kind.
    I think without more information though, this is really not a solvable situation, as it is rather hard to decipher what you are actually experiencing.

  • [solved] Encrypted Home

    I played two hours two day i think to get a encrypted home ;D
    So that's what i got before:
    I saw an article to encryptfs in the wiki which was linked to http://sysphere.org/~anrxc/j/articles/e … index.html,
    a very helpfull guide, but when i added the /etc/mtab line to /etc/fstab and rebooted the system always hang up at mounting the stuff, what did i made wrong?
    I have an Lightdm Setup, created today,
    How could I get an encrypted Home which would be mounted, when I log in? Or when the System Boots up? I got it mounted manually, but not automatically
    Another thing I saw in a Ubuntu wiki was
    adduser --encrypt-home <User>
    So, would be very cool If someone could help me guys, and remember you rocks.
    Last edited by check (2012-06-25 19:26:57)

    a very helpfull guide, but when i added the /etc/mtab line to /etc/fstab and rebooted the system always hang up at mounting the stuff, what did i made wrong?
    I wrote replicate it, not just copy/paste, and then I added an example. One key option is noauto so system doesn't attempt to mount it early in the boot, there is nothing in the kernel keyring at that time.
    How could I get an encrypted Home which would be mounted, when I log in? Or when the System Boots up? I got it mounted manually, but not automatically
    It's the same way as any other login manager. You have to come up with your own solution. Be it pam_mount, be it your shell initialization which does it, be it the login manager it self through some functionality which allows executing commands after a succesful login.

  • [solved] fsck and encrypted /home

    Hello,
    After testing arch for some weeks, I made the "final" switch this week-end: I moved my LUKS encrypted /home from ubuntu tu arch. During this process I had a problem with fsck on my encrypted /home. I put 0 in /etc/stab to disable fsck:
    /dev/mapper/home /home ext3 defaults 0 0
    So my question is: is it possible to activate fsck on my /home at boot time ? Or should I let this as it is ?
    Thanks,
    Last edited by boulde (2009-10-06 07:53:06)

    I don't remember exactly but there was fsck in the error message during the boot, it was not possible to boot. But I have just tested again with fsck and it works well !
    So this error was maybe not due to fsck (I had various issues with crypttab options, qwerty/azerty passphrase, etc.)  ... but I remember that before deactivating fsck the system was not booting, after it was.
    Anyway, now it works :-)

  • Cannot install windows xp home edition w/sp3 into my mac pro mac os 10.6.2

    cannot install windows xp home edition w/sp3 into my mac pro mac os 10.6.2. I followed the instructions step by step but it does let me install if fully when asks me to fully install it says it cannot where to install.

    Hi,
    how much diskspace did you assign to the Windows partition ?
    And did you do the reformating of the WIndows partition as described on pages 8-10 of the BootCamp Installation Guide ?
    In your first post you mentioned 'fully install' twice. Any chance that the XP disc you use is an Upgrade disc and not a full retail/OEM one ?
    Check with the label on the disc because such XP upgrade disc are not useable with BootCamp.
    Regards
    Stefan

  • Cannot save files to home on solaris amd64

    Hello,
    a weird problem occurs after installing Reader 9.1 for Solaris 10/11 amd64: I cannot save to my home directory
    /home/user (nor can other users save to their /home/user). This directory is mounted via NFS, but I can save into
    another NFS mounted directory mounted with exactly the same mount options. The error is: "The disk you were
    saving to or the disk used for temporary space is full....." . Which isn't exactly true, since the /home/user disk has
    2.1 TB free (it's ZFS), and the /tmp (which is also what $TMPDIR is pointing to) has 42 GB free (and I can save to /tmp),
    whereas the other mounted filesystem I can save to only has 110 GB free.
    So I suspect that the large free size of the /home/user directory is not resolved correctly (2 TB limit ?) . Where can I
    post this bug, or is it sufficient to mention it here ?

    One of my users is having the same problem on centos linux. /home/t4d5 is mounted  via NFS and automount. Size is 13TB. He can't 'save as' there, though there is space and he has permission. When he saves as to a local partition in /, no problem.
    'quota' seems to be reporting the wrong info for the NFS mounted partition. On theme4, where the actual disk resides and is exported, the user has plenty of quota to spare:
    [root@theme4 ~]# quota -vls tobiasf
    Disk quotas for user tobiasf (uid 2797):
         Filesystem  blocks   quota   limit   grace   files   quota   limit   grace
          /dev/sdb1       0       0       0               0       0       0       
          /dev/sdc1  87928M    268G    287G           10794       0       0       
          /dev/sdd1       0       0       0               0       0       0       
          /dev/sde1       0       0       0               0       0       0       
          /dev/sdf1   1312G   4578G   4769G            119k       0       0      
    [root@theme4 ~]# df|grep sdf
    /dev/sdf1              13T   11T  2.2T  84% /export/t4d5
    But on lee1, it looks like his quota is exhausted:
    [tobiasf@lee1 ~]$ quota
    Disk quotas for user tobiasf (uid 2797):
         Filesystem  blocks   quota   limit   grace   files   quota   limit   grace
    theme4:/export/t4d5
                    1374885168* 505032704 705032704          118802       0       0      
    Maybe the problem on the adobe side is that reader checks first instead of just trying to write.
    Thanks
    Dave
    [root@lee1 ~]# rpm -q AdobeReader_enu
    AdobeReader_enu-9.4-1
    [root@lee1 ~]# uname -a
    Linux lee1 2.6.18-194.8.1.el5 #1 SMP Thu Jul 1 19:04:48 EDT 2010 x86_64 x86_64 x86_64 GNU/Linux
    [root@lee1 ~]# df -h
    Filesystem            Size  Used Avail Use% Mounted on
    /dev/mapper/VolGroup00-LogVol00
                          143G   38G   98G  28% /
    /dev/sda1              99M   19M   75M  21% /boot
    tmpfs                 497M   12K  497M   1% /dev/shm
    theme4:/export/t4d5    13T   11T  2.2T  84% /home/t4d5

Maybe you are looking for