Description of problem - 
Installed the scale cluster using toolkit and the S3 service is not starting after the cluster deployment. 

The OCP platform infrastructure and deployment type (AWS, Bare Metal, VMware, etc. Please clarify if it is platform agnostic deployment), (IPI/UPI):
Scale cluster

The ODF deployment type (Internal, External, Internal-Attached (LSO), Multicluster, DR, Provider, etc):
Standalone noobaa

The version of all relevant components (OCP, ODF, RHCS, ACM whichever is applicable):
noobaa-core-5.20.0-20251025.el10.x86_64

Does this issue impact your ability to continue to work with the product?
Yes blocking the test progress

Is there any workaround available to the best of your knowledge?

No

Can this issue be reproduced? If so, please provide the hit rate

Yes, 100%

Can this issue be reproduced from the UI?

N/A

If this is a regression, please provide more details to justify this:

Steps to Reproduce:

1. Create a scale cluster on RHEL10 platform.

2. Select S3 protocol enablement during deployment.

Actual results:

root@rednew-41:~# cat /etc/redhat-release 
Red Hat Enterprise Linux release 10.0 (Coughlan)
root@rednew-41:~# 
root@rednew-41:~# mmdiag
Current GPFS build: "6.0.0.1".
Built on Oct 28 2025 at 15:53:33
Running 3 hours 9 minutes 10 secs, pid 34876

root@rednew-41:~# systemctl status noobaa
● noobaa.service - The NooBaa service.
     Loaded: loaded (/usr/lib/systemd/system/noobaa.service; disabled; preset: disabled)
     Active: activating (auto-restart) (Result: exit-code) since Wed 2025-10-29 10:00:21 CET; 1s ago
 Invocation: 067b5b435f07475aab3a63e38fb06fc1
    Process: 567610 ExecStart=/usr/local/noobaa-core/bin/node /usr/local/noobaa-core/src/cmd/nsfs.js (code=exited, status=1/FAILURE)
   Main PID: 567610 (code=exited, status=1/FAILURE)
   Mem peak: 33.4M
        CPU: 398ms

NB : /var/log/noobaa.log is not generated 

Expected results:

S3 service should be up and running 

Logs collected and log location:

Additional info: