wickyd

Members
  • Posts

    37
  • Joined

  • Last visited

Converted

  • Gender
    Undisclosed

Recent Profile Visitors

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

wickyd's Achievements

Newbie

Newbie (1/14)

3

Reputation

  1. Yeah, the P2000 is the lowest one with no transcoding limit, at least that's what i get from Here. That's the card I really want, but trying not to spend the money.
  2. thanks! I'm going to install it this week! I'll keep the thread open to post results in case anyone is interested.
  3. It does have an integrated GPU...i'm assuming a crappy one. I just wasn't sure the P1000 I was thinking of putting in would do more/better than the dual 8core/16HT procs.
  4. My Unraid Server currently has a dual Xeon E5-2640 V2 @ 2GHZ. I have the option to put in a Quadro P1000 w/ 4GB. I do quite a bit of transcoding (common for 3-4 streams at a time). I've also noticed that when I'm playing 4k videos, it hurts my cpu quite a bit. Is the Quadro P1000 better for transcoding than my dual procs? I know that the P1000 is locked for 3 simultaneous streams but I figured I can unlock that. Advice? TLDR: dual Xeon E5-2640 V2 @ 2GHZ vs. Quadro P1000, which would transcode better/more?
  5. Thank you! That just saved me a nice chunk of cash. Sent from my SM-N975U using Tapatalk
  6. Quick question, in dual parity, do the drives have to be the same size? I know they have to be bigger than my data drives. I have 5tb max data drive size and 1 8tb parity drive. Can I add a 6tb parity drive? Thanks Sent from my SM-N975U using Tapatalk
  7. ahhh! That makes sense! thank you!
  8. I have some older drives that aren't showing any errors yet but I can't run smart tests on them. Both short test and extended tests give me " Errors occurred - Check SMART report". I've looked at the report and I see a lot of corrected errors (understandable because they're 8 year old drives, but they're all reading as SMART results OK. Anything I should worry about? AL13SEB900_33J0A0OOFRD2_350000394a81af8c0-20210513-1915.txt AL13SEB900_6340A027FRD2_350000394d8029794-20210513-2206.txt Also, my whole array is showing perfect with no errors. On a side note, do I not see the temps on my small drives because they're just old SAS drives without the support for temp?
  9. As of last month, 64 GB ECC (DDR3) with Dual Xeon E5-2640 v2. Previously, was running 8GB DDR3 on Core i5 750, before that I was running 2GB on a Pentium 4 3.0. I've come a long way =).
  10. Backup up option vote here, for the entire server. I've used Unraid for about 8 years now (pre v.5) and am on my 5th iteration of hardware. Now that I have so many older drives and builds, I've been wanting to put together a 2nd unraid for full backups that i can keep offline except for the backups run. I know there are solutions out there but honestly, not being a linux guy they kicked my butt. In fact, trying to implement the SSH keys (to backup offsite) broke my old vpn solution.
  11. okay, so perusing the forums, i've found an old post from v. 5.0 that seemed similar to mine. It had to do with using some seagate SAS drives and not being able to spin down. First I thought it was my power, I have two 750w psu's and only had one plugged in. I plugged in the second one and rebooted to clear the logs, waited a couple of hours and started seeing the logs fill up again. then after reading https://forums.unraid.net/topic/27968-ioctl-errors/ , i thought be my SAS drives. so i turned off the drive spin down and four hours later, and i'm still at 1% log size. So my question is, is there anything i can do here? I'm not sure i like the drives spinning 24/7 (power AND wear on the drives come to mind). my log is above, and it's probably just my 4 drives that never showed their temps: edit: i've since put my drive default back on the 15 minute spin down, but put the four drives individually on "never" spin down. it'll do for now, until i can get a fix at least.
  12. Crap. So you think my PSU isn't giving enough power?
  13. Hey all, I've made some changes to my server recently (changed and added some docker configs) and am now getting logs filled up (fix common problems alerted me to it). I looked through the diagnostics and see that the issue might be a bad drive. Can someone take a look and confirm please? thanks, server-diagnostics-20201130-1152.zip
  14. Thanks! So, as you said, I had to go into the share and delete the 100 or so folders that were created by the last copy that didn't finish. then I just started doing it in batches. It recreated the folders and wrote in different disks again. i appreciate the help!!
  15. I think i get what you're saying, but I'm writing from a disk to a share that contains all disks (16). Are you saying i should start copying from disk to individual disks in the array?