I am getting a lot of these errors messages in the logs but there is no obvious reason why.
I have tried several tests already, including:
– rebooting
– rebooting into Safe Mode
– Running Disk Utility
– Running Disk Utility in Recovery Mode
– Running diagnostics
All tests come back OK.
Anyone else seeing this problem and found a resolution?
Does your computer have a traditional hard drive? If so you could run DriveDX to check the drive's health. I don't know how well DriveDX interprets SSD health though so you could post its report if you want although Apple SSDs don't have much useful information. Sometimes reviewing the "Health Indicators" (aka SMART Attributes) can identify a potential drive failure which is not being directly monitored by the app. To check external drives you need to install a special USB driver, but not all I/O boards on external drive adapters/enclosures support SMART communication pass through with the drive itself.
Keep in mind "disk I/O" errors can also be caused by a connected external device such as a phone, tablet, external drive, etc.
Does your computer have a traditional hard drive? If so you could run DriveDX to check the drive's health. I don't know how well DriveDX interprets SSD health though so you could post its report if you want although Apple SSDs don't have much useful information. Sometimes reviewing the "Health Indicators" (aka SMART Attributes) can identify a potential drive failure which is not being directly monitored by the app. To check external drives you need to install a special USB driver, but not all I/O boards on external drive adapters/enclosures support SMART communication pass through with the drive itself.
Keep in mind "disk I/O" errors can also be caused by a connected external device such as a phone, tablet, external drive, etc.
Ok, so my machine just crashed with the following trace:
Anonymous UUID: AD18ED7F-2C9B-8657-4055-24D1C36E6CA3
Wed May 29 10:33:42 2019
*** Panic Report ***
panic(cpu 0 caller 0xffffff7fa282fc0c): nvme: "Fatal error occurred. ID=0x8eb ARG1=0x1300200 ARG2=0x30003 ARG3=0x0 EDD0=0x10600000 EDD1=0x100000 EDD2=0x0 EDD3=0x1d400000 EDD4=0x765d0d00 EDD5=0x7e7e767e EDD6=0x18020205 EDD7=0x0 NANDV=0x1, DRAMV=0x2, SSDC=1024GB. FW Revision=14.17.01\n"@/BuildRoot/Library/Caches/com.apple.xbs/Sources/IONVMeFamily/IONVMeFamily-387.260.15/IONVMeController.cpp:5334
Backtrace (CPU 0), Frame : Return Address
0xffffff81ff7eba10 : 0xffffff801f5aea2d
0xffffff81ff7eba60 : 0xffffff801f6e9e95
0xffffff81ff7ebaa0 : 0xffffff801f6db70a
0xffffff81ff7ebb10 : 0xffffff801f55bb40
0xffffff81ff7ebb30 : 0xffffff801f5ae447
0xffffff81ff7ebc50 : 0xffffff801f5ae293
0xffffff81ff7ebcc0 : 0xffffff7fa282fc0c
0xffffff81ff7ebe20 : 0xffffff801fc5e877
0xffffff81ff7ebe90 : 0xffffff801fc5e799
0xffffff81ff7ebec0 : 0xffffff801f5ed9b5
0xffffff81ff7ebf40 : 0xffffff801f5ed555
0xffffff81ff7ebfa0 : 0xffffff801f55b0ce
Kernel Extensions in backtrace:
com.apple.iokit.IONVMeFamily(2.1)[FAFF8EA6-B8EF-314D-886A-DEAB39FF3EA9]@0xffffff7fa2822000->0xffffff7fa2861fff
dependency: com.apple.driver.AppleMobileFileIntegrity(1.0.5)[A367CF6B-B3EA-36FE-86E6-03B771CA8A69]@0xffffff7fa0388000
dependency: com.apple.iokit.IOPCIFamily(2.9)[CC6A465F-5A24-304D-B9DF-8C27819CC214]@0xffffff7f9fe95000
dependency: com.apple.driver.AppleEFINVRAM(2.1)[C3C74D36-E06B-3753-A373-5BC9D486DD9C]@0xffffff7fa055e000
dependency: com.apple.iokit.IOStorageFamily(2.1)[D43332F2-2D40-3DF1-8F77-D633BCDAE660]@0xffffff7fa017e000
dependency: com.apple.iokit.IOReportFamily(47)[5772C11C-ED28-322A-910F-874583B23101]@0xffffff7fa0a08000
BSD process name corresponding to current thread: kernel_task
Mac OS version:
18F132
Kernel version:
Darwin Kernel Version 18.6.0: Thu Apr 25 23:16:27 PDT 2019; root:xnu-4903.261.4~2/RELEASE_X86_64
Kernel UUID: 7C8BB636-E593-3CE4-8528-9BD24A688851
Kernel slide: 0x000000001f200000
Kernel text base: 0xffffff801f400000
__HIB text base: 0xffffff801f300000
System model name: MacBookPro13,2 (Mac-66E35819EE2D0D05)
...truncated...
Because the trace refers to IONVMeController I am assuming that it is actually a hardware error related to the NVMe SSD drive rather than a software error.
Looks like I am taking my machine into a Apple store after all.
Can you reply with some of the text from those logs messages?
Generally, disk I/O errors mean the hard drive is failing. This is not something that Disk Utility can fix.
Nothing else, but will keep an eye on events, and maintain an hourly backup for now.
If I take the machine into an Apple store and the diagnostics etc. all run Ok, what other evidence would I know to show there is a problem, any thoughts?
Thanks for the advice.
I don't normally go trawling for errors in Console, but I had an issue with a failed uninstall of a MySQL instance, and spotted the disk i/o error. And I don't use any "clean up" apps.
I agree with you about the usefulness of Console compared to what it used to tell you. The kind of information you now get about issues etc. are very sparse.
Hi,
The attached is what Console is telling me. The error only appears for this one service, and I have run a check in Diagnostics mode that has reported no errors (reference ADP00).
Diagnostics can only report errors. They cannot declare anything error-free.
It is possible that just one database for PerfPowerServices is corrupt. But the most likely explanation is that the hard drive is failing.
I suggest you back up the machine immediately.
Are you experiencing any other problems with the machine?
It is a bit difficult to say. If you aren’t having any problems, then there usually isn’t anything to worry about. Normally I try to encourage people not to look at the console log. It rarely has any useful information. On rare occasions, people get very confused and paranoid when they dig into it.
However, a disk I/O error is one of the few useful entries that the log might have. Apple re-wrote the entire logging system a couple of years ago and made it virtually useless. Used to, you could just scan the log file for any instances of “disk I/O error”. My app EtreCheck used to do just that. It still does, but the log file isn’t available to read anymore. These days, you need to be the administrator and run the new “log” program to see any historical log entries. It is very unusual to actually see anything useful in the Console app anymore.
EtreCheck looks for the string ": I/O error.” There would be a line in the log file that looked like:
17 Nov 2014 15:39:31 kernel[0]: disk0s2: I/O error.
And that would allow me to say that there definitely was an I/O failure reading the 2nd partition on the first hard disk, which is normally the boot partition. The error you see is slightly different. Considering how much the console app and logging system have been changed, I don’t know if that error really means anything.
If you aren’t experiencing errors, don’t go looking for them. I don’t know anything about your machine. Maybe you have run one of those “clean up” apps and it has corrupted this file.
Its a 1Tb SSD (Apple supplied) so a NVMe-based drive. I cloned the disk over the weekend and I'm taking regular backups via TM so hopefully I'm reasonably covered in the event of another problem. Will have to wait and see.
Thanks for your help.
Console showing PerfPowerServices disk I/O errors
