Which hard drive is hard drive 2?
An out of town friend has a old version of Acronis which is showing the errors in the attached log.txt file. This is his second hard drive in the machine in 5 years.
The machine has multiple hard drives (see DriveLayout.png). I volunteered to go out and replace the faulty drive but I want to make darn sure that is his data drive (one with C: D: and unallocated partitions) that is the problem one and not one of the other hard drives. I am asking because it appears Acronis numbers the hard drives starting at 1 whereas Windows starts at 0.
This version of Acronis does not appear to have the reporting capability. However I have attached a screen shot of Acronis Clone disk screen which I assume should be using the same numbering scheme as during an image backup.
Drive 2 in this screenshot is an old Maxtor hard drive which I do know is failing BUT does NOT have drive letters assigned to it as my friend does not use it any more. My question is this Drive 2 that Acronis Image backup complaining about? If so why is is it since the only 2 drives involved in the Acronis imaging are Disk 3 (source) and Disk 4 (destination for backup). The thing is that when I remotely do a chkdsk /f on the two partions on Disk 3 (as shown in screenshot) the next day Acronis does not complain for a week or two.
I will be going out there in a day and will unplug the power to the disk 1 and disk2 drives as neither have drive letters assigned to them in XP.
Call me confused!
As I would interpret the text file attachment, line 22-23 refers to disk 3 as the disk receiving the backup which you call Tiny.
Lines 3-7 where the error occurred indicates the disk 2 has two partitions (the unallocated is not considered as a partition), so this would seem to me to indicate the error message relates to disk 2 which is the the 640GB which has a volume name of XP in the first partition.
Acronis does start with 1 but you do not which disk is going to be considered as #1.
One source of confusion as to disk numbers:
A specific disk attached as an Esata will have different disk numbers than the same disk attached with a usb cable.
A disk attached to the motherboard will have different disk numbers than one attached to a PCI card.
A Sata disk will have a different disk number than a ATA disk or an ATA disk with slave.
If there are any SSD disks, these are often at the bottom of disk numbers.
My point being that knowing by disk number is confusing to say the least.
I intend to recommend to Acronis that an error message be identified with more disk identification rather than "disk 2." Certainly, they should be able to provide a serial or model number or volume name as part of the disk 2 error message.
The text file indicates disk 1 to be a single partition disk.
I don't know that I have been of much help. My diagnosis of disk number could be wrong.
Good luck.
As I would interpret the text file attachment, line 22-23 refers to disk 3 as the disk receiving the backup which you call Tiny.
Lines 3-7 where the error occurred indicates the disk 2 has two partitions (the unallocated is not considered as a partition), so this would seem to me to indicate the error message relates to disk 2 which is the the 640GB which has a volume name of XP in the first partition.
Acronis does start with 1 but you do not which disk is going to be considered as #1.
One source of confusion as to disk numbers:A specific disk attached as an Esata will have different disk numbers than the same disk attached with a usb cable.
A disk attached to the motherboard will have different disk numbers than one attached to a PCI card.
A Sata disk will have a different disk number than a ATA disk or an ATA disk with slave.
If there are any SSD disks, these are often at the bottom of disk numbers.
My point being that knowing by disk number is confusing to say the least.I intend to recommend to Acronis that an error message be identified with more disk identification rather than "disk 2." Certainly, they should be able to provide a serial or model number or volume name as part of the disk 2 error message.
The text file indicates disk 1 to be a single partition disk.
I don't know that I have been of much help. My diagnosis of disk number could be wrong.
Good luck.
As I would interpret the text file attachment, line 22-23 refers to disk 3 as the disk receiving the backup which you call Tiny.
Lines 3-7 where the error occurred indicates the disk 2 has two partitions (the unallocated is not considered as a partition), so this would seem to me to indicate the error message relates to disk 2 which is the the 640GB which has a volume name of XP in the first partition.
I looked at lines 3-7 and the only reference to disk 2 that I can see is line 7 which mentions 2-1. Is that indicating first partition on that hard drive?
My point being that knowing by disk number is confusing to say the least.I intend to recommend to Acronis that an error message be identified with more disk identification rather than "disk 2." Certainly, they should be able to provide a serial or model number or volume name as part of the disk 2 error message.
The text file indicates disk 1 to be a single partition disk.
No argument from me about it being confusing. I do not think it could be any more so. This is especially because Acronis indicates 0-0 which I take to mean Disk 0. How did you determine that disk 1 to be a single partition?
Thanks for all the help. Appreciate it.
Line 2 (0-0)is indicating it is checking the space before partition 1 on whatever disk it is. Nothing to indicate which disk #. This is assumed to be disk 1 but you have no clue as to which disk Acronis considers as disk 1.
Line 3 (1-1) is indicating it is checking the first partition of. Nothing to indicate which disk.
Line 4 (0-0) is indicating it is checking the space before partition 1 on the next disk (whatever it is)
Line 7 (2-1) is indicating it is checking the 2nd partition (whatever it is).
The above is how I am interpreting the results of the text posting. I may right and I may be wrong. I am not aware of posting by Acronis to provide any info as to how this information should be analyzed..
Geez not much wonder I was confused. Talk about obtuse messages. They should standardize on the O/S number scheme as well as indicating like you said Drive model and perhaps even partition label (if any). Too much info is better than too little.
Thanks for the explaination.
My suggestion would be to again check the disk for errors.
CHKDSK C: /R
and let it run overnight or it will take several hours. Chkdsk has been known to require more than one pass.
Check Events/appplications log file for results of actual corrections.