sacretagent Posted January 23, 2014 Share Posted January 23, 2014 hi Tom, a few observations no more /boot/plugins folder ? you moved the gui again to /boot/config/plugins no /boot/packages does that mean that if we make these folders that the new 64 bit unraid will not install anything from these folders ? guess to get KVM / libvirt and virt manager installed that the easiest way would be to dump them in /boot/packages but if that doesn't work any more then we will need to spam the go file again ? oh libvirt and qemu are installed already.... ooops gonna need to find another how to LOL Quote Link to comment
bonienl Posted January 23, 2014 Share Posted January 23, 2014 no more /boot/plugins folder ? you moved the gui again to /boot/config/plugins The webGui is now integrated and doesn't need to be stored on flash anymore. System plugins can still be put in /boot/plugins, this works! By desgin setting files are stored in the folder '/boot/config/plugins/<plugin-name>', hence the folder '/boot/config/plugins/webGui' Quote Link to comment
Tim Timmens Posted January 23, 2014 Share Posted January 23, 2014 Probably a silly question, Will upgrading to 64 bit increase my transfer speeds? Quote Link to comment
ironicbadger Posted January 23, 2014 Share Posted January 23, 2014 Probably a silly question, Will upgrading to 64 bit increase my transfer speeds? So I've just conducted a highly scientific test (and by that I mean completely ad-hoc). The last 24 hours I was actually moving several TBs of data off my old unRAID rig onto a test machine, also running unRAID, and after approximately 4TB the average transfer rate via NFS was 42MB/s. I'm only 13mins into a v6 test of the exact same thing but my average speed is hovering around almost exactly 42MB/s. So in short, no. To disable the banner, as was previously asked just go here. Quote Link to comment
sacretagent Posted January 23, 2014 Share Posted January 23, 2014 Not sure where to put this .... in this thread or make a new one in the virtualization board but we are missing something to make libvirt work root@Tower:/etc/rc.d# rc.libvirt restart libvirt is not running... root@Tower:/etc/rc.d# rc.libvirt start Starting libvirtd... p11-kit: couldn't load module: /usr/lib64/pkcs11/p11-kit-trust.so: libtasn1.so.6: cannot open shared object file: No such file or directory root@Tower:/etc/rc.d# virsh -c qemu+tcp://192.168.1.10/system nodeinfo p11-kit: couldn't load module: /usr/lib64/pkcs11/p11-kit-trust.so: libtasn1.so.6: cannot open shared object file: No such file or directory CPU model: x86_64 CPU(s): 2 CPU frequency: 2800 MHz CPU socket(s): 1 Core(s) per socket: 2 Thread(s) per core: 1 NUMA cell(s): 1 Memory size: 3962900 KiB not sure what it means ....not used to KVM so doing everything with the help of google how to's also how are we supposed to make changes to /etc/libvert/libvertd.conf stick ? was hoping to get a test vm running .... but seems my google fu is coming up short Quote Link to comment
splnut Posted January 23, 2014 Share Posted January 23, 2014 Not sure where to put this .... in this thread or make a new one in the virtualization board but we are missing something to make libvirt work root@Tower:/etc/rc.d# rc.libvirt restart libvirt is not running... root@Tower:/etc/rc.d# rc.libvirt start Starting libvirtd... p11-kit: couldn't load module: /usr/lib64/pkcs11/p11-kit-trust.so: libtasn1.so.6: cannot open shared object file: No such file or directory root@Tower:/etc/rc.d# virsh -c qemu+tcp://192.168.1.10/system nodeinfo p11-kit: couldn't load module: /usr/lib64/pkcs11/p11-kit-trust.so: libtasn1.so.6: cannot open shared object file: No such file or directory CPU model: x86_64 CPU(s): 2 CPU frequency: 2800 MHz CPU socket(s): 1 Core(s) per socket: 2 Thread(s) per core: 1 NUMA cell(s): 1 Memory size: 3962900 KiB not sure what it means ....not used to KVM so doing everything with the help of google how to's also how are we supposed to make changes to /etc/libvert/libvertd.conf stick ? was hoping to get a test vm running .... but seems my google fu is coming up short Experienced the same thing last night. Also had an error with virsh but it was late when I was playing with it. Will play more today. Webgui seems snappier, dont like the banner image but can disable it. Transferred data to and from a 250gb drive just fine. Quote Link to comment
Ford Prefect Posted January 23, 2014 Share Posted January 23, 2014 Not sure where to put this .... in this thread or make a new one in the virtualization board but we are missing something to make libvirt work root@Tower:/etc/rc.d# rc.libvirt restart libvirt is not running... root@Tower:/etc/rc.d# rc.libvirt start Starting libvirtd... p11-kit: couldn't load module: /usr/lib64/pkcs11/p11-kit-trust.so: libtasn1.so.6: cannot open shared object file: No such file or directory root@Tower:/etc/rc.d# virsh -c qemu+tcp://192.168.1.10/system nodeinfo p11-kit: couldn't load module: /usr/lib64/pkcs11/p11-kit-trust.so: libtasn1.so.6: cannot open shared object file: No such file or directory CPU model: x86_64 CPU(s): 2 CPU frequency: 2800 MHz CPU socket(s): 1 Core(s) per socket: 2 Thread(s) per core: 1 NUMA cell(s): 1 Memory size: 3962900 KiB not sure what it means ....not used to KVM so doing everything with the help of google how to's also how are we supposed to make changes to /etc/libvert/libvertd.conf stick ? was hoping to get a test vm running .... but seems my google fu is coming up short ...does libvirtd refuse to start?...might be possible to at least use it local from your root account/user. FAIR this is for security/ACL. you can control your VMs via virt-manager/virsh remotely from another client. Ultimately this lib should be supplied to run everything headless and enable remote management for VMs. Quote Link to comment
binhex Posted January 23, 2014 Share Posted January 23, 2014 maybe adding in this package may get around the issue with "p11-kit: couldn't load module: /usr/lib64/pkcs11/p11-kit-trust.so" http://search.slackware.eu/cgi-bin/package.cgi/view/slackware64-14.1/slackware64/n/p11-kit-0.16.4-x86_64-1.txz the following link shows a more detailed description of what's included in the package:- http://search.slackware.eu/cgi-bin/package.cgi/inspect/slackware64-current/slackware64/n/p11-kit-0.16.4-x86_64-1.txz im guessing this should of been included in the image, maybe missed off? Quote Link to comment
vl1969 Posted January 23, 2014 Share Posted January 23, 2014 so , how does this work? do I need special VHD image to run this in VM? do I just boot this from USB and can do virtualization from that? Quote Link to comment
limetech Posted January 23, 2014 Author Share Posted January 23, 2014 hi Tom, a few observations no more /boot/plugins folder ? you moved the gui again to /boot/config/plugins no /boot/packages does that mean that if we make these folders that the new 64 bit unraid will not install anything from these folders ? Those folders are still valid, probably should have included them in the build, I'll fix that in next beta, though some good ideas posted earlier about adding a _64 suffix or something. Only the webGui config file is stored in /boot/config/plugins/webGui - but file won't get created until you save a preference. guess to get KVM / libvirt and virt manager installed that the easiest way would be to dump them in /boot/packages but if that doesn't work any more then we will need to spam the go file again ? oh libvirt and qemu are installed already.... ooops gonna need to find another how to LOL There might be some things missing since I didn't explicitly test VM capabilities. As these come up I'll add to build. This is the main purpose of the -beta cycle. Quote Link to comment
limetech Posted January 23, 2014 Author Share Posted January 23, 2014 The webGui is now integrated and doesn't need to be stored on flash anymore. System plugins can still be put in /boot/plugins, this works! Right. When/if you download an updated webGui from github, the .plg file along with .gz file will land in /boot/plugins. By desgin setting files are stored in the folder '/boot/config/plugins/<plugin-name>', hence the folder '/boot/config/plugins/webGui' Correct. Quote Link to comment
limetech Posted January 23, 2014 Author Share Posted January 23, 2014 maybe adding in this package may get around the issue with "p11-kit: couldn't load module: /usr/lib64/pkcs11/p11-kit-trust.so" http://search.slackware.eu/cgi-bin/package.cgi/view/slackware64-14.1/slackware64/n/p11-kit-0.16.4-x86_64-1.txz the following link shows a more detailed description of what's included in the package:- http://search.slackware.eu/cgi-bin/package.cgi/inspect/slackware64-current/slackware64/n/p11-kit-0.16.4-x86_64-1.txz im guessing this should of been included in the image, maybe missed off? I'll add missing packages to the build. BTW, you can see the list of packages comprising the build in /var/log/packages. Quote Link to comment
garycase Posted January 23, 2014 Share Posted January 23, 2014 It does not support anymore IDE interfaces (hdX). My cache drive happens to be on IDE and disappeared. I'll look into that... Not sure why bonienl's IDE drive isn't seen, but mine works fine (the port was disabled in the BIOS on the old Dell OptiPlex I set this up on ... fixed that and it works just fine). Quote Link to comment
binhex Posted January 23, 2014 Share Posted January 23, 2014 I'll add missing packages to the build. BTW, you can see the list of packages comprising the build in /var/log/packages. great!, thanks for the tip Tom. Quote Link to comment
jphipps Posted January 23, 2014 Share Posted January 23, 2014 If we boot up an existing cluster with the new beta, is there any issues if we roll back to 5.0.5? Quote Link to comment
bonienl Posted January 23, 2014 Share Posted January 23, 2014 Not sure why bonienl's IDE drive isn't seen, but mine works fine (the port was disabled in the BIOS on the old Dell OptiPlex I set this up on ... fixed that and it works just fine). In my case nothing is detected for IDE (no probing) in the syslog of version 6.0, just the SATA ports. As a reference below an extract of the syslog of version 5.0.5 which DOES detect IDE (maybe this helps ?) And attached the complete v6.0 syslog. Jan 23 18:56:44 vesta kernel: atiixp 0000:00:14.1: IDE controller (0x1002:0x439c rev 0x00) Jan 23 18:56:44 vesta kernel: atiixp 0000:00:14.1: not 100%% native mode: will probe irqs later Jan 23 18:56:44 vesta kernel: ide0: BM-DMA at 0xff00-0xff07 Jan 23 18:56:44 vesta kernel: atiixp 0000:00:14.1: simplex device: DMA disabled Jan 23 18:56:44 vesta kernel: ide1: DMA disabled Jan 23 18:56:44 vesta kernel: Probing IDE interface ide0... Jan 23 18:56:44 vesta kernel: scsi1 : sata_sil24 Jan 23 18:56:44 vesta kernel: sata_mv 0000:02:00.0: version 1.28 Jan 23 18:56:44 vesta kernel: sata_mv 0000:02:00.0: Gen-IIE 32 slots 4 ports ? mode IRQ via INTx Jan 23 18:56:44 vesta kernel: scsi2 : sata_sil24 Jan 23 18:56:44 vesta kernel: ata1: SATA max UDMA/100 host m128@0xfe9ffc00 port 0xfe9f8000 irq 17 Jan 23 18:56:44 vesta kernel: ata2: SATA max UDMA/100 host m128@0xfe9ffc00 port 0xfe9fa000 irq 17 Jan 23 18:56:44 vesta kernel: scsi3 : sata_mv Jan 23 18:56:44 vesta kernel: scsi4 : sata_mv Jan 23 18:56:44 vesta kernel: scsi5 : sata_mv Jan 23 18:56:44 vesta kernel: scsi6 : sata_mv Jan 23 18:56:44 vesta kernel: ata3: SATA max UDMA/133 mmio m1048576@0xfe800000 port 0xfe822000 irq 18 Jan 23 18:56:44 vesta kernel: ata4: SATA max UDMA/133 mmio m1048576@0xfe800000 port 0xfe824000 irq 18 Jan 23 18:56:44 vesta kernel: ata5: SATA max UDMA/133 mmio m1048576@0xfe800000 port 0xfe826000 irq 18 Jan 23 18:56:44 vesta kernel: ata6: SATA max UDMA/133 mmio m1048576@0xfe800000 port 0xfe828000 irq 18 Jan 23 18:56:44 vesta kernel: ata3: SATA link up 3.0 Gbps (SStatus 123 SControl 300) Jan 23 18:56:44 vesta kernel: hdb: WDC WD1600AAJB-00J3A0, ATA DISK drive Jan 23 18:56:44 vesta kernel: hdb: host max PIO4 wanted PIO255(auto-tune) selected PIO4 Jan 23 18:56:44 vesta kernel: hdb: UDMA/100 mode selected Jan 23 18:56:44 vesta kernel: Probing IDE interface ide1... Jan 23 18:56:44 vesta kernel: ata3.00: ATA-8: WDC WD20EARS-00J2GB0, WD-WCAYY0068117, 80.00A80, max UDMA/133 Jan 23 18:56:44 vesta kernel: ata3.00: 3907029168 sectors, multi 0: LBA48 NCQ (depth 31/32) Jan 23 18:56:44 vesta kernel: ata3.00: configured for UDMA/133 Jan 23 18:56:44 vesta kernel: ide0 at 0x1f0-0x1f7,0x3f6 on irq 14 Jan 23 18:56:44 vesta kernel: ide1 at 0x170-0x177,0x376 on irq 15 Jan 23 18:56:44 vesta kernel: ahci 0000:00:11.0: version 3.0 Jan 23 18:56:44 vesta kernel: ahci 0000:00:11.0: AHCI 0001.0100 32 slots 6 ports 3 Gbps 0x3f impl SATA mode Jan 23 18:56:44 vesta kernel: ahci 0000:00:11.0: flags: 64bit ncq sntf ilck pm led clo pmp pio slum part ccc Jan 23 18:56:44 vesta kernel: scsi7 : ahci Jan 23 18:56:44 vesta kernel: scsi8 : ahci Jan 23 18:56:44 vesta kernel: scsi9 : ahci Jan 23 18:56:44 vesta kernel: scsi10 : ahci Jan 23 18:56:44 vesta kernel: scsi11 : ahci Jan 23 18:56:44 vesta kernel: scsi12 : ahci Jan 23 18:56:44 vesta kernel: ata7: SATA max UDMA/133 abar m1024@0xfe3ffc00 port 0xfe3ffd00 irq 22 Jan 23 18:56:44 vesta kernel: ata8: SATA max UDMA/133 abar m1024@0xfe3ffc00 port 0xfe3ffd80 irq 22 Jan 23 18:56:44 vesta kernel: ata9: SATA max UDMA/133 abar m1024@0xfe3ffc00 port 0xfe3ffe00 irq 22 Jan 23 18:56:44 vesta kernel: ata10: SATA max UDMA/133 abar m1024@0xfe3ffc00 port 0xfe3ffe80 irq 22 Jan 23 18:56:44 vesta kernel: ata11: SATA max UDMA/133 abar m1024@0xfe3ffc00 port 0xfe3fff00 irq 22 Jan 23 18:56:44 vesta kernel: ata12: SATA max UDMA/133 abar m1024@0xfe3ffc00 port 0xfe3fff80 irq 22 Jan 23 18:56:44 vesta kernel: ide-gd driver 1.18 Jan 23 18:56:44 vesta kernel: hdb: max request size: 512KiB Jan 23 18:56:44 vesta kernel: hdb: 312581808 sectors (160041 MB) w/8192KiB Cache, CHS=19457/255/63 Jan 23 18:56:44 vesta kernel: hdb: cache flushes supported Jan 23 18:56:44 vesta kernel: hdb: hdb1 Jan 23 18:56:44 vesta kernel: ata8: SATA link up 3.0 Gbps (SStatus 123 SControl 300) Jan 23 18:56:44 vesta kernel: ata7: SATA link up 3.0 Gbps (SStatus 123 SControl 300) Jan 23 18:56:44 vesta kernel: ata9: SATA link up 3.0 Gbps (SStatus 123 SControl 300) Jan 23 18:56:44 vesta kernel: ata10: SATA link up 3.0 Gbps (SStatus 123 SControl 300) syslog.zip Quote Link to comment
PeterB Posted January 23, 2014 Share Posted January 23, 2014 It has been suggested that discussion of x86_64 plugins is off-topic for this thread, so I seek advice on where I should post information relating to my successful conversion of the apcupsd plugin. Quote Link to comment
garycase Posted January 23, 2014 Share Posted January 23, 2014 It has been suggested that discussion of x86_64 plugins is off-topic for this thread, so I seek advice on where I should post information relating to my successful conversion of the apcupsd plugin. Just start a new thread titled "APCUPSD Plugin for x64" in the "User Customizations" area ... I'm sure there's a VERY high interest in having this plugin !! Quote Link to comment
meoge Posted January 23, 2014 Share Posted January 23, 2014 So I upgraded from 5.0.4. I was running a clean install with no plugins except the webgui. I copied over bzimage, bzroot, memtest and readme files and rebooted server. Server started, but I now get this message at the bottom of the page: Fatal error: Call-time pass-by-reference has been removed in /usr/local/emhttp/plugins/webGui/include/myPage_content.php(61) : eval()'d code on line 56 Any idea how to fix that? The issue is I don't have the ability to stop or reboot from the gui at this point. Quote Link to comment
Ockingshay Posted January 23, 2014 Share Posted January 23, 2014 It has been suggested that discussion of x86_64 plugins is off-topic for this thread, so I seek advice on where I should post information relating to my successful conversion of the apcupsd plugin. Just start a new thread titled "APCUPSD Plugin for x64" in the "User Customizations" area ... I'm sure there's a VERY high interest in having this plugin !! Since version 5 final this has been requested to reorganise the forums, and now another chance with a major milestone is about to be missed, as duplicate threads are being made all over the place. Is this something only Tom can do?, who understandably is extremely busy or can the mods sort it out?, or if not, promote one to admin and/or get someone like harmser to do it. The longer this is left the more time consuming it is to clean up. http://lime-technology.com/forum/index.php?topic=30384.0: 261 views and not even one curtesy response from staff. Quote Link to comment
bonienl Posted January 23, 2014 Share Posted January 23, 2014 So I upgraded from 5.0.4. I was running a clean install with no plugins except the webgui. I copied over bzimage, bzroot, memtest and readme files and rebooted server. Server started, but I now get this message at the bottom of the page: Fatal error: Call-time pass-by-reference has been removed in /usr/local/emhttp/plugins/webGui/include/myPage_content.php(61) : eval()'d code on line 56 Any idea how to fix that? The issue is I don't have the ability to stop or reboot from the gui at this point. Remove the old webGui as well (delete folder /boot/plugins) A newer version of PHP is installed together with unRAID v6.0 and some features are depreciated, giving now the error messages. You can reboot from a telnet session after the folder is deleted. Quote Link to comment
RobJ Posted January 23, 2014 Share Posted January 23, 2014 Not sure why bonienl's IDE drive isn't seen, but mine works fine (the port was disabled in the BIOS on the old Dell OptiPlex I set this up on ... fixed that and it works just fine). In my case nothing is detected for IDE (no probing) in the syslog of version 6.0, just the SATA ports. As a reference below an extract of the syslog of version 5.0.5 which DOES detect IDE (maybe this helps ?) And attached the complete v6.0 syslog. Jan 23 18:56:44 vesta kernel: atiixp 0000:00:14.1: IDE controller (0x1002:0x439c rev 0x00) Jan 23 18:56:44 vesta kernel: atiixp 0000:00:14.1: not 100%% native mode: will probe irqs later Jan 23 18:56:44 vesta kernel: ide0: BM-DMA at 0xff00-0xff07 Jan 23 18:56:44 vesta kernel: atiixp 0000:00:14.1: simplex device: DMA disabled Jan 23 18:56:44 vesta kernel: ide1: DMA disabled Jan 23 18:56:44 vesta kernel: Probing IDE interface ide0... ... Jan 23 18:56:44 vesta kernel: hdb: WDC WD1600AAJB-00J3A0, ATA DISK drive Jan 23 18:56:44 vesta kernel: hdb: host max PIO4 wanted PIO255(auto-tune) selected PIO4 Jan 23 18:56:44 vesta kernel: hdb: UDMA/100 mode selected Jan 23 18:56:44 vesta kernel: Probing IDE interface ide1... ... Jan 23 18:56:44 vesta kernel: ide0 at 0x1f0-0x1f7,0x3f6 on irq 14 Jan 23 18:56:44 vesta kernel: ide1 at 0x170-0x177,0x376 on irq 15 ... Jan 23 18:56:44 vesta kernel: ide-gd driver 1.18 Jan 23 18:56:44 vesta kernel: hdb: max request size: 512KiB Jan 23 18:56:44 vesta kernel: hdb: 312581808 sectors (160041 MB) w/8192KiB Cache, CHS=19457/255/63 Jan 23 18:56:44 vesta kernel: hdb: cache flushes supported Jan 23 18:56:44 vesta kernel: hdb: hdb1 Your v6 syslog shows no atiixp, so either it was inadvertently dropped, or perhaps the 64-bit version is not working correctly. Gary, is atiixp showing in your syslog? The atiixp module is used for onboard IDE drives, perhaps Gary's IDE drive is on a different controller? You might enable DMA in your BIOS IDE settings, as it may improve performance to that drive. Confusingly, it says it is using UDMA/100 though! Quote Link to comment
meoge Posted January 23, 2014 Share Posted January 23, 2014 So I upgraded from 5.0.4. I was running a clean install with no plugins except the webgui. I copied over bzimage, bzroot, memtest and readme files and rebooted server. Server started, but I now get this message at the bottom of the page: Fatal error: Call-time pass-by-reference has been removed in /usr/local/emhttp/plugins/webGui/include/myPage_content.php(61) : eval()'d code on line 56 Any idea how to fix that? The issue is I don't have the ability to stop or reboot from the gui at this point. Remove the old webGui as well (delete folder /boot/plugins) A newer version of PHP is installed together with unRAID v6.0 and some features are depreciated, giving now the error messages. You can reboot from a telnet session after the folder is deleted. I've deleted the folder. What is the command I need to type in the telnet session to safely reboot the server? Quote Link to comment
bonienl Posted January 23, 2014 Share Posted January 23, 2014 You might enable DMA in your BIOS IDE settings, as it may improve performance to that drive. Confusingly, it says it is using UDMA/100 though! Thanks for investigating and the tip, will change the DMA setting. I suppose the atiixp module needs to be added to get onbaord IDE working (beta2 ?) Quote Link to comment
jbartlett Posted January 23, 2014 Share Posted January 23, 2014 I've deleted the folder. What is the command I need to type in the telnet session to safely reboot the server? If the array isn't started, type in "reboot" and it should also be safe to simply reset the PC. 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.