December 3, 20187 yr Can you post a screenshot of your disk settings page? Green color = disk utilization below warning level Orange color = disk utilization between warning and critical level Red color = disk utilization above critical level Edited December 3, 20187 yr by bonienl
December 3, 20187 yr 3 hours ago, limetech said: Probably these will get merged into 4.19 since 4.19 is a LTS (long-term support) kernel. Let's be real, Unraid moves fast now. No more LTS for us
December 3, 20187 yr Author 21 minutes ago, Dazog said: Let's be real, Unraid moves fast now. No more LTS for us "support", as in linux kernel longterm support, means they will back-merge bug fixes only. With rare exceptions, no new device support, not even new PCI ID's for device which use the same driver as existing devices. Also, in the past I've been concerned about btrfs development - the line between a "bug fix" which will get back-ported and "improvement", which is not back-ported, is has not been that well defined. Meaning, some "fixes" required more code changes than developers were comfortable about trying to back-port. These days, I think that has largely settled down. Bottom line is that we need to try and keep up-to-date with kernels in order to support the latest hardware. Very likely Unraid 6.7.0-rc1 will be released with 4.19 kernel, but possible we move to 4.20 kernel before 6.7 stable is released.
December 4, 20187 yr Well there goes nearly a month of continuous uptime. Updating now... EDIT1: Updated. Nothing seeming out of sorts yet. Edited December 4, 20187 yr by urbanracer34
December 4, 20187 yr 1 hour ago, limetech said: "support", as in linux kernel longterm support, means they will back-merge bug fixes only. With rare exceptions, no new device support, not even new PCI ID's for device which use the same driver as existing devices. Also, in the past I've been concerned about btrfs development - the line between a "bug fix" which will get back-ported and "improvement", which is not back-ported, is has not been that well defined. Meaning, some "fixes" required more code changes than developers were comfortable about trying to back-port. These days, I think that has largely settled down. Bottom line is that we need to try and keep up-to-date with kernels in order to support the latest hardware. Very likely Unraid 6.7.0-rc1 will be released with 4.19 kernel, but possible we move to 4.20 kernel before 6.7 stable is released. It appears almost all the file system work is done on whatever the current mainline is. At least the change logs I have read for every release in the past few months. I only see bug fixes go back toward the LTS. Most of the performance and new features added to Btrfs are only in the next mainline, not backported to previous LTS release. Example: http://lkml.iu.edu/hypermail/linux/kernel/1810.2/05630.html Again. You guys are moving fast to patch security and microcode. Very happy but loud end user here PS. New AMD stuff always needs latest kernel's now-a days. Wait until people buy upcoming 64 core machines for Unraid/docker setups. Inform Linus his video looks weak now and he needs to do a new all NVME SSD unraid video
December 4, 20187 yr 7 hours ago, bonienl said: Can you post a screenshot of your disk settings page? Green color = disk utilization below warning level Orange color = disk utilization between warning and critical level Red color = disk utilization above critical level Disk settings attached. 70% does explain orange on disk17 (my second screenshot), I see. Main tab is reasonable. But what about the red disk19 and Cache disk on the Dashboard (first screenshot)? Edited December 4, 20187 yr by hawihoney
December 4, 20187 yr after the issue with 6.6.4, I'm worried about installing it so soon, how long should I wait before it's safe?
December 4, 20187 yr 1 hour ago, hawihoney said: But what about the red disk19 and Cache disk on the Dashboard Try the following: Go to Main -> Disk 19 -> Settings Make a settings change (e.g. change warning level) and undo this change. It will allow settings to be saved. Check if there is a difference in display.
December 4, 20187 yr 2 hours ago, takkkkkkk said: after the issue with 6.6.4, I'm worried about installing it so soon, how long should I wait before it's safe? It's safe after 666 days from release....
December 4, 20187 yr 19 hours ago, limetech said: but we're about to start Unraid 6.7 public -rc When can we expect this to be public available?
December 4, 20187 yr upgraded process on the ml30 g9 occurred without issue. This is kind of nice: colors.mov I mean, it's not as nice as multiple cache pools....but it's still nice.
December 4, 20187 yr 6 hours ago, bonienl said: Try the following: Go to Main -> Disk 19 -> Settings Make a settings change (e.g. change warning level) and undo this change. It will allow settings to be saved. Check if there is a difference in display. Yes, that worked. Colors on Dashboard are correct now. Can you please elaborate a little bit. Is this a bug or WAD?
December 4, 20187 yr 1 hour ago, 1812 said: colors.mov what the hell were you doing at that time? pretty big numbers on each core. and how to set the display of the core usage to these small line bars? Edited December 4, 20187 yr by s.Oliver
December 4, 20187 yr 3 hours ago, 1812 said: upgraded process on the ml30 g9 occurred without issue. This is kind of nice: colors.mov I mean, it's not as nice as multiple cache pools....but it's still nice. Is this the Dashboard??? And where comes the color from? EDIT: Ah, i see... the color comes automaticly 😉 EDIT2: Would be nice if the gray bar could be green 👍 Edited December 4, 20187 yr by Zonediver
December 4, 20187 yr Upgraded from 6.6.5 to 6.6.6 without issue. Log file looks clean; up-time of ~12 hours, so far.
December 4, 20187 yr will upgrade when i got some time free, or maybe i will wait for the 4.19 kernel, because i have heart that in that version the "Vega reset bug" is fixed? (someone who can confirm that? :S )
December 4, 20187 yr Upgrade not successful. I currently have 6.5.3, but i can't upgrade to anything higher than that. System just reboots after saying "BZRoot.......OK". Starting in GUI Safe mode works, but nothing else does. What i have tried: Update BIOS Different BIOS UEFI settings Updating syslinux.exe Adding acpi=off nolapic noapic to the syslinux.cfg Different USB drive Both 6.6.0 RC4 and 6.6.6 Don't know what to do next. 😕 My Specs are in the signature.
December 4, 20187 yr When array in stop state, GUI "Slots" broken ? http://192.168.X.X/webGui/images/sum.png Chrome Edge
December 4, 20187 yr 4 hours ago, s.Oliver said: what the hell were you doing at that time? pretty big numbers on each core. and how to set the display of the core usage to these small line bars? I was compiling the hp proliant bzimage while running my pfsense firewall, and hosting an external facing cloud. It's usually not that active. Usually runs between 10-30% I'm using one of the baked in themes.
Join the conversation
You can post now and register later. If you have an account, sign in now to post with your account.
Note: Your post will require moderator approval before it will be visible.