stealth82

I guess I can give it a try. I noticed your docker before but I will not be able to cover the other cases: audio-cd ripping, data-dvd .iso ripping etc

I guess this is still an open issue I read the whole thread, experienced same things, MakeMKV not working, unraid (6.1.6) going completely unresponsive (no webGUI, no ssh). I had to hard reset the server to get everything back on its feet I'm using a SATA BD-ROM and I thought the BD-ROM was the easy part in all this virtualization journey At the moment I have no other PC in the house that can rip my discs, as I ditched my old HTPC. Should I hold my breath for a solution or it's better I bring back the HTPC? I've been able to play movies with AnyDVD-HD installed though.

Really...

I also found out about this but I'm not sure if it can be solved... it's a flag mismatch IRQ error. Basically 2 devices trying to use the same IRQ because they one of them - or both? - is not properly supporting PCI2.3 INTx disable or something like that... http://marc.info/?l=kvm&m=138939395523823&w=2

Sorry for the confusion. I just found out what my problem was... It worked at first but then after more toying around it stopped and I couldn't get it to work anymore. That was before I tried to add the sound card - physically I mean, by taking down the server and everything... then I thought the problem was the coexistence. What I didn't realize is that I had reattached my monitor to the PCI-E gpu rather than the mobo gpu. So the server booted up with the mobo setting the PCI-E gpu as primary video card... What I just discovered is that it's not just a matter of having at least 2 video cards. If I don't take care of forcing the integrated GPU as primary from the BIOS - mine was set to auto, that's why where the monitor cable was attached made the difference - the screen would remain black. I investigated more when I realized there were more things written in the syslog than the vm log. In the syslog I found this line: vfio-pci 0000:01:00.0: Invalid ROM contents That ultimately led me to the source of the problem and solution. I have both SeaBIOS and OMVF (although I didn't test the corruption thing as I wrote previously but as I was suggested I would wait for unRAID 6.2) working now!

I don't want to hijack the thread but that is the same I have experienced - with Windows 10 as well - and I reported in this post I would also add that I'm still unable to get my gpu to boot. All I get is black screen no matter what combination I'm suggested. All this seems more a work of luck than anything... I 'm testing a GTX 750 Ti and it's the same, before I thought it was my GTS 450 to be too old for this stuff. Now I don't know what to do, whether to keep trying or drop virtualization till better times come.... Forget the last point. I just found out what the problem was.

I can definitively report that the sound card is working but I can't get the gpu to work at all. I tried all possible choices as listed in the wiki but all I get is a black screen. I guess I have to buy a newer gpu... that's sad.

OK, I did some more tests... Point 1 Any hardware change I make triggers some sort of corruption... the BIOS keeps on rebooting and the log prints this any time it does it: qemuAgentNotifyEvent:1244 : Received unexpected event 3 In other words it never gets to start Windows. I don't know if this is a defect of the procedure I followed and I should start from a clean disk but this is strange... but at the moment I can't make any hardware modification without incurring into the problem. Point 2 The error given when I tried to add the sound card is triggered if there's also the NVIDIA High Definition Audio - that of the gpu - defined. If I remove it then no error and the VM starts. What's with that?

I think it worked without the PCIe bridge now. Sorry but I'm quite new to this and my original VM was with SEABIOS so I created a new OVMF config, but same vdisk1, to match your instructions. I followed a guide to convert Windows from MBR to UEFI and tried again. This time I experience some sort of UEFI corruption as I tried to add the hostdev tag after video but before another USB thing... The screen remained black... I removed the sound card setting again and had to go through the reconfiguration of UEFI.. I don't know... Now should be the turn of the video card but I'm worried it won't be easy. Anyway thanks, I was able to install the Xonar drivers and have the SO see the card. Victory!

Thanks for the tip, and I added what you said to the configuration, but the VM refuses to start now: Here's the log: 2015-12-10T09:10:58.605047Z qemu-system-x86_64: -device vfio-pci,host=04:02.0,id=hostdev2,bus=pci.0,addr=0x8: vfio: Error: Failed to setup INTx fd: Device or resource busy 2015-12-10T09:10:58.605463Z qemu-system-x86_64: -device vfio-pci,host=04:02.0,id=hostdev2,bus=pci.0,addr=0x8: Device initialization failed 2015-12-10T09:10:58.605486Z qemu-system-x86_64: -device vfio-pci,host=04:02.0,id=hostdev2,bus=pci.0,addr=0x8: Device 'vfio-pci' could not be initialized

I'm sorry in advance for the probable dumb request but I couldn't find much info in the wiki or here. I just upgraded unRAID to make it VT-d capable and wanted to pass through my NVIDIA GTS 450 and Asus Xonar Sound Card. I struggled a little with the gpu but with the explicit rom file it seems to work now. As for the sound card I can't selected from the GUI, it's not listed, but I guess I can work some magic through the editing of the XML file, just as I did with the GPU. Here are my PCI devices: 00:00.0 Host bridge: Intel Corporation Xeon E3-1200 v2/3rd Gen Core processor DRAM Controller (rev 09) 00:01.0 PCI bridge: Intel Corporation Xeon E3-1200 v2/3rd Gen Core processor PCI Express Root Port (rev 09) 00:02.0 Display controller: Intel Corporation Xeon E3-1200 v2/3rd Gen Core processor Graphics Controller (rev 09) 00:14.0 USB controller: Intel Corporation 7 Series/C210 Series Chipset Family USB xHCI Host Controller (rev 04) 00:16.0 Communication controller: Intel Corporation 7 Series/C210 Series Chipset Family MEI Controller #1 (rev 04) 00:19.0 Ethernet controller: Intel Corporation 82579V Gigabit Network Connection (rev 04) 00:1a.0 USB controller: Intel Corporation 7 Series/C210 Series Chipset Family USB Enhanced Host Controller #2 (rev 04) 00:1c.0 PCI bridge: Intel Corporation 7 Series/C210 Series Chipset Family PCI Express Root Port 1 (rev c4) 00:1c.7 PCI bridge: Intel Corporation 7 Series/C210 Series Chipset Family PCI Express Root Port 8 (rev c4) 00:1d.0 USB controller: Intel Corporation 7 Series/C210 Series Chipset Family USB Enhanced Host Controller #1 (rev 04) 00:1f.0 ISA bridge: Intel Corporation Z77 Express Chipset LPC Controller (rev 04) 00:1f.2 SATA controller: Intel Corporation 7 Series/C210 Series Chipset Family 6-port SATA Controller [AHCI mode] (rev 04) 00:1f.3 SMBus: Intel Corporation 7 Series/C210 Series Chipset Family SMBus Controller (rev 04) 01:00.0 VGA compatible controller: NVIDIA Corporation GF116 [GeForce GTS 450 Rev. 2] (rev a1) 01:00.1 Audio device: NVIDIA Corporation GF116 High Definition Audio Controller (rev a1) 02:00.0 RAID bus controller: Marvell Technology Group Ltd. MV64460/64461/64462 System Controller, Revision B (rev 01) 03:00.0 PCI bridge: Integrated Technology Express, Inc. Device 8892 (rev 30) 04:02.0 Multimedia audio controller: C-Media Electronics Inc CMI8788 [Oxygen HD Audio] Here the IOMMU groups /sys/kernel/iommu_groups/0/devices/0000:00:00.0 /sys/kernel/iommu_groups/1/devices/0000:00:01.0 /sys/kernel/iommu_groups/1/devices/0000:01:00.0 /sys/kernel/iommu_groups/1/devices/0000:01:00.1 /sys/kernel/iommu_groups/2/devices/0000:00:02.0 /sys/kernel/iommu_groups/3/devices/0000:00:14.0 /sys/kernel/iommu_groups/4/devices/0000:00:16.0 /sys/kernel/iommu_groups/5/devices/0000:00:19.0 /sys/kernel/iommu_groups/6/devices/0000:00:1a.0 /sys/kernel/iommu_groups/7/devices/0000:00:1c.0 /sys/kernel/iommu_groups/8/devices/0000:00:1c.7 /sys/kernel/iommu_groups/9/devices/0000:00:1d.0 /sys/kernel/iommu_groups/10/devices/0000:00:1f.0 /sys/kernel/iommu_groups/10/devices/0000:00:1f.2 /sys/kernel/iommu_groups/10/devices/0000:00:1f.3 /sys/kernel/iommu_groups/11/devices/0000:02:00.0 /sys/kernel/iommu_groups/12/devices/0000:03:00.0 /sys/kernel/iommu_groups/12/devices/0000:04:02.0 Can anyone guide me?

Did you delete the file parity-checks.log ? I did. I even restarted the server, renamed the parity-checks.log, installed the patch from command line but no parity-checks.log gets created.

System notifications are indeed on. Just the "store to flash" was off. I enabled it but still no history button... what am I doing wrong?

I did as described here - actually installed the 2015.12.04 patch - but even after 20 mins the log didn't recreate by itself. I decided to create manually but no history button is visible nor is the last parity sync duration time. Should I reboot the server?

Well, I don't know how to intepret this but... Inspired by this thread, I just gave a couple of more tries to the issue. I ran a parity sync without corrections and it finished just a few minutes ago. The colums reads/writes at the end read 1883 errors but apart from that no sync errors?!? How should I intepret the 0 sync errors count? I don't know. Anyway I'm burying all this. A new parity disk is running the array just now and the sync is in progress. tower-diagnostics-20151206-1534.zip

Something is not right. I downloaded the docker and although nginx is advertised apache2 was deployed... LOL The nginx.xml files looks like this: <?xml version="1.0" encoding="utf-8"?> <Container> <Beta>False</Beta> <Category>Network:Web Network:Proxy</Category> <Date>2015-12-05</Date> <Name>Nginx</Name> <Support>http://lime-technology.com/forum/index.php?topic=44481.0</Support> <Overview>is a web server with a strong focus on high concurrency, performance and low memory usage. It can also act as a reverse proxy server for HTTP, HTTPS, SMTP, POP3, and IMAP protocols, as well as a load balancer and an HTTP cache.</Overview> <Changes> [center][img width='300px' src='https://raw.githubusercontent.com/linuxserver/docker-templates/master/linuxserver.io/img/linuxserver_small.png'][/center] [center][font size=4]Nginx Change Log[/font][/center] [b]06.12.2015:[/b] Initial Release</Changes> <Description>is a web server with a strong focus on high concurrency, performance and low memory usage. It can also act as a reverse proxy server for HTTP, HTTPS, SMTP, POP3, and IMAP protocols, as well as a load balancer and an HTTP cache..[br] [b][u][span style='color: #E80000;']Configuration[/span][/u][/b][br] [b]80[/b] Standard HTTP Port [br] [b]443[/b] Standard HTTPS Port [br] [b]/config[/b]Storing Configuration and the www folder[br] </Description> <Project>https://www.nginx.com/</Project> <Registry>https://registry.hub.docker.com/u/linuxserver/nginx/</Registry> <Repository>linuxserver/apache</Repository> <BindTime>true</BindTime> <Privileged>false</Privileged> <Environment> <Variable> <Name>PUID</Name> <Value>99</Value> </Variable> <Variable> <Name>PGID</Name> <Value>100</Value> </Variable> </Environment> <Networking> <Mode>bridge</Mode> <Publish> <Port> <HostPort>80</HostPort> <ContainerPort>80</ContainerPort> <Protocol>tcp</Protocol> </Port> <Port> <HostPort>443</HostPort> <ContainerPort>443</ContainerPort> <Protocol>tcp</Protocol> </Port> </Publish> </Networking> <Data> <Volume> <HostDir>/mnt/user/appdata/nginx</HostDir> <ContainerDir>/config</ContainerDir> <Mode>rw</Mode> </Volume> </Data> <Version></Version> <WebUI>http://[iP]:[PORT:80]/</WebUI> <Banner>https://raw.githubusercontent.com/linuxserver/docker-templates/master/linuxserver.io/img/nginx-banner.png</Banner> <Icon>https://raw.githubusercontent.com/linuxserver/docker-templates/master/linuxserver.io/img/nginx-icon.png</Icon> <ExtraParams></ExtraParams> </Container> I think the wrong repository is listed

btrfs

I can but my fear is that some of the rebuilt data is corrupt since it's been rebuilt by a failing parity drive with unreadable sectors.

I don't know if it's related but SMART is telling me the parity disk pending sector count is increasing (184 now). The parity disk is spun off. I wonder how it can know that considered it's off... I'm scrubbing the rebuilt disk - I don't know if it is related.

I attached a new diagnostic file. I'd really love to know if there's any way to track down whether the rebuilt has been affected - I think it has - and on what data, if any, the bad sectors "landed". I say if any because the rebuilt disk is 75% full and the errors started appearing in the last 25% of the rebuilding process I think. I don't know if this might mean that maybe there were not files there but just empty space to rebuild. Any insight? P.S. Why is unRAID considering the rebuilt disk OK considered it knows there were read errors from the parity? tower-diagnostics-20151203-1024.zip

Unfortunately, I don't think so. The parity drive has always been directly attached to the motherboard with a cable I don't have reasons to doubts. The connection was and is solid. That drive, though, had given me that very same error in the past. After that I put it under observation, ran a couple of preclears on it and seemed fine (I think some under a 100 sectors reallocated but no more growing pending sectors). I guess the best thing to do would have been to trash it rather than risk it... but i didn't have any disk to spare at the time. Is there any way I can know what sectors have affected the rebuilt drive now. What I would like to do if I can isolate the problem is to replace the parity drive with a new disk but what you are saying makes me think I could try to rebuild again from the "faulty" parity drive. I really don't know what to do now.

OK, I think the worst case scenario has just occurred. I wanted to take down the disk but since I bought a sata cage and rewired everything I wanted to give the disk another try. The disk came back online and it reported no errors. I guess a wire really got loose - it wasn't the disk, I can't give myself another explanation. Anyway I put it back into the array and unRAID started rebuilding it. As it was some hours in the rebuilding process the parity drive started throwing errors (843 in the errors column) 187 Reported uncorrect 0x0032 017 017 000 Old age Always Never 83 197 Current pending sector 0x0012 100 099 000 Old age Always Never 128 198 Offline uncorrectable 0x0010 100 099 000 Old age Offline Never 128 The disk that is getting rebuilt is toasted - data can't be trusted, I'm toasted. Am I right? :'(

Are you sure? If it reads "A mandatory SMART command failed: exiting. To continue, add one or more '-T permissive' options." is it a sign that looks OK? WDC_WD20EARS-00MVWB0_WD-WMAZA0747093-20151130-1731.txt smartctl 6.2 2013-07-26 r3841 [x86_64-linux-4.1.13-unRAID] (local build) Copyright (C) 2002-13, Bruce Allen, Christian Franke, www.smartmontools.org === START OF INFORMATION SECTION === Vendor: /1:0:1:0 Product: User Capacity: 600,332,565,813,390,450 bytes [600 PB] Logical block size: 774843950 bytes Physical block size: 1549687900 bytes Lowest aligned LBA: 14896 scsiModePageOffset: response length too short, resp_len=47 offset=50 bd_len=46 scsiModePageOffset: response length too short, resp_len=47 offset=50 bd_len=46 >> Terminate command early due to bad response to IEC mode page A mandatory SMART command failed: exiting. To continue, add one or more '-T permissive' options.

Apologies. I attached the right zip file now.

Hello, I think this could be my first disk dying of old age but I wanted to have some double confirmation by experts here. Today I was manually copying through mc data from my cache drive to /mnt/disk2 when promptly a notification on my iPhone came in. It was unRAID telling me something was wrong... Now disk2 is emulated and I tried to check SMART results to see what happened. Point is... it says the disk is unavailable and it can be spun up for diagnostic. I checked the syslog, which I attached, and looked up these 2 errors that I saw: DRDY ERR ICRC ABRT They should be, respectively: Drive media issue #1: These are almost always associated with bad sectors. Drive media issue #2: a pretty good indicator of a poor quality SATA cable Now the last one made me think. Some weeks ago I bought a Supermicro AOC-SASLP-MV8 controller and 2 Mini SAS to 4-SATA SFF-8087 Multi-Lane Forward Breakout Internal Cables. Till some moments ago I had no issues whatsoever though. Is it possible that just one sub-cable out of 4 is bad? Should I be worried about it or it could be that the cause is the disk's old age? I say old age because it shouldered 4y, 6m, 9d, 14h of service so far (I read that stat from its sibling, I have 2 disks bought in the same period). A new 4TB drive is on the way now and I will have to go for a parity swap procedure when it arrives. Are there any suggestions before getting into that or I should just give up on the old disk? tower-diagnostics-20151130-1731.zip