The vmware.log file is showing "Windows 7-s001.vmdk" : failed to open (14): Disk needs repair." not "Windows 7-s009.vmdk" as you show in the OP. Also why on earth would you start renaming the Extents form one to another directly. In other words if an Extent is missing or a corrupted one cannot be repaired using vmware-vdiskmanager then you copy an empty Extent (one the is ~320KB) to then name of the missing one or copy it to replace the corrupted one. Not start renaming several in a row at that will cause more damage then you already have! 
Hope you made a backup before your started messing around and did you first try using vmware-vdiskmanage?
Also note that in most cases if the first binary Extent is corrupted beyond repair or missing there is little how of successful recovery unless you have a backup to restore from and only a known good full backup to restore from will yield 100%successful recovery of the Virtual Machine itself and not necessarily current data beyond what's on the backup!