kortina

Members
  • Posts

    34
  • Joined

  • Last visited

Converted

  • Gender
    Undisclosed

Recent Profile Visitors

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

kortina's Achievements

Noob

Noob (1/14)

1

Reputation

  1. Thank you JorgeB. I feel a bit silly that I missed this.
  2. attached. Thank you for your time, it is most appreciated nas-diagnostics-20230616-2224.zip
  3. I am having some trouble with my array... I have a few older 8TB drives... It looks like one has failed, however when I change it over to another disk the interface wont let me choose the spare drive!? I can reboot, and the drive is then able to be selected... Parity attempts to rebuild, but the GUI says 'Unmountable: Wrong or no file system' Any ideas what I might be doing wrong? Thanks in advance
  4. looking for a bit of scripting help... I am trying to fetch a TV Guide (xml file) that is around 40Mb. The server is unreliable. using this: curl -L --limit-rate 200K "http://provider.url/epg?username=un&password=pw" --speed-time 15 --speed-limit 1000 -o /mnt/user/appdata/tvheadend/data/cronIPTV_EPG.xml I have run this multiple times my so I know the syntax is OK. but about 3 in 5 fail!!! output: curl: (28) Operation too slow. Less than 1000 bytes/sec transferred the last 15 seconds How do I wrap this command in a loop so that it will try 10 times if it falls over with the "operation too slow" error?
  5. Thanks for the pointer. To complete the story, this config is working November 2018 - Unraid 6.5.3, TVHeadEnd 4.3-1517~g7fc6cba4d, NGINX Config Type: Variable Name: RUN_OPTS Key: RUN_OPTS Value: --http_root /pvr **note that there is NO equals sign in the value NGINX: location /pvr { proxy_pass http://192.168.0.88:9981; proxy_set_header Host $host; proxy_set_header X-Real-IP $remote_addr; proxy_set_header X-Forwarded-For $proxy_add_x_forwarded_for; proxy_set_header Upgrade $http_upgrade; proxy_set_header Connection "upgrade"; } (Assuming that your unraid - tvheadend docker has the ip of 192.168.0.88)
  6. Hi guys, I am having trouble setting up a NGINX reverse proxy for TVHeadEnd. I followed some instructions back on P33. It seems that when I create the variables with unraid, it is not producing the correct command line: I have attached some images that highlight the issue. I have read on this page that there needs to be an equals sign between the http_root and value for the root. https://github.com/tvheadend/tvheadend/blob/master/docs/markdown/faqs.md#q-access-tvheadend-through-http-proxy --name='tvheadend' --net='bridge' -e TZ="Australia/Sydney" -e HOST_OS="unRAID" -e 'PGID'='100' -e 'PUID'='99' -e '--http_root '='/pvr' -p '9981:9981/tcp' Any ideas what I am doing wrong?
  7. Any plans to support https://github.com/buzzfeed/sso ? Looks like the oauthproxy2 project is dead.
  8. Hi Guys, I have an idea that I wanted to share. I am hosting a Retro gaming night soon, and was hoping to emulate TWO Amiga computers (connected via a Null Modem cable) I am comfortable with Windows and WinUAE, I can probably get the Video pass-through and 15khz output happening. Is there a way to create two virtual 'COM' ports, pass one to each VM... but JOIN the COM ports (like you would with a NULL Modem cable)?
  9. No luck with the RAM in DIMM2A. Tried my 4 sticks, and also tried two more from a friend (same ones). No answer from the Supermicro email address. Looks like it is time to buy the same board again.
  10. I have reached out to SuperMicro, suggestions: 1) Remove the power and try again. (No change) 2) Put just 1 stick of RAM in DIMM2A, try each stick. It is good to know that the update and same RAM is working for you. I will try option 2, but don't like my luck. Have also cleared the CMOS.
  11. Hi Guys, I have a X9SCM-F-O I updated the BIOS to the latest version (X9SCM4.109 - R2.1) This has bricked my server. I now get 5 short beeps, 1 long. (no POST) My suspicion is that the server is no longer detecting the RAM that I have - Kingston (KVR1333D3E9SK2/8G) - 16Gb I have tried a single stick, but with no luck. Without being able to POST, I cant do anything! Any suggestions?
  12. I thought that I would chime in and give my thoughts... I have been running unRAID for about 3 years 4.7, and recently upgraded to 5.0 and then 5.05. I run a 7 disk system on a Supermicro C2SEE system with a AOC-SASLP-MV8, Celeron 430 / 2Gb. I chose this hardware for the best support, least problem, low power. This is exactly what I wanted out of a file server. More recently I have built a Xeon 1230 / Supermicro / 16Gb hypervisor box (Win2012R2-HyperV). I run a full time Win8.1 VM which I use to record TV, Sickbeard, Couchpotato, SAB and a bunch of other tools. I am most confident with Windows, but like the idea of having a rock-solid file server for my "Production" XBMC clients. It is not the fact that it is Linux based, it is the fact that it is an appliance that does ONE job very very well. The only time unRAID gets rebooted, is when I need to swap a disk. Moving forward, I have had great service out of the hardware and the fact that it will not support x64 based unRAID 6.0 is not a big deal. In real world terms this hardware is old and has already returned it's value to me. I don't run plugins on unRAID. The main reason is because I do not want to sarifice any of the following: 1) My time in keeping up with the quirks 2) Stability of unRAID 3) Upgrade path for unRAID I have read countless threads during the v5 development where uncompatible plugins were the cause of issue. unRAID 6.0 with an included hypervisor would suit me well. I could run a full time Windows "utility" machine, and consolidate my hardware to just 1 box. This is important to my powerbill, my time. and the stability of my home network. Plugins have been underutilised by me because they do not inspire confidence. Keeping other apps isolated off to an additional VM moves them away from being in the realm of support for Tom, allowing him to focus on what is the core product. This is a good idea. Look forward to seeing where the development goes!
  13. That's why they are optional. Which is why I beleive that basic email alerting (Disk Full, Overheat, Parity Check Required, Disk with errors, etc...) should be included in the base product.
  14. Upgraded from 4.7 to 5.0 no problems The Good: Followed the instructions to format USB and copy the vital config. Ran the new-permissions script (took 4h 10m) Upgraded the web-gui (looks much nicer) *Changed my 2Tb parity drive to a brand new 3Tb drive (BIOS decided to change the boot order to this drive!?) Removed an error prone 1.5Tb drive and recycled the old 2Tb parity. The Missing: unRAID still does not email basic warnings... Dead Drive, Overheat, Almost Full, Parity Check older than x days, SMART report on reboot unRAID doesn't have a scheduled Parity Check (Montly?) Thanks for all of the hard work Tom. I am really happy with unRAID, just taking the time to give recommendations on what I think is important for the less technical user. What Next? Replace another old 1.5Tb drive with a fresh 3Tb (going to re-use the 1.5Tb in my PVR solution) Might try and run a version of unRAID with TVHeadend baked in, as it would be nice to have an XBMC-PVR backend. Wait for the plugin stuff to be finished PS - I didn't run any of the Beta/RC versions, my unRAID server is "Production" at home and the wife would NOT like the media server to be unavailable. While the forum seemed very good and responsive to the 'current' beta/rc I feel that I would have had to continue to run on the bleeding edge, while running the availability gauntlet for my home media. PPS - I don't like running plugins, as they seem to open the door to reliability issues.
  15. I am going to chime in again... as it seems that there are more than a few users who have different priorities to my own. Why? -Support for 3Tb drives With support for 3Tb drives, I will not need to upgrade PSU, Case, Sata controller. This is will be at least $300 (AUD) I understand that many users have used the 5.0beta and 5.0RC series and have had mostly good results. I am not keen to move to a beta or RC system mostly because of support. While the beta is fairly fresh it will be supported well on the forum, but the interest from the communitiy in a specific beta like "5.0-rc5-r8168 " will dwindle and leave its users in out in the cold. I have followed the series of beta and RC releaseses and have seen how progressing the beta's has created bugs for some, with the followup beta to introduce show stopper bugs. EG: You need to move on from a particular RC0 version to fix bug A. You cant move to RC1 as there is a critical bug that makes it not compatible with your hardware RC2 could be months away with little to no feedback from Tom as to where it is at. You need to stay on the bleeding edge to get any support from the forum (or stay on 4.7). Version 5.0 final will help the community, it will mark a reference point and the community will widely accept this version (with any bugs) and there can be documented wiki pages that point out any faults and work arounds. Version 5.0 final will help those who are not keen to fall into limbo in terms of longer term support. While this may not be super important to linux guru's it is a bit to much for those who are a bit fresh and like to treat unRAID as an appliance. unRaid is super reliable for me, this is very important unRaid 4.7 is well supported, this is important to me I can't touch 5.0beta or 5.0RC as my unRAID system is the heart of my media solution (XBMC) at home, and my wife would be very shitty if it became unreliable/unavailable.