hththt

Members
  • Posts

    10
  • Joined

  • Last visited

Everything posted by hththt

  1. I'm having some issue where I would like to mount a Remote SMB (from my Synology) so I can set up some rclone scripts to do backup but I don't want this mount to be shared by Unraid (since it's already shared by Synology). I thought this was possible since it was mentioned in the first page but I can't seem to find the mentioned 'Share' switch. Your help is much appreciated. Thank you!
  2. Winner winner chicken dinner root@nas:~# fstrim -v /mnt/disks/Samsung_SSD_860_EVO_2TB_S597NJ0MC06295J /mnt/disks/Samsung_SSD_860_EVO_2TB_S597NJ0MC06295J: 1.8 TiB (1999323762688 bytes) trimmed So I would say avoid the 4TB for now. Odd though since the only difference between the 2TB model and the 4TB model is the amount of LPDDR4 DRAM. I wonder if it has anything to do with the block size (like 512b vs 4k on > 2TB HDDs). I sort of want to try another 4TB drive. The reason why I went with the 860 EVO was because of the endurance rating. If you guys know another 4TB drive that would TRIM fine and has decent endurance rating, please let me know. Thanks!
  3. I tried with the fw the SSD came with (whichever that was) and then booted into Windows to upgrade to the latest (RVT04B6Q) and got the errors either times. I should have a 860 EVO 2TB tomorrow to try. I will report back.
  4. That's possible. But I think if it was mobo-related, it would be at least a combination of the mobo (the Intel SATA controllers) and the SSD since as mentioned in the original post, I was able to run TRIM on an old Crucial M4 SSD 512GB just fine.
  5. I got a hold of another 860 EVO 4TB, formatted to btrfs and mounted it under UD. But I got the same error as the other drive. At this point, I believe that there is probably something with the 4TB model of this drive. I will see if I can get my hand on a 2TB model and try again. Just wanted to circle back in case someone runs into the same issue in the future root@nas:~# fstrim -v /mnt/disks/Samsung_SSD_860_EVO_4TB_S596NE0MA02175A fstrim: /mnt/disks/Samsung_SSD_860_EVO_4TB_S596NE0MA02175A: the discard operation is not supported
  6. I actually ran and checked that DisableDeleteNotify command when I booted into Windows to run Samsung Magician and TRIM was enabled from Windows perspective. I was wondering how to check if it’s being trimmed successfully but as you mentioned, no easy way to do this. Also Windows can’t mount btrfs as is. I will probably try to get a hold of another 4TB from a different source and see if it’s this specific drive. I will report back but in the meantime, if there’s anything else you guys can think of, I can give it a try. Thank you for your help thus far.
  7. Hi johnnie.black, Thank you for your reply. I just tried connecting the SSD to the backplane so that it goes through the SAS3008 and yeap as you suspected, same error. At this point, I’m inclined to say there is something wrong with either this drive or with the 4TB model in general. Is there a way to verify whether TRIM works in Windows? Since I can boot into Windows on this same box, I can try to verify if it works on Windows.
  8. Hi Squid, Yeap. Positive. The Samsung SSD cache drive is hooked up directly to one of the onboard SATA ports. Only my 12 spinning HDDs are hooked up to the SAS3 backplane and then to a 9300-8i controller.
  9. Hi, I'm new to Unraid. I have read up a lot on it over the past 2 months and took the plunge to migrate my Windows Home Server 2011 over to Unraid. It's great to be a part of the community here. I have a Samsung 860 EVO I use for my cache drive. I installed Dynamix TRIM plugin to get this trimmed at 3AM everyday, but I kept getting the error: fstrim: /mnt/cache: the discard operation is not supported I got this same error when running via the Terminal. root@nas:~# fstrim /mnt/cache fstrim: /mnt/cache: the discard operation is not supported I checked to make sure the drive supports TRIM root@nas:~# hdparm -I /dev/sdb 2>&1 | grep TRIM * Data Set Management TRIM supported (limit 8 blocks) * Deterministic read ZEROs after TRIM I have been trying to troubleshoot this over the past 2 weeks with no success. I'm hoping you guys can point me to what to try next. My setup: Mobo: Supermicro X10DRi-T with Intel C612 SSD drive: Samsung 860 EVO 4TB 2.5" SATA SSD Connection method: Onboard SATA ports Unraid version: 6.8.2 Things I have tried (running the TRIM command via the Terminal manually for each of the below): 1. This mobo has 10 SATA ports: 4 I-SATA ports, 2 DOM I-SATA ports and 4 S-SATA ports. From looking at the mobo manual, all SATA ports are connected to Intel SATA controllers. I have tried 1 of each variant and got the same error. 2. I tried different SATA cables and got the same error. 3. I stopped the array, mounted the drive via Unassigned Device and for the same error: root@nas:~# fstrim -v /mnt/disks/Samsung_SSD_860_EVO_4TB_S4WUNE0M802047R fstrim: /mnt/disks/Samsung_SSD_860_EVO_4TB_S4WUNE0M802047R: the discard operation is not supported 4. I tried an old SSD I have on hand and this one seemed to work: root@nas:~# fstrim -v /mnt/disks/M4-CT512M4SSD1_0000000012330912F659-part2 /mnt/disks/M4-CT512M4SSD1_0000000012330912F659-part2: 68.8 MiB (72119296 bytes) trimmed root@nas:~# fstrim -v /mnt/disks/M4-CT512M4SSD1_0000000012330912F659-part4 /mnt/disks/M4-CT512M4SSD1_0000000012330912F659-part4: 306.7 GiB (329315692544 bytes) trimmed 5. I booted into Windows and installed Samsung Magician on the spare SSD I have above and the Samsung drive appears to be genuine and has the latest firmware. I attached my diagnostic to this post. I hope I am not missing something obvious. If I am, please pardon my ignorance and I appreciate you guys pointing me in the right direction. I think this means that for some odd reason, this Samsung drive does not support TRIM? Which is weird since it's a very popular drive. Please let me know what you think. Thanks! nas-diagnostics-20200210-1925.zip