Date: Thu, 27 Feb 2020 12:42:58 +0000 From: bugzilla-noreply@freebsd.org To: scsi@FreeBSD.org Subject: [Bug 225666] WDC WDS120G2G0A-00JH30 SSD need quirks=0x3<4K,NCQ_TRIM_BROKEN> Message-ID: <bug-225666-5313-fs2cIjkXoI@https.bugs.freebsd.org/bugzilla/> In-Reply-To: <bug-225666-5313@https.bugs.freebsd.org/bugzilla/> References: <bug-225666-5313@https.bugs.freebsd.org/bugzilla/>
next in thread | previous in thread | raw e-mail | index | archive | help
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=3D225666 --- Comment #6 from Mario Olofo <mario.olofo@gmail.com> --- Yes, I had this data corruption a while ago, so I tried to get help on the forums, but no luck. The link is https://forums.freebsd.org/threads/fixing-metadata-errors-after-zfs-clear-z= fs-scrub.72139/ So some days ago I again got time to try installing FreeBSD again so I send= an email to freebsd-stable lists, but besides the very good support from the people, didn't found a solution so far, but tested some things: 1- Installed FBSD on a hybrid HDD, worked without errors; 2- Did a memory test from Windows and the dell diagnostics tool, no errors found; 3- Installed on the SSD and after install, reboot and download some tools (= npm, node, git), the zpool scrub already show me checksum errors. 4- Reinstalled and this time just applied the patch and build the kernel. D= id a reboot, the quirks detected was 0x03 (from 0x0D that it detected previously= ), so I downloaded the same tools, did a git clone of one of my projects, npm install to get a lot of little files on node_modules and then after this I = ran the zpool scrub. The scrub found data errors. I think that enabling the bit= 4k just delays the problem, at least in my case. --=20 You are receiving this mail because: You are the assignee for the bug.=
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?bug-225666-5313-fs2cIjkXoI>