• Posts

  • Joined

  • Last visited


  • Gender

Recent Profile Visitors

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

EMKO's Achievements


Explorer (4/14)



  1. 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
  2. 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.
  3. 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?
  4. 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.
  5. 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 ?
  6. 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.
  7. 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
  8. " 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 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
  9. 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 ?
  10. "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?
  11. 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
  12. 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
  13. EMKO, Just reviewed your logs and there are multiple possibilities here, but Tom has already said it best himself: 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 ?
  14. 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?
  15. 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 tower-diagnostics-20160316-1521.zip