Did I fry my hard drive?

[JMJ_coder]

Hello,

On my Lenovo T61, I accidentally left it on during my trip home the other day from the office -- which has a bunch of speed bumps and potholes. It seemed unscathed, but a little later it started to give me errors on boot and halting -- a reboot would fix it. Now, it refuses to ever boot, it always gives me the boot error.

System:
Lenovo T61
128GB 7200 RPM Hard Drive (looking at the basic dmesg output, I'm guessing a Seagate)
NetBSD 4.0.1

I only have 80 GB actually being used in the partition scheme (1 partition):

  512 MB /
 4096 MB swap
 4096 MB /tmp
44544 MB /usr
 4096 MB /var
24576 MB /home

here is the error message:

wd0 at atabus1 drive 0: <ST506>
wd0: 69632 KB, 1024 cyl, 8 head, 17 sec, 512 bytes/sect x 139264 sectors
wd0: drive supports PIO mode 4, DMA mode 2, Ultra-DMA mode 6 (Ultra/133)
wd0(ahcisata0:0:0): using PIO mode 4, DMA mode 2, Ultra-DMA mode 6 (Ultra/133) (using DMA)
wd0: mbr partition exceeds disk size
wd0: mbr partition exceeds disk size
wd0: mbr partition exceeds disk size
wd0: mbr partition exceeds disk size
boot device: <unknown>
root device:

Here it is halted and awaits a command. If I try to use wd0a, I get:

root device: wd0a
dump device (default wd0b): wd0b
file system (default generic): generic
root on wd0a dumps on wd0b
wd0: mbr partition exceeds disk size
no file system for wd0 (dev 0x0)
cannot mount root, error = 79
root device (default wd0a):

Here again it halts and waits. If I select ffs for the file system (which is how the installer configured it), I get:

root device (default wd0a):
dump device (default wd0b): wd0b
file system (default generic): generic
root on wd0a dumps on wd0b
wd0: mbr partition exceeds disk size
cannot mount root, error = 22
root device (default wd0a):

I also noticed that this only seems to happen when dhclient is enabled and the cable plugged in -- but that could be a freakish coincidence. This has only started to happen in the past two days since I drove home with the laptop on. Any ideas?