SphericalRedundancy

Members
  • Content Count

    23
  • Joined

  • Last visited

Community Reputation

1 Neutral

About SphericalRedundancy

  • Rank
    Newbie

Converted

  • Gender
    Male

Recent Profile Visitors

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

  1. I currently have 8 NFS shares that are all working as expected configured as a private NFS share but I noticed today when I attempted to add a 9th NFS share that although the entry gets added to the /etc/exports file it does not actually export the new share as shown by showmount or exportfs -v. I noticed that when I run exportfs -ra to re-initilize the NFS service and have it export shares configured in /etc/exports it shows an error message about incorrect syntax for a bad option list. This points to line 9 in the /etc/exports file but line 9 is a complet
  2. Is there a way to update to a version that's above 6.5.3 but isn't 6.6.5? My server has been running smoothly for months and I avoided updating because I wanted to wait until 6.6.X was cleaned up of any of the bigger bugs but when I updated to 6.6.5 last week my server has crashed everyday since, downgrading to 6.5.3 and it no longer happens. I'd like to update to something other than 6.6.5 so that maybe I can narrow down which update is affecting me.
  3. Yea it's on lan, was using chrome, same thing for firefox though.
  4. So I just did this and its all working great except that after I installed the red hat qxl display controller driver, the black border around my mouse cursor was removed. So when I mouse over the file explorer, or anything that's got a white background, I can't see my mouse at all. Anyone got any ideas?
  5. Is it normally so slow? It takes several seconds after clicking or typing for anything to happen.
  6. I guess they could also implement logic to only move to cache if moving to a different drive and skip cache if moving to the same disk just a different folder. For now I guess I'll have to move share B to an unassigned device since I don't actually care about it being protected. I assume since that is outside of the array that I'd then be able to transfer to share A and it'd use the cache drive?
  7. So I've got 8 data drives, a parity drive, and a cache drive. So lets say I have two shares, share A is set as yes to use the cache drive while share B is set to not use it at all. I will sometimes need to transfer large (100 GB or more) folders from share B to the share A. Whenever I do this the transfer speed is very slow ranging from 5MB/s to 10MB/s and as far as I can tell this is because share B is not only writing to share A but also the parity. Why doesn't share B transfer to the cache drive first since share A is set to use it?
  8. Why is the drive temperature shown as an asterisk here? Happens to the bottom two drives sometimes.
  9. Gotcha, so yeah I did have it set incorrectly. Is there a way to have unraid move the files around again so they follow the new split level rules?
  10. The folders I copied were all tv shows for a single share and the share is set as follows. So that would be an example of how I have the tv share laid out, tv (share name) > type > bunch of different shows per type > season folders per show I have it set to split at level 2 which I think would only keep the season folders together? although based on your previous sentence and calling the share name itself the top level maybe it should be set to split at level 3?
  11. So I must be doing something wrong. Why is unRAID doing this? I moved a bunch of folders onto my cache drive totally about 750GB (my cache is 1TB) and before moving it disk 1 had about 900GB available and it seems like unRAID decided to move it all to one drive and I have no idea why. I'm pretty sure I have my split level set right on my shares but I don't know at this point.
  12. When there are updates for docker images and you run the update for all containers, if your time is off the docker pull/run command will fail because of a cert error but it will not display in the log shown, it'll show 0 bits pulled for the new image and rebuild the container using the existing image and show the update as successful even though no update has been applied.
  13. So I'm fairly new to unRAID and I'm in the process of transferring my current setup over to unRAID. I'm also used to using docker compose where you plan it all out very easily. So color me surprised when my Plex container, that was running fine, got completely wiped out after one failed re-run because I typed one of the volume paths incorrectly. Maybe I'm doing something wrong but if not, the idea that one failed run of a container deletes all the port, variable, and volume information is completely insane to me. Don't get me wrong, I understand that unRAID