I've restarted 3DSpace Index and CloudView starts successfully, but I'm seeing these issues:

  - Unrecognized or unsupported filesystem type 'overlayfs' warnings on startup

  - CVDiskStats collection errors: Configuration failed for ds-null (Mike says these are OK)

  - Failed to switch to generation 197 error in the index client

  - The ingress for ootb-25x-main-3dspaceindex appears correctly configured

  Questions for you:

  1. Are there known issues with 3DSearch/3DSpace Index on 25x FD06 that could cause persistent 404s after a container recovery?

  2. Is there anything specific to the index that needs to be remounted or reconfigured after a full container bounce?

  3. Do you have any recommendations for getting search back to a healthy state — should we do a full index rebuild?