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

Unraid OS version 6.8.0-rc series has started

limetech
in Announcements

Featured Replies

  • limetech featured and pinned this topic

Oh boy, been looking sooo forward to this, thanks Tom!!!!

Here we go boys!!!

    • Haha 1
    3 minutes ago, drawmonster said:

    Here we go boys!!!

    Let me know how it goes 🙂

    Dippin my toe all the way in on this one..

    Thank you @limetech team for all your hard work!👍👊

    • Thanks 1

    Stopped all of my VMs, and applied the update.   No problems so far.  Dockers and VMS seem to be working for me.

    Thank you @limetech team for the hard work!

     

    Joey

    • Thanks 1

    You guys make an excellent product.  I plan on buying another copy for another server soon.  I think I'll do some testing with the latest.   I've been running unraid on the following hardware and it just kills it.  

    unraid_page.png.71297df8ab4187fc73f1b6495b893678.png

    one thing i notice here, using webterminal

     

    exit

     

    will directly relogin again, so only way is to close the window while session open, by demand ?

    38 minutes ago, alturismo said:

    one thing i notice here, using webterminal

     

    exit

     

    will directly relogin again, so only way is to close the window while session open, by demand ?

    Solved in RC2

    thanks for the info

    2 minutes ago, bonienl said:

    Solved in RC2

     

    sweeet!! html login page!! WireGuard support!!! thank you gent :)

    Heading over to post a bug, release was a no-go for me. So close and looking forward to the new kernel; and hardware support :)

     

    Edit: Not a bug, a feature! Unassigned Drives needs an update to continue to work with encrypted drives is all. A security update has changed the way you decrypt drives outside the array. Worked around it for now with a link file in my Go but it's not a long-term fix.

    Edited by BLKMGK

    Just upgraded to 6.8.0-RC-1.  Syslog is full of the following errors: 

    Oct 14 23:03:24 MediaNAS rsyslogd: omfwd: socket 7: error 101 sending via udp: Network is unreachable [v8.1908.0 try https://www.rsyslog.com/e/2354 ]
Oct 14 23:03:24 MediaNAS rsyslogd: action 'action-2-builtin:omfwd' suspended (module 'builtin:omfwd'), retry 0. There should be messages before this one giving the reason for suspension. [v8.1908.0 try https://www.rsyslog.com/e/2007 ]
Oct 14 23:03:24 MediaNAS rsyslogd: action 'action-2-builtin:omfwd' resumed (module 'builtin:omfwd') [v8.1908.0 try https://www.rsyslog.com/e/2359 ]
Oct 14 23:03:24 MediaNAS rsyslogd: omfwd/udp: socket 2: sendto() error: Network is unreachable [v8.1908.0 try https://www.rsyslog.com/e/2354 ]
Oct 14 23:03:24 MediaNAS rsyslogd: omfwd: socket 2: error 101 sending via udp: Network is unreachable [v8.1908.0 try https://www.rsyslog.com/e/2354 ]
Oct 14 23:03:24 MediaNAS rsyslogd: action 'action-2-builtin:omfwd' suspended (module 'builtin:omfwd'), retry 0. There should be messages before this one giving the reason for suspension. [v8.1908.0 try https://www.rsyslog.com/e/2007 ]
Oct 14 23:03:24 MediaNAS rsyslogd: action 'action-2-builtin:omfwd' resumed (module 'builtin:omfwd') [v8.1908.0 try https://www.rsyslog.com/e/2359 ]
Oct 14 23:03:24 MediaNAS rsyslogd: omfwd/udp: socket 2: sendto() error: Network is unreachable [v8.1908.0 try https://www.rsyslog.com/e/2354 ]
Oct 14 23:03:24 MediaNAS rsyslogd: omfwd: socket 2: error 101 sending via udp: Network is unreachable [v8.1908.0 try https://www.rsyslog.com/e/2354 ]
Oct 14 23:03:24 MediaNAS rsyslogd: action 'action-2-builtin:omfwd' suspended (module 'builtin:omfwd'), retry 0. There should be messages before this one giving the reason for suspension. [v8.1908.0 try https://www.rsyslog.com/e/2007 ]
Oct 14 23:03:24 MediaNAS rsyslogd: action 'action-2-builtin:omfwd' resumed (module 'builtin:omfwd') [v8.1908.0 try https://www.rsyslog.com/e/2359 ]
Oct 14 23:03:24 MediaNAS rsyslogd: omfwd/udp: socket 2: sendto() error: Network is unreachable [v8.1908.0 try https://www.rsyslog.com/e/2354 ]
Oct 14 23:03:24 MediaNAS rsyslogd: omfwd: socket 2: error 101 sending via udp: Network is unreachable [v8.1908.0 try https://www.rsyslog.com/e/2354 ]
Oct 14 23:03:24 MediaNAS rsyslogd: action 'action-2-builtin:omfwd' suspended (module 'builtin:omfwd'), retry 0. There should be messages before this one giving the reason for suspension. [v8.1908.0 try https://www.rsyslog.com/e/2007 ]
Oct 14 23:03:24 MediaNAS rsyslogd: action 'action-2-builtin:omfwd' resumed (module 'builtin:omfwd') [v8.1908.0 try https://www.rsyslog.com/e/2359 ]
Oct 14 23:03:24 MediaNAS rsyslogd: omfwd/udp: socket 2: sendto() error: Network is unreachable [v8.1908.0 try https://www.rsyslog.com/e/2354 ]
Oct 14 23:03:24 MediaNAS rsyslogd: omfwd: socket 2: error 101 sending via udp: Network is unreachable [v8.1908.0 try https://www.rsyslog.com/e/2354 ]
Oct 14 23:03:24 MediaNAS rsyslogd: action 'action-2-builtin:omfwd' suspended (module 'builtin:omfwd'), retry 0. There should be messages before this one giving the reason for suspension. [v8.1908.0 try https://www.rsyslog.com/e/2007 ]
Oct 14 23:03:24 MediaNAS rsyslogd: action 'action-2-builtin:omfwd' resumed (module 'builtin:omfwd') [v8.1908.0 try https://www.rsyslog.com/e/2359 ]
Oct 14 23:03:24 MediaNAS rsyslogd: omfwd/udp: socket 2: sendto() error: Network is unreachable [v8.1908.0 try https://www.rsyslog.com/e/2354 ]
Oct 14 23:03:24 MediaNAS rsyslogd: omfwd: socket 2: error 101 sending via udp: Network is unreachable [v8.1908.0 try https://www.rsyslog.com/e/2354 ]
Oct 14 23:03:24 MediaNAS rsyslogd: action 'action-2-builtin:omfwd' suspended (module 'builtin:omfwd'), retry 0. There should be messages before this one giving the reason for suspension. [v8.1908.0 try https://www.rsyslog.com/e/2007 ]
Oct 14 23:03:24 MediaNAS rsyslogd: action 'action-2-builtin:omfwd' resumed (module 'builtin:omfwd') [v8.1908.0 try https://www.rsyslog.com/e/2359 ]
Oct 14 23:03:24 MediaNAS rsyslogd: omfwd/udp: socket 2: sendto() error: Network is unreachable [v8.1908.0 try https://www.rsyslog.com/e/2354 ]
Oct 14 23:03:24 MediaNAS rsyslogd: omfwd: socket 2: error 101 sending via udp: Network is unreachable [v8.1908.0 try https://www.rsyslog.com/e/2354 ]
Oct 14 23:03:24 MediaNAS rsyslogd: action 'action-2-builtin:omfwd' suspended (module 'builtin:omfwd'), retry 0. There should be messages before this one giving the reason for suspension. [v8.1908.0 try https://www.rsyslog.com/e/2007 ]
Oct 14 23:03:24 MediaNAS rsyslogd: action 'action-2-builtin:omfwd' resumed (module 'builtin:omfwd') [v8.1908.0 try https://www.rsyslog.com/e/2359 ]
Oct 14 23:03:24 MediaNAS rsyslogd: omfwd/udp: socket 2: sendto() error: Network is unreachable [v8.1908.0 try https://www.rsyslog.com/e/2354 ]
Oct 14 23:03:24 MediaNAS rsyslogd: omfwd: socket 2: error 101 sending via udp: Network is unreachable [v8.1908.0 try https://www.rsyslog.com/e/2354 ]
Oct 14 23:03:24 MediaNAS rsyslogd: action 'action-2-builtin:omfwd' suspended (module 'builtin:omfwd'), retry 0. There should be messages before this one giving the reason for suspension. [v8.1908.0 try https://www.rsyslog.com/e/2007 ]
Oct 14 23:03:24 MediaNAS rsyslogd: action 'action-2-builtin:omfwd' resumed (module 'builtin:omfwd') [v8.1908.0 try https://www.rsyslog.com/e/2359 ]
Oct 14 23:03:24 MediaNAS rsyslogd: omfwd/udp: socket 2: sendto() error: Network is unreachable [v8.1908.0 try https://www.rsyslog.com/e/2354 ]
Oct 14 23:03:24 MediaNAS rsyslogd: omfwd: socket 2: error 101 sending via udp: Network is unreachable [v8.1908.0 try https://www.rsyslog.com/e/2354 ]
Oct 14 23:03:24 MediaNAS rsyslogd: action 'action-2-builtin:omfwd' suspended (module 'builtin:omfwd'), retry 0. There should be messages before this one giving the reason for suspension. [v8.1908.0 try https://www.rsyslog.com/e/2007 ]
Oct 14 23:03:24 MediaNAS rsyslogd: action 'action-2-builtin:omfwd' resumed (module 'builtin:omfwd') [v8.1908.0 try https://www.rsyslog.com/e/2359 ]

     

    Also, I get a call trace that seems to be related to the i915 video module;

      

    Oct 14 23:04:52 MediaNAS kernel: Console: switching to colour dummy device 80x25
Oct 14 23:04:52 MediaNAS kernel: [drm] Supports vblank timestamp caching Rev 2 (21.10.2013).
Oct 14 23:04:52 MediaNAS kernel: [drm] Driver supports precise vblank timestamp query.
Oct 14 23:04:52 MediaNAS kernel: i915 0000:00:02.0: vgaarb: changed VGA decodes: olddecodes=io+mem,decodes=io+mem:owns=io+mem
Oct 14 23:04:52 MediaNAS kernel: [drm] Disabling framebuffer compression (FBC) to prevent screen flicker with VT-d enabled
Oct 14 23:04:52 MediaNAS kernel: [drm] Finished loading DMC firmware i915/skl_dmc_ver1_27.bin (v1.27)
Oct 14 23:04:52 MediaNAS kernel: [drm:drm_calc_timestamping_constants [drm]] *ERROR* crtc 48: Can't calculate constants, dotclock = 0!
Oct 14 23:04:52 MediaNAS kernel: WARNING: CPU: 2 PID: 7789 at drivers/gpu/drm/drm_vblank.c:638 drm_calc_vbltimestamp_from_scanoutpos+0x129/0x29c [drm]
Oct 14 23:04:52 MediaNAS kernel: Modules linked in: i915(+) iosf_mbi drm_kms_helper drm intel_gtt agpgart syscopyarea sysfillrect sysimgblt fb_sys_fops nct6775 hwmon_vid e1000e igb i2c_algo_bit sr_mod cdrom x86_pkg_temp_thermal intel_powerclamp coretemp kvm_intel kvm crct10dif_pclmul crc32_pclmul crc32c_intel ghash_clmulni_intel aesni_intel aes_x86_64 crypto_simd cryptd mpt3sas glue_helper raid_class i2c_i801 intel_cstate intel_uncore mxm_wmi i2c_core ahci intel_rapl_perf video wmi scsi_transport_sas backlight libahci acpi_pad button ie31200_edac [last unloaded: e1000e]
Oct 14 23:04:52 MediaNAS kernel: CPU: 2 PID: 7789 Comm: modprobe Not tainted 5.3.6-Unraid #1
Oct 14 23:04:52 MediaNAS kernel: Hardware name: To Be Filled By O.E.M. To Be Filled By O.E.M./C236 WSI, BIOS P2.60 03/06/2018
Oct 14 23:04:52 MediaNAS kernel: RIP: 0010:drm_calc_vbltimestamp_from_scanoutpos+0x129/0x29c [drm]
Oct 14 23:04:52 MediaNAS kernel: Code: 43 20 8b 80 78 01 00 00 23 43 50 a8 10 75 1b 48 8b 83 28 03 00 00 48 85 c0 0f 84 5b ff ff ff 48 83 78 28 00 0f 84 50 ff ff ff <0f> 0b e9 44 01 00 00 48 8b 43 20 48 8d 55 c0 41 57 44 89 f6 52 4c
Oct 14 23:04:52 MediaNAS kernel: RSP: 0018:ffffc90003dff7e8 EFLAGS: 00010002
Oct 14 23:04:52 MediaNAS kernel: RAX: 000000000000003f RBX: ffff888815b00000 RCX: ffffc90003dff888
Oct 14 23:04:52 MediaNAS kernel: RDX: 0000000000000000 RSI: ffffffffa0314379 RDI: 0000000000000001
Oct 14 23:04:52 MediaNAS kernel: RBP: ffffc90003dff850 R08: 0000000000000000 R09: 0000000000000000
Oct 14 23:04:52 MediaNAS kernel: R10: 0000000000000002 R11: ffff88884678e000 R12: 0000000000000000
Oct 14 23:04:52 MediaNAS kernel: R13: 0000000000000000 R14: 0000000000000000 R15: ffff888846789080
Oct 14 23:04:52 MediaNAS kernel: FS:  0000153176da5b80(0000) GS:ffff88884de80000(0000) knlGS:0000000000000000
Oct 14 23:04:52 MediaNAS kernel: CS:  0010 DS: 0000 ES: 0000 CR0: 0000000080050033
Oct 14 23:04:52 MediaNAS kernel: CR2: 000000000052a020 CR3: 0000000848700005 CR4: 00000000003606e0
Oct 14 23:04:52 MediaNAS kernel: DR0: 0000000000000000 DR1: 0000000000000000 DR2: 0000000000000000
Oct 14 23:04:52 MediaNAS kernel: DR3: 0000000000000000 DR6: 00000000fffe0ff0 DR7: 0000000000000400
Oct 14 23:04:52 MediaNAS kernel: Call Trace:
Oct 14 23:04:52 MediaNAS kernel: ? idr_alloc+0x41/0x63
Oct 14 23:04:52 MediaNAS kernel: ? drm_calc_timestamping_constants+0xac/0x12c [drm]
Oct 14 23:04:52 MediaNAS kernel: drm_get_last_vbltimestamp+0x54/0x73 [drm]
Oct 14 23:04:52 MediaNAS kernel: drm_reset_vblank_timestamp+0x58/0xc2 [drm]
Oct 14 23:04:52 MediaNAS kernel: drm_crtc_vblank_on+0x8f/0xcf [drm]
Oct 14 23:04:52 MediaNAS kernel: intel_modeset_setup_hw_state+0x786/0x1059 [i915]
Oct 14 23:04:52 MediaNAS kernel: intel_modeset_init+0x11a9/0x16e8 [i915]
Oct 14 23:04:52 MediaNAS kernel: ? fwtable_write32+0x8f/0x11f [i915]
Oct 14 23:04:52 MediaNAS kernel: ? fwtable_write32+0x8f/0x11f [i915]
Oct 14 23:04:52 MediaNAS kernel: i915_driver_load+0x108b/0x133f [i915]
Oct 14 23:04:52 MediaNAS kernel: ? idr_alloc_cyclic+0x53/0xa7
Oct 14 23:04:52 MediaNAS kernel: ? rpm_resume+0x9b/0x409
Oct 14 23:04:52 MediaNAS kernel: i915_pci_probe+0x108/0x12a [i915]
Oct 14 23:04:52 MediaNAS kernel: local_pci_probe+0x3c/0x7a
Oct 14 23:04:52 MediaNAS kernel: pci_device_probe+0x13c/0x196
Oct 14 23:04:52 MediaNAS kernel: ? sysfs_do_create_link_sd.isra.0+0x80/0xad
Oct 14 23:04:52 MediaNAS kernel: really_probe+0x145/0x283
Oct 14 23:04:52 MediaNAS kernel: driver_probe_device+0x9c/0xd1
Oct 14 23:04:52 MediaNAS kernel: device_driver_attach+0x37/0x50
Oct 14 23:04:52 MediaNAS kernel: __driver_attach+0x95/0x9d
Oct 14 23:04:52 MediaNAS kernel: ? device_driver_attach+0x50/0x50
Oct 14 23:04:52 MediaNAS kernel: bus_for_each_dev+0x70/0xa6
Oct 14 23:04:52 MediaNAS kernel: bus_add_driver+0xfb/0x1a9
Oct 14 23:04:52 MediaNAS kernel: driver_register+0x99/0xcf
Oct 14 23:04:52 MediaNAS kernel: ? 0xffffffffa04c6000
Oct 14 23:04:52 MediaNAS kernel: do_one_initcall+0x71/0x166
Oct 14 23:04:52 MediaNAS kernel: ? __vunmap+0x1c2/0x1e0
Oct 14 23:04:52 MediaNAS kernel: ? _cond_resched+0x1b/0x1e
Oct 14 23:04:52 MediaNAS kernel: ? kmem_cache_alloc+0x30/0x128
Oct 14 23:04:52 MediaNAS kernel: do_init_module+0x51/0x1da
Oct 14 23:04:52 MediaNAS kernel: load_module+0x19a1/0x1f95
Oct 14 23:04:52 MediaNAS kernel: ? __se_sys_init_module+0xd5/0x116
Oct 14 23:04:52 MediaNAS kernel: __se_sys_init_module+0xd5/0x116
Oct 14 23:04:52 MediaNAS kernel: do_syscall_64+0x57/0xfd
Oct 14 23:04:52 MediaNAS kernel: entry_SYSCALL_64_after_hwframe+0x44/0xa9
Oct 14 23:04:52 MediaNAS kernel: RIP: 0033:0x153176ee013a
Oct 14 23:04:52 MediaNAS kernel: Code: 48 8b 0d 59 7d 0c 00 f7 d8 64 89 01 48 83 c8 ff c3 66 2e 0f 1f 84 00 00 00 00 00 0f 1f 44 00 00 49 89 ca b8 af 00 00 00 0f 05 <48> 3d 01 f0 ff ff 73 01 c3 48 8b 0d 26 7d 0c 00 f7 d8 64 89 01 48
Oct 14 23:04:52 MediaNAS kernel: RSP: 002b:00007ffcdf22fde8 EFLAGS: 00000246 ORIG_RAX: 00000000000000af
Oct 14 23:04:52 MediaNAS kernel: RAX: ffffffffffffffda RBX: 0000000000427e30 RCX: 0000153176ee013a
Oct 14 23:04:52 MediaNAS kernel: RDX: 000000000041b400 RSI: 00000000002c38a8 RDI: 0000000000d3f810
Oct 14 23:04:52 MediaNAS kernel: RBP: 000000000041b400 R08: 000000000042501a R09: 0000000000000000
Oct 14 23:04:52 MediaNAS kernel: R10: 0000000000425010 R11: 0000000000000246 R12: 0000000000d3f810
Oct 14 23:04:52 MediaNAS kernel: R13: 0000000000427f40 R14: 0000000000040000 R15: 0000000000427e30
Oct 14 23:04:52 MediaNAS kernel: ---[ end trace c13b68bd66095883 ]---
Oct 14 23:04:52 MediaNAS kernel: [drm] Initialized i915 1.6.0 20190619 for 0000:00:02.0 on minor 0
Oct 14 23:04:52 MediaNAS kernel: ACPI: Video Device [GFX0] (multi-head: yes  rom: no  post: no)
Oct 14 23:04:52 MediaNAS kernel: input: Video Bus as /devices/LNXSYSTM:00/LNXSYBUS:00/PNP0A08:00/LNXVIDEO:00/input/input7
Oct 14 23:04:52 MediaNAS kernel: fbcon: i915drmfb (fb0) is primary device
Oct 14 23:04:52 MediaNAS kernel: Console: switching to colour frame buffer device 128x48
Oct 14 23:04:54 MediaNAS kernel: i915 0000:00:02.0: fb0: i915drmfb frame buffer device
Oct 14 23:04:56 MediaNAS kernel: [drm:intel_dp_get_link_train_fallback_values [i915]] *ERROR* Link Training Unsuccessful
Oct 14 23:04:58 MediaNAS root: Starting emhttpd

    System seems to currently be running OK, but, I have not really tried to do anything other than install the WireGuard plugin (not currently configured or active).

     

    Of course, I don't consider these things to be the result of any "bug" but it there something I can look at to track down the cause of these issues that only began with 6.8.0-RC1

     

    Diagnostics attached.

     

     

    medianas-diagnostics-20191015-0512.zip

    Edited by Hoopster

    Can you make a report under Bug reports, it will make it easier to track.

     

    15 minutes ago, bonienl said:

    Can you make a report under Bug reports, it will make it easier to track.

     

    Sure, I did not think this was a "bug" necessarily so I did not know if it belonged there.  I will make the report in that thread for tracking purposes.

    balls deep

    • Haha 1

    Can someone explain why AFP become deprecated?

    Edited by IGHOR
    AFC->AFP

    Can someone explain why AFC become deprecated?

    I would guess because Apple is also deprecating AFP and recommending users to switch to SMB.

     

     

    2 minutes ago, johnnie.black said:

    I would guess because Apple is also deprecating it and recommending users to switch to SMB.

    I can't find any information about this. And why would Apple reject own protocol in favor of Microsoft's protocol?

    Edited by IGHOR

    10 minutes ago, johnnie.black said:

    https://support.apple.com/en-us/HT207828

    Thanks, but it says AFP won't work on APFS volume that have no relation to unRAID.

    Time Machine remains to work on AFP in Time Capsule, so why to remove it from unRAID?

     

    Here is confirmation that AFP is deprecated https://developer.apple.com/library/archive/documentation/FileManagement/Conceptual/APFS_Guide/FAQ/FAQ.html

    Edited by IGHOR

    4 minutes ago, IGHOR said:

    Thanks, but it says AFP won't work on APFS volume that have no relation to unRAID.

    Time Machine remains to work on AFP in Time Capsule, so why to remove it from unRAID?

    Google   time machine with smb   and do your own research.

    2 minutes ago, Frank1940 said:

    Google   time machine with smb   and do your own research.

    I tried it some time ago, many tries. I got never finished my Time Machine backup over SMB this way.

    Well, will do it in other way.

    Guest
    This topic is now closed to further replies.
    Go to topic listing

    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.