Crashing and on booting up again there is only an Ash prompt!?!?

[flipjargendy]

This has happened in a fresh install of Debian Lenny and after doing a dist-upgrade. It has happen both times while running apt-get update and putting a CDRW in which would not mount. I don't know if that actually has to do with it. I've re-formated and re-installed twice now. It happened two times in a row. Each time when I boot up there are a bunch of errors and then it goes to an Ash shell.

Any ideas what could actually be doing this?

I'm going to try updating after I post this and see if it only happens then.

Thanks for any input :-)

[flipjargendy]

I've included the output that I get before being givin the Ash prompt.

I had to reinstall again!

It seems that there is no definite time span from a fresh install to when this error happens. I'm not sure if it has to do with when the sector of the HD is accessed or what. If it is my physical HD and not just a corrupt block... maybe something physically happen to my HD? i've formated many times now.

This is the screen of output that I could see... there was a ton more about IDE and HDA that I saw but it went so fast I couldn't read any of it. Here is what I could read when the readout was done:

ide failed opcode was: unknown
end_request: I/O Error, dev hda, sector 65415
JBD: Failed to read block at offset 7216
JBD: Recovery failed
Ext3-fs: error loading journal
Mount: Mounting /dev/hda1 on /root failed: Invalid argument
Begin running /scripts/local-bottom ...
Done.
Deon.
Begin Running /scripts/init-bottom ...
Mount: Mounting /root/dev on /dev/.static/dev failed: no such file or directory
Mount: /proc on /root/proc failed: No such file or directory
Target filesystem doesn't have /sbin/init.
No init found try passing INIT= bootarg

Busy Box v 1.14 (Debian 1:1.1.3-5)....

UPDATE: forgot to add that instead of using extX I've decided to use ReiserFS instead because I've always wanted to and I was curious if it would make a difference.