statecowboy

Edited - I just remembered I did add this disk a while back and left it during pre clear. I have not in fact formatted it. Sorry for wasting your time. Thanks for the input.

Had one of my data disks suddenly show as "Unsupported or no file system". I rebooted the server to see if it cleared, but it did not. I have posted full diagnostics. Thanks for the help. someflix-unraid-diagnostics-20241207-2214.zip

Here you go. someflix-unraid-diagnostics-20240411-1004.zip

Had a fairly new (I think it's maybe a year or so old) drive throw an error. Before I go about replacing it, I was hoping someone with more experience in drive errors could lend some advice. Thanks someflix-unraid-smart-20240411-0930.zip

Well, this is embarassing, but you guys are right. I totally forgot I recently replaced (upsized) my parity drive. This drive was the old parity drive, and I must just not have reformatted it. I just ticked the "format" button down below the main drive page. Sorry about that.

Was warned by fix common problems that I had a disk with errors. The main page shows "Unmountable: Unsupported or no file system". Reading the suggested fix, because the disk had data on it, it recommended to seek assistance here, so here I am. I do have a replacement disk on standby should that be the case, but figured I would seek guidance here before tossing this drive. someflix-unraid-diagnostics-20231215-0832.zip

I am not sure what caused it, but I no longer have this issue. I suspect that it was some sort of bug in the Ubiquiti software that was triggering something. I took my 48 port switch and my pi-hole machine out of my network stack trying to eliminate possible causes, and one of those seems to have resolved it.

Follow up post. It's happened again. My server has become unresponsive. I had to reboot it to get it back, but it came back up. I've attached my diagnostics. I noticed on the startup screen I get the following error: modprobe: ERROR: could not insert 'nct6775': No such device So, this does appear to be either a system or hardware error, not a plex thing. Any ideas? someflix-unraid-diagnostics-20220628-2143.zip

I'm going to apologize in advanced for this being an obscure request for help. I'm really not sure where to start. A couple of weeks ago my plex server was unresponsive. After logging into unraid's management interface and pulling up the docker logs I got an error message that said something along the lines of "preferences.xml" could not be read. When I opened my appdata folder to check that file it was completely blank. I did have a backup from appdata backup/restore and managed to replace the blank file. Plex started back up just fine and I went on my merry way, for about a day until this happened again a couple of more times. During these instances I also noticed that my unraid machine was not reachable at times, almost like there was a network problem. A reboot usually corrects this issue. I've tried a few things. At first, I thought somehow my pihole instance (running separately on an ubuntu server) was screwed up and I was having DNS issues. So, I did a fresh install of pihole. Things seemed to be working great until last night when my plex server was unresponsive again. I also could not log into my unraid machine. One thing I tried differently last night was I bypassed one of my network switches thinking possibly it could be going bad (I run a unifi network and my server was going through a USW-48 switch). We will see if that somehow corrects the issue. I guess my main question here is, does anyone have any idea what could be causing my "preferences.xml" to wipe itself like this? It seems somehow connected to network issues either with my server or with my netowrk hardware or software. I suppose these all could be symptoms of failing hardware, but I'm unsure of what steps I can take to diagnose that.

Attached. And yes, my dockers live on an unassigned device set to R/W slave mode.

Hi everyone. Was wondering if someone could do a sanity check on my config. I've had some weird issues with my docker image filling up, and I believe this only happens when I leave krusader running for a long time. Probably worth noting, every time I start krusader I get a notification that I can't save bookmarks to the home/nobody location. I am wondering if this is resulting in tmp files being written elsewhere within the docker image.

Hi all, first off thanks, Ed ( @SpaceInvaderOne) for this awesome video and container. I've set up a Hackintosh before and I remember how much research and pain goes into getting these things running smoothly. You make it look easy. I've managed to get everything up and running just fine for the initial install and boot. However, I am having fits trying to pass through my RX 590 (AMD) GPU. Since I switch the graphics to the GPU I can't use VNC obviously. The problem is splashtop sees the machine booted up but hangs at the connecting screen. XML below: <?xml version='1.0' encoding='UTF-8'?> <domain type='kvm' id='18' xmlns:qemu='http://libvirt.org/schemas/domain/qemu/1.0'> <name>MacinaboxCatalina</name> <uuid>a32d305c-5ba6-4744-a959-a6b9138edabb</uuid> <description>MacOS Catalina</description> <metadata> <vmtemplate xmlns="unraid" name="MacOS" icon="/mnt/disks/VM/MacinaboxCatalina/icon/catalina.png" os="Catalina"/> </metadata> <memory unit='KiB'>8388608</memory> <currentMemory unit='KiB'>8388608</currentMemory> <memoryBacking> <nosharepages/> </memoryBacking> <vcpu placement='static'>8</vcpu> <cputune> <vcpupin vcpu='0' cpuset='1'/> <vcpupin vcpu='1' cpuset='21'/> <vcpupin vcpu='2' cpuset='2'/> <vcpupin vcpu='3' cpuset='22'/> <vcpupin vcpu='4' cpuset='3'/> <vcpupin vcpu='5' cpuset='23'/> <vcpupin vcpu='6' cpuset='4'/> <vcpupin vcpu='7' cpuset='24'/> </cputune> <resource> <partition>/machine</partition> </resource> <os> <type arch='x86_64' machine='pc-q35-3.1'>hvm</type> <loader readonly='yes' type='pflash'>/mnt/disks/VM/MacinaboxCatalina/ovmf/OVMF_CODE.fd</loader> <nvram>/mnt/disks/VM/MacinaboxCatalina/ovmf/OVMF_VARS.fd</nvram> </os> <features> <acpi/> <apic/> </features> <cpu mode='host-passthrough' check='none'/> <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='qcow2' cache='writeback'/> <source file='/mnt/disks/VM/MacinaboxCatalina/Clover.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> <disk type='file' device='disk'> <driver name='qemu' type='raw' cache='writeback'/> <source file='/mnt/disks/VM/MacinaboxCatalina/Catalina-install.img'/> <backingStore/> <target dev='hdd' bus='sata'/> <alias name='sata0-0-3'/> <address type='drive' controller='0' bus='0' target='0' unit='3'/> </disk> <disk type='file' device='disk'> <driver name='qemu' type='raw' cache='writeback'/> <source file='/mnt/disks/VM/MacinaboxCatalina/macos_disk.img'/> <backingStore/> <target dev='hde' bus='sata'/> <alias name='sata0-0-4'/> <address type='drive' controller='0' bus='0' target='0' unit='4'/> </disk> <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='pcie-root-port'> <model name='pcie-root-port'/> <target chassis='1' port='0x10'/> <alias name='pci.1'/> <address type='pci' domain='0x0000' bus='0x00' slot='0x02' function='0x0' multifunction='on'/> </controller> <controller type='pci' index='2' model='pcie-root-port'> <model name='pcie-root-port'/> <target chassis='2' port='0x11'/> <alias name='pci.2'/> <address type='pci' domain='0x0000' bus='0x00' slot='0x02' function='0x1'/> </controller> <controller type='pci' index='3' model='pcie-root-port'> <model name='pcie-root-port'/> <target chassis='3' port='0x12'/> <alias name='pci.3'/> <address type='pci' domain='0x0000' bus='0x00' slot='0x02' function='0x2'/> </controller> <controller type='pci' index='4' model='pcie-root-port'> <model name='pcie-root-port'/> <target chassis='4' port='0x13'/> <alias name='pci.4'/> <address type='pci' domain='0x0000' bus='0x00' slot='0x02' function='0x3'/> </controller> <controller type='virtio-serial' index='0'> <alias name='virtio-serial0'/> <address type='pci' domain='0x0000' bus='0x02' slot='0x00' function='0x0'/> </controller> <controller type='usb' index='0' model='ich9-ehci1'> <alias name='usb'/> <address type='pci' domain='0x0000' bus='0x00' slot='0x07' function='0x7'/> </controller> <controller type='usb' index='0' model='ich9-uhci1'> <alias name='usb'/> <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'> <alias name='usb'/> <master startport='2'/> <address type='pci' domain='0x0000' bus='0x00' slot='0x07' function='0x1'/> </controller> <controller type='usb' index='0' model='ich9-uhci3'> <alias name='usb'/> <master startport='4'/> <address type='pci' domain='0x0000' bus='0x00' slot='0x07' function='0x2'/> </controller> <interface type='bridge'> <mac address='52:54:00:a2:2a:b0'/> <source bridge='br0'/> <target dev='vnet0'/> <model type='e1000-82545em'/> <alias name='net0'/> <address type='pci' domain='0x0000' bus='0x01' slot='0x00' 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-18-MacinaboxCatalina/org.qemu.guest_agent.0'/> <target type='virtio' name='org.qemu.guest_agent.0' state='connected'/> <alias name='channel0'/> <address type='virtio-serial' controller='0' bus='0' port='1'/> </channel> <input type='tablet' bus='usb'> <alias name='input0'/> <address type='usb' bus='0' port='1'/> </input> <input type='mouse' bus='ps2'> <alias name='input1'/> </input> <input type='keyboard' bus='ps2'> <alias name='input2'/> </input> <hostdev mode='subsystem' type='pci' managed='yes'> <driver name='vfio'/> <source> <address domain='0x0000' bus='0x81' slot='0x00' function='0x0'/> </source> <alias name='hostdev0'/> <rom file='/mnt/disks/VM/Sapphire.RX590.8192.190426.rom'/> <address type='pci' domain='0x0000' bus='0x03' slot='0x00' function='0x0' multifunction='on'/> </hostdev> <hostdev mode='subsystem' type='pci' managed='yes'> <driver name='vfio'/> <source> <address domain='0x0000' bus='0x81' slot='0x00' function='0x1'/> </source> <alias name='hostdev1'/> <address type='pci' domain='0x0000' bus='0x03' slot='0x00' function='0x1'/> </hostdev> <memballoon model='none'/> </devices> <seclabel type='dynamic' model='dac' relabel='yes'> <label>+0:+100</label> <imagelabel>+0:+100</imagelabel> </seclabel> <qemu:commandline> <qemu:arg value='-usb'/> <qemu:arg value='-device'/> <qemu:arg value='usb-kbd,bus=usb-bus.0'/> <qemu:arg value='-device'/> <qemu:arg value='isa-applesmc,osk=OBSCURED'/> <qemu:arg value='-smbios'/> <qemu:arg value='type=2'/> <qemu:arg value='-cpu'/> <qemu:arg value='Penryn,kvm=on,vendor=GenuineIntel,+invtsc,vmware-cpuid-freq=on,+pcid,+ssse3,+sse4.2,+popcnt,+avx,+aes,+xsave,+xsaveopt,check'/> </qemu:commandline> </domain> Logs from VM: -no-hpet \ -no-shutdown \ -boot strict=on \ -device pcie-root-port,port=0x10,chassis=1,id=pci.1,bus=pcie.0,multifunction=on,addr=0x2 \ -device pcie-root-port,port=0x11,chassis=2,id=pci.2,bus=pcie.0,addr=0x2.0x1 \ -device pcie-root-port,port=0x12,chassis=3,id=pci.3,bus=pcie.0,addr=0x2.0x2 \ -device pcie-root-port,port=0x13,chassis=4,id=pci.4,bus=pcie.0,addr=0x2.0x3 \ -device ich9-usb-ehci1,id=usb,bus=pcie.0,addr=0x7.0x7 \ -device ich9-usb-uhci1,masterbus=usb.0,firstport=0,bus=pcie.0,multifunction=on,addr=0x7 \ -device ich9-usb-uhci2,masterbus=usb.0,firstport=2,bus=pcie.0,addr=0x7.0x1 \ -device ich9-usb-uhci3,masterbus=usb.0,firstport=4,bus=pcie.0,addr=0x7.0x2 \ -device virtio-serial-pci,id=virtio-serial0,bus=pci.2,addr=0x0 \ -drive file=/mnt/disks/VM/MacinaboxCatalina/Clover.qcow2,format=qcow2,if=none,id=drive-sata0-0-2,cache=writeback \ -device ide-hd,bus=ide.2,drive=drive-sata0-0-2,id=sata0-0-2,bootindex=1,write-cache=on \ -drive file=/mnt/disks/VM/MacinaboxCatalina/Catalina-install.img,format=raw,if=none,id=drive-sata0-0-3,cache=writeback \ -device ide-hd,bus=ide.3,drive=drive-sata0-0-3,id=sata0-0-3,write-cache=on \ -drive file=/mnt/disks/VM/MacinaboxCatalina/macos_disk.img,format=raw,if=none,id=drive-sata0-0-4,cache=writeback \ -device ide-hd,bus=ide.4,drive=drive-sata0-0-4,id=sata0-0-4,write-cache=on \ -netdev tap,fd=35,id=hostnet0 \ -device e1000-82545em,netdev=hostnet0,id=net0,mac=52:54:00:a2:2a:b0,bus=pci.1,addr=0x0 \ -chardev pty,id=charserial0 \ -device isa-serial,chardev=charserial0,id=serial0 \ -chardev socket,id=charchannel0,fd=36,server,nowait \ -device virtserialport,bus=virtio-serial0.0,nr=1,chardev=charchannel0,id=channel0,name=org.qemu.guest_agent.0 \ -device usb-tablet,id=input0,bus=usb.0,port=1 \ -device vfio-pci,host=0000:81:00.0,id=hostdev0,bus=pci.3,multifunction=on,addr=0x0,romfile=/mnt/disks/VM/Sapphire.RX590.8192.190426.rom \ -device vfio-pci,host=0000:81:00.1,id=hostdev1,bus=pci.3,addr=0x0.0x1 \ -usb \ -device usb-kbd,bus=usb-bus.0 \ -device '************************' \ -smbios type=2 \ -cpu Penryn,kvm=on,vendor=GenuineIntel,+invtsc,vmware-cpuid-freq=on,+pcid,+ssse3,+sse4.2,+popcnt,+avx,+aes,+xsave,+xsaveopt,check \ -sandbox on,obsolete=deny,elevateprivileges=deny,spawn=deny,resourcecontrol=deny \ -msg timestamp=on 2020-01-01 22:24:00.755+0000: Domain id=18 is tainted: high-privileges 2020-01-01 22:24:00.755+0000: Domain id=18 is tainted: custom-argv 2020-01-01 22:24:00.755+0000: Domain id=18 is tainted: host-cpu char device redirected to /dev/pts/0 (label charserial0) 2020-01-01T22:27:47.374382Z qemu-system-x86_64: warning: guest updated active QH 2020-01-01T22:27:47.387079Z qemu-system-x86_64: warning: guest updated active QH Pic of splashtop attached.

@johnnie.black @dlandon - So, I just spent a couple hours cleaning my server for dust etc and checking connections. That said, most of that time was spent trying to flash my SAS card to p20.00.07.00. I can't seem to figure that out, and I've tried a few guides. Either way, when I put everything back together and booted back up to unraid the partition is now gone as it should be. So, maybe it was a loose connection or something.... I will read up more on how to flash this SAS card and try to do that as well for good measure. Thank you both again for your input. If anyone can recommend a good guide on flashing these things I would appreciate it. I get the following when attempting to use the exe in dos: Failed to Initialise PAL I know this isn't really a UD issue at this point, so I'll keep reading but if anyone could point me in the right direction I would appreciate it. EDIT/UPDATE - I managed to figure out how to flash the sas card (needed to do it through EFI shell). Everything is up to date now. I assume things are fine but will update if need be.

Thank you both for the replies. Johnnie, I bought my LSI card with IT mode flashed. I think what you'e saying is the 20.00.02.00 IT mode firmware may have issues and I should download and flash 20.00.07.00 version, correct? Sorry for the basic question but I want to make sure I understand what's going on. The only link on broadcom's site for my card in 20.00.07.00 is for a MSDOS windows. I'm going to go do some reading on these cards to educate myself, so apologies if this is basic stuff I should know.

Yep, sorry. You're right. That is my docker/VM SSD. Not sure what's going on with that. Anyway here is my diagnostic. someflix-unraid-diagnostics-20191227-2326.zip