Hawkins12

Members
  • Posts

    130
  • Joined

  • Last visited

Converted

  • Gender
    Male

Recent Profile Visitors

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

Hawkins12's Achievements

Apprentice

Apprentice (3/14)

7

Reputation

  1. Hmm I'll have to look at that. I guess i always assumed nothing would write to the array if a parity operation was in progress (whether its a check, rebuild, etc.) In fact, I can't manually click the "MOVE" button because it's grayed out and says "Disabled -- Parity operation is running". I didn't realize a background process could trump this.
  2. Perhaps this should go under the "bugs" if it truly is a bug; however, my mover is automatically scheduled to run at 1pm every day. I just replaced two 4TB drives with 2-12TB drives (yea I know I should have done each in separate steps) so at the current time, I have both drives being emulated. The data rebuild is currently at the 7.80TB mark; however, I noticed it really slowed down --- the reason, it looks like Mover ran in the background to move data off of my cache drives and placed data in one of the new 12TB drives I just installed still undergoing a parity rebuild. My question is if a data-rebuild is occuring, why would Mover run while the operation is in progress?
  3. I am looking to stress test a newly purchased HDD but the problem is my server has no additional bay slots. I would love to be able to run the pre-clear feature a couple times as these are "reman certified" drives. I know some of the HDD expansions/enclosures don't read SMART data so while they may be able to test drives, they won't be able to format in a way that's fit for unraid. What do you all do to stress test your drives when your server chassis are all full? I don't want to replace a drive just yet without knowing the new drive is good to go.
  4. Question for the group: I run "Disk Location" plugin. I noticed earlier today, I have a "Warning" on 3 different drives for the same reason --- "Command Timeout is above 5". When looking at these three drives (all Seagate), the command timeout SMART data shows 1 1 1 whereas some other Seagate drives show SMART data of 0 0 0. I am actively preparing replacements at this time but the thing that has me curious is Unraid still reports these drives as "OK". My nightly Unraid report lists all drives and any potentially errors/issues and none are identified. Is there a reason why Unraid doesn't report the "Command Timeout" issue as a pre-failure condition? Anything I should know on this? EDIT - And of course, I should have searched first, asked second. I see Update 2024.02.11 identified this issue and I would need to set to "Disabled". I guess for my education, is this really a pre-warning condition? Should I be concerned? I don't knwo much about this "Command Timeout" line item and curious to understand it and why your plugin sees it as a pre-failure condition but Unraid doesnt?
  5. Thanks for the reply. I think I'll choose the Remote Server and just incorporate my server IP address. Follow up question -- where does the syslog get stored if stick my Unraid server ip address here? Is there a designated place?
  6. I have had a couple crashes lately and believe its related to a specific docker. When I check the syslogs, they are reset upon the reboot. Is there a rolling log somewhere which I can see what was going on just before the system crash (about 8 hrs ago)? Which log would this be? Yes I know I can post diagnostics but would like to try my hand at it first for the learning/growth aspect. Thanks!
  7. Sorry for my silence here. I've been tied up. That being said, I am still receiving and would like to upload Diags; however, concerned about the information in them being uploaded to a public forum (yes I know they can be "anonymized" but that might not remove everything (ie. file names, etc.)) Is there specific logs you'd like to see where I can tailor diagnostics that would be helpful? Also,, I note in "Fix Common Problems", I am getting /var/log is getting full (currently 70 % used) and Docker image file is getting full (currently 85 % used).
  8. I upgraded to Unraid 6.12.6 a few days ago. Ever since upgrading, everyday my email has been bombarded with disk utilization warnings similar to the below. See below for my emails: Unraid seems to report a bunch of disks at high usage and then 1 minute later, report those same disks as normal. Is this a bug? Is there a fix? Thanks!
  9. I am in a bit of a pickle here. I originally installed MariaDB-Official to manage my nextcloud database online. Now I'd like to branch out to different dockers which require databases which I'd like to manage through one Maria-DB docker container (I plan to use adminer to help manage this). That being said, I forgot the or dont recall the root password. Here is my MariaDB setup: I have seen a lot of stuff out there on how to reset the root password by going to Safe Mode, and the --chart tables post arguments but that doesn't seem to be working. Is there a way I can reinstall the MariaDB docker (to reset the random root password) without losing my Nextcloud database? Any advice on how to correct? Thanks!
  10. Thanks for the quick reply. I suspected this was the case. Hopefully someone has experience with this. I did notice this when I looked at the drive attributes: Nothing carried over and is displaying via USB. I think that's pointing towards this strategy not working. I just wanted to buy some Manuf. Recert drives and have them tested first while under warranty but I might have to go another route. That being said, are you aware of any USB solutions that may work for my use case? Note that I don't want to run a drive off USB within the array -- simply preclear/test prior to deploying into the server at some future date.
  11. My unraid server drive bays are 100% full. Because of my desire to have backup HDD's ready to go, I decided to buy a Sabrent HDD Enclosure that plugs in via USB to the unraid server. The purpose of this is to buy additional drives, preclear those drives, and have them ready to go in case of failure so downtime/time necessary to rewrite a failed hdd would be as limited as possible. That being said, when I tried my first HDD preclear, I see the following in Unraid Note that I am actually preclearing a WD 2TB HDD that was actually deployed in the server previously and replaced. When the drive was deployed it looked something like : (yes I know this is a 6TB but only provided for purposes of illustration. Now this reminds me when I would buy the WD HDD's shuckable drives. I would leave them in the enclosures while I ran the preclear 2-3 times so it would be easier to return (or to prevent any hassle from trying to return a shucked drive). It's been a while since I've done this and the new unraid is here with more Preclear settings than previously. My question is that once this drive is erased/precleared, will it be hot swappable (if I don't use the Sabrent Enclosure)? Will Unraid recognize that the drive is prepped even if it isn't in the Sabrent enclosure? Am I overthinking this altogether? I was planning to buy some 14TB drives so the future disk replacements could take quite a while which is why I was testing on my 2TB spare drive for now. Thanks!
  12. I am presently having an issue with passing a docker GUI through a VPN. Historically, I've used the docker "nordvpn" and then passed "qBittorrent" through that docker with 100% success. I've been able to access the gui from my home PC and things worked just fine. Recent;y the docker "nordvpn" has not been updated and I can't even see it in the "app store". I've since switched to the docker "nordlynx" which is basically the same as before; however, I am having complications accessing the webgui. Note that the docker is starting and actually passing through as my curl ifconfig.io command is providing the same VPN IP for both nordlynx and qBitttorrent. In addition, I know qBittorrent is working in the background -- just the gui is not working. Here are my current settings: As mentioned, these settings are exactly the same as what worked for "nordvpn" docker. Yes the "nordvpn" docker is turned off and not in use. What could I be missing or doing wrong?
  13. Shame on me for updating. I updated docker yesterday and it no longer works. Then there was another update today which I presumed fixed the issue -- no avail. Docker doesn't connect to Nord. Any solutions? Note that logs show: A new version of NordVPN is available! Please update the application. New feature - Meshnet! Link remote devices in Meshnet to connect to them directly over encrypted private tunnels, and route your traffic through another device. Use the `nordvpn meshnet --help` command to get started. Learn more: https://nordvpn.com/features/meshnet/ Connecting to United States #9895 (us9895.nordvpn.com) You are connected to United States #9895 (us9895.nordvpn.com)! However, curl ifconfig.io yields no connection to the outside network.
  14. Sorry for my delayed response. Because I only had a small bit of files, I downloaded the backups on my PC and transferred them back to Unraid. Not the most ideal but I am not a big tech/code guy to understand all the behind-the-scenes permission issues. And calling support I didn't feel viable as the person would not understand Unraid or how it all works.
  15. thanks for this. I was baffled myself! Question -- Does this impact current functionality of the Docker? I suspect it doesn't, but figured I'd ask.