-
Posts
512 -
Joined
-
Last visited
-
Days Won
8
Content Type
Profiles
Forums
Downloads
Store
Gallery
Bug Reports
Documentation
Landing
Report Comments posted by eschultz
-
-
Changed Status to Retest
-
Changed Status to Retest
-
10 hours ago, Dazog said:
Some of these updates contain CVE patches!
acpid2 2.0.30
btrfs-progs-4.17.1
cifs-utils-6.8
coreutils 8.30
cryptsetup 2.04
curl 7.61.1
dbus 1.12.10
dhcpcd 7.08
E2fsprogs 1.44.4
ebtables 2.0.10 (rev 4)
encodings: 1.0.4 (rev 5)
ethtool 4.18-1
findutils 4.6.0
FreeType 2.9.1
fribidi 1.05
fuse 3.2.6
gdbm 1.18
Samba 4.8.5
RC3 will include all the updated packages that contain a CVE and Samba at the very least
-
Changed Status to Retest
-
Please retest this issue with 6.6.0-rc2 since we updated the kernel to 4.18
-
Yes, you're spot on with 'weirdness' with Haswell + Intel Pstate driver. Only real way to tell power usage is to use a kill-a-watt meter.
-
1
-
-
Can you please try upgrading to BIOS 1402 (released on 8/10/18) and retrying Unraid 6.6.0-rc1?
-
-
5 minutes ago, bastl said:
I have a feeling it's an AMD releated issue with Unraid 6.60-RC1. In earlier Versions i hadn't had any issues like this. Maybe someone with a Ryzen or Threadripper system reading this can test my xml or can try to reproduce this error.
I created a new VM using your XML on a Threadripper machine. Was able to edit and save (without any changes). Then edit, increase the memory and save again. No error messages here.
-
Does your cache pool devices consist of SSDs or HDDs?
Are you using Dynamix S3 Sleep plugin or some other way to make your machine sleep?
-
As a temporary fix to at least be able to type the correct characters to override grub's boot options you can edit the VM and passthrough the usb keyboard from the host to the VM. Then you can at least see from VNC but type from the physical keyboard without issue.
-
What is your native layout for VNC?
I know the 'en-us' keyboard layout for VNC in the current release of unRAID has an issue with "<". This is fixed in QEMU 2.12 which will be included in unRAID 6.6 (currently in development). I only have en-us keyboards here so it'll be tricky to reproduce exactly what you're experiencing but I'm curious if it is also fixed in the newer QEMU.
-
Changed Status to Solved
Changed Version to 6.5.3-rc2
-
Thanks for the PR. Fix is in 6.5.3-rc2 which was just released.
-
Changed Status to Solved
Changed Version to 6.5.3-rc2
-
1
-
-
2 hours ago, nickp85 said:
Awesome, so if I just change my blanks to some value, that that should take care of it?
Yes. Also, I'd change your '20%' to just '20'.
-
Maybe as a quick fix when we build emhttp-server.conf just remove '*.' from the ssl cert name (if found). So:
"return 302 https://*.stonecold.kr:443$request_uri;."
Would become:
"return 302 https://stonecold.kr:443$request_uri;."
-
16 minutes ago, jonathanm said:
So are you going to change to empty = 0 on future releases for those values?
Yup, that's exactly what I did and pushed the code change to github for a future release: https://github.com/limetech/webgui/commit/46cfa877917cb2198f73ac6447cde62ac5e91ed5
It'll also remove any garbage input (non-numeric, spaces, etc).
-
The 'bug' here is if you leave "Battery level to initiate shutdown (%):" or "Runtime left to initiate shutdown (minutes):" boxes empty (instead of 0) then it uses some random 5000 value ... which of course will tell unRAID to shutdown right after running on batteries since UPS at 100% < 5000
-
-
Just to confirm, @nickp85, the CyberPower CP1500PFCLCD is connected to the unRAID server via USB?
-
8 minutes ago, nickp85 said:
Model is CyberPower CP1500PFCLCD, very popular home UPS
I have at least a dozen UPSs here and half of them are CyberPower. I'm pretty sure I have a couple of that exact model. I'll see if I can try a couple of the CyberPower UPSs on some of the unRAID testbed machines.
-
I'm trying to reproduce with a very small UPS here (APC Back-UPS NS 4001) with the following settings in unRAID:
Battery level to initiate shutdown (%): 20
Runtime left to initiate shutdown (minutes): 5Time on battery before shutdown (seconds): 0
I pulled the APC's plug from the wall and almost immediately I got a notification that it was running on batteries. I continued to watch the unRAID APC Settings page to see the UPS runtime left and percentage steadily drop. After about 7-8min the UPS percentage dropped to ~40% and runtime left was 5min the unRAID server initiated a shutdown as expected.
It's taking forever for my UPS to recharge now but next test tomorrow will be to just use the percentage (20%) and set runtime left to 0.
-
A few more results:
- ASRock X370 Killer SLI w/ BIOS 3.40 ---> reports 64GB max. installable capacity (correct!)
- ASRock X370 Killer SLI w/ BIOS 4.70 ---> reports 256GB max. installable capacity (wrong!)
- Asus PRIME X370-PRO w/ BIOS 3402 ---> reports 64GB max. installable capacity (correct!)
- Asus PRIME X370-PRO w/ BIOS 4011 ---> reports 256GB max. installable capacity (wrong!)
...My guess is one of the AGESA updates is doing this
Problems adding new repository to dockerMan
-
-
-
-
-
in Prereleases
Posted
Changed Status to Retest