IPMCTL-DELETE-PCD(1)

💖 IPMCTL-DELETE-PCD 💖

okay bestie, welcome to the manual page for ipmctl-delete-pcd, straight out of the ipmctl family 💅 it's the one that clears select partition data from the PCD. yes, PCD. we love a four-letter acronym in this house. 🎀

---

✨ NAME ✨

ipmctl-delete-pcd — clears select partition data from the PCD. that's the whole vibe. that's the job. 🫶

---

🌈 SYNOPSIS 🌈

ipmctl delete [OPTIONS] -pcd [TARGETS]

---

🦋 DESCRIPTION 🦋

So here's the tea, bestie. When Config is specified, the Current, Input, and Output Data Size and Start Offset values in the Configuration header get set to zero, which makes those tables invalid. bye tables, we hardly knew ye. 😭

Note: When Config is specified, only PCD partition 1 is modified. And if the platform gets rebooted before you create a new goal on any targeted PMem modules, UEFI platform firmware will detect the missing tables and — if it can — restore the previous config using the PCD partition 0 tables. so it might just undo your whole thing. iconic behaviour honestly. 🙈

Note: This action is lowkey perfect when you're moving PMem modules from one system to another, because goal creation rules may restrict provisioning PMem modules that already have a configuration. Deleting the PCD = a way to prep a PMem module for provisioning with the create -goal or load -goal commands by clearing out existing configuration metadata. That means the PMem module can be provisioned in isolation using the create-goal command with the -dimm option. And once the PCD has been deleted, you should create the desired goal before rebooting. periodt. 👑

Warning: This command may result in data loss. Data should be backed up to other storage before executing this command, fr fr. And because of data dependencies, other commands may be affected until the system has been rebooted. be careful out there. 💀

---

🎀 OPTIONS 🎀

• -f, -force — deleting the PCD data is a destructive operation, so it normally needs confirmation from the user for each PMem module. This option suppresses the confirmation. no take-backsies energy, bestie. ✨
• -h, -help — displays help for the command. our forever fave.
• -ddrt — used to specify DDRT as the desired transport protocol for the current invocation of ipmctl.
• -smbus — used to specify SMBUS as the desired transport protocol for the current invocation of ipmctl.

Note: The -ddrt and -smbus options are mutually exclusive and may not be used together. pick a lane. 🚫

• -lpmb — used to specify large transport payload size for the current invocation of ipmctl.
• -spmb — used to specify small transport payload size for the current invocation of ipmctl.

Note: The -lpmb and -spmb options are mutually exclusive and may not be used together. same rule, different flags. ✨

• -o (text|nvmxml), -output (text|nvmxml) — changes the output format. One of: "text" (default) or "nvmxml".

---

🌸 TARGETS 🌸

• -dimm [DimmIDs] — deletes the PCD data on specific PMem modules by supplying one or more comma separated PMem module identifiers. The default is to delete the PCD data for all manageable PMem modules. the whole squad. 🫶
• -pcd [Config] — clears the configuration management information.

---

⭐ EXAMPLES ⭐

Clears the Cin, Cout, Ccur tables from all manageable PMem modules:

delete -dimm -pcd Config

---

💜 LIMITATIONS 💜

The specified PMem modules must be manageable by the host software, and if data-at-rest security is enabled, the PMem modules must be unlocked. Any existing namespaces associated with the requested PMem modules should be deleted before running this command. like, clean up your room first. 🧹

---

🔥 RETURN DATA 🔥

For each PMem module, the CLI will indicate the status of the operation. And if a failure occurs when deleting the platform configuration data from multiple PMem modules, the process will continue deleting the remaining PMem modules. it does not abandon the rest of the group. 💪

---

k bye bestie 🦋 that was ipmctl from 2024-04-22 — go clear that PCD (after backing up, obviously!!). mwah. 💖🎀✨