12 hours ago, nexusmaniac said:

 

@ljm42 - You've got similar hardware to me, how's rc9f behaving for you?

 

Sorry, I am still running 6.3.5 on bare metal. I have been testing the 6.4 rc's in a VM.

10 hours ago, Squid said:

10 hours ago, CHBMB said:

[mention=10290]Squid[/mention] Could it have anything to do with the new letsencrypt SSL stuff?

I'll revamp the code. Code expects no separate IP don't know about SSL

 

Saw the update, not sure if it was meant to fix it but still have the same issue.

 

Cheers,

 
Saw the update, not sure if it was meant to fix it but still have the same issue.
 
Cheers,

K. Does it work with the black or white theme?

1 hour ago, Squid said:

3 hours ago, Lebowski said:

 
Saw the update, not sure if it was meant to fix it but still have the same issue.
 
Cheers,

K. Does it work with the black or white theme?

Still not working with black or white theme.

On 24. 9. 2017 at 9:18 PM, limetech said:

 

Can you test something for me?  Look at the device identifier for your nvme device, let's say it's "nvme0n1".

Please see if output of this command:

smartctl -A /dev/nvme0n1

Looks identical to output of this command:

smartctl -A /dev/nvme0

(we just dropped the 'n1' from end of the device).

 

Also please include vendor/model of your NVMe device.  Thanks!

For the Samsung 950 Pro works both commands.

On 9/25/2017 at 6:54 AM, nexusmaniac said:

 

I will cross post just for the sake of showing that I did this already

 

I looked through every file of the log myself and although I'm no pro.. I know my way around Linux and nothing stood out to me!

 

I'm happy with the stability of my hardware. Including the PSU, 80+ Gold, be quiet! 550w Straight Power

It memtests for days with no issues and it's not as if it's crashing under high load, it's seemingly when it's doing nothing  So I'm stumped!

 

(The PSU has support for the lower power C states of Haswell so it's not like it's that either) I'm used to uptime in months, or between unRAID updates, whichever comes first  Happy to hear any other suggestions

 

 

If running an RC release and you get a full system lockup where the logs are unavailable to be obtained afterwards, you'll need to hook up a monitor and keyboard to the system directly, login to the console, and type the following command:

 

tail /var/log/syslog -f

This will start printing out log messages to the screen locally which may reveal a kernel panic right before the hang up.  Take a photo of those messages after the system reaches this hung state and post a new topic highlighting the system crash.  Without this, we cannot research the issue further at all.

1 minute ago, jonp said:

 

If running an RC release and you get a full system lockup where the logs are unavailable to be obtained afterwards, you'll need to hook up a monitor and keyboard to the system directly, login to the console, and type the following command:

 

tail /var/log/syslog -f

This will start printing out log messages to the screen locally which may reveal a kernel panic right before the hang up.  Take a photo of those messages after the system reaches this hung state and post a new topic highlighting the system crash.  Without this, we cannot research the issue further at all.

 

Brill! Thanks Jon!

 

I'll run this as and when I get a full lockup

 

(this will still give useful info after a reboot, right? When I say full lockup I mean I can't login to type )

2 hours ago, nexusmaniac said:

(this will still give useful info after a reboot, right? When I say full lockup I mean I can't login to type )

 

No. You need to type the command before the lock up. It simply displays the tail of the syslog on the screen, updating it in real time, so it needs to be running at the time of the crash.

2 hours ago, John_M said:

 

No. You need to type the command before the lock up. It simply displays the tail of the syslog on the screen, updating it in real time, so it needs to be running at the time of the crash.

 

Correct.  Sorry if I wasn't clear enough.

2 hours ago, John_M said:

 

No. You need to type the command before the lock up. It simply displays the tail of the syslog on the screen, updating it in real time, so it needs to be running at the time of the crash.

 

Just now, jonp said:

 

Correct.  Sorry if I wasn't clear enough.

 

Thought that might be the case

 

Thanks both!

 

I've got the command running now, I'll see what it says when I see the next lockup

10 hours ago, Lebowski said:

Still not working with black or white theme.

You're going to be SOL then.  Been testing with @CHBMB and cAdvisor won't let you hit its webUI via a HTTPS, and in an iframe calling a http from a https parent is a security breach and blocked by browsers.

 

Just uninstall the plugin, and simply hit cAdvisor via its icon

 

2 hours ago, Squid said:

You're going to be SOL then.  Been testing with @CHBMB and cAdvisor won't let you hit its webUI via a HTTPS, and in an iframe calling a http from a https parent is a security breach and blocked by browsers.

 

Just uninstall the plugin, and simply hit cAdvisor via its icon

No problems at all, was just reporting it. I don't really use it. I just hit the icon if I need it.

 

cheers

The temp reading on my NVME card through PCIE is now correct, thankyou.

I swapped to the "grey" UI theme today - works well so far.

 

However, noticed that down the bottom left corner it says "Array Started•Starting services...:

 

2 hours ago, marshy919 said:

However, noticed that down the bottom left corner it says "Array Started•Starting services...:

 

Does reloading the Main page in your browser fix it?

 

Are the hard lockups resolved in this version? I rolled back to 6.3.5 as it was locking up very frequently. 

What hard lockups?  I haven't had any hard lockups ever with unRAID.  Then again my server works properly...

50 minutes ago, HellDiverUK said:

What hard lockups?  I haven't had any hard lockups ever with unRAID.  Then again my server works properly...

That's nice for you. A number of people have reported these. For the record, tickets have been filed, although I haven't received a direct response. 

Are the hard lockups resolved in this version? I rolled back to 6.3.5 as it was locking up very frequently. 

Might be you have to try it for yourself, as it's difficult to confirm an issue has been solved unless it's tried by someone that was affected by it.

Or if there are others that have been affected and you're 110% sure it's exactly the same problem you could wait and see if anyone else reports that the issue is fixed.

12 minutes ago, CHBMB said:

Might be you have to try it for yourself, as it's difficult to confirm an issue has been solved unless it's tried by someone that was affected by it.

Or if there are others that have been affected and you're 110% sure it's exactly the same problem you could wait and see if anyone else reports that the issue is fixed.

Yeah, I was hoping to elicit a response from Lime Technology on this. I don't mind running it to produce reports, but not if they aren't getting responses. When it locked up, there weren't any messages printed to output, just a hard lock. Sent in the logs, though. 

@jonp has posted on the forum the last couple of days about hard locks and tail, on mobile atm, so can't find the posts but they're around somewhere!

9 minutes ago, bcjenkins said:

Yeah, I was hoping to elicit a response from Lime Technology on this. I don't mind running it to produce reports, but not if they aren't getting responses. When it locked up, there weren't any messages printed to output, just a hard lock. Sent in the logs, though. 

 

It can only be declared solved if Limetech is able to reproducre the problem themselves and subsequently find a fix.

 

Submitting diagnostics information when failures occur will help to further investigate the issue, hence the request to supply this information as much as possible.

 

Release notes are used to indicate which issues have been addressed.

Edited September 27, 20178 yr by bonienl

16 minutes ago, CHBMB said:

@jonp has posted on the forum the last couple of days about hard locks and tail, on mobile atm, so can't find the posts but they're around somewhere!

https://forums.lime-technology.com/topic/60292-unraid-os-version-640-rc9f-available/?page=5&tab=comments#comment-592494

Thanks for the helpful replies! I'll perform the upgrade again and output the log to screen as suggested. 

Nah didn't work. Tried different pc with different browser too.

Sent from my SM-G935F using Tapatalk

And another crash.

 

 

Sep 28 01:28:58 Tower kernel: CPU: 1 PID: 18408 Comm: apache2 Not tainted 4.12.14-unRAID #1
Sep 28 01:28:58 Tower kernel: Call Trace:
Sep 28 01:28:58 Tower kernel: out_of_memory+0x3ac/0x3ce
Sep 28 01:28:58 Tower kernel: Killed process 13687 (shfs) total-vm:25190852kB, anon-rss:21768572kB, file-rss:4kB, shmem-rss:760kB

Now rebooting into the rc9f version.. I will switch off syncthing.. Its the latest plugin I added..

 

Edited September 28, 20178 yr by Helmonder