Emerson Exchange 365

• Not Answered

Updates don't install when using "Microsoft Security Updates Installation via Batch File" - insufficient disk space

Guardian KBA AP-0900-0040 provides packages for a "batch install" of approved security updates, and I was curious why after uploading the latest REG file Guardian still showed I had a server that lacked a recommended update.

Launching it manually, the missed package eventually indicated "insufficient disk space" to install the patch. A glance at file explorer showed less than 2 GB remaining on C: drive.

I didn't see the insufficient space alert because the batch installer silences all console interaction (thankfully).

So a couple thoughts:

1.) One should always ensure sufficient disk space on C: drive. Maybe try installing the big cumulative Windows update manually.

2.) What's the least disruptive "supported" way to increase the space on C: drive (e.g., without doing a total OS & DeltaV reinstall)? D: is on the same physical RAID array and has abundant unused space . . .

-John

John Rezabek

• 22 Jun 2021 9:29 PM
• Cancel

9 Replies

• Felix

  

  • 22 Jun 2021 10:11 PM

  Recently something similar happened to me, I applied the settings indicated in NK-2100-0003, that helped me to recover space in C:
  Greetings.
  
  -Felix

  • Cancel
• David Foose

  

  • 23 Jun 2021 1:22 PM

  Not a DeltaV expert, but throwing out a couple items:
  
  - Windows has a "disk cleanup" feature. You can find that in the settings depending on what version of Windows you are talking about. I personally think that stuff in the recycle bin and downloads directory are fair game. You may also want to see the section marked "Windows Update Files". That is sometimes an optional setting to clear. Those are leftover copies of older files in case you want to remove/revert updates. If you are confident you aren't going to need to uninstall updates, that SHOULD be safe to purge too. It might be gigs of space just by itself.
  
  - I'd check to see why your HD is filled up. That isn't a good sign overall as it can indicate real issues with log files growing out of control, backups never being moved off or purged, or even (in some edge cases) cybersecurity concern with an attacker staging files for exfil or further attacks. Generally, I'd start with the known bad actors like OPC links, backup jobs, or log files. You may need to do a quick analysis via explorer to find which folder is huge in comparison. Not sure what the DeltaV's acceptance of the Sysinternals apps from Microsoft, but there are a couple in there that called diskview or disk usage that you could run or you just open explorer and do a little bit of hunting by right clicking on folders and checking the size, then narrow down the culprit. I'd start with temp folders, then move to program folders.

  • Cancel
• Tim Alexander

  

  • 24 Jun 2021 12:38 PM

  Look at disk space use of C:\Users directory
  
  A portable software (does not require install) that i recommend to inspect disk utilization is Space Sniffer (google will find it).
  
  If you open the Windows Task Scheduler, then navigate to \Microsoft\Windows\Servicing, there is a task called StartComponentCleanup. This will clean the WinSxS folder where windows updates are deflated from their compressed state.
  
  This can also be run from Powershell with the following command: Dism.exe /online /Cleanup-Image /ResetBase /StartComponentCleanup
  --The Reset Base removes superceded updates so you cannot roll back with Add/Remove Programs. This is less of an issue with Win10/SV16 as updates are cumulative.
  
  To actually utilize D:\ space what we have done during outages for customers is take an Acronis Backup using the Bootable Media with external drive to restore the same image to the machine, but modify the partition sizing to increase C:\ space when reapplying the image. If you have a server class machine with USB3 ports this can be done within 1 shift.
  
  I think as of now it is unsupported to relocate software from their default directories but we have also redone the AMS Server + installations as that creates the SQL data directory on the C:\ Partition by default and you are presented with a prompt to move it during install.
  
  It is not unlikely that the 80GB allocated for Server 2016 C:\ will be insufficient depending on your companion products.

  • Cancel
• Benji_Kidmose

  

  • 24 Jun 2021 1:46 PM

  In reply to David Foose:

  On our Operator Stations, I got to the point of blowing them away completely and starting over with a fresh install, was easier than every few months of patch installation trying to fight to find a bit of space. I also sometimes don't use the OEM image disk that comes with the machine, I have for instance one Pro station that gets lots of other software for various tasks and the 80GB is not enough, so I just load Windows 10 on it myself and partition the hard drives to a 20xx standard that makes more sense for today. hopefully Emerson in the future OEM images for hardware will partition the image from the start to have a more realistic hard drive size for C:\. Hard drives are hardly the cost driver for hardware anymore, sizing should reflect the low cost of space in todays hardware. At minimum the C:\ should be 120gb on workstations and 250gb on servers

  • Cancel
• Tim Alexander

  

  • 24 Jun 2021 3:00 PM

  In reply to Benji_Kidmose:

  Benji,
  
  As the D:\ Partition is empty with the default image, you can delete it, expand C:\ then recreate DVDATA(D:\) and proceed, using diskmgmt.msc

  • Cancel
• Benji_Kidmose

  

  • 24 Jun 2021 3:44 PM

  In reply to Tim Alexander:

  Hmm, good tip, your right should be able to expand prior to installing anything on D, missed the obvious simple solution. Easy fix on ops stations, will have to wait for next hardware upgrade to catch on servers.

  • Cancel
• Martin v. Bergeijk

  

  • 24 Jun 2021 3:45 PM

  In reply to Benji_Kidmose:

  Note: "You can use Disk Management to add space to an existing volume, extending it into empty space on the drive, but only if the empty space doesn't have a volume on it (it's unallocated) and comes immediately after the volume you want to extend, with no other volumes in-between. The volume to extend also must be formatted with the NTFS or ReFS file systems." See docs.microsoft.com/.../extend-a-basic-volume....

  • Cancel
• John Rezabek

  

  • 25 Jun 2021 1:43 PM

  In reply to Tim Alexander:

  . . . *not* unlikely 80GB will be insufficient . . . true that. The machine experiencing the issue is an APP station, historian, DeltaV Analyze, Communicator, OPC server (to PI on business network), etc. I applied most of the suggestions in NK-2100-0003 and now have > 20 GB free. We have the Emerson licensed Acronis service creating weekly images for this machine, but I've heard through song & story that Acronis doesn't capture "everything" needed for a DeltaV restore? Hence we are also manually backing up DB, Yellow Pages, graphics, etc. Any caveats other than PHV having a gap of a few hours?

  • Cancel
• Tim Alexander

  

  • 28 Jun 2021 1:11 PM

  In reply to John Rezabek:

  If you want to restore and clone the machine back to itself you can always take the backup when its off and you wont have to worry about the Acronis caveats you referred to.
  
  History and Events Gap if it is also the eChron Node.

  • Cancel