statecowboy

Members
  • Posts

    112
  • Joined

  • Last visited

Everything posted by statecowboy

  1. Unraid can do all of that. That's a beast of a build if you guys do it, nice to have someone else paying as well. My only concern would be finding a mobo to suit those needs with the latest gen of ryzen processors. I just attmempted a smaller 3700X build and was not satisfied with the MOBO options. Of course, the things I was interested in having you may not (ecc memory support, BMS, multiple NICs etc.).
  2. Thank you for the response. I have stripped everything back down, checked connections etc. and rebooted the server with the drive reintroduced. It's rebuilding now. I will follow up if there are any issues. Thanks, Johnnie.
  3. So, I knew it would happen eventually, but this is my first disk error. Diagnostic attached. Jan 5 08:25:45 someflix-unraid kernel: md: disk6 read error, sector=3453668352 Jan 5 08:25:45 someflix-unraid kernel: md: disk6 read error, sector=3453668360 Jan 5 08:25:45 someflix-unraid kernel: md: disk6 read error, sector=3453668368 Jan 5 08:25:45 someflix-unraid kernel: md: disk6 read error, sector=3453668376 Jan 5 08:25:45 someflix-unraid kernel: md: disk6 read error, sector=3453668384 Jan 5 08:25:45 someflix-unraid kernel: md: disk6 read error, sector=3453668392 Jan 5 08:25:45 someflix-unraid kernel: md: disk6 read error, sector=3453668400 Jan 5 08:25:45 someflix-unraid kernel: md: disk6 read error, sector=3453668408 Jan 5 08:25:46 someflix-unraid kernel: md: disk6 write error, sector=3453668352 Jan 5 08:25:46 someflix-unraid kernel: md: disk6 write error, sector=3453668360 Jan 5 08:25:46 someflix-unraid kernel: md: disk6 write error, sector=3453668368 Jan 5 08:25:46 someflix-unraid kernel: md: disk6 write error, sector=3453668376 Jan 5 08:25:46 someflix-unraid kernel: md: disk6 write error, sector=3453668384 Jan 5 08:25:46 someflix-unraid kernel: md: disk6 write error, sector=3453668392 Jan 5 08:25:46 someflix-unraid kernel: md: disk6 write error, sector=3453668400 Jan 5 08:25:46 someflix-unraid kernel: md: disk6 write error, sector=3453668408 Drive dying? I should mention, I just added hardware transcoding to my unraid last night with a 1050 Ti. So, it's possible I knocked a cable I suppose. I will check that as well. Drive only has 17,256 of power on time so I would be a bit surprised if it's already going bad. someflix-unraid-diagnostics-20200105-0845.zip
  4. What do you intend on doing with it? I have dual E5-2680 V2s in my system and I'm reading this sub-forum now to get ideas on how to save power cost. The 2680 is honestly way too much for what I need. I primarily serve plex content to family and friends, run a few dockers (sonarr radarr etc etc) and never really get much of a hit on CPU all while chewing up a lot of power (hence the reason I'm now looking at the newer ryzens to possibly lower my power bill a few bucks). My point is, it really depends on what you need.
  5. 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.
  6. Hm, I don't see too many differences from our configs. I'm still getting stuck when trying to use splashtop to connect to my VM. It just hangs at the connecting screen. I'll hop over to the support thread and see if someone can help me out. Thanks again.
  7. Thank you both for the comments. I just picked up an RX 590 (Sapphire) at my local microcenter. It came with a game and xbox game pass so jumped on it. That said, having some issues passing through my VM. Would you mind sharing your config for the catalina install? I managed to get everything going with VNC but when switching to the AMD card I'm hitting some road blocks.
  8. Hi all, it's been a while since I've purchased a video card. I've been checking out @SpaceInvaderOne's Macinabox and wanted to give it a try. That said, I'm assuming for optimum performance I should probably grab a GPU for passthrough. I saw that in order to run Mojave you need an AMD GPU. I was wondering if any others out there would not mind sharing what GPU you're using to do this, or any other recommendations on picking one up. I don't need top of the line, I primarily do gaming on an xbox. But I do some photo editing etc. so I'd want the performance to be as close to an actual MacOS experience as possible. I've been reading about top GPU ratings etc. but it's all a bit overwhelming with so many models and variants out there. I also occasionally run windows/linux VMs so I'd want whatever I pick up to be usable there as well. Edit - I should mention I run two QHD monitors for my primary work machine.
  9. @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.
  10. 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.
  11. 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
  12. Dec 27 23:15:42 someflix-unraid unassigned.devices: Error: shell_exec(/usr/bin/lsof '/mnt/disks/virtualisation' 2>/dev/null | /bin/sort -k8 | /bin/uniq -f7 | /bin/grep -c -e REG) took longer than 5s!
  13. FS: xfs /sbin/xfs_repair -n /dev/sdk1 2>&1 Phase 1 - find and verify superblock... Phase 2 - using internal log - zero log... - scan filesystem freespace and inode maps... - found root inode chunk Phase 3 - for each AG... - scan (but don't clear) agi unlinked lists... - process known inodes and perform inode discovery... - agno = 0 - agno = 1 - agno = 2 - agno = 3 - process newly discovered inodes... Phase 4 - check for duplicate blocks... - setting up duplicate extent list... - check for inodes claiming duplicate blocks... - agno = 0 - agno = 2 - agno = 3 - agno = 1 No modify flag set, skipping phase 5 Phase 6 - check inode connectivity... - traversing filesystem ... - traversal finished ... - moving disconnected inodes to lost+found ... Phase 7 - verify link counts... No modify flag set, skipping filesystem flush and exiting.
  14. One thing I like about unraid - it's simple enough for a linux novice to use, yet powerful enough to do everything and let you take the training wheels off if you're ready. One thing I'd like to see in 2020 - Some sort of offsite built in backup feature utilizing rclone or the like.
  15. Hi there. I can't seem to delete a partition in a disk I have set aside in unassigned devices. It's sdk and the partition is "NVR". I want to wipe that partition out so I can reformat the disk. I have unassigned devices set to destructive mode enabled. Everything appears to work as it should when I remove the partition and type "Yes" but the partition remains there unchanged afterwards. Diagnostics attached. someflix-unraid-diagnostics-20191222-0845.zip
  16. Sorry, upon further investigation pfblocker was blocking gitlab. I whitelisted it in pfsense and all is good.
  17. First off, thank you so much for all the work you put into making this community better. That said...:( Getting this error when pulling the docker. Looks like a cert problem with the actual repo. fatal: unable to access 'https://gitlab.com/Shinobi-Systems/Shinobi.git/': SSL certificate problem: self signed certificate
  18. Hi guys, I'm starting to get into VLANs and network segregation. I will list my gear below so you can see what I'm working with. In short, I started by setting up VLANs for my guest wifi and "IOT" devices on my network to separate them from my server and other PCs on my LAN. However, doing so presented some obstacles such as my Harmony Hub took forever to communicate with my Roku (the harmony hub was on IOT while the Roku was on LAN). After switching the Roku to IOT as well then I could not direct access my local plex server (it switched over to remote access). So, I'm now investigating VLANs in unraid and potentially running Plex in the same VLAN. I currently run all my dockers in bridge mode. My problem is there are so many apparent ways of segregating things I'm a bit overwhelmed on what to learn first. I eventually intend on adding POE cams to my network as well, so that will bring new complexity. What i would like to do is have my unraid server (for management access) on my LAN network protected from IOT devices (and WAN exposed dockers), while at the same time allowing IOT devices access to dockers as needed. I also want to keep guest wifi access segregated from everything (I think I've achieved this with my current setup). I serve up a plex server for family so need to keep that accessible from outside. To add complexity I run organizr and rev proxy all my services back into the LE container. So far I've set up a VLAN on my eth1 interface for dockers and tinkered with rev proxying a service back to my LE container from that VLAN. The rev proxy does not work, presumably because it's on a different subnet. So, it seems that if I do go the docker VLAN route, I will need all of my services that are reverse proxied on the same VLAN/subnet. Is this correct? Given the hardware/software available to me, is there another recommended route? I assume there are others here with a similar setup and goals, would you mind sharing what approach you take? Gear: ISP - Google Fiber (1Gb) - Firewall - PFSense Dedicated Box in lieu of google fiber network box (4 NICs available, 2 in use now for LAN and WAN, I have created VLANS for IOT, Guest, and Dockers, also running Avahi for LAN to IOT communication and an OpenVPN server for remote access) Switch - US-24-250W (Unifi 250W POE+ switch), 8 Port Unifi POE switch (currently not in use) APs - 2 Unifi AP Pros and 1 AP-LR (3 SSIDs corresponding to LAN and VLANs for Guest and IOT) Unifi Controller - running as docker service 4-port 1Gb PCIe NIC card - currently un-used (but accessible from Unraid). I had this going when I was running PFsense as a VM before purchasing a dedicated box. My MOBO also has 2 1Gb NICs available. Currently only 1 is in use.
  19. So I've been messing with tdarr_aio trying to convert my media files. I've been getting out of memory errors, which I thought were related to how I had it configured. So, I changed over to have it transcode to cache yesterday. I have it set up to run overnight and when I woke up today I got the following errors: **** Rootfs file is getting full (currently 100 % used) **** **** Out Of Memory errors detected on your server **** **** Plugin disklocation-master.plg is not up to date **** I tried logging in to see what was going on and it says my array is undefined. In addition, the main screen is flashing some error messages every so often (see excerpt of some of them below). I'm unable to pull diagnostics or logs. I tried rebooting but it the system wont respond. I'm a little nervous trying anything else before consulting the experts here. Any ideas? Warning: array_key_exists() expects parameter 2 to be array, boolean given in /usr/local/emhttp/plugins/unassigned.devices/include/lib.php on line 1328 Warning: file_put_contents(): Only 12288 of 12290 bytes written, possibly out of free disk space in /usr/local/emhttp/plugins/unassigned.devices/include/lib.php on line 105 Warning: file_put_contents(): Only 12288 of 14595 bytes written, possibly out of free disk space in /usr/local/emhttp/plugins/unassigned.devices/include/lib.php on line 105 Warning: file_put_contents(): Only 12288 of 14021 bytes written, possibly out of free disk space in /usr/local/emhttp/plugins/unassigned.devices/include/lib.php on line 105 Warning: file_put_contents(): Only 12288 of 14595 bytes written, possibly out of free disk space in /usr/local/emhttp/plugins/unassigned.devices/include/lib.php on line 105 Warning: file_put_contents(): Only 12288 of 14021 bytes written, possibly out of free disk space in /usr/local/emhttp/plugins/unassigned.devices/include/lib.php on line 105 Warning: file_put_contents(): Only 12288 of 14595 bytes written, possibly out of free disk space in /usr/local/emhttp/plugins/unassigned.devices/include/lib.php on line 105 Warning: file_put_contents(): Only 12288 of 14038 bytes written, possibly out of free disk space in /usr/local/emhttp/plugins/unassigned.devices/include/lib.php on line 105 Warning: file_put_contents(): Only 12288 of 14612 bytes written, possibly out of free disk space in /usr/local/emhttp/plugins/unassigned.devices/include/lib.php on line 105 Warning: file_put_contents(): Only 12288 of 14038 bytes written, possibly out of free disk space in /usr/local/emhttp/plugins/unassigned.devices/include/lib.php on line 105 Warning: file_put_contents(): Only 12288 of 14612 bytes written, possibly out of free disk space in /usr/local/emhttp/plugins/unassigned.devices/include/lib.php on line 105 Warning: file_put_contents(): Only 12288 of 14041 bytes written, possibly out of free disk space in /usr/local/emhttp/plugins/unassigned.devices/include/lib.php on line 105 Warning: file_put_contents(): Only 12288 of 14615 bytes written, possibly out of free disk space in /usr/local/emhttp/plugins/unassigned.devices/include/lib.php on line 105 Warning: file_put_contents(): Only 12288 of 14046 bytes written, possibly out of free disk space in /usr/local/emhttp/plugins/unassigned.devices/include/lib.php on line 105 Warning: file_put_contents(): Only 12288 of 14621 bytes written, possibly out of free disk space in /usr/local/emhttp/plugins/unassigned.devices/include/lib.php on line 105 Warning: file_put_contents(): Only 12288 of 14042 bytes written, possibly out of free disk space in /usr/local/emhttp/plugins/unassigned.devices/include/lib.php on line 105 Edit, I am able to start a terminal session and managed to run "df -a". Results below. Filesystem 1K-blocks Used Available Use% Mounted on rootfs 32882060 32882060 0 100% / proc 0 0 0 - /proc sysfs 0 0 0 - /sys tmpfs 32768 272 32496 1% /run devtmpfs 32882080 0 32882080 0% /dev devpts 0 0 0 - /dev/pts tmpfs 32966388 0 32966388 0% /dev/shm fusectl 0 0 0 - /sys/fs/fuse/connections cgroup_root 8192 0 8192 0% /sys/fs/cgroup cpuset 0 0 0 - /sys/fs/cgroup/cpuset cpu 0 0 0 - /sys/fs/cgroup/cpu cpuacct 0 0 0 - /sys/fs/cgroup/cpuacct blkio 0 0 0 - /sys/fs/cgroup/blkio memory 0 0 0 - /sys/fs/cgroup/memory devices 0 0 0 - /sys/fs/cgroup/devices freezer 0 0 0 - /sys/fs/cgroup/freezer net_cls 0 0 0 - /sys/fs/cgroup/net_cls perf_event 0 0 0 - /sys/fs/cgroup/perf_event pids 0 0 0 - /sys/fs/cgroup/pids tmpfs 131072 2056 129016 2% /var/log /dev/sda1 15289328 484912 14804416 4% /boot /dev/loop0 8832 8832 0 100% /lib/modules /dev/loop1 6016 6016 0 100% /lib/firmware rootfs 32882060 32882060 0 100% /mnt nfsd 0 0 0 - /proc/fs/nfs nfsd 0 0 0 - /proc/fs/nfsd /dev/md1 7813549600 4821123532 2992426068 62% /mnt/disk1 /dev/md2 7811939620 3911881956 3900057664 51% /mnt/disk2 /dev/md3 7811939620 3916374416 3895565204 51% /mnt/disk3 /dev/md4 7811939620 5456685024 2355254596 70% /mnt/disk4 /dev/md5 7811939620 4015610840 3796328780 52% /mnt/disk5 /dev/md6 7811939620 4715013348 3096926272 61% /mnt/disk6 /dev/md7 2928835740 171705200 2757130540 6% /mnt/disk7 /dev/md8 2928835740 162151152 2766684588 6% /mnt/disk8 /dev/md9 2928835740 2951616 2925884124 1% /mnt/disk9 /dev/md10 2928835740 2951616 2925884124 1% /mnt/disk10 /dev/sdd1 468851512 23456 467762176 1% /mnt/cache shfs 58588590660 27176448700 31412141960 47% /mnt/user0 shfs 59057442172 27176472156 31879904136 47% /mnt/user /dev/sdf1 488148084 199520904 288627180 41% /mnt/disks/virtualisation google: 1099511627776 36085148556 1099511627776 4% /mnt/disks/google /dev/loop2 41943040 16358260 23737564 41% /var/lib/docker /dev/loop2 41943040 16358260 23737564 41% /var/lib/docker/btrfs nsfs 0 0 0 - /var/run/docker/netns/default /dev/loop3 1048576 17736 925336 2% /etc/libvirt shm 65536 0 65536 0% /var/lib/docker/containers/2f61c1c7ebb16f7a8fd39081622b5356f28dc140f1139076f81261b702497af3/mounts/shm nsfs 0 0 0 - /var/run/docker/netns/7eda9535c0ec shm 65536 0 65536 0% /var/lib/docker/containers/bf300d1797b898b6dadcc38ba499d58010e5a7d2c00db8654b5c0e23366e4041/mounts/shm nsfs 0 0 0 - /var/run/docker/netns/dee9e1097d47 shm 65536 0 65536 0% /var/lib/docker/containers/30a49e4ca91a4690b204e016c069a79c033c7a895d566da510d98921eeea4589/mounts/shm shm 65536 0 65536 0% /var/lib/docker/containers/409801fad6b31f304ade30b709b1cc8277626067c619c6e1c0e480c94581031a/mounts/shm nsfs 0 0 0 - /var/run/docker/netns/23eef4ac9f4c shm 65536 0 65536 0% /var/lib/docker/containers/6300a9dcc3f8a2c440331805bdab740ea185a7a295727be2334572d0fc6e9cea/mounts/shm shm 65536 0 65536 0% /var/lib/docker/containers/9a1f8a31dd266f19bb36a71a60f2ad40d1cf1acb18f14911b2b01d4083797883/mounts/shm nsfs 0 0 0 - /var/run/docker/netns/d12fc7c5483f shm 65536 0 65536 0% /var/lib/docker/containers/9502ed9998ba3018917cb76d4cfb28ddaf00f230edd7d6f2c9354a44ccb3f185/mounts/shm nsfs 0 0 0 - /var/run/docker/netns/37afd77f133e shm 65536 0 65536 0% /var/lib/docker/containers/a0cb41179f4fa9d5bdd5ce371b935f7083cfdb43eda85b84d911d4292ea18d8e/mounts/shm nsfs 0 0 0 - /var/run/docker/netns/bc1116639230 shm 65536 0 65536 0% /var/lib/docker/containers/59d56acd3eb66f935c2711d276660d1d0aa95396c5f9d363fcea5bcc9741627f/mounts/shm nsfs 0 0 0 - /var/run/docker/netns/2e775457ecee shm 65536 0 65536 0% /var/lib/docker/containers/e48d24c1e3d9f753401c69764fe9a92ff04ebbe634a53149d64a624a385217e4/mounts/shm nsfs 0 0 0 - /var/run/docker/netns/45d78294f3e5 shm 65536 0 65536 0% /var/lib/docker/containers/2a69a8dd2b1eeb0dc3c5eb810a37c54bba639d47fe8e25b7f4868acdd988d14e/mounts/shm nsfs 0 0 0 - /var/run/docker/netns/9207588f1026 shm 65536 0 65536 0% /var/lib/docker/containers/63ecceb59d605b86de7c5e1c0834491cf0d145692beae1690ef864093af48f3c/mounts/shm nsfs 0 0 0 - /var/run/docker/netns/95702d9e885b shm 65536 0 65536 0% /var/lib/docker/containers/025e53301a9aba6cbdeb4b1a7775b8a74d5db9ed9b908a1e9714834503037189/mounts/shm nsfs 0 0 0 - /var/run/docker/netns/b71f9835c3ff shm 65536 4 65532 1% /var/lib/docker/containers/a2a69cbb162ffd2b1b8f46d68043742b204bd2653e57ff19fb0b06c91c683c5e/mounts/shm nsfs 0 0 0 - /var/run/docker/netns/4ab94956c615 shm 65536 4 65532 1% /var/lib/docker/containers/eb2fba9ec9a2b7553f55b25326ae412fe1addbc36d605b514c06f3c097865f36/mounts/shm nsfs 0 0 0 - /var/run/docker/netns/7c7aeabee4ee shm 65536 0 65536 0% /var/lib/docker/containers/963d92939bcc07a5b816b4075c30b158d4a05fc511e9a2e257000374cdeb45b1/mounts/shm nsfs 0 0 0 - /var/run/docker/netns/6a27c1c8e467 shm 65536 8 65528 1% /var/lib/docker/containers/24cc5a4724d9264e1b416394654e69cebae15000cca509341f97e62787075ce5/mounts/shm shm 65536 0 65536 0% /var/lib/docker/containers/9a664575317daf7e26fa4a23b07304f1f0b4b55b3ec1a9544cc8bba7cde2cdaa/mounts/shm nsfs 0 0 0 - /var/run/docker/netns/88e80135ea8c shm 65536 0 65536 0% /var/lib/docker/containers/b9b8e4cde24da367b26f85fa9ae1e1ee1cbece846fe0ef2299708dfb0a51c4a6/mounts/shm nsfs 0 0 0 - /var/run/docker/netns/61676b4ea872 shm 65536 0 65536 0% /var/lib/docker/containers/d224804c8efc900272a52b2700f3399afee2a348a0973e8b5f8313979020f432/mounts/shm nsfs 0 0 0 - /var/run/docker/netns/479029298b41 shm 65536 0 65536 0% /var/lib/docker/containers/ebd4a734aa797dd0b3baef48f8a340058af0988bb7545533830bf59e397138c1/mounts/shm nsfs 0 0 0 - /var/run/docker/netns/2095cb64d8c5 shm 65536 0 65536 0% /var/lib/docker/containers/43eb3b1908035f2d10780d3417b36fff4d00a0531d9c4851886d319320c6eedc/mounts/shm nsfs 0 0 0 - /var/run/docker/netns/f1002d0e21fa shm 65536 4 65532 1% /var/lib/docker/containers/4e1dc6a2af835ea9755154c15ad2b130630eb57c33b4b3ea11c8bba0315ed869/mounts/shm nsfs 0 0 0 - /var/run/docker/netns/0138765bc995 shm 65536 0 65536 0% /var/lib/docker/containers/0f149617a482c187dbb04dd33c8b9944475d5e14a8234c0054a312bbdebef7b0/mounts/shm nsfs 0 0 0 - /var/run/docker/netns/feea0544eb3c shm 65536 0 65536 0% /var/lib/docker/containers/2ce8cd71c77ed0bf24078400ac6ab6cbb17b13ca02b2269f429b6fc7f3112080/mounts/shm nsfs 0 0 0 - /var/run/docker/netns/9729d5f28cf1 shm 65536 0 65536 0% /var/lib/docker/containers/cbcc5486c636abb755202c65e57a973d56551014c9f4777702c6654253a1d655/mounts/shm nsfs 0 0 0 - /var/run/docker/netns/86a1ccf9f964 UPDATE (FIXED?) - Managed to reboot through terminal. Somehow I am setting things up incorrectly and my RAM was completely full.
  20. Yeah, I shut down the script and waited a week at one point but it was still running. Maybe I can wait longer. I'd just like to kill it somehow and be done with it so I can upgrade. Thanks for the input.
  21. Can someone please help me stop the currently running rclone process so i can update? I've tried killing processes, but I'm not sure I'm doing it right and I dont want to screw anything up. Here's what I get when attempting to update the plugin. plugin: updating: rclone.plg +============================================================================== | Skipping package rclone-2018.08.25-bundle (already installed) +============================================================================== Downloading rclone Downloading certs Archive: /boot/config/plugins/rclone-beta/install/rclone-beta-latest.zip creating: /boot/config/plugins/rclone-beta/install/rclone-v1.48.0-011-g276f8ccc-beta-linux-amd64/ inflating: /boot/config/plugins/rclone-beta/install/rclone-v1.48.0-011-g276f8ccc-beta-linux-amd64/rclone.1 inflating: /boot/config/plugins/rclone-beta/install/rclone-v1.48.0-011-g276f8ccc-beta-linux-amd64/README.txt inflating: /boot/config/plugins/rclone-beta/install/rclone-v1.48.0-011-g276f8ccc-beta-linux-amd64/git-log.txt inflating: /boot/config/plugins/rclone-beta/install/rclone-v1.48.0-011-g276f8ccc-beta-linux-amd64/README.html inflating: /boot/config/plugins/rclone-beta/install/rclone-v1.48.0-011-g276f8ccc-beta-linux-amd64/rclone Copy failed - is rclone running? plugin: run failed: /bin/bash retval: 1