 Running ess_ssr_setup hangs if recovery group descriptors exist. This
will simply hang and does not indicate that descriptors were found.An SSR might see the following
output:
Do you want to continue and perform changes and tests in this node? (y/n): y
2022-08-19 09:38:44,234 INFO: Going to set the root user password of this node to the password typed before
2022-08-19 09:38:44,433 INFO: Run 'Root_password_set' completed successfully
2022-08-19 09:38:44,602 INFO: Run 'Passwordless root SSH localhost' completed successfully
2022-08-19 09:38:44,602 INFO: Going to perform storage tests on this node
2022-08-19 09:38:44,602 INFO: Going to run 'Quick storage configuration check'
2022-08-19 09:38:45,484 INFO: Run 'Quick storage configuration check' completed successfully
2022-08-19 09:38:45,484 INFO: Going to run 'Check enclosure cabling and paths to disks'
2022-08-19 09:39:38,432 INFO: Run 'Check enclosure cabling and paths to disks' completed successfully
2022-08-19 09:39:38,432 INFO: Going to run 'Check disks for IO operations'
Product
- ESS 5000
- ESS 3500 (4u102)
 |
The SSR should contact service for help. |
When the essinstallcheck command is run, an error might occur. Customers
might face this issue when they run the essrun healthcheckcommand (that runs the
essinstallcheck command) with multiple nodes or group. The
mmvdisk locks other nodes when querying is the cause of this
error.Product
- ESS 3000
- ESS 3200
- ESS 5000
- ESS 3500
- ESS 3500 (4u102)
|
- Check Ansible logs before you run the mmvdisk command (in
essinstallcheck) and retry when ready.
- In the field, run the healthcheck command on individual nodes if the error
is seen.
|
|
The essrun update might hang with 'waiting for free locks'. The
mmapply policy causes locks.
Friday 12 August 2022 21:02:23 +0000 (0:00:00.536) 0:34:26.503 *********
FAILED - RETRYING: Waiting for free Locks (100 retries left).
FAILED - RETRYING: Waiting for free Locks (99 retries left).
Product
- ESS 3000
- ESS 3200
- ESS 5000
- ESS 3500
- ESS 3500 (4u102)
|
- Check if policy is being applied and wait until it finishes to run update.
- Run the mmcommon showlocks command to check what is causing the lock.
For more information about locks, see IBM Spectrum Scale Administration Guide.
|
GUI: wizard setup is not allowed to move past Rack Locations. Moving backward through GUI
and then trying to move forward is blocked.Product
- ESS 3000
- ESS 3200
- ESS 5000
- ESS 3500
- ESS 3500 (4u102)
|
- Back up to a Location information and re-enter the data.
- Clean up the GUI DB and start the wizard setup again.
|
When creating additional file systems in a tiered storage environment you might encounter a
MIGRATION callback error.
mmaddcallback: Callback identifier "MIGRATION" already exists or was specified multiple times.
If
a callback exists, file system creation will fail.
- ESS 3000
- ESS 3200
- ESS 5000
- ESS 3500
- ESS 3500 (4u102)
|
Delete the callback and create the file system again.
|
Many call home events for temperature sensor causes canister1_inlet_id1
failure.TS008179389 2022-08-05 02:16:50 New Case Opened 78E4007:canister:78E4007A/1:canister1_inlet_id1:Temperature sensor canister1_inlet_id1 is failed
TS008179399 2022-08-05 03:14:19 New Case Opened 78E4007:canister:78E4007A/1:canister1_inlet_id1:Temperature sensor canister1_inlet_id1 is failed
TS008179432 2022-08-05 07:15:33 New Case Opened 78E4007:canister:78E4007B/0:canister2_inlet_id0:Temperature sensor canister2_inlet_id0 is failed
|
- If this issue occurs in field, turn up the AC to cool ambient temperature.
- If this issue occurs, customers/CE must lower ambient lab temperature.
|
| Both ESS 3500 power supplies blink red-orange LED once every second during the I/O
load.
|
If this problem occurs, reseat the power supply. |
| The essrun ONLINE update failed on the mmchfirmware -N
localhost --type drive.
|
SSR and customers must manually run the mmchfirmware command after the
deployment completes. |