Jump to content

Lake-end

Members
  • Content Count

    19
  • Joined

  • Last visited

Community Reputation

0 Neutral

About Lake-end

  • Rank
    Member

Converted

  • Gender
    Undisclosed

Recent Profile Visitors

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

  1. Yeah I´ve just noticed the unraid bootmenu has this by default (I dont really boot this machine often). Seems that one of my RAM sticks has broken, so there we go.
  2. Would appreciate any pointers if available. More info: I am gettin the above freeze also when I SCP a 4gb ISO file to Array from my laptop. So it seems that either writing to the HDD array is hosed somehow or I might have RAM thats gone bad?
  3. Hello, I´ve been using this unraid setup for few years now but I am now facing problem I need some outside help with. I was trying to download my VM image file from my SSD cache drive (where I run all my VMs) to backup storage on my regulard HDD array. I am loggin on the Unraid via SSH and tried few things just regular cp, rsync etc operations to move this 100gb image file. I am getting consistent system crash trying to do this operation and from outside it looked like system just froze. When I had tail syslog running on second SSH window while doing this I could actually see the error happening. Problem is I dont understand what is happening. (log attached below) I´ve searched around for solution and so far ran the xfs repair for the Array drive and scrubbing for the SSD cache pool. Also I ran SMART tests for drives involved and they showed green and this doesnt "feel" like failing drive to me. One further issue I now understand might be related is following that started happening last week: I run unraid as my daily gaming/work computer by running a Windows 10 VM on it and using it for pretty much all my computing needs. Last week I noticed my VM started straight out crashing without any message (like someone switched of power from the VM) whenever Steam was trying to download large updates for games. This is also 100% reproducable, I need to pause all downloads in Steam or Ill get a crash. My VMs run on SSD cache pool. Anyone have any clues on what could be happening? Also I realize I am not running latest version and I am not asking for any fixes to be made to old version, just some support on figuring what is wrong in my system that used to run stable. Cheers! May 19 14:47:44 Megathron dnsmasq-dhcp[5182]: DHCP, sockets bound exclusively to interface virbr0 May 19 14:47:44 Megathron dnsmasq[5182]: reading /etc/resolv.conf May 19 14:47:44 Megathron dnsmasq[5182]: using nameserver 8.8.8.8#53 May 19 14:47:44 Megathron dnsmasq[5182]: using nameserver 8.8.4.4#53 May 19 14:47:44 Megathron dnsmasq[5182]: using nameserver 192.168.0.1#53 May 19 14:47:44 Megathron dnsmasq[5182]: read /etc/hosts - 2 addresses May 19 14:47:44 Megathron dnsmasq[5182]: read /var/lib/libvirt/dnsmasq/default.addnhosts - 0 addresses May 19 14:47:44 Megathron dnsmasq-dhcp[5182]: read /var/lib/libvirt/dnsmasq/default.hostsfile May 19 14:47:44 Megathron kernel: virbr0: port 1(virbr0-nic) entered disabled state May 19 14:47:46 Megathron sshd[4792]: Accepted password for root from 192.168.0.210 port 51339 ssh2 May 19 14:48:02 Megathron sshd[5327]: Accepted password for root from 192.168.0.210 port 51374 ssh2 May 19 14:48:45 Megathron kernel: general protection fault: 0000 [#1] PREEMPT SMP May 19 14:48:45 Megathron kernel: Modules linked in: xt_CHECKSUM iptable_mangle ipt_REJECT nf_reject_ipv4 ebtable_filter ebtables vhost_net tun vhost macvtap macvlan ipt_MASQUERADE nf_nat_masquerade_ipv4 iptable_nat nf_conntrack_ipv4 nf_nat_ipv4 iptable_filter ip_tables nf_nat md_mod x86_pkg_temp_thermal coretemp e1000e mxm_wmi i2c_i801 ptp i2c_smbus i2c_core pps_core kvm_intel ahci libahci kvm video wmi backlight [last unloaded: md_mod] May 19 14:48:45 Megathron kernel: CPU: 1 PID: 335 Comm: kworker/1:1 Not tainted 4.9.30-unRAID #1 May 19 14:48:45 Megathron kernel: Hardware name: System manufacturer System Product Name/MAXIMUS VIII GENE, BIOS 2202 09/19/2016 May 19 14:48:45 Megathron kernel: Workqueue: xfs-data/md1 xfs_end_io May 19 14:48:45 Megathron kernel: task: ffff88085a199a80 task.stack: ffffc90003920000 May 19 14:48:45 Megathron kernel: RIP: 0010:[<ffffffff8107dd9f>] [<ffffffff8107dd9f>] native_queued_spin_lock_slowpath+0x12d/0x17e May 19 14:48:45 Megathron kernel: RSP: 0018:ffffc90003923d60 EFLAGS: 00010282 May 19 14:48:45 Megathron kernel: RAX: 0000000000000775 RBX: ffff8807798bdaf8 RCX: ff79afd600018686 May 19 14:48:45 Megathron kernel: RDX: ffff88087ec58600 RSI: 0000000000080000 RDI: ffff8807798bdb70 May 19 14:48:45 Megathron kernel: RBP: ffffc90003923d60 R08: 0000000000000001 R09: ffff88087eff8000 May 19 14:48:45 Megathron kernel: R10: ffff8807798bdaf8 R11: ffffffffffffffe5 R12: 0000000000000001 May 19 14:48:45 Megathron kernel: R13: 0000000000000000 R14: 00000000000000dc R15: ffff88082dd13dc0 May 19 14:48:45 Megathron kernel: FS: 0000000000000000(0000) GS:ffff88087ec40000(0000) knlGS:0000000000000000 May 19 14:48:45 Megathron kernel: CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033 May 19 14:48:45 Megathron kernel: CR2: 00002b9ee126b570 CR3: 0000000001c09000 CR4: 00000000003406e0 May 19 14:48:45 Megathron kernel: DR0: 0000000000000000 DR1: 0000000000000000 DR2: 0000000000000000 May 19 14:48:45 Megathron kernel: DR3: 0000000000000000 DR6: 00000000fffe0ff0 DR7: 0000000000000400 May 19 14:48:45 Megathron kernel: Stack: May 19 14:48:45 Megathron kernel: ffffc90003923d70 ffffffff8167f0c0 ffffc90003923d90 ffffffff811490fd May 19 14:48:45 Megathron kernel: ffff88082dcaa700 ffff88082dcaac00 ffffc90003923df0 ffffffff81295df7 May 19 14:48:45 Megathron kernel: 00000000812b2f4b ffff8807798bdaf8 ffff8807798bdaf8 00000fff00001000 May 19 14:48:45 Megathron kernel: Call Trace: May 19 14:48:45 Megathron kernel: [<ffffffff8167f0c0>] _raw_spin_lock+0x21/0x25 May 19 14:48:45 Megathron kernel: [<ffffffff811490fd>] attach_nobh_buffers+0x32/0x92 May 19 14:48:45 Megathron kernel: [<ffffffff81295df7>] xfs_destroy_ioend+0xac/0xe2 May 19 14:48:45 Megathron kernel: [<ffffffff81295ebf>] xfs_end_io+0x92/0x99 May 19 14:48:45 Megathron kernel: [<ffffffff8105ed53>] process_one_work+0x192/0x295 May 19 14:48:45 Megathron kernel: [<ffffffff8105f752>] worker_thread+0x27d/0x369 May 19 14:48:45 Megathron kernel: [<ffffffff8105f4d5>] ? rescuer_thread+0x2b1/0x2b1 May 19 14:48:45 Megathron kernel: [<ffffffff81063939>] kthread+0xdb/0xe3 May 19 14:48:45 Megathron kernel: [<ffffffff8110c273>] ? kfree+0xdf/0xfa May 19 14:48:45 Megathron kernel: [<ffffffff8106385e>] ? kthread_park+0x52/0x52 May 19 14:48:45 Megathron kernel: [<ffffffff8105c16c>] ? umh_complete+0x20/0x20 May 19 14:48:45 Megathron kernel: [<ffffffff8105c28b>] ? call_usermodehelper_exec_async+0x11f/0x128 May 19 14:48:45 Megathron kernel: [<ffffffff8167f785>] ret_from_fork+0x25/0x30 May 19 14:48:45 Megathron kernel: Code: e8 10 66 87 47 02 c1 e0 10 74 6b 48 89 c1 c1 e8 12 48 c1 e9 0c ff c8 83 e1 30 48 98 48 81 c1 00 86 01 00 48 03 0c c5 60 62 9b 81 <48> 89 11 8b 42 08 85 c0 75 04 f3 90 eb f5 48 8b 0a 48 85 c9 74 May 19 14:48:45 Megathron kernel: RIP [<ffffffff8107dd9f>] native_queued_spin_lock_slowpath+0x12d/0x17e May 19 14:48:45 Megathron kernel: RSP <ffffc90003923d60> May 19 14:48:45 Megathron kernel: ---[ end trace 8c1a697b0d7af270 ]--- May 19 14:48:45 Megathron kernel: note: kworker/1:1[335] exited with preempt_count 1 May 19 14:48:45 Megathron kernel: BUG: unable to handle kernel paging request at ffffffffffffffd8 May 19 14:48:45 Megathron kernel: IP: [<ffffffff81064153>] kthread_data+0xc/0x11 May 19 14:48:45 Megathron kernel: PGD 1c0c067 May 19 14:48:45 Megathron kernel: PUD 1c0e067 May 19 14:48:45 Megathron kernel: PMD 0 May 19 14:48:45 Megathron kernel: May 19 14:48:45 Megathron kernel: Oops: 0000 [#2] PREEMPT SMP May 19 14:48:45 Megathron kernel: Modules linked in: xt_CHECKSUM iptable_mangle ipt_REJECT nf_reject_ipv4 ebtable_filter ebtables vhost_net tun vhost macvtap macvlan ipt_MASQUERADE nf_nat_masquerade_ipv4 iptable_nat nf_conntrack_ipv4 nf_nat_ipv4 iptable_filter ip_tables nf_nat md_mod x86_pkg_temp_thermal coretemp e1000e mxm_wmi i2c_i801 ptp i2c_smbus i2c_core pps_core kvm_intel ahci libahci kvm video wmi backlight [last unloaded: md_mod] May 19 14:48:45 Megathron kernel: CPU: 1 PID: 335 Comm: kworker/1:1 Tainted: G D 4.9.30-unRAID #1 May 19 14:48:45 Megathron kernel: Hardware name: System manufacturer System Product Name/MAXIMUS VIII GENE, BIOS 2202 09/19/2016 May 19 14:48:45 Megathron kernel: task: ffff88085a199a80 task.stack: ffffc90003920000 May 19 14:48:45 Megathron kernel: RIP: 0010:[<ffffffff81064153>] [<ffffffff81064153>] kthread_data+0xc/0x11 May 19 14:48:45 Megathron kernel: RSP: 0018:ffffc90003923e80 EFLAGS: 00010002 May 19 14:48:45 Megathron kernel: RAX: 0000000000000000 RBX: ffff88085a199a80 RCX: 0000000000000001 May 19 14:48:45 Megathron kernel: RDX: ffff88085a199a80 RSI: ffff88085a199b00 RDI: ffff88085a199a80 May 19 14:48:45 Megathron kernel: RBP: ffffc90003923e88 R08: 0000000000000113 R09: 0000000000044c00 megathron-diagnostics-20190519-1838.zip
  4. Didnt find answer to this with search, might be im bad @searching tho. With S3 Sleep plugin, what kind of before and after sleep commands should I use to make it play nicely together with my Windows VM? Any examples how you guys handle this tidily? I would like the system to suspend or shutdown a certain VM before system sleeping because after sleep the VM is not working anymore(at least there is no picture in displays via passthrough gfx card). After resuming from sleep I would like to start/restore that VM automatically. So far I´ve tried "virsh suspend Hyperion" and "virsh resume Hyperion", these work alright from command line in normal operation. But if I put unraid to S3 Sleep between the commands I dont get picture on my displays anymore, according the top command qemu is running wild with CPU so the VM is running alright but just not showing picture on my displays. Is there some command i could run after S3 Sleep that would reininitialize the gfx card or dispalys etc? Or should I be using Save/Restore instead?
  5. Did anyone figure this one out? I updated and am having the same problem. If there is no workaround, how do I rollback to working version again? ErrorWarningSystemArrayLogin 2017-03-19 16:31:39.625+0000: starting up libvirt version: 2.4.0, qemu version: 2.7.1, hostname: Megathron LC_ALL=C PATH=/bin:/sbin:/usr/bin:/usr/sbin HOME=/ QEMU_AUDIO_DRV=none /usr/local/sbin/qemu -name guest=Hyperion,debug-threads=on -S -object secret,id=masterKey0,format=raw,file=/var/lib/libvirt/qemu/domain-1-Hyperion/master-key.aes -machine pc-i440fx-2.5,accel=kvm,usb=off,dump-guest-core=off,mem-merge=off -cpu host,hv_time,hv_relaxed,hv_vapic,hv_spinlocks=0x1fff,hv_vendor_id=none -m 24576 -realtime mlock=off -smp 6,sockets=1,cores=3,threads=2 -uuid 9366709d-341c-8d6c-8a46-49a67ce382bd -display none -no-user-config -nodefaults -chardev socket,id=charmonitor,path=/var/lib/libvirt/qemu/domain-1-Hyperion/monitor.sock,server,nowait -mon chardev=charmonitor,id=monitor,mode=control -rtc base=localtime -no-hpet -no-shutdown -boot strict=on -device nec-usb-xhci,id=usb,bus=pci.0,addr=0x7 -device virtio-serial-pci,id=virtio-serial0,bus=pci.0,addr=0x3 -drive file=/mnt/user/VDisks/Hyperion/vdisk1.img,format=raw,if=none,id=drive-virtio-disk2,cache=writeback -device virtio-blk-pci,scsi=ofcharchannel0,id=channel0,name=org.qemu.guest_agent.0 -device vfio-pci,host=01:00.0,id=hostdev0,x-vga=on,bus=pci.0,addr=0x8 -device vfio-pci,host=01:00.1,id=hostdev1,bus=pci.0,addr=0x9 -device vfio-pci,host=02:00.0,id=hostdev2,bus=pci.0,addr=0xa -device usb-host,hostbus=1,hostaddr=2,id=hostdev3,bus=usb.0,port=1 -device usb-host,hostbus=1,hostaddr=3,id=hostdev4,bus=usb.0,port=2 -device virtio-balloon-pci,id=balloon0,bus=pci.0,addr=0xb -msg timestamp=on Domain id=1 is tainted: high-privileges Domain id=1 is tainted: host-cpu char device redirected to /dev/pts/0 (label charserial0) 2017-03-19T16:31:42.749032Z qemu-system-x86_64: -device vfio-pci,host=02:00.0,id=hostdev2,bus=pci.0,addr=0xa: Failed to mmap 0000:02:00.0 BAR 2. Performance may be slow 2017-03-19T16:31:42.806343Z qemu-system-x86_64: warning: Unknown firmware file in legacy mode: etc/msr_feature_control 2017-03-19T16:32:31.627414Z qemu-system-x86_64: terminating on signal 15 from pid 4933 2017-03-19 16:32:33.228+0000: shutting down, reason=destroyed EDIT: I figured it out! I had to disable the passthrough for my PCIE USB card. Any ideas how could I get the PCIE passhtrough working again, sucks using Windows VM without one? ie. how do I fix this: " 2017-03-19T17:00:39.411645Z qemu-system-x86_64: -device vfio-pci,host=02:00.0,id=hostdev2,bus=pci.0,addr=0xa: Failed to mmap 0000:02:00.0 BAR 2. Performance may be slow ? megathron-diagnostics-20170319-1847.zip
  6. Since my last post I havent been crashing. I went through my network assigning static IPs for everything and updated my BIOS, not sure which one cured it.
  7. Okay this is bit stupid, but since someone else might also face this later I´m gonna post last update and marking this SOLVED. I changed back to IGFX and everything works now. Somehow seems that booting succefully with PCIE (or Auto) mode fixed it and now switching back to IGFX also works. Weird but Ill take it.
  8. Okay problem now is that vms wont get gfx pass through anymore since Auto gives my nvidia card to unraid. Im pretty sure I used to be able to assign igfx as primary so unraid uses it. What am I doing wrong this time?
  9. Quick update: going from IGFX back to Auto on Primary Display seems to get me to login screen.
  10. Hey there, I´m kinda without working computer at the moment as I run my workstation as unRAID VM. So excuse me for being brief. I have Asus Maximux VIII Gene motherboard, I´ve just updated to latest BIOS from year old version. Now when after selecting unRAID from the boot menu I get to "Loading bzroot ... ok" and the system resets itself. It will keep doing the reset loop until I intervene. I think I did necessary changes in BIOS after updating, please sanity check this: -Enabled Intel Virtualization Technologies and VT-D -Set default boot gfx as IGFP -SATA is set to ACHI To troubleshoot this problem I also: -Removed the secureboot keys and set the os type as "Other OS" -Disabled Fast Boot The unRAID USB stick is untouched in its slot it was in and fuctioned before the update. Now would there be some legacy support setting for USB I should enable? I believe all USB ports on this mobo are USB3.0. I dont think BIOS upgrade would mess the unRAID installation on the USB stick would it? But might it somehow confuse the USB ID that is used by the licensing system? Any other ideas I could try? I´m willing to do pretty much anything as having no working computer at the moment is sorry state to exist in. Thanks for any ideas in advance! EDIT: I forgot to mention im on 6.2 stable, cant really send you the diagnostics log atm as I cant boot the system.
  11. Thanks will try that, at the moment I dont have another GPU to spare.
  12. How well does it work over remote desktop (VNC I guess)? Is it usable for say...video editing?
  13. Sorry for the late reply, I indeed have a Skylake, 6700k. Sorry for the late reply, I indeed have a Skylake, 6700k. You also happen to have Skylake CPU? I second this. Look at your network switch. Is it going ape-s**t? A couple possible causes are two DHCP servers issuing IPs on the same subnet or conflicting IPs. If your VMs are using dynamically assigned IPs, and you suspend them, it's possible that the IP that was on that VM is getting reassigned and when you wake the VM there is a conflict because it doesn't ask for another new IP. The next time it happens, do a 'ipconfig /release' and 'ipconfig /renew' on the VM, or just reboot it. See if that resolves the issue. If it does, stop suspending the VM and/or assign it a static IP. The VM freezes, ie locks up, totally. Also like I said earlier, unfortunately I cannot do anything on the Unraid itself. Maybe I need to have second keyboard(ps2?) on the machine and see if I can get anything done on it. Remember network dies I can not SSH in it and Windows VM has claimed the keyboard. But then again when this lockup happens, pushing power button doesnt close the system like it should, in normal situation unRAID closes nicely and system powers off, in this situtation nothing happens and I need to hold the powerbutton down for it to poweroff.
  14. Background: I have been using unRAID for few months now, I´m on Basic with couple HDDs and couple SSDs. SSDs are BTRFS with RAID0 for files and RAID1 for metadata. I run my main OS (Windows10) as VM on it as a daily driver. I also have Plex running as docker image, USB controller passthrough and coretemp plugin, that is about the extent of my "customization" from vanilla unRAID 6.1.9 My home network consists of LTE modem and ADSL modem connected to load balancing router to which my unRAID machine connects directly. unRAID is mapped with static IP. What happens: This only seems to happen when I am actively using the Win10 VM ie. I am doing something on the computer, I havent noticed this behavior ever when its sitting idle during nights etc. Windows OS will freeze, straight up lock up reacting to nothing. When I try switching my monitor input to show unRAID terminal it wont accept keyboard input nor is the "tail -f /var/log/syslog" moving, the cursor in the bottom left is still blinking tho. Since network is completely down and it wont accept keyboard input I am not actually sure if the whole unRAID has locked up, or just the VM. As I said syslog is not reacting, but the "cursor" is still blinking. EDIT: Considering pushing power button doesnt close the system like it should it seems whole computer has locked up, unRAID and all. Normally if I press power button unRAID powers off nicely. Now what is really peculiar is that when this happens, it also takes my home network down with it. I have no frigging clue how this is even possible, but indeed when my VM locks up all other devices in the network lose their internet connection. At first I was thinking that the cause must be the internet/network outage which is somehow crashing the VM, makes lot more sense, right? But no, if I reboot all my network related gear and try to get connection on other devices working, it will stay down until I disconnect unRAID computers network cable. Weird huh? I have no clue how could locked up unRAID cause the network to die, and keep it dead until I either remove the network cable or hard reset unRAID computer. You might say this has been just a coincidence, but this has happened at least 3-4 times already. I think there are two different things here, which are related but need to be solved. 1) Why is the Windows10 VM locking up? 2) Why does the VM or the unRAID manage to kill my network? For the 1) I have a slight hunch that it might be related to memory consumption. I have total of 16gb of RAM on the machine, out which 12GB is allocated to Windows10 VM and rest are free for unRAID itself. Last time this lockup happened, I was playing the new Deus Ex game, it eats fair bit of memory and when I opened my Chrome browser the lockup happened. My Chrome has like 30 open tabs, it will consume something like 6gb of RAM when fully loaded. So I have a feeling I might have run over that 12gb, but I assume Windows10 in default settings should be able to use pagefile or something so honestly I dont know why it would lockup. For the 2) I dont have any ideas, also I cant beging to understand how the unRAID box could kill my network. It seems to nuke all active devices in way that their connection gets interrupted and they wont be able to get working connection no matter if I reboot them or the network gear, only thing that seems to help is either pulling the network cable from unRAID or hard resetting it, then rebooting network gear gives me working network on all devices. If someone smarter than me could float ideas on whats causing this and how is the 2) even possible I would REALLY appreciate it. EDIT: Attached the diagnostics zip, let me know if something else would be helpful. megathron-diagnostics-20160824-2330.zip