Rick Sanchez Posted October 9, 2015 Share Posted October 9, 2015 (edited) Do you mean these? Edited May 10, 2018 by Rick Sanchez Quote Link to comment
itimpi Posted October 9, 2015 Share Posted October 9, 2015 Do you mean these? I do not think any of those plugins would be compatible with v6.1.3. Maybe your best way forward is to remove all plugins (by setting the config/plugins folder on the USB drive to be the same as the one in the unRAID release ZIP download) and then add any new ones you still want from the list of 6.1 verified ones. Quote Link to comment
Rick Sanchez Posted October 9, 2015 Share Posted October 9, 2015 Maybe your best way forward is to remove all plugins (by setting the config/plugins folder on the USB drive to be the same as the one in the unRAID release ZIP download) and then add any new ones you still want from the list of 6.1 verified ones. I don't follow; I thought v6 had a update button? Do I need to download and transfer/overwrite everything? Quote Link to comment
itimpi Posted October 9, 2015 Share Posted October 9, 2015 Maybe your best way forward is to remove all plugins (by setting the config/plugins folder on the USB drive to be the same as the one in the unRAID release ZIP download) and then add any new ones you still want from the list of 6.1 verified ones. I don't follow; I thought v6 had a update button? Do I need to download and transfer/overwrite everything? Not for beta 6. The GUI based update option was introduced later in the beta cycle. Since you were on beta 6 then you need to at the very least download the ZIP release and overwrite the bzimage and bzroot files. As I mentioned you should also reset the plugins folder (or remove the plugins before you try the update) and afterwards only install plugins that are certified as being compatible with the 6.1 release. Quote Link to comment
Rick Sanchez Posted October 9, 2015 Share Posted October 9, 2015 Ok, last question before I start. Is: 2015-09-20 unRAIDServer-6.1.3-x86_64.zip 2e5adccd90170075f6947daf1a7165e3 compatible with Intel? As it no longer states whether it is or isn't. Quote Link to comment
BRiT Posted October 9, 2015 Share Posted October 9, 2015 Ok, last question before I start. Is: 2015-09-20 unRAIDServer-6.1.3-x86_64.zip 2e5adccd90170075f6947daf1a7165e3 compatible with Intel? As it no longer states whether it is or isn't. No, it does state it explicitly. It explicitly states its compatible with any chip that can handle x86_64; that means 64 bit x86 cpus which means intel and amd. Quote Link to comment
itimpi Posted October 9, 2015 Share Posted October 9, 2015 Ok, last question before I start. Is: 2015-09-20 unRAIDServer-6.1.3-x86_64.zip 2e5adccd90170075f6947daf1a7165e3 compatible with Intel? As it no longer states whether it is or isn't. What might make you think it might not be? unRAID has always been compatible with Intel. It is not available on any platform that is not Intel compatible. The difference is that v6 requires a 64-bit Intel compatible platform. In my experience in practise one can normally assume any download that has 'x86_64' as part of the file name is 64-bit and Intel compatible. Quote Link to comment
trurl Posted October 9, 2015 Share Posted October 9, 2015 Ok, last question before I start. Is: 2015-09-20 unRAIDServer-6.1.3-x86_64.zip 2e5adccd90170075f6947daf1a7165e3 compatible with Intel? As it no longer states whether it is or isn't. If you delete plugins, config/plugins, and extra folders from your flash, and copy bzroot, bzimage, and config/go from the zip you should be good. When unRAID boots, it will only automatically load stuff from those folders and run whatever go has in it. Or you could just take a screenshot of your drive assignments and do a clean install. A clean install would get rid of any crud you might have acquired and might also be a good refresher course in how to set up your server. Quote Link to comment
HellDiverUK Posted October 9, 2015 Share Posted October 9, 2015 The difference is that v6 requires a 64-bit Intel compatible platform. In my experience in practise one can normally assume any download that has 'x86_64' as part of the file name is 64-bit and Intel compatible. Ironically, it's Intel that's compatible with AMD64, as AMD did 64-bit extensions first. So, really, it's and AMD64 requirement, not Intel at all. If Intel were left alone, we'd all be using Itanium IA64, which is horrible. Quote Link to comment
Rick Sanchez Posted October 9, 2015 Share Posted October 9, 2015 Ok, last question before I start. Is: 2015-09-20 unRAIDServer-6.1.3-x86_64.zip 2e5adccd90170075f6947daf1a7165e3 compatible with Intel? As it no longer states whether it is or isn't. What might make you think it might not be? unRAID has always been compatible with Intel. It is not available on any platform that is not Intel compatible. The difference is that v6 requires a 64-bit Intel compatible platform. In my experience in practise one can normally assume any download that has 'x86_64' as part of the file name is 64-bit and Intel compatible. Ok, thanks. The old versions had amd_ etc Quote Link to comment
RobJ Posted October 9, 2015 Share Posted October 9, 2015 If you installed dockerman files or the VM Manager plugin, they must be uninstalled. Does that mean this: IP Address/Extensions/Dockers or the Docker Manger plugin? I cannot remember if I installed VM Manager; where would I find it? If you created a docker.img file with an earlier v6 beta, you may have to delete and recreate it. Same questions I appreciate your questions, as I had to be vague with those instructions, no first-hand experience with early v6 betas. I've tried to improve that section now, partly using your screen pic (thank you!), and if you have time I would appreciate your review and any suggestions for further improvement. I'm hopeful though that soon, that section won't be needed, be obsolete. It's going to be difficult to understand why someone bold enough to install an early beta would not be fully current by now. Quote Link to comment
BobPhoenix Posted October 9, 2015 Share Posted October 9, 2015 I'm hopeful though that soon, that section won't be needed, be obsolete. It's going to be difficult to understand why someone bold enough to install an early beta would not be fully current by now. I can think of one reason. If you were using a Windows VM in XEN and don't want to reactivate when switching to KVM. Quote Link to comment
trurl Posted October 9, 2015 Share Posted October 9, 2015 ... It's going to be difficult to understand why someone bold enough to install an early beta would not be fully current by now. Much worse than still being on v4.7. At least in that case someone may still be running it, or at least still likely to remember it since it was around for a while. Fortunately, unRAID is designed so you can always start clean if necessary. I can think of one reason. If you were using a Windows VM in XEN and don't want to reactivate when switching to KVM. There is the XEN factor. I wonder how many others are still using it? Quote Link to comment
Rick Sanchez Posted October 9, 2015 Share Posted October 9, 2015 I appreciate your questions, as I had to be vague with those instructions, no first-hand experience with early v6 betas. I've tried to improve that section now, partly using your screen pic (thank you!), and if you have time I would appreciate your review and any suggestions for further improvement. I'm hopeful though that soon, that section won't be needed, be obsolete. It's going to be difficult to understand why someone bold enough to install an early beta would not be fully current by now. Not a problem. I was run over and spent ages in hospital due to complications which is why I haven't kept up to date but some of the features I used at the time were not compatible either. ---------------- Not for beta 6. The GUI based update option was introduced later in the beta cycle. Since you were on beta 6 then you need to at the very least download the ZIP release and overwrite the bzimage and bzroot files. As I mentioned you should also reset the plugins folder (or remove the plugins before you try the update) and afterwards only install plugins that are certified as being compatible with the 6.1 release. Do I remove the plugins from within UnRAID GUI or? - The only plugin I can remove is Docker from the GUI Can I leave docker? I really hope I can lol Quote Link to comment
itimpi Posted October 9, 2015 Share Posted October 9, 2015 Do I remove the plugins from within UnRAID GUI or? - The only plugin I can remove is Docker from the GUI You need to remove all the current plugins. The easiest way is to remove the plugins and config/plugins folders from the USB stick. As has been mentioned Docker Manager is now built into the standard unRAID release. You probably want to take screenshots of your current Docker settings to help with getting them back up an running under 6.1.3. The built-in one will have improved functionality over the older version from the beta cycle. VM Manager is now also built in and used to manage VM's under KVM. Not sure if you had any Xen VM's that need to be migrated to KVM? If you want to install plugins after doing the upgrade you should stick to the ones that are listed in the Plugins->6.1 (verified) part of the forum as plugins that have not been updated to be compatible with the improved security model introduced with the 6.1 release are likely to break. Quote Link to comment
Rick Sanchez Posted October 9, 2015 Share Posted October 9, 2015 Do I remove the docker share as well? Quote Link to comment
trurl Posted October 9, 2015 Share Posted October 9, 2015 Do I remove the docker share as well? Do you mean you have a user share named docker, or do you mean the docker .img file? Quote Link to comment
Rick Sanchez Posted October 9, 2015 Share Posted October 9, 2015 User share. I have no idea where the .img is! Quote Link to comment
trurl Posted October 9, 2015 Share Posted October 9, 2015 User share. I have no idea where the .img is! The docker .img file is a "virtual disk" that stores the actual code for all the dockers. Maybe you put it in your docker share. Is your docker share a cache-only share? Maybe if you post a screenshot of your current docker page it would help us see where you are. Quote Link to comment
Rick Sanchez Posted October 9, 2015 Share Posted October 9, 2015 (edited) Use cache disk: No Edited May 10, 2018 by Rick Sanchez Quote Link to comment
trurl Posted October 9, 2015 Share Posted October 9, 2015 Do you have a docker management page? If so, a screenshot might be able to save a lot of questions. Quote Link to comment
Rick Sanchez Posted October 9, 2015 Share Posted October 9, 2015 I've deleted all dockers and images Quote Link to comment
trurl Posted October 9, 2015 Share Posted October 9, 2015 I've deleted all dockers and images OK. Have you decided to do a clean install then? If not, what exactly are you hoping to preserve? Quote Link to comment
Rick Sanchez Posted October 9, 2015 Share Posted October 9, 2015 OK. Have you decided to do a clean install then? I thought that was required. If not, what exactly are you hoping to preserve? Nothing now; except my data lol -------------------- All working now thank you for your help guys! Quote Link to comment
johnodon Posted October 10, 2015 Share Posted October 10, 2015 EDIT: Just checked and SAB is running a repair on a download. Not sure it it is related but figured I would throw it out there. Maybe my VM and SAB are competing for the same CPUs? Just got these in my syslog. Nothing has crashed. CPUs 12 ann 13 are pinned to one of my OE VMs that I PXE boot (using NFS for the storage disk). Oct 10 19:54:00 unRAID kernel: ------------[ cut here ]------------ Oct 10 19:54:00 unRAID kernel: WARNING: CPU: 12 PID: 2866 at fs/nfsd/nfsproc.c:756 nfserrno+0x45/0x4c() Oct 10 19:54:00 unRAID kernel: nfsd: non-standard errno: -38 Oct 10 19:54:00 unRAID kernel: Modules linked in: xt_CHECKSUM ipt_REJECT nf_reject_ipv4 ebtable_filter ebtables kvm_intel kvm vhost_net vhost macvtap macvlan tun iptable_mangle xt_nat veth ipt_MASQUERADE nf_nat_masquerade_ipv4 iptable_nat nf_conntrack_ipv4 nf_nat_ipv4 iptable_filter ip_tables nf_nat md_mod igb i2c_algo_bit mvsas ahci i2c_i801 libsas libahci ptp scsi_transport_sas pps_core ipmi_si acpi_cpufreq Oct 10 19:54:00 unRAID kernel: CPU: 12 PID: 2866 Comm: nfsd Not tainted 4.1.7-unRAID #3 Oct 10 19:54:00 unRAID kernel: Hardware name: Supermicro X8DTH-i/6/iF/6F/X8DTH, BIOS 2.1b 05/04/12 Oct 10 19:54:00 unRAID kernel: 0000000000000009 ffff88000223bca8 ffffffff815eff9a 0000000000000000 Oct 10 19:54:00 unRAID kernel: ffff88000223bcf8 ffff88000223bce8 ffffffff810477cb 0000000000000000 Oct 10 19:54:00 unRAID kernel: ffffffff811e0f27 ffff880c61672408 ffff880c61672548 ffff880c43ecc0c0 Oct 10 19:54:00 unRAID kernel: Call Trace: Oct 10 19:54:00 unRAID kernel: [] dump_stack+0x4c/0x6e Oct 10 19:54:00 unRAID kernel: [] warn_slowpath_common+0x97/0xb1 Oct 10 19:54:00 unRAID kernel: [] ? nfserrno+0x45/0x4c Oct 10 19:54:00 unRAID kernel: [] warn_slowpath_fmt+0x41/0x43 Oct 10 19:54:00 unRAID kernel: [] nfserrno+0x45/0x4c Oct 10 19:54:00 unRAID kernel: [] nfsd_link+0x1f5/0x299 Oct 10 19:54:00 unRAID kernel: [] nfsd3_proc_link+0xb1/0xc0 Oct 10 19:54:00 unRAID kernel: [] nfsd_dispatch+0x93/0x14e Oct 10 19:54:00 unRAID kernel: [] svc_process+0x3c3/0x60f Oct 10 19:54:00 unRAID kernel: [] nfsd+0x106/0x158 Oct 10 19:54:00 unRAID kernel: [] ? nfsd_destroy+0x6f/0x6f Oct 10 19:54:00 unRAID kernel: [] kthread+0xd6/0xde Oct 10 19:54:00 unRAID kernel: [] ? kthread_create_on_node+0x172/0x172 Oct 10 19:54:00 unRAID kernel: [] ret_from_fork+0x42/0x70 Oct 10 19:54:00 unRAID kernel: [] ? kthread_create_on_node+0x172/0x172 Oct 10 19:54:00 unRAID kernel: ---[ end trace 3fbf405d57f675a1 ]--- Oct 10 19:54:00 unRAID kernel: ------------[ cut here ]------------ Oct 10 19:54:00 unRAID kernel: WARNING: CPU: 12 PID: 2866 at fs/nfsd/nfsproc.c:756 nfserrno+0x45/0x4c() Oct 10 19:54:00 unRAID kernel: nfsd: non-standard errno: -38 Oct 10 19:54:00 unRAID kernel: Modules linked in: xt_CHECKSUM ipt_REJECT nf_reject_ipv4 ebtable_filter ebtables kvm_intel kvm vhost_net vhost macvtap macvlan tun iptable_mangle xt_nat veth ipt_MASQUERADE nf_nat_masquerade_ipv4 iptable_nat nf_conntrack_ipv4 nf_nat_ipv4 iptable_filter ip_tables nf_nat md_mod igb i2c_algo_bit mvsas ahci i2c_i801 libsas libahci ptp scsi_transport_sas pps_core ipmi_si acpi_cpufreq Oct 10 19:54:00 unRAID kernel: CPU: 12 PID: 2866 Comm: nfsd Tainted: G W 4.1.7-unRAID #3 Oct 10 19:54:00 unRAID kernel: Hardware name: Supermicro X8DTH-i/6/iF/6F/X8DTH, BIOS 2.1b 05/04/12 Oct 10 19:54:00 unRAID kernel: 0000000000000009 ffff88000223bca8 ffffffff815eff9a 0000000000000000 Oct 10 19:54:00 unRAID kernel: ffff88000223bcf8 ffff88000223bce8 ffffffff810477cb 0000000000000000 Oct 10 19:54:00 unRAID kernel: ffffffff811e0f27 ffff880c61672408 ffff880c61672548 ffff880c19431680 Oct 10 19:54:00 unRAID kernel: Call Trace: Oct 10 19:54:00 unRAID kernel: [] dump_stack+0x4c/0x6e Oct 10 19:54:00 unRAID kernel: [] warn_slowpath_common+0x97/0xb1 Oct 10 19:54:00 unRAID kernel: [] ? nfserrno+0x45/0x4c Oct 10 19:54:00 unRAID kernel: [] warn_slowpath_fmt+0x41/0x43 Oct 10 19:54:00 unRAID kernel: [] nfserrno+0x45/0x4c Oct 10 19:54:00 unRAID kernel: [] nfsd_link+0x1f5/0x299 Oct 10 19:54:00 unRAID kernel: [] nfsd3_proc_link+0xb1/0xc0 Oct 10 19:54:00 unRAID kernel: [] nfsd_dispatch+0x93/0x14e Oct 10 19:54:00 unRAID kernel: [] svc_process+0x3c3/0x60f Oct 10 19:54:00 unRAID kernel: [] nfsd+0x106/0x158 Oct 10 19:54:00 unRAID kernel: [] ? nfsd_destroy+0x6f/0x6f Oct 10 19:54:00 unRAID kernel: [] kthread+0xd6/0xde Oct 10 19:54:00 unRAID kernel: [] ? kthread_create_on_node+0x172/0x172 Oct 10 19:54:00 unRAID kernel: [] ret_from_fork+0x42/0x70 Oct 10 19:54:00 unRAID kernel: [] ? kthread_create_on_node+0x172/0x172 Oct 10 19:54:00 unRAID kernel: ---[ end trace 3fbf405d57f675a2 ]--- Oct 10 19:54:00 unRAID kernel: ------------[ cut here ]------------ Oct 10 19:54:00 unRAID kernel: WARNING: CPU: 13 PID: 2866 at fs/nfsd/nfsproc.c:756 nfserrno+0x45/0x4c() Oct 10 19:54:00 unRAID kernel: nfsd: non-standard errno: -38 Oct 10 19:54:00 unRAID kernel: Modules linked in: xt_CHECKSUM ipt_REJECT nf_reject_ipv4 ebtable_filter ebtables kvm_intel kvm vhost_net vhost macvtap macvlan tun iptable_mangle xt_nat veth ipt_MASQUERADE nf_nat_masquerade_ipv4 iptable_nat nf_conntrack_ipv4 nf_nat_ipv4 iptable_filter ip_tables nf_nat md_mod igb i2c_algo_bit mvsas ahci i2c_i801 libsas libahci ptp scsi_transport_sas pps_core ipmi_si acpi_cpufreq Oct 10 19:54:00 unRAID kernel: CPU: 13 PID: 2866 Comm: nfsd Tainted: G W 4.1.7-unRAID #3 Oct 10 19:54:00 unRAID kernel: Hardware name: Supermicro X8DTH-i/6/iF/6F/X8DTH, BIOS 2.1b 05/04/12 Oct 10 19:54:00 unRAID kernel: 0000000000000009 ffff88000223bca8 ffffffff815eff9a 0000000000000000 Oct 10 19:54:00 unRAID kernel: ffff88000223bcf8 ffff88000223bce8 ffffffff810477cb 0000000000000000 Oct 10 19:54:00 unRAID kernel: ffffffff811e0f27 ffff880c61672408 ffff880c61672548 ffff880a33698d80 Oct 10 19:54:00 unRAID kernel: Call Trace: Oct 10 19:54:00 unRAID kernel: [] dump_stack+0x4c/0x6e Oct 10 19:54:00 unRAID kernel: [] warn_slowpath_common+0x97/0xb1 Oct 10 19:54:00 unRAID kernel: [] ? nfserrno+0x45/0x4c Oct 10 19:54:00 unRAID kernel: [] warn_slowpath_fmt+0x41/0x43 Oct 10 19:54:00 unRAID kernel: [] nfserrno+0x45/0x4c Oct 10 19:54:00 unRAID kernel: [] nfsd_link+0x1f5/0x299 Oct 10 19:54:00 unRAID kernel: [] nfsd3_proc_link+0xb1/0xc0 Oct 10 19:54:00 unRAID kernel: [] nfsd_dispatch+0x93/0x14e Oct 10 19:54:00 unRAID kernel: [] svc_process+0x3c3/0x60f Oct 10 19:54:00 unRAID kernel: [] nfsd+0x106/0x158 Oct 10 19:54:00 unRAID kernel: [] ? nfsd_destroy+0x6f/0x6f Oct 10 19:54:00 unRAID kernel: [] kthread+0xd6/0xde Oct 10 19:54:00 unRAID kernel: [] ? kthread_create_on_node+0x172/0x172 Oct 10 19:54:00 unRAID kernel: [] ret_from_fork+0x42/0x70 Oct 10 19:54:00 unRAID kernel: [] ? kthread_create_on_node+0x172/0x172 Oct 10 19:54:00 unRAID kernel: ---[ end trace 3fbf405d57f675a3 ]--- Quote Link to comment
Recommended Posts
Join the conversation
You can post now and register later. If you have an account, sign in now to post with your account.
Note: Your post will require moderator approval before it will be visible.