Date: Sun, 17 Mar 2024 08:03:44 -0400 From: mike tancsa <mike@sentex.net> To: Andrea Venturoli <ml@netfence.it> Cc: freebsd-hardware@freebsd.org Subject: Re: WD Blue 510 SSD and strange write performance Message-ID: <00cf68fe-73e2-4d28-bb49-6aad7eeaf884@sentex.net> In-Reply-To: <27933f54-2959-4071-b084-d796a7c3ae75@netfence.it> References: <e5c2a99d-931e-48b4-9445-fc4ad05ccc70@sentex.net> <CCAB653B-4DC6-4C69-AB68-CD258200D22F@gid.co.uk> <6504bd49-eca5-4e0a-b2bd-23d29405bb7a@sentex.net> <4832DE6A-5C82-4805-99BB-220D4342AE0F@fjl.co.uk> <69e47494-01aa-4149-a326-91d82dfdc46e@sentex.net> <C6B95542-AB00-4689-9918-738108C4F8FB@fjl.co.uk> <e02f55c5-947e-4650-b711-78f1e3004b50@sentex.net> <27933f54-2959-4071-b084-d796a7c3ae75@netfence.it>
next in thread | previous in thread | raw e-mail | index | archive | help
This is a multi-part message in MIME format. --------------CnN0rO33ICebgnjizmMEUWHh Content-Type: text/plain; charset=UTF-8; format=flowed Content-Transfer-Encoding: 8bit On 3/17/2024 4:32 AM, Andrea Venturoli wrote: > On 3/15/24 19:17, mike tancsa wrote: > >> (da5:mpr0:0:15:0): SCSI sense: UNIT ATTENTION asc:29,0 (Power on, >> reset, or bus device reset occurred) > > Hello. > I know I'm probably blaming the wrong component, but is your PSU up to > the task? > How many drives do you have? Are they power-hungrier than the others > you tried (Samsung ???)? > Do you have a spare PSU to test/add? > > Probably this is not the cause... still, before you bit farewell to > 400 bucks... > hehe, thanks Andrea :) I too dont want to be out the money. Power supply for sure is a good thing to check. In this case, the main server chassis is sized with a couple of redundant 1000W power supplies that should handle 12 full HDDs. Pretty sure in this case 6 SSDs should not stress it beyond the point. But I had 2 other test boxes on the bench and the one common variable seems to be the WDs. I feel like this is a sunk cost I am pushing myself into, but I did do some more testing. My co-worker came across this post which was interesting. https://forum.hddguru.com/viewtopic.php?f=10&t=43284 The very last entry says "For WD BLUE SA 510 there are some problems with this type of SSD. This YODA model To fix the SSD if it is still recognized, use the firmware update tools. And then do a secure erase or full wipe of the SSD. After this it will work well. I can give you a link to this utility if it necessary. Also ossible download it from manufacture FTP. If it is not recognized by the computer or is identified as a SSD device, there only one way, use production tools with new firmware to begin the production process by testing the controller and NAND chip and forming a translator. The SSD will be like brand new. " After I did the erase, the tests worked for a good 5 cycles and performance was MUCH smoother and consistent. But then the drives started to fail again. So I really wonder if TRIM has something to do with it as my test is essentially writing a 250G data set with about 28 million txt files, destroying the dataset and then copying it again. I noticed these 2 commits for other drives. I wonder if the WD is having similar issues. https://cgit.freebsd.org/src/commit/?h=stable/14&id=bf11fee6a5cf97102f87695185cadb63d5a2a7de and https://cgit.freebsd.org/src/commit/?h=stable/14&id=50aa22323424ccea00ef5d8f24e729a480cc77eb I hope you dont mind bcc'ing you Andriy. I noticed you only added the NCQ quirks for CAM ata and not for CAM scsi. I am running into odd issues with some WD drives and wondering if there is the same root limitation of these WD SA 510 drives like the Samsungs ? However, in my use of the Samsungs I have not been able to trigger these bugs so far. ---Mike --------------CnN0rO33ICebgnjizmMEUWHh Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: 8bit <!DOCTYPE html> <html> <head> <meta http-equiv="Content-Type" content="text/html; charset=UTF-8"> </head> <body> <div class="moz-cite-prefix">On 3/17/2024 4:32 AM, Andrea Venturoli wrote:<br> </div> <blockquote type="cite" cite="mid:27933f54-2959-4071-b084-d796a7c3ae75@netfence.it">On 3/15/24 19:17, mike tancsa wrote: <br> <br> <blockquote type="cite">(da5:mpr0:0:15:0): SCSI sense: UNIT ATTENTION asc:29,0 (Power on, reset, or bus device reset occurred) <br> </blockquote> <br> Hello. <br> I know I'm probably blaming the wrong component, but is your PSU up to the task? <br> How many drives do you have? Are they power-hungrier than the others you tried (Samsung ???)? <br> Do you have a spare PSU to test/add? <br> <br> Probably this is not the cause... still, before you bit farewell to 400 bucks... <br> <br> </blockquote> <p><br> </p> <p>hehe, thanks Andrea :) I too dont want to be out the money. Power supply for sure is a good thing to check. In this case, the main server chassis is sized with a couple of redundant 1000W power supplies that should handle 12 full HDDs. Pretty sure in this case 6 SSDs should not stress it beyond the point. But I had 2 other test boxes on the bench and the one common variable seems to be the WDs. <br> </p> <p>I feel like this is a sunk cost I am pushing myself into, but I did do some more testing. My co-worker came across this post which was interesting. <br> </p> <p><a class="moz-txt-link-freetext" href="https://forum.hddguru.com/viewtopic.php?f=10&t=43284">https://forum.hddguru.com/viewtopic.php?f=10&t=43284</a></p>; <p>The very last entry says <br> </p> <p>"<span style="color: rgb(0, 0, 0); font-family: Verdana, Tahoma, Helvetica, Arial, "lucida grande", "trebuchet ms", sans-serif; font-size: 13px; font-style: normal; font-variant-ligatures: normal; font-variant-caps: normal; font-weight: 400; letter-spacing: normal; orphans: 2; text-align: start; text-indent: 0px; text-transform: none; widows: 2; word-spacing: 0px; -webkit-text-stroke-width: 0px; white-space: normal; background-color: rgb(236, 236, 236); text-decoration-thickness: initial; text-decoration-style: initial; text-decoration-color: initial; display: inline !important; float: none;">For WD BLUE SA 510 there are some problems with this type of SSD. This YODA model</span><br style="margin: 0px; padding: 0px; color: rgb(0, 0, 0); font-family: Verdana, Tahoma, Helvetica, Arial, "lucida grande", "trebuchet ms", sans-serif; font-size: 13px; font-style: normal; font-variant-ligatures: normal; font-variant-caps: normal; font-weight: 400; letter-spacing: normal; orphans: 2; text-align: start; text-indent: 0px; text-transform: none; widows: 2; word-spacing: 0px; -webkit-text-stroke-width: 0px; white-space: normal; background-color: rgb(236, 236, 236); text-decoration-thickness: initial; text-decoration-style: initial; text-decoration-color: initial;"> <span style="color: rgb(0, 0, 0); font-family: Verdana, Tahoma, Helvetica, Arial, "lucida grande", "trebuchet ms", sans-serif; font-size: 13px; font-style: normal; font-variant-ligatures: normal; font-variant-caps: normal; font-weight: 400; letter-spacing: normal; orphans: 2; text-align: start; text-indent: 0px; text-transform: none; widows: 2; word-spacing: 0px; -webkit-text-stroke-width: 0px; white-space: normal; background-color: rgb(236, 236, 236); text-decoration-thickness: initial; text-decoration-style: initial; text-decoration-color: initial; display: inline !important; float: none;">To fix the SSD if it is still recognized, use the firmware update tools.<br> </span><span style="color: rgb(0, 0, 0); font-family: Verdana, Tahoma, Helvetica, Arial, "lucida grande", "trebuchet ms", sans-serif; font-size: 13px; font-style: normal; font-variant-ligatures: normal; font-variant-caps: normal; font-weight: 400; letter-spacing: normal; orphans: 2; text-align: start; text-indent: 0px; text-transform: none; widows: 2; word-spacing: 0px; -webkit-text-stroke-width: 0px; white-space: normal; background-color: rgb(236, 236, 236); text-decoration-thickness: initial; text-decoration-style: initial; text-decoration-color: initial; display: inline !important; float: none;">And then do a secure erase or full wipe of the SSD. After this it will work well. I can give you a link to this utility if it necessary. Also ossible download it from manufacture FTP.</span><br style="margin: 0px; padding: 0px; color: rgb(0, 0, 0); font-family: Verdana, Tahoma, Helvetica, Arial, "lucida grande", "trebuchet ms", sans-serif; font-size: 13px; font-style: normal; font-variant-ligatures: normal; font-variant-caps: normal; font-weight: 400; letter-spacing: normal; orphans: 2; text-align: start; text-indent: 0px; text-transform: none; widows: 2; word-spacing: 0px; -webkit-text-stroke-width: 0px; white-space: normal; background-color: rgb(236, 236, 236); text-decoration-thickness: initial; text-decoration-style: initial; text-decoration-color: initial;"> <span style="color: rgb(0, 0, 0); font-family: Verdana, Tahoma, Helvetica, Arial, "lucida grande", "trebuchet ms", sans-serif; font-size: 13px; font-style: normal; font-variant-ligatures: normal; font-variant-caps: normal; font-weight: 400; letter-spacing: normal; orphans: 2; text-align: start; text-indent: 0px; text-transform: none; widows: 2; word-spacing: 0px; -webkit-text-stroke-width: 0px; white-space: normal; background-color: rgb(236, 236, 236); text-decoration-thickness: initial; text-decoration-style: initial; text-decoration-color: initial; display: inline !important; float: none;">If it is not recognized by the computer or is identified as a SSD device, there only one way, use production tools with new firmware to begin the production process by testing the controller and NAND chip and forming a translator. The SSD will be like brand new.<br> "<br> </span></p> <p>After I did the erase, the tests worked for a good 5 cycles and performance was MUCH smoother and consistent. But then the drives started to fail again. So I really wonder if TRIM has something to do with it as my test is essentially writing a 250G data set with about 28 million txt files, destroying the dataset and then copying it again.</p> <p>I noticed these 2 commits for other drives. I wonder if the WD is having similar issues. <br> </p> <p><a class="moz-txt-link-freetext" href="https://cgit.freebsd.org/src/commit/?h=stable/14&id=bf11fee6a5cf97102f87695185cadb63d5a2a7de">https://cgit.freebsd.org/src/commit/?h=stable/14&id=bf11fee6a5cf97102f87695185cadb63d5a2a7de</a><br>; and<br> <a class="moz-txt-link-freetext" href="https://cgit.freebsd.org/src/commit/?h=stable/14&id=50aa22323424ccea00ef5d8f24e729a480cc77eb">https://cgit.freebsd.org/src/commit/?h=stable/14&id=50aa22323424ccea00ef5d8f24e729a480cc77eb</a><br>; </p> <p>I hope you dont mind bcc'ing you Andriy. I noticed you only added the NCQ quirks for CAM ata and not for CAM scsi. I am running into odd issues with some WD drives and wondering if there is the same root limitation of these WD SA 510 drives like the Samsungs ? However, in my use of the Samsungs I have not been able to trigger these bugs so far.</p> <p> ---Mike<br> </p> </body> </html> --------------CnN0rO33ICebgnjizmMEUWHh--
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?00cf68fe-73e2-4d28-bb49-6aad7eeaf884>