cyberstyx

Members
  • Posts

    30
  • Joined

  • Last visited

Converted

  • Gender
    Undisclosed

Recent Profile Visitors

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

cyberstyx's Achievements

Newbie

Newbie (1/14)

3

Reputation

  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 for this operation. People had issues with those files being on Cache Disks which, when dropped below a certain point, could cause this. My problem was a bit more obvious, if you knew where to look ofc. The drive hosting the VMs, and I suspect hosting other files for this reason, dropped to the amazing 20,5KB of free space. Which was strange as I had stopped all writes on this disk at 50+GB. That nice docker I have, which is a Minecraft server for the kids, ended up eating up all available free space due to daily backups. Clearing that space and returning the disk to 50+ free GB allowed my VM to start correctly. I can't tell you how nice it is to hit F5 and have the Web GUIs running on that VM to actual no say something rude to me... I hope this situation is also helpful to someone else to, especially you ashman70 I will change the topic to solved, and I hope it stays like that
  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, everything ok, no problems in the logs, as initially mentioned. Trying to resume Win10 fails 9/10 of the tries (web GUI refreshes but the pause icon is still there). After a few tries the icon refreshes to "started", but refreshing the Web GUI with F5 shows it again as paused. When there is that very fast paused > resumed > paused again sequence, I can see from the VNC connection that the VM Win10 machines gets "one step" ahead: it shows the Windows logo, then it will show the progress bar / rotation, then it will update a bit the bar / rotation... it 's like the VM gets auto-paused, at some point it may resume for a fraction and then gets insta-paused again. As this seems to be a system issue and not a VM issue, since Win10 is auto-blocked before the OS even loads and since WinServer2012 also got behaved similarly at least once, I think there is no point in trying to make more VMs with different OSes in case the OS has an issue. For the time being I am not accessing through VNC / RDP the WinServer2012 as, at least its MySQL DB services, are working fine.
  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.5,accel=kvm,usb=off,mem-merge=off -cpu host,hv_time,hv_relaxed,hv_vapic,hv_spinlocks=0x1fff,hv_vendor_id=none -drive file=/boot/config/vm-ovmfs/OVMF-pure-efi-Apps_1.fd,if=pflash,format=raw,unit=0,readonly=on -drive file=/etc/libvirt/qemu/nvram/8ad559d1-4831-d65c-493f-4baaa9094b41_VARS-pure-efi.fd,if=pflash,format=raw,unit=1 -m 2560 -realtime mlock=off -smp 1,sockets=1,cores=1,threads=1 -uuid 8ad559d1-4831-d65c-493f-4baaa9094b41 -no-user-config -nodefaults -chardev socket,id=charmonitor,path=/var/lib/libvirt/qemu/domain-Apps/monitor.sock,server,nowait -mon chardev=charmonitor,id=monitor,mode=control -rtc base=localtime -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=pcir=0x3 -chardev pty,id=charserial0 -device isa-serial,chardev=charserial0,id=serial0 -chardev socket,id=charchannel0,path=/var/lib/libvirt/qemu/channel/target/domain-Apps/org.qemu.guest_agent.0,server,nowait -device virtserialport,bus=virtio-serial0.0,nr=1,chardev=charchannel0,id=channel0,name=org.qemu.guest_agent.0 -device usb-tablet,id=input0 -vnc 0.0.0.0:1,websocket=5701 -k en-us -device qxl-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=0x8 -msg timestamp=on Domain id=2 is tainted: high-privileges Domain id=2 is tainted: host-cpu char device redirected to /dev/pts/1 (label charserial0) ehci warning: guest updated active QH ehci warning: guest updated active QH ehci warning: guest updated active QH ehci warning: guest updated active QH ehci warning: guest updated active QH 2017-03-02T16:23:50.703615Z qemu-system-x86_64: terminating on signal 15 from pid 8085 2017-03-02 16:23:50.904+0000: shutting down 2017-03-02 16:23:54.572+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.5,accel=kvm,usb=off,mem-merge=off -cpu host,hv_time,hv_relaxed,hv_vapic,hv_spinlocks=0x1fff,hv_vendor_id=none -drive file=/boot/config/vm-ovmfs/OVMF-pure-efi-Apps_1.fd,if=pflash,format=raw,unit=0,readonly=on -drive file=/etc/libvirt/qemu/nvram/8ad559d1-4831-d65c-493f-4baaa9094b41_VARS-pure-efi.fd,if=pflash,format=raw,unit=1 -m 2560 -realtime mlock=off -smp 1,sockets=1,cores=1,threads=1 -uuid 8ad559d1-4831-d65c-493f-4baaa9094b41 -no-user-config -nodefaults -chardev socket,id=charmonitor,path=/var/lib/libvirt/qemu/domain-Apps/monitor.sock,server,nowait -mon chardev=charmonitor,id=monitor,mode=control -rtc base=localtime -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=pcir=0x3 -chardev pty,id=charserial0 -device isa-serial,chardev=charserial0,id=serial0 -chardev socket,id=charchannel0,path=/var/lib/libvirt/qemu/channel/target/domain-Apps/org.qemu.guest_agent.0,server,nowait -device virtserialport,bus=virtio-serial0.0,nr=1,chardev=charchannel0,id=channel0,name=org.qemu.guest_agent.0 -device usb-tablet,id=input0 -vnc 0.0.0.0:1,websocket=5701 -k en-us -device qxl-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=0x8 -msg timestamp=on Domain id=3 is tainted: high-privileges Domain id=3 is tainted: host-cpu char device redirected to /dev/pts/1 (label charserial0) The message "ehci warning: guest updated active QH" did not appear again after the restart. It's XML file is: <domain type='kvm' id='3'> <name>Apps</name> <uuid>8ad559d1-4831-d65c-493f-4baaa9094b41</uuid> <description>Windows Applications</description> <metadata> <vmtemplate xmlns="unraid" name="Windows 10" icon="windows.png" os="windows10"/> </metadata> <memory unit='KiB'>2621440</memory> <currentMemory unit='KiB'>2621440</currentMemory> <memoryBacking> <nosharepages/> </memoryBacking> <vcpu placement='static'>1</vcpu> <cputune> <vcpupin vcpu='0' cpuset='1'/> </cputune> <resource> <partition>/machine</partition> </resource> <os> <type arch='x86_64' machine='pc-i440fx-2.5'>hvm</type> <loader readonly='yes' type='pflash'>/boot/config/vm-ovmfs/OVMF-pure-efi-Apps_1.fd</loader> <nvram>/etc/libvirt/qemu/nvram/8ad559d1-4831-d65c-493f-4baaa9094b41_VARS-pure-efi.fd</nvram> </os> <features> <acpi/> <apic/> <hyperv> <relaxed state='on'/> <vapic state='on'/> <spinlocks state='on' retries='8191'/> <vendor id='none'/> </hyperv> </features> <cpu mode='host-passthrough'> <topology sockets='1' cores='1' threads='1'/> </cpu> <clock offset='localtime'> <timer name='hypervclock' present='yes'/> <timer name='hpet' present='no'/> </clock> <on_poweroff>destroy</on_poweroff> <on_reboot>restart</on_reboot> <on_crash>restart</on_crash> <devices> <emulator>/usr/local/sbin/qemu</emulator> <disk type='file' device='disk'> <driver name='qemu' type='raw' cache='writeback'/> <source file='/mnt/user/VMs/Apps/vdisk1.img'/> <backingStore/> <target dev='hdc' bus='virtio'/> <boot order='1'/> <alias name='virtio-disk2'/> <address type='pci' domain='0x0000' bus='0x00' slot='0x06' function='0x0'/> </disk> <disk type='file' device='cdrom'> <driver name='qemu' type='raw'/> <source file='/mnt/user/Applications/System/Microsoft Windows/Windows 10/Microsoft Windows 10 Home and Pro x64 Clean ISO/en_windows_10_multiple_editions_x64_dvd_6846432.iso'/> <backingStore/> <target dev='hda' bus='sata'/> <readonly/> <boot order='2'/> <alias name='sata0-0-0'/> <address type='drive' controller='0' bus='0' target='0' unit='0'/> </disk> <disk type='file' device='cdrom'> <driver name='qemu' type='raw'/> <source file='/mnt/user/Applications/unRAID/VIRTIO drivers/virtio-win-0.1.112.iso'/> <backingStore/> <target dev='hdb' bus='sata'/> <readonly/> <alias name='sata0-0-1'/> <address type='drive' controller='0' bus='0' target='0' unit='1'/> </disk> <controller type='usb' index='0' model='ich9-ehci1'> <alias name='usb'/> <address type='pci' domain='0x0000' bus='0x00' slot='0x07' function='0x7'/> </controller> <controller type='usb' index='0' model='ich9-uhci1'> <alias name='usb'/> <master startport='0'/> <address type='pci' domain='0x0000' bus='0x00' slot='0x07' function='0x0' multifunction='on'/> </controller> <controller type='usb' index='0' model='ich9-uhci2'> <alias name='usb'/> <master startport='2'/> <address type='pci' domain='0x0000' bus='0x00' slot='0x07' function='0x1'/> </controller> <controller type='usb' index='0' model='ich9-uhci3'> <alias name='usb'/> <master startport='4'/> <address type='pci' domain='0x0000' bus='0x00' slot='0x07' function='0x2'/> </controller> <controller type='pci' index='0' model='pci-root'> <alias name='pci.0'/> </controller> <controller type='sata' index='0'> <alias name='sata0'/> <address type='pci' domain='0x0000' bus='0x00' slot='0x04' function='0x0'/> </controller> <controller type='virtio-serial' index='0'> <alias name='virtio-serial0'/> <address type='pci' domain='0x0000' bus='0x00' slot='0x05' function='0x0'/> </controller> <interface type='bridge'> <mac address='52:54:00:72:8d:a8'/> <source bridge='br0'/> <target dev='vnet1'/> <model type='virtio'/> <alias name='net0'/> <address type='pci' domain='0x0000' bus='0x00' slot='0x03' function='0x0'/> </interface> <serial type='pty'> <source path='/dev/pts/1'/> <target port='0'/> <alias name='serial0'/> </serial> <console type='pty' tty='/dev/pts/1'> <source path='/dev/pts/1'/> <target type='serial' port='0'/> <alias name='serial0'/> </console> <channel type='unix'> <source mode='bind' path='/var/lib/libvirt/qemu/channel/target/domain-Apps/org.qemu.guest_agent.0'/> <target type='virtio' name='org.qemu.guest_agent.0' state='disconnected'/> <alias name='channel0'/> <address type='virtio-serial' controller='0' bus='0' port='1'/> </channel> <input type='tablet' bus='usb'> <alias name='input0'/> </input> <input type='mouse' bus='ps2'/> <input type='keyboard' bus='ps2'/> <graphics type='vnc' port='5901' autoport='yes' websocket='5701' listen='0.0.0.0' keymap='en-us'> <listen type='address' address='0.0.0.0'/> </graphics> <video> <model type='qxl' ram='65536' vram='65536' vgamem='16384' heads='1'/> <alias name='video0'/> <address type='pci' domain='0x0000' bus='0x00' slot='0x02' function='0x0'/> </video> <memballoon model='virtio'> <alias name='balloon0'/> <address type='pci' domain='0x0000' bus='0x00' slot='0x08' function='0x0'/> </memballoon> </devices> </domain> I have a Windows Server 2012 running fine at the same time. Access to the host / server, file sharing, an existing docker, are all running fine. The host (6.2) was restarted a week ago ago due to its relocation to a different room. I didn't fine something relevant by searching the forum. Any thoughts would be appreciated! Kind regards, Christos.
  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 Nov 8 18:45:54 Tower kernel: ata17.00: irq_stat 0x40000008 Nov 8 18:45:54 Tower kernel: ata17.00: failed command: READ FPDMA QUEUED Nov 8 18:45:54 Tower kernel: ata17.00: cmd 60/08:c0:70:00:44/00:00:7c:00:00/40 tag 24 ncq 4096 in Nov 8 18:45:54 Tower kernel: res 41/40:00:70:00:44/00:00:7c:00:00/40 Emask 0x409 (media error) <F> Nov 8 18:45:54 Tower kernel: ata17.00: status: { DRDY ERR } Nov 8 18:45:54 Tower kernel: ata17.00: error: { UNC } Nov 8 18:45:54 Tower kernel: ata17.00: configured for UDMA/133 Nov 8 18:45:54 Tower kernel: sd 17:0:0:0: [sdg] tag#24 UNKNOWN(0x2003) Result: hostbyte=0x00 driverbyte=0x08 Nov 8 18:45:54 Tower kernel: sd 17:0:0:0: [sdg] tag#24 Sense Key : 0x3 [current] [descriptor] Nov 8 18:45:54 Tower kernel: sd 17:0:0:0: [sdg] tag#24 ASC=0x11 ASCQ=0x4 Nov 8 18:45:54 Tower kernel: sd 17:0:0:0: [sdg] tag#24 CDB: opcode=0x28 28 00 7c 44 00 70 00 00 08 00 Nov 8 18:45:54 Tower kernel: blk_update_request: I/O error, dev sdg, sector 2084831344 Nov 8 18:45:54 Tower kernel: Buffer I/O error on dev sdg, logical block 260603918, async page read Nov 8 18:45:54 Tower kernel: ata17: EH complete Nov 8 18:45:57 Tower kernel: ata17.00: exception Emask 0x0 SAct 0x8 SErr 0x0 action 0x0 Nov 8 18:45:57 Tower kernel: ata17.00: irq_stat 0x40000008 Nov 8 18:45:57 Tower kernel: ata17.00: failed command: READ FPDMA QUEUED Nov 8 18:45:57 Tower kernel: ata17.00: cmd 60/08:18:70:00:44/00:00:7c:00:00/40 tag 3 ncq 4096 in Nov 8 18:45:57 Tower kernel: res 41/40:00:70:00:44/00:00:7c:00:00/40 Emask 0x409 (media error) <F> Nov 8 18:45:57 Tower kernel: ata17.00: status: { DRDY ERR } Nov 8 18:45:57 Tower kernel: ata17.00: error: { UNC } Nov 8 18:45:57 Tower kernel: ata17.00: configured for UDMA/133 Nov 8 18:45:57 Tower kernel: sd 17:0:0:0: [sdg] tag#3 UNKNOWN(0x2003) Result: hostbyte=0x00 driverbyte=0x08 Nov 8 18:45:57 Tower kernel: sd 17:0:0:0: [sdg] tag#3 Sense Key : 0x3 [current] [descriptor] Nov 8 18:45:57 Tower kernel: sd 17:0:0:0: [sdg] tag#3 ASC=0x11 ASCQ=0x4 Nov 8 18:45:57 Tower kernel: sd 17:0:0:0: [sdg] tag#3 CDB: opcode=0x28 28 00 7c 44 00 70 00 00 08 00 Nov 8 18:45:57 Tower kernel: blk_update_request: I/O error, dev sdg, sector 2084831344 Nov 8 18:45:57 Tower kernel: Buffer I/O error on dev sdg, logical block 260603918, async page read Nov 8 18:45:57 Tower kernel: ata17: EH complete Nov 8 18:46:00 Tower kernel: ata17.00: exception Emask 0x0 SAct 0x20000 SErr 0x0 action 0x0 Nov 8 18:46:00 Tower kernel: ata17.00: irq_stat 0x40000008 Nov 8 18:46:00 Tower kernel: ata17.00: failed command: READ FPDMA QUEUED Nov 8 18:46:00 Tower kernel: ata17.00: cmd 60/08:88:20:04:44/00:00:7c:00:00/40 tag 17 ncq 4096 in Nov 8 18:46:00 Tower kernel: res 41/40:00:20:04:44/00:00:7c:00:00/40 Emask 0x409 (media error) <F> Nov 8 18:46:00 Tower kernel: ata17.00: status: { DRDY ERR } Nov 8 18:46:00 Tower kernel: ata17.00: error: { UNC } Nov 8 18:46:00 Tower kernel: ata17.00: configured for UDMA/133 Nov 8 18:46:00 Tower kernel: sd 17:0:0:0: [sdg] tag#17 UNKNOWN(0x2003) Result: hostbyte=0x00 driverbyte=0x08 Nov 8 18:46:00 Tower kernel: sd 17:0:0:0: [sdg] tag#17 Sense Key : 0x3 [current] [descriptor] Nov 8 18:46:00 Tower kernel: sd 17:0:0:0: [sdg] tag#17 ASC=0x11 ASCQ=0x4 Nov 8 18:46:00 Tower kernel: sd 17:0:0:0: [sdg] tag#17 CDB: opcode=0x28 28 00 7c 44 04 20 00 00 08 00 Nov 8 18:46:00 Tower kernel: blk_update_request: I/O error, dev sdg, sector 2084832288 Nov 8 18:46:00 Tower kernel: Buffer I/O error on dev sdg, logical block 260604036, async page read Nov 8 18:46:00 Tower kernel: ata17: EH complete Nov 8 18:46:03 Tower kernel: ata17.00: exception Emask 0x0 SAct 0x20000 SErr 0x0 action 0x0 Nov 8 18:46:03 Tower kernel: ata17.00: irq_stat 0x40000008 Nov 8 18:46:03 Tower kernel: ata17.00: failed command: READ FPDMA QUEUED Nov 8 18:46:03 Tower kernel: ata17.00: cmd 60/08:88:a8:08:44/00:00:7c:00:00/40 tag 17 ncq 4096 in Nov 8 18:46:03 Tower kernel: res 41/40:00:a8:08:44/00:00:7c:00:00/40 Emask 0x409 (media error) <F> Nov 8 18:46:03 Tower kernel: ata17.00: status: { DRDY ERR } Nov 8 18:46:03 Tower kernel: ata17.00: error: { UNC } Nov 8 18:46:03 Tower kernel: ata17.00: configured for UDMA/133 Nov 8 18:46:03 Tower kernel: sd 17:0:0:0: [sdg] tag#17 UNKNOWN(0x2003) Result: hostbyte=0x00 driverbyte=0x08 Nov 8 18:46:03 Tower kernel: sd 17:0:0:0: [sdg] tag#17 Sense Key : 0x3 [current] [descriptor] Nov 8 18:46:03 Tower kernel: sd 17:0:0:0: [sdg] tag#17 ASC=0x11 ASCQ=0x4 Nov 8 18:46:03 Tower kernel: sd 17:0:0:0: [sdg] tag#17 CDB: opcode=0x28 28 00 7c 44 08 a8 00 00 08 00 Nov 8 18:46:03 Tower kernel: blk_update_request: I/O error, dev sdg, sector 2084833448 Nov 8 18:46:03 Tower kernel: Buffer I/O error on dev sdg, logical block 260604181, async page read Nov 8 18:46:03 Tower kernel: ata17: EH complete Nov 8 18:46:05 Tower kernel: ata17.00: exception Emask 0x0 SAct 0x400000 SErr 0x0 action 0x0 Nov 8 18:46:05 Tower kernel: ata17.00: irq_stat 0x40000008 Nov 8 18:46:05 Tower kernel: ata17.00: failed command: READ FPDMA QUEUED Nov 8 18:46:05 Tower kernel: ata17.00: cmd 60/08:b0:a8:08:44/00:00:7c:00:00/40 tag 22 ncq 4096 in Nov 8 18:46:05 Tower kernel: res 41/40:00:a8:08:44/00:00:7c:00:00/40 Emask 0x409 (media error) <F> Nov 8 18:46:05 Tower kernel: ata17.00: status: { DRDY ERR } Nov 8 18:46:05 Tower kernel: ata17.00: error: { UNC } Nov 8 18:46:05 Tower kernel: ata17.00: configured for UDMA/133 Nov 8 18:46:05 Tower kernel: sd 17:0:0:0: [sdg] tag#22 UNKNOWN(0x2003) Result: hostbyte=0x00 driverbyte=0x08 Nov 8 18:46:05 Tower kernel: sd 17:0:0:0: [sdg] tag#22 Sense Key : 0x3 [current] [descriptor] Nov 8 18:46:05 Tower kernel: sd 17:0:0:0: [sdg] tag#22 ASC=0x11 ASCQ=0x4 Nov 8 18:46:05 Tower kernel: sd 17:0:0:0: [sdg] tag#22 CDB: opcode=0x28 28 00 7c 44 08 a8 00 00 08 00 Nov 8 18:46:05 Tower kernel: blk_update_request: I/O error, dev sdg, sector 2084833448 Nov 8 18:46:05 Tower kernel: Buffer I/O error on dev sdg, logical block 260604181, async page read Nov 8 18:46:05 Tower kernel: ata17: EH complete Nov 8 18:46:09 Tower kernel: ata17.00: exception Emask 0x0 SAct 0x2000000 SErr 0x0 action 0x0 Nov 8 18:46:09 Tower kernel: ata17.00: irq_stat 0x40000008 Nov 8 18:46:09 Tower kernel: ata17.00: failed command: READ FPDMA QUEUED Nov 8 18:46:09 Tower kernel: ata17.00: cmd 60/08:c8:88:29:44/00:00:7c:00:00/40 tag 25 ncq 4096 in Nov 8 18:46:09 Tower kernel: res 41/40:00:88:29:44/00:00:7c:00:00/40 Emask 0x409 (media error) <F> Nov 8 18:46:09 Tower kernel: ata17.00: status: { DRDY ERR } Nov 8 18:46:09 Tower kernel: ata17.00: error: { UNC } Nov 8 18:46:09 Tower kernel: ata17.00: configured for UDMA/133 Nov 8 18:46:09 Tower kernel: sd 17:0:0:0: [sdg] tag#25 UNKNOWN(0x2003) Result: hostbyte=0x00 driverbyte=0x08 Nov 8 18:46:09 Tower kernel: sd 17:0:0:0: [sdg] tag#25 Sense Key : 0x3 [current] [descriptor] Nov 8 18:46:09 Tower kernel: sd 17:0:0:0: [sdg] tag#25 ASC=0x11 ASCQ=0x4 Nov 8 18:46:09 Tower kernel: sd 17:0:0:0: [sdg] tag#25 CDB: opcode=0x28 28 00 7c 44 29 88 00 00 08 00 Nov 8 18:46:09 Tower kernel: blk_update_request: I/O error, dev sdg, sector 2084841864 Nov 8 18:46:09 Tower kernel: Buffer I/O error on dev sdg, logical block 260605233, async page read Nov 8 18:46:09 Tower kernel: ata17: EH complete Nov 8 18:46:11 Tower kernel: ata17.00: exception Emask 0x0 SAct 0x40 SErr 0x0 action 0x0 Nov 8 18:46:11 Tower kernel: ata17.00: irq_stat 0x40000008 Nov 8 18:46:11 Tower kernel: ata17.00: failed command: READ FPDMA QUEUED Nov 8 18:46:11 Tower kernel: ata17.00: cmd 60/08:30:88:29:44/00:00:7c:00:00/40 tag 6 ncq 4096 in Nov 8 18:46:11 Tower kernel: res 41/40:00:88:29:44/00:00:7c:00:00/40 Emask 0x409 (media error) <F> Nov 8 18:46:11 Tower kernel: ata17.00: status: { DRDY ERR } Nov 8 18:46:11 Tower kernel: ata17.00: error: { UNC } Nov 8 18:46:12 Tower kernel: ata17.00: configured for UDMA/133 Nov 8 18:46:12 Tower kernel: sd 17:0:0:0: [sdg] tag#6 UNKNOWN(0x2003) Result: hostbyte=0x00 driverbyte=0x08 Nov 8 18:46:12 Tower kernel: sd 17:0:0:0: [sdg] tag#6 Sense Key : 0x3 [current] [descriptor] Nov 8 18:46:12 Tower kernel: sd 17:0:0:0: [sdg] tag#6 ASC=0x11 ASCQ=0x4 Nov 8 18:46:12 Tower kernel: sd 17:0:0:0: [sdg] tag#6 CDB: opcode=0x28 28 00 7c 44 29 88 00 00 08 00 Nov 8 18:46:12 Tower kernel: blk_update_request: I/O error, dev sdg, sector 2084841864 Nov 8 18:46:12 Tower kernel: Buffer I/O error on dev sdg, logical block 260605233, async page read Nov 8 18:46:12 Tower kernel: ata17: EH complete which don't look promising...
  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 # # Cycle 1 of 1, partition start on sector 64. # # # # # # Step 1 of 5 - Pre-read verification: [9:58:19 @ 55 MB/s] SUCCESS # # Step 2 of 5 - Zeroing the disk: [7:34:05 @ 73 MB/s] SUCCESS # # Step 3 of 5 - Writing unRAID's Preclear signature: SUCCESS # # Step 4 of 5 - Verifying unRAID's Preclear signature: SUCCESS # # Step 5 of 5 - Post-Read in progress: (53% Done) # # # # # # # # # # # # ** Time elapsed: 61:24:10 | Current speed: 30.2 MB/s | Average speed: 4 MB/s # # # ############################################################################################################################ # Cycle elapsed time: 79:00:36 | Total elapsed time: 79:00:37 # ############################################################################################################################ ############################################################################################################################ # # # S.M.A.R.T. Status # # # # # # ATTRIBUTE INITIAL STATUS # # 5-Reallocated_Sector_Ct 0 - # # 9-Power_On_Hours 41989 - # # 194-Temperature_Celsius 30 - # # 196-Reallocated_Event_Count 0 - # # 197-Current_Pending_Sector 6 - # # 198-Offline_Uncorrectable 0 - # # 199-UDMA_CRC_Error_Count 0 - # # # # # # # # # # # ############################################################################################################################ # SMART overall-health self-assessment test result: PASSED # ############################################################################################################################ And I have a new WD RED 6TB waiting to joing the Array. Is this normal? Can I / should I stop the process and if so will unRaid (6.2) allow me to add it in the array? There was a "197-Current_Pending_Sector 6" which Googled to "zeroing the disk fixes it", and SMART overall status is passed. Thank you, Christos.
  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... - process known inodes and perform inode discovery... - agno = 0 - agno = 1 - agno = 2 - agno = 3 - process newly discovered inodes... Phase 4 - check for duplicate blocks... - setting up duplicate extent list... - check for inodes claiming duplicate blocks... - agno = 2 - agno = 3 - agno = 1 - agno = 0 Phase 5 - rebuild AG headers and trees... - reset superblock... Phase 6 - check inode connectivity... - resetting contents of realtime bitmap and summary inodes - traversing filesystem ... - traversal finished ... - moving disconnected inodes to lost+found ... Phase 7 - verify and correct link counts... Maximum metadata LSN (3:1410955) is ahead of log (1:2). Format log to cycle 6. done Disk4 is mounted again and the files re-appeared. Browsing directly in disk4 did not show and lost+found folder. I will check back the behavior of the disk in a few hours as I have already seeing it "appearing and disappearing" once, but I 'm guessing the command did the trick.
  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 followed the instructions suggested at https://lime-technology.com/wiki/index.php/Check_Disk_Filesystems#Drives_formatted_with_XFS , I stopped the Array and started it in Maintenance mode, then run xfs_repair -v /dev/md4 which returned some errors and suggestions, see attached "xfs_repair md4.txt", which advises that "The filesystem has valuable metadata changes in a log which needs to be replayed. Mount the filesystem to replay the log, and unmount it before re-running xfs_repair". So I stopped the Array and restarted it (no in Maintenance mode), and now on the webGUI the Dashboard shows the Disk4 as active, but the Main tab shows it as unmountable. Accessing Disk4 from there (its settings) I see the File system status to be "Unmountable - No file system (32)". And that 's how far I could go on my own. I have one parity disk and 5 data disks. xfs_repair suggests I use the -L option in case that helps, but that also says it can cause data corruption so why would I want to do that, I have opted for a parity disk. Is there a way to use the parity to rebuilt disk4? Are there any other suggestions that could restore the file system and mount disk4 again without any data loss? xfs_error_md4.zip xfs_repair_md4.txt
  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 Ready at 35%. There was no possibility to safe boot, repair, revert or anything like that. In the end I edited the config file again and changed USB mode from 3.0 to 2.0. I also changed the Machine Type from i440fx.2.3 to 2.5 (a new option in 6.2? ) as well as the two CDROMs from IDE to SATA. But I am guessing that the USB Mode did the trick. It is still a bit strange as Win10 booted just fine and operated for a few days without problems with "the new hardware".
  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 update process from the GUI, is there anything else I should do? My system is: unRaid 6.1.7 1 docker (MineOS for the kids) 2 VMs (Win10, WinServer 2012), both with OVMFS (separate filenames - was fixed / better supported in 6.2) Parity (on motherboard) + 5 HDDs (2 on motherboards, 2 on 1st Sata PCIex, 1 on 2nd Sata PCIex) Public and private user shares (no disk shares) root + 2 custom users Preclear disks, Unassigned Devices, Community Applications, Dynamix webGui plugins My 6.1.7 was my first (clean) installation and I have not updated since, but 6.2 is an excellent update with tons of features I would like to have. Thank you in advance.