Is anyone else experiencing issues with host56? It is appearing to have disk space issues... when I login to lish, lish (not my VPS) gives this error:

Cannot make directory '/var/run/screen/S-ericgatenby': No space left on device

When I try to boot, I get this:

xen_linode_boot: failed to get domid
xen_linode_boot: warning - li-network might not have ran

I entered a support ticket a support just over 2 hours ago and am awaiting response.

Yes, I'm having the same issue.

Same for me...
Started after the HE network problems.
-- jp

Yeah well the crash on 56 has destroyed my node , absolutely screwed it, it single user mode I got this:

EXT3-fs: mounted filesystem with ordered data mode.
VFS: Mounted root (ext3 filesystem) readonly.
Freeing unused kernel memory: 204k freed
INIT: version 2.86 booting
INIT: cannot execute "/etc/init.d/rcS"
Give root password for maintenance
(or type Control-D to continue):
Login incorrect.
Give root password for maintenance
(or type Control-D to continue):
(none) ~ # w
Error: /proc must be mounted
To mount /proc at boot you need an /etc/fstab line like:
proc /proc proc defaults
In the meantime, mount proc /proc -t proc
(none) ~ # df
Filesystem 1K-blocks Used Available Use% Mounted on
/dev/hda1 2233171 1281262 951909 58% /
sysfs 2233171 1281262 951909 58% /sys
udev 2233171 1281262 951909 58% /dev
devpts 2233171 1281262 951909 58% /dev/pts
/dev/hda3 2233171 1281262 951909 58% /home
none 2233171 1281262 951909 58% /dev/shm
(none) ~ # fdisk /dev/hda1
Device contains neither a valid DOS partition table, nor Sun, SGI or OSF disklabel
Building a new DOS disklabel. Changes will remain in memory only,
until you decide to write them. After that, of course, the previous
content won't be recoverable.

Warning: invalid flag 0x0000 of partition table 4 will be corrected by w(rite)

Command (m for help): p

Disk /dev/hda1: 2361 MB, 2361393152 bytes
255 heads, 63 sectors/track, 287 cylinders
Units = cylinders of 16065 * 512 = 8225280 bytes

Device Boot Start End Blocks Id System

Command (m for help): q

(none) ~ # cd /home
(none) home # ls
(none) home #


This is catastrophic, I need my system to do things so I can print stuff for my soccer game tomorrow, what can I do? Cry?

cherring: I'm sorry to hear about your issues.

Can't you redeploy a fresh distro via the distro wizard, then restore your data +config files from your latest backups?

Not most fun of things, but should get you back on your feet with minimal loss, especially if you've been running nightly backups that stores a copy of data off-site (e.g. with rdiff-backup).

Also, please keep in mind that this is one of the risks of a beta program. If you need stability, you're better off seeing if you can move back to a regular UML-based Linode.

df is going to show the contents of /etc/mtab, which, at this point isn't valid.



hda1 won't have a partition, so that makes sense, too.



/home isn't mounted yet, so that makes sense that the mountpoint is empty.

I'm almost 100% certain that the destruction was limited to your /etc/inittab and /etc/fstab files. If you can repair those, you'll be back in business...

-Chris

Unfortunately my backup system was on hiatus but it's ok because caker has gone in and fixed the things he mentioned above as the problem and all my data is fine, I'm so relieved, and off to get my backup system running again.

I understand that this is a risk of a beta, and frankly feel a little stupid that my backups weren't running, and am so grateful that caker was able to sort me out, once again an example of the guys at Linode going above and beyond, manky thanks to him, he saved my bacon.