JorgeB

Moderators
  • Posts

    60000
  • Joined

  • Last visited

  • Days Won

    627

Everything posted by JorgeB

  1. You can copy the VM to the array, then copy back with cp --sparse=always, that will "re-sparsify" the vdisk, then do the changes.
  2. No. You need to trim de vdisk by running Windows defrag, after making that change, trimming the SSD won't do anything.
  3. Constant ATA errors from disk3, replace cables and post new diags.
  4. You can rename the *.plg files, then reboot, to reinstall rename back.
  5. If it doesn't crash in safe mode with the same containers running it could be a plugin.
  6. This may help https://forums.unraid.net/topic/51703-vm-faq/?do=findComment&comment=557606
  7. Correct. It should help, as long as compatible, using a different brand board where it would work in the GPU slot would also solve the issue. Yep.
  8. See if Windows is set to sleep/hibernate after a while.
  9. Then unmount should not complete until all data in RAM is written to the device, you also invoke a sync command before the unmount, then it should unmount immediately.
  10. Disk/exclusive shares will generally perform noticeably better, so if possible for your use case, use them.
  11. Possibly some board compatibility issue with the HBA, probably not much else you can do other than using a different one if available.
  12. Mar 17 16:51:02 Tower smbd[29090]: streams_xattr_pwrite: Write to xattr [user.DosStream.Timing.Info:$DATA] on file [NYG GB.ts] exceeds maximum supported extended attribute size. Depending on filesystem type and operating system (OS) specifics, this value may be increased using the value of the parameter: smbd max xattr size = <bytes>. Consult OS and filesystem manpages prior to increasing this limit. Not sure the max XFS supports, maybe @dlandonknows.
  13. OK, the x4 is normal, not normal only linking at PCIe 1.0, check the bard BIOS to see if the PICe slot link is limited.
  14. It's only linking at PCIe 1.0 speeds, and also only x4, what is the board model and slot where it is installed?
  15. If you have issues with two different filesystems it suggests to me a hardware problem, start by running memtest, if no errors are found try using just one stick of RAM, if the same try the other one, that will basically rule out a RAM issue.
  16. The card is capable of 12Gbps per port, that's 1200MB/s (with SAS3 devices, it will be 6Gbps per port with SATA max). also 1.5GB/s not the same as 1.5Gbps Likely the HBA is not linking at full speed/width, post the output of: lspci -d 1000: -vv
  17. I do, the only clue you get for now when a pool device drops, is that is stops showing the temp.
  18. Nothing suggesting a disk problem so far, only a filesystem issue, probably as a result of the previously failed disk, check filesystem on disk2, run it without -n, and if it asks for -L use it.
  19. Since the device dropped offline there's no SMART, you need to reconnect the device to get that again.
  20. Same issue, one of your devices dropped offline, Unraid does not currently monitor pool devices, it's an old feature request of mine, for now you see here for better pool monitoring.
  21. Do you see the same after booting in safe mode?
  22. Is this with a user share or disk/exclusive share?
  23. This is a very bad idea. Unraid requires a specific partition layout, since you extended the array and not the partition it's complaining, it *may* work if you create a new partition using the new capacity, but I have no way of testing.