September 1, 201510 yr A note was added to the OP pointing to the other announcement thread. Good idea, but it's buried at the very bottom of the fairly long announcement post. Suggest it should be (a) VERY obvious (perhaps larger font); and (b) be at the top of the thread; and © a more aggressive note ==> i.e. instead of "... please see this thread regarding plugin support." something along the lines of "IMPORTANT: Review this thread regarding plugin support in v6.1 BEFORE you upgrade to this version."
September 1, 201510 yr I don't see mention anywhere on a streamlined way of going from 5.06 to 6.1. I know the plugin situation is in disarray right now, and that most/all will not be compatible, but can you still migrate while preserving drive/share info?
September 1, 201510 yr I don't see mention anywhere on a streamlined way of going from 5.06 to 6.1. I know the plugin situation is in disarray right now, and that most/all will not be compatible, but can you still migrate while preserving drive/share info? http://lime-technology.com/wiki/index.php/Upgrading_to_UnRAID_v6
September 1, 201510 yr I don't see mention anywhere on a streamlined way of going from 5.06 to 6.1. The fastest way is using the plugin option in the GUI. That will automatically disable all existing v5 plugins and add-ons but it will bring forward your disk and basic settings. I know the plugin situation is in disarray right now, and that most/all will not be compatible, but can you still migrate while preserving drive/share info? Yes - that is what doing it via the GUI will achieve. There is also the Upgrade to v6 guide that covers all aspects of upgrading and how to do it manually. In particular it discusses the pros and cons of plugins and dockers which is one area where you need to make decisions for v6.
September 1, 201510 yr Squid- thanks for the reference. I'd seen that. I presume it IS valid for 6 AND 6.1...... Itimpi- I don't remember any "plugin option" in the 5.06 GUI, but I'll look when I get home.
September 1, 201510 yr Itimpi- I don't remember any "plugin option" in the 5.06 GUI, but I'll look when I get home. There is the announcement thread covering this method of update. I have never tried it, so I am not sure exactly sure how reliable that method of update is proving to be.
September 1, 201510 yr Just updated and seeing this in my logs once every minute: crond[1988]: exit status 127 from user root /usr/local/emhttp/plugins/dyanmix/scripts/monitor &> /dev/null
September 1, 201510 yr Just updated and seeing this in my logs once every minute: crond[1988]: exit status 127 from user root /usr/local/emhttp/plugins/dyanmix/scripts/monitor &> /dev/null Jim.. are you back on baremetal.. cuz I'm having this as well as a guest on ESXi?
September 1, 201510 yr Just updated and seeing this in my logs once every minute: crond[1988]: exit status 127 from user root /usr/local/emhttp/plugins/dyanmix/scripts/monitor &> /dev/null Jim.. are you back on baremetal.. cuz I'm having this as well as a guest on ESXi? Nope, I'm still on ESXi 5.5 as a guest.
September 1, 201510 yr Author Just updated and seeing this in my logs once every minute: crond[1988]: exit status 127 from user root /usr/local/emhttp/plugins/dyanmix/scripts/monitor &> /dev/null Jim.. are you back on baremetal.. cuz I'm having this as well as a guest on ESXi? Nope, I'm still on ESXi 5.5 as a guest. You guys maybe try this. Type: /usr/local/emhttp/plugins/dyanmix/scripts/monitor at the console and let's see what it outputs.
September 1, 201510 yr Just updated and seeing this in my logs once every minute: crond[1988]: exit status 127 from user root /usr/local/emhttp/plugins/dyanmix/scripts/monitor &> /dev/null Been lots of reports of this. Normally resolved by Disabling/Enabling notifications via Settings.
September 1, 201510 yr Author Just updated and seeing this in my logs once every minute: crond[1988]: exit status 127 from user root /usr/local/emhttp/plugins/dyanmix/scripts/monitor &> /dev/null Been lots of reports of this. Normally resolved by Disabling/Enabling notifications via Settings. Would be nice to know why this happens in a VM.
September 1, 201510 yr You guys maybe try this. Type: /usr/local/emhttp/plugins/dyanmix/scripts/monitor at the console and let's see what it outputs. I just get the following output: root@SPE-UNRAID:~# /usr/local/emhttp/plugins/dyanmix/scripts/monitor -bash: /usr/local/emhttp/plugins/dyanmix/scripts/monitor: No such file or directory Just updated and seeing this in my logs once every minute: crond[1988]: exit status 127 from user root /usr/local/emhttp/plugins/dyanmix/scripts/monitor &> /dev/null Been lots of reports of this. Normally resolved by Disabling/Enabling notifications via Settings. Yes that fixes it.
September 1, 201510 yr Would the .../dyanmix/... be the problem? (Dyan Cannon nice, Dyan Mix not so...)
September 1, 201510 yr Would the .../dyanmix/... be the problem? (Dyan Cannon nice, Dyan Mix not so...) Well... aren't you a keen eye. Nice spot!
September 1, 201510 yr Just updated and seeing this in my logs once every minute: crond[1988]: exit status 127 from user root /usr/local/emhttp/plugins/dyanmix/scripts/monitor &> /dev/null Been lots of reports of this. Normally resolved by Disabling/Enabling notifications via Settings. Would be nice to know why this happens in a VM. Same error on bare metal here. Don't think it's vm esxi related. Upgraded from 6.0 final.
September 1, 201510 yr Would the .../dyanmix/... be the problem? (Dyan Cannon nice, Dyan Mix not so...) You hit the nail on the head ... The installation script has a typo (really all of us overlooked this), but RobJ has a keen eye sed -i 's|sbin/monitor|emhttp/plugins/[color=red]dyanmix[/color]/scripts/monitor|g'
September 1, 201510 yr Author Would the .../dyanmix/... be the problem? (Dyan Cannon nice, Dyan Mix not so...) You hit the nail on the head ... The installation script has a typo (really all of us overlooked this), but RobJ has a keen eye sed -i 's|sbin/monitor|emhttp/plugins/[color=red]dyanmix[/color]/scripts/monitor|g' Holy Typo Batman! Problem fixed (updated plugin files on github).
September 1, 201510 yr Seeing the following messages in my console. Not showing up in my log accessed through the webGUI.
September 2, 201510 yr I just upgraded to 6.1 from 6.0.1 and it all seemed to go just fine. I just have one strange problem with some of my dockers. The version column is shown as "Not Available", but they all seems to be working just fine. Any idea what this could be?
September 2, 201510 yr I just upgraded to v6.1 and it all seemed to work fine but now i can't seem to see my disks browsing from the network any longer. i used to be able to see the disks as shares and i could work with the actual files on those disks but now they are not visible. Is there a setting that i need to turn on to see them again? Thanks James
September 2, 201510 yr I just upgraded to v6.1 and it all seemed to work fine but now i can't seem to see my disks browsing from the network any longer. i used to be able to see the disks as shares and i could work with the actual files on those disks but now they are not visible. Is there a setting that i need to turn on to see them again? Thanks James See the release notes in the first post of this thread about Enable Disk Shares.
September 2, 201510 yr Hi, I'm running 5.0.5 x86; is it possible to upgrade directly to v6.1 x64? (CPU is 64-bit) Thanks
September 2, 201510 yr Hi, I'm running 5.0.5 x86; is it possible to upgrade directly to v6.1 x64? (CPU is 64-bit) Thanks Yes, but only after you remove any and all plugins from v5.
Archived
This topic is now archived and is closed to further replies.