Centos 6.5 crashes

[zonepilot]

I have installed and run Zoneminder under Centos 6.5. It seemingly works fine (with SE-linux off), however after some time it has caused my server to crash. It hangs and keyboard is blinking, and only way to come back up is to hard reboot. On 3 occasions it stopped with this screen-output (see image screen-crash-1) and the latest it showed a screen like image 2.
Could anyone help me finding out what could be the cause of this?
I do not have a clue what these trace calls are or how they appear, other than they only started appearing after I installed Zoneminder.
Cheers,

[connortechnology]

Those traces show linux going nuts looking to write a file.

The problem could be due to fs corruption, bad HD, bad ram. Lots of things. ZM isn't at fault, it is just pushing your system.

Start with fsck, then mem testing.

[zonepilot]

Hi

Thanks for guiding me on this – I realise it is a hardware failure of some kind. I tried using FSCK but was unable to do – it is a LVM and I could not unmount the drive for checking, and could not reboot the system on a LiveCD for some reason – so gave up on that. However the system was running fine until today, when it crashed again. I then noticed when I reboot the machine that I get the following message briefly shown during POST: hub 1-0:1.0: over-current change on port 7

Anybody have an idea what this could be?

Regards

From: Isaac Connor [mailto:notifications@github.com]
Sent: 03 December 2014 16:09
To: ZoneMinder/ZoneMinder
Cc: zonepilot
Subject: Re: [ZoneMinder] Centos 6.5 crashes (#619)

Those traces show linux going nuts looking to write a file.

The problem could be due to fs corruption, bad HD, bad ram. Lots of things. ZM isn't at fault, it is just pushing your system.

Start with fsck, then mem testing.

—
Reply to this email directly or view it on GitHub #619 (comment) . https://github.com/notifications/beacon/AJmJ9O845c8i6E5qZspYbhHk4XEBTSXwks5nTx75gaJpZM4DDv3O.gif

No virus found in this message.
Checked by AVG - www.avg.com
Version: 2014.0.4794 / Virus Database: 4235/8683 - Release Date: 12/05/14

[nzbtuxnews]

May be late replying but...

the current over-charge on the usb port may or may not be related to the file write issue you had. If related then I would check for motherboard shorts with the case, if not then I'd suspect motherboard failure.

If not related, then the file write issue is likely due to dying HDD or bad ram, most likely dying HDD. I
I literally went through dozens of drives with similar errors. Basically what you saw is a kernel panic.

First start off by doing a fsck from a boot CD on the drive (on all ext4 partitions) that is likely to be failing. If fsck fixes some stuff, BACKUP right away.

That reminds me when I had a Slackware server doing the same thing because the mdadm driver was crashing due to HDD failure (WD greens.........) Live n Learn