To clarify, this "server" is actually a virtual machine (i.e., a "Cloud Server" running on Rackspace.com). It was allocated/instantiated by a co-worker via their website, which has a browser-hosted control panel interface.
Quote:
Originally Posted by Habitual
Look at /etc/fstab?
Mentions cryptsetup That's a keyword. Does the host utilize what appears to be disk encryption?
|
We have never made any attempt to encrypt the file system, if that's what you mean.
Quote:
Originally Posted by Habitual
is a repair suggestion I've read.
|
Some googling
reveals that this means "attempt to correct a system with broken dependencies in place." I have tried running this:
Code:
sudo apt-get install -f
and the result:
Code:
0 upgraded, 0 newly installed, 0 to remove and 0 not upgraded
.
Seems to me I would need to run
apt-get install -f <package-name> but I've no idea which package to specify.
Quote:
Originally Posted by Habitual
You are "running a server"?
|
As clarified above, I'm talking about a virtual machine running on Rackspace's system.
Quote:
Originally Posted by Habitual
I don't fix computers, sorry. "blah blah blah" doesn't work for me.
|
I apologize if this is confusing. I redacted the lengthy output of the command in the interest of focusing on the problem. Most of the other output seemed fine so it didn't seem relevant.
Quote:
Originally Posted by Habitual
|
I have only rarely dealt with an fstab file and then only under close supervision. It's been my experience with virtual machines that complaints sometimes arise about the 'canonical' device being found or something. This seems to happen because the host (a hypervisor I presume) apparently (and inexplicably) renames the default device to something else under certain conditions and certain configuration values end up complaining about it. This is currently the contents of /etc/fstab:
Code:
$ cat /etc/fstab
# CLOUD_IMG: This file was created/modified by the Cloud Image build process
/dev/xvda1 / ext4 errors=remount-ro,noatime,barrier=0 0 1
#/dev/xvdc1 none swap sw 0 0
/dev/xvdb1 /var/www/html/cdn1 ext3 defaults,noatime,_netdev,nofail 0 2
/dev/xvdc1 /var/www/vlnt_user_upload ext3 defaults,noatime,_netdev,nofail 0 2
df says this:
Code:
~$ sudo df
Filesystem 1K-blocks Used Available Use% Mounted on
udev 2011096 0 2011096 0% /dev
tmpfs 404076 5732 398344 2% /run
/dev/xvda1 81254044 3998536 77239124 5% /
tmpfs 2020376 0 2020376 0% /dev/shm
tmpfs 5120 0 5120 0% /run/lock
tmpfs 2020376 0 2020376 0% /sys/fs/cgroup
/dev/xvdb1 77277192 53144 73291940 1% /var/www/html/cdn1
/dev/xvdc1 77277192 578660 72766424 1% /var/www/user_upload
tmpfs 404528 0 404528 0% /run/user/1002
This contradicts my hypothesis that the hypervisor was changing device names. Oh well.
Quote:
Originally Posted by Habitual
Good Luck.
|
Thanks.
Quote:
Originally Posted by Habitual
"Fix" is restore /etc/fstab from backup.
|
I've never modified this file and, having done a
sudo find / -name "*fstab*", it would appear there are no backup files from which to restore.
I've been googling these errors. No epihanies yet.