thingie2

Members
  • Posts

    45
  • Joined

  • Last visited

Recent Profile Visitors

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

thingie2's Achievements

Rookie

Rookie (2/14)

3

Reputation

  1. So It's not due to the spindown... I've just had a bunch of write errors on one of the drives connected to the controller, even with spindown disabled for that drive. Any other ideas? tower-diagnostics-20231031-1756.zip
  2. OK, I've turned off spindown on the 2 drives connected to the SAS card. If it does turn out to be OK without the drives spinning down, what are my options? Is there anything other than keep them spun up, or don't use the card?
  3. Unfortunatly, even after the SAS card firmare update, I got some further read errors yesterday evening. Any other ideas? tower-diagnostics-20231031-0833.zip
  4. Right, got the card flashed, now I just need to plug a drive or 2 into it & leave it for a while & confirm if the error comes back or not.
  5. Awesome, I'll try the 9211-8i Firmware then, as I can't find anything specifically for the 9200-8i! I saw a few references implying they were the same, but nothing concrete.
  6. Cheers, I've just checked the sticker on the card, and apparently it's a 9200-8i, so I'll try finding updated firmware for it & giving it a go 1 drive at a time & hope it behaves from there.
  7. Thanks, I'll try to find the axact model number of the card & see if I can find updated firmware for it. Is there any way to check it's been fixed, other than just hooking my array up to it & hope it doesn't cause any problems when errors do occur?
  8. I recently bought a 2nd hand SAS card (been using a PCI-E SATA card for a while, but decided to change due to the claims of a SAS card being better), but since installing, I've been getting drive errors. I had 3 of my drives connected to it. Initially, it was a single drive, started with a couple of read errors, then write errors, so I wondered if it was a cable issue. I swapped the drive to a different connector on the SAS cable, and rebuilt the drive with errors. All was ok again for a day or so, then a different drive got read errors, and then another one (all from the SAS card). Thankfully no more write errors, so I didn't have to rebuild anything. I've now connected everything up avoiding the SAS card again until I can resolve this issue, but I've attached a diagnostics log from the first drive that got errors, does anyone have any pointers to what I need to do to resolve this? tower-diagnostics-20231023-1729.zip
  9. Add the ability to add hysterisis for warnings such as temperature, disk space etc. Lets say you have your disk temp threshold for a warning at 45C, when the drive gets close, it might vary slightly -> 44>45>44>45>44>45 etc. Each time it moves from 44 to 45, a warning message (for any notification methods chosen, e.g. email), which seems excessive. If some hysterisis was added, for example to be able to say "don't re-alert unless it drops under 43C", then you'd only get the notification on the first instance, then you wouldn't get further notifications. This could be user configurable, so you can make it 1C (current behaviour) if desired, but allows the reduction in notifications if desired. Same idea for disk space (e.g. require a 5% drop before re-notification, so the removal/addition of a small file doesn't re-trigger (e.g. a cache drive that might be continually changing). There may be other scenarios too, but they're the only ones that come to mind.
  10. anyone with any solution to this? I've currently reverted back to 6.9.2, where everything works, but I'd like to update to the latest at some point, but will be holding off if there's no fix for this.
  11. Update for anyone else who finds this & has a similar problem. I forced an update on the container & that seemed to remove all the bloat & the container is back down to a more reasonable ~600MB
  12. EpicGanmes-Freegames - Large docker image. I've recently been getting warnings that my docker image is filling up, and upon checking the size of each docker image, this image is by far the largest (6.6GB). Is this normal? It sounds excessively large for a container
  13. Yesterday, I finally remembered to update Unraid to 6.11.5 (I was on 6.9.?) prior to this, however ever since the update, my Libreelec VM has not been working. Intially it gave a "failed to start xorg server" error, which I've had before & seems to be GFX card driver related, so I tried the whole "remove & re-add the GFX card", however since then, I don't get any feed at all on the output of the GPU (The VM does say it's running, however). I'm passing through a GT710 to the VM, which worked fine previously. I noticed an error in the libvirt logs saying "15093: error : virNetSocketReadWire:1791 : End of file while reading data: Input/output error" which from what I can find could well be related & I have removed all other pass-through devices to the VM to check & this error still appears. XML for the VM in question: <?xml version='1.0' encoding='UTF-8'?> <domain type='kvm' id='3'> <name>LibreElec2</name> <uuid>22e56e89-63cd-936b-2c02-c246fc055fd8</uuid> <metadata> <vmtemplate xmlns="unraid" name="Linux" icon="linux.png" os="linux"/> </metadata> <memory unit='KiB'>8388608</memory> <currentMemory unit='KiB'>8388608</currentMemory> <memoryBacking> <nosharepages/> </memoryBacking> <vcpu placement='static'>2</vcpu> <cputune> <vcpupin vcpu='0' cpuset='15'/> <vcpupin vcpu='1' cpuset='31'/> </cputune> <resource> <partition>/machine</partition> </resource> <os> <type arch='x86_64' machine='pc-q35-5.1'>hvm</type> <loader readonly='yes' type='pflash'>/usr/share/qemu/ovmf-x64/OVMF_CODE-pure-efi.fd</loader> <nvram>/etc/libvirt/qemu/nvram/22e56e89-63cd-936b-2c02-c246fc055fd8_VARS-pure-efi.fd</nvram> </os> <features> <acpi/> <apic/> </features> <cpu mode='host-passthrough' check='none' migratable='on'> <topology sockets='1' dies='1' cores='1' threads='2'/> <cache mode='passthrough'/> </cpu> <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='raw' cache='writeback'/> <source file='/mnt/user/domains/LibreElec2/vdisk2.img' index='1'/> <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='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> <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='0x8'/> <alias name='pci.1'/> <address type='pci' domain='0x0000' bus='0x00' slot='0x01' function='0x0' multifunction='on'/> </controller> <controller type='pci' index='2' model='pcie-root-port'> <model name='pcie-root-port'/> <target chassis='2' port='0x9'/> <alias name='pci.2'/> <address type='pci' domain='0x0000' bus='0x00' slot='0x01' function='0x1'/> </controller> <controller type='pci' index='3' model='pcie-root-port'> <model name='pcie-root-port'/> <target chassis='3' port='0xa'/> <alias name='pci.3'/> <address type='pci' domain='0x0000' bus='0x00' slot='0x01' 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='pci' index='5' model='pcie-root-port'> <model name='pcie-root-port'/> <target chassis='5' port='0xb'/> <alias name='pci.5'/> <address type='pci' domain='0x0000' bus='0x00' slot='0x01' function='0x3'/> </controller> <controller type='pci' index='6' model='pcie-to-pci-bridge'> <model name='pcie-pci-bridge'/> <alias name='pci.6'/> <address type='pci' domain='0x0000' bus='0x01' slot='0x00' function='0x0'/> </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='sata' index='0'> <alias name='ide'/> <address type='pci' domain='0x0000' bus='0x00' slot='0x1f' function='0x2'/> </controller> <interface type='bridge'> <mac address='52:54:00:ab:e0:e6'/> <source bridge='br0'/> <target dev='vnet2'/> <model type='virtio-net'/> <alias name='net0'/> <address type='pci' domain='0x0000' bus='0x03' slot='0x00' function='0x0'/> </interface> <serial type='pty'> <source path='/dev/pts/2'/> <target type='isa-serial' port='0'> <model name='isa-serial'/> </target> <alias name='serial0'/> </serial> <console type='pty' tty='/dev/pts/2'> <source path='/dev/pts/2'/> <target type='serial' port='0'/> <alias name='serial0'/> </console> <channel type='unix'> <source mode='bind' path='/var/lib/libvirt/qemu/channel/target/domain-3-LibreElec2/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='tablet' bus='usb'> <alias name='input0'/> <address type='usb' bus='0' port='3'/> </input> <input type='mouse' bus='ps2'> <alias name='input1'/> </input> <input type='keyboard' bus='ps2'> <alias name='input2'/> </input> <audio id='1' type='none'/> <hostdev mode='subsystem' type='pci' managed='yes'> <driver name='vfio'/> <source> <address domain='0x0000' bus='0x21' slot='0x00' function='0x0'/> </source> <alias name='hostdev0'/> <rom file='/mnt/user/isos/MSI.GT710.2048.160112_mod.rom'/> <address type='pci' domain='0x0000' bus='0x04' slot='0x00' function='0x0' multifunction='on'/> </hostdev> <hostdev mode='subsystem' type='pci' managed='yes'> <driver name='vfio'/> <source> <address domain='0x0000' bus='0x21' slot='0x00' function='0x1'/> </source> <alias name='hostdev1'/> <address type='pci' domain='0x0000' bus='0x04' 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> </domain> I've attached a diagnostics file from my server, but anything else, let me know. Any suggestions on how to fix this? tower-diagnostics-20230119-1207.zip
  14. I shouldn't have had either on the array, as they were both set to prefer cache & they always used to be on the cache only, but I've just checked & docker.img was on disk 5 for some reason. I didn't even think to check the location, as I was still getting it with docker turned off, but maybe Unraid does stuff with docker.img for upto a min or so after docker has actually been turned off (I didn't leave it off long, as when I still saw the RW happening, I decided it must not be that & turned it back on!) I've moved it back to the cache drive where it should have been & will leave it be for a few hours/over night & confirm it's fixed it.
  15. Hi All, I've been having this issue for a couple of weeks now. My drives (usually all of them, but occasionally it's just 1+parity) won't spin down (or spin back up again if I force a spin down). I have tried disabling Docker & VMs, still happens. I have tried using the File Activity & Active streams plugins, but these show nothing is happening. tower-diagnostics-20220922-1809.zip I'm at a loss as to how to try and find the source of these reads & writes, so my drives can spin down when (as far as I'm aware), nothing should be happening! I've attached a diagnostics, hopefully that'll say something. If anyone can point me at anything else to check/any further information to give to help solve this, please let me know. thanks in advance.