Tom's Guide | Tom's Hardware | Tom's Games
 |
 |
 |
i am running an abit kg7-RAID with operating system and programs on the raid-0 setup. i have two additional harddrives that i need to format and span them for data storage. i try to use partition magic 7 but when it begins to load i get this error: (( Init Failed: Error 100 ; Partition table is bad. )) I can't seem to get the fdisk utility to work either(although not specified for NT of XP).. please help.
I have exactly the same problem as you..any fix? I'm just glad to hear it isn't my partition table on my RAID gone bad...
JKP
0 
Forgot to mention -
ABIT KT7a-raid (latest bios).
Running a storage RAID on two IBM Deskstars (30GB)It must be a mobo\HPT360 prob....
let me know when someone knows a fix...
0
Got the same problem, error 100 partition table bad... 10 gig, 20gig as IDE Masters, and 2 20 gig set up as Raid 0 striped. Program hust won't run... appreciate any ideas..
J
0
Thank god for that, i was pulling my hair out. Dual booting 2k/xp on kt7a - raid.
two 45gig DTLA's on Raid 0.
PM7 works fine on 2k and shows no errors
but load up on xp pro and it gives you a big f**k you.
init failed error 100 partition table bad.just been looking for hours to try and find a problem that apparently isn't even there.
Well done powerquest, great product when it works but the site stinks for further information. ok got that off my chest.
Any ideas anyone has will be much appreciated.
0
Im having the same problem.
WindowsXP
KT7-RAID
2 x 30 gig western digital (7200 rpm)
Partition magic 7.0The problem from what i have gathered from the powerquest database is that it is trying to read a removeable disk, IE your CDROM or other removable IDE drive. (this i havent found any truth to)
what ive noted my self is PM7 reads both drives (or more) on the RAID seperately and it should not, one is the boot master and the other is "hidden" from the system. PM7 is trying to read each drive individualy when it should be reading it as one drive.
this is why the partition table is bad, because with reading one of the drives buy its self it IS bad because it takes both drives to make up the correct partition.
There should be a utility in the partition package that is SUPPOSED to correct this, i cannot get it to help. There is a explaniation on how it is supposed to help on the powerquest web site, if anyone has any luck with this please respond.
(BTW: anyone who can run PM7 from win98 which dual boots with XP, why dont you run it from win98? just wondered if there was a issue w/ that.)
0
I finnaly figured this one out just last night.
The problem is as i previously noted and heres the very simply fix:
If you go in to device manager in windows XP, you'll notice that it list both (or more) of the hard drives on your raid controller. Now only one of these drives is "visable" to the system, its the one that is the boot disk. One of the drives will show up in the DM with the storage capacity and sectors and such of the RAID array (the boot device), the other hard drive will show up with nothing.All you need to do is in the device manager with the "blank" drive select "disable device". That should put a nice fat red "X" through the icon for the device.
Now just run partition magic and have fun! it will only scan the boot device and read it as the RAID array.
Surprisingly this works w/o any problems, heck even on the PowerQuest web site they claim you cannot partition a "striped" device using PM in windows XP. We now know they are wrong.
Good luck!
(now if i could only get linux to recognize my HTP370 RAID controller! any tips welcome)
0
Can anyone else confirm that this works?
I have a kt7-raid with 2x30gig as raid-0 and 1x30 gig on IDE1. OS is on raid and spare hdd is storage.
Now I didn't always have this prob and it comes and goes.
Anyone have an explaination as to how that could be? (the coming and going of the prob)
0
I have a solution!!!
This really only works for kt7-raid users.I had the RAID bios version 2.0.2019 and my 2x30gig hdd's would show up in device manager as 2 seperate hdd's and not one as it should. Now I upgraded to RAID bios 2.31 and installed the 2.31 drivers (had the default MS ones before) and now device manager sees it as one drive not 2.
Now I load up pm7 and no error :)
Now I'm not sure if it was the 2.31 BIOS or 2.31 driver that fixed it but its best to match the bios and driver versions.
Now some of you may know the latested official kt7-raid bios only comes with RAID bios 2.0.2019 or something liike that. What you need to do is grab the bios on this site http://www.viahardware.com/faq/kt7/faqdownloads.html#BIOS%20releases
The owner of that site has merger the 2.31 bios (which is an official version) into the latest kt7-raid bios.
So go grab the modified bios and the 2.31 driver. Flash the bios first then install the driver when you reboot.
Hope this helps :)
0  |
 |
 |
This post is quite old and has been locked from receiving new replies. Please create a new posting instead.
| Ads by Google |
