EMKO
-
Posts
186 -
Joined
-
Last visited
Content Type
Profiles
Forums
Downloads
Store
Gallery
Bug Reports
Documentation
Landing
Posts posted by EMKO
-
-
yes it is doing a correction every time, i am using two SASLP-MV8 not sure if they are based on Marvel controllers, although i didn't get these errors for a long time.
-
Does anyone know how i can identify the drive causing the parity check errors? i get 5 every time. Is there a way to make Unraid remember the values on each disk at these error spots and then after a another parity check compare to see what drive is changing these spots? and have ability rerun at these spots to see if its fixed? i have 11 drivers many different sizes maybe i can get a notification when error happens so i can at least narrow it down if it gets passed some smaller drives without errors.
or am i limited to having to take a drive out one at a time with a new one rebuild the data and then check with a party check that takes like 20hours? each time?
-
Ok so i am having another weird issue appear, i am trying to transfer files from an unraid share to a usb connected to one of my vms, the usb is passed to the vm via a pci-e usb controller that is passed through directly
After transferring around 200gb i get all of samba lock up and be inaccessible - i lose access to the unraid gui as well but everything else works; vms, ssh, etc.
I managed to get powerdown to run which fetched the log but actually did not manage to shut down the system it just sat there
I have checked my logs and can see nothing wrong or reported incorrectly - i have tried this transfer using both my vms on the system but it seems to fail on both after 200gb
Can anyone see any issues in my logs? At the moment everything seems to be working solid except for the actual nas part (i can write as much as i like but get issues with reads)
I am unsure if this is occurring also due to the fact my vms seem to be leaking memory heavily and on a fresh boot my system will have 9gb memory left, after 7 days a 12gb vm jumps to 19gb memory usage and the system has less then 1gb free
The issue i am having at present can happen after an hour however
Regards,
Jamie
Edit: This issue does seem to be beta related as i was able to transfer over 4tb's of data to backup usbs on 6.1.9
I've been having this issue as well. Any time I try and transfer files from a share to a flash drive or another computer, it will lock up Samba, WebGUI, Dockers, pretty much everything. I can SSH as well, but powerdown does nothing. I've also observed this same behavior when Sabnzbd is processing very large files and moving them into the array. Seems it's definitely because of heavy IO load. I'll try the suggested fix of changing the md_num_stripes to 8192 and report back if that works around the issue.
I too have had several issues, when transferring files (between drives in array, between drives and cache, between local USB and drives in array) with everything locking up, losing GUI, etc but can still SSH and my Powerdown script also does nothing. Hopefully the LT guys are reading this and notice a pattern of some kind here.
I'm transfering over 50GB right now after trying out the workaround of adjusting the md_num_stripes. So far I haven't run into an issue. Usually for me it would lock up almost immediately.
I made the md_num_stripes change on mine, but havn't attempted any large file transfers since (and was tired of hard power cycling my server several times a day when doing previous trouble shooting.
i reported this same problem since beta 16 i don't think they know or can reproduce this, worst is i can't clean power down
what does md_num_stripes do and what should i set it as? to fix this problem.
-
Can't dump the ROM
root@Tower:/sys/bus/pci/devices/0000:04:00.0# cat rom > /boot/vbios.dump
cat: rom: Input/output error
i can dump the ROM of the GPU that Unraid is using i don't understand why i can't dump this one.
any ideas? do i need to run a VM and then shut it down then do a dump?
also i have a spare card that i want to use but its 3 slot sized so i will have to remove my SATA ports cards to fit it does Unraid Array need to be up to do a dump? so that i can use 2 GPU's get the dump and then install back my SAtA ports ?
-
another thing you can try is to specify the rom file. http://lime-technology.com/wiki/index.php/UnRAID_6/VM_Management#Edit_XML_for_VM_to_supply_GPU_ROM_manually, but i think it is as saarg says the card doesnt reset.
but it works fine with Openelec VM i can from Unraid stop the VM and restart it without problems but i can not do this with Windows 7 only thing i couldn't do was Force Stop the VM if i did that the VM would not boot again until i did a reboot of the server.
Is this because Windows 7 is using Seabios? while Openelec uses OVFM i think OVFM does something that helps with this problem.
-
Your GPU most likely doesn't support to be reset. What you can do to avoid restarting unraid is to safely remove the GPU before you reboot the VM. It's done the same way as with a USB stick.
could you please explain how this is done?
what i find strange is this only happens with Windows 7
Openelec i can stop and start the VM perfectly fine BUT i can not Force stop if i do that it behaves just like Windows 7 VM
-
" However, using either bios type, the server/VM are completely unstable and will regularly lock up the entire unRaid server (can’t even power down from console or ssh) seemingly during file transfers between the unRaid shares and the VM’s 2nd vdisk. I have not seen/noticed a lockup outside of transferring/accessing files. "
sounds like the problems i had with 6.2 where any time i tried to transfer files around with samba Unraid would stop showing files/folder anymore so apps etc would crash i couldn't even reboot unraid with ssh
http://lime-technology.com/forum/index.php?topic=47408.375
Yea something very wrong with samba i think, today i was working on my desktop and Windows File History tried to back up the file to my Backup share this worked on 6.1.9 just fine but on 6.2 Unraid webui is not responding and the Openelec VM crashed.If i type in the share into windows explorer it causes the window to not respond i dont understand its as if Windows sees the shares but something is going very wrong and can't connect to it.
This time i can't even get the diagnostics
and again i can't get the system even to reboot in ssh have to manually power it down.
EDIT: some more information
Dockers are running during the problem BUT looks like no of them can see the array files, is this a file system problem?
EDIT:
so i sshed into Unraid to see if i can see the array files
/mnt/user - works, i can see all my share folders
/mnt/user/Tv Shows works i can see all my tv show folders
/mnt/user/Tv shows/24 works i see the seasons folders
/mnt/user/Tv shows/24/Season 1 Nope when i get into it and type ls it just hangs nothing happens, whats going oN?
Edit: after going to eat and coming back Unraid webui responed
i managed to get a diagnostic file then i checked if the smb shares are working they where up and loading but if i tried to open any file it froze up.looks like Unraid can't see any files/folders after the bug happens
maybe you can try boot in safemode with no vms and test out transferring files between two share and see if that crashes Unraid, i dont know if this is a samba problem or something else but maybe it can be triggered other ways
thanks
-
5 - Obtain the vendor/product ID for that device from the last column. 00:19.0 from my example is 8086:153b.
6 - Edit your syslinux.cfg file and add the following after the append but before initrd=/bzroot.
Code: [select]
pci-stub.ids=8086:153b
what does this do?
i have a on board network and a pci 2 port
but all show up same
05:00.0 0200: 10ec:8168 (rev 0c)
06:00.0 0200: 10ec:8168 (rev 0c)
0d:00.0 0200: 10ec:8168 (rev 09)
i did add the 2 port to my vm and its working but what happens when i reboot the system? will unraid try to use it ?
-
"Oh wait, I lied - I DID add the MSI interrupt line to the sound.conf file on this install, same as you would for OE. So one tiny tweak."
what is that and why do we need it?
-
wow works great can't Unraid automate this? Unraid way i would get USB to work for 1-2min this way works and i can change the usb device at any time.
Only problem if i change anything in the VM this VM text gets reset
-
just to let you know i am back on 6.1.9 all transfers working perfect so its definitely something to do with 6.2.0
now i just have to figure out how to get my dockers/vms back
do you guys have any clue what the problem with 6.2.0 could be?
More fixes coming for -beta19, suggest you try that when it gets published.
Hi Just to say I have found samba shares being very slow aswell.
When using my win 10 vm the vm will take forever to view the mapped drives and slow transfers when using shares. I cant be bothered to downgrade so will wait for the next beta, but just thought I would let you know im having same issue.
I get the same issue, including samba locking up entirely when trying to load a steam library over it
Looking forward to beta 19, hopefully it comes out pretty soon
YES another person with same problem
hopefully this means its reproducible and they can fix it -
just to let you know i am back on 6.1.9 all transfers working perfect so its definitely something to do with 6.2.0
now i just have to figure out how to get my dockers/vms back
do you guys have any clue what the problem with 6.2.0 could be?
EMKO,
Just reviewed your logs and there are multiple possibilities here, but Tom has already said it best himself:
just to let you know i am back on 6.1.9 all transfers working perfect so its definitely something to do with 6.2.0
now i just have to figure out how to get my dockers/vms back
do you guys have any clue what the problem with 6.2.0 could be?
More fixes coming for -beta19, suggest you try that when it gets published.
oh nice i will test it, is there easy way to downgrade if it still has problems? when i went back to 5.1.9 all my dockers/vms where missing/broken.
can i just backup my dockers.img ?
-
just to let you know i am back on 6.1.9 all transfers working perfect so its definitely something to do with 6.2.0
now i just have to figure out how to get my dockers/vms back
do you guys have any clue what the problem with 6.2.0 could be?
-
Yea something very wrong with samba i think, today i was working on my desktop and Windows File History tried to back up the file to my Backup share this worked on 6.1.9 just fine but on 6.2 Unraid webui is not responding and the Openelec VM crashed.
If i type in the share into windows explorer it causes the window to not respond i dont understand its as if Windows sees the shares but something is going very wrong and can't connect to it.
This time i can't even get the diagnostics
and again i can't get the system even to reboot in ssh have to manually power it down.
EDIT: some more information
Dockers are running during the problem BUT looks like no of them can see the array files, is this a file system problem?
EDIT:
so i sshed into Unraid to see if i can see the array files
/mnt/user - works, i can see all my share folders
/mnt/user/Tv Shows works i can see all my tv show folders
/mnt/user/Tv shows/24 works i see the seasons folders
/mnt/user/Tv shows/24/Season 1 Nope when i get into it and type ls it just hangs nothing happens, whats going oN?
Edit: after going to eat and coming back Unraid webui responed
i managed to get a diagnostic file then i checked if the smb shares are working they where up and loading but if i tried to open any file it froze up.From reviewing your logs, can you please boot up in safe mode and try your testing again? You have a large number of plugins on your system that we'd like to see out of the equation before continuing diagnosis. Keep in mind, we have massively upgraded the OS / kernel in this release, so it's quite possible that some of the packages installed via these plugins will require updating before they are properly compatible. If you can cause another issue to occur with no plugins running, please report back with another diagnostics.
Ok booted into safe mode did a transfer from share to share on my computer same result
Edit: sorry but this is as much as i can handle right now going back to 6.1.9 hope the logs show something and it can be fixed
-
Yea something very wrong with samba i think, today i was working on my desktop and Windows File History tried to back up the file to my Backup share this worked on 6.1.9 just fine but on 6.2 Unraid webui is not responding and the Openelec VM crashed.
If i type in the share into windows explorer it causes the window to not respond i dont understand its as if Windows sees the shares but something is going very wrong and can't connect to it.
This time i can't even get the diagnostics
and again i can't get the system even to reboot in ssh have to manually power it down.
EDIT: some more information
Dockers are running during the problem BUT looks like no of them can see the array files, is this a file system problem?
EDIT:
so i sshed into Unraid to see if i can see the array files
/mnt/user - works, i can see all my share folders
/mnt/user/Tv Shows works i can see all my tv show folders
/mnt/user/Tv shows/24 works i see the seasons folders
/mnt/user/Tv shows/24/Season 1 Nope when i get into it and type ls it just hangs nothing happens, whats going oN?
Edit: after going to eat and coming back Unraid webui responed
i managed to get a diagnostic file then i checked if the smb shares are working they where up and loading but if i tried to open any file it froze up. -
oh sorry didn't even know Unraid had diagnostics, anyways here is the diagnostics did another test same result transfer goes for about 10% then drops to 0 bytes/s and Openelec VM is frozen.
Only happens when i transfer from share to share, if i transfer to my computer first then to the share it works.
Every time this happens i can't get Unraid to shutdown properly or i don't know how to, the webui stops responding
-
second time this has happened, i have a file in one share and am trying to move it to another during the transfer the speed will drop to 0 and the Openelec VM that's running will freeze.
I then trying to stop the array looks like it shuts down all the Dockers fine but the webui never loads back up i think it gets stuck on shutting down the frozen VM. Last time i tried to load the tower/VMS page and that made the webui stop loading.
i don't know whats happening maybe samba is crashing since both times Openelec was also watching video files using smb, on windows i can brows the smb shares and see the files but i cant get them to open.
also when i ssh and typed reboot it wont reboot
6.1 i did this many times never had a problem.
edit:
transferring the file first to my computer then to the share i want works, tested again to see if i can direct transfer between the shares and this time openelec vm was not playing any files but still the speed dropped to 0.
trying to go to the VMs page does not load and causes the webui to never load again and the smb shares are not working anymore.
-
i don't have this "<qemu:arg value='vfio-pci,host=01:00.0,bus=pcie.0,multifunction=on,x-vga=on'/>" any ideas?
<domain type='kvm' id='14'><name>OpenELEC 6.0</name>
<uuid>712159f2-29a3-2536-c9fa-dc78f56ee6a1</uuid>
<metadata>
<vmtemplate xmlns="unraid" name="OpenELEC" icon="openelec.png" openelec="6.0.0_1"/>
</metadata>
<memory unit='KiB'>4718592</memory>
<currentMemory unit='KiB'>4718592</currentMemory>
<memoryBacking>
<nosharepages/>
<locked/>
</memoryBacking>
<vcpu placement='static'>2</vcpu>
<cputune>
<vcpupin vcpu='0' cpuset='0'/>
<vcpupin vcpu='1' cpuset='1'/>
</cputune>
<resource>
<partition>/machine</partition>
</resource>
<os>
<type arch='x86_64' machine='pc-q35-2.5'>hvm</type>
<loader readonly='yes' type='pflash'>/usr/share/qemu/ovmf-x64/OVMF_CODE-pure-efi.fd</loader>
<nvram>/etc/libvirt/qemu/nvram/712159f2-29a3-2536-c9fa-dc78f56ee6a1_VARS-pure-efi.fd</nvram>
</os>
<features>
<acpi/>
<apic/>
</features>
<cpu mode='host-passthrough'>
<topology sockets='1' cores='1' threads='2'/>
</cpu>
<clock offset='utc'>
<timer name='rtc' tickpolicy='catchup'/>
<timer name='pit' tickpolicy='delay'/>
<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/vm/OpenELEC-unRAID.x86_64-6.0.0_1.img'/>
<backingStore/>
<target dev='hdc' bus='virtio'/>
<readonly/>
<boot order='1'/>
<alias name='virtio-disk2'/>
<address type='pci' domain='0x0000' bus='0x02' slot='0x04' function='0x0'/>
</disk>
<controller type='usb' index='0' model='nec-xhci'>
<alias name='usb'/>
<address type='pci' domain='0x0000' bus='0x00' slot='0x07' function='0x0'/>
</controller>
<controller type='sata' index='0'>
<alias name='ide'/>
<address type='pci' domain='0x0000' bus='0x00' slot='0x1f' function='0x2'/>
</controller>
<controller type='pci' index='0' model='pcie-root'>
<alias name='pcie.0'/>
</controller>
<controller type='pci' index='1' model='dmi-to-pci-bridge'>
<model name='i82801b11-bridge'/>
<alias name='pci.1'/>
<address type='pci' domain='0x0000' bus='0x00' slot='0x1e' function='0x0'/>
</controller>
<controller type='pci' index='2' model='pci-bridge'>
<model name='pci-bridge'/>
<target chassisNr='2'/>
<alias name='pci.2'/>
<address type='pci' domain='0x0000' bus='0x01' slot='0x01' function='0x0'/>
</controller>
<controller type='virtio-serial' index='0'>
<alias name='virtio-serial0'/>
<address type='pci' domain='0x0000' bus='0x02' slot='0x03' function='0x0'/>
</controller>
<filesystem type='mount' accessmode='passthrough'>
<source dir='/mnt/user/vm/'/>
<target dir='appconfig'/>
<alias name='fs0'/>
<address type='pci' domain='0x0000' bus='0x02' slot='0x01' function='0x0'/>
</filesystem>
<interface type='bridge'>
<mac address='52:54:00:d8:1e:27'/>
<source bridge='br0'/>
<target dev='vnet0'/>
<model type='virtio'/>
<alias name='net0'/>
<address type='pci' domain='0x0000' bus='0x02' slot='0x02' function='0x0'/>
</interface>
<serial type='pty'>
<source path='/dev/pts/0'/>
<target port='0'/>
<alias name='serial0'/>
</serial>
<console type='pty' tty='/dev/pts/0'>
<source path='/dev/pts/0'/>
<target type='serial' port='0'/>
<alias name='serial0'/>
</console>
<channel type='unix'>
<source mode='bind' path='/var/lib/libvirt/qemu/channel/target/domain-OpenELEC 6.0/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>
<hostdev mode='subsystem' type='pci' managed='yes'>
<driver name='vfio'/>
<source>
<address domain='0x0000' bus='0x07' slot='0x00' function='0x0'/>
</source>
<alias name='hostdev0'/>
<address type='pci' domain='0x0000' bus='0x02' slot='0x05' function='0x0'/>
</hostdev>
<hostdev mode='subsystem' type='pci' managed='yes'>
<driver name='vfio'/>
<source>
<address domain='0x0000' bus='0x07' slot='0x00' function='0x1'/>
</source>
<alias name='hostdev1'/>
<address type='pci' domain='0x0000' bus='0x02' slot='0x06' function='0x0'/>
</hostdev>
<memballoon model='virtio'>
<alias name='balloon0'/>
<address type='pci' domain='0x0000' bus='0x02' slot='0x07' function='0x0'/>
</memballoon>
</devices>
</domain>
-
Start up a new Openelec 6.0 VM i get this in the logs never seen this before is there a problem? Openelec does run fine
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-03-12T21:42:40.054309Z qemu-system-x86_64: AMD CPU doesn't support hyperthreading. Please configure -smp options properly.
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-03-12T21:42:42.885398Z qemu-system-x86_64: vfio-pci: Cannot read device rom at 0000:08:00.0
Device option ROM contents are probably invalid (check dmesg).
Skip option ROM probe with rombar=0, or load from file with romfile=
Also now i can stop/start up Openelec VM as much as i want the GPU pass thought works every time.
Has the no on board single Nvidia GPU card pass through been fixed?
-
okay its checking in so you can block bad beta releases etc, but can't you add a Warning that you have not connected and tell the user there is a risk ? and still let them use it if they accept? i want to test out the new beta but i am not sure what will happen since i use Pfsense Vm to run my internet and i need Unraid to be running
-
the software is a bit relaxed if it has already authenticated before. If it has, then it gives an additional period of time of purchased features before it get's mad that it can't contact home. This would be an acceptable solution.
Definitely not for me. I use unRAID as just a NAS, I don't use any of the features. I have zero use for it to have network access, so to protect my data, I have it only accessible internally. There's no reason I should have to change that now, and I'm not going to reconfigure it on the firewall every time it stops working. It should work like it's been working
I get that, and this is an assumption, but if you have a router that supports iptables, you could easily setup a firewall rule to allow outgoing from unraid's ip to limetech's key server ip. I still don't think it should be calling home at all, but I get it, they are trying to protect themselves against pirates and that's hard to do these days.
but how do i connect to the internet? if i use Pfsense on Unraid as a VM? i have to have Unraid let me run the VM first before it can connect to the internet.
-
Important: Your server will require internet access upon boot in order to validate with the LimeTech key server.
What the hell?
so how do i get my internet if i cant boot Unraid? since i use Pfsense in a VM running ON UNRAID LOL
??????? -
sorry if dumb question but would this ROM thing work for the problem i have with any time i start a VM with GPU pass through i can only do it once, if i turn off the VM and try to start it up again nothing shows up.
-
so, I finally finished doing it. installed windows 10 with kodi, win10 native AMD drivers give me perfect passthrough and HD audio bitstreaming in a VM. so yes, as we know, the linux AMD drivers suck and until they are fixed, used the Nvidia 720.
or wait for the noted above news for maybe a real fix from AMD, but who knows when that will be.
Either way I am going to stick with nvidia cards. The one other HUGE advantage I am seeing (maybe just specific to me) is that I can force shutdown a VM with an nvidia card and start it up again without issue. With the AMD cards this always caused a kernel panic in the VM and the only way to fix was to restart the server. All 3 of my HD6450's (3 different vendors) exhibited this behavior.
Every time i stop my openelec vm i i can not get it to work again unless i reboot the Unraid machine i am on a nvidia 430 how can i tell if the VM has a kernel panic?
I would see it on my TV during the boot process. So, output was making it to the display but eventually paniced.
John
hmm i will check though i am 100% sure i just get a black screen
i really hope this gets fixed so i can change VM's without having to reboot the Unraid machinelike i run Pfsesne and that uses VNC works fine when it reboots
i managed to get a diagnostic file then i checked if the smb shares are working they where up and loading but if i tried to open any file it froze up.
??
Parity check consistant error count.
in General Support
Posted
oh crap not what i was hoping for
well maybe i can see if i can get this one drive onto my motherboard SATA
thanks