9 minutes ago, dlandon said:

Should the DOCKER_CUSTOM_NETWORKS be br0 and not eth1?

 

No, any interface which has an IP address assigned is automatically taken into the list. DOCKER_CUSTOM_NETWORKS lists all other available interfaces which might be used as well.

 

another call trace...

 

 

overnight server attempted to run scheduled parity check and hit another call trace. shares are unreachable now. progress is 0.0% with a finish time of 9044 days and 35 minutes. attempting to download diagnostics will not actually complete or do anything. I can't cancel the parity check either. But web gui seems functional and I was able to download the syslog, which is attached.

 

 

 

syslog.txt

I have the same problem reported by a few other users that the Unraid GUI does not start (worked find in previous 6.4.1 release) and just left with a flashing cursor, diagnostics attached.

king-diagnostics-20180302-1309.zip

2 hours ago, dlandon said:

That did it.  Is this a bug, or is it my setup?

 

dlandon and myself went into closed debug session and found out that the root cause is a single host (/128) IPv6 assignment, which doesn't allow an IPv6 gateway to be set.

 

An update to the docker script is made to cope with this situation and will be available in the next release. If you have a similar issue as dlandon, temporary set "IPv4 only" for the interface as a workaround.

 

54 minutes ago, remotevisitor said:

I have the same problem reported by a few other users that the Unraid GUI does not start (worked find in previous 6.4.1 release) and just left with a flashing cursor, diagnostics attached.

king-diagnostics-20180302-1309.zip

 

That is for uploading your diags and I hope this helps it get looked into.   I need the built in gui and it does not work for me.

 

13 hours ago, fmp4m said:

Updated to 6.5.0 and now the built in gui wont load,  all I get is a white cursor.    I have to ctrl alt f1 or such to go into a shell mode to control.

I let the server run all night with the cursor displayed to see of it ever went into the gui.   it did not.   I could no longer log into the web gui either,  so I used the f1 shell to reboot into no gui and will flash back today if no other info is needed for this problem.

it appears TRIM is broken with LSI 2308 cards.

 

I have 2 ssd's on it and I get this error and did in 6.4.1 also.

 

print_req_error: critical target error,

 

 

 

Upgraded from previous rc without issues.  VMs came up fine and Docker(w/separate vlan) working normally.

Edited March 2, 20188 yr by Dephcon

5 hours ago, dlandon said:

That did it.  Is this a bug, or is it my setup?

I updated my smaller server and use two dockers with br0 so they get their own ip and didn't have this issue...perhaps it was a corrupted docker config?

 

15 minutes ago, Can0nfan said:

I updated my smaller server and use two dockers with br0 so they get their own ip and didn't have this issue...perhaps it was a corrupted docker config?

 

No.  It looks like my router is not handing out a proper IPv6 gateway address.  I've been messing with the latest Merlin firmware on my ASUS router, and I'm sure it has an issue.

3 hours ago, fmp4m said:

I let the server run all night with the cursor displayed to see of it ever went into the gui.   it did not.   I could no longer log into the web gui either,  so I used the f1 shell to reboot into no gui and will flash back today if no other info is needed for this problem.

 

Looking into it...

46 minutes ago, limetech said:

 

Looking into it...

If you want any more diagnostic uploads to help with this then please ask

I have a problem that I think is 6.5.0rc1 related - installed last night and my tvheadend docker can no longer see my tv cards.  I've checked and the cards are setup correctly using the DVB plugin and I've also verified by temporarily installing dvblink and it can see my cards and scan fine when i use --device=/dev/dvb in extra parameters

 

I've tried doing a fresh tvh install including removing appdata and the cards are still missing.  

 

 

highlander-diagnostics-20180302-1027.zip

6 minutes ago, DZMM said:

I have a problem that I think is 6.5.0rc1 related - installed last night and my tvheadend docker can no longer see my tv cards.  I've checked and the cards are setup correctly using the DVB plugin and I've also verified by temporarily installing dvblink and it can see my cards and scan fine when i use --device=/dev/dvb in extra parameters

 

I've tried doing a fresh tvh install including removing appdata and the cards are still missing.  

 

 

highlander-diagnostics-20180302-1027.zip

From the 1st post in the support thread for the 'DVB edition':

 

In order to use TVHeadEnd or MythTV with PCIe or USB DVB Tuners you need to run a special Unraid build which contains the necessary drivers. 

 

This replaces the Unraid bzroot and bzimage files (the OS) with newly created ones that have drivers for DVB hardware incorporated.

 

16 minutes ago, trurl said:

From the 1st post in the support thread for the 'DVB edition':

 

In order to use TVHeadEnd or MythTV with PCIe or USB DVB Tuners you need to run a special Unraid build which contains the necessary drivers. 

 

This replaces the Unraid bzroot and bzimage files (the OS) with newly created ones that have drivers for DVB hardware incorporated.

 

 

25 minutes ago, DZMM said:

I've checked and the cards are setup correctly using the DVB plugin and I've also verified by temporarily installing dvblink and it can see my cards and scan fine when i use --device=/dev/dvb in extra parameters

I have - I've been running tvh for about a year using the DVB builds, which come out brilliantly around 24 hours after Limetech's builds

I have - I've been running tvh for about a year using the DVB builds, which come out brilliantly around 24 hours after Limetech's builds

It's nothing to do with the unRAID release and the fact it appears in dvblink tells me it's a tvh issue@DZMM

Have you tried a fresh install of tvh as I recommended?

Sent from my LG-H815 using Tapatalk

5 minutes ago, CHBMB said:

It's nothing to do with the unRAID release and the fact it appears in dvblink tells me it's a tvh issue@DZMM

Have you tried a fresh install of tvh as I recommended?

Sent from my LG-H815 using Tapatalk
 

yes - backed up appdata and deleted it and the image and did a fresh install - still no cards

9 hours ago, bonienl said:

 

LOL

If only it was just that easy 

I don't have any drive with UDMA counter non-zero, so I have never trigged the condition.

 

But a quick glance seems to indicate that the following code in scripts/monitor would be involved.

      $attr = "$name.$id";
      $last = ($saved[$item][$attr] ?? 0)*$level;
      if ($raw>0 || $fail) {
        if ($raw>$last) {
          exec("$notify -e ".escapeshellarg("unRAID $text SMART health [$id]")." -s ".escapeshellarg("Warning [$server] - $word is $raw").
" -d ".escapeshellarg("$info")." -i \"warning\"");
          $saved[$item][$attr] = $raw;
          unset($saved[$item][$ack]);
        }

The code knows $attr so easy to check if it's 199, i.e. UDMA CRC.

The code knows if $saved[$item][$attr] is set or not.

So if $raw > $last and $attr is 199 and $saved[$item][$attr] is empty then the code could skip the notify and just save the $raw value as the baseline value for further tests.

30 minutes ago, DZMM said:

yes - backed up appdata and deleted it and the image and did a fresh install - still no cards

ok, rolled back to 6.4.1 and the tuners re-appeared - @CHBMB I'll try a different tvh build, but my money's on there's a problem with 6.5.1

 

Will report back if a different TVH build works or not

ok, rolled back to 6.4.1 and the tuners re-appeared - [mention=6219]CHBMB[/mention] I'll try a different tvh build, but my money's on there's a problem with 6.5.1
 
Will report back if a different TVH build works or not

Problem with that theory is the tuners are appearing in Unraid and in DVBlink.

So in the Operating System and a different container they're detected.

Sent from my LG-H815 using Tapatalk

Not sure if I screwed something up but ever since upgrading my username and password won’t work when I SSH, telnet works fine.  I did enable SSL.

14 hours ago, dlandon said:

No.  It looks like my router is not handing out a proper IPv6 gateway address.  I've been messing with the latest Merlin firmware on my ASUS router, and I'm sure it has an issue.

 

 

ahhh Router firmware....fun I hope you find the answer....i hate ipv6 lol I will never have the 200 trillion devices needed for it on my LAN lol