-
Posts
802 -
Joined
-
Last visited
Content Type
Profiles
Forums
Downloads
Store
Gallery
Bug Reports
Documentation
Landing
Report Comments posted by IamSpartacus
-
-
20 hours ago, bonienl said:
There are two fan entries reported in the list, this is the reason the fans section is present on the dashboard.
I see. So is it safe to assume that everyone system will have that section on the dash since I'd assume every system has fan sensors?
-
23 hours ago, bonienl said:
What is the output of
sensors -uA
Quoteroot@BEAST-BACKUP:~# sensors -uA
power_meter-acpi-0
power1:
power1_average: 4294967.295
power1_average_interval: 4294967.295acpitz-acpi-0
temp1:
temp1_input: 27.800
temp1_crit: 119.000
temp2:
temp2_input: 29.800
temp2_crit: 119.000nct6776-isa-0290
Vcore:
in0_input: 0.000
in0_min: 0.000
in0_max: 1.744
in0_alarm: 0.000
in0_beep: 0.000
in1:
in1_input: 0.136
in1_min: 0.000
in1_max: 0.000
in1_alarm: 1.000
in1_beep: 0.000
AVCC:
in2_input: 3.376
in2_min: 0.000
in2_max: 0.000
in2_alarm: 1.000
in2_beep: 0.000
+3.3V:
in3_input: 3.360
in3_min: 0.000
in3_max: 0.000
in3_alarm: 1.000
in3_beep: 0.000
in4:
in4_input: 0.496
in4_min: 0.000
in4_max: 0.000
in4_alarm: 1.000
in4_beep: 0.000
in5:
in5_input: 1.856
in5_min: 0.000
in5_max: 0.000
in5_alarm: 1.000
in5_beep: 0.000
in6:
in6_input: 1.696
in6_min: 0.000
in6_max: 0.000
in6_alarm: 1.000
in6_beep: 0.000
3VSB:
in7_input: 3.392
in7_min: 0.000
in7_max: 0.000
in7_alarm: 1.000
in7_beep: 0.000
Vbat:
in8_input: 3.152
in8_min: 0.000
in8_max: 0.000
in8_alarm: 1.000
in8_beep: 0.000
fan1:
fan1_input: 0.000
fan1_min: 0.000
fan1_alarm: 0.000
fan1_beep: 0.000
fan1_pulses: 2.000
fan2:
fan2_input: 0.000
fan2_min: 0.000
fan2_alarm: 0.000
fan2_beep: 0.000
fan2_pulses: 2.000
SYSTIN:
temp1_input: 0.000
temp1_max: 0.000
temp1_max_hyst: 0.000
temp1_alarm: 0.000
temp1_type: 4.000
temp1_offset: 0.000
temp1_beep: 0.000
CPUTIN:
temp2_input: -61.500
temp2_max: 80.000
temp2_max_hyst: 75.000
temp2_alarm: 0.000
temp2_type: 4.000
temp2_offset: 0.000
temp2_beep: 0.000
AUXTIN:
temp3_input: -13.500
temp3_max: 80.000
temp3_max_hyst: 75.000
temp3_alarm: 0.000
temp3_type: 4.000
temp3_offset: 0.000
temp3_beep: 0.000
PCH_CHIP_TEMP:
temp7_input: 0.000
PCH_CPU_TEMP:
temp8_input: 0.000
PCH_MCH_TEMP:
temp9_input: 0.000
intrusion0:
intrusion0_alarm: 0.000
intrusion0_beep: 0.000
intrusion1:
intrusion1_alarm: 0.000
intrusion1_beep: 0.000
beep_enable:
beep_enable: 0.000coretemp-isa-0000
Package id 0:
temp1_input: 36.000
temp1_max: 80.000
temp1_crit: 100.000
temp1_crit_alarm: 0.000
Core 0:
temp2_input: 31.000
temp2_max: 80.000
temp2_crit: 100.000
temp2_crit_alarm: 0.000
Core 1:
temp3_input: 36.000
temp3_max: 80.000
temp3_crit: 100.000
temp3_crit_alarm: 0.000 -
Sorry a little confused by your response. The dashboard will show the Airflow section regardless of the plugin being installed if fans are present in the system? I used to have the plugin installed but it's been gone for over a month. Multiple reboots since then.
-
11 minutes ago, johnnie.black said:
Thanks you.
10 minutes ago, johnnie.black said:Also did you try v6.8 final? Kernel went back to 4.19
Yes I just did try. Tried with 3 different USB flash drives as well. No change. So it doesn't appear to be related to a specific kernel.
This where it gets to before it reboots the server.
-
On 11/15/2019 at 3:00 PM, BoarAnt said:
Correct. At the grub menu, press the Tab button to enable editing, and add nomodeset as an additional argument at the end of the linux line and press return to boot. Once unraid is up, be sure to go into the flash drive and edit those lines in your grub.cfg permanently.
Just confirming that 'nomodeset' does not allow my EPYC 7302p server to boot in RC4-RC6, not in any mode (I tried all 4).
-
17 minutes ago, BoarAnt said:
I'm not sure if you've done this yet, but have you added 'nomodeset' to the grub boot options yet? Most EPYC server boards have an aspeed bmc chip (mine is the ast2500) which interfered on boot. My unraid setup didn't boot until I added that in my grub configs.
I have not. How exactly is that done? Just add nomodeset in each of the Syslinux configs?
-
15 hours ago, BoarAnt said:
I'm using a Gigabyte MZ32-AR0, and I upgraded from the stable build (6.7.2).
Thanks for the info. Not sure what could be causing my issue then. Even a fresh vanilla install on a new USB doesn't boot. Maybe I'll try booting a different Linux distro using the same kernel to see if it is some issue with my board and the latest kernel.
-
5 hours ago, BoarAnt said:
I'm using an EPYC 7452 on RC5 without issues.
With what motherboard? And what version did you upgrade from?
-
If anyone successfully updates to RC5 using an EPYC 7002 series CPU please let me know. I'm in a holding pattern.
-
3 hours ago, Lev said:
I was also going to recommend this @IamSpartacus. I've experienced something similar when I was booting ESXi and switching EFI / Legacy boot resolved it.
Yes that was one of the first things I tried since it was a quick and easy try. No dice.
-
18 hours ago, cybrnook said:
@IamSpartacus long shot, do you have any special kernel parameters you are passing along besides the default kernel values? I assume not unless you added custom values to both standard and gui modes lines.
Didnt think of that. I am doing PCIE ACS override and isolating some cores.
-
7 minutes ago, limetech said:
AMD microcode is distributed as part of "kernel firmware":
https://git.kernel.org/pub/scm/linux/kernel/git/firmware/linux-firmware.git/log/
We have been updating kernel firmware with each -rc. You can look at change log to see that after -rc3 there were 2 updates then you can look at above link to see that AMD microcode as updated. Probably AMD broke something.
I see there was this on 10-22. My guess is you are right and AMD broke something. Hopefully it gets patched in a future kernel firmware update.
2019-10-22 linux-firmware: Update AMD cpu microcode20191022
-
1 minute ago, jbartlett said:
If you're feeling spunky, try downgrading your BIOS a version.
Not an option, latest BIOS version fixed a major issue so it's not worth even going down that path.
-
48 minutes ago, itimpi said:
Try booting in GUI mode. There have been reports of some systems only being able to boot in GUI mode although the cause has never been udentified
30 minutes ago, jbartlett said:I don't recall reading if you had or not but did you check for a BIOS update?
Just tried GUI mode, no dice. Reset the CMOS, no dice. I'm on the latest version of my BIOS which is pretty new. I'm stuck on RC3 for the foreseeable future.
-
6 minutes ago, phbigred said:
See if the system pings even being stuck at that point. Mine booted but was stuck at that screen. I've seen an issue post bios flash for Ryzen 1.0.0.3 Abba. Ended up clearing the CMOS and that corrected it.
It's definitely not pingable, I'm watching the system via IPMI and it just resets the server completely back to the BIOS screen.
-
Fresh install with the same USB did not work. Trying a fresh install with a new USB. That should tell me if it's some kind of comparability with the new kernel. I am running an EPYC 7302p system so maybe it's too new for the kernel? RC3 works without issue though.
I should also note I had this same issue trying to upgrade to RC4 so that's when the change that is affecting me happened.
EDIT: Yup, even a brand new USB with a fresh install of RC5 won't boot. Guess I'm stuck on RC3. Will providing diagnostics while RC3 is installed help in any way?
-
14 minutes ago, trurl said:
Checkdisk on flash. Copy previous folder to root. Try upgrade again.
I've tried the update 3 times (with copying previous back to flash each time). Also tried booting to safe mode, no difference. But yea I'll do a checkdisk on the flash.
EDIT: Windows found no errors on the flash drive with a chkdsk. Is there any where I can directly download RC5 so I can install it fresh on a USB to test?
EDIT 2: Found the direct DL link. Gonna test installing it fresh.
-
-
34 minutes ago, sittingmongoose said:
None, Auto, Kyber, BFQ, MQ-Deadline are the 5 options I see in RC5.
Yes but what do they each do is my question?
32 minutes ago, limetech said:I've never seen those messages but seems to indicate something seriously messed up.
Also what is "mover tuner"?
It's a plugin that allows for further tuning of the mover. These are the settings I'm using and I'm not having any issues with the mover affecting the rest of my system since upgrading to rc1. Before 6.8rc1 I was having lots of issues.
-
Is there any info on what each of the different options in `Tunable (scheduler)` are supposed to do?
-
2 hours ago, sittingmongoose said:
I cant do any file transfers as the server is remotely located. I actually never saw that file transfer issue. I had/have a problem streaming off the array. Its reproducible for me and I have seen a handful of other users running newer RCs have the same issue. Users that have posted in the slow array performance thread that was set to "solved", and also in the RC3/4/5 release threads.
For me to reproduce it, all I have to do is start parity check and I can no longer stream videos without buffering. If you want to be sure to trigger it, you can run mover and parity check at once and try to stream. I am able to run both mover and parity check while still being able to use plex on RC1.
I have 4 streams going right now including a 4k direct play (over 100Mbps bandwidth). I started the mover and none of the streams are being affected. I'm running rc3 currently. I will test parity check next but need mover to finish because I have mover set to be disabled during parity checks. I have the mover tuner plugin set to enable turbo write during moves so all my disks are spun up and being read at over 160MB/s during the mover process and still no streams are being affected.
EDIT: Can confirm parity check does not affect my streams either.
-
3 hours ago, sittingmongoose said:
I am testing the same way. If I turn on parity check and mover, it’s completely unusable.
in rc1, pretty much nothing stoped streams from working. It did slow down mover and parity checks but that’s expected.
Make sure your CPU Scaling Governor is not set to Power Save if you're using the Tips and Tweaks plugin. I found that while that setting is supposed to keep the CPU frequency at it's lowest setting regardless of load, in 6.7.x and earlier it was actually still ramping up the CPU frequency on demand. Now in 6.8 is keeps the CPU at the minimum frequency. I've since set the governor to On Demand and it's working as expected. I've heard of other users with very power system performance in 6.8 with the CPU Scaling Governor set to Power Save and switching to On Demand fixed it.
- 2
-
Not sure if this is a 6.8RC1 issue or some other temporary docker image repository issue but all my dockers shows they have an update and won't update. The previous script fix for this in 6.7.2 doesn't fix it. Diagnostics attached.
-
My fear is we dont see 6.8 until they figure out the SQLite issue which is anyone's guess.
Unraid OS version 6.9.0-beta25 available
-
-
-
-
-
in Prereleases
Posted
Does anyone know if NFS v4 is/will be supported in 6.9?