Related: sysdiagnose and related approaches to gathering information
For reference only, here's a shortlist of sysdiagnose-related feedback to Apple. A few of the items are ZFS-related.
Most details were lost a few months ago (my bad) when a hard disk failed without comprehensive backups, hence the gaps below. I might fill the gaps at some point in the future but in the meantime, the titles alone are fairly self-explanatory.
----
process-specific things should run earlier in the sysdiagnose routine
sysdiagnose should run allmemory – typically the longest part of its routine – later, or last
… because running allmemory before spindump may take so long that when spindump time is reached, there's no longer value in gathering process-specific data …
if any partition type is ZFS, then sysdiagnose should run zpool status -xv -T d
…
if any partition type is ZFS, then sysdiagnose should run zfs list, then for each listed filesystem zfs get all
…
if any partition type is ZFS, then sysdiagnose should try zstat
…
sysdiagnose seems unable to move on in troublesome environments
…
if sysdiagnose is used with option -f then allmemory should use the same path for transient subdirectory allmemoryDataFiles and for allmemoryData.amdata
…
nvram -p enhancement to the sysdiagnose script
Within the script,
/usr/bin/sysdiagnose
I see nothing relating to NVRAM.
Results of script might be improved with use of:
nvram -p
Maybe also option -x for XML. Whatever will be most useful for diagnoses.