Thread: [Solved] BunBun Down!

Originally Posted by WileECyte

Hopefully there's a BIOS upgrade.

there was one, released back in 07 (latest bios), which i updated a while back during the xp sp3 mayhem.

jesus i cannot get a break. Its not the install cd. Getting:

"The file or directory C:\ is corrupt and unreadable. Please run the chkdsk utility" at the Windows 7 Install CD menu. IE at that point in time there cannot possibly be any fucking C drive! What on earth? Of course googling only reveals situations with people who have bad hdd's but that's not the case here. Im getting the error message the second i hit the first button at the windows 7 install screen! (select lanaguage, keyboard, hit install windows pops up a EULA, thats where i get the error message).

w
t
f

Yikes. What chipset is your motherboard, Bunni? I've had problems installing Windows XP on SATA drives before, but that was remedied by slipstreaming the drivers into the OS CD.

Bunni, Some boards (I know mine has it) have the ability to change the mode of your SATA controllers I think some have a 'legacy' mode that fakes being an IDE controller. I did this until I got the OS installed and that seemed to work.

Originally Posted by WileECyte

Yikes. What chipset is your motherboard, Bunni? I've had problems installing Windows XP on SATA drives before, but that was remedied by slipstreaming the drivers into the OS CD.

Originally Posted by WileECyte

Bunni, Some boards (I know mine has it) have the ability to change the mode of your SATA controllers I think some have a 'legacy' mode that fakes being an IDE controller. I did this until I got the OS installed and that seemed to work.

Originally Posted by JimboIncinerator

If you dont already, do a md5 checksum on the win7 download from msn to ensure no corruption.

Oh i did, it wasnt the cd though. I downloaded DIRECTLY off of msdn's site, tried downloading 64bit twice, burned onto shiny ass new dvd's, verified the burns. Both of those got the message, in addition to the 32bit i had lying around.

---

Ok i seem to have located and solved the problem. One of the hdd's in my raid went bad, well, that's not quite right, more so: "something happened to it, that caused the partition table to go wack". This drive, it so happens, was the drive that played host to what correlated to my C:\ drive (NOT OS PARTITION!, OS's Were E:, H:/L: (depending on what os i was in)). This C:\ partition (along with the D:\ partition that was on the same drive) went hay wire screwy.

Thats what caused all my problems. Id wager a LARGE sum of money that the os installs where perfectly fine. This C:\ drive did have a windows sig on it, which is likely what caused it to be partially detected as a windows install and cause complete chaos. This drive, however, also played host to my mbr (which was perfectly fine).


This bad C:\ partition is what caused that error message in windows 7 install, and ironically the fix for it was to just ignore the message. My problem booting though, was solved by shoving the raid array down on the hdd boot priority list. For some reason, I CAN boot from a raid array fine, just booting from a mbr on raid array which references a drive off the raid caused the boot problem, in addition to the bad partition table on the raid drive.



Ironically i am not as aggravated as you would think, i do have w7 64bit installed, up and running and i must say its running quite fast (or at least much faster than my xp install was (which was lightning fast), (the vista install was laughable sloooooowwwww)). Now this is probably not the os, but rather the new (well used, new) cpu i got (upgraded from a 939 1 core to a 939 2 core). I just never got the chance (because of this mayhem) to test the new cpu out on xp.


I am not quite sure what caused the one drive to go wacky. I easily recovered the D partition on the disk, but the C:\ drive is causing me problems. This partition however was used as a overflow fill so, obviously its contents are nothing more than temporary files, of which i couldnt care less about lol.


All in all, this is just another reason i hate windows. I would love them ever so much more (or at least not hate them as much) if they would just provide decent error messages. Or at the very least, stack traces...