Jump to content


  • Content Count

  • Joined

  • Last visited

Community Reputation

0 Neutral


  • Rank
    Advanced Member


  • Gender

Recent Profile Visitors

The recent visitors block is disabled and is not being shown to other users.

  1. Thank you guys for a quick response and your comments. I raised this originally as an 'Urgent' due to the fact that I believed something must have changed the USB drive's status during the upgrade process. I did some more reading of other posts and I decided to run the 'make_bootable' app on the USB via my desktop PC. That worked, and the BIOS booted the USB as it should. It ran through first but then got stuck and locked up the server, so I rebooted and then ran GUI with safemode/no plugins. It booted fine with no apparent issues. One more reboot, and I let it bootup normally and everything started as intended, checked logs and all was good.
  2. Hi, I used the Update OS option within the Unraid webpage, it downloaded the files extracted and then told me to reboot the system. I rebooted the system and when going through and past POST, the BIOS stated 'Boot Error' I rebooted again and seleced Force boot USB drive within the BIOS and it still gave me a 'Boot Error' indicating to me that it wasn't in a position to boot the inernal USB drive. The USB device shows up in the BIOS fine so knows it is there and go to excecute but fails. I have a flash copy backup of 6.7.2 my previous version, can I just put that on another USB and boot from that?? Will it cause any issues due to the upgrade proccess being completed? I don't want to go ahead with this step unless I can get some feedback. Thanks.
  3. Hi Constructor... I've deleted the docker.img file from the cache/system folder and the system recreated it but not sure where it put it as it is no longer in 'system'. I looked at previous apps and selected the ones I wanted and HEY PRESTO back to normal working operation with the DOCKER. Great stuff, so thanks for all the DOCKER related info/tips NOW, that moves me onto why ALL my VM's have disappeared any ideas how to get them back?
  4. docker and libvirt files are in the "system" folder which resides on the cache and nowhere else. settings - docker says location : /mnt/user/system/docker/docker.img
  5. Thanks for the replies so far... I tried to connect to SABNZB which in on 8080 - can't be reached... and I also can't connect to any others that I had set up I was running 6.6.5 and upgraded to 6.6.6 when I noticed no dockers, vm's so thought something must have gone wrong with the upgrade so I restored to my previous 6.6.5 which then showed me no dockers., vms I tried the GUI SAFE mode option and after starting the array no dockers or vms. One thing I did see on restarting was the closed down activities and it said stopping docker containers and then it said that libvirt "was not running". What would cause both dockers and vm's to not show up? All shares, disks, plugins, tools all appear to be OK. The app data info is a still there as is appconfig data (well for 2 apps anyway - (musicbrainz& upststaboard) I have backups of my previous unraid root flash files for 6.6.3 / 6.6.2 version, would there be anything in there to help me fix my issue? Anything else I can look at, provide logs, config, settings to assist in the diagnosis and fix?
  6. I've checked the system share and its only on the cache, there are no other system folders on any other drive. I've also gone through the disks and also other shares and cannot see a system folder or the docker.img libvit.img files... I am perplexed why all my dockers' apps have disappeared (dockers appdata is still in the 'AppData' folder) and vm's also not showing but the disks are in the 'domain' folder.
  7. I updated to 6.6.6 and thought everything was good until I noticed that the Dashboard was showing 'No apps available to show' I then checked each of the header sections and DOCKER, is blank ( shouldn't be) also VMs ( I had 3 running) everything else seems fine (drives, shares,plugins are ok) Thinking there was a problem I restored to 6.6.5 and still the same issue, what has gone wrong here? HELP, please. I thought about going back to 6.6.6 but wanted to post in here first for your comments. I've run the Diagnostics Tool and zip attached. goliath-diagnostics-20190109-1208.zip
  8. Hi, I am trying to change from the default naming in the PATH string and it only shows me (title) and wants to delete the existing filename which has "track name - artist". What do I need to add to enable a filename that gives me "trackname-artistname?"
  9. deleted APPdata for Observium, started... It took about 10 mins, then I could log in. Not sure what happened on the first install which then you mentioned I needed to delete appdata and start up that seemed to fix it as I got to the Observium dashboard. Thanks.
  10. installed , tried login with 'observium' name and Pswd, not being recognised. Waited 10 mins still not working. restarted app waited another 5 mins still won't accept login credentials.
  11. Updated and all seems good. Like the Update OS page, that's a good move.
  12. Well, after installing to 6.4.0.rc4 and tested my original VM it was still working. I then tried a fresh install going through the creation and install process and updating the Video driver with qxldod which WORKED!! So, not sure exactly what the issue was, either a dodgy Windows image as I was using one from march but getting a new download gave me an image with a date of 27th April 2017, or something else... Suffice to say, everything is working as it should for me as far as I can tell under 6.4.0rc4 edition. Any further issues, I will report back. Thanks for the help with this.
  13. Thanks for the comments jonp and Gridrunner. So I ended up doing this.., 1. Fresh install of unraid 6.3.5 booted up, added my drives and let the parity check run to completion so all data was verified2. After parity check completed, stopped array, deleted all flash files on usb and copied backup of 6.3.5 (with all my data/users/plugins etc) 3. Downloaded Windows 10 creators edition (april 2017edition) via microsofts "media creaton tool". 4. Downloaded fresh virtio 1.26.2 from with VM settings option in unraid 5. New windows 10 vm creation option, only changing size to 50G, and keyboard to UK. 6. Kicked off new windows 10 install and choosing the qxldod driver IT WORKED!!!!. So... I am not at a bit of a junction point... do I now upgrade to the latest rc edition and try from step 5 and see how I go I think I will so... I'll do that in the next hour of so and feedback
  14. ok, it was currently set to 8gb, I halved it to 4gb left the ram bits all at 131072 - issue persists then tried all ram bits at 65536 - issue persists