Skip to content
View in the app

A better way to browse. Learn more.
Unraid

A full-screen app on your home screen with push notifications, badges and more.

To install this app on iOS and iPadOS
  1. Tap the Share icon in Safari
  2. Scroll the menu and tap Add to Home Screen.
  3. Tap Add in the top-right corner.
To install this app on Android
  1. Tap the 3-dot menu (⋮) in the top-right corner of the browser.
  2. Tap Add to Home screen or Install app.
  3. Confirm by tapping Install.
Unraid Summer Sale in live: 20% off Starter and Unleashed + buy one, get one 50% off

johner

Members

  • Joined

  • Last visited

View Profile Find content

Everything posted by johner

  1. [6.9.2] Notifications can't be cleared if log on session has expired

    johner posted a report in Stable Releases
    If there are notifications queued up in the UI, but by the time you click x or clear all the log in session has expired, they look like they are clearing by disappearing, but then they all come back again. A page refresh (and subsequent re-log in/confirm the 'insecure' cert to continue) then they can be cleared. The expected behavior would be for the client side browser logic to detect it couldn't post the clear request to the server, and force a refresh/relogin or the like.

  2. [6.9.1] Kernal Panic(?) on array start (after cache config modification)

    johner posted a report in Stable Releases
    So I had everything running nice, 23 disk unraid, 2xraid1 nvme cache, 1xssd cache2. My original config had 4 slots for cache, but with only 2 drives. I stopped the array and shrunk the slots to 2, after restarting the array the machine froze. I couldn't access the logs via the web portal, but could see on the console (and via SSH) that something serious happened. I had to reboot to free it up and fortunately i have it set to not start the array as every start of the array it would freeze again with the same errors on the console (lots of hex pairs i think). I removed the cache config, recreated it (2 slots!), formatted again and now it works fine. I can no longer see the log entries, and don't have a copy - I assume due to the reboot? Is there an archive of them anywhere? I've not changed any logging settings. I would try to reproduce this and capture the logs but I'm getting pressure from the family to get it back up and running 🙂 Just happened again: Mar 25 10:00:46 Tower kernel: BUG: kernel NULL pointer dereference, address: 0000000000000000 Mar 25 10:00:46 Tower kernel: #PF: supervisor read access in kernel mode Mar 25 10:00:46 Tower kernel: #PF: error_code(0x0000) - not-present page Mar 25 10:00:46 Tower kernel: PGD 8000000169cbd067 P4D 8000000169cbd067 PUD 16a028067 PMD 0 Mar 25 10:00:46 Tower kernel: Oops: 0000 [#1] SMP PTI Mar 25 10:00:46 Tower kernel: CPU: 0 PID: 1402 Comm: btrfs Not tainted 5.10.21-Unraid #1 Mar 25 10:00:46 Tower kernel: Hardware name: Supermicro Super Server/X10SRH-CLN4F, BIOS 3.2 11/22/2019 Mar 25 10:00:46 Tower kernel: RIP: 0010:strcmp+0x2/0x1a Mar 25 10:00:46 Tower kernel: Code: ef 4c 89 c0 c3 48 89 f8 48 89 fa 8a 0a 48 89 d7 48 8d 52 01 84 c9 75 f3 31 d2 8a 0c 16 88 0c 17 48 ff c2 84 c9 75 f3 c3 31 c0 <8a> 14 07 3a 14 06 74 06 19 c0 83 c8 01 c3 48 ff c0 84 d2 75 eb 31 Mar 25 10:00:46 Tower kernel: RSP: 0018:ffffc900017f7d78 EFLAGS: 00010246 Mar 25 10:00:46 Tower kernel: RAX: 0000000000000000 RBX: ffff8881559c5800 RCX: 0000000000000000 Mar 25 10:00:46 Tower kernel: RDX: 0000000000000001 RSI: ffffffff81d9d9b5 RDI: 0000000000000000 Mar 25 10:00:46 Tower kernel: RBP: fffffffffffffffe R08: 0000000000000001 R09: 0000000000004000 Mar 25 10:00:46 Tower kernel: R10: ffffc900017f7f08 R11: 0000000000000000 R12: 0000000000000006 Mar 25 10:00:46 Tower kernel: R13: ffff88816a984000 R14: 0000000000000000 R15: 00000000000037b4 Mar 25 10:00:46 Tower kernel: FS: 00001498a6a99d40(0000) GS:ffff88903fa00000(0000) knlGS:0000000000000000 Mar 25 10:00:46 Tower kernel: CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033 Mar 25 10:00:46 Tower kernel: CR2: 0000000000000000 CR3: 0000000163544001 CR4: 00000000001706f0 Mar 25 10:00:46 Tower kernel: Call Trace: Mar 25 10:00:46 Tower kernel: btrfs_rm_device+0x10b/0x4ad Mar 25 10:00:46 Tower kernel: btrfs_ioctl+0xced/0x2c28 Mar 25 10:00:46 Tower kernel: ? getname_flags+0x44/0x146 Mar 25 10:00:46 Tower kernel: ? vfs_statx+0x72/0x105 Mar 25 10:00:46 Tower kernel: ? vfs_ioctl+0x19/0x26 Mar 25 10:00:46 Tower kernel: vfs_ioctl+0x19/0x26 Mar 25 10:00:46 Tower kernel: __do_sys_ioctl+0x51/0x74 Mar 25 10:00:46 Tower kernel: do_syscall_64+0x5d/0x6a Mar 25 10:00:46 Tower kernel: entry_SYSCALL_64_after_hwframe+0x44/0xa9 Mar 25 10:00:46 Tower kernel: RIP: 0033:0x1498a6bb1417 Mar 25 10:00:46 Tower kernel: Code: 00 00 90 48 8b 05 79 2a 0d 00 64 c7 00 26 00 00 00 48 c7 c0 ff ff ff ff c3 66 2e 0f 1f 84 00 00 00 00 00 b8 10 00 00 00 0f 05 <48> 3d 01 f0 ff ff 73 01 c3 48 8b 0d 49 2a 0d 00 f7 d8 64 89 01 48 Mar 25 10:00:46 Tower kernel: RSP: 002b:00007ffe3629bf38 EFLAGS: 00000246 ORIG_RAX: 0000000000000010 Mar 25 10:00:46 Tower kernel: RAX: ffffffffffffffda RBX: 00007ffe3629e0f0 RCX: 00001498a6bb1417 Mar 25 10:00:46 Tower kernel: RDX: 00007ffe3629cf60 RSI: 000000005000943a RDI: 0000000000000004 Mar 25 10:00:46 Tower kernel: RBP: 0000000000000001 R08: 1999999999999999 R09: 0000000000000000 Mar 25 10:00:46 Tower kernel: R10: 00001498a6c33ac0 R11: 0000000000000246 R12: 0000000000000002 Mar 25 10:00:46 Tower kernel: R13: 00007ffe3629cf60 R14: 0000000000000004 R15: 00007ffe3629e138 Mar 25 10:00:46 Tower kernel: Modules linked in: md_mod xt_MASQUERADE iptable_nat nf_nat ip6table_filter ip6_tables iptable_filter ip_tables igb i2c_algo_bit sb_edac x86_pkg_temp_thermal intel_powerclamp coretemp kvm_intel kvm crct10dif_pclmul crc32_pclmul crc32c_intel ghash_clmulni_intel a>Mar 25 10:00:46 Tower kernel: CR2: 0000000000000000 Mar 25 10:00:46 Tower kernel: ---[ end trace 7e2ba978fa8ddfc8 ]--- Mar 25 10:00:46 Tower kernel: RIP: 0010:strcmp+0x2/0x1a Mar 25 10:00:46 Tower kernel: Code: ef 4c 89 c0 c3 48 89 f8 48 89 fa 8a 0a 48 89 d7 48 8d 52 01 84 c9 75 f3 31 d2 8a 0c 16 88 0c 17 48 ff c2 84 c9 75 f3 c3 31 c0 <8a> 14 07 3a 14 06 74 06 19 c0 83 c8 01 c3 48 ff c0 84 d2 75 eb 31 Mar 25 10:00:46 Tower kernel: RSP: 0018:ffffc900017f7d78 EFLAGS: 00010246 Mar 25 10:00:46 Tower kernel: RAX: 0000000000000000 RBX: ffff8881559c5800 RCX: 0000000000000000 Mar 25 10:00:46 Tower kernel: RDX: 0000000000000001 RSI: ffffffff81d9d9b5 RDI: 0000000000000000 Mar 25 10:00:46 Tower kernel: RBP: fffffffffffffffe R08: 0000000000000001 R09: 0000000000004000 Mar 25 10:00:46 Tower kernel: R10: ffffc900017f7f08 R11: 0000000000000000 R12: 0000000000000006 Mar 25 10:00:46 Tower kernel: R13: ffff88816a984000 R14: 0000000000000000 R15: 00000000000037b4 Mar 25 10:00:46 Tower kernel: FS: 00001498a6a99d40(0000) GS:ffff88903fa00000(0000) knlGS:0000000000000000 Mar 25 10:00:46 Tower kernel: CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033 Mar 25 10:00:46 Tower kernel: CR2: 0000000000000000 CR3: 0000000163544001 CR4: 00000000001706f0 Mar 25 10:00:48 Tower emhttpd: shcmd (2307): mkdir -p /mnt/scratch tower-diagnostics-20210325-1500.zip

  3. [DEPRECATED] dyonr - qbittorrentvpn

    johner replied to Dyon's topic in Docker Containers
    what did you change the webUI port to (from the 8080)? The firewall rules are still only forwarding 8080 and 51820 (VPN port you've set?) DNS value wouldn't affect the webui access but would affect tracker lookups, i assume you have something preventing you ISP snooping your DNS look ups on your router if you have changed it in the docker? although I still see 1.1.1.1 as the primary, so unlikely an issue, i'd still ditch the router one.

  4. [DEPRECATED] dyonr - qbittorrentvpn

    johner replied to Dyon's topic in Docker Containers
    Hi, Awesome work! A question on the ports that are mapped and firewall rules in the docker. I noticed it default maps 8999 TCP/UDP from the docker to the unraid host, why is this? I ask as if all traffic is routed via the VPN in the docker, then 8999 (BT) would never leave/come via the docker IP<>host. EDIT: Is it safer to not have it in case the kill switch doesn't work (I haven't looked to see how that is implemented so no idea if it could 'fail'). I noticed the firewall rules don't allow it in or out, so no issues with a leak, therefore the docker port mapping superfluous. Also, is it possible to block all inbound traffic on the VPN tunnel, except the qtorrent BT port (8999 in the default config, but obviously make configurable). I think it's wide open at the moment, i can get to qtorrent UI on the VPN external IP on port 8080 - not ideal. In addition, there are a few that probably aren't need, such as 8080 outbound, only inbound is needed for the UI, and 1195 inbound is not needed, VPN instantiates outbound only. Many thanks!

  5. ***GUIDE*** Passing Through Network Controllers to unRAID 6 Virtual Machines

    johner replied to jonp's topic in VMs
    So after fighting and losing to using two bridges with pfsense (Physical machines could access the Internet but VMs on br0 couldn't - appeared to be an issue with inbound packets to the VMs), I passed through two of my Intel NICs (same vendor IDs). I was fortunate that they were in different IOMMU groups, and all I did was add the hostdev rows to the pfsense VM XML. No syslinux.cfg stubs and no ACS override. Really simple in the end. Unraid no longer sees the cards in the network settings. Did something change in 6.3.2 to make this so easy? Should I expect the world to end as I'm missing something? My Windows VM can now use the Internet, I can RDP to it from the internet (although this did work from the LAN even though internet didn't). I'm curious why twin bridges didn't work, I might search harder for an answer one day out of curiosity. Thanks all, couldn't have done it without this thread. ESXi night night! John

Account

Navigation

Search

Search

Configure browser push notifications
Chrome (Android)
  1. Tap the lock icon next to the address bar.
  2. Tap Permissions → Notifications.
  3. Adjust your preference.
Chrome (Desktop)
  1. Click the padlock icon in the address bar.
  2. Select Site settings.
  3. Find Notifications and adjust your preference.