MigrationParityInit
What the point of no return (initializeMigrationParity) would do now, present in the verified phase (only a passing verify offers it) and in initializing. The screen and the command show unprotectedWindow and rollback before asking for confirmation.
True in initializing: the former parity and cache disks are already formatted and recorded, and running initializeMigrationParity with this confirmation finishes the rest and erases nothing.
The exact string initializeMigrationParity requires. Absent when problem is set.
erases object[]required
Every device the point of no return erases; empty when finishing.
Possible values: [parity, cache]
The device node, as it is named in confirmation.
True when only a partition of the device's disk is erased (the cache of an Unraid boot + data device, or a spare partition of the boot disk); the rest of that disk is left alone.
Why it cannot be offered now (a disk missing, swapped or not allowed, or no data disk with the pool's minfreespace free); no confirmation is given.
The unprotected window: the array has no redundancy from the moment Unraid's array stopped until the initial sync completes.
What rollback means once this is confirmed, for this session's boot mode and layout: the general statement first, then the row of the table that applies.
{
"finishing": true,
"confirmation": "string",
"erases": [
{
"role": "parity",
"device": "string",
"serial": "string",
"wwn": "string",
"size": 0,
"partition": true
}
],
"problem": "string",
"unprotectedWindow": "string",
"rollback": [
"string"
]
}