在Kubernetes用离线模式部署KubeSphere，部署完成后发现openldap-0和redis两个pod一直是ContainerCreating状态，进而导致ks-console和ks-controller-manager都无法正常启动。
1、kubectl describe发现报如下错误信息：
Mounting command: systemd-run
Mounting arguments: –description=Kubernetes transient mount for /apps/kubernetes/pods/d482cb4d-a457-43e9-a83a-128998c83d83/volumes/kubernetes.ionfs/pvc-994c9565-3061-4f2f-85e5-d3fa61ef4e80 –scope – mount -t nfs XX.XX.60.112:/apps/nfs/kubesphere-system-redis-pvc-pvc-994c9565-3061-4f2f-85e5-d3fa61ef4e80 /apps/kubernetes/pods/d482cb4d-a457-43e9-a83a-128998c83d83/volumes/kubernetes.ionfs/pvc-994c9565-3061-4f2f-85e5-d3fa61ef4e80
Output: Running scope as unit run-33540.scope.
mount: wrong fs type, bad option, bad superblock on XX.XX..60.112:/apps/nfs/kubesphere-system-redis-pvc-pvc-994c9565-3061-4f2f-85e5-d3fa61ef4e80,
missing codepage or helper program, or other error
(for several filesystems (e.g. nfs, cifs) you might
need a /sbin/mount.<type> helper program)
In some cases useful info is found in syslog - try
dmesg | tail or so.
Warning FailedMount 15s (x4 over 7m5s) kubelet, XX.XX..60.108 Unable to attach or mount volumes: unmounted volumes=[redis-pvc], unattached volumes=[redis-pvc default-token-8lnsc]: timed out waiting for the condition
2、由于KubeSphere需要default的storageClass，这里已经部署default的storageClass，对应的主机的nfs中的目录也有数据。
想请教一下各位大佬，是什么原因导致的呢？
