[SOLVED] Error mounting a Fat32 partition

Hi, I'm new to this distro, but it looks quite neat. Unfortunately, I have an issue that I haven't been able to solve through the wiki or the man pages.
I have my main hard drive partitioned in three:
- Windows (ntfs)
- Linux (ext3)
- Data (all my files, docs, images...) (fat32)
I have problems mounting the Data partition into Archlinux.
A) Trying manually
First I tried mounting it manually to make sure I had done it right. The command
sudo mount -t vfat /dev/sda5 /media/docs
allowed me to see and read the files and write them. When I switched back to Windows, however, the OS told me there was an error in the Data partition, specifically with all the files I have changed or created using Archlinux. I ran Chkdsk and it fixed the files by deleting changes. Now, whenever I try to mount manually the partition, it mount it as a read-only file system, even when the -w or the -rw option is added.
B) Writting in /etc/fstab
Meanwhile, I tried several options in fstab to see if I could write on the disk. The lines I tried are:
/dev/sda5 /media/docs vfat defaults 0 0
/dev/sda5 /media/docs vfat defaults,iocharset=utf8,umask=000 0 0
/dev/sda5 /media/docs vfat defaults,user,dmask=000,fmask=111 0 0
/dev/sda5 /media/docs vfat defaults,user,rw,umask=000, 0 0
/dev/sda5 /media/docs vfat user,rw,umask=000, 0 0
/dev/sda5 /media/docs vfat defaults,iocharset=utf8,user,rw,umask=000, 0 0
All these options (I obviously didn't use them at the same time) mounted the partition and I could read the files, but I was never able to write to it, either as a normal user or root. I read the wiki, the man page of fstab and mount and there isn't anything much of help there.
Hope someone can help me. Thanks a lot.
R
P.D. I've been doing all these switching back and forwrad between windows and linux. I have always hibernated windows. I don't think this is the problem, but I will shut Windows down completely to see if it was the Chkdsk utility.
Last edited by robertoprs (2009-02-09 07:07:34)

Sorry, I forgot to post the answer...
So I just needed to restart Windows after using Chkdsk. Now I can read and write even when Windows is only hibernated. I'm just curious. I understand that this problem was a very stupid question, but it wasn't obvious to me that Chkdsk needed a reboot to "let go" the partition. Why is that?
Thanks for your help.
By the way, I've learned a lot with the wiki guides. This distro is getting better and better!

Similar Messages

  • [SOLVED] Error mounting Kindle

    Dear all,
    whenever I connect my Kindle to the laptop, caja (Mate's fork of Nautilus) shows this error message:
    Unable to mount Kindle
    Error mounting /dev/sdc1 at /run/media/luca/Kindle: Command-line `mount -t "vfat" -o "uhelper=udisks2,nodev,nosuid,uid=1000,gid=1000,shortname=mixed,dmask=0077,utf8=1,showexec,flush" "/dev/sdc1" "/run/media/luca/Kindle"' exited with non-zero exit status 32: mount: unknown filesystem type 'vfat'
    Any idea how can I fix this issue?
    Last edited by lucacerone (2014-05-21 23:22:40)

    I should also mention that before rebooting I also installed the packages dosfstools ntfs-3g ntfsprogs (dosfstools contains tools to manage vfat partitions),
    I am not sure whether this contributed to fix the issues or not.

  • [SOLVED] Error mounting an ISO file located in an EncFS folder

    I have some multimedia files inside an EncFS folder (decrypted via cryptkeeper).
    When trying to loop mount the ISO files I get:
    mount: foo.iso: failed to setup loop device: Permission denied
    There's no error mounting the same ISO from a «regular» FS.
    Is there a way around this?
    Last edited by JoaoVidal (2014-02-24 06:36:42)

    unSpawn at linuxquestions.org answered:
    See 'man encfs': the warning at "--public" and 'man fuse': "allow_other"
    Without setting the option 'public' in encfs or 'allow_other' is fuse, not even root can access the encfs mount and therefore mounting fails (sudo mount...).
    Also, cryptkeeper now has the preference "Allow other users to access mounted folders" which gives exactly this kind of permission.

  • [SOLVED]Error mounting: mount exited with exit code 16

    hi guys, i have a dual OS.  today after i force  shutdown my computer,  i can't mount one of the ntfs 。it shows the follow errors:
    Error mounting: mount exited with exit code 16: Mount is denied because the NTFS volume is already exclusively opened.
    The volume may be already mounted, or another software may use it which
    could be identified for example by the help of the 'fuser' command.
    any idea?
    Last edited by wntyygtwxf (2011-12-01 11:09:27)

    i resolve it by myself.
    first, i mount it at another place, just like  sudo mount   /dev/sda?  ~/home/down
    then umount it.
    now it work well. but i don't know why this worked.

  • (solved) Auto mount another internal partition

    I have a shared partition between my Arch and my Windows7 in my HD. The drive is in NTFS format. How do I automount it upon boot?
    I've tried:
    UUID=0352059936CBAE58 /dev/sda2 /media/Data ntfs defaults 0 1
    but that didn't work. There was another method on a Linux Mint forum, but neither did that.
    Last edited by zephyrus17 (2009-05-08 12:20:31)

    EDIT: Fixed it. Found a typo error. Thanks for the help
    Hmm... It's weird. It's not working, the automounting.
    I have this in fstab:
    /dev/sda2  /media/Data   ntfs-3g  users,uid=1000,gid=100,fmask=0113,dmask=0002         0 0
    But I have all my pictures on the partition /media/Data, and have symlinks from my /home pointing to it. And basically my wallpaper is in that /media/Data partition. Problem is, when I boot up, the chosen wallpaper doesn't show. Instead it's the green leaf wallpaper. Is this due to the mounting problem?
    Last edited by zephyrus17 (2009-05-08 12:20:14)

  • Cannot mount FAT32 partition

    After updating my arch install a few days ago I cannot mount my FAT32 partitions. The partitions worked fine before, but now when I go to mount them nothing happens at all, not even an error. They use to automount. When I go to my computer I can see all partitions but when I click on them nothing happens. I don't see the partitions in the fstab either. The partitions work fine in windows so it is not the data, any suggestions?
    Thanks in advanced.

    Have you tried to put the following in /etc/PolicyKit/PolicyKit.conf
    <?xml version="1.0" encoding="UTF-8"?> <!-- -*- XML -*- -->
    <!DOCTYPE pkconfig PUBLIC "-//freedesktop//DTD PolicyKit Configuration 1.0//EN"
    "http://hal.freedesktop.org/releases/PolicyKit/1.0/config.dtd">
    <!-- See the manual page PolicyKit.conf(5) for file format -->
    <config version="0.1">
    <match action="org.freedesktop.hal.storage.mount-removable">
    <return result="yes"/>
    </match>
    <match action="org.freedesktop.hal.power-management.*">
    <return result="yes"/>
    </match>
    </config>

  • [SOLVED]Cannot mount partitions with PCMANFM --no longer an issue

    Hi,
    I have searched and searched and pulling my hair out on this issue. I am using PCMANFM .9.10 on an LXDE install using the Arch x86 iso.  My HD contains several linux partitions and a FAT32 partition.
    I am not able to mount these partitions in PCMANFM.  I am able to mount my usb flash drive
    When trying to mount a partition in PCMANFM I get a "not authorized to perform operation" error message.
    Today, June 11 I partially rewrote this due to the lack of response I am getting on this problem.
    1. did a reinstall of Arch & LXDE today.  I've done two or three installs. dbus is in daemons in /etc/rc.conf
    2. initially the partition icons did not show up
    3. then, I installed gvfs and added 55-my-conf.pkla in /etc/polkit-1/localauthority/50-local.d/
    4. With that the partition icons show up in PCMANFM
    5. But I still get the "not authorized to perform operation" message
    The 55-my-conf.pkla has this content:
    [Storage Permissions]
    Identity=unix-group:storage
    Action=org.freedesktop.udisks.filesystem-mount;org.freedesktop.udisks.drive-eject;org.freedesktop.udisks.drive-detach;org.freedesktop.udisks.luks-unlock;org.freedesktop.udisks.inhibit-polling;org.freedesktop.udisks.drive-set-spindown;org.freedesktop.udisks.filesystem-mount-system-internal
    ResultAny=yes
    ResultActive=yes
    ResultInactive=no
    contents of .xinitrc
    #!/bin/sh
    # ~/.xinitrc
    # Executed by startx (run your window manager from here)
    if [ -d /etc/X11/xinit/xinitrc.d ]; then
    for f in /etc/X11/xinit/xinitrc.d/*; do
    [ -x "$f" ] && . "$f"
    done
    unset f
    fi
    # exec gnome-session
    # exec startkde
    #exec startxfce4
    exec startlxde
    # ...or the Window Manager of your choice
    At /usr/share/polkit-1/actions/org.freedesktop.udisks.policy
    I changed <action id="org.freedesktop.udisks.filesystem-mount-system-internal">
    mount a system-internal disk at <allow_active> from "auth_admin_keep" to "yes".
    Still didn't work!
    Either this is a bug or I have a permission problem somewhere.
    Can you please advise how to do this or point me to a recent tutorial to be able to  auto mount other partitions not using /etc/fstab?  Some of the older posts refer to hal or other package that have been deprecated. 
    Thanks
    Edit: latest. It seems that I must mount the desired partition from the terminal. example: $sudo mount /dev/sda5 /mnt
    then can edit it from PCMANFM by going to / and then /mnt. Apparently I do not have to manually unmount.
    Last edited by linuxloverjerry1 (2012-06-13 04:25:37)

    Hi,
    I have searched and searched and pulling my hair out on this issue. I am using PCMANFM .9.10 on an LXDE install using the Arch x86 iso.  My HD contains several linux partitions and a FAT32 partition.
    I am not able to mount these partitions in PCMANFM.  I am able to mount my usb flash drive
    When trying to mount a partition in PCMANFM I get a "not authorized to perform operation" error message.
    Today, June 11 I partially rewrote this due to the lack of response I am getting on this problem.
    1. did a reinstall of Arch & LXDE today.  I've done two or three installs. dbus is in daemons in /etc/rc.conf
    2. initially the partition icons did not show up
    3. then, I installed gvfs and added 55-my-conf.pkla in /etc/polkit-1/localauthority/50-local.d/
    4. With that the partition icons show up in PCMANFM
    5. But I still get the "not authorized to perform operation" message
    The 55-my-conf.pkla has this content:
    [Storage Permissions]
    Identity=unix-group:storage
    Action=org.freedesktop.udisks.filesystem-mount;org.freedesktop.udisks.drive-eject;org.freedesktop.udisks.drive-detach;org.freedesktop.udisks.luks-unlock;org.freedesktop.udisks.inhibit-polling;org.freedesktop.udisks.drive-set-spindown;org.freedesktop.udisks.filesystem-mount-system-internal
    ResultAny=yes
    ResultActive=yes
    ResultInactive=no
    contents of .xinitrc
    #!/bin/sh
    # ~/.xinitrc
    # Executed by startx (run your window manager from here)
    if [ -d /etc/X11/xinit/xinitrc.d ]; then
    for f in /etc/X11/xinit/xinitrc.d/*; do
    [ -x "$f" ] && . "$f"
    done
    unset f
    fi
    # exec gnome-session
    # exec startkde
    #exec startxfce4
    exec startlxde
    # ...or the Window Manager of your choice
    At /usr/share/polkit-1/actions/org.freedesktop.udisks.policy
    I changed <action id="org.freedesktop.udisks.filesystem-mount-system-internal">
    mount a system-internal disk at <allow_active> from "auth_admin_keep" to "yes".
    Still didn't work!
    Either this is a bug or I have a permission problem somewhere.
    Can you please advise how to do this or point me to a recent tutorial to be able to  auto mount other partitions not using /etc/fstab?  Some of the older posts refer to hal or other package that have been deprecated. 
    Thanks
    Edit: latest. It seems that I must mount the desired partition from the terminal. example: $sudo mount /dev/sda5 /mnt
    then can edit it from PCMANFM by going to / and then /mnt. Apparently I do not have to manually unmount.
    Last edited by linuxloverjerry1 (2012-06-13 04:25:37)

  • Solaris-x86 mount fat32 partition, the partition max size limit?

    solaris10 x86, laptop, 10G FAT32 partition for windows & x86 exchange data.
    the fat32 partition mount as normal, can be read fine.
    but write some file by x86, that can not find by windows.
    anyboy know did the solaris-x86 mount fat32 partition, the partition max size limit? or no limit, why this problem occur?

    Mounting Windows partition in Solaris
    The easiest way to share data now is to do it through a FAT32 partition. Solaris
    recognises it as partition of type pcfs. It is specified as device:drive where drive is
    either the DOS logical drive letter (c through z) or a drive number (1 through 24).
    Drive letter c is equivalent to drive number 1 and represents the Primary DOS partition
    on the disk; drive letters d through z are equivalent to drive numbers 2 through 24,
    and represent DOS drives within the Extended DOS partition.Syntax is
    mount -F pcfs device:drive /directroy-name
    where directory name specifies the location where the file system is mounted.
    To mount the first logical drive (d:) in the Extended DOS partition from an IDE hard
    disk in the directory /d use
    mount -F pcfs /dev/dsk/c0d0p0:d /d
    You can use mount directory-name after appending following line is in
    /etc/vfstab file
    device:drive directory-name pcfs no rw
    for example
    c0d0s0:c /c pcfs no rw
    If your windows partition like the following means
    C: - NTFS, D:-FAT32, E:-NTFS, F:-FAT32
    Then you can only mount D, F not C & E.
    Mounting D Drive:
    mount -F pcfs /dev/disk/c0d0p0:c /mountpoint
    Mounting F Drive
    mount -F pcfs /dev/disk/c0d0p0:d /mountpoint
    The driveletter only for fat not including other file systems (ntfs or any linux filesystems).

  • [SOLVED] Mounting a logical partition

    Scenario:
    /dev/sda1 primary NTFS windows boot
    /dev/sda2 primary NTFS windows home
    /dev/sda3 primary ext4 arch /boot
    /dev/sda5 primary ext4 arch /
    /dev/sda6 logical ext4 arch /home
    /dev/sda7 arch swap
    Do I perform mount /dev/sda6 /mnt/home as if it were a "normal" partition?
    EDIT: I would mount each logical partition as normal.
    Last edited by tancrackers (2012-08-29 03:34:46)

    shortcut144 wrote:
    perbh wrote:
    Assume your fat-partition is /dev/sda5 (just as an example)
    sudo mount -t vfat /dev/sda5 /some/mount/point
    Otherwise - as 's3kt0r' says - you can easily mount a ntfs-partition for read/write as well (using ntfs-3g)
    Awesome, thank you.  Marked as solved.
    Should I put this command in my fstab, or just make a startup command for this?
    You could do either ....
    If it will _always_ be there and you always want it mounted - put it in /etc/fstab, -or- you could put it in /etc/rc.local (without using 'sudo' of course).
    I'm a great believer in using rc.local because you _know_ that everything which might be needed (modules eg.) will be available by then.
    If you use /etc/fstab, your entry would be:
    /dev/sda5 /mount/point vfat defaults 0 0

  • [solved] docker: Error mounting: invalid argument

    I'm relatively new to using docker. When I had initially set it up (weeks ago) I was able to pull and manipulate containers. Today I came back to my docker project and now I can't even successfully pull an image.
    $ docker pull ubuntu:14.04
    ubuntu:14.04: The image you are pulling has been verified
    511136ea3c5a: Download complete
    511136ea3c5a: Error downloading dependent layers
    d497ad3926c8: Downloading [============================> ] 115.7 MB/201.6 MB 7s
    e791be0477f2: Download complete
    3680052c0f5c: Download complete
    22093c35d77b: Download complete
    5506de2b643b: Download complete
    5506de2b643b: Error pulling image (14.04) from ubuntu, endpoint: https://registry-1.docker.io/v1/, Error mounting '/dev/mapper/dock5506de2b643b: Error pulling image (14.04) from ubuntu, Error mounting '/dev/mapper/docker-8:98-380441-511136ea3c5a64f264b78b5433614aec563103b4d4702f3ba7d4d2698e22c158' on '/var/lib/docker/devicemapper/mnt/511136ea3c5a64f264b78b5433614aec563103b4d4702f3ba7d4d26982014/11/14 20:14:12 Error pulling image (14.04) from ubuntu, Error mounting '/dev/mapper/docker-8:98-380441-511136ea3c5a64f264b78b5433614aec563103b4d4702f3ba7d4d2698e22c158' on '/var/lib/docker/devicemapper/mnt/511136ea3c5a64f264b78b5433614aec563103b4d4702f3ba7d4d2698e22c158': invalid argument
    This is the log:
    $ journalctl -e
    Nov 14 20:24:47 example.com docker[18225]: 2014/11/14 20:24:47 docker daemon: 1.3.1 4e9bbfa; execdriver: native; graphdriver:
    Nov 14 20:24:47 example.com docker[18225]: [0687b0f9] +job serveapi(fd://)
    Nov 14 20:24:47 example.com docker[18225]: [info] Listening for HTTP on fd ()
    Nov 14 20:24:47 example.com docker[18225]: [0687b0f9] +job init_networkdriver()
    Nov 14 20:24:47 example.com docker[18225]: [0687b0f9] -job init_networkdriver() = OK (0)
    Nov 14 20:24:47 example.com docker[18225]: 2014/11/14 20:24:47 WARNING: Your kernel does not support cgroup swap limit.
    Nov 14 20:24:47 example.com docker[18225]: [info] Loading containers:
    Nov 14 20:24:47 example.com docker[18225]: .[error] daemon.go:321 Failed to load container 07b2a034632f0ddb8f01ebdcf1c0cc4ba0ade7a6d927b544754b44aa3b58f877: open /var/lib/docker/containers/07b2a034632f0ddb8f01ebdcf1c0cc4ba0ade7a6d927b544754b44aa3b58f877/config.json: no such file or directory
    Nov 14 20:24:47 example.com docker[18225]: .[error] daemon.go:321 Failed to load container 0bb0b50393dd951caeaa8386eb8ec8be1cc60e0822167ebed4dfdce9724b618c: open /var/lib/docker/containers/0bb0b50393dd951caeaa8386eb8ec8be1cc60e0822167ebed4dfdce9724b618c/config.json: no such file or directory
    Nov 14 20:24:47 example.com docker[18225]: .[error] daemon.go:321 Failed to load container 15732a4b2a97b91a2c590cab260f91dde7708b50059942221d349a778f94c892: open /var/lib/docker/containers/15732a4b2a97b91a2c590cab260f91dde7708b50059942221d349a778f94c892/config.json: no such file or directory
    Nov 14 20:24:47 example.com docker[18225]: .[error] daemon.go:321 Failed to load container 17b4471d4b031cd24feba6a2dc46e1524bcd9a6bb3b03342a642a5968caff3fa: open /var/lib/docker/containers/17b4471d4b031cd24feba6a2dc46e1524bcd9a6bb3b03342a642a5968caff3fa/config.json: no such file or directory
    Nov 14 20:24:47 example.com docker[18225]: .[error] daemon.go:321 Failed to load container 20686bda195d61f2c76c3e3c809f8b07df9b830d8bc650e10593e1863c82b7f3: open /var/lib/docker/containers/20686bda195d61f2c76c3e3c809f8b07df9b830d8bc650e10593e1863c82b7f3/config.json: no such file or directory
    Nov 14 20:24:47 example.com docker[18225]: .[error] daemon.go:321 Failed to load container 2fe7db68f38445c8ac0124be87174f66ccd1729880c5fa94b93d77ac0aa547fe: open /var/lib/docker/containers/2fe7db68f38445c8ac0124be87174f66ccd1729880c5fa94b93d77ac0aa547fe/config.json: no such file or directory
    Nov 14 20:24:47 example.com docker[18225]: .[error] daemon.go:321 Failed to load container 31b34a085e90849bcffd50c5f7b41d93849d494913448a92849c5d621555251d: open /var/lib/docker/containers/31b34a085e90849bcffd50c5f7b41d93849d494913448a92849c5d621555251d/config.json: no such file or directory
    Nov 14 20:24:47 example.com docker[18225]: .[error] daemon.go:321 Failed to load container 3484c3c05947051eea53865c973100d493e7ec495b3d7a5d4fbc1e5096196733: open /var/lib/docker/containers/3484c3c05947051eea53865c973100d493e7ec495b3d7a5d4fbc1e5096196733/config.json: no such file or directory
    Nov 14 20:24:47 example.com docker[18225]: .[error] daemon.go:321 Failed to load container 3ed275efb25789d6c9e18bf36e46f437fbdb21f3ffd7a93cb4525610737441f0: open /var/lib/docker/containers/3ed275efb25789d6c9e18bf36e46f437fbdb21f3ffd7a93cb4525610737441f0/config.json: no such file or directory
    Nov 14 20:24:47 example.com docker[18225]: .[error] daemon.go:321 Failed to load container 4503890c72d2f728e315b6ecae05fbabba85a3f959898a52df800f6fa22ca094: open /var/lib/docker/containers/4503890c72d2f728e315b6ecae05fbabba85a3f959898a52df800f6fa22ca094/config.json: no such file or directory
    Nov 14 20:24:47 example.com docker[18225]: .[error] daemon.go:321 Failed to load container 4db4ed2fbac1b442d770bcd325937508d2b190caa766f4ddef4f21628a953ea2: open /var/lib/docker/containers/4db4ed2fbac1b442d770bcd325937508d2b190caa766f4ddef4f21628a953ea2/config.json: no such file or directory
    Nov 14 20:24:47 example.com docker[18225]: .[error] daemon.go:321 Failed to load container 56f36a11482d6b9c513cbb819d6c67a768bd47dc4c02bd0de62c61365b6ba363: open /var/lib/docker/containers/56f36a11482d6b9c513cbb819d6c67a768bd47dc4c02bd0de62c61365b6ba363/config.json: no such file or directory
    Nov 14 20:24:47 example.com docker[18225]: .[error] daemon.go:321 Failed to load container 5b254c1c2344f61ab6bf6b338b22150cccd6ebd04407f3d00d6b5b3e37810d4f: open /var/lib/docker/containers/5b254c1c2344f61ab6bf6b338b22150cccd6ebd04407f3d00d6b5b3e37810d4f/config.json: no such file or directory
    Nov 14 20:24:47 example.com docker[18225]: .[error] daemon.go:321 Failed to load container 73fd6f0edadcf67fcdad7a397784275db013df085e648230b5818f0e68e3f48c: open /var/lib/docker/containers/73fd6f0edadcf67fcdad7a397784275db013df085e648230b5818f0e68e3f48c/config.json: no such file or directory
    Nov 14 20:24:47 example.com docker[18225]: .[error] daemon.go:321 Failed to load container 7ad8ad079db979b156af858cd36b908434157efd43e8cbc13677fa287bdf4da0: open /var/lib/docker/containers/7ad8ad079db979b156af858cd36b908434157efd43e8cbc13677fa287bdf4da0/config.json: no such file or directory
    Nov 14 20:24:47 example.com docker[18225]: .[error] daemon.go:321 Failed to load container 82a2e14c00dd73e2df1d78c45a0e576d52637c5dc422c32182ded365d6893167: open /var/lib/docker/containers/82a2e14c00dd73e2df1d78c45a0e576d52637c5dc422c32182ded365d6893167/config.json: no such file or directory
    Nov 14 20:24:47 example.com docker[18225]: .[error] daemon.go:321 Failed to load container 86572f605d7990f173875853bcfbdfe3f909c9b26f439378ab73d561e0e735eb: open /var/lib/docker/containers/86572f605d7990f173875853bcfbdfe3f909c9b26f439378ab73d561e0e735eb/config.json: no such file or directory
    Nov 14 20:24:47 example.com docker[18225]: .[error] daemon.go:321 Failed to load container 9eecdb0bf364f80cc88532832221da9de86c10a31b24660fdce8b68c79504a88: open /var/lib/docker/containers/9eecdb0bf364f80cc88532832221da9de86c10a31b24660fdce8b68c79504a88/config.json: no such file or directory
    Nov 14 20:24:47 example.com docker[18225]: .[error] daemon.go:321 Failed to load container a0920424bc83bffbc980f39f6dad17c865f84de1c3508a01d3c1298870f608c1: open /var/lib/docker/containers/a0920424bc83bffbc980f39f6dad17c865f84de1c3508a01d3c1298870f608c1/config.json: no such file or directory
    Nov 14 20:24:47 example.com docker[18225]: .[error] daemon.go:321 Failed to load container be228e991ffba0d423bb8bdca22fda9e318b7084bae53d765212bed6612e6b01: open /var/lib/docker/containers/be228e991ffba0d423bb8bdca22fda9e318b7084bae53d765212bed6612e6b01/config.json: no such file or directory
    Nov 14 20:24:47 example.com docker[18225]: .[error] daemon.go:321 Failed to load container e01b5a18f7c252f9c06e6d2dc9720baa184bc803e52aa68e9253372854382213: open /var/lib/docker/containers/e01b5a18f7c252f9c06e6d2dc9720baa184bc803e52aa68e9253372854382213/config.json: no such file or directory
    Nov 14 20:24:47 example.com docker[18225]: .[error] daemon.go:321 Failed to load container f00aff0df390b90f0a739430b4896cd67afc256a1c657271caf989fd3791ac91: open /var/lib/docker/containers/f00aff0df390b90f0a739430b4896cd67afc256a1c657271caf989fd3791ac91/config.json: no such file or directory
    Nov 14 20:24:47 example.com docker[18225]: .[error] daemon.go:321 Failed to load container f271529997f7479b5b6f65ccdd21d6b91445bbb31a3b253e95b1cf6ad6468c37: open /var/lib/docker/containers/f271529997f7479b5b6f65ccdd21d6b91445bbb31a3b253e95b1cf6ad6468c37/config.json: no such file or directory
    Nov 14 20:24:47 example.com docker[18225]: .......................[info] : done.
    Nov 14 20:24:47 example.com docker[18225]: [0687b0f9] +job acceptconnections()
    Nov 14 20:24:47 example.com docker[18225]: [0687b0f9] -job acceptconnections() = OK (0)
    Nov 14 20:24:47 example.com docker[18225]: [info] POST /v1.15/images/create?fromImage=ubuntu%3A14.04
    Nov 14 20:24:47 example.com docker[18225]: [0687b0f9] +job pull(ubuntu, 14.04)
    Nov 14 20:24:47 example.com docker[18225]: [0687b0f9] +job trust_update_base()
    Nov 14 20:24:48 example.com docker[18225]: [0687b0f9] -job trust_update_base() = OK (0)
    Nov 14 20:24:48 example.com docker[18225]: [0687b0f9] +job trust_key_check(/library/ubuntu)
    Nov 14 20:24:48 example.com docker[18225]: [0687b0f9] -job trust_key_check(/library/ubuntu) = OK (0)
    Nov 14 20:24:48 example.com kernel: device-mapper: thin: Creation of new snapshot 0 of device 0 failed.
    Nov 14 20:24:48 example.com kernel: JBD2: no valid journal superblock found
    Nov 14 20:24:48 example.com kernel: EXT4-fs (dm-1): error loading journal
    Nov 14 20:24:48 example.com kernel: JBD2: no valid journal superblock found
    Nov 14 20:24:48 example.com kernel: EXT4-fs (dm-1): error loading journal
    Nov 14 20:24:52 example.com systemd-udevd[298]: error: /dev/dm-1: No such device or address
    Nov 14 20:24:53 example.com docker[18225]: [error] pull.go:151 Error from V2 registry: Error mounting '/dev/mapper/docker-8:98-380441-511136ea3c5a64f264b78b5433614aec563103b4d4702f3ba7d4d2698e22c158' on '/var/lib/docker/devicemapper/mnt/511136ea3c5a64f264b78b5433614aec563103b4d4702f3ba7d4d2698e22c158': invalid argument
    Nov 14 20:24:57 example.com kernel: JBD2: no valid journal superblock found
    Nov 14 20:24:57 example.com kernel: EXT4-fs (dm-1): error loading journal
    Nov 14 20:24:57 example.com kernel: JBD2: no valid journal superblock found
    Nov 14 20:24:57 example.com kernel: EXT4-fs (dm-1): error loading journal
    Nov 14 20:25:02 example.com systemd-udevd[298]: error: /dev/dm-1: No such device or address
    Nov 14 20:25:03 example.com docker[18225]: Error pulling image (14.04) from ubuntu, Error mounting '/dev/mapper/docker-8:98-380441-511136ea3c5a64f264b78b5433614aec563103b4d4702f3ba7d4d2698e22c158' on '/var/lib/docker/devicemapper/mnt/511136ea3c5a64f264b78b5433614aec563103b4d4702f3ba7d4d2698e22c158': invalid argument
    Nov 14 20:25:03 example.com docker[18225]: [0687b0f9] -job pull(ubuntu, 14.04) = ERR (1)
    Nov 14 20:25:03 example.com docker[18225]: panic: runtime error: invalid memory address or nil pointer dereference
    Nov 14 20:25:03 example.com docker[18225]: [signal 0xb code=0x1 addr=0x20 pc=0x6bb9ac]
    Nov 14 20:25:03 example.com docker[18225]: goroutine 58 [running]:
    Nov 14 20:25:03 example.com docker[18225]: runtime.panic(0xa6bc20, 0x1087c93)
    Nov 14 20:25:03 example.com docker[18225]: /usr/lib/go/src/pkg/runtime/panic.c:279 +0xf5
    Nov 14 20:25:03 example.com docker[18225]: bufio.(*Writer).flush(0xc2082228c0, 0x0, 0x0)
    Nov 14 20:25:03 example.com docker[18225]: /usr/lib/go/src/pkg/bufio/bufio.go:530 +0xdc
    Nov 14 20:25:03 example.com docker[18225]: bufio.(*Writer).Flush(0xc2082228c0, 0x0, 0x0)
    Nov 14 20:25:03 example.com docker[18225]: /usr/lib/go/src/pkg/bufio/bufio.go:519 +0x39
    Nov 14 20:25:03 example.com docker[18225]: net/http.(*response).Flush(0xc20816fa40)
    Nov 14 20:25:03 example.com docker[18225]: /usr/lib/go/src/pkg/net/http/transport.go:885 +0x38f
    Nov 14 20:25:03 example.com docker[18225]: created by net/http.(*Transport).dialConn
    Nov 14 20:25:03 example.com docker[18225]: /usr/lib/go/src/pkg/net/http/transport.go:601 +0x957
    Nov 14 20:25:03 example.com docker[18225]: goroutine 118 [runnable]:
    Nov 14 20:25:03 example.com docker[18225]: net/http.(*persistConn).readLoop(0xc2080d7130)
    Nov 14 20:25:03 example.com docker[18225]: /usr/lib/go/src/pkg/net/http/transport.go:868 +0x829
    Nov 14 20:25:03 example.com docker[18225]: created by net/http.(*Transport).dialConn
    Nov 14 20:25:03 example.com docker[18225]: /usr/lib/go/src/pkg/net/http/transport.go:600 +0x93f
    (snipping several dozen lines of stack trace in the middle there)
    The search results for various permutations of "docker error mount invalid argument dm" are badly washed out so I wasn't able to find any helpful leads; nor was I able to find anything relevant in the docker issue list. I tried re-installing docker (by running pacman -Rns docker and then pacman -S docker hoping that it was a config setting I could nuke & pave but this had no effect. I then ran the following:
    $ dmsetup ls
    docker-8:98-380441-pool (254:0)
    followed by dmsetup remove docker-8:98-380441-pool and attempted the pull again. No difference.
    I'm convinced this is not a docker bug but a misconfiguration of my system, but the error provided ("error mounting .... invalid argument") is rather opaque and I'm stuck with what to try next.
    Any suggestions would be appreciated.
    Last edited by cmtonkinson (2014-11-15 11:41:47)

    Well, rm -rf /var/lib/docker did it!
    I was unable to remove /var/lib/docker/devicemapper ("device or resource busy") but that doesn't seem to matter - as you suggest docker reconfigured itself. Thanks for the tip!
    For the record (should have posted this previously):
    $ docker info
    Containers: 1
    Images: 7
    Storage Driver: devicemapper
    Pool Name: docker-8:98-380441-pool
    Pool Blocksize: 65.54 kB
    Data file: /var/lib/docker/devicemapper/devicemapper/data
    Metadata file: /var/lib/docker/devicemapper/devicemapper/metadata
    Data Space Used: 598.3 MB
    Data Space Total: 107.4 GB
    Metadata Space Used: 1.18 MB
    Metadata Space Total: 2.147 GB
    Library Version: 1.02.90 (2014-09-01)
    Execution Driver: native-0.2
    Kernel Version: 3.17.2-1-ARCH
    Operating System: Arch Linux
    WARNING: No swap limit support
    $ docker --version
    Docker version 1.3.1, build 4e9bbfa

  • [SOLVED] My /home and /boot partition show on my desktop; not mounted

    I'm guessing these two fie systems aren't mounted  and the computer is seeing them as separate volumes?
    So I guess I made a mistake during the install. This kind of explains a few things because when updating my kernel GRUB wasn't being updated as if the /boot partition wasn't mounted. I had to completely reinstall GRUB to have it point to the right kernel.
    Is there a way to fix this and get these mounted how they need to be? Probably something with my fstab file?
    When I installed I mounted my root, created /mnt/boot and /mnt/home, then mounted those to their own partitions that I had created.
    I generated my fstab and checked it, and everything looked fine. I just don't know why everything else is just fine, but /boot and /home aren't mounted?
    My partition scheme is GPT and looks like
    /dev/sda1 -- bios boot
    /dev/sda2 -- /boot
    /dev/sda3 -- /
    /dev/sda4 -- /swap
    /dev/sda5 -- /home
    I used UUIDs if that makes any difference.
    Thanks.
    Last edited by stevenmw (2014-11-06 16:41:12)

    All right. I did what bstaletic said, and performed option 3 of his suggestions. My fstab file is restored but now when I start lightdm I get to my login screen, login, and have a black screen with just a cursor. All I did was run the install media, mount each partition (starting with root first). Then I turned my swap on.
    After that, I ran
    genfstab -U -p /mnt > fstab
    I checked the fstab file, it looked like this
    # /dev/sda3
    UUID=c2d39ee2-e1c4-4989-9937-91fad2951d67 / ext4 rw,relatime,data=ordered 0 1
    # /dev/sda2
    UUID=9cd92417-c4c0-40c7-9de3-3b65b896e36b /boot ext2 rw,relatime 0 2
    # /dev/sda5
    UUID=db8633d3f-0cb2-49dc-9792-356ad37ace58 /home ext4 rw,relatime,data=ordered 0 2
    # /dev/sda4
    UUID=00d4f1cd-cc6c-4dd3-B4c7-67da333205ea none swap defaults 0 0
    So I unmouted everything and turned swap off and went back into my system. The fstab file matched the output above. I started lightdm so i could get into xfce to see if the volumes were no longer on my desktop. However, now I get a black screen with a cursor. I let it sit for a while, but I ended up going into a tty and rebooting. Same issue. Black screen and cursor. I can see and login to lightdm just fine, but not my xfce DE.
    I did try reinstalling lightDM and xfce4 and xfce4-goodies. Not xorg though. I'll try reinstallign it and see what that does.
    Last edited by stevenmw (2014-10-15 20:01:51)

  • [solved] Encrypt a FAT32 partition

    Hi all,
    I'll soon format my iMac Alu to get :
    - 50 GB Mac OS X (HFS+)
    - 50 GB Archlinux (ext3)
    - 400 GB Data (FAT32) readable by both Mac OS X and Arch.
    Is it possible to get an encrypted FAT32 partition ? (like in 256 bits, let's be crazy)
    Which could of course be decrypted on the flow by Mac and Arch ?
    edit : I've found http://www.truecrypt.org is it any good ?
    Thx.
    ~ktr
    Last edited by Kooothor (2008-09-26 11:34:26)

    Ok, thx

  • Viewing contents of FAT32 partition

    I am having trouble viewing the contents of my FAT32 partition. I installed Solaris 10 on c0d1. I also added a 2GB FAT32 partition to c0d1 as well for sharing files between windows xp and Solaris 10.
    I added the following in my /etc/vfstab to mount the partition
    /dev/dsk/c0d1p2:c     -     /share     pcfs     -     yes     -
    But that caused my system not to load up properly.
    I commented the line out and it boots up normally. Then I tried to mount the partition from the terminal
    mount -F pcfs /dev/dsk/c0d1p2:c /mnt
    but it says "is already mounted or /mnt is busy." I'm not sure where to go to view the contents of the partition, either in the gui (Java Desktop) or from the terminal. Can somebody please help?

    Actually, I spoke incorrectly. It did boot, but failed to load the graphical login console. Here are the errors that followed:
    checking ufs filesystems
    /dev/rdsk/c0d1s7: is logging
    svc:/system/filesystem/local: default: 'WARNING: /sbin/mountall -l failed: exit status 1
    svc.startd[7]: svc:/system/filesystem/local:default: Method "/lib/svc/method/fs-local" failed with exit status 95.
    [ system/filesystem/local:default failed fatally (see 'svcs -x' for details) ]
    sol console login:I also tried mounting to /, but that resulted in the same: is already mounted or / is busy.

  • [Triaged] System tries to mount iPod firmware partition

    Hi. I switched from hal-easy back to hal today, and it's started doing something weird.
    It's trying to mount my iPod's firmware partition now. It's the first partition, and doesn't have a file system on it. So before mounting the iPod's real partition, I get an error dialog about how it failed to mount that first partition, and then proceeds to mount the second one. Icons for both partitions are visible on the desktop, and in thunar. I'm using xfce 4.6, and exo-mountopt from AUR.
    It didn't behave this way before switching to hal-easy, and while I was using hal-easy. What could be going on here? How can I fix it?
    Last edited by TiZ (2009-09-23 19:35:37)

    I found a way to work around this problem.
    Create /etc/udev/rules.d/10-local.rules, or if you already have it, add this:
    # Ignore iPod's first partition
    SUBSYSTEMS=="usb" ATTRS{product}=="Rockbox media player" KERNEL=="sd?1" OPTIONS+="ignore_device last_rule"
    SUBSYSTEMS=="usb" ATTRS{product}=="iPod" KERNEL=="sd?1" OPTIONS+="ignore_device last_rule"
    This covers iPods with both Apple OS and Rockbox. After making it, the icon for the system partition will still be on the desktop. Just log out and log back in and it will disappear.
    And if you get nitpicky about the volume label being all-caps like I do, you can make /etc/hal/fdi/policy/05-labels.fdi and then restart hal:
    <?xml version="1.0" encoding="ISO-8859-1"?>
    <deviceinfo version="0.2">
    <device>
    <match key="volume.label" string="TIZPOD">
    <merge key="volume.label" type="string">TiZPod</merge>
    </match>
    </device>
    </deviceinfo>
    Unfortunately, these are all only work-arounds for behavior that was not exhibited before... as for when it changed, I can't remember for the life of me. I'd rather not have to use work-arounds, but they're working. I've marked the thread as "triaged" instead of "solved" because the problem's not fixed, just worked around.
    Now I'd like to figure out how to get my iPod icon back instead of the boring hard drive icon when I use Rockbox USB, but I'm sure I can just google around for that.
    Last edited by TiZ (2009-09-23 19:38:39)

  • How to mount SATA Ntfs Partitions on Arch Linux

    Please help me mounting sata ntfs partitions.
    Here is my fdisk -l :
    [kaola@ArchHost ~]$ sudo fdisk -l
    Disk /dev/sda: 80.0 GB, 80026361856 bytes
    255 heads, 63 sectors/track, 9729 cylinders
    Units = cylinders of 16065 * 512 = 8225280 bytes
    Disk identifier: 0x020e020e
    Device Boot Start End Blocks Id System
    /dev/sda1 1 371 2980026 82 Linux swap / Solaris
    /dev/sda2 * 372 2803 19535040 83 Linux
    /dev/sda3 2804 6450 29294527+ 83 Linux
    /dev/sda4 6451 6463 104422+ 83 Linux
    Disk /dev/sdb: 160.0 GB, 160041885696 bytes
    255 heads, 63 sectors/track, 19457 cylinders
    Units = cylinders of 16065 * 512 = 8225280 bytes
    Disk identifier: 0xd7a23d33
    Device Boot Start End Blocks Id System
    /dev/sdb1 2 5875 47182905 5 Extended
    /dev/sdb2 * 5876 9139 26218080 7 HPFS/NTFS
    /dev/sdb5 2 3918 31463271 7 HPFS/NTFS
    /dev/sdb6 3919 5875 15719571 7 HPFS/NTFS
    Disk /dev/sdc: 4043 MB, 4043308544 bytes
    255 heads, 63 sectors/track, 491 cylinders
    Units = cylinders of 16065 * 512 = 8225280 bytes
    Disk identifier: 0x00050ebd
    Device Boot Start End Blocks Id System
    /dev/sdc1 1 491 3943926 b W95 FAT32
    As far as I know, the sata ntfs partitions are those with (sdb#).
    I tried mounting one of them but this is what it shows:
    [kaola@ArchHost ~]$ sudo mount /dev/sdb6
    mount: can't find /dev/sdb6 in /etc/fstab or /etc/mtab
    Please help me, this is very annoying compared to ubuntu which does do the job pretty well.  By the way, I'm using kde as my DE.  Dolphin sees the partitions but cant access.
    It says:
    An error occured while accessing 'Backup2 HD2', the system responded:
    org.freedesktop.Hal.Device.Volume.UnknownFailure: TODO:
    have to rethink extra options
    Reading some tutorials on ntfs-3g wiki, I've modified my fstab.  Still, I can't read the partitions...Please help me, this is my fstab:
    # /etc/fstab: static file system information
    # <file system> <dir> <type> <options> <dump> <pass>
    none /dev/pts devpts defaults 0 0
    none /dev/shm tmpfs defaults 0 0
    UUID=2167baaa-d1e0-4719-920c-0bc09fa56caa / reiserfs defaults 0 1
    UUID=3e2250a0-ac45-458c-ba40-44ddbe8af54d /boot ext2 defaults 0 1
    UUID=cbf76343-12cf-4975-9284-3360735be927 /home reiserfs defaults 0 1
    UUID=f39da452-efe4-49d0-abd4-bb5246b83b33 swap swap defaults 0 0
    /dev/cdrom /media/cdrom auto ro,user,noauto,unhide 0 0
    /dev/dvd /media/dvd auto ro,user,noauto,unhide 0 0
    UUID=2167baaa-d1e0-4719-920c-0bc09fa56caa / reiserfs defaults 0 1
    UUID=3e2250a0-ac45-458c-ba40-44ddbe8af54d /boot ext2 defaults 0 1
    UUID=cbf76343-12cf-4975-9284-3360735be927 /home reiserfs defaults 0 1
    UUID=f39da452-efe4-49d0-abd4-bb5246b83b33 swap swap defaults 0 0
    /dev/sdb1 /mnt/ntfs1 ntfs-3g users,noauto,uid=1000,gid=100,fmask=0113,dmask=0002,locale=en_US.utf8 0 0
    /dev/sdb2 /mnt/ntfs2 ntfs-3g users,noauto,uid=1000,gid=100,fmask=0113,dmask=0002,locale=en_US.utf8 0 0
    /dev/sdb5 /mnt/ntfs3 ntfs-3g users,noauto,uid=1000,gid=100,fmask=0113,dmask=0002,locale=en_US.utf8 0 0
    /dev/sda6 /mnt/ntfs4 ntfs-3g users,noauto,uid=1000,gid=100,fmask=0113,dmask=0002,locale=en_US.utf8 0 0
    Last edited by kaola_linux (2008-10-04 14:51:24)

    AD28 wrote:
    For seamless integration similar to Ubuntu:
        Follow this wiki for ntfs-3g installation and fstab configuration.
    For basic on-demand support:
    # pacman -Sy ntfs-3g
    and mount with:
    # mount -t ntfs-3g /dev/sdbX /mnt
    Now that did the trick!!!!!
    A happy Arch Linux user here!!!!hehee
    Any idea how to automate this? I want it to be automatically mounted so that it would be easy to transfer files...Pleasssseeeeee.....Thanks

Maybe you are looking for