cancel
Showing results for 
Search instead for 
Did you mean: 

Image clean up failure (174)

xsoldier2006
Level 2

Hi all, 

    We are working on our Dedup storage shares quiet a bit recently. I'm guessing that maybe a couple images got moved/removed without acknowledging NBU so I"m seeing the image cleanup 174 error. Is there any solution or direction to dig into why and guide straightening this kind of issue? thanks

 

 

2/25/2015 7:16:06 PM - begin 
2/25/2015 7:16:06 PM - Info nbdelete(pid=3348) deleting expired images. Media Server: blamds2.newbalance.com Media: @aaaed     
2/25/2015 7:16:06 PM - Info bpdm(pid=23012) started            
2/25/2015 7:16:06 PM - started process bpdm (23012)
2/25/2015 7:16:06 PM - requesting resource @aaaed
2/25/2015 7:16:06 PM - granted resource MediaID=@aaaed;DiskVolume=BLA_OST_FILESHARE.blaexg2.LSU_Exagrid;DiskPool=LSU_FileShare_DP;Path=BLA_OST_FILESHARE.blaexg2.LSU_Exagrid;StorageServer=LSU_Exagrid;MediaServer=nbvrts01
2/25/2015 7:16:07 PM - Info bpdm(pid=23012) initial volume BLA_OST_FILESHARE.blaexg2.LSU_Exagrid: Kbytes total capacity: 41758369304, used space: 0, free space: 41758369304
2/25/2015 8:16:08 PM - Critical bpdm(pid=23012) sts_delete_image of image blamx1fcs.newbalance.com_1423884603_C2_F1_R97 failed: error 2060019 error occurred on network socket 
2/25/2015 8:16:08 PM - Critical bpdm(pid=23012) image delete failed: error 2060019: error occurred on network socket   
2/25/2015 8:16:08 PM - Info bpdm(pid=23012) ending volume BLA_OST_FILESHARE.blaexg2.LSU_Exagrid: Kbytes total capacity: 41779614404, used space: 0, free space: 41779614404
2/25/2015 8:16:08 PM - end ; elapsed time: 1:00:02
media manager - system error occurred(174)

1 ACCEPTED SOLUTION

Accepted Solutions

Marianne
Level 6
Partner    VIP    Accredited Certified

Oh dear!! Why on earth would you want to do that?

  We are working on our Dedup storage shares quiet a bit recently. I'm guessing that maybe a couple images got moved/removed without acknowledging NBU .....

Any kind of manual removal will cause all sorts of corruption and confusion. 
Try this: 

nbdelete -allvolumes -force

See this explanation: 

https://www-secure.symantec.com/connect/forums/nbdelete#comment-7767761

 

View solution in original post

1 REPLY 1

Marianne
Level 6
Partner    VIP    Accredited Certified

Oh dear!! Why on earth would you want to do that?

  We are working on our Dedup storage shares quiet a bit recently. I'm guessing that maybe a couple images got moved/removed without acknowledging NBU .....

Any kind of manual removal will cause all sorts of corruption and confusion. 
Try this: 

nbdelete -allvolumes -force

See this explanation: 

https://www-secure.symantec.com/connect/forums/nbdelete#comment-7767761