That line is not an error, however, it does appear in the midst of detecting your drive's partitions, for example:
QUOTE
hda: MAXTOR 6L060L3, ATA DISK drive
hdc: IBM-DTLA-307045, ATA DISK drive
ide0 at 0x1f0-0x1f7,0x3f6 on irq 14
ide1 at 0x170-0x177,0x376 on irq 15
blk: queue c02f5844, I/O limit 4095Mb (mask 0xffffffff)
hda: 117266688 sectors (60041 MB) w/1819KiB Cache, CHS=116336/16/63, UDMA(100)
blk: queue c02f5be4, I/O limit 4095Mb (mask 0xffffffff)
hdc: 90069840 sectors (46116 MB) w/1916KiB Cache, CHS=89355/16/63, UDMA(100)
Partition check:
hda: hda1 hda2 < hda5 hda6 hda7 >
hdc: unknown partition table
There may be a problem with your partition table or the drive itself.
Does the system lock up solid (ie. pressing the num lock doesn't make the LED flash), or does it seem like it's frozen? Linux boot ups can some times be deceiving. When it has trouble initializing something, it will work on it for a long period of time (sometimes upwards to 5 minutes) until finally it skips it and moves along. If you can press the num lock button and it flashes, then let the server sit there and continue it's bootup. After it finally boots, log in as root, and view the output of "dmesg" (/var/log/dmesg) or any errors or warnings.