When you got all those errors in your log for /dev/hdc, did you have a cd in the cdrom drive? Perhaps it was a cd that did not make sense as a file system.
If you have a typical motherboard with two IDE controllers, the first device on the primary controller will be /dev/hda.
This is where most people put their hard drive if they have only one hard drive. If you have a scsi hard drives then these get named things like /dev/sda. (If you have a very modern motherboard with serial ATA drives then what do these get named? As I recall they also get named /dev/s..., but I don't have such a system near me at the moment.)
People will suggest that you learn to consult your /etc/fstab file. But nowadays (FC3) it is not so simple to interpret this file as in olden times (FC2). If you run the udev service, it rewrites this file for you at boot time , so trying to edit this file is futile.
In olden times, the typical /etc/fstab setup had a hard drive /dev/hda. On the drive were several partitions /dev/hda1, /dev/hda2, etc. Each partition was associated with a file system (in window's terms, a folder). In the FC3 /etc/fstab you see references to labels. When you create a partition on a device, you can give it a label. So instead of referring to the partition as /dev/hda1 we might refer to it by its label. FC3 has some standard labels that it uses, but I've never seen their system explained. It is no longer simple to glance at /etc/fstab and tell what devices are on you machine. Perhaps someone can tell us some other way to discover this.
What things must we learn about to control our /etc/fstab on the default FC3 installation? udev and fstab-sync and the "HAL" daemon, which seems to have no man page of its own.
"Never let the task you are trying to accomplish distract you from the study of computers."