https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=239801
Hiroki Sato <h...@freebsd.org> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|Open |In Progress --- Comment #5 from Hiroki Sato <h...@freebsd.org> --- (In reply to Daniel Mafua from comment #4) Thanks for your report. I have several other systems which are suffering from the same problem. Here is information about this problem which I got so far: * mfi(4) can report I/O errors which is not related to an actual hardware failure after upgrading FreeBSD to 11.3 or 12.0. * The error does not depend on ZFS while ZFS is very likely to report checksum errors of the zpool. On a system using UFS, the I/O error can cause a system panic, boot failure, or something fatal. * It seems that the I/O error depends on a specific firmware version. Some older firmware versions work fine even with mfi(4) on 11.3 and 12.0. * If the device is also supported by mrsas(4), switching to it will solves the error. Note that it will cause an incompatibility issue---mfi(4) uses /dev/mfi* device nodes for the attached drives and mfiutil(8) as the userland utility. mrsas(4) uses /dev/da* and a vendor-supplied utility such as megaCli instead. I am investigating what caused this regression but a workaround is to use mrsas(4) instead of mfi(4) by specifying hw.mfi.mrsas_enable="1" at boot time. -- You are receiving this mail because: You are the assignee for the bug. _______________________________________________ freebsd-bugs@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-bugs To unsubscribe, send any mail to "freebsd-bugs-unsubscr...@freebsd.org"