Diagnose a SUSE Server That Hangs at the systemd Shutdown Screen
Use systemd jobs and the previous boot journal to locate a slow service, mount, or storage dependency, then correct it without masking the cause.
The Fitness app on iOS 18 has added some new customizations such as you can change the Summary page of the Fitness app, add the necessary cards to the summary page according to your usage needs. Thus, users can customize the Fitness app on iPhone to their liking. Below are detailed instructions for changing the Fitness app on iPhone.
How to Customize the Fitness App on iPhone
Step 1:
On the interface of the Fitness application, scroll down and select Edit Summary . Now we can change the existing cards on the Summary page.

You can delete any cards you don't need by clicking the - sign or change the display order by moving the cards according to your needs.
Step 2:
If you want to add another management card, click the Add button in the top left corner of the interface. Now you will see other cards to choose from to add to the Summary page. Scroll down to see all the other cards and choose which card you want to use.
Step 3:
When you tap on a card it will show the card's contents as shown below. We will look at the different cards and tap Add Card to add it to the Summary page in the Fitness app.
Step 4:
The new card will then appear on the Summary page above and you can change the display order according to your needs. Finally, click Done in the upper right corner to save the changes.
Use systemd jobs and the previous boot journal to locate a slow service, mount, or storage dependency, then correct it without masking the cause.
Use firewall-cmd to inspect the active zone, allow HTTP safely, preserve SSH access, and verify that the rule survives a reload on SLES 15.
Trace a PAM failure to its service, account policy, or identity provider, then repair the right SLES configuration while preserving a working admin session.
Trace a failed kernel module at SLES startup, correct an obsolete boot entry or repair the required driver, and verify the next boot.
Prepare SCSI SAN paths, enable multipathd, inspect SUSE’s hardware defaults, and verify stable device maps without guessing array settings.
Find the process holding Zypper’s package lock, distinguish process conflicts from package locks, and retry updates without deleting lock files blindly.
Register SLE HA, bootstrap SLES 15 nodes, then add fencing, quorum, and tested service resources before relying on failover.
Trace a Zypper refresh error to SUSE, RMT, or a third-party endpoint, then apply the right server-side or cache fix without disabling essential updates.
Resolve SUSE LVM thin-pool space errors by checking data and metadata usage, expanding the pool safely, and preventing repeat outages.
Identify whether Btrfs is intentionally read-only, short on space, or protecting data after errors, then choose a recovery path that fits the cause.








