tropical b

Members
  • Posts

    16
  • Joined

Recent Profile Visitors

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

tropical b's Achievements

Newbie

Newbie (1/14)

5

Reputation

  1. Updated from 6.11.1 to 6.11.4 with no issues at all. Thanks team! ๐Ÿคฉ
  2. Pretty sure I saw this issue with 6.10 as well. The first thing I tried was adjusting the font size in display settings.. didn't correct the problem. I had to disable the duckduckgo extension to fix the weird font display issue. Not sure why the duckduckgo extension caused that, but happy to have the font look good again!
  3. It's a hard drive, yes? Wouldn't it just work? ๐Ÿ˜‡ I'm using the SATA version of the Seagate Exos X18 without any issues... this one: https://www.seagate.com/products/enterprise-drives/exos-x/x18/
  4. Thanks so much! This fixed the issue for me. ๐Ÿ‘๐Ÿคฉ
  5. Thanks @wgstarks. I think I found it (link below), and maybe I will try installing screen at some point. I haven't used it for a few months so am not sure it is worth the effort do manually. I do think that link will be handy to bookmark for future reference, in case I would like to try to install a slackware package that is not natively installed or unavailable via Community Applications. Appreciate the note about tmux. I had no idea what this was; never heard of it. Tried it out after reviewing the below reference and I think this will be what I use in the future, if I ever need to use multiple windows in a command line session. I have used screen for years so tmux is a bit different, but it seems more powerful as well. I will just need to keep the cheat sheet handy (provided in the very helpful link below). Thanks again!! https://linuxhandbook.com/tmux/
  6. I posted my comment below. Thanks for considering my feature request. Appreciate @wgstarks suggesting I post it here! ๐Ÿ‘
  7. Upgrade to 6.11.0 worked well for me, though I learned after upgrading via FixCommonProblems that nerdpack isn't supported anymore.. rather unfortunate to have this discovery after the fact. I reviewed the release notes before upgrading and there was no mention of this. ๐Ÿค” I was luckily only using nerdpack for fan speed monitoring and screen on the terminal. I see now that the fan monitoring is still working ok, but screen is gone... so I probably won't bother to install screen since I didn't use it very much anyway. But it would be much appreciated to have advance notice of this for future Unraid releases. Otherwise, smooth upgrade; thanks Limetech! I know there are a lot of moving parts for these releases so understand stuff like this can happen. ๐Ÿ˜ป If I decide to try to install screen, I saw this post shows how to install packages that nerdpack helped install before and may try it out:
  8. I was also unaware of Nerdpack not being supported anymore, and didn't see this until after upgrading to UnRaid 6.11.0 (which fortunately went smoothly). I was using Nerdpack for fan speed monitoring and the screen application. After updating I received a notification from FixCommonProblems that Nerdpack was incompatible (!!). So, I uninstalled it. Fortunately no impact seen to fan speed monitoring, but of course the screen program is now gone. I thought about it a bit and don't use screen much, so not sure if I am going to bother installing that. Would be appreciated for Limetech to inform their users of these major changes in the release notes... ๐Ÿ˜ผ
  9. Fantastic, easy to understand guide. Thank you @lotetreemedia! ๐Ÿ˜
  10. Adding my experience: Reasonably smooth upgrade from 6.9.2 -> 6.10.2. Thanks to @SimonF for helping me figure out why local GUI wasn't working when booting with a monitor connected to my Nvidia graphics card (the i915 driver (Intel integrated GPU is enabled by default as of version 6.10.0). I was running version 6.9.2 & read release notes only for 6.10.2 before upgrade. What I should have done was read release notes for all versions up to the one I was upgrading to; so, should have also read release notes for 6.10.0 & 6.10.1 as well. To help people like me in the future who may not remember this โ˜บ๏ธ, may I suggest including the link to the Unraid release notes page in future OS update notices & reminding folks to review for changes to minimize surprises? This could help others save some time, in case they move from one update to another and don't immediately think to check all the release notes up to the version they are moving to. Link to release notes: https://wiki.unraid.net/Manual/Release_Notes. I've been using 6.10.2 a bit more than 12 hours and so far it is working well. Thanks very much for all the hard work on the new release!
  11. Thank you, @SimonF! I recently upgraded from 6.9 to 6.10.2, and was not understanding why I couldn't get the GUI to show up locally. I have an Intel HD 530 iGPU (which I totally forgot about) and an Nvidia GT730. I have my monitor hooked up to the Nvidia card, so when booting up I saw everything loading fine.. then right after loading samba the screen blanks and I just see a blinking underline cursor. Even in GUI w/safe mode. So I missed this note about the i915 driver being loaded by default. I am not using the i915 for anything (no transcoding, etc). So I'm happy with this solution. Thanks!
  12. Thanks @trurl! I marked your post as the solution. ๐Ÿ‘ Appreciate you sharing your insight!
  13. Hi @trurl, thanks for the suggestion. I have resolved the issue. ๐Ÿ˜ I reviewed the diagnostics and everything looked OK, so thought I'd try a reboot. Rebooting ran the Fix Common Problems Community App (thanks @Squid!), which informed me Share system is set to cache only, but files / folders exist on the array. I corrected by following the steps in this topic: After running mover (I had logging enabled to confirm which files it moved), I then set the share to Only: Cache. Checked mover log and confirmed it moved the docker.img and a vm image file to the cache drive. This issue arose because I set up Unraid without a cache at first.. set up docker.. then added cache NVME pool. After doing that somehow the docker/VM images files got "stuck" on the array, so whenever I would run a Docker app it would access the docker.img file on the array, and I would hear the drives being pinged every 3-4 seconds. Now the docker/VM content is properly stored on the cache pool & I have set the docker/VM shares properly to use only the cache. And when I run docker, I hear nothing but SILENCE! Thanks for the suggestion of using the diagnostics, as it did tell me much more about the system and the way it is configured. And it led me to the eventual solution! I also changed the "Fix Common Problems" app to run every day. That way if something weird occurs I don't have to wait for a reboot to find it. (As before the app was set to only run on bootup). Thanks all.
  14. Hi everyone, I've been using Unraid for about a month and this is my first post! Great product and I am enjoying it so far. The documentation is wonderful and it has been a great experience setting up my own NAS using some spare hardware. It feels good to re-purpose an old PC! One question about Docker: Why are my docker containers frequently accessing the physical disks, when they should be using cache? I have reviewed the docker reference and don't understand why this is happening. https://wiki.unraid.net/Manual/Docker_Management More details: I have a 1TB cache pool (two NVME drives) & I have set up the appdata, domains and system shares to "Prefer: Cache" setting. I understand this to mean that new content for Docker would write to cache, *except* if cache pool fills up. If that happens then Docker content would write to the array, then when mover executes, it would move from array to cache pool (again, provided there is space on the cache). So with this config, I start up two Docker containers, and immediately I hear the physical disks (spindle drives) working every 4 seconds or so. If I stop the Docker containers, the physical disks are quiet and I don't hear them. I would think if I have Docker shares set up to "Prefer: Cache" and cache pool is nearly empty (confirmed during testing cache it had over 900GB of free space), there would be no reason for Docker to write to or access the physical disks. Is everything set up properly and this is the way it is supposed to work? Or do I need to change some settings somewhere? Appreciate any suggestions. Thanks!