ibphantom

I have 13TB Free and my docker file is double the normal in size, every other container works, and I've changed file permissions to 777. Still having the problem.

I've tried. Nothing should have changed, but when I do change the Host Paths from /mnt/disks/user/docker-settings/omada-controller/ instead of /mnt/disks/extrassd/, that's when I get the second error. The first error occurs since the update to 5.12.X

I've never had a problem with the container before this previous Major update. The error was fixed by changing /mnt/disks/user/docker-settings/omada-controller/ instead of /mnt/disks/extrassd/ This error started when 5.12.X came out. My last backups of this are from 5.9.31 and it's still giving me this even if I try to pull the 5.9.x Tag @mbentley New Error after changing to /mnt/disks/user 2023-10-15 07:28:24,380 Log4j2-TF-5-AsyncLoggerConfig-4 ERROR An exception occurred processing Appender RollingFile org.apache.logging.log4j.core.appender.AppenderLoggingException: Error writing to stream ../logs/server.log at org.apache.logging.log4j.core.appender.OutputStreamManager.writeToDestination(OutputStreamManager.java:252) at org.apache.logging.log4j.core.appender.FileManager.writeToDestination(FileManager.java:277) at org.apache.logging.log4j.core.appender.rolling.RollingFileManager.writeToDestination(RollingFileManager.java:275) at org.apache.logging.log4j.core.appender.OutputStreamManager.flushBuffer(OutputStreamManager.java:283) at org.apache.logging.log4j.core.appender.OutputStreamManager.flush(OutputStreamManager.java:294) at org.apache.logging.log4j.core.appender.AbstractOutputStreamAppender.directEncodeEvent(AbstractOutputStreamAppender.java:199) at org.apache.logging.log4j.core.appender.AbstractOutputStreamAppender.tryAppend(AbstractOutputStreamAppender.java:190) at org.apache.logging.log4j.core.appender.AbstractOutputStreamAppender.append(AbstractOutputStreamAppender.java:181) at org.apache.logging.log4j.core.appender.RollingFileAppender.append(RollingFileAppender.java:312) at org.apache.logging.log4j.core.config.AppenderControl.tryCallAppender(AppenderControl.java:161) at org.apache.logging.log4j.core.config.AppenderControl.callAppender0(AppenderControl.java:134) at org.apache.logging.log4j.core.config.AppenderControl.callAppenderPreventRecursion(AppenderControl.java:125) at org.apache.logging.log4j.core.config.AppenderControl.callAppender(AppenderControl.java:89) at org.apache.logging.log4j.core.config.LoggerConfig.callAppenders(LoggerConfig.java:542) at org.apache.logging.log4j.core.async.AsyncLoggerConfig.callAppenders(AsyncLoggerConfig.java:126) at org.apache.logging.log4j.core.config.LoggerConfig.processLogEvent(LoggerConfig.java:500) at org.apache.logging.log4j.core.config.LoggerConfig.log(LoggerConfig.java:483) at org.apache.logging.log4j.core.async.AsyncLoggerConfig.log(AsyncLoggerConfig.java:120) at org.apache.logging.log4j.core.async.AsyncLoggerConfig.logToAsyncLoggerConfigsOnCurrentThread(AsyncLoggerConfig.java:168) at org.apache.logging.log4j.core.async.AsyncLoggerConfigDisruptor$Log4jEventWrapperHandler.onEvent(AsyncLoggerConfigDisruptor.java:112) at org.apache.logging.log4j.core.async.AsyncLoggerConfigDisruptor$Log4jEventWrapperHandler.onEvent(AsyncLoggerConfigDisruptor.java:98) at com.lmax.disruptor.BatchEventProcessor.processEvents(BatchEventProcessor.java:168) at com.lmax.disruptor.BatchEventProcessor.run(BatchEventProcessor.java:125) at java.base/java.lang.Thread.run(Thread.java:833) Caused by: java.io.IOException: No space left on device at java.base/java.io.FileOutputStream.writeBytes(Native Method) at java.base/java.io.FileOutputStream.write(FileOutputStream.java:349) at org.apache.logging.log4j.core.appender.OutputStreamManager.writeToDestination(OutputStreamManager.java:250) ... 23 more

The container is broken for me " text error warn system array login tar: html/Omada.png: Cannot write: No space left on device tar: html/echarts.min.js: Cannot write: No space left on device tar: html/logo.png: Cannot write: No space left on device tar: Exiting with failure status due to previous errors /entrypoint.sh: line 301: echo: write error: No space left on device INFO: Validating user/group (omada:omada) exists with correct UID/GID (508:508) INFO: Group (omada) doesn't exist; creating INFO: User (omada) doesn't exist; creating INFO: Time zone set to 'America/Los_Angeles' INFO: Setting 'manage.http.port' to 18088 in omada.properties INFO: Setting 'manage.https.port' to 18043 in omada.properties INFO: Setting 'portal.http.port' to 18088 in omada.properties INFO: Setting 'portal.https.port' to 18843 in omada.properties INFO: Value of 'port.adopt.v1' already set to 29812 in omada.properties INFO: Value of 'port.app.discovery' already set to 27001 in omada.properties INFO: Value of 'port.upgrade.v1' already set to 29813 in omada.properties INFO: Value of 'port.manager.v1' already set to 29811 in omada.properties INFO: Value of 'port.manager.v2' already set to 29814 in omada.properties INFO: Value of 'port.discovery' already set to 29810 in omada.properties INFO: Value of 'port.transfer.v2' already set to 29815 in omada.properties INFO: Value of 'port.rtty' already set to 29816 in omada.properties INFO: Report HTML directory missing; extracting backup to '/opt/tplink/EAPController/data/html' html/ html/Omada.png html/echarts.min.js html/logo.png INFO: Validating user/group (omada:omada) exists with correct UID/GID (508:508) INFO: Group (omada) exists; skipping creation INFO: User (omada) exists; skipping creation INFO: Time zone set to 'America/Los_Angeles' INFO: Value of 'manage.http.port' already set to 18088 in omada.properties INFO: Value of 'manage.https.port' already set to 18043 in omada.properties INFO: Value of 'portal.http.port' already set to 18088 in omada.properties INFO: Value of 'portal.https.port' already set to 18843 in omada.properties INFO: Value of 'port.adopt.v1' already set to 29812 in omada.properties INFO: Value of 'port.app.discovery' already set to 27001 in omada.properties INFO: Value of 'port.upgrade.v1' already set to 29813 in omada.properties INFO: Value of 'port.manager.v1' already set to 29811 in omada.properties INFO: Value of 'port.manager.v2' already set to 29814 in omada.properties INFO: Value of 'port.discovery' already set to 29810 in omada.properties INFO: Value of 'port.transfer.v2' already set to 29815 in omada.properties INFO: Value of 'port.rtty' already set to 29816 in omada.properties INFO: Report PDF directory missing; creating '/opt/tplink/EAPController/data/pdf' WARN: Ownership not set correctly on '/opt/tplink/EAPController/data'; setting correct ownership (omada:omada) WARN: Ownership not set correctly on '/opt/tplink/EAPController/logs'; setting correct ownership (omada:omada) WARN: Ownership not set correctly on '/opt/tplink/EAPController/properties'; setting correct ownership (omada:omada) INFO: Database directory missing; creating '/opt/tplink/EAPController/data/db' done INFO: Version check passed; image version (5.12.7) >= the last version ran (0.0.0); writing image version to last ran file... text error warn system array login tar: html/Omada.png: Cannot write: No space left on device tar: html/echarts.min.js: Cannot write: No space left on device tar: html/logo.png: Cannot write: No space left on device tar: Exiting with failure status due to previous errors /entrypoint.sh: line 301: echo: write error: No space left on device INFO: Validating user/group (omada:omada) exists with correct UID/GID (508:508) INFO: Group (omada) doesn't exist; creating INFO: User (omada) doesn't exist; creating INFO: Time zone set to 'America/Los_Angeles' INFO: Setting 'manage.http.port' to 18088 in omada.properties INFO: Setting 'manage.https.port' to 18043 in omada.properties INFO: Setting 'portal.http.port' to 18088 in omada.properties INFO: Setting 'portal.https.port' to 18843 in omada.properties INFO: Value of 'port.adopt.v1' already set to 29812 in omada.properties INFO: Value of 'port.app.discovery' already set to 27001 in omada.properties INFO: Value of 'port.upgrade.v1' already set to 29813 in omada.properties INFO: Value of 'port.manager.v1' already set to 29811 in omada.properties INFO: Value of 'port.manager.v2' already set to 29814 in omada.properties INFO: Value of 'port.discovery' already set to 29810 in omada.properties INFO: Value of 'port.transfer.v2' already set to 29815 in omada.properties INFO: Value of 'port.rtty' already set to 29816 in omada.properties INFO: Report HTML directory missing; extracting backup to '/opt/tplink/EAPController/data/html' html/ html/Omada.png html/echarts.min.js html/logo.png INFO: Validating user/group (omada:omada) exists with correct UID/GID (508:508) INFO: Group (omada) exists; skipping creation INFO: User (omada) exists; skipping creation INFO: Time zone set to 'America/Los_Angeles' INFO: Value of 'manage.http.port' already set to 18088 in omada.properties INFO: Value of 'manage.https.port' already set to 18043 in omada.properties INFO: Value of 'portal.http.port' already set to 18088 in omada.properties INFO: Value of 'portal.https.port' already set to 18843 in omada.properties INFO: Value of 'port.adopt.v1' already set to 29812 in omada.properties INFO: Value of 'port.app.discovery' already set to 27001 in omada.properties INFO: Value of 'port.upgrade.v1' already set to 29813 in omada.properties INFO: Value of 'port.manager.v1' already set to 29811 in omada.properties INFO: Value of 'port.manager.v2' already set to 29814 in omada.properties INFO: Value of 'port.discovery' already set to 29810 in omada.properties INFO: Value of 'port.transfer.v2' already set to 29815 in omada.properties INFO: Value of 'port.rtty' already set to 29816 in omada.properties INFO: Report PDF directory missing; creating '/opt/tplink/EAPController/data/pdf' WARN: Ownership not set correctly on '/opt/tplink/EAPController/data'; setting correct ownership (omada:omada) WARN: Ownership not set correctly on '/opt/tplink/EAPController/logs'; setting correct ownership (omada:omada) WARN: Ownership not set correctly on '/opt/tplink/EAPController/properties'; setting correct ownership (omada:omada) INFO: Database directory missing; creating '/opt/tplink/EAPController/data/db' done INFO: Version check passed; image version (5.12.7) >= the last version ran (0.0.0); writing image version to last ran file...

/usr/local/sbin/shfs /mnt/ -disks 63 -o default permissions,allow other, noatime -o remember=0 /usr/bin/dockerd -p /var/run/dockerd.pid --log-optt max-size=500m --log-opt max-file=1 --log-level=fatal -storage-driver=btrfs Here's an HTOP of what I'm seeing. I've also attached server logs. Any ideas? Anything to optimize? unraid-diagnostics-20230526-1530.zip

Containers that have a version with a single character give me the error "Please match the requested format" I see this with AlmaLinux and RockyLinux. Is there a format that I overlooked for these versions?

6.11.0-rc5 to 6.11.0. Ran the updater, let it do it's prep and rebooted when I was given the Update Ready/Reboot banner. I've had the warning about NerdPack since the initial 6.11.0-RC, but I don't even remember what I used NerdPack for and everything seems to be working fine. I'll update if I find anything. NVIDIA Quadro P600 had no problem with the update for me. Thank you. Every day I feel I got my monies worth on this OS. Great responsive community. I don't see myself going back to any other.

Pretty sure I just bricked my card. The firmware was out of date. I followed instructions to a T deleting old firmware using FreeDOS, then loading up new firmware with sas2flash, I assured it was using the proper firmware,... But after shutting down and moving systems, it no longer boots with any system. At this point, I don't feel comfortable with sas cards. They are supposed to be more reliable than just a pcie to sata, right? I'm thinking of just going with this: https://www.amazon.com/gp/aw/d/B09K4WKHKK/ref=ox_sc_act_image_1?smid=A30D00PBBJUKCM&psc=1 Any downside to the ASM1166? This one should just drop in and work, right? No speed difference? I have two potentially dead cards if anyone wants them.

It was supposed to be pre-flashed https://www.amazon.com/dp/B08QJCQ76S?psc=1&ref=ppx_yo2ov_dt_b_product_details I'm guessing next step is to follow this guide and make sure it actually has proper firmware? I do also see people saying they have problems with the first slot, so I may try moving that.

Alright, new day, new card. @JorgeB Today I have a Broadcom / LSI MegaRAID SAS 9240-8i, which you can see in LSPCI. The drive still isn't showing up however. Any tips? I'm completely new to RAID cards, so maybe switching to IT mode went wrong? How can I assure that? Any other suggestions? unraid-diagnostics-20220821-1410.zip

You're right, I'll remember to get that right on my initial post at some point. Thank you. Going through lcscsi.txt and lspci.txt, I don't see anything related to adaptec. What do we look for here? unraid-diagnostics-20220820-0247.zip

I thought I read everything I needed before buying this Adaptec 71605 and an additional 16TB Exos drive. I've filled all the sata ports on my B550 VISION D-P MB and thought this would be the next step to adding storage. Problem is, I see the light on the card and I can hear/feel the drive spin up, but I don't get any new drive information. I don't even know what to look for anymore as I've started getting desperate downloading old storage manager applications. I can't get the card to work on my windows machine either. Shamelessly... where do I need to start?

Unraid OS: 6.10.2 Plex Version: 4.76.1 The server is on my local network. Unraid is .2 and Plex is .3 I tried SSL versions as well.

Been having trouble lately @dorgan Sometimes the streams show properly, other times I see double entries. Today, I noticed that there's definitely streams running, but the plugin isn't picking them up. In the plugin settings, I removed the token entirely, saved, then grabbed the token again using the "Get Plex Token" button, no problem. The plugin finds the local IP, External IP, and External Domain name. I select Local IP and Save, and then the entire server gets sluggish. If I'm quick and refresh the Plex Streams Dashboard or NAV just as I save I can catch active streams, but refreshing again.. the server is still being slow...eventually the page refreshes and I no longer notice a slowdown to the unraid gui, but the streams do not show in the Dashboard or NAV. Let me know if you need any info from my server to help, if you don't mind helping. Thanks!

Fan Control isn't working for me either and I've done quite of bit of reading. sensors-detect detected things, sensors shows the results. You can see attached. I was then able to detect and load the driver in Dynamix System Temp but PWM and Fan Speeds don't seem to be detected. Ideas? I attached the log and saw errors, but at this point am tired of running in circles with searches, what do those mean? M/B: ASUSTeK COMPUTER INC. STRIX Z270I GAMING Version Rev X.0x BIOS: American Megatrends Inc. Version 1205. Dated: 05/11/2018 CPU: Intel® Core™ i7-7700T CPU @ 2.90GHz HVM: Enabled IOMMU: Enabled Cache: 256 KiB, 1 MB, 8 MB Memory: 16 GiB DDR4 (max. installable capacity 32 GiB) Network: bond0: fault-tolerance (active-backup), mtu 1500 eth0: 1000 Mbps, full duplex, mtu 1500 Kernel: Linux 5.10.28-Unraid x86_64 System Temp Available drivers: Coretemp nct6775 Sensors Processor temperature: coretemp Mainboard temperature: acpitz Array fan speed: None Fan Auto Control autofan version: 1.6 Fan control function: Enabled PWM controller: None (None in the drop down) PWM fan: Detect blanked out Minimum PWM value: Detect blanked out Low temperature threshold (°C): High temperature threshold (°C): Refresh interval (minutes): Exclude drives: None sensordetectandsensors.txt livelog.txt

You're awesome. Thank you. For future searches: Unraid > Community Apps > Settings > Allow install of second instance: YES

Great looking overhaul on the new Community Apps. One problem, if a container is already installed I have no way of installing a second instance of that container from Community Apps as the install button disappears once CA recognizes a single instance of the container already installed.

I was running a Valheim Server and was convinced I should turn up an Ark server. From Community Apps the Ark docker said update steamcmd, then it allowed me to install so I did. It then failed the Valheim server. With a restart of Valheim, I'm getting: "Connecting anonymously to Steam Public...Retrying. . . Warning: failed to init SDL thread priority manager: SDL not found " Full log: https://pastebin.com/cBzueCAu Update: no SteamCMD related containers work, all give similar errors.

Thank you, @trurl Reference for anyone else reading this in the future. In Unraid, Go to the Shares tab, Click your share(in my case UnraidNAS), and Change "Use cache pool (for new files/directories):" to 'NO', then Apply your change. Then, move the files to /mnt/user/UnraidNAS/ (/mnt/user/ is where you should be mounting to, for any share) Once the file transfer is complete, go back to Shares, and enable the cache pool.

Hi! I'm new to the storage array scene. I recently purchased (4) 16TB drives, 1 for parity, the drives are in a share called UnraidNAS. Before buying these drives I have been using a WDNAS drive that I was able to mount to the Unraid server at /mnt/remotes/WDNAS_Public/ Within WDNAS, I have a PLEX folder that holds a folder structure of my media. My questions are, When moving the PLEX folder from WDNAS, what is the proper location to move this to? It's about 7.1TB of data, and I have a 1TB NVME Cache. I would want to skip cache for bulk moves, correct? Would I SSH, and use 'cp -rg /mnt/remotes/WDNAS_Public/PLEX /mnt/user0/UnraidNAS' to mitigate filling up the cache? Or is it better to go 'cp -rg /mnt/remotes/WDNAS_Public/PLEX /mnt/disk1/UnraidNAS' , straight to disk1? For clarity, since the above question is about a bulk move, it is true that /mnt/nas/UnraidNAS/ is what I would link 99% of the time to my containers so that it quickly gets moved to cache, and scheduled to be moved by the scheduler, correct? Is there a fix for the bug where if you move files from disk1 to user, you lose your data? Thank you.