unRAID Server Release 6.2.0-beta18 Available


Recommended Posts

  • Replies 421
  • Created
  • Last Reply

Top Posters In This Topic

Top Posters In This Topic

Posted Images

I will do a reboot after parity check .....but right now this is in my syslog on so many rows....

Will report after reboot tomorrow.

 


Mar 12 17:44:01 Tower emhttp: shcmd (2589): /etc/rc.d/rc.nfsd start |& logger
Mar 12 17:45:01 Tower emhttp: get_filesystem_status: getxattr: /mnt/user/Movie Operation not supported
Mar 12 17:45:01 Tower emhttp: get_filesystem_status: getxattr: /mnt/user/Music Operation not supported
Mar 12 17:45:01 Tower emhttp: shcmd (2601): /etc/rc.d/rc.nfsd start |& logger
Mar 12 17:46:01 Tower emhttp: get_filesystem_status: getxattr: /mnt/user/Movie Operation not supported
Mar 12 17:46:01 Tower emhttp: get_filesystem_status: getxattr: /mnt/user/Music Operation not supported
Mar 12 17:46:01 Tower emhttp: shcmd (2613): /etc/rc.d/rc.nfsd start |& logger
Mar 12 17:47:01 Tower emhttp: get_filesystem_status: getxattr: /mnt/user/Movie Operation not supported
Mar 12 17:47:01 Tower emhttp: get_filesystem_status: getxattr: /mnt/user/Music Operation not supported
Mar 12 17:47:01 Tower emhttp: shcmd (2625): /etc/rc.d/rc.nfsd start |& logger

 

 

 

 

 

 

15:34:49 Tower kernel: DMAR:[fault reason 06] PTE Read access is not set

Mar 12 15:34:49 Tower kernel: DMAR: DMAR:[DMA Read] Request device [02:00.0] fault addr fc02b7000

Mar 12 15:34:49 Tower kernel: DMAR:[fault reason 06] PTE Read access is not set

Mar 12 15:34:49 Tower kernel: DMAR: DMAR:[DMA Read] Request device [02:00.0] fault addr fc02b9000

Mar 12 15:34:49 Tower kernel: DMAR:[fault reason 06] PTE Read access is not set

Mar 12 15:34:49 Tower kernel: DMAR: DMAR:[DMA Read] Request device [02:00.0] fault addr fc02b9000

Link to comment

Let's try to stay on topic here. We will address the phone home licensing stuff soon but for now, let's not derail this thread with that discussion. We are actively looking into some of the other issues that have been found here.

 

Jonp, with all do respect this IS on-topic. If LT is planning another announcement, then say so and most will hold discussion until that time (and it should be a SHORT amount of time!). But absent a response to the on-topic issue of a new "feature" it will continue to be discussed appropriately.

Link to comment

I will do a reboot after parity check .....but right now this is in my syslog on so many rows....

Will report after reboot tomorrow.

 


Mar 12 17:44:01 Tower emhttp: shcmd (2589): /etc/rc.d/rc.nfsd start |& logger
Mar 12 17:45:01 Tower emhttp: get_filesystem_status: getxattr: /mnt/user/Movie Operation not supported
Mar 12 17:45:01 Tower emhttp: get_filesystem_status: getxattr: /mnt/user/Music Operation not supported
Mar 12 17:45:01 Tower emhttp: shcmd (2601): /etc/rc.d/rc.nfsd start |& logger
Mar 12 17:46:01 Tower emhttp: get_filesystem_status: getxattr: /mnt/user/Movie Operation not supported
Mar 12 17:46:01 Tower emhttp: get_filesystem_status: getxattr: /mnt/user/Music Operation not supported
Mar 12 17:46:01 Tower emhttp: shcmd (2613): /etc/rc.d/rc.nfsd start |& logger
Mar 12 17:47:01 Tower emhttp: get_filesystem_status: getxattr: /mnt/user/Movie Operation not supported
Mar 12 17:47:01 Tower emhttp: get_filesystem_status: getxattr: /mnt/user/Music Operation not supported
Mar 12 17:47:01 Tower emhttp: shcmd (2625): /etc/rc.d/rc.nfsd start |& logger

 

 

Yeah I get:

 

Starting RPC NSM (Network Status Monitor):  /sbin/rpc.statd
Starting NFS server daemons:
  /usr/sbin/exportfs -r
  /usr/sbin/rpc.nfsd 8
  /usr/sbin/rpc.mountd
rpc.mountd: svc_tli_create: could not open connection for udp6
rpc.mountd: svc_tli_create: could not open connection for tcp6
rpc.mountd: svc_tli_create: could not open connection for udp6
rpc.mountd: svc_tli_create: could not open connection for tcp6
rpc.mountd: svc_tli_create: could not open connection for udp6
rpc.mountd: svc_tli_create: could not open connection for tcp6

Link to comment

Let's try to stay on topic here. We will address the phone home licensing stuff soon but for now, let's not derail this thread with that discussion. We are actively looking into some of the other issues that have been found here.

 

This is important - I want to try the beta, and will help report issues/etc found, but I can't install something that's going to hold all my data hostage if I can't connect to the internet.

Link to comment

Can i download the libvirt.img somewhere?

 

It will be created for you.

 

Not in my case..  :'( changed it to: /mnt/user/VMS/Libvirt/

 

Log:

Mar 12 19:46:35 serverramon emhttp: shcmd (316): /etc/rc.d/rc.libvirt start |& logger

Mar 12 19:46:35 serverramon root: no image mounted at /etc/libvirt

 

Link to comment

Quick question about the update to docker; does this mean that docker can now have their own IP address? If so, I assume it will require support built by each keeper of dockers for some custom config to each docker, correct?

 

This would be fantastic since it would allow to direct a specific dockers's traffic over a VPN tunnel on my pfsense router.

 

+1 !

Link to comment

Let's try to stay on topic here. We will address the phone home licensing stuff soon but for now, let's not derail this thread with that discussion. We are actively looking into some of the other issues that have been found here.

 

This is important - I want to try the beta, and will help report issues/etc found, but I can't install something that's going to hold all my data hostage if I can't connect to the internet.

 

Lets wait for LT to explain this feature... I never read anywhere that is something that happens al the time, maybe only on first boot or something...  A bit more info would be appreciated, based on that outcome a discussion might be needed.

Link to comment

Let's try to stay on topic here. We will address the phone home licensing stuff soon but for now, let's not derail this thread with that discussion. We are actively looking into some of the other issues that have been found here.

 

Jonp, with all do respect this IS on-topic. If LT is planning another announcement, then say so and most will hold discussion until that time (and it should be a SHORT amount of time!). But absent a response to the on-topic issue of a new "feature" it will continue to be discussed appropriately.

All I meant by my post is that I didn't want pages of phone-home discussion to bury feedback relating to bugs and other issues.  We will address the concerns about phone home licensing soon, but for now, we are trying to stay focused on bugs we need to solve.

 

I thoroughly hear the concerns you guys are bringing up. We will address this.

Link to comment

Let's try to stay on topic here. We will address the phone home licensing stuff soon but for now, let's not derail this thread with that discussion. We are actively looking into some of the other issues that have been found here.

 

Jonp, with all do respect this IS on-topic. If LT is planning another announcement, then say so and most will hold discussion until that time (and it should be a SHORT amount of time!). But absent a response to the on-topic issue of a new "feature" it will continue to be discussed appropriately.

All I meant by my post is that I didn't want pages of phone-home discussion to bury feedback relating to bugs and other issues.  We will address the concerns about phone home licensing soon, but for now, we are trying to stay focused on bugs we need to solve.

 

I thoroughly hear the concerns you guys are bringing up. We will address this.

 

And that is fair ... and now you've said it :) We eagerly await.

Link to comment

Let's try to stay on topic here. We will address the phone home licensing stuff soon but for now, let's not derail this thread with that discussion. We are actively looking into some of the other issues that have been found here.

 

Sorry, but this is not at all off topic. This is a potential huge flaw. Sure there are more important bugs, but this is not off topic.

 

edit: read the rest of the replies... I will wait, as long as I know my voice (and others) have been heard.

Link to comment

Important: Your server will require internet access upon boot in order to validate with the LimeTech key server.

 

Is this a one-time validation OR is this new version crippled unless it phones home at EVERY reboot???????

HOPEFULLY this only will apply to the beta and evaluation versions. If I can't start my server because my internet happens to be down... >:( >:(

 

Has there been any word on this? I prevent outside network access on my unRAID box at the firewall (and won't be changing it). I thought our keys were tied to the USB, what's to authenticate?

 

For -beta and -rc releases, of all key types, the server must validate at boot time.  The reason is that this lets us "invalidate" a beta release.  That is, if a beta gets out there with a major snafu we can prevent it being run by new users who stumble upon the release zip file.  For example, if there is a bug in P+Q handling.  Remember the reiserfs snafu last year?  We want to minimize that.

 

For stable releases, Basic/Plus/Pro keys do not validate at boot time, that is, works the same as it always has.

 

Starting with 6.2, Trials will require validation with key server.  This is in preparation for making the Trial experience easier.

Link to comment

Important: Your server will require internet access upon boot in order to validate with the LimeTech key server.

 

Is this a one-time validation OR is this new version crippled unless it phones home at EVERY reboot???????

HOPEFULLY this only will apply to the beta and evaluation versions. If I can't start my server because my internet happens to be down... >:( >:(

 

Has there been any word on this? I prevent outside network access on my unRAID box at the firewall (and won't be changing it). I thought our keys were tied to the USB, what's to authenticate?

 

For -beta and -rc releases, of all key types, the server must validate at boot time.  The reason is that this lets us "invalidate" a beta release.  That is, if a beta gets out there with a major snafu we can prevent it being run by new users who stumble upon the release zip file.  For example, if there is a bug in P+Q handling.  Remember the reiserfs snafu last year?  We want to minimize that.

 

For stable releases, Basic/Plus/Pro keys do not validate at boot time, that is, works the same as it always has.

 

Starting with 6.2, Trials will require validation with key server.  This is in preparation for making the Trial experience easier.

 

Thanks !

Link to comment

 

Important: Your server will require internet access upon boot in order to validate with the LimeTech key server.

 

Is this a one-time validation OR is this new version crippled unless it phones home at EVERY reboot???????

HOPEFULLY this only will apply to the beta and evaluation versions. If I can't start my server because my internet happens to be down... >:( >:(

 

Has there been any word on this? I prevent outside network access on my unRAID box at the firewall (and won't be changing it). I thought our keys were tied to the USB, what's to authenticate?

 

For -beta and -rc releases, of all key types, the server must validate at boot time.  The reason is that this lets us "invalidate" a beta release.  That is, if a beta gets out there with a major snafu we can prevent it being run by new users who stumble upon the release zip file.  For example, if there is a bug in P+Q handling.  Remember the reiserfs snafu last year?  We want to minimize that.

 

For stable releases, Basic/Plus/Pro keys do not validate at boot time, that is, works the same as it always has.

 

Starting with 6.2, Trials will require validation with key server.  This is in preparation for making the Trial experience easier.

 

Finally some answer to this topic. Great feature btw, to invalidate betas.

Keep up the good work.

 

Link to comment

For -beta and -rc releases, of all key types, the server must validate at boot time.  The reason is that this lets us "invalidate" a beta release.  That is, if a beta gets out there with a major snafu we can prevent it being run by new users who stumble upon the release zip file

...

For stable releases, Basic/Plus/Pro keys do not validate at boot time, that is, works the same as it always has.

 

Fair enough! Thanks for clarification, will give the beta a try today :)

Link to comment

In regards to the dual parity slot, you should be able to disable it if you don't intend to use it. 

 

I started my array with parity 2 set to unassigned and it stays visible with a big red X and an alert notification that parity 2 is in error state.

 

This also an issue with a brand new system, it shows the red X and an alert notification is sent out.

 

Yeah that's a known issue, should have documented that.

Link to comment

I'm just backing up my server ready for an upgrade to this one. Luckily I have enough storage for a full backup.

 

My main use is gaming vms on this server so I'm going to be testing ovmf for sure. Especially as I am having trouble with seabios still

 

Looking forward to the new version updates. This will be my first time going to a beta or doing a major version jump so I will let you know how easy it was for someone with little knowledge

 

Regards

Jamie

Link to comment

Where can we find the documentation on the new xml attributes for docker containers (ie: hidden, required, etc etc.)

 

Or, do we just have to play around with the options in dockerMan and see what user templates it creates with the various options?

 

Ah, that is in the wiki.  gfjardim did this a while back, but we just never linked it from a main page because the changes weren't live yet.  I think there have been some further adjustments since then, so bare with us as we probably need to bring that up to date.

 

http://lime-technology.com/wiki/index.php/DockerTemplateSchema

Link to comment

changed appdata default to /mnt/cache/appdata from /mnt/user/appdata (/mnt/user/appdata just plain doesn't work for some dockers, including postgres and anything that uses sqlite)

 

mover ran at my set time 8.00 am, and now i have an appdata folder on disk1, which is something new....

 

sparkly, did you happen to catch diagnostics for this event?  I'd like to see logs.

Link to comment

For -beta and -rc releases, of all key types, the server must validate at boot time.  The reason is that this lets us "invalidate" a beta release.  That is, if a beta gets out there with a major snafu we can prevent it being run by new users who stumble upon the release zip file

...

For stable releases, Basic/Plus/Pro keys do not validate at boot time, that is, works the same as it always has.

 

Fair enough! Thanks for clarification, will give the beta a try today :)

 

Right sorry we should have explained this better in the first post.  Nothing nefarious going on here.  There will be some who object but we felt this was the prudent thing to do.

 

This is a fairly complex release because we are introducing some new concepts, for example, "system shares".  The motivation is all about improving the first-time user experience.  If you have seen the early Linus Tech Tips videos on setting up VM's for example, it was far too complex.  We want a new user to boot, click, click, click, and boom! windows pops up on their graphics card.  Well it's still more than 3 clicks but it's far better than it was.

Link to comment

changed appdata default to /mnt/cache/appdata from /mnt/user/appdata (/mnt/user/appdata just plain doesn't work for some dockers, including postgres and anything that uses sqlite)

 

mover ran at my set time 8.00 am, and now i have an appdata folder on disk1, which is something new....

 

sparkly, did you happen to catch diagnostics for this event?  I'd like to see logs.

 

i rebooted several times since, i like to do reboots a few times when i'm on a new version, to make sure things come back up etc..

 

steps though...

 

 

loaded up 6.2

stopped the array to change the options for default appdata from /mnt/user/appdata to /mnt/cache/appdata because of the reasons previously stated.

 

whether or not the appdata folder was made on disk1 at that point or after mover ran, i can't say, but that's when i first noticed it.

 

the shares page, had an unusual usage figure for appdata share, investigated and found that there was an appdata folder on disk1.

 

it was empty, and i deleted it, it hasn't made a reappearance since.

Link to comment

Seems nice!

 

Any update on the Plus license storage device limits on 6.2?

 

There is no change to the number of storage devices you can use with a Plus license in 6.2.

This would mean that the limits are the same for the free and Basic license if free is increased to 6.    This seems to remove much of the incentive to ever move from Free to Basic licenses.  I would have thought you should reduce the limit for Free back to 4 or 5 (I agree 3 was too low) or increase the limits for Basic.  A suggestion might be something like 8 for Basic and 15 for Plus.  This seems more in line with the increase in the Pro limits.

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