christenlanger

Members
  • Posts

    10
  • Joined

  • Last visited

Recent Profile Visitors

The recent visitors block is disabled and is not being shown to other users.

christenlanger's Achievements

Noob

Noob (1/14)

0

Reputation

  1. I'm having the same trouble. The audio device can't be reset. I've found a way to reset without rebooting by repurposing a script by Spaceinvader One resetting the GPU. It's just a bit of a hassle to do every time so I'm just looking at using an audio interface at the moment.
  2. Sorry for the late reply. I've managed to solve it a while back by just rebooting the server. I will let you know if I encounter this bug again. Although I have already updated the plugin to the latest.
  3. Sorry if this is a very basic question but I cannot update the My Servers plugin and it just says Pending. It is true in both the Plugin page and the CA page.
  4. I've bound my GPU to vfio on boot. Is getting the error "NVIDIA-SMI has failed because it couldn't communicate with the NVIDIA driver. Make sure that the latest NVIDIA driver is installed and running." normal?
  5. I've managed to pass my GPU through to a VM but any 2nd VM I create does not correctly pass-through for some reason. The first VM is stopped of course. There's nothing in the log that indicates a failure, I think. Is there a possibility that this is a hardware issue with the GPU? UPDATE: I have solved the issue by binding the GPU to vfio on boot. I'm actually not sure if that was the correct solution but it seems to be working now.
  6. So I've started an extended test for my four drives roughly 16 hours ago. I have two 4TBs and one 8TB, both of which are desktop drives, and my 10TB NAS drive which serves as parity. 6 hours would have passed before I went to sleep and I checked on their status. Both the 4TBs were further in the process at about 80% while the larger drives were still at 50%. Looked par for the course. When I woke up just a bit earlier, my 2-year old 4TB and the 8TB has already finished. The 10TB and other newer 4TB drive was still at 90%. A couple of hours later, the 10TB drive has finished it self-test as well while the 4TB is still at 90%. My drives FYI: 4TB - WD Blue (CMR) WD40EZRZ - 1% utilization 4TB stuck at 90% - WD Blue (SMR) WD40EZAZ - 74% utilization 8TB - Seagate Barracuda (SMR) ST8000DM004 - 20% utilization 10TB - WD Red Plus WD101EFBX - parity Should I wait a few more hours, or just restart the test? For the record, the spin-down delay is disabled. Unraid never lets you start an extended test anyway if it's enabled.
  7. At this point I'm keen on waiting for the stable release for that version. Thanks for the direction.
  8. So there's really nothing wrong but is there a way to configure this? When all disks are spinning, the hdd activity led (the one that you connect to the motherboard) will only light up on actual disk activity, which is expected. If at least one drive is spun down (either manually or automatically), the led will flash once a second outside of disk activity. It still permanently lights up when there's a write happening so it's normal during that.
  9. The first cycle is about to finish and it's the full pre-read, zeroing, post-read run. After some time it started to make sense that I should not at least skip post-read. Am I right in thinking that the pre-reads after the 1st cycle doesn't really do much aside from additional testing? Since you just finished the post-read from the previous cycle, it seems like it makes sense that you could go to a write process instead of another read process. I don't know what I'm talking about.
  10. I've recently bought a new 10TB drive intending for it to be the new parity drive and I'm almost at the end of the first full pre-clear cycle which I'm estimating to complete with a total of 51 hours. I have read that 3 cycles should be a good stress test to catch a bad drive. My question would be, is it ok to skip the pre-read, or post-read, or both for the subsequent cycles? I do want to test this drive enough that if it fails, I could have it immediately replaced within its two week immediate replacement window.