If this is your first visit, be sure to check out the FAQ by clicking the link above. You may have to register before you can post: click the register link above to proceed. To start viewing messages, select the forum that you want to visit from the selection below. |
|
|
Thread Tools | Rate Thread | Display Modes |
#1
|
|||
|
|||
Phantom disk problem.
On starting up this morning I get a prompt that the C: drive needs repairing, & that I should restart. I did, and the computer did the chkdsk & repair routine. It then restarted and the system stopped at auto repair and then went to the blue screen with the usual options to either restart, restore etc. I chose restart & the computer restarted as normal. Of course I rushed to do an image backup. The "HD Tune" found nothing wrong. What's going on? Among others, this figures prominently in Event Viewer..... https://postimg.cc/F1Shsg0n |
Ads |
#2
|
|||
|
|||
Phantom disk problem.
Peter Jason wrote:
On starting up this morning I get a prompt that the C: drive needs repairing, & that I should restart. I did, and the computer did the chkdsk & repair routine. It then restarted and the system stopped at auto repair and then went to the blue screen with the usual options to either restart, restore etc. I chose restart & the computer restarted as normal. Of course I rushed to do an image backup. The "HD Tune" found nothing wrong. What's going on? Among others, this figures prominently in Event Viewer..... https://postimg.cc/F1Shsg0n This thread gives me the "name" of the thing. It's a Macrium service as far as I know. https://forum.macrium.com/Topic23031.aspx Macrium Reflect Change Block Tracker (MRCBT) EventID 1013 VolumeShadowCopy4 ******* This is a "service" that runs with Macrium 7 or so. As far as I know. It has something to do with keeping track of changed clusters. It may have something to do with differential or incremental backups. But since it runs when you're not doing anything or have any scheduled stuff set up, it's a mystery as to what it's doing. Shadow Copies are invented, to allow "freezing" a volume at a particular point in time, and "new" writes are placed where they won't upset the frozen image. The backup software might refer to the Shadow Copy with the frozen image available in it. The "regular running" OS refers to the set of clusters that are currently up to date at the current point in time. Shadow Copies on OSes Vista+, support persistent shadows. That means a Shadow set up on one boot cycle in Vista, can continue to be used on another boot cycle. The OS supports as many as 64 shadows at one time - you can freeze the OS 64 times, and have things computed against those frozen points in time. Normally, you expect something like vssadmin list shadows to have a relatively small number of entries, like about five or so. ******* OK, now that I looked at your picture a third time, I see the EventID is 1013. https://forum.macrium.com/Topic26883.aspx https://forum.macrium.com/Topic26880.aspx The threads started Dec.2018 so are relatively recent. "MRCBT Errors since installing V7.2.3897 IRP_MJ_READ failed on device \Device\HarddiskVolume20 === real disk with status 0xC0210000 Event ID 1013 IRP_MJ_READ failed on device \Device\HarddiskVolumeShadowCopy10 == shadow with status 0x80000010 Event ID 1013 they coincide with the installation of: MR v7.2.3897 and continue into v7.2.3906. v7.2.3906 was installed on the 30th November. " "Status 0xC0210000L indicates that the volume was locked by Bitlocker Drive Encryption and status 0x80000010L indicates that the volume (shadow copy) was taken offline. ​​ These codes do not technically classify as errors and can safely be ignored. ​​They do not indicate an issue with either the disk or with CBT. ​ We are aware that CBT is too aggressive in its generation of these events and we will address this in the next update. " "Status 0x80000001 indicates that the volume (shadow copy) was taken offline. This status shows that something attempted to read from the shadow copy device after it had been taken offline. It has no dependency on BitLocker. " Which might not be quite true, if C: needs CHKDSK. CBT has a preference in Macrium, which might not work. Macrium can also be modified to remove CBT, which of course will likely come back on the next Update. "Uninstall the CBT component. Go to Control Panels Programs and Features select Reflect click Change Modify uncheck CBT. " "I don't do incremental backups, so the advantages of enabling CBT aren't particularly relevant to me. A side-benefit is that my full image backups seem to complete noticeably faster. " So CBT is related to incrementals (at the very least). Not related to full backups, if that is all you do. It's possible CBT was also the pig in the first Macrium 7 I tested, where I was seeing a service with high CPU, while Macrium was not running. I wish I'd kept notes of that. A later version "appeared" fixed. One of the perils of attempting to be "too whizzy" I guess. Paul |
#3
|
|||
|
|||
Phantom disk problem.
On Wed, 12 Dec 2018 20:00:31 -0500, Paul
wrote: Peter Jason wrote: On starting up this morning I get a prompt that the C: drive needs repairing, & that I should restart. I did, and the computer did the chkdsk & repair routine. It then restarted and the system stopped at auto repair and then went to the blue screen with the usual options to either restart, restore etc. I chose restart & the computer restarted as normal. Of course I rushed to do an image backup. The "HD Tune" found nothing wrong. What's going on? Among others, this figures prominently in Event Viewer..... https://postimg.cc/F1Shsg0n This thread gives me the "name" of the thing. It's a Macrium service as far as I know. https://forum.macrium.com/Topic23031.aspx Macrium Reflect Change Block Tracker (MRCBT) EventID 1013 VolumeShadowCopy4 ******* This is a "service" that runs with Macrium 7 or so. As far as I know. It has something to do with keeping track of changed clusters. It may have something to do with differential or incremental backups. But since it runs when you're not doing anything or have any scheduled stuff set up, it's a mystery as to what it's doing. Shadow Copies are invented, to allow "freezing" a volume at a particular point in time, and "new" writes are placed where they won't upset the frozen image. The backup software might refer to the Shadow Copy with the frozen image available in it. The "regular running" OS refers to the set of clusters that are currently up to date at the current point in time. Shadow Copies on OSes Vista+, support persistent shadows. That means a Shadow set up on one boot cycle in Vista, can continue to be used on another boot cycle. The OS supports as many as 64 shadows at one time - you can freeze the OS 64 times, and have things computed against those frozen points in time. Normally, you expect something like vssadmin list shadows to have a relatively small number of entries, like about five or so. ******* OK, now that I looked at your picture a third time, I see the EventID is 1013. https://forum.macrium.com/Topic26883.aspx https://forum.macrium.com/Topic26880.aspx The threads started Dec.2018 so are relatively recent. "MRCBT Errors since installing V7.2.3897 IRP_MJ_READ failed on device \Device\HarddiskVolume20 === real disk with status 0xC0210000 Event ID 1013 IRP_MJ_READ failed on device \Device\HarddiskVolumeShadowCopy10 == shadow with status 0x80000010 Event ID 1013 they coincide with the installation of: MR v7.2.3897 and continue into v7.2.3906. v7.2.3906 was installed on the 30th November. " "Status 0xC0210000L indicates that the volume was locked by Bitlocker Drive Encryption and status 0x80000010L indicates that the volume (shadow copy) was taken offline. ?? These codes do not technically classify as errors and can safely be ignored. ??They do not indicate an issue with either the disk or with CBT. ? We are aware that CBT is too aggressive in its generation of these events and we will address this in the next update. " "Status 0x80000001 indicates that the volume (shadow copy) was taken offline. This status shows that something attempted to read from the shadow copy device after it had been taken offline. It has no dependency on BitLocker. " Which might not be quite true, if C: needs CHKDSK. CBT has a preference in Macrium, which might not work. Macrium can also be modified to remove CBT, which of course will likely come back on the next Update. "Uninstall the CBT component. Go to Control Panels Programs and Features select Reflect click Change Modify uncheck CBT. " "I don't do incremental backups, so the advantages of enabling CBT aren't particularly relevant to me. A side-benefit is that my full image backups seem to complete noticeably faster. " So CBT is related to incrementals (at the very least). Not related to full backups, if that is all you do. It's possible CBT was also the pig in the first Macrium 7 I tested, where I was seeing a service with high CPU, while Macrium was not running. I wish I'd kept notes of that. A later version "appeared" fixed. One of the perils of attempting to be "too whizzy" I guess. Paul Thank, I did yet another Properties/Tools/Check on all my disks and found a remote one (an old Intel SSD) that needed fixing. After this the problem went away. I note that Macrium always detects all the disks when starting & maybe this caused it. |
Thread Tools | |
Display Modes | Rate This Thread |
|
|