dallas64 went unresponsive. We took this opportunity to update it to our latest Xen stack. Linodes are booting up now.

-Tom

I'm seeing massive filesystem damage on my linode on dallas64.

My linode on dallas64 isn't even booting up. I've tried the boot button on the Linode Manager and the boot command from lish. The Linode Manager page is stuck at 0% and the lish status command always gives "Powered Off"

I'm at a bit of a loss as to what I should try next...

Ah, it's finally rebooting now.

Waiting on fsck to se if I have any damage like jasonuhl...

The damage I'm seeing looks a lot worse than what I'd expect from just an unclean shudown.

I was actually down in single user mode investigating my filesystem problems (stuff was failing with EIO all over the place) before dallas64 went down, so I kinda suspect that the host going unresponsive is a symptom of some deeper problem rather than the cause.

Well my Linode hasn't come back up automatically, the status is as follows:

JobID: 741945 - Lassie initiated boot
Job Entered 09/09/2008 09:55:47 PM Status In Queue
Host Start Date Host Finish Date
Host Duration waiting on host Host Message

Edit: I logged into the console, and it seems to have kickstarted it, so its coming up - slowly - now.

It would be good if we could get an email when one of our Linodes goes down, is this an option I missed somewhere?