I've got Debian server with one disk. No dual boot or anything fancy. Just Debian 6.0 (Squeeze).
I rebooted the server today and now it doesn't boot. I get the following (from GRUB):
error: hd0,msdos out of disk
I then get a grub prompt grub rescue>
I've been googling for ages with no luck.
/etc/fstab
> #/etc/fstab: static file system information.
> #
> # <file system> <mount point> <type> <options> <dump> <pass>
> aufs / aufs rw 0 0
> tmpfs /tmp tmpfs nosuid,nodev 0 0
I've run debian rescue mode and looked through the syslog. I see hundreds of entries like this:
Jun 30 22:51:08 kernel: [ 615.217382] sd 2:0:0:0: [sda] Unhandled error code
Jun 30 22:51:08 kernel: [ 615.217385] sd 2:0:0:0: [sda] Result: hostbyte=DID_BAD_TARGET driverbyte=DRIVER_OK
Jun 30 22:51:08 kernel: [ 615.217389] sd 2:0:0:0: [sda] CDB: Read(10): 28 00 00 00 00 00 00 00 08 00
Jun 30 22:51:08 kernel: [ 615.217399] end_request: I/O error, dev sda, logical block 0
Jun 30 22:51:08 kernel: [ 615.217402] Buffer I/O error on device sda, logical block 0
I've never dealt with that error before, but this thread addresses one likely cause of the error. It suggests you may have installed GRUB to a partition, rather than to the MBR, and to fix booting from the installation CD in rescue mode, then doing:
Of course replace /dev/sda1 and /dev/sda with their proper equivalents on your system.
Well i've write an article about how to repair grub loader here I think that it is helpful in your situation
Most likely your MBR which includes the master partition table has been (partially) corrupted. I would interpret that grub error message as that a record in the partition table points to a region which is outside of the drive (msdos just means the type of the partitioning). Another possibility could be that something has changed in the BIOS settings that affected the drive geometry (number of heds, cyls, tracks and sectors). Have you checked that the battery on the moverboard that feeds CMOS is okay?