| View previous topic :: View next topic |
| Author |
Message |
caker
Linode.com Staff
Joined: 15 Apr 2003
Posts: 2715
Location: Galloway, NJ
|
 Posted: Mon Sep 21, 2009 12:36 pm Post subject: Reboot: fremont88 |
 |
|
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 |
|
| Back to top |
|
 |
Darxus
Senior Newbie
Joined: 24 Jan 2007
Posts: 6
Location: Boston Massachusetts
|
| Posted: Mon Sep 21, 2009 2:21 pm Post subject: |
|
|
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. |
|
| Back to top |
|
|
kpavery
Newbie
Joined: 21 Sep 2009
Posts: 2
|
| Posted: Mon Sep 21, 2009 3:47 pm Post subject: |
|
|
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:
| Code: | :: 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. |
|
| Back to top |
|
|
Darxus
Senior Newbie
Joined: 24 Jan 2007
Posts: 6
Location: Boston Massachusetts
|
| Posted: Mon Sep 21, 2009 3:56 pm Post subject: |
|
|
kpavery: That sucks. Backups are good.
Did you try the "e2fsck -b 8193 <device>" that it recommended? |
|
| Back to top |
|
|
caker
Linode.com Staff
Joined: 15 Apr 2003
Posts: 2715
Location: Galloway, NJ
|
| Posted: Mon Sep 21, 2009 3:59 pm Post subject: |
|
|
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 |
|
| Back to top |
|
|
kpavery
Newbie
Joined: 21 Sep 2009
Posts: 2
|
| Posted: Mon Sep 21, 2009 4:01 pm Post subject: |
|
|
Darxus, yes thank god i have one. 
Caker, thank you. I had no idea. sorry about that. |
|
| Back to top |
|
|
Darxus
Senior Newbie
Joined: 24 Jan 2007
Posts: 6
Location: Boston Massachusetts
|
| Posted: Fri Sep 25, 2009 9:55 am Post subject: |
|
|
| Any progress on that investigation into preventing this from recurring? |
|
| Back to top |
|
|
caker
Linode.com Staff
Joined: 15 Apr 2003
Posts: 2715
Location: Galloway, NJ
|
| Posted: Fri Sep 25, 2009 10:07 am Post subject: |
|
|
| Darxus wrote: | | 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 |
|
| Back to top |
|
|
Darxus
Senior Newbie
Joined: 24 Jan 2007
Posts: 6
Location: Boston Massachusetts
|
| Posted: Fri Sep 25, 2009 10:12 am Post subject: |
|
|
| Thanks, caker. |
|
| Back to top |
|
|
|
RSS 2.0 | Additional RSS options
FAQ
Search
Memberlist
Usergroups
Register
Profile
Log in to check your private messages
Log in
