This is a weird situation: I was playing a movie in Gnome's default player, often advancing with the seekbar. As I once pulled the seekbar quite far, the display suddenly went off and the computer seemed quite busy for a few minutes--and there was still no display. I tried the keyboard, even the Reset button--to restart the PC, but they didn't work. I had to turn off the switch on the switch board (now I regret for not waiting a few more minutes before doing that).

I powered on the PC after a while but nothing happened except for the power led getting on and the DVD-ROM led blinking several times. There was no display and nothing else.

However, later it was found that the power supply had some problems. So, I changed it and everything came back to life.

Except, during the verbose booting log I got this error:
I didn't understand what to do for the maintenance.

Did you try running "e2fsck -b 8193 /dev/sda9" as it instructed?

Basically, your filesystem has become corrupted because it was not cleanly unmounted when the system was forcibly shutdown. You need to attempt file recovery to get the partition back into working order, if for nothing else than to recover as much files from it as possible.

Yeah, last night I tried e2fsck -b 8193 /dev/sda9 but it did return the same as
I understand that it became corrupted. But how can I recover the partition or its files? Is there an easy, effective way? I'm googling for ways, but any suggestions from you guys?

I'm not exactly sure which mal-setting of hardware caused this problem. I changed a few of them in these few days while running Windows XP all the time with a broken heart and making preparations for a reinstall of Debian--I installed R-Linux on my XP and recovered over 1GB files from my Debian Home dir.

Apparently, while changing the power supply the technician made those wrong settings: the most important one which I suspect prevented Debian from loading was the guy connected the harddisk to wrong SATA port (XP loaded fine, though). Also the SATA DVD-RAM was not connected at all.

Fixing those, I was still on XP. This morning I booted into Debian just out of curiosity...

And voila! Lenny is there! Everything is the same they were!

I write this post because there have been many visitors to this thread but there wasn't any solution. I thought no one has ever experienced this. But I know a few must have been thinking about it. So, this is to let evryone know that it had to be the hardware thing.

Thanks everyone!

My guess would be the Technician restored the Default BIOS settings.

Changing something as simple as LBA access to the drive in BIOS could confuse the system when it tries to access the drive.

Well, I don't think so, because I didn't have to change any settings in the BIOS.

While connecting the DVD-RAM I noticed that the bootable hard disk was connected to the slave SATA port. As I said, XP booted without any problems though. I have another hard drive--an IDE one--installed as secondary slave. The secondary master is a DVD-ROM. I just connected the bootable HDD as primary master and the DVD-RAM as slave. And I can log on to Debian again!

I said I'm not sure if what I did really solved the issue.

Anyways, thanks for yor reply, farslayer.

Mistyped. Please ignore.

I must have misread.. I thought you said after changing BIOS settings it started working again.. Wow was that ever off.. It's been a long day and I'm just looking forward to getting out of work and hitting the road to the Ohio Linuxfest.

Come on clock T minus 43 minutes and counting