Partition Magic Error #100

[mrmomaz]

Dual boot with BiNG
Win XP/SP2
3 HDDs

I've lost a HDD. I cannot see the drive in either Windows Explorer, Partition Magic or BiNG. PM give me a error 100 = bad parition table, and recommended back up of effected partitions, delete them and restoring. I cannot see the drive, so doing a back up is out of the question. (PM only presented this #100 error the first time I started PM after the reboot and subsequent lost of HDD.) I've run Norton AV (Both OS partitions, D: and K: ) and found no errors.

I only received the error #100 the first time I ran PM. No errors popped up when it was started as with the 100 error.

Is the PM error referring to drive C: or the drive that is not shown??????

When I boot, Windows does a scandisk of partitions D (only data) and K (only downloads) which both come up clean. (Different HDDs.) I don't k now why it picks those partitions.

Back ground:
the system would reboot whever I deleted a file on the HDD in question,
most of the partitions on the lost HDD had MOUNTED drive assignments instead of being assigned drive letters,
I found one partition that had both a drive letter and a mounted drive assignement and wondered if this was the cause of the reboot, so I removed (Diskmgmt) all the the assignements on the now lost HDD, rebooted and have not seen the drive since.


Suggestions?

[Paul Komski]

First check that all three drives are seen in the BIOS setup. If so then run partinfo (http://www.terabyteunlimited.com/utilities.html) and post the results back here.

[mrmomaz]

one of the drives is an external USB/firewire drive, but i see the the 2 internal drives in BIOS. I also see the miissing drive in the partinfo information. The missing drive is the first drive.
thanks for the post.

[mrmomaz]

after reading my post above "one of the drives is an external USB/firewire drive," I changed the connection from firewire to USB and I got all the partitions back! So I must have a bad firewire <?>? The firewire and USP ports that I am using are on the same card.

However, anytime I delete a file, the system reboots! I had this problem when the drive was connected Firewire too. This happens on the HDD in question as well as my other drives.

So:
what part of the firewire do i look at? where do I begin looking for a system that reboot on deletion?

thanks for any suggestions.

[mrmomaz]

"This happens on the HDD in question as well as my other drives."

i now seem to be able to deleete from my internal drives ok. deletion from external = reboot.

[mjc]

How are the external drives (USB or Firewire) powered? Are the drawing the power from the USB port or do they have their own power supplies?

Does it happen with a memory stick, too or is the problem just limited to actual hard drives?

I think you may have power problem with the USB/Firewire card...and if there is, then 'flaky' drive reading is a definite...if the drives aren't being read/seen by the USB card properly that is going to be more important to straighten out before you try to tackle the partition problem.

[mrmomaz]

How are the external drives (USB or Firewire) powered? The external drive has it's own power supply

Does it happen with a memory stick, too or is the problem just limited to actual hard drives? memory stick works fine. Internal drive seem to be the problem AND it is only a problem when I delete older files. (If I created a file, then I can turn right around and delete it with no reboot - but if I delete a file from last month , the I reboot)

I think you may have power problem with the USB/Firewire card...QUOTE] Power has crossed my mind, but didn';t know how good the idea was :) :) I will unplug the power from drives that I can do without for awhile and see if that helps the power problem.

Are we talking TOTAL power output or power to the USB/FIREWIRE card? I will change the USB to a different ouutlet (back of case on motherboard instead of front on a card)

[mrmomaz]

When I get this deletion reboot, I get stop error <blue screen> (0x0011012f,0x0->703,0-0,0-0) i have not been able to find an english translation of this error. Ideas?

[mrmomaz]

I get stop error <blue screen> (0x0011012f,0x0->703,0-0,0-
this should have read more properly as I get stop error <0x023> (0x0011012f,0x0->703,0-0,0)

Sorry for leaving out the most important piece of information.

It is intermittant in that I can delete some files, but if I hit the right ones, then its blue scrren of death for me. CHKDSK /f did not find errors. I'm doing CHKDSK /r now but not finding errorss.

[Paul Komski]

I had missed returning to this thread for some reason and have only just read the partinfo file.

The 4gig (Drive 3) has had a BootItNG Partition Manager as indicated by Partition Type DF. This creates atypical partition tables and shouldn't be mixed with other boot managers or indeed anything else, such as fdisk /mbr that writes to the MBR. Since the partition tables are atypical they shouldnt be accessed from other sources - only by using BiNG.

The 280gig (Drive 4) appears to be using another boot manager (XOSL) on the first FAT32 partition table as well as another BootItNG (typeDF) on the fourth partition table. In between them are one NTFS and an extended partition containing 10 logical partitions.

The 76gig(Drive 5) is the only drive with a partition marked as Active (though that is immaterial if you are using a boot manager). This is an NTFS partition followed by some unallocated space - then an extended partition containing a number of logicals and finally a primary "large" FAT16 that you have called "FOR BING" and which has not been designated a drive letter.

It is not clear which is the external drive but regardless of that you appear to be mixing boot managers and more importantly using BiNG atypical partition managment, which can use more than the normal four primary partition tables. It's hard to make sense of all of this unless we know which of the three drives is set as the boot device in the BIOS setup and whether you are using a normal boot process or a 3rd Party boot manager from that hard drive.

Partition Magic is giving you errors whether or not there are "errors" if there is BiNG software in situ - since it is atypical and therefore likely to be non-sensical to PM. It is wise to either use one or another Partition Manager and not to mix them.

BiNG (and PM) can also be put out by having an external drive attached particularly with BiNG if this is a USB2 drive and USB2 has not been enabled in the BiNG settings.

Suggest that you remove the external. Then decide which drive you are booting to via the BIOS and then boot to a BiNG floppy or CD and see what it then sees and whether it prompts you to reactivate it or any other messages.

The STOP errors may or may not be related but are a different problem, which we can return to when we get your missing drive on line.

[mrmomaz]

Don't worry about the delay, Paul; I'm sure you're busy and this is a real can of worms here.

This post is out of sequence with the above thread/posts but it is fresh in my mind and possibly more important that the BSOD above. Maybe this should be a different thread in which case feel free to move it. I put it here because I think I need to solve all of the problems in this thread. I need to sort out the answers to your above questions which I will do ASAP. ANYWAY:

The 280/300 gig drive is the external USB/Firewire drive. It also seems to be the drive that causes the most stop errors (oxo23. ox19). The big picture: is when I was just rebooting after a stop error, it occured to me to take this drive offline and turned it off during the boot process (stupid, but I did it.) Then I saw ? lines of 'folder entry removed' roll by at which time I turned it back on. This stopped the 'folder entrty removed' lines <or maybe it finished with the drive> at which time I was queried to convert the <?> to files at which time I tried to enter 'N" (dumb again) but the screen said 'YES' so I don't know what CHKDSK? accepted. I only know that the PC locked up which is when I came here for help. Without touching the PC it started to reboot and I immediately turned it off <off button>. NOW:


do I have a chance of getting those files back?
If I turn that drive off before I next boot, will those files remain as they are until I turn the drive on again, when I'm ready to attempt recovery (or accept their loss)?
I don't know what to ask, so I'll make the post and field questions.
(The files are important, but not worth paying for data recovery. I do have many of them backed up-it's not knowing what is missing.) thanks for any help
WIN XP/SP2

[Paul Komski]

Remove the external and boot to a BiNG CD or floppy and see if you can reactivate BiNG installed onto the MBR/EMBR. If that works take out the CD or floppy and see if you can boot to the Boot Manager on the hard drive. It that succeeds see what partitions it can display for you.

Always avoid running chkdsk when data recovery is the main concern - unless there is a very specific reason for doing so.

If I turn that drive off before I next boot, will those files remain as they are until I turn the drive on again, when I'm ready to attempt recovery (or accept their loss)?Yes. The only way that the files would be affected is if anything is written to the drive (including chkdsk "fixing" errors) or the development of bad sectors on a failing drive.

[mrmomaz]

The External drive only had data on it, even tho a BiNG partition was present. (It would come up as the first or last drive depending on if it was USB or Firewire and BOOTNO worked better this way.. It has never been a boot drive.)

So, As expected, i turned the eterrnal drive off, turned the system on and BiNG showed me all my drives -except for the ext that I had turned off. (No nneed to floppy etc.) Continued the boot and the boot finished normal. (The external HDD and the Stop errors are the problems.)

I ran chkdsk on all of my drives last night with no errors and that is the only time that i have run CHKDSK. It runs automatically after a STOP error. HOW do 'i m;ake/get it to not run. That is how I got caught wiht the 'folder remoded' errors. it delayed before it tran and i wwaas not expecting it.

ok, i'll leave the ext HDD off and answer your above questions so maybe a solution to the stop codes can be found. AAnd then work on the EXT HDD files.

I see that this is now a thrread by itself. I didn't really know where to pout it.
thaks

[mrmomaz]

Lets make sure I understand how Bing should be set up:

I am using BiNG (only) as my boot manager.
I think therefore that each HDD should have a MBR and that it does not get a drive letter.
It was under this assumption that I set the drives up. If I'm wrong, thenlet me have the good news so I can correct it.
As things are, I am able to dual boot to either "Norton" on the 76gig drive OR to "COX" on the 280 gig drive.
I have formatted the XOSL partition and left it as a primary partition so as to not change Boot.ini.

[quote]The 4gig (Drive 3) has had a BootItNG Partition Manager as indicated by Partition Type DF. This creates atypical partition tables and shouldn't be mixed with other boot managers or indeed anything else, such as fdisk /mbr that writes to the MBR. Since the partition tables are atypical they shouldnt be accessed from other sources - only by using BiNG.I don't think I understand the bolded sentence. This is also onlly a data fsrive. It actually is a RACK drive.

The 280gig (Drive 4) appears to be using another boot manager (XOSL) on the first FAT32 partition table as well as another BootItNG (typeDF) on the fourth partition table. I tried XOSL and then went back to BiNG and did not complete my housekeeping. The XOSL parittion has been formatted but not assigned a drive letter.


The 76gig(Drive 5) is the only drive with a partition marked as Active (though that is immaterial if you are using a boot manager). This is an NTFS partition followed by some unallocated space - then an extended partition containing a number of logicals and finally a primary "large" FAT16 that you have called "FOR BING" and which has not been designated a drive letter.This is my main boot drive and therefore marked as active. I don't see any quesxtions in this paragraph?

It is not clear which is the external drive but regardless of that you appear to be mixing boot managers and more importantly using BiNG atypical partition managment, which can use more than the normal four primary partition tables. It's hard to make sense of all of this unless we know which of the three drives is set as the boot device in the BIOS setup and whether you are using a normal boot process or a 3rd Party boot manager from that hard drive.I t hink I have limited all my drives to no more than 4 primary partitions to conform to BiNG and I now have removed XOSL. Knowing that the BIOS boots to the 76gig drive, is there anything I need to do with this paragraph?

Partition Magic is giving you errors whether or not there are "errors" if there is BiNG software in situ - since it is atypical and therefore likely to be non-sensical to PM.I have stopped using PM.

BiNG (and PM) can also be put out by having an external drive attached particularly with BiNG if this is a USB2 drive and USB2 has not been enabled in the BiNG settings.By USB2 are you refering to USB 2.0? I have NOT checked either USB 2.0 support for IEEE1394 Support because I never intend to have the USB/fireware drive as a bootable drive. OK?

Suggest that you remove the external. with the external drive unpluged/off, i am able to boot to either the NORTON or the COX partition as usual.
Are we ready for the stop errors.

I don't know if you want it, but here is another partinfo snapshot.--OPPS I must have had XOSL on each HDD and I only removed one. Partinfo to follow tomorrow after I get rid of the other two.
thaks for the help!

"The STOP errors may or may not be related but are a different problem, which we can return to when we get your missing drive on line."
__________________

[Paul Komski]

I'm still rather confused as to which drive is which. You say that "The 280/300 gig drive is the external USB/Firewire drive" and also say that "As things are, I am able to dual boot to either "Norton" on the 76gig drive OR to "COX" on the 280 gig drive". Unless you have been able to boot to an external drive then just I don't follow this.

Also when you say that "The missing drive is the first drive" it would be helpful if you could say which actually is the first drive by reference to its size. Let's just call them the 4G, 76G and 280G from now on. The first drive, for example, in the partinfo log is called Drive3 and is the 4G. The 280G and the 76G appear in it as Drive4 and Drive5 respectively. This on its own is odd since there is no mention of Drives 1 and 2, which implies some difficulty in the system communicating with the BIOS.

Have got to have a good grip on all the drive geometry to be of any real help. In particular which is the external drive - though if you do post another partinfo log (with no external attached) then that should become clear. Need to know which drive you meant by the "first drive" and also which drive is the external.

FYI there is a setting in the BiNG settings for enabling USB2. If the system has difficulty recognising a USB drive then this should be tried both enabled and disabled. It doesn't matter which drive is the boot drive since BiNG is seeing it before the system boots.

[mrmomaz]

"I'm still rather confused as to which drive is which" Me too, when I get in a hurry. Lets try this:

4G = my financial information and is a removable 'rack' drive,
76G = primary drive that I boot to ("NORTON"). BIOS has this as boot drive. (SATA drive)
280G = alternate drive that I boot to. ("COX"). Also contains XOSL which I don't know how to get rid of. Format and renamed and still XOSL in partition listing???
55G = Win98SE that I used to be able to boot to. Used as data storage.
200G = External drive that is in trouble. USB/Firewire connectonable. power and data are disconnected. Has it's own external power source.
ZIP drive = 100G ZIP and is first drive listed in DISKMGMT.MSC.
The ZIP and the Rack are the drives that are not mentioned.

"... there is no mention of Drives 1 and 2, which implies some difficulty in the system communicating with the BIOS." 1 and 2 are the zip and rack.

FYI: The unidentified paritions on the 280G are BiNG images.

"FYI there is a setting in the BiNG settings for enabling USB2. If the system has difficulty recognising a USB drive then this should be tried both enabled and disabled. It doesn't matter which drive is the boot drive since BiNG is seeing it before the system boots." I understand the USB setting in BiNG allows BiNG to use a USB drive as a boot drive and searches for it . I do not intend to boot from the external and therefore opted to save the search time and not enable USB. Same for 1394. I ran the system with them enabled and unenabled and there was no difference except it searched for the drives when BiNG does it's drive search.

Partitiin infor attched.

I'd send a screen shot of DISKMGMT but I don't know of a screen capture program that will give me a file that is small enough to transmit. Is there such a program?

[Paul Komski]

I understand the USB setting in BiNG allows BiNG to use a USB drive as a boot drive and searches for it.

It doesn't work that way. Regardless of bootability, BiNG may not be able to see an external drive at all. In order to see it, its USB2 setting may or may not need to be enabled; both settings should be tried if there is a problem with recognition. If BiNG attempts to boot an external drive it will almost certainly fail since this is dependent much more on the BIOS than anything else. Even on mobos that purport to boot to USB drives, this will usually only work to USB CDDrives, FloppyDrives and ZipDrives or to "hard drives" that are able to emulate one of this trio.

This time in partinfo Disk1(280g), Disk2(76g), Disk3 not mentioned, Disk4(4g) and Disk5(55g). The missing Disk3 is presumably the zip drive.

You can upload pics to sites such as http://www.postthatpic.com/ and then post the link to it here if you have difficulty with screenshots that are too big to upload here within the 20k limit.

So am I right in thinking that (leaving chkdsk aside for the moment) most or all of your problems are with the external drive. If you can't get it recognised by BiNG or Disk Management or partinfo then detach it from its enclosure and swap it temporarily for one of your other hard drives. That's the only rational way to discriminate between a problem with the drive and a problem with the enclosure or its cabling.

[mrmomaz]

So that we are both working towards the same problem resolution, I'd like to mention that this thread started with my not being able to see my external drive via firewire. When I switched to USB (only changing the cables) I could see and work with the external drive as if nothing had happened.
Some time later (I don't remember if it was that day or the next) I started getting stop errors 0x19 and 0x23 (and a few others) and I posted on the same thread for help with the stop codes. I most recently added a post on this thread that I turned the drive off during a CHKDSK run causing more problems.

The stop codes bother me the most as I'm afraid to open files that I'd really be upset if they were to be corrupted because of a stop error. How we proceed I'll leave up to your desecration. Maybe it is more than a bad 1394 cable? I did run the Seagate diagnostic program against the external drive and it came up clean. I also did CHKDSK /f/r two nights ago on the ext HDD and found no errors.

NOTE: I have two OSs in my dual boot, both win xp/pro/sp2. One is a copy that has been around for a long time and has many programs installed (NORTON-80GIG). The other OS is a clean install and has minimal programs loaded (COX-280GIG). The 280GIG OS gets very few stop errors while the 80 gig gets them all the tiime. I did a repair install on the NORTON/80G drive(followed michaelstevenstech.com/xprepairinstall.htm) but this did not help.

Which problem we work on first I will leave to your desecration.

I did not know about uploading and supplying the URL. thanks. I will work on that next. (A picture helps me understand and maybe it would help you too?)

I understand the deeper workings of the USB2 and 1134 bottons in BiNG now. I have been able to get to my external drive with the buttons enabled and with them unenabled, so I would assume that the button are not an issue?

'This time in partinfo Disk1(280g), Disk2(76g), Disk3 not mentioned, Disk4(4g) and Disk5(55g). The missing Disk3 is presumably the zip drive." I agree that the zip AND RACK have changed places - w/o my changing anything, other than eliminating the ext HDD.

"So am I right in thinking that (leaving CHKDSK aside for the moment) most or all of your problems are with the external drive." YES (stop coeds and 'folder entry removed' errors)
" If you can't get it recognised by BiNG or Disk Management or partinfo then detach it from its enclosure and swap it temporarily for one of your other hard drives. That's the only rational way to discriminate between a problem with the drive and a problem with the enclosure or its cabling. " I don't think this is needed as I can get to the drive USB. 1394 can be tested later.
thanks for the post

[Paul Komski]

I've lost a HDD. I cannot see the drive in either Windows Explorer, Partition Magic or BiNG.I was working towards finding your lost HDD. But it seems like you have already found it then and that it is the external.

I never rush to run chkdsk unless the cause of a problem is known.

STOP errors are not directly related to the file system. They occur when something or some application crashes. They have multiple causes from rogue software programs to bad hardware and can often be very hard to pin down. A process of elimination is usually done early-on by booting to safe mode or of using msconfig to try to detect if a particular program can be fingered as the cause. The next is to try swapping hardware items and by simplifiying the system. If one is technical enough Dr Watson Logs or other memory dump analysis and debugging can be helpful. Faulty hardware can go right down to the motherboard itself. Occasionally flashing the BIOS can be helpful if the problem are caused by chipset configs that can be updated.

A clean reinstall may prevent such errors either totally or just for a while. I still think that it is worth trying things without the USB device and with as few hard drives attached as possible. The same philosophy of simplifying things and then seeing if problems disappear.

[mrmomaz]

I had the feeling that you were working on the lost drive problem and I was working on STOP errors. Now that we are on the same page, what to do is the question.

I did the MSCONFIG exercise where I disabled all the START-UP items and added them back in after running tests (deleting items actually). I did not find an offending element. (But then how long does one run before an intermittent problem occurs?)

I used the NORTON/76GIG OS most of today and the only problem I had was it would run *very* slow now and then. A reboot solved the problem, but no STOP errors.

I"m not technical enough to rumable thru a Dr. Watson or memory dump.

I also worked in Safe mode and everything worked safe mode normal.

From your comments: what I can do is:

uninstall any recently added software,
run without the ZIP drive,
disconnect the 280Gig/COX drive,
reinstall drivers ????????,
maybe reinstall heavily used programs???,
run programs that I remember causing STOP errors before,
delete as many records as I can [probably not many w/o all my drives,
if i can find a pattern, then work with MSCONFIG and/or SAFE mode,
I don't know what else to do beside fixing records in the EXT HDD and repeating the above with that dirve attached.,

How else would you suggest I approach the problem of finding STOP errors?

and how do I go about getting my records back on the extrnal drive? I may find the stop errors when I connnect the ext drive.

[mrmomaz]

One should not talk too soon. As soon as I made the above post, I began activating postthatpix.com.... OPERA was not responding so I attempted to switch to IE at which time I received a stop error ox50 [see attachement - hopefully- to see if any of the information is useful to you.] Maybe I have to bog the system down?? I believe this is the second time I have received a 0x50 stop error.

other specifics are: stop 0x050 PAGE_FAULT_IN_NONPAGED_AREA
file css_dvp.sys date stamp4484751c

see http://www.imagehosting.com/show.php/257945_seriousError.JPG.html

[Paul Komski]

As far as recovering lost files goes you could try GetDataBack (http://www.runtime.org) or other software recovery programs such as used HERE (http://certificationchat.com/showthread.php?t=22235).

If you are not getting the blue screening in Safe Mode or after disabling items via msconfig then these BSODs are very likely to be software related - as shown in posts like THIS (http://www.cablehell.co.uk/forums/index.php?showtopic=21696) (not that you would necessarily be running NTL Netguard).

[mrmomaz]

Would you guess this is a software or hardware problem? I have BiNG Image backups of my OS and could use those?

[Paul Komski]

There is always overlap between software and hardware or they would never be able to have a symbiotic relationship.

If parts of the file system have become corrupt so that files are absent or damaged one can call this a software problem. If viruses or hijacking is running amuk this also can be called a software problem. Of course it could have been either software (eg a virus) or hardware (eg a failing disk or sudden power surge) that was the primary cause.

I dont want to get into semantics but if a system boots up and operates normally in safe mode but not in normal mode this indicates that some software (including the file system) has gone astray somewhere and that one isn't dealing with say an overheating CPU or bad RAM. In that sense I think you have a software problem but that doesnt mean that your hardware or its supporting drivers are A-OK.

If you have backups of your data then you dont need to use recovery programs such as GDB but if you do need to recover such data then GDB is one of the most consistently successful round here. In data loss situations use recovery software first before using chkdsk/scandisk to repair the file system since in "tidying-up and repairing" they can do more harm than good to data in an attempt to get the file sysem reintegrated.

If you are only getting problems on an external drive then the hard drive in it could be beginning to fail or the USB/Firewire interface could also be suspect. That is the reason for suggesting using it as an ordinary IDE drive and of testing it with its makers' diagnostics.

[mrmomaz]

In data loss situations use recovery software first before using chkdsk/scandisk....
How do I prevent CHKDSK/SCANDISK from starting automatically by windows during or after a reboot?

There is always overlap between software and hardware
I now have a better understanding of which direction my problems are. I have an BiNG image back up of my OS from some time ago (before disk problems) which I will restore and test. I will also run mfgr full disk test against the questionable drive, which is still under warranty.
That is the reason for suggesting using it as an ordinary IDE drive and of testing it with its makers' diagnostics.quorisity question--do i understand you right that the external case can be opened and the actual disk mounted in the tower? hmmm

If you have backups of your data...
I was refering to an operating system back up. I unfortunately moved a lot of files around the night before CHKDSK did me in, so I don't know what files were on that drive. SO I will probably move any good data off that external drive and then play with GDB for experience purposes if nothing else. There are a few files on the ext drive which I really do want- many I can suffer not having.

[mrmomaz]

As far as recovering lost files goes you could try GetDataBack (http://www.runtime.org) .... I actually tried GDB (and liked it) but it did not/could not recover the files that I told CHKDSK to return to freespace and they appear to be the only files that were effected. (CHKDSK/FREESPACE only took one folder which is probably all backed up.) Long story short, the files that I really wanted were intact and I felt there was a high enough probablility that I would not lose any file that I could not recreate, so I did not run GBD; nor pursue any other recovery program. I will rely on my backups and the data that is still on the disk.

If you are not getting the blue screening in Safe Mode or after disabling items via msconfig then these BSODs are very likely to be software related - as shown in posts like THIS (http://www.cablehell.co.uk/forums/index.php?showtopic=21696) (not that you would necessarily be running NTL Netguard). I did not seem to get the BSoD in either Safe mode or with MSCONFIG/startup modified. (but this is an intermittant thing)


I found the quoted article very interesting as I also suspected cs_dvp.sys as well as Dustbuster. (Norton I.S. claimed Dustbuster had a virus and wanted to clean or delete it and Dustbuster is an AV program itself. I d/l ed Dustbuster a few weeks ago when NIS targeteed a system file as being a virus.)

The short story is: I restored the oldest BiNG partition of the problem Windows and have been running for 3-4 days without any stop errors. I have all my drives up and running and am doing file transfers between HDDs as well as large sorts to test both the cooling and the power supply. I lost some windows settings and will have to reinstalll a couple of utility programs, but that will be done slowly to see if they cause a problem.

I've learned a lot with this problem. I may run into it again as I reinstall the utility programs, but I'm better prepared for it this time. thanks for your help.