footballmad

<?xml version='1.0' encoding='UTF-8'?> <domain type='kvm'> <name>Win10-Game</name> <uuid>64af1713-66ec-a989-f732-a5ad44584c23</uuid> <metadata> <vmtemplate xmlns="unraid" name="Windows 10" icon="windows.png" os="windows10"/> </metadata> <memory unit='KiB'>33554432</memory> <currentMemory unit='KiB'>33554432</currentMemory> <memoryBacking> <nosharepages/> </memoryBacking> <vcpu placement='static'>12</vcpu> <cputune> <vcpupin vcpu='0' cpuset='3'/> <vcpupin vcpu='1' cpuset='19'/> <vcpupin vcpu='2' cpuset='4'/> <vcpupin vcpu='3' cpuset='20'/> <vcpupin vcpu='4' cpuset='5'/> <vcpupin vcpu='5' cpuset='21'/> <vcpupin vcpu='6' cpuset='6'/> <vcpupin vcpu='7' cpuset='22'/> <vcpupin vcpu='8' cpuset='7'/> <vcpupin vcpu='9' cpuset='23'/> <vcpupin vcpu='10' cpuset='8'/> <vcpupin vcpu='11' cpuset='24'/> </cputune> <resource> <partition>/machine</partition> </resource> <os> <type arch='x86_64' machine='pc-i440fx-3.0'>hvm</type> <loader readonly='yes' type='pflash'>/usr/share/qemu/ovmf-x64/OVMF_CODE-pure-efi.fd</loader> <nvram>/etc/libvirt/qemu/nvram/64af1713-66ec-a989-f732-a5ad44584c23_VARS-pure-efi.fd</nvram> </os> <features> <acpi/> <apic/> <hyperv> <relaxed state='on'/> <vapic state='on'/> <spinlocks state='on' retries='8191'/> <vendor_id state='on' value='none'/> </hyperv> </features> <cpu mode='host-passthrough' check='none'> <topology sockets='1' cores='6' threads='2'/> </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='block' device='disk'> <driver name='qemu' type='raw' cache='writeback'/> <source dev='/dev/disk/by-id/ata-LITEONIT_LCS-256M6S_2.5_7mm_256GB_TW0XFJWX5508535R0932'/> <target dev='hdc' bus='sata'/> <boot order='1'/> <address type='drive' controller='0' bus='0' target='0' unit='2'/> </disk> <disk type='block' device='disk'> <driver name='qemu' type='raw' cache='writeback'/> <source dev='/dev/disk/by-id/ata-WDC_WD5002ABYS-02B1B0_WD-WCASY9127385'/> <target dev='hdd' bus='sata'/> <address type='drive' controller='0' bus='0' target='0' unit='3'/> </disk> <controller type='usb' index='0' model='ich9-ehci1'> <address type='pci' domain='0x0000' bus='0x00' slot='0x07' function='0x7'/> </controller> <controller type='usb' index='0' model='ich9-uhci1'> <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'> <master startport='2'/> <address type='pci' domain='0x0000' bus='0x00' slot='0x07' function='0x1'/> </controller> <controller type='usb' index='0' model='ich9-uhci3'> <master startport='4'/> <address type='pci' domain='0x0000' bus='0x00' slot='0x07' function='0x2'/> </controller> <controller type='pci' index='0' model='pci-root'/> <controller type='ide' index='0'> <address type='pci' domain='0x0000' bus='0x00' slot='0x01' function='0x1'/> </controller> <controller type='sata' index='0'> <address type='pci' domain='0x0000' bus='0x00' slot='0x03' function='0x0'/> </controller> <controller type='virtio-serial' index='0'> <address type='pci' domain='0x0000' bus='0x00' slot='0x04' function='0x0'/> </controller> <interface type='bridge'> <mac address='52:54:00:31:94:83'/> <source bridge='br0'/> <model type='virtio'/> <address type='pci' domain='0x0000' bus='0x00' slot='0x09' function='0x0'/> </interface> <serial type='pty'> <target type='isa-serial' port='0'> <model name='isa-serial'/> </target> </serial> <console type='pty'> <target type='serial' port='0'/> </console> <channel type='unix'> <target type='virtio' name='org.qemu.guest_agent.0'/> <address type='virtio-serial' controller='0' bus='0' port='1'/> </channel> <input type='tablet' bus='usb'> <address type='usb' bus='0' port='1'/> </input> <input type='mouse' bus='ps2'/> <input type='keyboard' bus='ps2'/> <graphics type='vnc' port='-1' autoport='yes' websocket='-1' listen='0.0.0.0' keymap='fr-ch'> <listen type='address' address='0.0.0.0'/> </graphics> <video> <model type='qxl' ram='65536' vram='65536' vgamem='16384' heads='1' primary='yes'/> <address type='pci' domain='0x0000' bus='0x00' slot='0x02' function='0x0'/> </video> <hostdev mode='subsystem' type='pci' managed='yes'> <driver name='vfio'/> <source> <address domain='0x0000' bus='0x05' slot='0x00' function='0x0'/> </source> <address type='pci' domain='0x0000' bus='0x00' slot='0x05' function='0x0'/> </hostdev> <hostdev mode='subsystem' type='pci' managed='yes'> <driver name='vfio'/> <source> <address domain='0x0000' bus='0x05' slot='0x00' function='0x1'/> </source> <address type='pci' domain='0x0000' bus='0x00' slot='0x06' function='0x0'/> </hostdev> <memballoon model='virtio'> <address type='pci' domain='0x0000' bus='0x00' slot='0x08' function='0x0'/> </memballoon> </devices> <seclabel type='dynamic' model='dac' relabel='yes'/> </domain>

Hi guys, Hopefully this is something simple for you. I took out my GTX 1060 for another project, originally it was used on a VM passthroughed. I've since removed it and thought changing to VNC would be sufficient to start it and have access but I have this error,any ideas please? Thanks

Thanks for your reply, so I can forget it for docker containers then.

So what's the point in isolating cores? Sorry if I've misunderstood.

Thanks for the reply, I guess it was this part of the video I must have misunderstood. My question now is, is there any way at all to pin multiple cpu cores exclusively for docker applications? Thanks

More info that should be useful. The error stated above says that Plex "will only execute on a single isolated core" As you can see here, I pinned 10-15,26-31 for Plex. On the dashboard I have this, clearly showing one core at 100% Did I misunderstand advanced tweaks from @SpaceInvaderOne ???? Many thanks

After reading what I wrote I would like to clarify, If I understand correctly, I could pin Plex to 4 cores but it will only ever use one? Is that correct?

Hi, After watching many of the excellent videos by SpaceInvader One, I decided to isoloate some cpus from UNRAID and the pin them to one VM and my Plex docker. However since doing this I have this error message from the "fix common problems" plugin, ERRORS FOUND SUGGESTED FIX Docker Application plex has multiple CPUs pinned to isolated CPUs Unless you know exactly what you are doing, pinning a docker application to multiple isolated CPUs will only allow the application to execute on a single isolated core and adjust either the Isolated CPUs or the application's CPU pinning I upgraded to Version 6.6.0 the other day without issue. Here's the line I added, isolcpus=4-15,20-31 and wanted to pin 4 or 6 cores to Plex. https://youtu.be/p0iPpPyebUw?t=517 Any advice please?

Actually a very good idea, thanks. Although I couldn't afford to back up everything as there's just too much but I could take the essentials. Other than building another array, would you have any recommendation on accessing the data? I have a desktop PC that I could add an expansion card to, maybe dual boot with a Linux distribution to access the data?

Is there then a better way to access my data while I wait for the PCBs to sent? I mean without mounting disk individually in read-only from the cli? Thanks

If I understand, if even 1 byte of data is written the I can forget using the parity drive to recover in the future? Is there a way to start the array in Read-Only mode?

Here's an update. I tested each previously working disk one by one and they are all ok (I have left out the parity dirive) Thanks bjp999. Of the 7 fried disks, one is working without doing anything. I mentioned previously that I swapped a PCB from a spare equivalent disk to a fried disk but didn't connect it to UNRAID and subsequently swapped it back as it were before, therefore no change. Thanks johnathanm. After finding nothing in Europe, I contacted donordrives again and I'm waiting for info but I'll order 2 PCBs and swap these myself changing the BIOS ROM too. Now could someone look over my plan on how to continue please? This may seem optimistic but here goes. I'd like to be able to access my data before putting the (hopefully) recovered disks back in the array. I will go on the assumption that I am able to recover 5 of the remaining fried disks. That leaves one that could be rebuilt using my "old" parity drive. Ignoring the Cache and Parity drives for the moment, I have 9 working drives with my data. Would it be reasonable to start the array with these 9 drives, leaving out the parity drive for later and not writing anything to the array in the hope of rebuilding as it was before if I can indeed repair the fried disks? Even better, could I do the above but add a new disk for new data, being careful that anything new is written to this disk only and when the times comes to add the 5 "repaired" disks, I can remove the new disk and add the old parity drive and it would be as it was before? I'm aware that in the meantime I'd be unprotected of any subsequent disk failures due to no parity. I hope I don't misunderstand completely how Unraid works and thanks for any input.

Yes. Leave parity out. Do you know which disk was parity? Parity is not a mountable disk since it has no filesystem, but it is also possible that one or more data disks would also be unmountable due to filesystem corruption, so if you already know which disk is parity it would simplify things. Yes I do, luckily I had labelled all disks and took screenshots of the "Main" page. On another note, does anyone know of a similar company in Europe as donordrives quoted me $60 dollars for diagnostics which is fair but $55 per disk to be shipped back to me in Switzerland? Thanks for your help so far guys.

Not entirely clear what you mean by your "proper array". Since you have too many failed disks, parity can't help, so in a sense you no longer have your "proper array". You just have a bunch of drives, each with their own files, that are no longer related by parity. Some of the drives are still good, some are bad and maybe unreadable. Whatever you wind up with as far as getting new drives, getting files from the failed drives, and including your still good drives with their files, will become your array. I would definitely follow bjp999 advice. Work with one disk at a time. Maybe the part you are asking about is how to reconfigure your array as needed as you proceed. Do you know how to use Tools - New Config? Or you can just use the other method mentioned by bjp999, resetting disk.cfg and deleting super.dat each time you need to change, which is effectively what New Config does. You're quite correct that I no longer have a "proper" array. I just meant to say that, following bjp999's advice and checking the disks one by one and then putting these all together into what would be my new array. I sent an email to www.donordrives.com, I'll see what they advise. Let's imagine that all but one of the dead drives are repairable (surely too optimistic), then parity would then do it's job and I wouldn't have lost anything. But am I correct in saying that at no time should I connect the current parity drive before having all (but one) HDDs back in the server?

The link you posted is about scavenging the heads from compatible models, it's not about the PCB matching and whether or not chips must be moved or reprogrammed from the original to replacement PCB to get your data back. I STRONGLY advise you to call them and consult on your exact situation before you accidentally make it much worse. Keep in mind the best chance of getting data back relies on NOT modifying any of the data on any of the drives. You can use the parity disk to replace any single data drive, but as soon as 2 or more drives is compromised, you lose the data on both those drives. I'll definitely contact them and see what they advise, I'm just thinking ahead, probably too far I guess, about copying my data of these drives and the best way to do that.

YES Good to know, thanks. So as my HDDs are indeed dead and if I'm lucky and manage to buy replacement controllers and even luckier that they work, I'll need to get the data off them. Does what I wrote above make sense? I could add the new 4TB drive with copied data back to my proper array at a later date and continue to do the same.

So the controllers definitely got fried https://www.dropbox.com/s/0ccsdor8nkbxpbs/20170206_184035.jpg?dl=0 After reading some information on the link you posted I thought I'd try to swap over a controller. 3 of the dead disks are WD 2.0TB One model is from Dec 2010 which is within 3 months of the spare disk I have, this is said to be important http://www.donordrives.com/blog/matching-guide#wd The Model numbers match. Made in the same country. It actually spun up and OSX asked me to initialise but I ejected. Although there was definitely a slight grinding/clicking noise so if it was ok in UNRAID I'd want to get my data off asap. Obviously my ideal situation would be getting as much of my data back as I can. I bought a 4TB disk today, would it be a good idea to follow what was said here by bjp999? Back up my config folder on your desktop computer, so you have the original should you need it. Copy the disk.cfg file from a fresh unRAID .zip file (or I've attached one for convenience) into the config directory on the flash. And delete super.dat from same folder. So config will be as before but with a fresh disk.cfg and no super.dat. (You'll have original copies of both of these should you need them). Boot. unRAID should come up with an empty array. Assign the one disk to disk1 slot (note parity is at the top, so this will be the second dropdown! (DO NOT ASSIGN ANYTHING TO THE PARITY SLOT!) Start the array. I mean to say start with the new 4TB and the 2TB with the borrowed controller (Does UNRAID start without a parity drive?) If this is successful then copy the data over from the 2TB to the 4TB. If this works then I would be willing to order the other HDD chip/controllers from the site you mentioned, damn it would be amazing to be able to recover a lot if not all of what I lost

Thanks a lot for your advise, you're absolutely right, I've been at this for hours today so I'll take a look tomorrow evening with a clearer head.

I know specialist companies exist but I couldn't afford that. I have one or two disks of the same model laying around, does anyone know what are the chances of swapping the HDD controller from these and getting something working again?

I've just finished checking via the USB enclosure and no disk even spins up anymore. By a new config, do you mean just unassigning the dead disks? No I don't have a backup of the disks :'(

Going to leave your actual question to others here, but I will go and say that if you happen to have any power splitters to always plug the female end into the male end prior to installing and make sure that the wire colors line up with each other. I have seen in the past some splitters where an end was on upside down which would easily cause this issue. Side note: Always hang onto an old small drive that you're never going to use to test out backplanes.... I did use a Molex splitter as the cables from the PSU were not long enough, I've already taken out the IcyBox the killed my disks so I can't check exactly how it was connected but the colours line up correctly on the splitter. Although what you say makes sense, otherwise I don't know how 7 disks would suddenly die. Damn :'(

So here goes. I could explain the long process I've gone through upgrading my server's hardware (Mobo, CPU, RAM, PSU) I thought that taking everything out the server caused the initial problems I had, maybe a bad connection to one of the 4 IcyBoxes I already had. http://www.raidsonic.de/products/internal_cases/backplanes/index_en.php?we_objectID=1152 It seems that somehow the IcyBox killed 5 disks then another 2 disks when I was swapping things around to find where the problem was coming from. I'm still in the process of testing these disks but of the 3 I've plugged into a (new) USB harddrive enclosure into my Mac, none are seen at all, whereas when I connected 2 of the non missing disks OSX asked to initialise the disks, which of course I didn't, only ejected it. I had a total of 17 disks before this issue. https://www.dropbox.com/s/w35u75w1ak5qr4g/UNRAID-disks.png?dl=0 I only have one parity disk but even with 2 I know the data loss would have still been huge. 15x Data HDDs (4x4TB & 11x2TB) 1x Cache HDDs at 500GB So my question is, how can I start unraid without causing any more data loss? Is it simply a question of starting and unticking "correct Parity errors" ? Thanks

Thanks for all these userful docker containers, 90% of mine are from you guys. I know this is not a question related specifically to this container (as it installs and works without any visible problems) but could someone please point me in the right direction for documentation in setting kodi up once installed. I mean I've used Kodi for years but always with a GUI so setup that way is simple and something I've done many times. This is what I've tried so far. Added a mediasources.xml with this format <mediasources> <network> <location id="0">smb://myusername:mypassword@myserver/Movies</location> <location id="1">smb://myusername:mypassword@myserver/TV Series</location> <location id="2">smb://myusername:mypassword@myserver/Music</location> </network> </mediasources> I've also added a sources.xml with this format <sources> <programs> <default pathversion="1"></default> </programs> <video> <default pathversion="1"></default> <source> <name>TV Series</name> <path pathversion="1">smb://10.0.0.50/TV Series/</path> <allowsharing>true</allowsharing> </source> I've then connected (successfully) with YATSE app from my android and send the "update video" command but no updates to the library occur. Any advice is welcome. Thanks