mbc0

Members
  • Content count

    133
  • Joined

  • Last visited

Community Reputation

0 Neutral

About mbc0

  • Rank
    Advanced Member

Converted

  • Gender
    Undisclosed
  1. Thanks for chiming in, there does not seem to be a solution so I am moving DVBLink back to my Gen8 microserver where it worked perfectly...
  2. fingers crossed you will be able to do something with it :-) Thanks for chiming in
  3. Yes, would love the docker to work but that is due to my pixilation issues on heavy CPU usage, I do run just a vm with 4GB assigned purely to run DVBLink & Crashplan so I use the auto login, it can stay running forever without any issues until I start a video encode it pixelates DVBLink (even after the encode has finished) the only way to clear it again is to reboot :-S The docker would probably be the answer but like you I cannot get the WEBUI!
  4. Ah yes, I remember that now! I too have changed the service to run as a user but if you set your VM to login automatically (run netplwiz) everything will be automatic!
  5. what do you have to make sure you are logged in to?
  6. No activity on this thread since June, Docker last updated in June and your question is unanswered, looking like this is dead project :-( Just thought I would have a go with this as I am suffering a pixelation issue when cpu is stressed but cannot get the WEBUI either
  7. Hi, Not sure if this is the right place to ask this but I have a DVBLink installation running on a Windows 7 VM hosted by my unRAID server. All works perfectly for about a week and then I start getting disconnection issues resulting in picture glitching/breaking up. I can restart the DVBLink Service or the VM but still have the same problem, the only way I have found to clear the problem is to reboot the whole server (This has happened about 3 times now) Just fishing for ideas in case anyone else has had the same/similar issues? I5 unRAID Server 18GB RAM 42TB Storage VM running from 480GB SSD DVBSKY Dual DVBS-2 PCI-E Card Many Thanks
  8. Please Don't remove them! It would be a deal breaker for me!
  9. Hi, I notice quite a lot that when I want to access certain folders I have to wait until 2, 3, 4 or sometimes 5 drives have spun up individually whilst watching a blue circle spin round I know that when I shut down my array, unRAID is able to spin up all my drives simultaneously why can it not do the same when requested file access? is there a way to do this? Many Thanks
  10. Hi, My USB hub is detected by unraid but I was wondering if it was possible to pass through the whole hub to a VM like you would stub a PCI Device? Each device I connect to the hub show up to be passed through but would be nice if I could get the whole hub. Cheers
  11. Ok, Swapped out the Promise card for a Via Chipset Card and all the errors have gone and system is flying again! Thanks for you help fellas
  12. Hi mate, I disabled the VM to see if that cured the issue after googling found the same results this morning but it had no effect. Cheers
  13. Many Thanks for your reply, I will exchange that controller to see if that resolves the issue, I did indeed delete the previous log file as the UI wouldn't work and the system had ground to a halt with out of memory errors, deleting the log file cured that. I am stuck with the system trying to move 400GB of data which will take weeks at the speed it is going, how can I safely take down the server whilst the mover is running? Thanks Again
  14. Anyone got any ideas? I still have 360GB to shift before the mover finishes which will take weeks at this rate!
  15. Hi, I have an issue where my server is running very slow (mover is running about about 1GB every 20-30 mins) I can see these errors in my log which appear to be relating to a hard disk issue but the addresses do not match up to anything in my device list? Can someone throw me a bone please? Nov 18 12:05:06 UNRAIDSERVER kernel: DMAR: DRHD: handling fault status reg 3 Nov 18 12:05:06 UNRAIDSERVER kernel: DMAR: DMAR:[DMA Read] Request device [04:00.0] fault addr ffff0000 Nov 18 12:05:06 UNRAIDSERVER kernel: DMAR:[fault reason 06] PTE Read access is not set Nov 18 12:05:06 UNRAIDSERVER kernel: DMAR: DRHD: handling fault status reg 3 Nov 18 12:05:06 UNRAIDSERVER kernel: DMAR: DMAR:[DMA Read] Request device [04:00.0] fault addr fffe0000 Nov 18 12:05:06 UNRAIDSERVER kernel: DMAR:[fault reason 06] PTE Read access is not set Nov 18 12:05:06 UNRAIDSERVER kernel: DMAR: DRHD: handling fault status reg 3 Nov 18 12:05:06 UNRAIDSERVER kernel: DMAR: DMAR:[DMA Read] Request device [04:00.0] fault addr ffff0000 Nov 18 12:05:06 UNRAIDSERVER kernel: DMAR:[fault reason 06] PTE Read access is not set Nov 18 12:05:07 UNRAIDSERVER kernel: DMAR: DRHD: handling fault status reg 3 Nov 18 12:05:07 UNRAIDSERVER kernel: DMAR: DMAR:[DMA Read] Request device [04:00.0] fault addr fffdc000 Nov 18 12:05:07 UNRAIDSERVER kernel: DMAR:[fault reason 06] PTE Read access is not set Nov 18 12:05:07 UNRAIDSERVER kernel: DMAR: DRHD: handling fault status reg 3 Nov 18 12:05:07 UNRAIDSERVER kernel: DMAR: DMAR:[DMA Read] Request device [04:00.0] fault addr ffff8000 Nov 18 12:05:07 UNRAIDSERVER kernel: DMAR:[fault reason 06] PTE Read access is not set Nov 18 12:05:07 UNRAIDSERVER kernel: DMAR: DRHD: handling fault status reg 3 Nov 18 12:05:07 UNRAIDSERVER kernel: DMAR: DMAR:[DMA Read] Request device [04:00.0] fault addr fffec000 Nov 18 12:05:07 UNRAIDSERVER kernel: DMAR:[fault reason 06] PTE Read access is not set Nov 18 12:05:07 UNRAIDSERVER kernel: DMAR: DRHD: handling fault status reg 3 Nov 18 12:05:07 UNRAIDSERVER kernel: DMAR: DMAR:[DMA Read] Request device [04:00.0] fault addr ffff8000 Nov 18 12:05:07 UNRAIDSERVER kernel: DMAR:[fault reason 06] PTE Read access is not set Nov 18 12:05:07 UNRAIDSERVER kernel: DMAR: DRHD: handling fault status reg 3 Nov 18 12:05:07 UNRAIDSERVER kernel: DMAR: DMAR:[DMA Read] Request device [04:00.0] fault addr fffd8000 Nov 18 12:05:07 UNRAIDSERVER kernel: DMAR:[fault reason 06] PTE Read access is not set Nov 18 12:05:07 UNRAIDSERVER kernel: DMAR: DRHD: handling fault status reg 3 Nov 18 12:05:07 UNRAIDSERVER kernel: DMAR: DMAR:[DMA Read] Request device [04:00.0] fault addr ffff8000 Nov 18 12:05:07 UNRAIDSERVER kernel: DMAR:[fault reason 06] PTE Read access is not set Nov 18 12:05:07 UNRAIDSERVER kernel: DMAR: DRHD: handling fault status reg 3 Nov 18 12:05:07 UNRAIDSERVER kernel: DMAR: DMAR:[DMA Read] Request device [04:00.0] fault addr ffff4000 Nov 18 12:05:07 UNRAIDSERVER kernel: DMAR:[fault reason 06] PTE Read access is not set Nov 18 12:05:07 UNRAIDSERVER kernel: DMAR: DRHD: handling fault status reg 3 Nov 18 12:05:07 UNRAIDSERVER kernel: DMAR: DMAR:[DMA Read] Request device [04:00.0] fault addr ffff8000 Nov 18 12:05:07 UNRAIDSERVER kernel: DMAR:[fault reason 06] PTE Read access is not set Nov 18 12:05:09 UNRAIDSERVER kernel: DMAR: DRHD: handling fault status reg 3 Nov 18 12:05:09 UNRAIDSERVER kernel: DMAR: DMAR:[DMA Read] Request device [04:00.0] fault addr ffff4000 Nov 18 12:05:09 UNRAIDSERVER kernel: DMAR:[fault reason 06] PTE Read access is not set Nov 18 12:05:11 UNRAIDSERVER kernel: DMAR: DRHD: handling fault status reg 3 Nov 18 12:05:11 UNRAIDSERVER kernel: DMAR: DMAR:[DMA Read] Request device [04:00.0] fault addr ffff9000 Nov 18 12:05:11 UNRAIDSERVER kernel: DMAR:[fault reason 06] PTE Read access is not set unraidserver-diagnostics-20161118-1204.zip
Copyright © 2005-2017 Lime Technology, Inc. unRAIDĀ® is a registered trademark of Lime Technology, Inc.