Jump to content

Kevin

Members
  • Content Count

    10
  • Joined

  • Last visited

Community Reputation

0 Neutral

About Kevin

  • Rank
    Member

Converted

  • Gender
    Undisclosed
  1. My unraid dashboard shows roughly 45% CPU usage across 24 threads. BOINC is working on 24 tasks (all with status running) with no computing restrictions imposed by me, so I'm wondering if this is an issue on my end? I would have assumed it would use close to 100% CPU.
  2. Yep, this worked for me as well with the same TBS 6981 tuner card. Good call. 👍
  3. In light of current events I imagine they're probably having an influx of new users right now, so perhaps their servers are experiencing high levels of demand.
  4. Hi guys. After updating from TBS build 6.6.7 (which was fully working with my TBS 6981) to TBS 6.8.2, my TVHeadend docker will no longer start. Fails with error "Server Execution Error" If I remove '--device=/dev/dvb/' from Extra Parameters it'll launch, but obviously without the card being passed through. Then when I try to reapply '--device=/dev/dvb/", the action fails with: "/usr/bin/docker: Error response from daemon: error gathering device information while adding custom device "/dev/dvb": no such file or directory." My TBS card shows up under System Devices as Conexant Systems CX23885, which iirc is how it presented before the update (from 6.6.7 to 6.8.2), so I think the card is being detected as before, but I'm really not sure. I'm already out of my depth at this point, so any help is appreciated. Maybe I should try the CrazyCat build instead?
  5. Looks like we have a winner. Thanks for all the helpful suggestions, you guys rock.
  6. I'm wondering if there's any way from the Unraid side to prevent the creation of .DS_Store and (sometimes hundreds) of ._FILENAME files in every.single.directory the Mac connects to? These files are not visible when browsing from the Mac itself using Finder, but they are visible and causing problems for non-Mac devices which also need to access these shares. Many thanks.
  7. My server was having random reboots on 6.7.2 (TBS Open Source) over the course of a few days before I noticed. At the time I resolved the problem by reverting back to 6.6.7 (TBS Open Source), no unwanted reboots for months. However, I've recently revisited 6.7.2 and the issue returns. I'm now running (TBS Open Source) 6.8.0 rc5, we'll see how that goes.
  8. Hi guys. So, this probably isn't an Unraid problem at all, but I thought there'd be no harm in asking the experts. Anyway the situation is, I have a server (intel S2600GL based) with which I'm using an old Adaptec 5805 PCIe raid controller (Intel's own RAID configuration utility terrifies me, which is why I didn't use the controller that came with board). A while ago I bought some new Seagate Exos 6TB SAS drives. These are SAS 12Gb/s drives, which are to my understanding backwards compatible with SAS 6Gb/s controllers and interfaces. For now I have them configured in RAID 1 - probably not the ideal way to use Unraid, but this system has evolved over a period of years into something of a Frankenstein, and it's quite complicated, so this is where it's at as of now. The problem I have is that after every power down I have to physically go to the server, enter the RAID configuration utility and rescan the drives in order to get them detected. At power on I can hear the drives spin up, activity lights flash and whatnot, but the controller just doesn't seem to catch them before it's finished its POST. After rescan I can exit the utility, reboot and it'll run perfectly fine for months, then at some indeterminate time something happens and the drives disappear from Unraid. My best guess is the controller pulls the drives to protect the data. (a hardware RAID thing I think?) It takes a power cycle, rescan, reboot to get the drives detected with logical volume status 'optimal' and make Unraid happy again. So far I've tried moving the drives to different slots on the backplane, but the problem eventually reemerges. Since this problem only began when I installed the new drives, I'm inclined to think there is some incompatibility between drives and controller, but I wouldn't even know where to start with diagnosing that. Could it be I simply need a newer raid controller? My backplane only has the old type sff-8087 connectors, although I think I've seen adaptor cables online. For now I have all important data backed up and the only thing keeping me from messing with it more is the prospect of downtime and it doesn't seem to have reached the threshold of brokenness where it becomes worth fixing. I'd just like to hear ideas or if anyone has experienced anything similar. Many thanks (apologies for incoherent rambling)
  9. 64 gigs ECC because I had it just collecting dust on a shelf and it's nice to have headroom when I need to run some VMs. Got a bunch spare too, limited by the number of slots on my board for now.