Fireball3

Members
  • Posts

    1350
  • Joined

  • Last visited

1 Follower

Converted

  • Gender
    Undisclosed
  • Location
    Good old Germany
  • Personal Text
    >> Engage <<

Recent Profile Visitors

3663 profile views

Fireball3's Achievements

Community Regular

Community Regular (8/14)

48

Reputation

  1. This should answer your question: https://forums.unraid.net/topic/47914-controlr-androidios-app-for-unraid/?do=findComment&comment=1014190
  2. Have you tried taping the contacts? There is a detailed description somewhere in the forum. Use the search function please, I'm on tapatalk at the moment. Maybe you have to use another board for the flash procedure.
  3. OK, weekend is approaching and I have to get the media server up and running again... 😓 My plan is to setup a clean unRAID on the USB and copy the settings without the docker from the old install. Maybe I should skip the plugins also since they are giving errors in the syslog? So, what are the essential parts that I need to copy to the fresh install? super.dat license file ... ?
  4. I pulled the syslog. Maybe this will encourage you to give me some advice. 😉 syslog_18.01.2021.txt I wonder why the rootfs is 684M only. Shouldn't that be of the size of installed RAM??? 🤔
  5. Hi folks, I ran into this issue after installing the MiniDLNA docker. Probably didn't pay attention (took the presettings) with the settings of the docker. Now the server is running out of space on the rootfs when booting. The GUI is not available, SMB not running, array is not mounted. Luckily I can ssh in and see what's going on. When trying to grab a diagnostics I get this: root@Tower:~# diagnostics Starting diagnostics collection... Warning: file_put_contents(): Only 0 of 5 bytes written, possibly out of free disk space in /usr/local/emhttp/plugins/dynamix/scripts/diagnostics on line 80 Warning: file_put_contents(): Only 0 of 975 bytes written, possibly out of free disk space in /usr/local/emhttp/plugins/dynamix/scripts/diagnostics on line 85 Warning: file_put_contents(): Only 0 of 78 bytes written, possibly out of free disk space in /usr/local/emhttp/plugins/dynamix/scripts/diagnostics on line 101 Warning: file_put_contents(): Only 0 of 2 bytes written, possibly out of free disk space in /usr/local/emhttp/plugins/dynamix/scripts/diagnostics on line 120 Warning: file_put_contents(): Only 0 of 34 bytes written, possibly out of free disk space in /usr/local/emhttp/plugins/dynamix/scripts/diagnostics on line 122 Warning: file_put_contents(): Only 0 of 2 bytes written, possibly out of free disk space in /usr/local/emhttp/plugins/dynamix/scripts/diagnostics on line 120 Warning: file_put_contents(): Only 0 of 34 bytes written, possibly out of free disk space in /usr/local/emhttp/plugins/dynamix/scripts/diagnostics on line 122 echo: write error: No space left on device echo: write error: No space left on device echo: write error: No space left on device echo: write error: No space left on device echo: write error: No space left on device echo: write error: No space left on device echo: write error: No space left on device echo: write error: No space left on device echo: write error: No space left on device Warning: file_put_contents(): Only 0 of 29 bytes written, possibly out of free disk space in /usr/local/emhttp/plugins/dynamix/scripts/diagnostics on line 160 Warning: file_put_contents(): Only 0 of 29 bytes written, possibly out of free disk space in /usr/local/emhttp/plugins/dynamix/scripts/diagnostics on line 160 Warning: file_put_contents(): Only 0 of 29 bytes written, possibly out of free disk space in /usr/local/emhttp/plugins/dynamix/scripts/diagnostics on line 160 Warning: file_put_contents(): Only 0 of 29 bytes written, possibly out of free disk space in /usr/local/emhttp/plugins/dynamix/scripts/diagnostics on line 160 Warning: file_put_contents(): Only 0 of 29 bytes written, possibly out of free disk space in /usr/local/emhttp/plugins/dynamix/scripts/diagnostics on line 160 Warning: file_put_contents(): Only 0 of 29 bytes written, possibly out of free disk space in /usr/local/emhttp/plugins/dynamix/scripts/diagnostics on line 160 Warning: file_put_contents(): Only 0 of 29 bytes written, possibly out of free disk space in /usr/local/emhttp/plugins/dynamix/scripts/diagnostics on line 160 Warning: file_put_contents(): Only 0 of 29 bytes written, possibly out of free disk space in /usr/local/emhttp/plugins/dynamix/scripts/diagnostics on line 160 Warning: file_put_contents(): Only 0 of 65 bytes written, possibly out of free disk space in /usr/local/emhttp/plugins/dynamix/scripts/diagnostics on line 166 Warning: file_put_contents(): Only 0 of 535 bytes written, possibly out of free disk space in /usr/local/emhttp/plugins/dynamix/scripts/diagnostics on line 210 done. ZIP file '/boot/logs/tower-diagnostics-20210117-0922.zip' created. The diagnostic file contains only empty files. Checking for space: root@Tower:~# df -h Filesystem Size Used Avail Use% Mounted on rootfs 684M 684M 0 100% / tmpfs 32M 368K 32M 2% /run devtmpfs 684M 0 684M 0% /dev tmpfs 747M 0 747M 0% /dev/shm cgroup_root 8.0M 0 8.0M 0% /sys/fs/cgroup tmpfs 128M 140K 128M 1% /var/log /dev/sda 1003M 246M 758M 25% /boot /dev/loop0 9.2M 9.2M 0 100% /lib/modules /dev/loop1 7.3M 7.3M 0 100% /lib/firmware Is my assumption correct about the docker filling up the rootfs? That was the last thing I set up before this problem arose. How can I free up the space used by the docker? I checked the stick on a Windows machine for filesystem issues, but all is fine. I have teamviewer access only to the server. Safe boot and such things are not an option. I can ask the remote user to plug the stick into a Windows machine and change/modify content on the stick or do it via console. I would prefer not to set up a new config but remove the docker to free up space.
  6. It's it true that solid state drives are always filled up according to those graphs posted? Will empty space always be shifted in the right side of the graph/drive or will it be more like a sawtooth pattern on a well run in drive where data may have been deleted in random areas of the drive?
  7. Just to make sure I understand it right. The flat line that basically indicates the max. interface throughput is trimmed (empty) space on the SSD?
  8. Those are the features I personally need most. 🤤 Thanks for finally bringing this to life.
  9. I can second this find. I'm playing with a HP NL54 microserver. After installing the plugin it detects the correct sensors. Assignment of sensors Pressing "APPLY" Of course, no sensor data is displayed. After deleting /etc/sensors.d/sensors.conf I can repeat the procedure. If the file is not deleted or modified like below, no chance to get the selection back. Initial sensors.conf root@Tower:~# cat /etc/sensors.d/sensors.conf # sensors chip "k10temp-pci-00c3" label "temp1" "CPU Temp" chip "w83795adg-i2c-1-2f" label "temp2" "MB Temp" chip "w83795adg-i2c-1-2f" label "fan1" "Array Fan" root@Tower:/etc/sensors.d# sensors Error: File /etc/sensors.d/sensors.conf, line 4: Undeclared bus id referenced Error: File /etc/sensors.d/sensors.conf, line 6: Undeclared bus id referenced sensors_init: Can't parse bus name Deleted the sensors.conf and rescan. Sensors were back for selection in the GUI. Note, the K10 sensor disappeared... Pressed APPLY again and they were gone. I change the sensors.conf like this root@Tower:/etc/sensors.d# cat /etc/sensors.d/sensors.conf # sensors chip "w83795adg-i2c-12f" label "temp1" "CPU Temp" chip "w83795adg-i2c-12f" label "temp2" "MB Temp" chip "w83795adg-i2c-12f" label "fan1" "Array Fan" root@Tower:/etc/sensors.d# sensors Error: File /etc/sensors.d/sensors.conf, line 2: Parse error in chip name Error: File /etc/sensors.d/sensors.conf, line 4: Parse error in chip name Error: File /etc/sensors.d/sensors.conf, line 6: Parse error in chip name But the sensors reapear in the GUI. Of course there is no further benefit in having them back for selection, as long as they can't be saved and the temps are not displayed as intended. @bonienl Please let me know how I can contribute further to help debugging this issue. I also noticed this little spelling error in the mouseover.
  10. Is the PCB itself genuine LSI or a rebrand? For LSI you shouldn't need the workaround as for the rebranded cards. Have you tried the toolset I used for the Dell adapters? Should be linked in my signature. Ima posting this from my mobile so can't provide a link right now.
  11. The router will sent the magic packet and wake up the machine if it sees traffic dedicated for the server, but the NIC will have to do its job and listen for it. The router setting just takes over the wake-up task that you would need to perform by hand with a wake up command sent from PC or smartphone. Maybe on those server boards the WOL is done via the management interface? The support should be able to help.
  12. The wake-up can not be performed by the plugin. The feature is called wake-on-lan aka. WOL and it must be configured in the BIOS if you use the on-board NIC. Check the manual of your board. If you use an add-on NIC the issue gets more sophisticated.
  13. @trurl I'm using Tapatalk here and I selected the name off the list that popped up but for reasons the link failed!?But I see there is a difference once the post is online. Edit: Once edited, the link gets fixed... Just edit and save without any modification.
  14. I suppose one of your 4TB drives is parity at the moment. The new drive is bigger than your current drives, so it will have to be the new parity drive. The parity needs to be at least as big as your biggest data drive. I'm not sure how the preclear is handled in recent versions. Maybe @johnnie.black can help here? For the Plex thing you should read up on how to use docker containers and see if that works for you. IIRC there is also a install package on the Plex site if you want to go that way. Sorry for the global answers, but I'm travelling at the moment and can't provide links as I'm writing this on my mobile. Gesendet von meinem Mi 9 SE mit Tapatalk
  15. Hi, welcome to the unRAID forums. If you didn't know by now, writing everything in CAPITAL letters is considered as SHOUTING to others. Now we have 3 possibilities on the receiver side: 1. You are not sure about your orthography skills and go all capital. 2. Your caps-lock has been unintentionally stuck. 3. You are intentionally shouting at us. Please elaborate.