For the past 3 weeks, I've been experiencing the weirdest issue while testing new hard drives with badblocks (using this wrapper script specifically: bht).
Specifically, when using either the TL-D800S or TL-D1600S with the MS-01, I experience a non-zero amount of verify errors on all my drives. These errors start appearing anywhere between 25% and 75% through the first read pass of the test. Below is a sample output:
Despite the verify errors reported by badblocks, smartctl shows no issues, and all smartctl self-tests pass without any problems (long, short, conveyance). Additionally, I couldn't find any dmesg or system logs directly correlated with these errors.
Initially, I thought I had just been unlucky with shipping damage, so I returned the first eight drives I tested (a mix of Ultrastar and Exos drives). However, I grew suspicious of the TL-D800S after experiencing the same issues with the second set of eight drives I received. Therefore, I switched to the TL-D1600S, but the badblocks errors persisted.
Before starting any of my tests, I made sure to check my RAM with Memtest86+ for over five passes, detecting zero errors. I'm currently using the 96GB kit (CT2K48G56C46S5), but switching to the 64GB kit didn't seem to make any difference in my badblocks tests (I have the 13900H version). Moreover, since I'm running Proxmox, I updated the Intel microcode as suggested by Craft Computing. I've tried disabling C-states with no success, but I haven't yet tried the new 1.22 BIOS.
Most recently, I decided to test the TL-D1600S and the drives connected to a PC with an AMD CPU, and so far, I have not seen the same badblocks errors. The test hasn't completed all four read/write passes yet (which takes around a week), but at least it has gotten past the first read/write pass.
Has anyone else experienced this issue with their MS-01 + QNAP jbod combo? I'm really confused as to what could be going on and I am at a loss as to how to debug further.
UPDATE:
I returned the Minisforum MS-01 and replaced it with a Lenovo Thinkstation P3 Ultra. The new setup is working without any issues, so it seems the problems I experienced were exclusive to the MS-01, rather than related to Big/Little, C-states, or Proxmox.
Specifically, when using either the TL-D800S or TL-D1600S with the MS-01, I experience a non-zero amount of verify errors on all my drives. These errors start appearing anywhere between 25% and 75% through the first read pass of the test. Below is a sample output:
Despite the verify errors reported by badblocks, smartctl shows no issues, and all smartctl self-tests pass without any problems (long, short, conveyance). Additionally, I couldn't find any dmesg or system logs directly correlated with these errors.
Initially, I thought I had just been unlucky with shipping damage, so I returned the first eight drives I tested (a mix of Ultrastar and Exos drives). However, I grew suspicious of the TL-D800S after experiencing the same issues with the second set of eight drives I received. Therefore, I switched to the TL-D1600S, but the badblocks errors persisted.
Before starting any of my tests, I made sure to check my RAM with Memtest86+ for over five passes, detecting zero errors. I'm currently using the 96GB kit (CT2K48G56C46S5), but switching to the 64GB kit didn't seem to make any difference in my badblocks tests (I have the 13900H version). Moreover, since I'm running Proxmox, I updated the Intel microcode as suggested by Craft Computing. I've tried disabling C-states with no success, but I haven't yet tried the new 1.22 BIOS.
Most recently, I decided to test the TL-D1600S and the drives connected to a PC with an AMD CPU, and so far, I have not seen the same badblocks errors. The test hasn't completed all four read/write passes yet (which takes around a week), but at least it has gotten past the first read/write pass.
Has anyone else experienced this issue with their MS-01 + QNAP jbod combo? I'm really confused as to what could be going on and I am at a loss as to how to debug further.
UPDATE:
I returned the Minisforum MS-01 and replaced it with a Lenovo Thinkstation P3 Ultra. The new setup is working without any issues, so it seems the problems I experienced were exclusive to the MS-01, rather than related to Big/Little, C-states, or Proxmox.
Last edited:
