JustinChase

but parity is valid, according to the server Does that mean they were "corrected". I don't really want to start another check right now, at least not before asking about it here, in case there is something I need to do/check first. it also took many hours longer than normal, which leads me to believe it did 'correct' during the process. I replaced my parity drive and array drives with 12TB drives last month, and created a new config, telling it parity was valid (since I believed it was). Maybe this is just the result of that, but I wanted to ask before doing anything else.

I deleted all data, and am just rebuiling now, while I use the server, but am not moving files around this time. We'll see how it goes. If any issues, I'll try the export function next time. I read all the descriptions of all the buttons, and there was no obvious 'rebuild' function I could decipher. thanks again for the help.

Ah, that helps; thank you! doesn't make as much sense as being in the log folder on the plugin page, but now I know. it actually shows tons of warnings and errors about SHA256 mismatches and/or missing files. I may have been doing some moving of files when the process was originally running, so maybe that's the issue. It took about a day to run, and I'm not sure when I can not use the server for that long to run it again, but I'll try to do that soon, and have it re-evaluate all files during that time and see if errors continue. I just installed a brand new parity drive and system drive, both of which passed the preclear, so I'd be surprised if there was bit rot happening already. I guess we'll see soon enough. thanks again for your help.

I couldn't find any "log tab", but there is a "log files" folder on the plugin page. The only thing in that folder is a file called duplicate_file_hashes.txt That only lists all the duplicate hashes it found, but nothing about any errors, or help figuring out which file triggered the error.

If I can't find out which file(s) have gone bad, I'm not sure this really helps. It only causes me stress knowing something is 'broke'. Is there a way to know what's not right? Or should I just uninstall the plugin to not have the stress of knowing there is an un-fixable problem with my data?

I have the Dynamix Active Streams plugin installed, and when I watch a movie on the laptop, it does show the stream on the plugin page, but not on the dashboard. The dashboard shows 0 streams next to every share, no matter if I'm streaming or not. I'm not sure if the dashboard uses the plugin to show streams, or why it's not showing any active streams on the dashboard, but it would be nice if it did show streams on the dashboard, and it'd be awesome if one could click the non-zero number of streams here (once they show up) to bring up the list of streams it's identified.

I got a server popup yesterday with the following error... found 1 file with sha256 hash key mismatch no more information, and I can't find any errors or more information in the plugin page. how do I know what the issue is and how to fix it? thanks

I recently purchased two 12TB drives to upgrade my array. 1 is now my parity drive, and the other is now an array drive. I currently only have 10TB of data, so the new 12TB drive will hold everything, for a while longer. I'm not sure if I should remove all the other drives, and just use these 2 drives for the array, or leave the other drive(s) in for some reason. I can always add drives back if/when I run out of space. I'm wanting to move the server parts to a much smaller box than what everything is in today, and I need to get down to 3 or fewer (3.5") drives, to fit the case I already have and wish to use. Is there any benefit to keeping a 3rd drive in the array, or is it "just as good" to shrink to only the 2 new drives (parity and array) bought on the same day (same brand, type, etc). If I do keep another drive in there, which of these should I keep? (I'm leaning to the 7200 RPM that is only 2 years old) Disk 1 - Model family:Seagate Desktop HDD.15 Device model:ST4000DM000-1F2168 Rotation rate:5900 rpm Power on hours 50578 (5y, 9m, 6d, 10h) showing no errors under attributes Disk 2 - Model family:Seagate Desktop HDD.15 Device model:ST4000DM000-1F2168 Rotation rate:5900 rpm Power on hours 54367 (6y, 2m, 14d, 7h) with a Reallocated sector count = 40 and Reported uncorrect = 11 (errors?) highlighted in yellow Disk 3 - Model family:Seagate Desktop HDD.15 Device model:ST4000DM000-1F2168 Rotation rate:5900 rpm Power on hours 46364 (5y, 3m, 14d, 20h) with a Command timeout = 10 11 11 and UDMA CRC error count = 4546 (errors?) highlighted in yellow Disk 4 - Model family:HGST Deskstar NAS Device model:HGST HDN724040ALE640 Rotation rate:7200 rpm Power on hours 18951 (2y, 1m, 30d, 15h) showing no errors under attributes Finally, should I even keep the disks with over 5 years and errors, or empty and trash them? What about the 5 year old drive with no errors? Worth keeping as a backup for something else? I appreciate any feedback or suggestions. 18951 (2y, 1m, 30d, 15h)

That makes sense, thanks for letting me know. Could you please add this to the first post, because I'll forget in a year or 2 when I try to do this again, and I always look to the first post for instructions, which will save me having to search the thread to find this tidbit. Thanks again, the script works great (once I get it to run).

I'm having the same issue today. I have this script on my flash drive, but get permissions denied error also. root@media:/boot/scripts# unRAIDFindDuplicates.sh -v -bash: ./unRAIDFindDuplicates.sh: Permission denied What am I doing wrong, how to fix?

I am 65% of the way through the parity swap procedure, and when I went to the Array Operation tab to see the progress I had this error on that screen... Fatal error: Uncaught Error: Call to undefined function parse_file() in /usr/local/emhttp/plugins/dynamix.s3.sleep/Sleep.php:18 Stack trace: #0 /usr/local/emhttp/plugins/dynamix/include/DefaultPageLayout.php(520) : eval()'d code(549): include() #1 /usr/local/emhttp/plugins/dynamix/include/DefaultPageLayout.php(520): eval() #2 /usr/local/emhttp/plugins/dynamix/template.php(60): require_once('/usr/local/emht...') #3 {main} thrown in /usr/local/emhttp/plugins/dynamix.s3.sleep/Sleep.php on line 18 I had just installed the preclear plugin through the community applications plugin, but have not started any preclear, or done anything else since installing the plugin. I'm not sure this is a sleep plugin problem, I'm only reporting here because it's the only thing mentioned in the error.

I did not know about that, thanks for sharing. I'm more worried about the existing disk failing than the new drive failing in the next 5-10 days. so, I'm thinking I'll install the new 12TB drive in the parity slot, old parity in failing disk 3 slot, disconnect disk 3, and start the procedure without preclearing the new drive. While at the same time, preclearing the other new 12TB drive, so that hopefully the preclear is done not long after the data is all correctly on the new parity and array drives. Then i can swap the parity drive for the precleared one, then preclear the old/new parity drive. More work for the server, more risk to my data I suppose, but a horrible idea?

In order to get to using two 12 TB drives, one as parity, and one as array, I believe I have to start by upgrading the parity drive, since I cannot have an array drive any larger than parity, which is currently 4TB. When upgrading the parity from 4TB to 12TB, I believe it will use the array drives to rebuild parity, so if the 3TB drive fails during this time, I believe I've lost all that data for good (except for using the old 4TB parity drive). Am I mistaken, is there some way to get to the 12TB drives without the 3TB drive being a liability, and is so, how?

I have a 4TB parity drive, three 4TB array drives, and this malfunctioning 3TB drive. They are all of very similar age, and I'd like to retire them all, sooner than later. I've ordered two 12 TB external drives (WD - Easystore 12TB External USB 3.0 Hard Drive - Black) and want to move all data to the 12 TB drive, with 12 TB parity. I don't want to worry when rebuilding parity onto the new drive, that the 3TB drive fails during the process. I want to get the data off the drive before anything else. Any ideas if there might be a solution to speed it up, or I just need to be patient?

Thanks, I just ordered the new drive to replace it, but my current concern is how to get the data off more quickly than at 2.5MB/sec. Any idea if moving to other controller, next to the disk I'm moving files to, will speed up the data movement?

I've started seeing some errors on Disk 3, so I've decided to move all the files from that drive to my other drives, and to eliminate that drive, and do with fewer drives in the system. I'm currently seeing about 2MB/s transfer speed from that disk, which means it will take about a week to move 1TB off the drive. The drive in question is on a separate controller from the other drives in my system, and I'm wondering if I can move it to the same controller as the disk I'm trying to copy to to improve the transfer speed, but I'm not sure how that will affect the array if I move the position of 2 drives. Any guidance, or suggestions to speed up the drive would be much appreciated. I'm not sure what log files, or anything that I can provide to help, but will happily upload whatever anyone needs to see. Thanks in advance for any help. ChristopherBaber_20200402_102340.tar.gz media-diagnostics-20200402-1043.zip

Sorry, no @renk1. I never was able to get it working, but also, I have not tried since shortly after I wrote that, so it's very possible it will work now. If you end up being successful, I'd love to hear about it, as I'd still like to get this working someday.

I would sure like some help getting this working again.

I've had that drive in the machine for over a year. I've gotten this message a few times in the last week. i suppose that could be a random kernel issue, as you say, but I wonder if there's any way to actually troubleshoot it, vs assume it's a kinda known issue and ignore it.

That doesn't sound good. How might I try to identify and then fix these issues? I was looking at the SSD trim application, and I think it was set to disabled. I just changed it to daily at 8:50 after posting, as a test. I just looked at the log and see these as the last items in there... May 18 08:47:12 media apcupsd[26964]: apcupsd 3.14.14 (31 May 2016) slackware startup succeeded May 18 08:47:12 media apcupsd[26964]: NIS server startup succeeded May 18 08:50:07 media kernel: DMAR: DRHD: handling fault status reg 3 May 18 08:50:07 media kernel: DMAR: [DMA Read] Request device [02:00.0] fault addr fd1ff000 [fault reason 06] PTE Read access is not set May 18 08:50:07 media kernel: DMAR: DRHD: handling fault status reg 3 May 18 08:50:07 media kernel: DMAR: [DMA Read] Request device [02:00.0] fault addr ffcae000 [fault reason 06] PTE Read access is not set May 18 08:50:07 media kernel: DMAR: DRHD: handling fault status reg 3 May 18 08:50:07 media kernel: DMAR: [DMA Read] Request device [02:00.0] fault addr fd1ff000 [fault reason 06] PTE Read access is not set May 18 08:50:07 media kernel: DMAR: DRHD: handling fault status reg 3 May 18 08:50:12 media kernel: dmar_fault: 242 callbacks suppressed May 18 08:50:12 media kernel: DMAR: DRHD: handling fault status reg 3 May 18 08:50:12 media kernel: DMAR: [DMA Read] Request device [02:00.0] fault addr f0d0b000 [fault reason 06] PTE Read access is not set May 18 08:50:12 media kernel: DMAR: DRHD: handling fault status reg 3 May 18 08:50:12 media kernel: DMAR: [DMA Read] Request device [02:00.0] fault addr edd5e000 [fault reason 06] PTE Read access is not set May 18 08:50:12 media kernel: DMAR: DRHD: handling fault status reg 3 May 18 08:50:12 media kernel: DMAR: [DMA Read] Request device [02:00.0] fault addr edd33000 [fault reason 06] PTE Read access is not set May 18 08:50:12 media kernel: DMAR: DRHD: handling fault status reg 3 May 18 08:50:19 media kernel: dmar_fault: 467 callbacks suppressed May 18 08:50:19 media kernel: DMAR: DRHD: handling fault status reg 3 May 18 08:50:19 media kernel: DMAR: [DMA Read] Request device [02:00.0] fault addr f0412000 [fault reason 06] PTE Read access is not set May 18 08:50:19 media kernel: DMAR: DRHD: handling fault status reg 3 May 18 08:50:19 media kernel: DMAR: [DMA Read] Request device [02:00.0] fault addr fdde8000 [fault reason 06] PTE Read access is not set May 18 08:50:19 media kernel: DMAR: DRHD: handling fault status reg 3 May 18 08:50:19 media kernel: DMAR: [DMA Read] Request device [02:00.0] fault addr f0b0c000 [fault reason 06] PTE Read access is not set May 18 08:50:19 media kernel: DMAR: DRHD: handling fault status reg 3 May 18 08:50:24 media root: /etc/libvirt: 28 GiB (30063636480 bytes) trimmed on /dev/loop3 May 18 08:50:24 media root: /var/lib/docker: 12.4 GiB (13295656960 bytes) trimmed on /dev/loop2 May 18 08:50:24 media root: /mnt/cache: 400.4 GiB (429951348736 bytes) trimmed on /dev/nvme0n1p1 Is the drive going bad?

I have been passing through a USB controller for a year or more to my VM, to which I connect my keyboard, and occasionally plug in my phone to load music onto it. When I updated to RC .7 from the last beta, it stopped working. I updated to .8, still not working. I'm now running 6.7.0 and it still doesn't work. I saw there were some changes to how to pass through controllers and devices, but from what I've read, the method I use should still work. I've unselected the controller in the VM setup, booted to the VM, shut it down, and re-selected it, and that didn't get it working. How might I go about getting this working again? VM XML... <?xml version='1.0' encoding='UTF-8'?> <domain type='kvm' id='1'> <name>Server</name> <uuid>random-string</uuid> <description>Media Server</description> <metadata> <vmtemplate xmlns="unraid" name="Windows 10" icon="windows.png" os="windows10"/> </metadata> <memory unit='KiB'>16777216</memory> <currentMemory unit='KiB'>16777216</currentMemory> <memoryBacking> <nosharepages/> </memoryBacking> <vcpu placement='static'>2</vcpu> <cputune> <vcpupin vcpu='0' cpuset='2'/> <vcpupin vcpu='1' cpuset='3'/> </cputune> <resource> <partition>/machine</partition> </resource> <os> <type arch='x86_64' machine='pc-i440fx-2.11'>hvm</type> </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='2' 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='cdrom'> <driver name='qemu' type='raw'/> <source file='/mnt/user/backup/Programs/WindowsISOs/virtio-win-0.1.141.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> <disk type='file' device='disk'> <driver name='qemu' type='qcow2' cache='writeback'/> <source file='/mnt/cache/VMs/server.qcow2'/> <backingStore/> <target dev='hdc' bus='sata'/> <boot order='1'/> <alias name='sata0-0-2'/> <address type='drive' controller='0' bus='0' target='0' unit='2'/> </disk> <controller type='virtio-serial' index='0'> <alias name='virtio-serial0'/> <address type='pci' domain='0x0000' bus='0x00' slot='0x04' function='0x0'/> </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='0x03' function='0x0'/> </controller> <controller type='usb' index='0' model='qemu-xhci' ports='15'> <alias name='usb'/> <address type='pci' domain='0x0000' bus='0x00' slot='0x07' function='0x0'/> </controller> <interface type='bridge'> <mac address='52:54:00:bd:e0:72'/> <source bridge='br0'/> <target dev='vnet0'/> <model type='virtio'/> <alias name='net0'/> <address type='pci' domain='0x0000' bus='0x00' slot='0x02' function='0x0'/> </interface> <serial type='pty'> <source path='/dev/pts/0'/> <target type='isa-serial' port='0'> <model name='isa-serial'/> </target> <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-1-Server/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='mouse' bus='ps2'> <alias name='input0'/> </input> <input type='keyboard' bus='ps2'> <alias name='input1'/> </input> <hostdev mode='subsystem' type='pci' managed='yes' xvga='yes'> <driver name='vfio'/> <source> <address domain='0x0000' bus='0x01' slot='0x00' function='0x0'/> </source> <alias name='hostdev0'/> <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='0x01' slot='0x00' function='0x1'/> </source> <alias name='hostdev1'/> <address type='pci' domain='0x0000' bus='0x00' slot='0x06' function='0x0'/> </hostdev> <hostdev mode='subsystem' type='pci' managed='yes'> <driver name='vfio'/> <source> <address domain='0x0000' bus='0x0b' slot='0x00' function='0x0'/> </source> <alias name='hostdev2'/> <address type='pci' domain='0x0000' bus='0x00' slot='0x08' function='0x0'/> </hostdev> <memballoon model='none'/> </devices> <seclabel type='dynamic' model='dac' relabel='yes'> <label>+0:+100</label> <imagelabel>+0:+100</imagelabel> </seclabel> </domain> media-diagnostics-20190518-1250.zip

I've gotten this message emailed to me a few times over the last week. I really have no idea what it's trying to tell me (other than there's an issue) or where to go about trying to fix it. Any ideas what needs fixed? media-diagnostics-20190518-1250.zip

I have this in my syslinux.cfg file... label KVM with GUI/unRAID OS menu default kernel /bzimage append vfio-pci.ids=1b21:1142 intel_iommu=on pcie_acs_override=downstream,multifunction initrd=/bzroot,/bzroot-gui which worked great until about rc7, and now I cannot get my VM to recognize my USB keyboard, or any hard drives I connect to the USB port. Do these changes have anything to do with my new issue, or is it just coincidence and I need to look elsewhere for a solution to this new problem? if so, where might I look next? Thanks media-diagnostics-20190511-1957.zip

I upgraded to rc7, then 8, and now the final version. in all 3 versions, I've lost the USB controller in my VM. I un-selected the (other PCI devices) rebooted the VM, then stopped, and re-selected it, and it still isn't being recognized (I can't use my keyboard in the VM). I saw some mention about changing the way devices are handled, but I don't follow unraid closely enough to know if this is my problem, or something else. i've posted my diagnostics. i didn't see anything obvious in there, but maybe one of you is able to see what happened and point me to a solution. Thanks media-diagnostics-20190511-1957.zip

I have 2 4TB discs in my array (Disc2 and Disc3). I've moved all my movies to these 2 discs. When I check the size of all the movies and associated files in Windows Explorer, it reports they take 7.6 TB When I look at my array in unRAID, those discs show 3.97 and 3.93 full. I realize windows may not measure the same way as unRAID, but it seems I'm losing almost .4TB of space somehow. What am I missing? Why does unRAID not show as much free space as windows? I do use the recycle app, but it shows as empty, both in the app and in Putty/Midnight Commander. I'm confused.