fremont88 had an issue with its RAID subsystem and required a reboot to recover. We're investigating ways to prevent this from occurring. Linodes are coming back on line now.

We apologize for the inconvenience.

-Chris

I believe that's the first time I've had my host rebooted on me in the 2.7 years I've had a linode.

Thanks.

sorry if this isn't where i should post this, but i'm on fremont88 and i have filesystem issues.

when i login to lish i get an error message that looks like this:

:: Checking Filesystems                                                  [BUSY] /dev/xvda:
The superblock could not be read or does not describe a correct ext2
filesystem.  If the device is valid and it really contains an ext2
filesystem (and not swap or ufs or something else), then the superblock
is corrupt, and you might try running e2fsck with an alternate superblock:
    e2fsck -b 8193 <device>

                                                                         [FAIL]

*****************  FILESYSTEM CHECK FAILED  ****************
*                                                          *
*  Please repair manually and reboot. Note that the root   *
*  file system is currently mounted read-only. To remount  *
*  it read-write type: mount -n -o remount,rw /            *
*  When you exit the maintenance shell the system will     *
*  reboot automatically.                                   *
*                                                          *
************************************************************

i'm not exactly sure what to do to fix this error. i fsck'ed the file system, without the -f flag it says no problems, and with the -f flag it checks it but doesn't do any repairs.

kpavery: That sucks. Backups are good.

Did you try the "e2fsck -b 8193 <device>" that it recommended?

This is an Arch Linux problem. They updated udev and compiled out support for older kernels.

kpavery - edit your configuration profile and select a newer kernel (2.6.30 for example), save, and reboot. You'll be fine.

-Chris

Darxus, yes thank god i have one.

Caker, thank you. I had no idea. sorry about that.

Any progress on that investigation into preventing this from recurring?

We believe this was caused by a flaky drive, which has since been replaced.

-Chris

Thanks, caker.