MigrationChecklist
Whether the array record carries the time its migration's point of no return finished, which nothing but that step writes. False for a migration that is pending, part-way through, or was undone; then the checklist does not apply and items is empty.
That time; present exactly when finished is true.
items object[]required
In the order of the migration's steps.
Possible values: [appdata_cache, initial_sync, full_scrub, notifications, schedules, user_scripts, restore_drill]
Possible values: [todo, done, not_applicable]
True only for user_scripts and restore_drill while they are not acknowledged. An item with a record is never acknowledgeable.
When the record says it was done, or when it was acknowledged.
The job the item derives from. For restore_drill, the latest succeeded fix job that had a path (startFix), which an acknowledgement records. A fix of the whole array or of one disk is not a restore drill and is not shown.
Who acknowledged it, local for the daemon's own socket.
notifications object
How many notification channels exist.
How many are enabled and have a test that succeeded since they last changed.
The names of the Unraid notification agents the scan found, never anything inside them: recreate each as a channel.
schedules object
Whether the nightly chain's mover step is enabled.
Whether the nightly chain's sync step is enabled. Unraid has no sync schedule to carry over, so the user chooses one.
Whether the nightly chain's scrub step is enabled.
Local time the chain starts, HH:MM.
Day of week, 0=Sunday through 6=Saturday.
Possible values: >= 0 and <= 6
offers objectrequired
Values read from Unraid's configuration that the schedules item offers to carry over. A value the flash did not have is absent, never an "off".
Unraid's mover schedule, as written.
HH:MM when the mover schedule is a daily line, offered as the nightly chain's start time.
parityCheck object
Unraid's parity-check schedule as dynamix.cfg wrote it, offered as the scrub schedule.
True when Unraid's parity check wrote no corrections, which maps to a scrub that only reports.
Unraid's global spin-down delay, offered as the default.
scripts object[]
The User Scripts the scan found, on user_scripts only. Empty when the scan found none or could not say; the report's User Scripts row tells which.
The schedule the plugin's customSchedule.cron gives it, absent when it has none there.
{
"finished": true,
"finishedAt": "2024-07-29T15:51:28.071Z",
"items": [
{
"id": "appdata_cache",
"status": "todo",
"acknowledgeable": true,
"doneAt": "2024-07-29T15:51:28.071Z",
"jobId": "string",
"acknowledgedBy": "string",
"acknowledgedAt": "2024-07-29T15:51:28.071Z",
"notifications": {
"channels": 0,
"tested": 0,
"agents": [
"string"
]
},
"schedules": {
"mover": true,
"sync": true,
"scrub": true,
"chainStartTime": "string",
"weeklyScrubDay": 0,
"offers": {
"moverCron": "string",
"moverTime": "string",
"parityCheck": {
"mode": "string",
"hour": "string",
"dayOfMonth": "string",
"day": "string",
"month": "string",
"frequency": "string",
"correcting": true
},
"scrubReportOnly": true,
"spindownDelay": "string"
}
},
"scripts": [
{
"name": "string",
"schedule": "string"
}
]
}
]
}