Marc_G2

Members
  • Content Count

    72
  • Joined

  • Last visited

Everything posted by Marc_G2

  1. v 6.8.3 After moving my unRAID over to a different motherboard I've encountered read errors which I might be the fault of my LSI expansion card. This is the second that resulted in a disk getting disabled. I originally though it had something to do with my UEFI boot setting since the first time happened right at start up. See topic below. This time, the server was running for a couple days before it randomly happened. Does anyone have an idea of what the issue is specifically? Is it the expansion card? Or could problem still be my HDD that got disabled? Before migrati
  2. This should not affect the spin down, is the USB device capable of spin down and also does it report that correctly, eventually this is the problem. I think half the issue is the UD plugin since I confirmed it didn't spin down the drive after 15 minutes. But apparently upgrading to 6.9.X (from 6.8.3) may fix the problem. So I will try that a little later
  3. Maybe it's my configuration? If my appdata folder is on the array, would a running docker keep it always active? For the USB drive, I have it enabled as a share. I'm wondering if that affects the UD plugin spin down behavior. My one other UD share is a SSD and it was active this morning as well. But I previously haven't payed any attention to whether it's label ever changes to spun down or not
  4. I recently used luckybackup for the first time where I'm backing up to a USB drive with the UD plugin. And I ran into a couple issues. 1) It appears luckybackup was keeping my array active (drives not spinning down) when not syncing anything. 2) The external USB drive never spins down even when not in use. Does someone know how I can address this?
  5. Okay I honestly think that boot mode setting was the cause. The array is working fine in emulation mode. I will work on fixing the disabled disk now
  6. Yeah I switched over to a different motherboard and everything seemed good initially. But Now I'm getting a read errors where one of disks automatically got disabled. I've attached diagnostics. I stopped the array which took a very long time. Advice on what went wrong and how to proceed would be greatly appreciated Edit: I rebooted the system to change a UEFI boot setting back to see if that caused an issue with my LSI sata expansion card. It seems like everything to card is having issues. nas-ng-diagnostics-20210417-1357.zip Update: S
  7. Diagnostics attached nas-ng-diagnostics-20210416-2054.zip
  8. So I have a USB DAC I want to use in my VM. Initially I tried passing just the device to the VM. But when playing audio I would periodically (like every 8 seconds) get these pop/crack sounds. I'm not sure if that's a good way describe it. If the audio playing is busy enough, the pop is subtle enough to be missed. After that, I tried using the USB PCIe card passed through to the VM. The result there was much better. But I'm stilling getting pops every 30 to 90 seconds. Updating the drivers didn't help. Changing USB cables didn't help. Ideally I'd use the optical output on my moth
  9. I'm not sure so I recommend using the command line method to dump the VBIOS. Also you may not actually need two GPUs as suggested. You might save yourself some hassle by restarting the system without any videos cables connected. https://www.youtube.com/watch?v=mM7ntkiUoPk
  10. I believe whether a GPU has a zero RPM mode for it's fans is governed by its VBIOS or firmware. Check if the OEM provides alternate firmware for it
  11. @zeus83 Thanks for letting us know. I'm now trying to get a 3080 to go with my new LG CX TV I ordered today because of a sale. I really wish I got into the EVGA queue earlier lol.
  12. You aren't using a VM are you? That wouldn't work with putting the whole system to sleep.
  13. It would be nice if we could have different excluded for each day of the week on the Sleep Plugin. Is there maybe a workaround to achieve this? Is there a command (after wakeup) I could execute where it would check the current day of the week and tell unraid to not sleep for the next X hours?
  14. Up until now, I've been using a modified of the S3 sleep plugin which was recommenced to me in the above post. The problem was the plugin wasn't reliably detecting when all drives were spun down. Does anyone know if the current version of the plugin, or unRAID 6.8+ resolved this issue?
  15. Thanks, I will give your version a try. I wish there was dedicated forum threads for each these plugins.
  16. So I'm still having a problem where S3 Sleep is erroneously detecting drive activity (and then not going to sleep). What is criteria for hard drive activity occurring? I assumed it was checking if the drives were spun up. But that doesn't appear to be the case. At the moment, my best guess of the root cause is one of my windows PCs (that remain on most of the time) is somehow causing the issue. Anyone have an idea? I've attached a screenshot of plugin config. EDIT. I wanted to have this image as just a clickable item you could expand. Is that not possible?
  17. No any CPU activity spikes I've seen have always been temporary (and I assume are due to normal activity). So I don't believe I've had that particular issue. Based on the debug logs, it's always because of detected array activity. But I still haven't confirmed what's been pinging my server so much.
  18. Thanks, I forgot about that option. The system ran throughout the night again and according to the syslog, it was detecting drive activity. I'll try disabling Cache Directories to see if that fixes the issue. Usually when I've encountered this issue, unRAID would show all drives being spun down when I checked in the morning. So I didn't think it was the plugin misbehaving.
  19. S3 Sleep, Unreliable activation. I have my unRAID server setup to go to sleep after a period of inactivity. Most of the time it works as expected. But frequently I would leave the server untouched over night and find out the next morning it never automatically went to sleep. Whether it works correctly seems random. Do you have an idea on what could be causing the issue? The only other plugins that run automatically daily are Dynamix SSD TRIM and Cache Directories. I don't imagine those being the issue.
  20. I have my unRAID server setup to go to sleep after a period of inactivity. Most of the time it works as expected. But frequently I would leave the server untouched over night and find out the next morning it never automatically went to sleep. Whether it works correctly seems random. Does anyone have an idea on what could be causing the issue? The only other plugins that run automatically daily are Dynamix SSD TRIM and Cache Directories. I don't imagine those being the issue. unRAID 6.7.2 MSI X270 Gaming Plus Ryzen 3600X
  21. You did confirm the performance was bad with multiple games right?
  22. Some Googling showed that the error could be result of corrupt file system. I ran Windows Chkdsk and it found no errors. Against my better judgement, I decided to delete the empty partition shown in the screenshot and now it can't boot properly. I guess I will do another fresh install of windows.
  23. UPDATE. I ended up formatting the SSD to XFS, and the problem went a way. The drive was originally formatted to NTFS by Windows when I created the VM. Perhaps that caused the issue. ORIGINAL POST_________________________ I've attached my system log. I believe there's an issue with my UD mounted SSD that's causing my system log to get filled up with this message below. Most recently, I created a new Windows 10 VM while passing though the SSD. I'm guessing that's related. I also recently enabled ACS override to pass though a USB card. Help would be greatly appreci
  24. I created a new VM while passing though the SSD. Sustained write speed is now 200+ MB/s. Definitely better, but still not close to bare metal. Crystal diskmark gave bad results due to caching. For perspective, this is what Space Invader One got for a Vdisk. He had similarly bad sequential write speeds. https://youtu.be/QaB9HhpbDAI?t=15m44s Should I still configure the disk to as a "thin provisioned drive"?
  25. I believe the config is correct (see above). The media type says it's a "Solid state drive" and doesn't say it's a thin provisioned drive. So I'm not sure where I went wrong.