Unraid OS Version 7.0.0-beta.1 available

1 minute ago, J000K3R said:

But as you can see in the screenshot, this is my test unraid on which nothing is currently on it except a Windows Server ISO.

Your "isos" share is set to be on a pool named "cache" but you don't have one, so correct that. Did you add/remove pools as part of testing?

14 hours ago, itimpi said:

I have a feeling that there is unlikely to be any easy way to create a use friendly dashboard for a mobile due to its limited screen resolution and the fact it is browser based.

 

There are apps that run natively on iOS and Android (such as Control/R) and that is quite probably the only way to realistically achieve this as they can design their own UI.

 

 

There are many web based applications or websites that will be rendered in a mobile view depending on the screen size/resolution/type of the device used. It really is standard behaviour nowadays, and web frameworks offer many hooks to support this.

 

A 3rd party application to emulate a web frontend will always be a worse solution in comparison to native support. I really don't expect everything to be rendered perfectly on mobile, does not even make sense, but at least the major pages and the home dashboard really should be rendered correctly.

2 hours ago, Kilrah said:

Your "isos" share is set to be on a pool named "cache" but you don't have one, so correct that. Did you add/remove pools as part of testing?

Thanks my mistake sorry!!

19 minutes ago, sir_storealot said:

There are many web based applications or websites that will be rendered in a mobile view depending on the screen size/resolution/type of the device used. It really is standard behaviour nowadays, and web frameworks offer many hooks to support this.

i agree to that statement - but what I meant that there is no easy way to re-engineer the current Unraid GUI to use such a framework.  You really need the system to be engineered from the outset with that in mind. There is also the fact that quite a bit of the GUI ends up being rendered as a result of plugin installation (which are provided by third parties), and changing any of the current assumptions about the GUI would probably break them.   

 

I also suspect that from a Limetech perspective there is little need in most cases to put the effort into such a re-engineering job.  Since Unraid is designed to run as a server the vast majority of the time it will be administered at the detailed level from a system with better resolution than a mobile can provide.   That is where I can see apps like control/R coming in as they can provide basic view/stop/start capabilities without the need to support the full GUI. 

I'm sure I am over looking something here... I select remove snapshot and i get an error Image Currently active for this domain. The restore works fine.  Thanks

Is there a way to disable the "set favorite" option? Ive clicked on the heart on accident multiple times now and i personally dont need that feature.

Just now, Mainfrezzer said:

Is there a way to disable the "set favorite" option? Ive clicked on the heart on accident multiple times now and i personally dont need that feature.

Goto favorites tab there you can delete using bin icon

51 minutes ago, sobesjm said:

I'm sure I am over looking something here... I select remove snapshot and i get an error Image Currently active for this domain. The restore works fine.  Thanks

You cannot delete snapshot if the active disk path for vm.

The Proceed button in the confirmation dialog box from the Dashboard page links to CPU pinning settings. Same for the next button: Halting the system. 

 

When Docker is enabled, the system will not reboot, not even from a SSH session with command

reboot -h

 

The UI becomes unresponsive.

8 minutes ago, SimonF said:

Goto favorites tab there you can delete using bin icon

i know where i can delete them. i just want the whole feature disabled.

The heart is an active annoyance and an enemy of userfriendlyness in terms of the clickable size of the icon.
 

 

 

4 minutes ago, Mainfrezzer said:

i know where i can delete them. i just want the whole feature disabled.

The heart is an active annoyance and an enemy of userfriendlyness in terms of the clickable size of the icon.
 

 

Sorry miss read. I dont believe option to disable currently.

19 minutes ago, Mainfrezzer said:

i know where i can delete them. i just want the whole feature disabled.

The heart is an active annoyance and an enemy of userfriendlyness in terms of the clickable size of the icon.
 

 

Just done some testing it would need conditions adding to the settings and tools page. WIll check with team on it.

fractal-diagnostics-20240630-0018.zipfractal-diagnostics-20240630-0018.zipfractal-diagnostics-20240630-0018.zipI get the following in my system log:

 

Jun 29 18:08:24 Fractal kernel: kernel tried to execute NX-protected page - exploit attempt? (uid: 0)
Jun 29 18:08:24 Fractal kernel: BUG: unable to handle page fault for address: ffff888343959d88
Jun 29 18:08:24 Fractal kernel: #PF: supervisor instruction fetch in kernel mode
Jun 29 18:08:24 Fractal kernel: #PF: error_code(0x0011) - permissions violation
Jun 29 18:08:24 Fractal kernel: PGD 5e01067 P4D 5e01067 PUD 80000003400001e3 
Jun 29 18:08:24 Fractal kernel: Oops: 0011 [#1] PREEMPT SMP NOPTI
Jun 29 18:08:24 Fractal kernel: CPU: 6 PID: 1358 Comm: arc_prune Tainted: P           O       6.8.12-Unraid #3
Jun 29 18:08:24 Fractal kernel: Hardware name: ASUS System Product Name/PRIME H510M-E, BIOS 2402 12/18/2023
Jun 29 18:08:24 Fractal kernel: RIP: 0010:0xffff888343959d88
Jun 29 18:08:24 Fractal kernel: Code: ad de 80 96 95 43 83 88 ff ff 00 f0 32 e8 83 88 ff ff 46 67 ce a0 ff ff ff ff 00 98 ee c3 82 88 ff ff 40 00 00 00 00 00 00 00 <48> a2 98 e6 82 88 ff ff 05 02 00 03 00 00 00 00 00 00 00 00 00 00
Jun 29 18:08:24 Fractal kernel: RSP: 0018:ffffc9000112bd30 EFLAGS: 00010246
Jun 29 18:08:24 Fractal kernel: RAX: ffff888343959d88 RBX: ffff88833dda8000 RCX: 0000000000000011
Jun 29 18:08:24 Fractal kernel: RDX: ffffffffa10a44b8 RSI: ffffc9000112bd68 RDI: ffff888357df6200
Jun 29 18:08:24 Fractal kernel: RBP: ffffc9000112bdcc R08: 0000000000000000 R09: 0000000000150014
Jun 29 18:08:24 Fractal kernel: R10: 0000000000000000 R11: 0000000000000020 R12: 00000000000059a3
Jun 29 18:08:24 Fractal kernel: R13: ffff888357df6200 R14: ffff888106abfcc0 R15: ffff88810f5b3180
Jun 29 18:08:24 Fractal kernel: FS:  0000000000000000(0000) GS:ffff88883e780000(0000) knlGS:0000000000000000
Jun 29 18:08:24 Fractal kernel: CS:  0010 DS: 0000 ES: 0000 CR0: 0000000080050033
Jun 29 18:08:24 Fractal kernel: CR2: ffff888343959d88 CR3: 00000001d3324004 CR4: 00000000003706f0
Jun 29 18:08:24 Fractal kernel: Call Trace:
Jun 29 18:08:24 Fractal kernel: <TASK>
Jun 29 18:08:24 Fractal kernel: ? __die_body+0x1a/0x5c
Jun 29 18:08:24 Fractal kernel: ? page_fault_oops+0x332/0x37f
Jun 29 18:08:24 Fractal kernel: ? fixup_exception+0x22/0x250
Jun 29 18:08:24 Fractal kernel: ? exc_page_fault+0xf2/0x116
Jun 29 18:08:24 Fractal kernel: ? asm_exc_page_fault+0x22/0x30
Jun 29 18:08:24 Fractal kernel: ? zfs_prune+0xec/0x2ec [zfs]
Jun 29 18:08:24 Fractal kernel: ? put_cpu_partial+0x62/0x8e
Jun 29 18:08:24 Fractal kernel: ? zpl_prune_sb+0x32/0x50 [zfs]
Jun 29 18:08:24 Fractal kernel: ? arc_prune_task+0x1b/0x2e [zfs]
Jun 29 18:08:24 Fractal kernel: ? taskq_thread+0x2d4/0x3c1 [spl]
Jun 29 18:08:24 Fractal kernel: ? __pfx_default_wake_function+0x10/0x10
Jun 29 18:08:24 Fractal kernel: ? __pfx_taskq_thread+0x10/0x10 [spl]
Jun 29 18:08:24 Fractal kernel: ? kthread+0xf4/0xff
Jun 29 18:08:24 Fractal kernel: ? __pfx_kthread+0x10/0x10
Jun 29 18:08:24 Fractal kernel: ? ret_from_fork+0x21/0x36
Jun 29 18:08:24 Fractal kernel: ? __pfx_kthread+0x10/0x10
Jun 29 18:08:24 Fractal kernel: ? ret_from_fork_asm+0x1b/0x30
Jun 29 18:08:24 Fractal kernel: </TASK>
Jun 29 18:08:24 Fractal kernel: Modules linked in: nft_fib_inet nft_fib_ipv4 nft_fib_ipv6 nft_fib nft_reject_inet nf_reject_ipv4 nf_reject_ipv6 nft_reject nft_ct nft_chain_nat ip_set nf_tables xt_nat xt_tcpudp xt_conntrack xt_MASQUERADE nf_conntrack_netlink nfnetlink xfrm_user xfrm_algo iptable_nat nf_nat nf_conntrack nf_defrag_ipv6 nf_defrag_ipv4 xt_addrtype br_netfilter bridge stp llc nfsd auth_rpcgss oid_registry lockd grace sunrpc bluetooth ecdh_generic ecc md_mod tcp_diag inet_diag ip6table_filter ip6_tables iptable_filter ip_tables x_tables efivarfs macvtap macvlan tap intel_rapl_common x86_pkg_temp_thermal intel_powerclamp zfs(PO) coretemp kvm_intel i915 kvm crct10dif_pclmul crc32_pclmul crc32c_intel spl(O) ghash_clmulni_intel iosf_mbi drm_buddy sha512_ssse3 ttm sha256_ssse3 i2c_algo_bit sha1_ssse3 aesni_intel drm_display_helper crypto_simd cryptd drm_kms_helper input_leds rapl mei_hdcp mei_pxp wmi_bmof intel_cstate drm nvme intel_uncore hid_apple e1000e led_class intel_gtt mei_me i2c_i801 nvme_core i2c_smbus agpgart mei ahci
Jun 29 18:08:24 Fractal kernel: i2c_core libahci thermal fan tpm_crb video tpm_tis tpm_tis_core wmi tpm backlight button acpi_tad acpi_pad
Jun 29 18:08:24 Fractal kernel: CR2: ffff888343959d88
Jun 29 18:08:24 Fractal kernel: ---[ end trace 0000000000000000 ]---
Jun 29 18:08:24 Fractal kernel: RIP: 0010:0xffff888343959d88
Jun 29 18:08:24 Fractal kernel: Code: ad de 80 96 95 43 83 88 ff ff 00 f0 32 e8 83 88 ff ff 46 67 ce a0 ff ff ff ff 00 98 ee c3 82 88 ff ff 40 00 00 00 00 00 00 00 <48> a2 98 e6 82 88 ff ff 05 02 00 03 00 00 00 00 00 00 00 00 00 00
Jun 29 18:08:24 Fractal kernel: RSP: 0018:ffffc9000112bd30 EFLAGS: 00010246
Jun 29 18:08:24 Fractal kernel: RAX: ffff888343959d88 RBX: ffff88833dda8000 RCX: 0000000000000011
Jun 29 18:08:24 Fractal kernel: RDX: ffffffffa10a44b8 RSI: ffffc9000112bd68 RDI: ffff888357df6200
Jun 29 18:08:24 Fractal kernel: RBP: ffffc9000112bdcc R08: 0000000000000000 R09: 0000000000150014
Jun 29 18:08:24 Fractal kernel: R10: 0000000000000000 R11: 0000000000000020 R12: 00000000000059a3
Jun 29 18:08:24 Fractal kernel: R13: ffff888357df6200 R14: ffff888106abfcc0 R15: ffff88810f5b3180
Jun 29 18:08:24 Fractal kernel: FS:  0000000000000000(0000) GS:ffff88883e780000(0000) knlGS:0000000000000000
Jun 29 18:08:24 Fractal kernel: CS:  0010 DS: 0000 ES: 0000 CR0: 0000000080050033
Jun 29 18:08:24 Fractal kernel: CR2: ffff888343959d88 CR3: 00000001d3324004 CR4: 00000000003706f0
Jun 29 18:08:24 Fractal kernel: note: arc_prune[1358] exited with irqs disabled

 

I only have an Intel 10th gen i3 in my system.

Actually, it may be Docker related, as I saw the message appear in the log after enabling Docker.

Edited Saturday at 10:26 PM by bpwats
maybe Docker related

3 hours ago, SimonF said:

Just done some testing it would need conditions adding to the settings and tools page. WIll check with team on it.

would be lovely.




For anyone looking for a quick fix. 

The following filter in ublock origin or any other blocker will help out for the moment

Quote

UNRAIDADRESS##.fa.fa-heart.favo
 

that will get rid of the heart

Hi,

 

Any idea what's going on? I have the latest beta. I am using both IPv4 and IPv6 with macvlan and host access enabled. 

 

Jun 29 04:11:25 UNRAID dhcpcd[1539]: eth0: adding address fd11:8a45:f39:54d:2d0:b4ff:fe02:2cf2/64
Jun 29 04:11:25 UNRAID dhcpcd[1539]: eth0: adding route to fd11:8a45:f39:54d::/64
Jun 29 04:11:25 UNRAID avahi-daemon[11257]: Registering new address record for fd11:8a45:f39:54d:2d0:b4ff:fe02:2cf2 on eth0.*.
Jun 29 04:12:37 UNRAID avahi-daemon[11257]: Withdrawing address record for fd11:8a45:f39:54d:2d0:b4ff:fe02:2cf2 on eth0.
Jun 29 04:42:36 UNRAID dhcpcd[1539]: eth0: expired address fd11:8a45:f39:54d:2d0:b4ff:fe02:2cf2/64
Jun 29 04:42:36 UNRAID dhcpcd[1539]: eth0: part of a Router Advertisement expired
Jun 29 04:42:36 UNRAID dhcpcd[1539]: eth0: deleting route to fd11:8a45:f39:54d::/64
Jun 29 09:29:58 UNRAID dhcpcd[1539]: eth0: adding address fd11:8a45:f39:54d:2d0:b4ff:fe02:2cf2/64
Jun 29 09:29:58 UNRAID avahi-daemon[11257]: Registering new address record for fd11:8a45:f39:54d:2d0:b4ff:fe02:2cf2 on eth0.*.
Jun 29 09:29:58 UNRAID dhcpcd[1539]: eth0: adding route to fd11:8a45:f39:54d::/64
Jun 29 09:30:27 UNRAID avahi-daemon[11257]: Withdrawing address record for fd11:8a45:f39:54d:2d0:b4ff:fe02:2cf2 on eth0.
Jun 29 10:00:27 UNRAID dhcpcd[1539]: eth0: expired address fd11:8a45:f39:54d:2d0:b4ff:fe02:2cf2/64
Jun 29 10:00:27 UNRAID dhcpcd[1539]: eth0: part of a Router Advertisement expired
Jun 29 10:00:27 UNRAID dhcpcd[1539]: eth0: deleting route to fd11:8a45:f39:54d::/64

 

I noticed on one of my servers the following:

un 29 03:04:22 Tower sSMTP[1608191]: Authorization failed (535 5.7.8  https://support.google.com/mail/?p=BadCredentials ffacd0b85a97d-3675a0d90casm3515521f8f.32 - gsmtp)

 

According to the timeline it showed right after trim was finished:

Jun 29 03:04:21 Tower root: /etc/libvirt: 919.8 MiB (964440064 bytes) trimmed on /dev/loop3
Jun 29 03:04:21 Tower root: /var/lib/docker: 18.3 GiB (19657920512 bytes) trimmed on /dev/loop2
Jun 29 03:04:21 Tower root: /mnt/database: 1.5 TiB (1616786391040 bytes) trimmed on /dev/sdb1
Jun 29 03:04:21 Tower root: /mnt/cache: 850.1 GiB (912759029760 bytes) trimmed on /dev/nvme0n1p1
Jun 29 03:04:21 Tower sSMTP[1608191]: Creating SSL connection to host
Jun 29 03:04:21 Tower sSMTP[1608191]: SSL connection using TLS_AES_256_GCM_SHA384

 

Checking notification settings I don't have anything enabled for email:

 

Diagnostics attached

 

tower-diagnostics-20240630-0035.zip

On 6/28/2024 at 2:00 PM, SimonF said:

needs to support libsslv3 for 7 I believe

So i have to wait for a python or unraid update?

I just noticed something very funky going on with the docker page. Same happens with the unlimited width option

16 hours ago, bpwats said:

The Proceed button in the confirmation dialog box from the Dashboard page links to CPU pinning settings. Same for the next button: Halting the system.

Not sure I follow, can you post a screenshot?

 

16 hours ago, bpwats said:

When Docker is enabled, the system will not reboot, not even from a SSH session with command

This is not normal, please create a new thread and post the diagnostics.

 

16 hours ago, bpwats said:

Actually, it may be Docker related, as I saw the message appear in the log after enabling Docker.

 

That looks like a problem with that zfs filesystem, and if it happens after enabling docker it's probably where the docker image/folder resides, recommend backing up and recreating that pool, running memtest may also be a good idea.

11 hours ago, thecode said:

According to the timeline it showed right after trim was finished:

It wouldn't explain why it's trying to send an email, but it's probably because it's trying to TRIM the flash drive and failing, please post the output of:

 

fstrim -v -a

 

Apologies if this has been asked and answered already, though I couldn't find anything with a search.

 

Does Unraid 7.0.* release contain the Intel ARC Graphics cards drivers?

2 minutes ago, dalben said:

Apologies if this has been asked and answered already, though I couldn't find anything with a search.

 

Does Unraid 7.0.* release contain the Intel ARC Graphics cards drivers?

Yes as in 6.8 kernel

2 hours ago, JorgeB said:

Not sure I follow, can you post a screenshot?

 

This is not normal, please create a new thread and post the diagnostics.

 

I cannot post a screen shot. Like I said, you would see the reboot confirmation dialog. Hammer the Proceed button and after several clicks the CPU pinning settings. It sounds like very abnormal behaviour indeed.

This would happen after the kernel error I posted. Diagnostics file is included already.
The error really messes up emhttpd: becomes unresponsive, will not reboot. Does not respond to reboot -h in SSH session. Containers keep running though. A hard reset is needed.

When this error has not occured yet, the webgui runs snappy and reboot buttons function as expected. Nice touch to provide more info during the reboot process. 
 

Initially I thought the arc reference had to do with Intel Arc support, but rather it is an OpenZFS thing.
I have the maximum 32GB memory in my system. To rule out hardware RAM errors, I ran the included new MemTest for over 2 hours, showing 2 complete passes and no errors.

My cache_nvme 1TB is formatted as ZFS, as well as 3 8TB cache_ssd EVO as RaidZ, giving 15TB to put files on.

 

Please read this and related links in that issue. As I understand things, ZFS aggressively takes RAM and does play nice with the kernel, which only sees 5 GB allocated or so.

I reverted to 6.12.10. Problem went away. So it has to do something with the updated versions under the hood.

20 hours ago, bpwats said:

The Proceed button in the confirmation dialog box from the Dashboard page links to CPU pinning settings

Initially you didn't mention that this was after clicking reboot, so it's likely related to the zfs issue.