HDD problem

Last night I installed msn onto this PC (which I've had for nearly a month now) and it wouldn't work, so I gave up with it. Played a few 3v3's afterwards, and near the end of the last one my PC rebooted (blue flash on the screen and then some multicoloured specs for half a second before reboot [not actual "BlueScreen"]).

I went back on ET and finished the game and went to bed. When I got back home today and went on my PC I instantly uninstalled msn as I saw it and went on ET to go to u|k serv, when I got kicked by some PB problem - said something like "couldnt load PnkBstrB.exe" aswell as "server handshake failed" at the bottom (no clue what that meant). I tried reconnecting and I was kicked again with the same reason.

I rebooted and opened ET, it said there was no such program as "Enemy Territory" so I went to My Computer to try to access the Local Disk (Z:) Drive and it came up with: "The disk in drive Z is not formatted; do you want to format it now ?"

I already formatted it a when I first got this PC (a few weeks ago) and I have alot of fles on it, not important things, just demos etc (which I don't mind losing) but I would very much rather it being fixed tbh, instead of formatting it.

Thanks if you try to help ;)

EDIT: It's a Samsung Spinpoint 1tb if that helps.
Comments
9
lol you didnt handshake pb?!
epic fail !
always handshake the boss !

btw, im sure a forum thread will help more
+
different forum xD

crossfire isnt well known for serious :~<

good night :~D
So have you formatted it?
delete all files on c/programs/wolfensteinet...
reinstall et + newest patch

dont forget the pb update :>
Had exactly the same problem with my hdd few days ago...
Wanted to defrag and due a storm my pc turned off... after i turned it back on, chkdsk started (and thats what fucked up all my files) and the disk appeared as 'not formatted'...

However...you can try some tools (google ftw) to repair the mbr (master boot record) but the chance to get back your stuff is pretty low...
checkdisk doesn't fuck up files it fixes them. It's more likely to be corrupted filesystem table than MBR's partition table. In case of MBR it's easier to fix stuff.
And yeah, defragmenting (!) during a storm is the greatest idea ever, lol. Actually in your case it had to be corrupted filesystem too, since partition table isn't edited during defragmentation afaik.
Parent
When i rebooted the comp, checkdisk started before the login-window and just AFTER that my files began to fuck up... chkdsk moved them to found.000-folder.

After like 2-3 reboots on the next day my whole stuff was spreaded over like 1300 subfolders in the found.000-folder...

I don't know and i don't care what exactly was fucked up there... mbr, filesystem, whatever... in fact i lost all my files because chkdsk 'fixed' them...

And btw... i wasnt at home and since it was a sunny day i didnt though about rain, storm and shit... so dont blame me for that :D:D
Parent
well ofc when you do defragmentation and interrupt you get damaged MFT and that's why checkdisk tries to identify where are your real files, since there can be thousands of files that link to the same data in the MFT table. And if there is thousands pieces of the same data that are linked by thousands of other nodes then you are probably fucked up. Moral: don't do defragmentation it always does more harm.
Parent
Back to top