Welcome to WebmasterWorld Guest from 188.8.131.52
Forum Moderators: bakedjake
Here's the extract from messages where it rebooted following my power cycle:-
Jul 6 14:47:02 MyMachine kernel: EXT3-fs: INFO: recovery required on readonly filesystem.
Jul 6 14:47:02 MyMachine kernel: EXT3-fs: write access will be enabled during recovery.
Jul 6 14:47:02 MyMachine kernel: kjournald starting. Commit interval 5 seconds
Jul 6 14:47:02 MyMachine kernel: EXT3-fs: sda1: orphan cleanup on readonly fs
Jul 6 14:47:02 MyMachine kernel: EXT3-fs: sda1: 8 orphan inodes deleted
Jul 6 14:47:02 MyMachine kernel: EXT3-fs: recovery complete.
Jul 6 14:47:02 MyMachine kernel: EXT3-fs: mounted filesystem with ordered data mode.
Other than that the usual port scanning and SSH hacking attempts.
I'll move SSH from port 22 and also to a new IP...
Not that I'll probably be able to say anything of much use, my sysadmin skills are very amateur (i.e. learnt on the job when something breaks...).
If you want my opinion though I'd say you're having hardware rather than hacking problems, maybe something along these lines:
Try inputting "dmesg", that might get you a swathe of angst-causing messages.
RAID isn't a magic bullet unfortunately, particulary not software raid, which has caused me a fair bit of pain in the past.
dmesg might help
Don't seem to have that.
Nothing in /var/log for the RAID disks.
or maybe your raid setup has a log file.
Can't find one....
It's hardware RAID, which I can't access unless I'm in front of the machine, so might need to take a trip down to the datacenter (it's a co-lo box).
Thanks for all the help anyway, I'll keep digging.