https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=229745
--- Comment #51 from Wayne Willcox <wwillc...@gmail.com> --- Ok have some new information in my case. I commented out from /boot/loader.conf #vfs.zfs.cache_flush_disable="1" I commented out from /boot/device.hints #hint.ahcich.0.sata_rev=2 so that I was back to the standard defaults. Backed up the New WD Blue drive model WD30EZRZ using rsnapshot installed the same FreeBSD 12.1 on a New WD RED drive: ada0 at ahcich4 bus 0 scbus4 target 0 lun 0 ada0: <WDC WD30EFRX-68EUZN0 82.00A82> ACS-2 ATA SATA 3.x device ada0: Serial Number WD-WCC4N3SJU005 ada0: 600.000MB/s transfers (SATA 3.x, UDMA6, PIO 8192bytes) ada0: Command Queueing enabled ada0: 2861588MB (5860533168 512 byte sectors) ada0: quirks=0x1<4K> restored the snapshot I created from the Blue drive onto the Red drive and rebooted. Let it run off the Red drive and for the first time it successfully ran overnight without disabling /zroot. It didn't log any timeout errors and the work load was the same. So 2 new WD Blue drives had this problem and just switching to a new WD Red seems to have resolved the problem. I intend to monitor the Red drive and see if it continues to behave properly (I expect it will I have a lot of Red drives in service). Additionally I am going to do some more testing with these drives in a test rig. -- 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"
