Unraid OS Version 7.0.0-beta.2 available

21 hours ago, asychev said:

beta2 is not available in USB creator

 

Hmm, I see it. I am using the new USB Creator available here:

  https://unraid.net/getting-started

 

First press "Choose OS":

 

 then choose the last option in the list:

 

then you should be able to choose either 7.0.0-beta.1 or 7.0.0-beta.2:

 

If you aren't seeing those options then it sounds like your USB Creator is using an old cached list of options.

 

You can try restarting the USB Creator, if that doesn't help then try uninstalling/reinstalling the USB Creator, if that doesn't help try restarting your computer or running it on a different computer, if that doesn't help maybe something on your network is caching or blocking the download and it may help to try from a different network? If any of those helps please let me know which as it may give us ideas on how to improve this for other people.

 

Failing all of that, you can install the latest stable to the flash drive and then upgrade.

Okay, reinstall works. I can see beta versions, but only just once after full reinstall, so there should be a bug anyway.

On 7/31/2024 at 9:00 PM, asychev said:

beta2 is not available in USB creator, opened a bug https://github.com/unraid/usb-creator-next/issues/49

Just try again? Sometimes doesn't show up on first try for me but closing and reopening it will.

 

15 hours ago, asychev said:

@ljm42 are there any solutions?

If beta 1 is available you could try starting with that and then upgrading to beta 2 from there.

New system with two nvmes that I want to run as a zfs mirror.  Purchased new usb stick, downloaded 6.? to it, did an upgrade to 7.0.0b2.  Created a cache pool with the two drives as zfs mirror.  No other pools created.  Created a SMB share called "Public".  Went to try docker and VM and the "Docker" and "VMs" menu shows the services aren't started.  I checked the settings and their are caution signs on the paths.  I checked "Shares" and don't see shares for isos, appdata or system.  Manually create these shares, reboot and now docker and vms are working. 

 

These default shares should be automatically created in this situation which many people will want to run.

4 hours ago, Chris Hafey said:

These default shares should be automatically created in this situation which many people will want to run.

They should, issue was likely upgrading from 6, since how those shares are created changed for 7

Is there a way to do a clean install of 7 (not an upgrade from 6?)

Yes the new creator offers beta2 installation.

7 minutes ago, Chris Hafey said:

Is there a way to do a clean install of 7 (not an upgrade from 6?)

Yep, you can use the USB tool

I'm on 7B2, I seem to be having permission issues. I tried running the new permission tool, and re-editing the permissions for each user(made things a little better as I could now I had rights to view into folders), yet I get errors when trying to write to the shares that I have read/write permissions. One of the changes I made worth mentioning was that I changed my cache drives to ZFS, and that cache drive then writes to the unraid pool.

I want to do a clean install of 7.0.0-beta.2. I'm using Ubuntu on my primary machine. Where can I download the Unraid 7 image?

27 minutes ago, jpmeijers said:

Where can I download the Unraid 7 image?

Using the USB tool.

Just upgraded to this beta on my i5 7500 setup with 5x 16TB Iron Wolf Pro drives in a ZFS pool with compression enabled. Just added the L2ARC 480GB Sata SSD and am glad to finally be able to use the 1TB WD SN850X as a standard Cache pool for the ZFS pool! No issues that I can see so far; I use Syncthing to keep this server replicating my main server. Syncthing is still scanning files, I'll report back if there are any issues! I like the UI changes on the dashboard!

Am i the only one, who has problems, with the dashboard not saving the layout? I unlock it, rearrange, lock it again, but after unraid shutdown, the layout is reset to default

In Zpool settings it says:

status: Some supported and requested features are not enabled on the pool. The pool can still be used, but some features are unavailable. action: Enable all features using 'zpool upgrade'. Once this is done, the pool may no longer be accessible by software that does not support the features. See zpool-features(7) for details.

 

Does 'zpool upgrade’ mean thru terminal?

ignore it for now. It was mentioned in the release notes, that you most likely ticked off as being read 😁

i see this the first time after update to beta 2, but i'm not sure.

 

Aug  8 10:28:16 SilverNAS kernel: WARNING: CPU: 1 PID: 158096 at fs/notify/fdinfo.c:55 show_mark_fhandle+0x79/0xe8
Aug  8 10:28:16 SilverNAS kernel: Modules linked in: af_packet xt_CHECKSUM ipt_REJECT nf_reject_ipv4 ip6table_mangle iptable_mangle vhost_net tun vhost vhost_iotlb tap xt_nat xt_tcpudp veth xt_conntrack xt_MASQUERADE nf_conntrack_netlink nfnetlink xfrm_user xfrm_algo ip6table_nat iptable_nat nf_nat nf_conntrack nf_defrag_ipv6 nf_defrag_ipv4 xt_addrtype br_netfilter md_mod zfs(PO) bluetooth ecdh_generic ecc spl(O) it87(O) hwmon_vid ip6table_filter ip6_tables iptable_filter ip_tables x_tables bridge stp llc bonding tls r8152(O) r8169 realtek led_class i915 intel_rapl_common x86_pkg_temp_thermal intel_powerclamp coretemp kvm_intel kvm iosf_mbi drm_buddy ttm i2c_algo_bit crct10dif_pclmul crc32_pclmul crc32c_intel ghash_clmulni_intel drm_display_helper sha512_ssse3 sha256_ssse3 sha1_ssse3 aesni_intel drm_kms_helper crypto_simd cryptd mei_pxp mei_hdcp rapl intel_cstate drm mei_me intel_gtt i2c_i801 mei agpgart i2c_smbus ahci libahci i2c_core thermal fan button video wmi backlight [last unloaded: r8152(O)]
Aug  8 10:28:16 SilverNAS kernel: CPU: 1 PID: 158096 Comm: lsof Tainted: P           O       6.8.12-Unraid #3
Aug  8 10:28:16 SilverNAS kernel: Hardware name: retsamarret 000-F5221-FBA002-2000/TM-J3355-2G2L, BIOS MAPL0304V22 03/21/2022
Aug  8 10:28:16 SilverNAS kernel: RIP: 0010:show_mark_fhandle+0x79/0xe8
Aug  8 10:28:16 SilverNAS kernel: Code: ff 00 00 00 89 c1 74 04 85 c0 79 22 80 3d 0a 40 2c 01 00 75 5e 89 ce 48 c7 c7 4b 4a 27 82 c6 05 f8 3f 2c 01 01 e8 23 28 d8 ff <0f> 0b eb 45 89 44 24 0c 8b 44 24 04 48 89 ef 31 db 48 c7 c6 89 4a
Aug  8 10:28:16 SilverNAS kernel: RSP: 0018:ffffc9000afb7c30 EFLAGS: 00010282
Aug  8 10:28:16 SilverNAS kernel: RAX: 0000000000000000 RBX: ffff888104964db8 RCX: 0000000000000027
Aug  8 10:28:16 SilverNAS kernel: RDX: 0000000082440510 RSI: ffffffff82258ed4 RDI: 00000000ffffffff
Aug  8 10:28:16 SilverNAS kernel: RBP: ffff888101246168 R08: 0000000000000000 R09: ffffffff82440510
Aug  8 10:28:16 SilverNAS kernel: R10: 00007fffffffffff R11: 0000000000000000 R12: ffff888101246168
Aug  8 10:28:16 SilverNAS kernel: R13: ffff888101246168 R14: ffffffff812f1e37 R15: ffff88810525ae78
Aug  8 10:28:16 SilverNAS kernel: FS:  000014de1fbdff00(0000) GS:ffff8882f5c80000(0000) knlGS:0000000000000000
Aug  8 10:28:16 SilverNAS kernel: CS:  0010 DS: 0000 ES: 0000 CR0: 0000000080050033
Aug  8 10:28:16 SilverNAS kernel: CR2: 00000000004a5000 CR3: 00000002d704a000 CR4: 00000000003506f0
Aug  8 10:28:16 SilverNAS kernel: Call Trace:
Aug  8 10:28:16 SilverNAS kernel: <TASK>
Aug  8 10:28:16 SilverNAS kernel: ? __warn+0x99/0x11a
Aug  8 10:28:16 SilverNAS kernel: ? report_bug+0xdb/0x155
Aug  8 10:28:16 SilverNAS kernel: ? show_mark_fhandle+0x79/0xe8
Aug  8 10:28:16 SilverNAS kernel: ? handle_bug+0x3c/0x63
Aug  8 10:28:16 SilverNAS kernel: ? exc_invalid_op+0x13/0x60
Aug  8 10:28:16 SilverNAS kernel: ? asm_exc_invalid_op+0x16/0x20
Aug  8 10:28:16 SilverNAS kernel: ? __pfx_inotify_fdinfo+0x10/0x10
Aug  8 10:28:16 SilverNAS kernel: ? show_mark_fhandle+0x79/0xe8
Aug  8 10:28:16 SilverNAS kernel: ? __pfx_inotify_fdinfo+0x10/0x10
Aug  8 10:28:16 SilverNAS kernel: ? seq_vprintf+0x33/0x49
Aug  8 10:28:16 SilverNAS kernel: ? seq_printf+0x53/0x6e
Aug  8 10:28:16 SilverNAS kernel: ? preempt_latency_start+0x2b/0x46
Aug  8 10:28:16 SilverNAS kernel: inotify_fdinfo+0x83/0xaa
Aug  8 10:28:16 SilverNAS kernel: show_fdinfo.isra.0+0x66/0xab
Aug  8 10:28:16 SilverNAS kernel: seq_show+0x154/0x172
Aug  8 10:28:16 SilverNAS kernel: seq_read_iter+0x171/0x353
Aug  8 10:28:16 SilverNAS kernel: ? do_filp_open+0x8e/0xb8
Aug  8 10:28:16 SilverNAS kernel: seq_read+0xe2/0x109
Aug  8 10:28:16 SilverNAS kernel: vfs_read+0xa6/0x197
Aug  8 10:28:16 SilverNAS kernel: ? __do_sys_newfstat+0x35/0x5c
Aug  8 10:28:16 SilverNAS kernel: ksys_read+0x76/0xc2
Aug  8 10:28:16 SilverNAS kernel: do_syscall_64+0x6c/0xdc
Aug  8 10:28:16 SilverNAS kernel: entry_SYSCALL_64_after_hwframe+0x78/0x80
Aug  8 10:28:16 SilverNAS kernel: RIP: 0033:0x14de1fe6e5cd
Aug  8 10:28:16 SilverNAS kernel: Code: 41 48 0e 00 f7 d8 64 89 02 b8 ff ff ff ff eb bb 66 2e 0f 1f 84 00 00 00 00 00 0f 1f 00 80 3d 59 cc 0e 00 00 74 17 31 c0 0f 05 <48> 3d 00 f0 ff ff 77 5b c3 66 2e 0f 1f 84 00 00 00 00 00 48 83 ec
Aug  8 10:28:16 SilverNAS kernel: RSP: 002b:00007ffd9cbb3688 EFLAGS: 00000246 ORIG_RAX: 0000000000000000
Aug  8 10:28:16 SilverNAS kernel: RAX: ffffffffffffffda RBX: 000000000043f600 RCX: 000014de1fe6e5cd
Aug  8 10:28:16 SilverNAS kernel: RDX: 0000000000000400 RSI: 0000000000446e00 RDI: 0000000000000007
Aug  8 10:28:16 SilverNAS kernel: RBP: 000014de1ff52230 R08: 0000000000000001 R09: 0000000000000000
Aug  8 10:28:16 SilverNAS kernel: R10: 0000000000000000 R11: 0000000000000246 R12: 000014de1ff520e0
Aug  8 10:28:16 SilverNAS kernel: R13: 0000000000001000 R14: 0000000000000000 R15: 000000000043f600
Aug  8 10:28:16 SilverNAS kernel: </TASK>
Aug  8 10:28:16 SilverNAS kernel: ---[ end trace 0000000000000000 ]---

Edited August 8 by dibux

2 hours ago, dibux said:

i see this the first time after update to beta 2, but i'm not sure

This call trace has been happening to almost everyone running 7.0.0-beta, it happens just once after every boot and it appears to be harmless:

 

 

On 8/5/2024 at 10:11 AM, JorgeB said:

Using the USB tool.

The USB Creator was only available to download for Windows and MAC when I checked before. Today there is a DEB for Linux. Downloaded, Installed, selected "Unraid OS Releases (next branch)" and selected USB drive. "Next" remains greyed out. Selected another version, "Next" appears. Selecting "next branch" again makes next button not work. So no, using the USB tool does not give me Unraid 7.

13 minutes ago, jpmeijers said:

So no, using the USB tool does not give me Unraid 7.

It should, try again:

https://forums.unraid.net/bug-reports/prereleases/unraid-os-version-700-beta2-available-r3096/?do=findComment&comment=29419

 

Is there a thread for the linux deb usb creator? I don't remember seeing one, and it's not installing on mint 21.3, says dependency is not satisfiable: libarchive13t64

Wonder if anyone can help

 

I have a nvidia p2000 amd recently added an arc a380.my server boots fine with this config.

If i remove the p2000 the server will no longer boot in normal or safe mode

It either hangs at "waiting 30 seconds for unraid to be found" or something like that.

I have removed all nvidia drivers but the issue continues.

 

The motherboard is a supermicro and does have onboard graphics also. I also sometimes get usb errors referring to my tripplite ups instead of the waiting 30 seconds for unraid

 

As soon as i put the p2000 back in it boots up with no issue

It seems that OpenZFS now supports linux kernel upto 6.9. Can we expect new beta/rc?

On 7/13/2024 at 5:12 PM, txwireless said:

Beta 1 seemed to go smoothly yesterday when I installed.  Today upgraded to beta 2 and my logs are being filled with line after line of errors with the following (with unique time stamps and share names):

emhttpd: error: get_fs_sizes, 7823: No such file or directory (2): statfs: /mnt/user/

 

Same thing happens once I start the array in safe mode and goes away when I stop it. If it is a recurring issue and I'm too stupid with search to find it then I apologize and a link to it would be much appreciated.

I'm having the same issue after upgrading:

It's basically all the shares on the system.

22 minutes ago, JayDV8 said:

I'm having the same issue after upgrading

The user you quoted determined it was a disk needing filesystems repair.