greg_gorrell

All is up and running aside from the fact my docker templates are missing. Anyone know where they are stored on the flash drive?

Thanks guys, I would love to contribute to this wiki but I think the organization is flawed. We need some kind of hierarchy for placing all these pages.. I have had a couple users of the forum recommend not even using the wiki and to just seek out the information in the forums. Back to the issue, along the lines of bzimage and bzroot, how am I still having issues after downgrading again? All I did was replace these two files, just as instructed in the wiki. I have no ssh access (root access denied), plex is still eating up all the RAM, and I come home today and the CPU was clocked out and ram full. It was unresponsive so I had to pull the plug. From my understanding, by replacing these two files, I should have gotten rid of all the issues that arose from the initial upgrade. What am I missing? Technically I am starting fresh already, correct?

All I need to keep is that key file then? Plugins can be reinstalled, dockers will be on cache drive, and I can add my existing vdisks. I'm so disappointed my whole server is wrecked from this update

Does anyone know know what the easiest way would be to wipe my server and start fresh. After the 6.2 upgrade, then downgrade, my server is all buggy and I can't get more than 24 hours uptime. If i wipe the flash drive, what files do I need to copy for the key? I understand I bzroot and bzimage are the two files that load into RAM, which I copied back to the flash drive from the 6.1.9 zip to downgrade, but my dockers still aren't working as they were prior to the upgrade. Are there files that I want to keep for the license, or do I just put in my code I receive from e-mail when I boot the server for the first time?

I think it is only some AMD CPU's that have problems. Mine (an A4-4300 APU) is working fine. You are correct, it seems to be the FX line.

Not to hijack the thread but I want to install Windows Home Server as well. I found a thread on here on time comparing the versions but I can't find it now. Why are you choosing WHS 2011? Which is the best version, I think I read that WHS 2012 was worse, or that Microsoft pulled some of the features. Sent from my SM-N910V using Tapatalk

The hyperthreading issue is the same thing. If you have other VMs, specifically Linux (Ubuntu), you'll notice that error in the log for that VM. It seems to only affect the Windows VMs though. Sent from my SM-N910V using Tapatalk

Well for starters you should be posting your diagnostics and at the very least your system configuration. But if you have an AMD CPU, I'd advise that you downgrade. Search the forums and you'll notice a lot of us are having issues, I started a bug report thread. If you have an Intel CPU then we will just have to check out your diagnostics if you would post them. Sent from my SM-N910V using Tapatalk

I do, and run plex from chrome on my laptop which is always on the coffee table. Works wonderfully.

Did anyone figure this out? I am having the same issue with rc4. 2016-09-15 01:15:20.620+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 'Windows 7' -S -machine pc-i440fx-2.5,accel=kvm,usb=off,mem-merge=off -cpu host -m 2048 -realtime mlock=off -smp 1,sockets=1,cores=1,threads=1 -uuid ee79459c-c582-a638-7830-dabe9c563f8f -no-user-config -nodefaults -chardev 'socket,id=charmonitor,path=/var/lib/libvirt/qemu/domain-Windows 7/monitor.sock,server,nowait' -mon chardev=charmonitor,id=monitor,mode=control -rtc base=localtime,driftfix=slew -global kvm-pit.lost_tick_policy=discard -no-hpet -no-shutdown -boot strict=on -device ich9-usb-ehci1,id=usb,bus=pci.0,addr=0x7.0x7 -device ich9-usb-uhci1,masterbus=usb.0,firstport=0,bus=pci.0,multifunction=on,addr=0x7 -device ich9-usb-uhci2,masterbus=usb.0,firstport=2,bus=pci.0,addr=0x7.0x1 -device ich9-usb-uhci3,masterbus=usb.0,firstport=4,bus=pci.0,addr=0x7.0x2 -device virtio-serial-pci,id=virtio-serial0,bus=pci.0,addr=0x4 -drive 'file=/mnt/user/VM/Windows 7/vdisk1.img,format=r-vga,id=video0,ram_size=67108864,vram_size=67108864,vgamem_mb=16,bus=pci.0,addr=0x2 -device virtio-balloon-pci,id=balloon0,bus=pci.0,addr=0x6 -msg timestamp=on Domain id=5 is tainted: high-privileges Domain id=5 is tainted: host-cpu char device redirected to /dev/pts/2 (label charserial0) warning: host doesn't support requested feature: CPUID.80000001H:EDX [bit 0] warning: host doesn't support requested feature: CPUID.80000001H:EDX [bit 1] warning: host doesn't support requested feature: CPUID.80000001H:EDX [bit 2] warning: host doesn't support requested feature: CPUID.80000001H:EDX [bit 3] warning: host doesn't support requested feature: CPUID.80000001H:EDX [bit 4] warning: host doesn't support requested feature: CPUID.80000001H:EDX [bit 5] warning: host doesn't support requested feature: CPUID.80000001H:EDX [bit 6] warning: host doesn't support requested feature: CPUID.80000001H:EDX [bit 7] warning: host doesn't support requested feature: CPUID.80000001H:EDX [bit 8] warning: host doesn't support requested feature: CPUID.80000001H:EDX [bit 9] warning: host doesn't support requested feature: CPUID.80000001H:EDX [bit 12] warning: host doesn't support requested feature: CPUID.80000001H:EDX [bit 13] warning: host doesn't support requested feature: CPUID.80000001H:EDX [bit 14] warning: host doesn't support requested feature: CPUID.80000001H:EDX [bit 15] warning: host doesn't support requested feature: CPUID.80000001H:EDX [bit 16] warning: host doesn't support requested feature: CPUID.80000001H:EDX [bit 17] warning: host doesn't support requested feature: CPUID.80000001H:EDX [bit 23] warning: host doesn't support requested feature: CPUID.80000001H:EDX [bit 24] 2016-09-15T01:15:27.605955Z qemu-system-x86_64: terminating on signal 15 from pid 5794 2016-09-15 01:15:27.806+0000: shutting down I also saw something about hyperthreading not being supported

Nobody can answer this or have any clue what I can do? All VM's are returning the same errors depending on what machine I choose in the VM settings. Q35-2.5: i44fx: After I reboot the unRAID server, these VMs will stay running for a period of time then crash. Any attempts to reboot them return the errors until it is rebooted again. This is getting so frustrating as I use the Ubuntu server for network functions. A failed hard disk shouldn't be causing me so many issues like this. I will also note I have a PFSense VM (FreeBSD) that is running in shell mode and that seems to be staying up without any issues, although it is not set up inside the VM or anything. I only installed the OS and went no further. Please, I would appreciate any advice to go on. Edit- looks like I am running out of memory according to the logs but I have no idea why. I am trying to run all the same plugins, dockers, and VMs as I was before I updated to 6.2 and had this disk failure, actually less because I dont have everything installed yet. Edit 2- It appears Plex is the issue. It is slowly taking up more and more memory until the system runs out. That is a separate issue but why is my CPU all of a sudden not allowing me to install a Windows 7 VM? qemu-system-x86_64: AMD CPU doesn't support hyperthreading. Please configure -smp options properly. tower-diagnostics-20160914-2043.zip

You can, go into the share settings and select cache only. Sent from my SM-N910V using Tapatalk

Are the vdisk images still located on the array where you had them before the upgrade? Sent from my SM-N910V using Tapatalk

Hey guys, I had some issues with a disk failure last week so I replaced the disks with new ones and copies what VM images I could over to them. The OpenELEC and Ubuntu Server copied fine and will start on a clean boot of the unRAID server. The problem is for some reason I keep getting errors regarding connecting to monitor. Here is an example of one while I am trying to create a new Windows VM: VM creation error internal error: process exited while connecting to monitor: warning: host doesn't support requested feature: CPUID.80000001H:EDX [bit 0] warning: host doesn't support requested feature: CPUID.80000001H:EDX [bit 1] warning: host doesn't support requested feature: CPUID.80000001H:EDX [bit 2] warning: host doesn't support requested feature: CPUID.80000001H:EDX [bit 3] warning: host doesn't support requested feature: CPUID.80000001H:EDX [bit 4] warning: host doesn't support requested feature: CPUID.80000001H:EDX [bit 5] warning: host doesn't support requested feature: CPUID.80000001H:EDX [bit 6] warning: host doesn't support requested feature: CPUID.80000001H:EDX [bit 7] warning: host doesn't support requested feature: CPUID.80000001H:EDX [bit 8] warning: host doesn't support requested feature: CPUID.80000001H:EDX [bit 9] warning: host doesn't support requested feature: CPUID.80000001H:EDX [bit 12] warning: host doesn't support requested feature: CPUID.80000001H:EDX [bit 13] warning: host doesn't support requested feature: CPU This is happening with graphics passthrough, and also even just using the VNC. Does anyone know what is causing this? It will work fine for a short period of time after a reboot but eventually causes none of my VMs to start or install.

Thanks for adding this in here trurl. I know when I set up unraid initially I went through the user manual for version 6. Maybe until something is figured out, we could add something in there. I guess it's more or less about getting the importance of using the notifications out there. Sent from my SM-N910V using Tapatalk

Flixx, you will have some problems recovering the data if your parity is invalid. Make sure you pull the bad drives and only power them up if you need to pull data. The normal copy command will not work with drives that have bad sectors. I found that the "dd" command with the conv=noerror will give you the best chances of recovering your data. Apparently FAT32 is the only file system that can remap bad sectors on a disk. fsck will only label them as bad, so if you have large files written across these bad blocks/sectors, they will be unable to be read or restored. Just some things I learned the past week when this happened to me.

I think this should come set up as the default. I have mine set up now, but it's one of those "learned the hard way" lessons.

All you really should have to do is remove the second cache drive, then go into the disk settings for your first cache disk and change the filesystem from brtfs back to xfs or whatever it was initially. No data would have been modified or removed.

Squid, yes I did a clean shut down and I turn off auto load. All of the other files/VMs have copied aside from this. Im guessing my VM img is written across some of these bad sectors on the drive. Is there a way to have unRAID ignore the bad sectors while copying, or perhaps another tool I can use that will ignore them? So far I have come across a utility called dd that may do what I am looking for. http://aeroquartet.com/wordpress/2012/06/06/how-to-copy-a-file-with-io-errors/ Ever have experience with this?

Everything is backed up fine from the cache drive except for the Windows VM img, which is the most critical file. root@Tower:/mnt# cp -r -v cache/VM/"Windows 7 Pro"/ /mnt/disk1/Backup/ 'cache/VM/Windows 7 Pro/' -> '/mnt/disk1/Backup/Windows 7 Pro' 'cache/VM/Windows 7 Pro/Windows ' -> '/mnt/disk1/Backup/Windows 7 Pro/Windows ' 'cache/VM/Windows 7 Pro/Windows /vdisk1.img' -> '/mnt/disk1/Backup/Windows 7 Pro/Windows /vdisk1.img' cp: error reading 'cache/VM/Windows 7 Pro/Windows /vdisk1.img': Input/output error root@Tower:/mnt# cp -r -v cache/VM/"Windows 7 Pro"/ /mnt/disk1/Backup/ 'cache/VM/Windows 7 Pro/Windows /vdisk1.img' -> '/mnt/disk1/Backup/Windows 7 Pro/Windows /vdisk1.img' cp: error reading 'cache/VM/Windows 7 Pro/Windows /vdisk1.img': Input/output error Does anyone have an ideas on how I can get this Windows image off of this failing disk? Should I just back up from inside the VM and then reinstall Windows on the new cache drive, then restore said backup?

Thanks trurl! tail -f --lines=100 /var/log/syslog >/boot/syslogtail.txt I must have skimmed right over that link, my apologies. Its moot at this point as I have fixed the issue but I will add it to my notes in case the filesystem gets corrupt as I start trying to salvage my VM images again.

So xfs repair is like the chkdisk for FAT systems? I am running the tail -f /var/log/syslog command from the console but when I pull the flash to veiw the log on my computer, the log is from yesterday and not capturing the most recent events. I was reading the tips on this post http://lime-technology.com/forum/index.php?topic=39257 and it doesn't mention any other steps to save the syslog.txt to the flash. Shouldn't there be something else in the syntax specifying that the log needs saved to the flash drive?

Well my dockers are already gone; the only two I cared about were Plex and OpenVPN anyways. OPlex doesnt take much to setup and I hear OpenVPN-AS plugin is way better than the docker verison so that leaves my two VM's to salvage. My main concern is WIndows, which is a 50GB image. And ideas on how I can mount this and salvage that file or is it beyond the capabilities of unRAID?

Johnnie, I have disk1 and cache that are both xfs. I can get the array up in maintenance mode so I will run xfs repair again and turn on tailing before starting the array up to get a better log. I spend a better part of the night trying to back up my vm's from the failing cache drive and it kept crashing. Maybe that drive is the culprit, I just need that windows vm img off there.

Now I can't even mount my array without the whole server crashing. This is the log I get on the TV hooked up to unRAID.