cyberstyx

Members
  • Content Count

    30
  • Joined

  • Last visited

Community Reputation

3 Neutral

About cyberstyx

  • Rank
    Newbie

Converted

  • Gender
    Undisclosed

Recent Profile Visitors

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

  1. Solved it today. Did some more searching around, trying to use virtfs etc to get some more data about what is happening. Didn't progress so much with that, buy while reading about different solutions to this type of problem, I found out that having your free disk space reduced below a certain point could create issues with VMs running that would instantly pause them without any appropriate messages whatsoever. It seemed a bit strange as my VMs have all their disk size (40GB each) pre-allocated, but the problem is with the amount of free space the system uses
  2. I don't think it 's the actual VM due to its behavior, which seems to me OS-irrelevant. It seems like it's either a VM configuration option (even though I didn't touch anything and it first happened when the VM was on and iddle for many days) or something going on with KVM. I hope an expert user will have some time to check the logs or suggest something...
  3. I tried to access my Win Server 2012 VM (through Web VNC). When I logged in and as Desktop appeared and started loading, this VM also got paused as well and could not resume it. I tried to stop the array to do a system reboot, the Web GUI got in an infinite "Unmounting shares... Trying to unmount shares" loop. SSHed to the system, tried to powerdown, the command would not complete. Had to do a shutdown -r now. After the restart, Win Server 2012 got up again (was on a auto-power-up mode), Win10 was paused again. Shares, docker, WinServer2012 MySQL connections etc, everyt
  4. ashman70, so what did you eventually do? Created a new Win10 VM? A different OS VM?
  5. Here are the diagnostics tower-diagnostics-20170303-0109.zip
  6. Hello all, Returned today from work to find out my Windows 10 VM is inaccessible. Turns out it is "paused", but even resuming it from the Web GUI does nothing. I did a Forced Stop and restarted it, it reached the Windows loading screen and then got paused again - same behavior as above. The log from the VM tab is not helping me: 2017-02-22 17:26:33.687+0000: starting up libvirt version: 1.3.1, qemu version: 2.5.1, hostname: Tower LC_ALL=C PATH=/bin:/sbin:/usr/bin:/usr/sbin HOME=/ QEMU_AUDIO_DRV=none /usr/local/sbin/qemu -name Apps -S -machine pc-i440fx-2
  7. The fact that the drive had 6 and is slow on the post-read may mean it's starting to fail. Zeroing it *may* have fixed those 6, but if the drive is going bad, there may be more now. You can let it complete or stop it, but I would do at least one more Preclear on it, preferably 2 more. You want perfect Preclears, running at normal speed, before you can trust it. From the web GUI I checked Tools > Preclear > Log option, and the pop-up window gets regularly spammed with these Nov 8 18:45:54 Tower kernel: ata17.00: exception Emask 0x0 SAct 0x1000000 SErr 0x0 action 0x0 No
  8. Hey all, I have added an older 2TB disk for PreClearing (2016.09.26b), and although it started at nice speeds now at step 5 it's really crawling - 61 hours at current step ############################################################################################################################ # # # unRAID Server Pre-Clear of disk /dev/sdg # #
  9. After around 7 hours of operation and continued disk accessing on it due to various operations working in the background, everything is working as should after the repair. Thank you a lot johnnie.black
  10. Running xfs_repair -L /dev/md4 returned this Phase 1 - find and verify superblock... Phase 2 - using internal log - zero log... ALERT: The filesystem has valuable metadata changes in a log which is being destroyed because the -L option was used. - scan filesystem freespace and inode maps... Metadata corruption detected at xfs_agf block 0x1/0x200 flfirst 118 in agf 0 too large (max = 118) sb_icount 6656, counted 6912 sb_fdblocks 75816018, counted 73851558 - found root inode chunk Phase 3 - for each AG... - scan and clear agi unlinked lists... - pr
  11. Returned home today and found out that many files were missing from a share (many disks store files in that share). In MC disk4 appeared as a red "?disk4" and could not be accessed. The main screen had all disks as active (green dot). I did not restart the server, just did a Array stop-start. The files re-appeared in the share and disk4 was accessible through MC. After some minutes that I checked back, the issue had re-appeared, files were missing and disk4 could not be accessed The attached Syslog "xfs error md4.zip" shows some issues with the file system of the disk. I fo
  12. Yes I have the anniversary edition now. I could not revert back to any previous version even if I could as the VM was not working (could not get into safe mode and booting from Window's ISO and trying any possible option in troubleshooting was not working). Yes, I had one VCPU for that during all my tries. It 's also in the official manual when upgrading a host with Win10. The only setting that seemed to matter, at least in my situation, was to change the USB mode from 3.0 back to 2.0.
  13. I troubleshooted this and found the solution, so I 'm writing this down in case someone finds it useful. After upgrading from 6.1.7 to 6.2 I also edited the VM configuration and changed the VNC GFX but also the USB Mode from 2.0 EHCI to 3.0 XHCI. The VM functioned properly until it auto-updated itself to the Anniversary edition. At this point after restarting it stopped at 35% and completely hanged, while the CPU shows a continues 100% activity. I changed the CPU to another non-used one for troubleshooting, it stayed again at 100% while Windows Update stayed at Getting Things Re
  14. Everything worked like a charm. Upgrading was faster than upgrading your typical Windows application Only one thing I had to edit: the OVMF locations of my VMs in their XML files, which had been edited manually by me in the first place (trick for multiple OVMF VMs prior to 6.2). Thanks for your help!
  15. Hello all, Had a look about upgrading from an already 6.x version to 6.2 but there is no info. There is a analytical guide from v5 to v6 but there is so much not needed information there. One comment I saw was the obvious "click the update button from the Tower/Plugins menu", but as I am not a Linux user and as I have a few posts that had some issues after an upgrade from 6.x to 6.2, such as dockers, shares, issues with booting, I 'd rather first ask the obvious. Apart from copying the USB system files from the USB drive to my local PC for backup purposes, and before running the