Unraid OS version 6.9 beta1 available


72 posts in this topic Last Reply

Recommended Posts

  • Replies 71
  • Created
  • Last Reply

Top Posters In This Topic

Top Posters In This Topic

Popular Posts

I agree that it's not okay to complain about not hearing anything since B1.  If for no other reason than this is a crazy time (I've thought a few times "man, I hope those guys aren't sick").  But I wo

Multiple cache pools being internally tested now.  Multi array pools not in the cards for this release.

When is the next new unraid version available?

9 hours ago, Dazog said:

Help them translate Unraid!

A number of languages are done, but Limetech is going to rely on the community to get other languages included.

See the Multi-language section for more details.

 

Link to post
On 6/8/2020 at 6:52 AM, bonienl said:

Update: there is a lot going one

I agree that it's not okay to complain about not hearing anything since B1.  If for no other reason than this is a crazy time (I've thought a few times "man, I hope those guys aren't sick").  But I would say that it's a missed opportunity to not share at least something of what's happening behind the scenes.  This is a pretty committed and passionate user-base, and some level of sharing would only strengthen it.  I work in big-tech myself, so I get the struggle of figuring out how much to share with your customers.  A monthly blog with some latest development details, near-term roadmap info, things to look forward to with unraid, etc, would go a long way IMHO. 

  • Like 10
Link to post
On 6/8/2020 at 8:45 AM, cobhc said:

That's an unbelievably selfish view to have on this. We would all like a new release with new features, bugs fixed, etc. but it's not as simple as just flicking a switch and with the current world pandemic things are likely to take even longer. The fact that your only post on here is to bitch that it's been 3 months since a release speaks volumes about how little you know about development and thus aren't in the position to be able to judge.

Exactly. Just stay on stable and wait for official releases then.

Link to post

I'm on beta1. Installed beta22, here's what broke:

 

Samba fell off domain

VMs all disappeared (I have custom settings for VM storage and libvirt location)

Cache drives no longer assigned to cache

System hung and needed a forced reset

 

I rolled back and then had to fix VM locations etc.

Link to post

I'm running the beta too, primarily because for some reason the stable version would not work with my mainboard's Ethernet whereas the beta works flawlessly. I updated to beta 2 and so far nothing seems to cause troubles. I don't use VMs though. Array, cache pool, shares and docker containers (Nextcloud, Letsencrypt...) have all survived the upgrade.

Link to post
14 hours ago, XiuzSu said:

Has the list of upcoming features and update notes for 6.9 been released? I haven't seen them anywhere.

Yes.

Release notes are included at the start of the thread here that announced the availability of the  6..9.0 beta 22 release.

 

  • Thanks 1
Link to post
  • 2 weeks later...

If you go to the beta can you go back to stable simply? I'm getting some crazy errors when trying to go back to stable. And my Cachē drive unmounted/unassigned itself

```Linux 5.7.2-Unraid.

root@Tower:~# tail -f /var/log/syslog
Jun 27 15:15:19 Tower kernel: SQUASHFS error: Unable to read fragment cache entry [1602b7c]
Jun 27 15:15:19 Tower kernel: SQUASHFS error: Unable to read page, block 1602b7c, size 3a4c
Jun 27 15:15:19 Tower kernel: veth3f1bd44: renamed from eth0
Jun 27 15:15:19 Tower kernel: br-341c40ac3595: port 1(vethde87652) entered disabled state
: SQUASHFS error: Unable to read fragment cache entry [1602b7c]
Jun 27 15:15:23 Tower kernel: SQUASHFS error: Unable to read page, block 1602b7c, size 3a4c
Jun 27 15:15:23 Tower kernel: SQUASHFS error: Unable to read fragment cache entry [1602b7c]
Jun 27 15:15:23 Tower kernel: SQUASHFS error: Unable to read page, block 1602b7c, size 3a4c
Jun 27 15:15:23 Tower kernel: SQUASHFS error: Unable to read fragment cache entry [1602b7c]
Jun 27 15:15:23 Tower kernel: SQUASHFS error: Unable to read page, block 1602b7c, size 3a4c
Jun 27 15:15:23 Tower kernel: SQUASHFS error: Unable to read fragment cache entry [1602b7c]
Jun 27 15:15:23 Tower kernel: SQUASHFS error: Unable to read page, block 1602b7c, size 3a4c
Jun 27 15:15:23 Tower kernel: docker0: port 1(veth48c12f9) entered disabled state
Jun 27 15:15:23 Tower kernel: device veth48c12f9 left promiscuous mode
Jun 27 15:15:23 Tower kernel: docker0: port 1(veth48c12f9) entered disabled state
Jun 27 15:15:24 Tower kernel: br-341c40ac3595: port 1(vethde87652) entered disabled state
Jun 27 15:15:24 Tower kernel: device vethde87652 left promiscuous mode
Jun 27 15:15:24 Tower kernel: br-341c40ac3595: port 1(vethde87652) entered disabled state
Jun 27 15:15:24 Tower kernel: docker0: port 2(vethd184548) entered disabled state
Jun 27 15:15:24 Tower kernel: device vethd184548 left promiscuous mode
Jun 27 15:15:24 Tower kernel: docker0: port 2(vethd184548) entered disabled state
Jun 27 15:15:24 Tower kernel: SQUASHFS error: Unable to read fragment cache entry [1602b7c]
Jun 27 15:15:24 Tower kernel: SQUASHFS error: Unable to read page, block 1602b7c, size 3a4c
Jun 27 15:15:24 Tower kernel: SQUASHFS error: Unable to read fragment cache entry [1602b7c]
Jun 27 15:15:24 Tower kernel: SQUASHFS error: Unable to read page, block 1602b7c, size 3a4c
Jun 27 15:15:24 Tower kernel: SQUASHFS error: Unable to read fragment cache entry [1602b7c]
Jun 27 15:15:24 Tower kernel: SQUASHFS error: Unable to read page, block 1602b7c, size 3a4c
Jun 27 15:15:24 Tower kernel: vethd492f19: renamed from eth0
Jun 27 15:15:24 Tower kernel: device br0 left promiscuous mode
Jun 27 15:15:24 Tower kernel: veth94e50e2: renamed from eth0
Jun 27 15:15:24 Tower kernel: SQUASHFS error: Unable to read fragment cache entry [1602b7c]
Jun 27 15:15:24 Tower kernel: SQUASHFS error: Unable to read page, block 1602b7c, size 3a4c
Jun 27 15:15:24 Tower kernel: SQUASHFS error: Unable to read fragment cache entry [1602b7c]
Jun 27 15:15:24 Tower kernel: SQUASHFS error: Unable to read page, block 1602b7c, size 3a4c
Jun 27 15:15:24 Tower kernel: SQUASHFS error: Unable to read fragment cache entry [1602b7c]
Jun 27 15:15:24 Tower kernel: SQUASHFS error: Unable to read page, block 1602b7c, size 3a4c
Jun 27 15:15:24 Tower kernel: SQUASHFS error: Unable to read fragment cache entry [1602b7c]
Jun 27 15:15:24 Tower kernel: SQUASHFS error: Unable to read page, block 1602b7c, size 3a4c
Jun 27 15:15:24 Tower kernel: SQUASHFS error: Unable to read fragment cache entry [1602b7c]
Jun 27 15:15:24 Tower kernel: SQUASHFS error: Unable to read page, block 1602b7c, size 3a4c
Jun 27 15:15:24 Tower kernel: SQUASHFS error: Unable to read fragment cache entry [1602b7c]
Jun 27 15:15:24 Tower kernel: SQUASHFS error: Unable to read page, block 1602b7c, size 3a4c
Jun 27 15:15:27 Tower kernel: vethb5852b4: renamed from eth0
Jun 27 15:15:27 Tower kernel: docker0: port 6(vethcbd2e42) entered disabled state
Jun 27 15:15:27 Tower kernel: SQUASHFS error: Unable to read fragment cache entry [1602b7c]
Jun 27 15:15:27 Tower kernel: SQUASHFS error: Unable to read page, block 1602b7c, size 3a4c
Jun 27 15:15:27 Tower kernel: SQUASHFS error: Unable to read fragment cache entry [1602b7c]
Jun 27 15:15:27 Tower kernel: SQUASHFS error: Unable to read page, block 1602b7c, size 3a4c
Jun 27 15:15:27 Tower kernel: SQUASHFS error: Unable to read fragment cache entry [1602b7c]
Jun 27 15:15:27 Tower kernel: SQUASHFS error: Unable to read page, block 1602b7c, size 3a4c
Jun 27 15:15:27 Tower kernel: veth2262833: renamed from eth0
Jun 27 15:15:27 Tower kernel: docker0: port 3(vethb2d76f2) entered disabled state
Jun 27 15:15:27 Tower kernel: SQUASHFS error: Unable to read fragment cache entry [1602b7c]
Jun 27 15:15:27 Tower kernel: SQUASHFS error: Unable to read page, block 1602b7c, size 3a4c
Jun 27 15:15:27 Tower kernel: SQUASHFS error: Unable to read fragment cache entry [1602b7c]
Jun 27 15:15:27 Tower kernel: SQUASHFS error: Unable to read page, block 1602b7c, size 3a4c
Jun 27 15:15:27 Tower kernel: SQUASHFS error: Unable to read fragment cache entry [1602b7c]
Jun 27 15:15:27 Tower kernel: SQUASHFS error: Unable to read page, block 1602b7c, size 3a4c
Jun 27 15:15:29 Tower kernel: veth20b9485: renamed from eth0
Jun 27 15:15:29 Tower kernel: docker0: port 5(vethaabdc05) entered disabled state
Jun 27 15:15:29 Tower kernel: SQUASHFS error: Unable to read fragment cache entry [1602b7c]
Jun 27 15:15:29 Tower kernel: SQUASHFS error: Unable to read page, block 1602b7c, size 3a4c
Jun 27 15:15:29 Tower kernel: SQUASHFS error: Unable to read fragment cache entry [1602b7c]
Jun 27 15:15:29 Tower kernel: SQUASHFS error: Unable to read page, block 1602b7c, size 3a4c
Jun 27 15:15:29 Tower kernel: SQUASHFS error: Unable to read fragment cache entry [1602b7c]
Jun 27 15:15:29 Tower kernel: SQUASHFS error: Unable to read page, block 1602b7c, size 3a4c
Jun 27 15:15:37 Tower kernel: docker0: port 6(vethcbd2e42) entered disabled state
Jun 27 15:15:37 Tower kernel: device vethcbd2e42 left promiscuous mode
Jun 27 15:15:37 Tower kernel: docker0: port 6(vethcbd2e42) entered disabled state
Jun 27 15:15:37 Tower kernel: docker0: port 3(vethb2d76f2) entered disabled state
Jun 27 15:15:37 Tower kernel: device vethb2d76f2 left promiscuous mode
Jun 27 15:15:37 Tower kernel: docker0: port 3(vethb2d76f2) port ........................................................................................................................................................................................................................................................................
:14 Tower root: error: Failed to connect socket to '/var/run/libvirt/libvirt-sock': No such file or directory
Jun 27 15:18:14 Tower root: cat: /var/run/libvirt/libvirtd.pid: No such file or directory
Jun 27 15:18:14 Tower root: kill: usage: kill [-s sigspec | -n signum | -sigspec] pid | jobspec ... or kill -l [sigspec]
Jun 27 15:18:16 Tower kernel: SQUASHFS error: Unable to read fragment cache entry [1602b7c]
Jun 27 15:18:16 Tower kernel: SQUASHFS error: Unable to read page, block 1602b7c, size 3a4c
Jun 27 15:18:16 Tower kernel: SQUASHFS error: Unable to read fragment cache entry [1602b7c]
Jun 27 15:18:16 Tower kernel: SQUASHFS error: Unable to read page, block 1602b7c, size 3a4c
Jun 27 15:18:16 Tower kernel: SQUASHFS error: Unable to read fragment cache entry [1602b7c]
Jun 27 15:18:16 Tower kernel: SQUASHFS error: Unable to read page, block 1602b7c, size 3a4c
Jun 27 15:18:17 Tower root: /etc/rc.d/rc.libvirt: line 151:  7185 Bus error               /sbin/modprobe -ra $MODULE $MODULES 2> /dev/null
Jun 27 15:18:17 Tower root: virtlogd is not running...
 cache entry [1602b7c]
Jun 27 15:18:17 Tow
Jun 27 15:18:18 Tower avahi-dnsconfd[16049]: read(): EOF```

 

 

 

Edited by Fiservedpi
Link to post
11 minutes ago, Fiservedpi said:

And my Cachē drive unmounted/unassigned itself

Yes.  Reverting from beta 22 to beta 1 or 6.8.3 you will have to reassign your cache drive.

 

For the errors, I would start a new thread and include your diagnostics with it.

  • Thanks 1
Link to post
33 minutes ago, Fiservedpi said:

Jun 27 15:15:23 Tower kernel: SQUASHFS error: Unable to read page, block 1602b7c, size 3a4c

Those squashfs errors are originating from trying to read from 'bzmodules' on your usb flash boot device.

  • Thanks 1
Link to post
  • 2 weeks later...
19 minutes ago, CEH1934 said:

Will the coming release mean that multi-disk BTRFS arrays can spread their stripes across the array disks?

No, each array data disk is still an independent filesystem, what you can do with the latest betas is to have multiple btrfs storage pools, each pool is independent and can use one of the available btrfs profiles, they behave like the normal cache pool.

Link to post

after some days of testing i consider moving my UAD nvme drive where my vm's are located to setup as 2nd cache pool for VM usage.

 

my question is out of interest about timeline, i ll backup my VM vdisks to array, as my UAD drive is already xfs formatted, will it be wiped out when i assign it as cache and i have to copy over my vdisks back or will the data keep there and i just rewrite my pathes in the VM xml's ?

 

its just about time effort todo the move, for a note thanks ahead.

 

and the cache will be a single drive "pool", so xfs should be fine when i read correctly.

Link to post
12 hours ago, alturismo said:

will it be wiped out when i assign it as cache and i have to copy over my vdisks back or will the data keep there and i just rewrite my pathes in the VM xml's ?

It won't be wiped as long as it was formatted with a relatively recent UD release, like in the last couple of years or so, and even if an older release was used it won't be, it will just be unmountable due to invalid partition layout.

 

 

Link to post
3 hours ago, johnnie.black said:

It won't be wiped as long as it was formatted with a relatively recent UD release, like in the last couple of years or so, and even if an older release was used it won't be, it will just be unmountable due to invalid partition layout.

 

 

thanks for the info, then a full copy and move is mandatory anyway, just so i plan time.

Link to post

Tested beta 25 on a spare laptop today, very nice, One thing i noticed, i chose encrypted btfrs as file system in disk settings, formatted my disk, but it shows up as xfs anyway? Is this an issue or did i do something wrong? Also I did had to enter a passphrase to start the array, i guess this is related to the encrypted disk? But... if i stop and restart the array, it asks for a passphrase again and i can enter anything i want, i doesn’t have to be the same as i entered before? What’s the use of that?

Link to post
18 minutes ago, jowi said:

Tested beta 25 on a spare laptop today, very nice, One thing i noticed, i chose encrypted btfrs as file system in disk settings, formatted my disk, but it shows up as xfs anyway? Is this an issue or did i do something wrong? Also I did had to enter a passphrase to start the array, i guess this is related to the encrypted disk? But... if i stop and restart the array, it asks for a passphrase again and i can enter anything i want, i doesn’t have to be the same as i entered before? What’s the use of that?

You posted this in the wrong place.

Link to post
Guest
This topic is now closed to further replies.