Filesystem corruption

[mxairman]

Hello.

I'm having a problem with my server. 3 days ago, I was unable to access the web GUI and when i logged in with ssh, it was giving me segmentation fault error. I was unable to run anything from within the virtual machines installed on it. Ping was ok.

I asked my web host for a reboot, and they informed me after the reboot that they had to run fsck on it after the reboot. Afterwards, I had to run fsck on one of the virtual machines as well.

Now I'm having a similar problem: the hosts are working ok, but when I try to open the proxmox web gui it gives me the following message:

[B]Internal Server Error[/B]

 The server encountered an internal error or misconfiguration and was unable to complete your request. Please contact the server administrator, root and inform them of the  time the error occurred, and anything you might have done that may have  caused the error.
    [2602]ERR:  24:  Error in Perl code: Could not open dbm file  /var/lib/libapache-sessionx-perl/DB_File/sessions.db: Read-only file  system at /usr/share/perl5/Apache/Session/Store/DB_File.pm line 32.    
 Apache Embperl 2.2.0 [Sun Oct  3 18:13:34 2010]

I try to ssh into the server and I get the following message:

ssh_exchange_identification: Connection closed by remote host

I'm running 5 KVM VM's on it, and I didn't do any update, upgrade or configuration change before this problem.

Troubleshooting becomes a little difficult being a remote server, so I don't have much access to server logs, etc right now.

I'd appreciate if anyone has an idea of what would be the problem. Thank you in advance. Best regards.

 

[typo3usa]

This smells of disk issue. The drive may have gone into READ ONLY MODE to protect its data...

In short - if the system had to do a fsck on reboot - did it show any errors?
what was the report from the Datacenter in regards to the drives?

Do you have backups ? Is this a Colo or your own system?

 

[mxairman]

Hi typo3usa.

Thanks for the reply. Problem came again for the 3rd time (waiting for fsck from the datacenter). I read in other post that there was some problem with the virtio-net driver which should be solved after a kernel upgrade. I did apt-get upgrade before the 3rd failure, so if the problem is not solved, I'll also assume it's a disk failure. The guys at the datacenter told me that the hard disks look good, and that the RAID1 array is working properly. I'll post the results. Thank you.