Monday, December 17, 2012 12:50 PM
I am currently finishing settin up a new env. for a customer, everything is ok except backup, i am currently backinup host and 3 vm on it.
i am receiving the following errors everytime the backup starts :
filter manager error id 3
volsnap error id 27
disk i/o error at logical bloc etc.. id 153
is everyone experiencing this ?
I already tried everything related to these knowns errors since they are quite famous in the windows history .. but no luck at the moment.
they only occurs if vms are on, if powered off backup runs fine.
however even with these errors backups finishes and restores are ok.
The bad part is that they are all related to the shadow that backup is mounting everytime for the procedure. (dont tell me to chkdsk my lun :) )
- Edited by Ales75 Friday, January 04, 2013 3:01 AM follow up
Monday, December 17, 2012 2:43 PMYou didn't mention which backup software you use. I assume you use Windows backup. This could be VSS issue. Please run VSSADMIN LIST WRITERS to check any errors?
Bob Lin, MVP, MCSE & CNE Networking, Internet, Routing, VPN Troubleshooting on
Monday, December 17, 2012 2:51 PM
Thanks for your answer..
yes i use WSB, well as i mentioned before i tried all the checks possibile.. i am an old user and fan of WSB.. and to be honest this is the first time i have problems like these.. usually at maximum in the past i had volsnap 27 errors.. but not filter manager and I/O
as a plus i isolated more the problem by doing this, before backup was relying on vvs software on the iscsi back up server, then i wanted to try the new hardware vss i installed it configured permission.. they are working perfect but errors are the same.. with both kind of vss.
on a hard disk i wouldn't be to much worried.. plenty solutions for fixing them.. but on the shadow i really dont know..
Monday, December 17, 2012 2:57 PM
want to add this..
i have a clue about the filter manager error, but doesn't help too much, i check to what pid is related and unfortunately to the nt system pid :(
i hoped it was on another service for exampe so i could had stop that particular service before the backup and then eventually with a task reactivate it after.. but.. no luck
Monday, December 17, 2012 3:38 PM
here you can see the two shadows mounted by WSB and on the right the errors generated..
just when wms are on if powered off , no errors. i am supposing there's a problem in mounting while already locked by the hyper V
Tuesday, December 18, 2012 4:35 PM
i just found a very long thread about this kinds of errors since 2010 and still nowadays not a real solution.
Friday, January 04, 2013 3:07 AM
at this point i would like to know if anyone using windows server backup especially for hyper v backups, is getting these kinds of errors, because i have on three new and different servers and i wasted too much time troubleshooting them.
Disk I/O error id 153 coming from the shadow mounted by wbadmin ! not the hard disk.. ! and always referred to the same blocks.
and often but not always, filter manager errors.
Or.. someone find an answer to this.. so i can have my answer too.. :)
This crazy after more then two years and solution.
- Edited by Ales75 Friday, January 04, 2013 3:17 AM correction
Friday, January 25, 2013 3:08 PMI have an identical problem where I'm getting 153:s after the last volsnap 66 event. Every night I get 4 warnings for the same blocks at the same time
Saturday, January 26, 2013 6:35 AM
welcome to the I/O group !
i still have errors and at the moment ignoring them, since even if i went on looking for fixes.. no way..
i have this on 4 different servers.. and since my last investigations i am sure its related to hardware/drivers problems.
i do get 4 warning same blocks to.. (funny)
what i noticed is that they are all coming from similar hardware, dell perc raid controller and seagate drives...
however i am quite sure it is related to the dell perc raid controller an not disks.
i guess what your hardware is.. ???? tell me please.. this will help the situation finding a correct way to fix it.
------------------------------------------------------- I understand a little computers.
Tuesday, March 19, 2013 7:00 PM
I have got the same roblem on two totally different servers: one is an Acer Ac100, the other an Lenovo. Both servers run Windows Backup without errors as long as the had Windows 2008R2 on it, but after upgrading to 2012 the report error 153 as soon the backup starts. This would be no problem, because the backup finishes, but sometimes the Windows Backup run into a timeout and windows tries to reset the Raid controller and does this until infinitely. Last resort then is to restart the server.
Thursday, April 18, 2013 3:36 PM
On 2012 Essentials running as a Hyper-V guest, I sometimes get 153 errors during Windows Server Backup to go with my bogus FilterManager 3 errors. Checking the 153 from yesterday, it was reported twice on Disk 6. But there are only four virtual disks attached to the server, two IDE and two SCSI, so it must be referring to a temporary drive created during the backup.
This year, I've seen two 153 events on 1/24, 2/20, 4/6, 4/8, and 4/17. So not often, but seems to be increasing in frequency. Maybe I will run chkdsk on the backup VHD just in case.
Thursday, May 02, 2013 2:15 PM
We are experiencing similar issues.
I have two Windows 2012 hyper-v servers with 4 virtuals on each server.
Whenever I back them up with Altaro Hyper-v backup I get the following messages in the event log.
So each time I backup a single Hyper-V server I get the following errors for each backup.
In the log files its looks like I get the disk errors after the following events “Volsnap”
Volsnap 64 (information)
Volsnap 66 (information)
Disk 153 (warning)
Disk 153 (warning)
My backups are successful and I have confirmed this with Altaro.
"When a backup is triggered, we request a shadow copy using the Microsoft Hyper-V VSS writer, which in turn requests a shadow copy inside each VM too along with the one on the host, this is then presented to Altaro for us to read and backup from, then dismounted.
These warnings are probably being written when a Microsoft VSS shadow copy is requested."
But long story short my backups are successful.
Wish I know why the Disk error warning is happening though.