Issues with your account? Bug us in the Discord!
drat...HDD total failure...
A2597
Fanboy
in Zocalo v2.0
Well...this stinks. Total HDD crash. not just a wipe, a hardware failure. drive unusable.
to make matters worse, I haven't backed up in about 70 days. So sorry Striker, you're going to have to wait a little longer on that project...
aside from that, nothing really major lost. Few papers, lots of e-mails, about a gig of blender files, and of course my GUI I made.
drat...cost $150 to get a new HD as well...only one store sells them, and the prices went like this.
60 gig - $109
80 gig - $160
120gig- $200
200gig- $250 with $100 instant rebate.
gee, hard choice.
soo...now I'm trying to figure out why windows reads it as a 190gig HD (Expected, the 1000 / 1024 megabytes to a gig thing), but shows 125 gigs free in windows...65 gig's of NTSF file tables?!?
to make matters worse, I haven't backed up in about 70 days. So sorry Striker, you're going to have to wait a little longer on that project...
aside from that, nothing really major lost. Few papers, lots of e-mails, about a gig of blender files, and of course my GUI I made.
drat...cost $150 to get a new HD as well...only one store sells them, and the prices went like this.
60 gig - $109
80 gig - $160
120gig- $200
200gig- $250 with $100 instant rebate.
gee, hard choice.
soo...now I'm trying to figure out why windows reads it as a 190gig HD (Expected, the 1000 / 1024 megabytes to a gig thing), but shows 125 gigs free in windows...65 gig's of NTSF file tables?!?
Comments
When using a drive over about 40GB you should really partition it into multiple partitions. Keeping it as one big partition is pretty silly. This makes things generally more efficient, plus it makes it easier for you to organise your data.
(well, my drive didn't crash, windows just decided to recycle some folders)
So what's the brand of "winner"?
BTW, New Hitachi's have nice "feature":
[url]http://7k250.euweb.cz/[/url]
Usually it's because either their MoBo needs some flashing or the most common problem, windows doesn't support it. No sweat though, all the major brands have tools on their webbys for this.
[URL=https://maxtor.custhelp.com/cgi-bin/maxtor.cfg/php/enduser/olh_adp.php?p_faqid=960&&p_sid=iYDPnf6h&p_lva=]Maxtor's Big Drive Enabler[/URL]
[URL=http://www.seagate.com/support/disc/utils.html]Seagate's Tools (I think you can choose DiscWizard or Reg48bitLBA for your problems)[/URL]
[URL=http://wdc.custhelp.com/cgi-bin/wdc.cfg/php/enduser/std_adp.php?p_faqid=950&p_created=1049994313&p_sid=hQ69Om6h&p_lva=&p_sp=cF9zcmNoPTEmcF9zb3J0X2J5PWRmbHQmcF9ncmlkc29ydD0mcF9yb3dfY250PTExNSZwX3NlYXJjaF90ZXh0PWRyaXZlIGNhcGFjaXR5JnBfc2VhcmNoX3R5cGU9c2VhcmNoX2ZubCZwX3Byb2RfbHZsMT05MSZwX3Byb2RfbHZsMj05MyZwX2NhdF9sdmwxPSZwX3BhZ2U9MQ**&p_li=]Western Digital's Tools, choose from the list[/URL]
Good luck :D
This 190 GB is right because HD makers use 1000 as coefficient instead of 1024.
With big drives difference comes pretty big.
(compare 1 000 000 000 to 1024x1024x1024 and you'll get error per GB)
[B]When booting up, my RAID card shows my 160 GIG Maxtor (Gives a list of all hard drives attatched and their sizes) as a 159,*** MB Drive (I guess about the equivolent to 160 Gigs, it's close enough) Yet in Windows, it shows up being a 152 Gig. Nothing TOO major to me, but it's the priciple of the matter. [/B][/QUOTE]
The actual size of the drive is 163 921 571 840 bytes. If you dived it 3 times with 1000 you get about 160GB which is what (as earlier said) used by the HD makers. If you use 1024 which is what actually should be used you get about 152GB.
I don't know why your raid card shows it as a 159,***MB
163 921 571 840 / 1000 / 1000 / 1000 = 163.921...
163 921 571 840 / 1024 / 1024 / 1024 = 152.663...
[B]That 125 GB is because windows need update. (or registry fix)[/b][/quote]
[b]WRONG![/b] It shows up as 125GB because its a limitation in his BIOS. He needs to flash it to the latest version, assuming his mobo's manufacturer (MSI) even bothered releasing a fix allowing drives larger than 120GB to be used.
[quote][b]This 190 GB is right because HD makers use 1000 as coefficient instead of 1024.
With big drives difference comes pretty big.
(compare 1 000 000 000 to 1024x1024x1024 and you'll get error per GB) [/B][/QUOTE]
No, its wrong. It should be LARGER than the box specification (204800kB). Now in WINDOWS it would be about 190GB due to cluster size, depending on what file system he chose (anything other than NTFS for NT/2000/XP is just plain STUPID from a security standpoint let alone stability.)
BIOS idetects it as the 200gig HD, it's a windows only thing.
the update will fix it. I just need to download all 134 megs of it...
[B]When using a drive over about 40GB you should really partition it into multiple partitions. Keeping it as one big partition is pretty silly. This makes things generally more efficient, plus it makes it easier for you to organise your data. [/B][/QUOTE]
Thats not really true anymore, the only reason to partition a large drive now is so that you don't lose your crap on it, With the cluster size of NTFS and Fat32 you don't lose the space that you used to with Fat16.
the amount of wasted slackspace with NTFS is negligible,
[B]The actual size of the drive is 163 921 571 840 bytes. If you dived it 3 times with 1000 you get about 160GB which is what (as earlier said) used by the HD makers. If you use 1024 which is what actually should be used you get about 152GB.
I don't know why your raid card shows it as a 159,***MB
163 921 571 840 / 1000 / 1000 / 1000 = 163.921...
163 921 571 840 / 1024 / 1024 / 1024 = 152.663... [/B][/QUOTE]
And the kicker is that sometime, for unexplained reasons, and only once every three Blue Moons, it shows it being the 163 Gigs. Very, very wierd, but so long as it holds data at around the 160 and doesn't DIE, I'll be happy.
[B]And the kicker is that sometime, for unexplained reasons, and only once every three Blue Moons, it shows it being the 163 Gigs. Very, very wierd, but so long as it holds data at around the 160 and doesn't DIE, I'll be happy. [/B][/QUOTE]
It does really sound to me like a bios issue, OR perhaps a bad harddrive controller, Granted, i'm too poor to buy anything over a 120 right now, but since my 120 gig mp3 drive is now full, im' thinking its time for a 250 gig drive...
[B]It does really sound to me like a bios issue, OR perhaps a bad harddrive controller, Granted, i'm too poor to buy anything over a 120 right now, but since my 120 gig mp3 drive is now full, im' thinking its time for a 250 gig drive... [/B][/QUOTE]
That's what I was thinking as well. Again: So long as it work, I'm happy, y'know?
HD Size: 189 GB
Freespace: 123 (@ 2 gigs of installed stuff so far)
WHAT GIVES?!?
This is my mobo BTW...if that matters...it's only two years old.
[url]http://www.msicomputer.com/product/detail_spec/product_detail.asp?model=KT3_Ultra[/url]
[B]ok, SP1 installed, Maxtor bigdrive patch installed...
HD Size: 189 GB
Freespace: 123 (@ 2 gigs of installed stuff so far)
WHAT GIVES?!?
This is my mobo BTW...if that matters...it's only two years old.
[url]http://www.msicomputer.com/product/detail_spec/product_detail.asp?model=KT3_Ultra[/url] [/B][/QUOTE]
Problem #1, its MSI, they are the Yugo of the motherboard world, I wouldn't use an MSI board if you PAID me. The are total crap (imho)
My advice, ditch it and pick up an Asus or an Abit.
#2, like has been said before, go to msi's website and make sure you have the latest Bios. a lot can happen in 2 years if you have not updated the bios.
I fyou decide to give it a try, be sure to read up on how to do it etc.
Suggest you read the
[URL=http://www.msi.com.tw/program/support/bios/bos/spt_bos_list.php?kind=1&CHIP=Archives&ID=4]"To update the BIOS, please do the following"[/URL]
Here is your BIOS upgrades
[URL=http://www.msi.com.tw/program/support/bios/bos/spt_bos_detail.php?UID=11&kind=1]BIOS upgrades for KT3 Ultra[/URL]
the big HD patch and SP1 only work for hard drives you have NOT installed yet....not on the already installed and formatted disc! Yea...way to go Macroshit!
anyhoo, problem solved by re-formatting (Don't worry, I backed up the 300 megs of stuff I've done over the past two days) as a 80gig and 120gig HD....
I now have 189gigs of space! :)
thanks for your help guys!
[B]the big HD patch and SP1 only work for hard drives you have NOT installed yet....not on the already installed and formatted disc! Yea...way to go Macroshit![/B][/QUOTE]
That's because of what we like to call a "partition table", among other things. Basically, you formatted with an OS that could only handle 120GB in a single file system so the file system was created with that much. That's just how file systems work, you can't really blame anyone for the fact that just because you patch it it automatically resizes all your partitions or something. That would be plain stupid. You could have also got it up to full capacity by using something like partition magic and resizing the partition that way.
partition magic also saw that space as "used" and ergo, unmodifiable.
[B]wrong.
partition magic also saw that space as "used" and ergo, unmodifiable. [/B][/QUOTE]
Thats pretty odd, since Partition Magic doesn't care if it's usable or not under normal circumstances,
[B]Perhaps it's an older version of PM? [/B][/QUOTE]
I would think so.
Well, only thing that comes to my mind is that what's said in finnish as "VIAllinen". (meaning faulty in english)
[url]http://www.viaarena.com/?PageID=2[/url]
Have you tried these drivers?
It's odd that PM8 wouldn't resize the partition. Were you running it in windows or from the rescue discs? If it was running in windows it might have been taking windows' word for info on the harddrive, whereas the sensible thing to do would be to use the BIOS.
[B]well...problem solved.
the big HD patch and SP1 only work for hard drives you have NOT installed yet....not on the already installed and formatted disc! Yea...way to go Macroshit!
anyhoo, problem solved by re-formatting (Don't worry, I backed up the 300 megs of stuff I've done over the past two days) as a 80gig and 120gig HD....
I now have 189gigs of space! :)
thanks for your help guys! [/B][/QUOTE]
Oh? I've been able to use the full capacity of >128GB Drives after a format and patch. It takes a little bit of tinkering, but only a little, and nothing even that complex
[B]well...problem solved.
the big HD patch and SP1 only work for hard drives you have NOT installed yet....not on the already installed and formatted disc! Yea...way to go Macroshit!
anyhoo, problem solved by re-formatting (Don't worry, I backed up the 300 megs of stuff I've done over the past two days) as a 80gig and 120gig HD....
I now have 189gigs of space! :)
thanks for your help guys! [/B][/QUOTE]
Told ya MaxBlast would work. :)
[B]If it was running in windows it might have been taking windows' word for info on the harddrive, whereas the sensible thing to do would be to use the BIOS.[/B][/QUOTE]
Yeah, it should have that tool for making disks whit DOS version of PM8.
I was able to repartition and format one HD wich had two NTFS partitions and somehow normal F-disk didn't want to create new partitions, or even delete old partitions.