Partition error causing corrupted data

Please excuse my english as I speak french.

So may be anyone can be of assistance on that matter. I just purchase TI 8. I have a Dell 4500 with a 80g hard drive running XP home edition and SP2 installed. My drive is partitionned in C D E F G. I made a backup of partition C on drive F of my harddisk. Everything wnet fine. I used the boot CD to reload the image ( Drive C active partition selected) All went fine. Except that I experimented slow booting and some programm seem to run very slowley. I used partition magic 8 from PowerQuest to check my hard Disk. I was given the message that a Extended partition on Disk 1 crossed the 1024 cylinder boundarie and should be mark as extendedX partition to avoid corrupt data.
Once PowerQuest fix that problem, the system was running well. So After many attemp to reload a image of my Drive C (Boot image) I had each time to run partition magic to fix that boudarie problem ( no idea what it is). So how can I prevent TI 8 to cause that error

M Denis T

 

I too get the powerquest error message about fixing the extended partition to extendedX. any advances on this ?

 

Hi, denistr and reep

You might not have noticed that this is Acronis Ti Forum.

If you need advice on another product works it is best to post in General Software and Services Forum.

But a quick word is that the software product you are talking about always says that as it works the cylinder boundaries on a fat file system.

Take Care,
TheQuest

 

Hi, it is or can be a Acronis Ti problem.
I have the same problem. After a clean Windows XP install on NTFS drives and after a Create Image and Restore Image with Acronis all seems well. But rebooting the system with a PQ DriveImage 6.00 recovery cd after that the same error report is generated which PQ than fixes.
If the boundry crossing is a real threat for your data and it is caused by a Acronis restore than it is a Acronis problem!
I want to know if I must take this Powerquest warning serious or not for my peace of mind..

Regards,
Henk

 

I get the same problem if I clone a disk which has an extended partition. I had thought TrueImage was not creating the cloned extended partition correctly. I originally created the extended partition with PartitionMagic so I suppose that PM might not be creating it in the correct format. If I run PartitionMagic it reports the situation and gives the option to fix it. I suppose I should do a test by creating the extended partition using Windows Disk Management and then see what happens when I clone it.

 

Hello denistr,

Thank you for choosing Acronis Disk Backup Software.

Please make sure that you use the latest build (937) of Acronis True Image 8.0 which is available at: http://www.acronis.com/homecomputing/support/updates/

To get access to updates you should create an account at:
http://www.acronis.com/homecomputing/my/
then log in and use your serial number to register your software.

Please also check each partition of your hard drive by Windows utility:

- For Windows 9x please use Windows menu Start\Run
then enter the command "scandskw" and test all drives;

- For Windows XP please use Windows menu Start\Run, then enter the command
"chkdsk c: /r" "chkdsk d: /r" for every partition of your hard drive.

Please note that you will need to reboot your computer in order to scan the system partition.

Create new image of a system partition, restore it then and see whether the problem still persists.

If the problem still persists then please create Acronis Report as it is described in Acronis Help Post prior to restoring the image (when the problem is fixed and everything works fine).

Restore the image of a system partition then and create new Acronis Report before fixing the problem using PowerQuest (when everything works slowly).

Rename the first report to report_before.txt and the second report to report_after.txt.

Send these files to support@acronis.com along with the link to this thread. We will investigate the problem and try to provide you with the solution.

Thank you.
--
Alexey Popov

 

I have run into this isssue too.

WinXP Pro SP2 working fine, boots OK, and TI creates/verifies images fine while in windows. When rebooting to restore the system partition, TI reports image is corrupt. Rebooted back into winxp and TI verifies image as OK.

I finally got TI to restore the image by booting with the TI rescue CD instead of the TI MBR boot and NOT choosing to verify the image.

Partition Magic 7 reports an Extended partition on Disk 1 crossed the 1024 cylinder boundary and should be mark as extendedX partition to avoid corrupt data. I let Partition Magic fix this, but TI still reports images as corrupt when rebooting to TI, or using TI rescue CD (not in windows).

I cannot use my winxp o/s cd to boot to recovery console, either! (to attempt to fix MBR) It gives me a blue screen with a STOP: 0x0000009C error after loading all the drivers.

Using special version of TI, build 903.

Is my 1 year old Maxtor 80GB drive going bad??

Problem still there after performing chkdsk /r on all partitions and creating a new image. The issue is that I can never "fix" the problem.

Partition Magic thinks the extendedx partiton is now marked correctly, as I do not get any errors running Partition Magic (until I restore an image). System boots into winxp fine. And I can create/verify/explore images while in windows.

But I am always getting the corrupt image error when running TI from boot or CD and can not run winxp CD to do a repair install or run the winxp recovery console.

 

Have a look at: http://support.microsoft.com/?kbid=329284

 

Thanks tachyon42, I did run across that MSKB article. I think I've narrowed it down to a heat problem - I used a hairdryer set on "cool" to cool off my power supply and cpu/memory. I was then able to boot to the recovery console from the winxp cd AND could also verify images from the TI boot CD. Once I let Partitionmagic fix the extendedX error, I did not see it again.

I've got the side of my case off now and I am suspecting a power supply heat issue at this point... my cpu temp monitor showed only 120 deg. with the case buttoned up, so I don't think it is that.

So, my issue does not appear to be directly caused by any TI or MBR/partition issue. Once things warm up with the case buttoned up, the Partitionmagic extendedX error reappears along with the failure to verify TI images (except in widnows) and STOP: 0x0000009C error when booting from winxp o/s CD.

My faith in TI 8 has been restored for now

 

Weird symptoms, hard to believe!

 

Follow-up: First test of the morning with a "cold" system. I booted with TI CD, verified & restored my good image of last night. TI verify & restore went well. Checked with PartionMagic - PM showed the extendedX partition error. WinXP CD boots to rescue console.

So I can confirm that restoring my system and data partitions with TI 8 (special version 903) boot CD will give me an extendedX partition error in Partition Magic.

I am not concluding if this is either TI or PM related...

I'm not sure what that means for my system, as I have restored with TI many times and have never checked for the extendedX partition error with PM before. No speed issues with the extendedX condition here, as the original poster, denistr, reported.

Other than that, I'm off power supply shopping today. I got this case w/supply new in the box for only $40 a year ago, so the p/s is pretty generic.

 

It's a confusing set of symptoms so maybe there are several problems which are causing it. I suppose you checked that the fans are working correctly.

 

Fans are OK... I think I've narrowed it down to the CPU. When winxp cd gives me the STOP: 0x0000009C error, I took off the side of the case and cooled only the cpu heatsink. It didn't feel hot, just warm. BIOS said 114 deg F. Winxp cd booted OK after about 30 seconds of cooling.

I'm measuring temp with a thermocouple mounted with compound on the heatsink right over the chip. Anything 114 deg F or above gives me the xp CD boot error. Could I have a half-baked cpu? (it's a used slot 1 P3-600M). I've re-mounted the heatsink with arctic silver compound, but get the same temps. CPU only cost me $30 + shipping -> maybe I should buy another and try it - - -

 

More on subject... I repartioned my HD so the extended partition begins with cylinder 1024. This gave me a primary partition of about 8GB.

You would think that since my ext partition no longer "crosses" the 1024 cylinder, I would no longer see the "Extended partition on Disk 1 crossed the 1024 cylinder boundary" warning in PartitionMagic after restoring an image with TI. I still got it.

I think for users like me using xp (esp. w/NTFS) and not using a boot manager to boot other o/s's (like DOS or linux), this is of not much consequence. XP doesn't care about the 8GB (1024 cyl) limit.

Still, it is a curiosity why restoring an image with TI makes PM want to re-mark the extended partition as an extendedX partition.

 

If it's a used CPU maybe the previous owner damaged it by overclocking or something. Problem could also be the motherboard. Can you test CPU in another motherboard or another CPU in this motherboard?

Anyway I think we can conclude that the ExtendedX problem is a separate issue with either PartitonMagic or TrueImage.