![]() |
|
Welcome to Vista Banter. You are currently viewing our boards as a guest which gives you limited access to view most discussions, articles and access our other FREE features. By joining our free community you will have access to ask questions and reply to others posts, upload your own photos and access many other special features. Registration is fast, simple and absolutely free so please, join our community today! If you have any problems with the registration process or your account login, please contact contact support. |
|
|||||||
| Windows Vista File Management Issues or questions in relation to Vista's file management. (microsoft.public.windows.vista.file_management) |
|
|
|
LinkBack | Thread Tools | Display Modes |
|
|||
|
Gerry
There is a lot of information on the net about this problem. It appears to be an issue with a drive in all cases, but nothing consistent with the drive type. Take a look at the following link, maybe something will jump out at you. "vista" "volmgr" "The system failed to flush data to the transaction log" - Google Search: http://www.google.com/search?hl=en&q...=Google+Search -- Ronnie Vernon Microsoft MVP Windows Desktop Experience "Gerry Hickman" wrote in message ... Hi, OK, I don't think the problem is anything to do with VSS. I now see what's happening. I'd been running chkdsk at the exact time of these problems, and it's chkdsk that starts VSS! The original problem is that the hard disk becomes unresponsive, and the Event log fills up with Event 57 volmgr The system failed to flush data to the transaction log. Corruption may occur. \Device\HarddiskVolume3 This is a DYNAMIC volume, otherwise it would probably say something like the "the device did not respond within the timeout period". Microsoft's Event help does not have any help on the volmgr Event. Caching is disabled, so I don't know why it needs to "flush" anything, it should give an IO error instead. Gerry Hickman wrote: Hi Ronnie, Kerry is correct about the Previous Versions being tied to System Restore. You cannot disable these components, individually. OK. If System Restore is enabled, the way it works is to create a Restore Point once a day, by default. It then monitors that drive and records any changes. The only other thing that might be using the Volume Shadow Copy Service would be if you have a Scheduled Backup set to automatic. I don't have any backup jobs defined. I can see VSS service start-up in the Event log at times that do NOT match the SR scheduled task. I've disabled SR on the C drive now, will see if VSS ever starts on it's own again... |
|
|||
|
Well, I don't know how to "turn on" the Shadow Copy... That is the most
important thing, I guess... Then, maybe, when I try to install MS updates and other MS software and hardware that I own, it might work without me sitting here going through everything as I did with Windows 95 - through Vista... any help greatly appreciated! -- White 27 "Kerry Brown" wrote: If you turn off Automatic restore points for a drive it also turns off Previous Versions. -- Kerry Brown MS-MVP - Windows Desktop Experience: Systems Administration http://www.vistahelp.ca/phpBB2/ "Gerry Hickman" wrote in message ... Hi, (Vista SP1 x86) Over the last few months I've been seeing an issue where one of my hard drives becomes unresponsive, then it returns to normal. At first I thought it was a faulty hard drive, either remapping bad blocks or failing internal cache, but extensive block-level and SMART testing indicated the drive was OK. I now notice there's a pattern to this problem. The Volume Shadow Copy Service is always being started by Windows around the same time I'm seeing the problem. I looked in the scheduled tasks to see what times System Restore (SR) was running, but the times did not coincide with the problem. I now wonder if it's something to do with the "Previous Versions" feature? I'd like to disable what ever is causing VSS to start, I can disable SR, but don't know how to disable "Previous Versions". I don't really want to disable the VSS service completely. I'd like to run it like this for a few weeks and see if it solves the problem. -- Gerry Hickman (London UK) |
|
|||
|
Hi Ronnie,
There is a lot of information on the net about this problem. It appears to be an issue with a drive in all cases, but nothing consistent with the drive type. Take a look at the following link, maybe something will jump out at you. "vista" "volmgr" "The system failed to flush data to the transaction log" - Google Search: http://www.google.com/search?hl=en&q...=Google+Search Yes, I'd read most of those before posting here, wasn't convinced of the answers. Disabling ReadyBoost certainly didn't make any difference. I've ordered a new drive. -- Gerry Hickman (London UK) |
|
|||
|
Yellowscarf47
Go to Start and type services and click services in the results. Scroll down to Volume Shadow Copy and double click. Set the Start Up Type to automatic and click the Start Button. -- Ronnie Vernon Microsoft MVP Windows Desktop Experience "yellowscarf47" wrote in message ... Well, I don't know how to "turn on" the Shadow Copy... That is the most important thing, I guess... Then, maybe, when I try to install MS updates and other MS software and hardware that I own, it might work without me sitting here going through everything as I did with Windows 95 - through Vista... any help greatly appreciated! -- White 27 "Kerry Brown" wrote: If you turn off Automatic restore points for a drive it also turns off Previous Versions. -- Kerry Brown MS-MVP - Windows Desktop Experience: Systems Administration http://www.vistahelp.ca/phpBB2/ "Gerry Hickman" wrote in message ... Hi, (Vista SP1 x86) Over the last few months I've been seeing an issue where one of my hard drives becomes unresponsive, then it returns to normal. At first I thought it was a faulty hard drive, either remapping bad blocks or failing internal cache, but extensive block-level and SMART testing indicated the drive was OK. I now notice there's a pattern to this problem. The Volume Shadow Copy Service is always being started by Windows around the same time I'm seeing the problem. I looked in the scheduled tasks to see what times System Restore (SR) was running, but the times did not coincide with the problem. I now wonder if it's something to do with the "Previous Versions" feature? I'd like to disable what ever is causing VSS to start, I can disable SR, but don't know how to disable "Previous Versions". I don't really want to disable the VSS service completely. I'd like to run it like this for a few weeks and see if it solves the problem. -- Gerry Hickman (London UK) |
|
| Thread Tools | |
| Display Modes | |
|
|