BurlyOaf

Members
  • Posts

    20
  • Joined

  • Last visited

Converted

  • Gender
    Undisclosed

BurlyOaf's Achievements

Noob

Noob (1/14)

0

Reputation

  1. Hi All, Did anyone get any further with this? I am having no luck at all, Should there be an xml template for it maybe? It seems the interfaces aren't being assigned in the VM. Also, do i need 2 physical interfaces for this, or can 2 virtuals be created on virbr0 ? Thanks
  2. You are a gentleman, thankyou hopefully it works
  3. bumping an old thread, i am having a go at getting this running as i can't seem to find a docker to do it unfortunately but in the instructions at step 8, 8. Download and copy the following file into the root of your cache drive (/mnt/cache) Customizable PXE Server Menu <--- Download Link the file is no longer there, would anyone have this file on hand and be able to host it somewhere for me to grab please? Cheers,
  4. I am having a similar drama with Sonarr and Mover. mover is scheduled, but doesn't seem to run and has resulted in my cache drive running out of space. i have tried quite a few times, invoking mover, letting it finish, then altering the TV share to not use cache. the next day there is TV present on the cache again, and i have to re-enable cache on the share to get mover to get them from there, then disable mover again. Sonarr is set for /config /mnt/cache/appdata/nzbdrone2/ /mnt/ /mnt/
  5. I had a friend at work try it on his server aswell with the same result ;/
  6. I have tried re-installing a few more times, and still it all looks fine, but no response from server or webui, the tail of my logs looks just like most other peoples, and it just sits there, has anyone had any luck or able to shed any light? my folders are /mnt/disk11/apps/musicbrainz3/data and /mnt/disk11/apps/musicbrainz3/config the folder has been incrementing as i try re-installing
  7. Hi all, i think i am having dramas getting this going, should the webui take hours to become available? The download and building of database *seems* fine. but starting of the server / webui i don't seem to be having any luck with
  8. Hi All, I had an ageing WD RED 3TB that had failed and i replaced it with another WD RED 3TB, everything had been fine, until last night the drive got some read errors after a parity check and a few hours later was disabled. I am chasing advice on what my next move should be, reboot and re-add the drive? Pre clear it again see results then re-add the drive, other suggestions / ideas. I checked and made sure all cables were nicely seated when i put the new drive in but i can check this again. Unfortunately the drive that previously failed has been RMA'd, i was told they would straight swap but wan't the case when i arrived, so i don't currently have a hot spare. My array is 11 3TB drives, one of which is Parity, and an SSD for cache. Last disk in the array is currently disabled. Diagnostics are attached, any help would be greatly appreciated Cheers, ironman-diagnostics-20160419-1141.zip
  9. Hi Guys, Not sure if any of you will be able to help me, i can't get my head around observium, do i install it as bridge or host? if i go bridge i can access observium but can't add any devices, and if i go host it has a cry about sql, i believe because i am already running mysql on port 3306 Ideas? Cheers,
  10. Hi All, Just an update, not really sure what has (hopefully) fixed this, But since doing the BIOS upgrade i had ~2 days stable at work, and have taken it home and had it running for just over 3 days so far, all seems to be running nicely, vm and heaps of dockers running without a drama Happy Days! Cheers
  11. I have just had a look at the console screen, it has the output below. cp: cannot stat '/boot/config/*.conf' : no such file or directory i had a look at some other threads, and typing 'diagnostics' gives the same output, but does create the diagnostics file in /boot/logs My flash is an Imation Nano Pro 8GB, i have seen some suggestions of reformatting and putting unraid back onto the flash. Is that a likely solution?
  12. Thanks for looking Rob, I have left it running since the BIOS upgrade and memory reseat seems fine so far. uptime ~22 hours so far. below is what is in /boot/packages , the only one that i have installed is screen. I had previously thought that UnMENU was the culprit and had not run it, but the crashing happened still. root@IronMan:/boot/packages# ls airvideo-unmenu-package.conf* mover_fix-logging-unmenu-package.conf* apcupsd-3.14.10-unmenu-package-x86_64.conf* mysql-unmenu-package.conf* apcupsd-3.14.10-unmenu-package.conf* ntfs-3g-2010.3.6-unmenu-package.conf* apcupsd-unmenu-package.conf* openssh-unmenu-package.conf* apcupsd3-unmenu-package.conf* openssl-unmenu-package.conf* bwm-ng-unmenu-package-x86_64.conf* p910nd-unmenu-package.conf* bwm-ng-unmenu-package.conf* pbzip2-unmenu-package.conf* compiler-unmenu-package.conf* pciutils-unmenu-package.conf* compiler-unmenu-package_x86_64.conf* perl-unmenu-package.conf* cpio-unmenu-package.conf* php-unmenu-package.conf* cpufrequtils-unmenu-package.conf* powerdown-2.06_ctlaltdel-unmenu-package.conf* cxxlibs-unmenu-package.conf* powerdown-overtemp-unmenu-package.conf* dmidecode-unmenu-package.conf* powerdown_ctlaltdel-unmenu-package.conf* ds_store_cleanup-unmenu-package.conf* proftp-unmenu-package.conf* dynamic-dns-unmenu-package.conf* python-unmenu-package.conf* encfs-unmenu-package.conf* python_cheetah-unmenu-package.conf* file-unmenu-package.conf* reiserfsck-3.6.21-unmenu-package.conf* hdparm-9.27-unmenu-package.conf* rsync-unmenu-package.conf* hdparm-9.37-unmenu-package-1.conf* ruby-unmenu-package.conf* htop-unmenu-package.conf* sabnzbd-unmenu-package.conf* iftop-unmenu-package.conf* screen-4.0.3-x86_64-4.txz* image_server-unmenu-package.conf* screen-4.0.3-x86_64-4.txz.auto_install* inotify-tools-unmenu-package.conf* screen-4.0.3-x86_64-4.txz.manual_install* iperf-unmenu-package.conf* screen-unmenu-package-x86_64.conf* istat-unmenu-package.conf* screen-unmenu-package.conf* jre-unmenu-package.conf* shellinabox-unmenu-package.conf* lighttpd-unmenu-package.conf* smartctl-unmenu-package.conf* lsof-unmenu-package.conf* socat-unmenu-package.conf* mail-ssmtp-unmenu-package-x86_64.conf* sqlite-unmenu-package.conf* mail-ssmtp-unmenu-package.conf* svn-unmenu-package.conf* mail_status-unmenu-package.conf* unraid-web-unmenu-package.conf* md5deep-unmenu-package.conf* unrar-unmenu-package.conf* monthly-parity-unmenu-package.conf* utempter-1.1.5-x86_64-1.txz* mover_conditional_sync-unmenu-package.conf* vim-unmenu-package.conf* mover_exclude_underscore-unmenu-package.conf* zip-unmenu-package.conf* root@IronMan:/boot/packages# 14/07/2015 9:46:23 PM or 9:57PM (trying to suss whether the time in the alert is host system time or gmail's time) but a few minutes either side of the crash it became unresponsive to pings, and it's mac address is unlearnt from my switch. The diagnostic capture was after a reboot, in safe mode. The last crash there was some output i didn't manage to get a photo of, but usually it looks as it does straight from boot, but the cursor stops flashing. The syslog tail was via a screen output to a file. Temperatures all seem hunky dory. ironman-diagnostics-20150716-0803.zip
  13. also I am not sure if this helps or not, but i tailed syslog and dmesg to files yesterday (attached) to see if anything happened before it crashed again (it did) Since then, i have upgraded my bios to version 2103, and reseated ram. Any input would be greatly appreciated, cheers. Syslog output Jul 14 07:58:54 IronMan dnsmasq-dhcp[2423]: read /var/lib/libvirt/dnsmasq/default.hostsfile Jul 14 07:58:54 IronMan kernel: virbr0: port 1(virbr0-nic) entered disabled state Jul 14 07:58:55 IronMan avahi-daemon[2062]: Service "IronMan" (/services/sftp-ssh.service) successfully established. Jul 14 07:58:55 IronMan avahi-daemon[2062]: Service "IronMan" (/services/smb.service) successfully established. Jul 14 07:58:55 IronMan avahi-daemon[2062]: Service "IronMan" (/services/ssh.service) successfully established. Jul 14 07:58:55 IronMan ntpd[1540]: Listen normally on 3 docker0 172.17.42.1:123 Jul 14 07:58:55 IronMan ntpd[1540]: Listen normally on 4 virbr0 192.168.122.1:123 Jul 14 07:58:55 IronMan ntpd[1540]: new interface(s) found: waking up resolver Jul 14 09:21:49 IronMan in.telnetd[13158]: connect from 192.168.1.254 (192.168.1.254) Jul 14 09:21:55 IronMan login[13159]: ROOT LOGIN on '/dev/pts/0' from '192.168.1.254' ironman-dmesg.txt