[SOLVED] /proc must be mounted! ...what? o.O

I just bumped into this strange error message while installing archlinux from a usb netinstall stick to my laptop for the third time. (why do for the third time you ask? well that's a whole other mystery itself, you see for some reason I could not start X anymore as anyone else but root... strange isn't it?)
Anyways, back to the topic: I now find myself unable to install archlinux to my laptop at all. The reason being that error message (in the topic) that shows itself after I've configured the system (rc.conf settings and all that jazz and setting up the root password) and select "done".
Already tried google to no avail. Also tried reinstalling the netinstall image to the usb stick again thinking that maybe data on it got corrupted or something when I took it off unsafely. Well that didn't help either.
What does this mean? What went wrong? Did I suddenly make a trivial mistake that I've never done before when installing archlinux? That doesn't sound very plausible to me...
Last edited by Rayniac (2011-10-08 20:56:32)

I'm getting this as well. A few days ago, I installed Arch on a VirtualBox VM successfully. I had messed some stuff up with X, so I attempted to to a fresh reinstall today. During the package install process, the following appears in the logs:
installing linux...
>>> Updating module dependencies. Please wait ..
>>> Generating initial ramdisk, using mkinitcpio. Please wait...
/sbin/mkinitcpio: line 160: 2558 Segementation fault mountpoint -q /p
==> ERROR: /proc must be mounted!
I didn't notice the error while installing packages the first time around and it displayed when I pressed done on the install. I tried the install a few more times, and noticed the error during installing packages then. The error line number is always 160, but I think the segmentation fault had a different number before.
When I go to a different console during the setup process, I can cd into /proc and see things in it.
I've tried both the rit.edu and gatech.edu mirrors, thinking it may have been a repo issue.
I'm using the ext4 filesystem if it matters.
Please let me know if I can provide any more information.
Last edited by gshakhn (2011-10-08 18:36:21)

Similar Messages

HT5675 This update, upon booting, has caused my disk space to fill up and my system freezes up. The same happens to my coworker's computer. We both watch the remaining disk space decrease and the "spinning rainbow appears" and we must restart. What do we

Software Update: Java for OS X 2013-002 1.0
This update, upon booting, has caused my disk space to fill up and my system freezes up. The same happens to my coworker's computer. We both watch the remaining disk space decrease and the "spinning rainbow appears" and we must restart. What do we do?

First, empty the Trash if you haven't already done so.
Use a tool such as OmniDiskSweeper (ODS) to explore your volume and find out what's taking up the space. You can delete files with it, but don't do that unless you're sure that you know what you're deleting and that all data is safely backed up. That means you have multiple backups, not just one.
Proceed further only if the problem hasn't been solved.
ODS can't see the whole filesystem when you run it just by double-clicking; it only sees files that you have permission to read. To see everything, you have to run it as root.
Back up all data now.
Install ODS in the Applications folder as usual.
Triple-click the line of text below to select it, then copy the selected text to the Clipboard (command-C):sudo /Applications/OmniDiskSweeper.app/Contents/MacOS/OmniDiskSweeper
Launch the Terminal application in any of the following ways:
☞ Enter the first few letters of its name into a Spotlight search. Select it in the results (it should be at the top.)
☞ In the Finder, select Go ▹ Utilities from the menu bar, or press the key combination shift-command-U. The application is in the folder that opens.
☞ Open LaunchPad. Click Utilities, then Terminal in the icon grid.
Paste into the Terminal window (command-V). You'll be prompted for your login password, which won't be displayed when you type it. You may get a one-time warning not to screw up. If you see a message that your username "is not in the sudoers file," then you're not logged in as an administrator.
I don't recommend that you make a habit of doing this. Don't delete anything while running ODS as root. If something needs to be deleted, make sure you know what it is and how it got there, and then delete it by other, safer, means.
When you're done with ODS, quit it and also quit Terminal.

"Time machine error, The disk image cannot be mounted" What can I do??

I ran the time machine. Then, "preparing backup" showed up for a long time. After that, a window pop out: "Time machine error, The disk image cannot be mounted" What is disk image? What can I do (I can't back up anything)
P.S. I use time capsule for backup. there were no problem on connection

I'm having the same issue. I do not have TC as my base station. It says right in the book that if you choose, you do not have to have it run as your router, just as a part of your existing wireless network. All software is up to date and I have already shortened the name of both my TC and TC disc to 6 characters and no spaces! I've already spoken with someone today about this. He really didn't know. Have tried backing up both wirelessly and directly connecting with an Ethernet cord. I had to finally call because when I attempted to register the product to get online support, apple.com didn't recognize the serial number!!! The gentleman on the phone got it registered for me. I bought the TC from an official apple store and for whatever reason when he put in the serial number his computer said that this TC was so "old" I guess that there was technically "no support." That basically means that even though my parents just purchased this for me a week before Christmas, that it was made a year ago and the warranty is not good?? I need to do more research on that. Right now I am very unhappy about this. I am a firm apple user and have been for years, but this is frustrating.
I had read somewhere else (not sure I've been searching apple for what seems like forever now) to make sure that the TC was showing up in "devices" of the Finder. Mine doesn't show up there, but rather in the "Network" window. Is this an issue? If it is, can anyone tell me how to fix that. I have Time Machine backing up to my TC, so I do not see why it would be.
UPDATE: I just opened up my TC on the "Shared" section of the Finder window and deleted the old "sparsebundle" (I had no clue that anything had backed up way back at 3:30pm on Dec 29) and now I get a slightly new message: Time Machine Error: The backup disc image could not be created." So now the word "mounted" is replaced with "created." This error showed up a lot sooner than the original one. Ok, no clue. I am going to try to Change the Disc again, and try again. I will post another update.
Message was edited by: kryzma

My MacBook Pro says: iDisc not mounted, what does this mean???

I'm trying to acess my iDisc and it's not working. Message pops up that says "iDisc not mounted", what does this mean? I can no longer download music or movies from itunes also, because it says startup disc is full. I've tried to delete items from my computer, still not enough room. I don't know what to do here. Maybe I accidentally deleted the iDisc??? Also, the Mobile Me thing isn't working either...it says "an error was returned from the server. check back later." Guurrrrhhhh! Somebody please help me....

Falling Rain wrote:
I meant 'duh' to myself....
Most of the movies r for my son...synced to his iPad 2....can I delete them off my MBP??? Will they remain in the cloud? Or should I just copy my entire iTunes library to an external hard drive? Can I add more memory to this MBP?
You need a bigger Hard Drive, not More Memory (well, you may need that too but it has nothing to do with this problem)
Buy and fit a bigger hard drive, post back if you need help with that.

[Solved]External HDD only mounts as read only

Okay, I have a general log, but I'm not completely sure what all information you need. Ask and you will receive.
So I run udiskie through i3, works great, but my file systems get mounted as read-only, which is..not great. It's pretty irritating. So I thought, hey, let's just chown that shit, right? No. It's a read only file system.
Anyway, so I did killall udiskie, tried mounting it manually and all as demonstrated in lsblk, and it's still read only, for some interesting reason. (Sorry the lsblk log isn't clean). If there's some other output you'd like, let me know...
I run the thunar file manager, which is alright, but it doesn't auto-mount (I tried setting it up, googled it a lot, it just didn't auto-mount, and udiskie looked like it worked fine until I realized it was all read-only).
In lsblk I ran sudo thunar to view the drive, since permission was denied to myself. It was still read-only, meaning it's not necessarily a udiskie problem? I could mount my other flash drive alright it appeared, but when I did it with udiskie it was also readonly.
The flash drive was made with dd, so it had two partitions, the second one mounted fine, the first one not so much, and with udiskie it just mounted what looked like the second one with more files (So maybe both? I was a bit confused).
lsblk: http://pastebin.com/WdJbky9j
udiskie -a: http://pastebin.com/RT2sQE01
On a side note, those awesome arrows on the side of my terminal thanks to zsh and oh-my-zsh? They're just empty rectangles in rxvt-unicode, and I have no idea why. They display fine in pastebin. If anyone happens to know what I'm missing there, much obliged.
Solution:
Actually understand NTFS in linux (Working on it)
Install ntfs-3g
Last edited by Rojikku (2014-07-02 02:06:18)

lsblk -f: http://pastebin.com/KeHpDtF6
Anything I could say would be repetitive of the data. >>; But for record purposes, btrfs and the external is ntfs.
Edit: I don't have ntfs-3g installed, FYI. It seemed like an alternative to udiskie and I dislike installing things frivolously. I noticed another user fixed a somewhat similar problem like that, would that be my issue?
Last edited by Rojikku (2014-07-02 01:37:24)

[Solved] sshfs can't mount via fstab on startup

I have an HDD mounted in my RPI which I've mounted as a filesystem in my desktop via sshfs (through fstab).
If I do "sudo mount -a", it seems to mount just fine, so I researched a bit (even though I'm still an newbie in Arch and Linux distros in general) and found out that it's most probably is caused due to the network not being initialized fast enough for the sshfs fstab entry to be discovered (due to having no network and therefore no access to it).
I'm really not sure how to provide any info which would help you guyz help me so I'm just gonna provide the sshfs entry from my fstab file and the journalctl logs that seem to be relevant.
Jun 23 22:32:00 home systemd[1]: home-username-media-downloads-mydrive.mount mount process exited, code=exited status=1
Jun 23 22:32:00 home systemd-udevd[168]: renamed network interface eth0 to enp0s25
Jun 23 22:32:00 home systemd[1]: Failed to mount /home/username/media/downloads/mydrive.
Jun 23 22:32:00 home systemd[1]: Dependency failed for Remote File Systems.
Jun 23 22:32:00 home systemd[1]: Unit home-username-media-downloads-mydrive.mount entered failed state.
Jun 23 22:32:00 home dhcpcd[236]: eth0: waiting for carrier
Jun 23 22:32:00 home dhcpcd[236]: eth0: removing interface
[email protected]:/media/mydrive/ /home/username/media/downloads/mydrive fuse IdentityFile=/home/username/.ssh/mykey,uid=1000,gid=1000,reconnect,_netdev,allow_other,transform_symlinks,user,idmap=user,BatchMode=yes 0 0
ps: This issue might be related to a recent attempt I've had to enable? the Gnome NetworkManager service, I'm not sure if it's related but I've first noticed the issue the same day I tried to enable that service (which I've later disabled because I couldn't get my network connected).
Last edited by Varemenos (2014-06-27 23:44:00)

It just doesn't want to work...
# systemctl status home-username-media-downloads-mydrive.mount
==>
● home-username-media-downloads-mydrive.mount - mydrive Sshfs mount
Loaded: loaded (/etc/systemd/system/home-username-media-downloads-mydrive.mount; enabled)
Active: failed (Result: exit-code) since Thu 2014-06-26 16:45:21 EEST; 31s ago
Where: /home/username/media/downloads/mydrive
What: [email protected]:/media/mydrive/
Process: 281 ExecMount=/bin/mount [email protected]:/media/mydrive/ /home/username/media/downloads/mydrive -t fuse.sshfs -o IdentityFile=/home/username/.ssh/mykey,uid=1000,gid=1000,reconnect,_netdev,allow_other,transform_symlinks,user,idmap=user,BatchMode=yes (code=exited, status=1/FAILURE)
Jun 26 16:45:21 home mount[281]: read: Connection reset by peer
Jun 26 16:45:21 home systemd[1]: home-username-media-downloads-mydrive.mount mount process exited, code=exited status=1
Jun 26 16:45:21 home systemd[1]: Failed to mount mydrive Sshfs mount.
Jun 26 16:45:21 home systemd[1]: Unit home-username-media-downloads-mydrive.mount entered failed state.
The file:
[Unit]
Description=mydrive Sshfs mount
Requires=network-online.target
After=[email protected]
[Mount]
What=[email protected]:/media/mydrive/
Where=/home/username/media/downloads/mydrive
Type=fuse.sshfs
Options=IdentityFile=/home/username/.ssh/mykey,uid=1000,gid=1000,reconnect,_netdev,allow_other,transform_symlinks,user,idmap=user,BatchMode=yes
[Service]
Restart=on-failure
RestartSec=10
[Install]
WantedBy=multi-user.target
Note that running
systemctl start home-username-media-downloads-mydrive.mount
, works just fine...
Last edited by Varemenos (2014-06-26 14:00:23)

[Solved]Yet Another HAL / Mounting issue....

My issue can be avoided by manually mounting a device, just to get that out there.
Whenever I transfer a larger file ( > 200mb) onto a removable USB device formated in either FAT or any non-journaled filesystem, Thunar will *pretend* like its unmounting the device but after about 20 seconds it states:
Failed to unmount "<device name>".
Did not receive a reply. Possible causes include: the remote application did not send a reply,
the message bus security policy blocked the reply, the reply timeout expired,
or the network connection was broken.
On top of the message, my data written is mostly corrupt.
What I know:
** Thunar uses exo-unmount to unmount devices given a HAL uuid. Maybe this is failing? Any clue how to debug this?
** 20-storage-methods.fdi states that all vfat mounted devices have 'flush' and 'async' mount options... could this be an issue?
** I'm part of the 'storage' and 'power' groups.
** i start XFCE using ck-launch-session startxfce4
I've made sure that the device has no other handles and is not open in any window. My system(s) all have new and updated HAL and DBUS, as well as every other package. Running 'sync' after writing the files sometimes fixes the issue. Does anyone have a fix for why removable drives aren't "sending a reply" ? Thanks!
--Anthony
Last edited by anthonyclark (2010-09-22 17:48:13)

Alright ... well. I managed to solve this kind of. As per my last post regarding the same exact issue, I must've missed a reply from Inxsible telling me to use the FIRST suggest UDEV rule from the arch udev wiki.
The result of this is basically...
*Device inserted
*Mounted in /media/<device name> automatically
*(No access via Thunar sidepane since it gets mounted with `mount`)
*No need to manually unmount
*just unplug or power off the device and it gets "lazy" unmounted via `unmount`
Downside:
*Mounting a drive via TrueCrypt creates a directory in /media that doesn't get automatically deleted.
*Not a solution to Thunar having response issues with unmounting.
/etc/udev/rules.d/11-media-by-label-auto-mount.rules
KERNEL!="sd[a-z][0-9]", GOTO="media_by_label_auto_mount_end"
# Import FS infos
IMPORT{program}="/sbin/blkid -o udev -p %N"
# Get a label if present, otherwise specify one
ENV{ID_FS_LABEL}!="", ENV{dir_name}="%E{ID_FS_LABEL}"
ENV{ID_FS_LABEL}=="", ENV{dir_name}="usbhd-%k"
# Global mount options
ACTION=="add", ENV{mount_options}="relatime"
# Filesystem-specific mount options
ACTION=="add", ENV{ID_FS_TYPE}=="vfat|ntfs", ENV{mount_options}="$env{mount_options},utf8,gid=100,umask=002"
# Mount the device
ACTION=="add", RUN+="/bin/mkdir -p /media/%E{dir_name}", RUN+="/bin/mount -o $env{mount_options} /dev/%k /media/%E{dir_name}"
# Clean up after removal
ACTION=="remove", ENV{dir_name}!="", RUN+="/bin/umount -l /media/%E{dir_name}", RUN+="/bin/rmdir /media/%E{dir_name}"
# Exit
LABEL="media_by_label_auto_mount_end"
Last edited by anthonyclark (2010-09-22 03:50:00)

[SOLVED] DBUS boot problems - Mounting system devices as a normal user

I have the [testing] and [community-testing] repositories enabled. A few days ago, probably due to an update, I started having trouble mounting devices and the shutdown/reboot options don't show up anymore on the LXDE exit menu.
I use gvfs for mounting devices as a normal user with PCManFM or Thunar. The error message is "Authentication is required".
After some testing, I found out that by restarting dbus, I could start mounting devices again:
/etc/rc.d/dbus restart
So my guess is that there's some problem with dbus startup. I have it in DAEMONS of rc.conf, as well as .xinitrc, the daemon seems to start correctly on boot, and it worked previously, so I have no idea of what could be wrong.
My ~/.xinitrc:
if [ -d /etc/X11/xinit/xinitrc.d ]; then
for f in /etc/X11/xinit/xinitrc.d/*; do
[ -x "$f" ] && . "$f"
done
unset f
fi
if test -z "$DBUS_SESSION_BUS_ADDRESS" ; then
eval 'dbus-launch --sh-syntax --exit-with-session'
fi
numlockx && exec ck-launch-session dbus-launch startlxde
My /etc/rc.conf:
# /etc/rc.conf - Main Configuration for Arch Linux
# LOCALIZATION
# LOCALE: available languages can be listed with the 'locale -a' command
# DAEMON_LOCALE: If set to 'yes', use $LOCALE as the locale during daemon
# startup and during the boot process. If set to 'no', the C locale is used.
# HARDWARECLOCK: set to "", "UTC" or "localtime", any other value will result
# in the hardware clock being left untouched (useful for virtualization)
# Note: Using "localtime" is discouraged, using "" makes hwclock fall back
# to the value in /var/lib/hwclock/adjfile
# TIMEZONE: timezones are found in /usr/share/zoneinfo
# Note: if unset, the value in /etc/localtime is used unchanged
# KEYMAP: keymaps are found in /usr/share/kbd/keymaps
# CONSOLEFONT: found in /usr/share/kbd/consolefonts (only needed for non-US)
# CONSOLEMAP: found in /usr/share/kbd/consoletrans
# USECOLOR: use ANSI color sequences in startup messages
LOCALE="ca_AD.UTF-8"
DAEMON_LOCALE="no"
HARDWARECLOCK="UTC"
TIMEZONE="Europe/Andorra"
KEYMAP="es"
CONSOLEFONT=
CONSOLEMAP=
USECOLOR="yes"
# HARDWARE
# MODULES: Modules to load at boot-up. Blacklisting is no longer supported.
# Replace every !module by an entry as on the following line in a file in
# /etc/modprobe.d:
# blacklist module
# See "man modprobe.conf" for details.
MODULES=()
# Udev settle timeout (default to 30)
UDEV_TIMEOUT=30
# Scan for FakeRAID (dmraid) Volumes at startup
USEDMRAID="no"
# Scan for BTRFS volumes at startup
USEBTRFS="no"
# Scan for LVM volume groups at startup, required if you use LVM
USELVM="no"
# NETWORKING
# HOSTNAME: Hostname of machine. Should also be put in /etc/hosts
HOSTNAME="localhost"
# Use 'ip addr' or 'ls /sys/class/net/' to see all available interfaces.
# Wired network setup
# - interface: name of device (required)
# - address: IP address (leave blank for DHCP)
# - netmask: subnet mask (ignored for DHCP) (optional, defaults to 255.255.255.0)
# - broadcast: broadcast address (ignored for DHCP) (optional)
# - gateway: default route (ignored for DHCP)
# Static IP example
# interface=eth0
# address=192.168.0.2
# netmask=255.255.255.0
# broadcast=192.168.0.255
# gateway=192.168.0.1
# DHCP example
# interface=eth0
# address=
# netmask=
# gateway=
interface=eth0
address=
netmask=
broadcast=
gateway=
# Setting this to "yes" will skip network shutdown.
# This is required if your root device is on NFS.
NETWORK_PERSIST="no"
# Enable these netcfg profiles at boot-up. These are useful if you happen to
# need more advanced network features than the simple network service
# supports, such as multiple network configurations (ie, laptop users)
# - set to 'menu' to present a menu during boot-up (dialog package required)
# - prefix an entry with a ! to disable it
# Network profiles are found in /etc/network.d
# This requires the netcfg package
#NETWORKS=(main)
# DAEMONS
# Daemons to start at boot-up (in this order)
# - prefix a daemon with a ! to disable it
# - prefix a daemon with a @ to start it up in the background
# If you are sure nothing else touches your hardware clock (such as ntpd or
# a dual-boot), you might want to enable 'hwclock'. Note that this will only
# make a difference if the hwclock program has been calibrated correctly.
# If you use a network filesystem you should enable 'netfs'.
DAEMONS=(hwclock syslog-ng network crond alsa dbus cupsd)
Thanks!
Last edited by gamezelda (2011-11-08 19:28:04)

I solved it.
The Wiki page for Mounting for normal users with PCManFM tells to create a "/etc/polkit-1/localauthority/50-local.d/55-myconf.pkla" file specifying the privileges to grant to the user. The problem is that it does not include the privilege needed to mount internal drives (which was what I was trying to mount). To fix it, I added:
;org.freedesktop.udisks.filesystem-mount-system-internal
To the "Action=..." line.
(Though I have no idea why it worked before it broke, or why restarting dbus after initializing my WM fixed it.)
As for the power issues, I've concluded that it was working, but restarting dbus after initializing my WM broke it (my bad for not checking it before restaring dbus). So it all works now.

[SOLVED] I cannot make mounted ext4 partition writeable.

I want to make /dev/sdc2 (mounted on /mnt/SteamLinux) writeable, so I could install Steam games on it.
/etc/fstab
# /etc/fstab: static file system information
# <file system> <dir> <type> <options> <dump> <pass>
# /dev/sdb3
UUID=7cfc361a-47e1-45b9-8429-054d31302402 / ext4 rw,relatime,data=ordered 0 1
# /dev/sdb4
UUID=04b8a615-8738-4d5c-b4de-16a0f92ade4d /home ext4 rw,relatime,data=ordered 0 2
# /dev/sdc2
UUID=1501a760-5c07-4279-a2c2-9695e08a6cdd /mnt/SteamLinux ext4 defaults 0 0
# NTFS drives
/dev/sda1 /mnt/Blue ntfs-3g defaults 0 0
/dev/sdc1 /mnt/Black ntfs-3g defaults 0 0
fsck /dev/sdc2 result:
fsck from util-linux 2.22.2
e2fsck 1.42.7 (21-Jan-2013)
fsck.ext4: Permission denied while trying to open /dev/sdc2
You must have r/w access to the filesystem or be root
What should I do to make it writeable without root access?
Last edited by White girl (2013-03-31 00:10:21)

Mr.Elendig wrote:uhm, just run fsck as root? And for access as a normal user: chown and chmod
Ran fsck as root, it went fine. Remounted /dev/sdc2, then ran
sudo chmod -R +w /dev/sdc2
I assume it's a command to make this partition writeable for regular user. Steam still threw me as readonly.
Got it working by using /mnt/SteamLinux instead of /dev/sdc2.
Steam issue is still not resolved, but it's irrelevant to the thread now... (Steam refuses to download anything to this partition, it returns me as 0MB available space)
Last edited by White girl (2013-03-30 14:16:23)

[Solved] /proc, /sys, Various systemd Directories: No Space?

Howdy-ha, folks. So out of sheer FILESYSTEM (=) USED FREE (-) %USED AVAILABLE rootfs [==========----------] 48% proc [====================] 100% sys [====================] 100% dev [--------------------] 0% run [=-------------------] 0% /dev/sdb2 [==========----------] 48% securityfs [====================] 100% tmpfs [--------------------] 0% devpts [====================] 100% tmpfs [--------------------] 0% cgroup [====================] 100% pstore [====================] 100% efivarfs [====================] 100% cgroup [====================] 100% cgroup [====================] 100% cgroup [====================] 100% cgroup [====================] 100% cgroup [====================] 100% cgroup [====================] 100% cgroup [====================] 100% systemd-1 [====================] 100% systemd-1 [=-------------------] mqueue [====================] 100% hugetlbfs [====================] 100% debugfs [====================] 100% configfs [====================] 100% none [=-------------------] 0% /dev/sdb1 [=-------------------] /dev/mapper/home [==========----------] 49% binfmt_misc [====================] 100% Well, that's not right. I'm not $ testdb
'oxygen-icons-4.10.5-1': description 'oxygen-icons-4.10.5-1': file list is So: What did I screw up this time? Are Last edited by ANOKNUSA (2013-07-28 curiosity, I decided that I'd install GNOME and KDE to see how Steam performed under their conditions. While installing KDE (and before installing GNOME), I receieved an error about no disk space remaining on the device. Incredulous, I ran "dfc" and saw plenty of space left on the drives. "dfc -a" told me this, however:
TOTAL MOUNTED ON
4.2G 8.0G /
0B 0B /proc
0B 0B /sys
3.8G 3.8G /dev
3.8G 3.8G /run
4.2G 8.0G /
0B 0B /sys/kernel/security
3.8G 3.8G /dev/shm
0B 0B /dev/pts
3.8G 3.8G /sys/fs/cgroup
0B 0B /sys/fs/cgroup/systemd
0B 0B /sys/fs/pstore
0B 0B +ys/firmware/efi/efivars
0B 0B /sys/fs/cgroup/cpuset
0B 0B /sys/fs/cgroup/memory
0B 0B /sys/fs/cgroup/devices
0B 0B /sys/fs/cgroup/freezer
0B 0B /sys/fs/cgroup/net_cls
0B 0B /sys/fs/cgroup/blkio
0B 0B /sys/fs/cgroup/bfqio
0B 0B /proc/sys/fs/binfmt_misc
4% 488.3M 511.0M /boot
0B 0B /dev/mqueue
0B 0B /dev/hugepages
0B 0B /sys/kernel/debug
0B 0B /sys/kernel/config
3.8G 3.8G /tmp
4% 488.3M 511.0M /boot
14.6G 28.8G /home
0B 0B /proc/sys/fs/binfmt_misc
even sure what the problem is here, so Im not sure how to begin troubleshooting it. A reboot is about as far as I got, and it didn't help. Incidentally, my pacman databases seem to be screwed up as well, as the installation partially finished before spitting out the error:
file is missing
missing
there any systemd docs in particular I should look into? At the moment my system seems to be running alright, as I was able to log in and post this, at least. I can look into the pacman docs/wiki page for clearing up the database issue when I get a chance. Thanks in advance.
19:28:57)

karol wrote:/proc is a pseudo-filesystem, it doesn't occupy space and it's recreated on boot so don't bother removing anything from /proc.
ewaller wrote:... in fact, both /proc and /sys are the kernel's way of communicating with user space.
I knew their contents were temporary, but didn't realize they didn't in fact exist; since they store vital system/session data, I figured they were more tangible then that. Anyhoo, here's what karol asked for
Filesystem Inodes IUsed IFree IUse% Mounted on
/dev/sdb2 0 0 0 - /
dev 982K 413 982K 1% /dev
run 983K 496 983K 1% /run
tmpfs 983K 1 983K 1% /dev/shm
tmpfs 983K 9 983K 1% /sys/fs/cgroup
/dev/sdb1 0 0 0 - /boot
none 983K 17 983K 1% /tmp
/dev/mapper/home 0 0 0 - /home
I recreated this by trying to install GNOME and got this:
error: could not extract usr/lib/libspandsp.so.2 (Can't create '/usr/lib/libspandsp.so.2')
error: could not extract usr/lib/pkgconfig/spandsp.pc (Can't create '/usr/lib/pkgconfig/spandsp.pc')
error: problem occurred while installing spandsp
error: could not open file /var/lib/pacman/local/spandsp-0.0.6pre21-1/desc: No space left on device
error: could not update database entry spandsp-0.0.6pre21-1
error: could not commit transaction
error: failed to commit transaction (transaction aborted)
Errors occurred, no packages were upgraded.
My first inclination after seeing "not enough space" was to clear the pacman cache and re-sync the mirrors (stupid knee-jerk reaction); now, sync gives me this:
$ pacman -Syy
error: failed to update core (unable to lock database)
error: could not open file /var/lib/pacman/sync/extra.db.part: No space left on device
error: failed to update extra (failed to retrieve some files)
error: failed to update community (unable to lock database)
multilib 107.3 KiB 206K/s 00:01 [-----------------------------------------------------------------------------] 100%
error: could not rename /var/lib/pacman/sync/multilib.db.part to /var/lib/pacman/sync/multilib.db (No space left on device)
error: failed to update multilib (unexpected error)
repo-ck 42.7 KiB 464K/s 00:00 [-----------------------------------------------------------------------------] 100%
error: could not rename /var/lib/pacman/sync/repo-ck.db.part to /var/lib/pacman/sync/repo-ck.db (No space left on device)
error: failed to update repo-ck (unexpected error)
error: failed to synchronize any databases
error: failed to init transaction (unexpected error)

[solved] /proc/acpi/thermal_zone/: No such file or directory

i want to monitor my laptop temperature with conky but i get
Conky: scandir for /proc/acpi/thermal_zone/: No such file or directory
does anyone know what i must install in order for it to work?
Last edited by red-guy (2011-03-21 17:05:00)

red-guy wrote:also, why do you even bother posting if it's not to help?
Because :
stlarch wrote:You are just expected to try to help yourself first. Then, when you've exhausted every effort ask. It's the Arch way. The wiki is your best friend.
And also because as forum moderator, we have to keep the boards as clean as possible. For you the problem might be new, but for many users here, they have seen these types of threads many times which have also been answered over and over again and also documented in the wiki. The wiki is a resource that has been created by the collective efforts of the Arch users - present and past. Make use of it.
As a general rule, if you have an issue, search the wiki, then the internet, then the forums for similar threads and if you still have problems then post a thread detailing what attempts you have made in order to fix the problem. That way, people don't give you options that you have already tried and know that they don't work.
In addition, please go through the forum rules to familiarize yourself with the basic rules and policies of the Arch forums.

[Solved]Permission issues with mounted media

hello everyone. i have a issue that is more of a annoyance than a problem. when i attach my usb hard drive i get this error
Rejected send message, 1 matched rules; type="method_call", sender=":1.15" (uid=1000 pid=8611 comm="exo-mount) interface="org.freedesktop.Hal.Device.Volume" member="Mount" error name="(unset)" requested_reply=0 destination="org.freedesktop.Hal" (uid=0 pid=3138 comm="/usr/sbin/hald)).
and am forced to open up the file manager as root to do anything with the device or its contents after transfer. if anyone has a suggestion or fix please enlighten me. im using openbox and thunar. i used the ck-launch-session in my ~/.xinitrc. thank you ahead of time for your help.
Last edited by trishtren18 (2009-12-20 16:37:17)

DeSian wrote:
jasonwryan wrote:Have you tried the fixes suggested in the HAL entry? It sounds like a policy kit fix...
I've tried every way before and this also:
Try adding /usr/sbin/console-kit-daemon to /etc/rc.local that has fixed it for me, for some reason it mustn't of been getting started
still have the same error message by trying to mount USB device.
Error:
Rejected send message, 1 matched rules; type="method_call", sender=":1.10" (uid=1000 pid=1756 comm="pcmanfm) interface="org.freedesktop.Hal.Device.Volume" member="Mount" error name="(unset)" requested_reply=0 destination="org.freedesktop.Hal" (uid=0 pid=1598 comm="/usr/sbin/hald))
and i can't Shutdown and Reboot from LXDE
http://wiki.archlinux.org/index.php/LXD … _from_LXDE
best regards
This thread is marked solved - you may want to open a new one & include details about your DE/WM, any errors, what happens when you try to mount manually etc...

[solved] when it's mounted it is actually unmounted and vice versa?

I have a strange problem. I mounted one of my partitions (sdb2) manually as a regular user. Now I can't unmount it any more. I can't unmount it as root. Although sdb2 is nut mounted according to mtab, it somehow remains mounted because ls /mnt/archive still lists the files as if sdb2 was stil mounted. I can open the directories. I can open files on this 'unmounted' partition in my file manager (Xfe). Even after rebooting I can access sdb2 via mount point /mnt/archive although sdb2 shouldn't be mounted automatically because of the noauto in fstb. So, after rebooting I can access the directories and files on sdb2 without mounting the partition. When I mount it manually now, I can't access anything: /mnt/archive is an empty directory. And now there is an entry in mtab that says that sdb2 is mount on /mnt/archive. But after unmounting sdb2 /mnt/archive is no longer an empty directory. All the files and directories on sdb2 are accessible.
Before all this 33% of my root space was used. Now it's 76%. Whenever I mounted a partition on a mount point in /mnt before, it didn't change this used space on my root partition. So why does it seem to do that now?
Can anyone explain what is going wrong here and how to solve it?
Ther is no problem with sdb1. After mounting it, I can access the directories and files on it. The used space on my root partition is not increased. After unmounting sdb1 /mnt/vbox is an empty file.
fstab:
devpts /dev/pts devpts defaults 0 0
shm /dev/shm tmpfs nodev,nosuid 0 0
/dev/sda1 /boot ext2 defaults 0 1
/dev/sda2 swap swap defaults 0 0
/dev/sda3 / ext3 defaults 0 1
/dev/sda5 /home reiserfs defaults 0 1
/dev/sda7 /home/phnx2/music reiserfs user,rw,noauto 0 0
/dev/sdb1 /mnt/vbox ext3 user,rw,noauto 0 0
/dev/sdb2 /mnt/archive ext3 user,rw,noauto 0 0
Last edited by lnx (2011-06-14 09:43:19)

I suppose your first manual mounting as user didn’t succeed, so you accidentally copied the contents you wanted to be on the sdb2 partition while it wasn’t mounted. So those files remained on the same (/) partition, but under the “mount point” /mnt/archive. Then if you mount sdb2 over it, its contents become invisible and inaccessible, but you can access the empty sdb2. You should backup the files you have in /mnt/archive, really mount sdb2, and then copy the files “back” to /mnt/archive.

[SOLVED] Suddenly unable to mount samba share using cifs

I have a home server running ArchLinux, hosting an SMB share. My client box is also ArchLinux, both are up to date, running Linux-ck 3.9.2-2-ck. Prior to rebooting both machines around twenty minutes ago, the share mounted fine for months.
Here is the extent of the "verbosity" I receive from mount:
mount error(13): Permission denied
Refer to the mount.cifs(8) manual page (e.g. man mount.cifs)
Here is my fstab:
# /etc/fstab: static file system information
# <file system> <dir> <type> <options> <dump> <pass>
tmpfs /tmp tmpfs nodev,nosuid 0 0
# UUID=71066ae2-40ec-4125-9db7-d04b6a04f712
UUID=71066ae2-40ec-4125-9db7-d04b6a04f712 / ext4 rw,relatime,data=ordered 0 2
# UUID=172faa6a-9cca-4d9e-a0b9-a5da3ea81922
UUID=172faa6a-9cca-4d9e-a0b9-a5da3ea81922 /boot ext2 rw,relatime 0 2
# UUID=65023815-33fc-4ebd-b245-65683201fbcf
UUID=65023815-33fc-4ebd-b245-65683201fbcf /home ext4 rw,relatime,data=ordered 0 2
UUID=1a23d461-fa2b-4ea4-8e58-e7efba3f3bed /media/Storage ext3 rw 0 2
//ARRAY/Array /media/Array cifs credentials=/home/xaero/.smbpasswd,iocharset=utf8,uid=1000,gid=1000,nounix,sec=ntlm 0 0
I have tried any number of different options on that final line defining this share now:
I have tried //array/array (which is what it was originally) and //ARRAY/Array (which is case-sensitive) as well as any combination of using my credentials file (which used to work) or user=,pass= as well changing my credentials file to use quotation marks around my password as it has special characters. I've also read of using sec=ntlm fixing mount issues, but in my case it did not. I'm kind of scratching my head here as passing --verbose to mount yields zero additional information... the uid and gid entries were necessary in the past to mount this share, however I have tried both with and without them, to no avail.
I rely on SMB in lieu of sshfs as there isn't a stable sshfs implementation for Windows users, which there are some on my network; I also find for whatever reason SMB happens to be faster.
Last edited by Xaero252 (2013-05-19 21:45:30)

I'm not exactly sure what fixed this... I looked at the configuration file to make sure I hadn't missed it being updated, and it was in the new format; everything setup correctly (I remember having to edit it not long ago to fix something, probably for the update which you mentioned) I reverted my fstab back to the way it was before (making backups is good) and restarted the smbd on the server numerous times... at some point it just started working again. I wish I had a more concrete answer for documentation sake, but I was literally just rebooting/restarting services in desperation with little to no config hacking between and suddenly things clicked. I'm also no longer running the sec=ntlm option..
Thanks for reminding me to check my config though, when I updated I had forgotten to enable user restriction (guest was enabled, and certain directories weren't user-specific)

My HDD died and my Time Machine won't mount, what can I do?

My late 2011 MBP lost its drive due to some mystery physical damage, so I popped it out and replaced it with a Crucial SSD. I thought it was weird that I couldn't reboot from my time machine backup on a WD My Book 3TB external, I had to get a friend to make a bootable Mountain Lion flash drive for me. That worked like a charm, but the problem is actually with the time machine disk... it's dead too.
What's happening is that when I plug it in it will mount for maybe 30 seconds... I can see one or sometimes both partitions and it will sometimes appear in Disk Utility, sometimes not. Sometimes the files appear on the drive, sometimes not. Whenever I try to do any action on the disk, whether its open a folder or repair permissions or whatever, the computer hangs up until it's disconnected. No matter what I do, the disk will dismount "improperly" after 1-2 minutes.
The drive itself is an ex-government USB 3.0 external. I have a spare identical drive around, so I took that apart and used its SATA hookup on my time machine drive, which didn't fix anything. This extra drive fully assembled also mounts and works fine. So that rules out the computer and the SATA connection, I think.
So what can I do to save my data short of mailing in to a recovery place? Are there any utilities that can pull data from an unmounted drive? Any tricks to keep it from dismounting? Running out of ideas here. Thanks for any help you guys can give.

This seems to be a common occurance with Western Digital external drives. More than like the physical drive inside the enclosure is fine, maybe not, but the enclosures electronics are failing. Only way to tell is to remove the drive from the enclosure and connect it to your Mac with a SATA to USB adapter. If the drive is fine you will then be able to read from it and restore your Mac from it.
NOTE:
The late 2011 model and beyond can use the Apple Online Internet Recovery system. That is where you boot the system from the Apple server from over the internet. To use that you have to hold down the Command + Option/Alt + r keys at startup and keep them held down until you see a globe on the screen.

[SOLVED] /proc must be mounted! ...what? o.O

Similar Messages

Maybe you are looking for