X_STORAGE_LIST_FAILED
Means
the objects could not be listed
Typical cause
the disk refused a listing — a denied s3:ListBucket, a throttle, an expired credential, a root this process cannot read. A disk nobody has written to yet is honestly empty and answers an empty page; everything else reaches here, because sweepOrphans walks list() and a swallowed refusal certifies a prefix nothing could see as having no orphans
Fix
the fix is the driver's own — ls -ld <root> on local, aws s3api list-objects-v2 --bucket <bucket> on s3 — so it reproduces the refusal with the disk's own words