If the event persists, gather logs, and then contact Technical Support for additional troubleshooting. For instructions on how to
gather cluster logs, see
.
400120001
One of the boot disks is unhealthy, and the boot data is no longer being mirrored across the two boot disks. Loss of the
remaining boot disk will lead to node failure.
Administrator action
Boot disks are not customer-replaceable components. Contact Dell EMC PowerScale Technical Support.
400130001
The NFS export rules are configured in such a way that the client cannot mount the path.
Administrator action
If you want the client to have permission to mount the specified directory, modify your NFS export rules to permit access. For
more information, see the NFS section of the
OneFS Web Administration Guide
.
If the event persists, gather logs, and then contact Technical Support for additional troubleshooting. For instructions on how to
gather cluster logs, see
.
400130002
When processing NFS export rules, an attempt to look up the DNS name for the specified host failed.
Administrator action
1. Make sure that the DNS server includes an entry for the reported host name, and that non-PowerScale hosts can resolve
the host name.
2. Check for misspellings and typographical errors in the cluster NFS configuration. Where possible, use a fully qualified domain
name (FQDN) for every host in the NFS export rules. If you are not using a FQDN, make sure that each full domain name for
the host is part of the DNS search path in the cluster configuration.
If the event persists, gather logs, and then contact Technical Support for additional troubleshooting. For instructions on how to
gather cluster logs, see
.
400140001
The NFSv4 server could not look up the user or group name to map to a user id (UID) or group id (GID).
Description
NFSv4 uses the string 'user@domain' instead of numeric UIDs and GIDs. This event occurs if there is a mismatch between the
client domain name and the NFSv4 server domain name, or if the user database configuration is incorrect.
For example, the domain name stored in the
idmap.conf
file on the client might not match the NFSv4 domain name of the
cluster (vfs.nfsrv.nfsv4.domainname).
Software events
85