
I changed the hard drive in the machine along the way (from a 1 TB HD to a 1 TB SSD) and have also tested this while booting from an external drive. I have turned off Spotlight for the RAID, so Spotlight is not writing indexes to the RAID (this helped early troubleshooting immeasurably).
Kernel trap if I left the RAID drives plugged on during boot). IOGMD if I boot, then plug in the RAID1, rebuild it (Disk Utility invariably rebuilds the mirror, a 1 week process) and then I initiate a copy (actually, this is probably independent of whether the rebuild finishes). I suspect these are related to whether the RAID is plugged in on boot: The memory addresses vary somewhat from report to report. Panic(cpu 0 caller 0xffffff80108aa81f): "IOGMD: not wired for the /iokit/Kernel/IOMemoryDescriptor.cpp:2324 Copying a small file seems to not be an issue (e.g. If I delete the RAID, I can format and copy to each the disks. About that time OS X notified me it had downloaded High Sierra and asked, would I like to update? Sure.Ģ2 KPs later, it seems that the KPs are caused by writes to the RAID 1 when the OS is High Sierra (both versions 17E199 and 17E202 show up in the. I built a RAID1 with matched 8TB USB disks (Seagate Expansion 8TB Desktop External Hard Drive USB 3.0 (STEB8000100)) under Sierra and copied about 360 GB to them.
Hello, I pulled out my old iMac 11,1 to set up a home server.