Hoopster

Depends on when they were formatted with XFS. I don't remember exactly when XFS started taking much more space than it used to, but it has been about two years, I think. There are some posts in the forums about it as many started noticing what you did; a relatively large amount of space taken on a newly formatted disk.

I have two Kingston MobileLites in use on Unraid servers; one G2 and one G3. They both have worked flawlessly for many years. Those are no longer available (not even on eBay last I checked). As to the other card readers that fall under the MobileLite family, some work well with Unraid (unique GUID) and some do not. There seem to be a lot of counterfeit flash drives these days as well and those always seem to have generic GUIDs. It much more of a crap shoot than it used to be.

That is just the space taken up by the XFS file system. There is no data on the disk. The file system supports a lot of new features now that take up some space when the disk is formatted.

It's not complicated. How did you create the Unraid boot flash?

Been posted a few times. Here is the fix, it worked for me.

You want AHCI

You have to select the setting icon (wrench) first in the upper right corner. Your prior screen shot shows that is there.

I don't think so. My Plex installation is working perfectly and it also shows the question marks for Plex in docker allocations.

Select the Settings Icon in upper right corner: Then on the left side, you should see a menu like this with Remote Access under Settings:

Did you lose local access via the Web GUI, remote access via the forwarded port or both? Does Plex say it is accessible remotely? For better support of a particular Plex docker application, you should post your question in the support thread for that docker application.

Thanks. Somehow I missed previous mentions of the issue.

A few days ago, I started receiving email messages from Unraid with the following "error." cron for user root /usr/bin/run-parts /etc/cron.daily 1> /dev/null warning: Potentially dangerous mode on unraid-api: 0666 error: Ignoring unraid-api because it is writable by group or others. error: found error in file unraid-api, skipping warning: Potentially dangerous mode on unraid-api.patch: 0666 error: Ignoring unraid-api.patch because it is writable by group or others. error: found error in file unraid-api.patch, skipping I am not sure to what it refers. Is this any cause for concern?

@Maximo101 As Trurl has pointed out, Unraid often has issues with SATA cards based on Marvell controllers. It is not just Unraid as it a general issues with Marvell drivers for Linux. I have a 6-port IO Crest SATA card that worked great with earlier version of Unraid but as the kernel changes happened, issues started popping up. That's when I replaced it with the Dell H310 HBA that I got very cheap on eBay.

My HDD temps are very good after a few modifications. During parity check or extended disk activity, the hottest temperature I have see on any drive is ~46C. During "normal" use, I see HDD temps from mid 30s to low 40s (36-43C range) See this forum discussion for some worthwhile modifications that increase cooling in the case. I posted a lot in that thread. In addition to the modifications mentioned in the first few posts, here is a summary of what I put in the case. I have been very happy with the case for about 6 1/2 years now. SATA cable to each drive in hot-swap cages connected either directly from motherboard and/or HBA (I have a Dell 310). Power to the hot-swap cages is via Molex power cables from PSU. There is a smaller Silverstone NAS case that had some well-documented cooling issues but the CS380 is not terrible; however, it can be improved with the mods mentioned above. As far as room in the case, I currently have a Micro-ATX motherboard in the case but it can fit a full ATX motherboard. I would not use a motherboard with SATA connectors aligned vertically on the edge of the board. There is little room between the edge of the board and the hot-swap cages. Use a motherboard with SATA ports on the board surface that face upwards.

Since you are new here (relatively) it is time to introduce you to the concept of "Soon" The Unraid team never sets release dates for any version of Unraid whether it is a beta or the final release. If you are waiting for something in the future (like 7.1), "soon" is all you are going to get as far as timing. It gets released when the team feels it is ready. "Soon" can be days, weeks, or months.

Same here. I see it on boot but it does not get stuck here; maybe 3-5 seconds before it moves on and boots normally. Not much of a solution for the OP, but it seems to be a "normal" error. Getting stuck, of course, is not normal.

Docker Image for me. Only once have I experienced a corrupt docker image file requiring deletion, recreation and Previous Apps to bring it all back. I have been using Docker since it was first introduced in Unraid.

Found the problem. Somehow Disk 5 was excluded in global share settings. Nothing I remember doing, but, that was the case.

I have an array with 5 disks. When I go to share settings to set which disks to include in the share, only Disk 1 to Disk 4 appear in the dropdowns for included and excluded disks. Setting a share to All only includes those 4 disks. As seen below, there are 5 disks in the array and all show green balls. There is probably an answer already posted somewhere in the forums but I am being lazy right now as I am headed out the door for a few hours.

Because I can 😀 Actually, I just discovered the Site-to-Site VPN capabilities of my routers and set it up just last week. It was super easy and is based on WireGuard. I do not have a lot of experience with it yet but I m about to move my backup server down to our second home this week and I will be trying it out a lot more. I intend to do unattended Unraid to Unraid server backups over Site Magic utilizing User Scripts and the IPMI capabilities of the servers. WireGuard on the 24x7 Unraid server is what I have been using for years for remote LAN access to Unraid and other resources on the same LAN. I also included my docker container VLAN subnet (192.168.3.0/24) in the allowed IP addresses for the WireGuard client devices (phones, laptops, PCs, tablets) from which I access the LAN and VLAN remotely. It works great. WireGuard on a Raspberry Pi in the LAN is my backup entry point in case there is an issue with it on the Unraid server. For this setup, I have two ports forwarded in my router, one for WireGuard on Unraid and one for WireGuard on the RPi. I am not as familiar with Tailscale use as I just started using it recently but it is also based on WireGuard.

I currently do it both ways. I am not into the reverse proxy thing like many are but, what I have done so far works well and seems fairly secure. I have had no issues. i started by doing OpenVPN and ZeroTier on the Unraid server. I always seemed to use OpenVPN and rarely used ZeroTier (no particular reason). The past couple of years, I migrated almost exclusively to WireGuard on Unraid setup to allow access to anything on the LAN plus my VLAN (it is in the allowed IP address ranges) on which I put my docker containers. As a backup, I have WireGuard installed on a Raspberry Pi on the LAN in case the Unraid server is down. It is usually on 24x7, but if a power outage occurs, I need to get into the LAN a different way as I do not have the Unraid server set to automatically boot when power is restored. When Tailscale integration with Unraid came along, I set that up as well. Recently, I discovered that my router/gateway (Ubiquiti UniFi Cloud Gateway Ultra) has an SD-WAN site-to-site VPN feature built in so I use that between the networks in my two homes. I can also include the docker VLAN so I can access anything on 3-4 related LANs/VLANs securely. It uses Wireguard tunnels. Basically, I have four ways to access LAN resources and all work great and securely. WireGuard on one of two Unraid servers for LAN-specific access Wireguard on a Raspberry Pi on either LAN for LAN-specific access Tailscale on Unraid servers as well as many other devices for access to resources on either site Site Magic Site-to-Site VPN (WireGuard) on routers for access to anything on LANs/VLANs in two different sites Wireguard requires forwarding a single port and client configuration Tailscale requires no port forwarding but requires "setup" of devices in the Tailscale network Site Magic requires no port forwarding and no client setup

I agree with this and thank you. I switched to this image ASAP after Linuxserver announced the dual docker approach to the UniFi controller. I have several current docker containers from Linuxserver installed in Unraid (also a couple from Binhex) but I may also look into switching. I was very, very happy with this image as long as I was using it which was until very recently. I only went away from it when UniFi implemented Site Magic (super easy SD-WAN site--to-site VPN) and the UniFi routers/gateways i chose to use at both sites required use of their built-in controller. For anyone looking for a UniFi controller Docker container, I see no reason to not use this one.

I have been doing rsync backup between my main and backup servers for years. The backup server is off until powered on via IPMI. It is automated and works great but both servers have been in the same LAN. Ideally, the backup would be offsite in a different location than the source. We recently purchased another home 270 miles away so I am moving my backup server there. Requirements for Off-Site backup: Backup server powered off when we are not in the "remote" home until backup is needed Secure/encrypted connection between LANs at source and backup location Ability to continue to power backup server on/off via IPMI Remain completely automated with no user intervention required as it is now I looked into how to establish a Wireguard, Tailscale or site-to-site VPN connection between the two locations via the backup script. Although I think this is possible, it was not totally straightforward and I was spinning my wheels a bit. UniFi Site Manager already lets me manage both LANs remotely via Teleport as I have UniFi Cloud Gateway Ultra routers/gateways in both locations. While doing some minor configuration changes on both LANs, I came across the Site Magic SD-WAN capability in Site Manager. With a few clicks, I had both LANs linked in a mesh configuration. It was super easy. I can now access devices/resources on either LAN as if they were all local. Site Magic creates Wireguard encrypted tunnels. I have yet to try the backup to a remote server as I have not moved the backup server, but, all indications are it should work seamlessly. [UPDATE]: Remote backup works as expected. I just had to make sure the target server was recognized by the source server for automated SSH purposes. Here are the two sites linked in what I called MadMesh: Requirements to use Site Magic: Ubiquiti routers/gateways from a list of supported devices (the older USG is not supported) At least one gateway with a public IP address (both of mine have public IP). A change in public IP address by ISP is automatically supported. Non-overlapping subnets (mesh configuration) Same owner for all included sites Site Magic SD-WAN supports Hub and Spoke and Mesh configurations Complete description is found here.

For years, I have been running a weekly rsync backup from one Unraid server to another via a user script which called ipmitool. ipmitool was part of the Nerd Pack which is no longer supported in Unraid 7.0.0. As it turns out, just installing the version of ipmitool included in Nerd Pack into /boot/extra does not work either because of some library dependencies which have also changed. There is a way around that by downgrading to a 6.x.x version of Unraid, copying the necessary files and then copying them back to the right place after upgrading to Unraid 7.0.0. I did not feel that was a good long-term solution. Instead of ipmitool, I am now using Freeipmi for Slackware. Freeipmi uses the ipmipower command to turn a machine on and off via the on-board IPMI. Accordingly, I had to modify the user script doing the rsync backup on the local LAN to use the new commands and syntax. I replaced this ipmitool command in the script which runs from the source server: ipmitool -I lan -H 192.168.1.17 -U admin -P {password} chassis power on The new command using Freeipmi/ipmipower is: ipmipower -h 192.168.1.17 -u admin -p {password} --on I also needed to modify the shutdown of the target server after the backup is complete. In the user script, I replaced the following ipmitool command: ipmitool -I lan -H 192.168.1.17 -U admin -P {password} chassis power soft The new command using Freeipmi/ipmipower is: ipmipower -h 192.168.1.17 -u admin -p {password} --soft I have yet to work out doing this over the Internet by first establishing a Wireguard or Tailscale connection to the remote target server but that is the next step as the backup target server is being moved 270 miles south of the source server.

Thank you for being on top of these issues and addressing them. Fortunately, all three of my Unraid servers are currently on version 7.0.0. There are some I manage remotely for family and friends that I will need to update.