mrmomaz1234
Programmer
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?
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?
