I installed the php4-mysql module or w/e and then rebooted. After I rebooted I noticed nothing started/loaded. I could login, and instead of saying Suzzy: at the bash screen I received a (none): I then rebooted to see if I could catch the screen and I saw it said Input/output Error when trying to load the init.d stuff. I went into my /etc/init.d/ folder and tried to execute some commands like reboot. I typed ./reboot and received 'bash - ./reboot Input/output error' Then I tried ./reboot > blah.txt to output the error into a file or something. I received 'bash - ./reboot > blah.txt Read-only system. Is it mounting my harddrive as read-only cuasing nothing to load?

you could try remount it r/w:
mount -o rw /dev/hda1
(of course, you have to change the device name appropriately)

If it works, check /etc/fstab

Anybody?

Bump. Guys I really need help.

did you try remounting the hard drive r/w as suggested above?

try with the appropriate device of course. If that fails, check dmesg... this looks like a potential sign of a future failure of drive.

Alright I do it and the command works, and I can make files now, but I still get an Input/Output error when I try to execute /etc/init.d/rc and /etc/init.d/rcS

Is dmesg showing anything unusual?

EXT3-fs: INFO: recovery required on readonly filesystem.
EXT3-fs: write access wil be enabled during recovery
kjournald starting. Commit interval 5 seconds
EXT3-fs: recovery complete.
EXT3-fs: mounted filesystem with ordered data mode.
EXT3-FS on hde1, internal journal
NET: Registered protocol family 10
IPv6 over IPv4 tunneling driver

That's that bottom portion of it.

Boot to a single-user runlevel or from a boot CD, and e*fsck the drive. You may need to check your IDE cables if errors keep recurring, or you might need to bump down the DMA level.

You might also be encountering some of the known flakiness in ext3 journaling, in which case you could either upgrade your kernel or you could simply mount the partition as ext2 (the better option is to upgrade the kernel if you're running a version with the known-bad journaling code)