RealActorRob

Members
  • Posts

    64
  • Joined

  • Last visited

Recent Profile Visitors

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

RealActorRob's Achievements

Rookie

Rookie (2/14)

4

Reputation

  1. Got it running. Notes and a YouTube video to follow. Using XMrig CPU only just to get it going. First note, 3GB of RAM is enough. Have 300+mb left over. I suppose this might not be enough for GPU mining, but it's fine for CPU XMR mining.
  2. I gave up and got HiveOS installed in a VM.
  3. I'm thinking I need to allocate more resources to the Container....gotta research that. Every time I go to CA and pull it, it just more or less stops updating during the install. Sometimes it's running, sometimes not. When I edited it last time, it just left me with an orphan image. Where should I look in the logs/start? EDIT: Here's something: Sep 11 22:08:01 BlackTower nginx: 2021/09/11 22:08:01 [error] 8214#8214: *63500 upstream timed out (110: Connection timed out) while reading upstream, client: 2600:1700:4c60:e8f0:f1ab:d0ad:81bd:db28, server: , request: "POST /Apps/AddContainer?xmlTemplate=default:/tmp/community.applications/tempFiles/templates-community-apps/lnxdsRepository/lnxd-XMRig-latest.xml HTTP/1.1", upstream: "fastcgi://unix:/var/run/php5-fpm.sock:"
  4. My other dockers are normal. Also, when I go to edit it and apply, just sits at Stopping container: XMRig for a good long time. 16 gig RAM XEON X3440 (4 cores, 8 HT) Usually have plenty of CPU/RAM. The big peak was the pinned XMR task...decided to use only one core/HT leaving other 3 of each free. (No, not CPU 0 ) Also, when I go to the Docker tab from the Stats tab...VERY slow to show Docker images. Like, MINUTES to even show the Unraid undulating 'wave'. Last time, it installed and going to Docker in another tab showed it running but the install never showed it as complete. As far as I can see, feels beta. GTG, but will play later. Overall it feels like it kinda works but appears to fully load down the machine, and when installs complete, it doesn't say so. And it's a simple CPU mine, no GPU passthru.
  5. Installs hang, typical example: IMAGE ID [1638176776]: Pulling from lnxd/xmrig. IMAGE ID [a70d879fa598]: Already exists. IMAGE ID [c4394a92d1f8]: Already exists. IMAGE ID [10e6159c56c0]: Already exists. IMAGE ID [4e603f86bf28]: Already exists. IMAGE ID [82c680df2f37]: Pulling fs layer. Extracting. Pull complete. IMAGE ID [8c1b41ba1f70]: Pulling fs layer. Download complete. Extracting. Pull complete. IMAGE ID [216bbbf373ef]: Pulling fs layer. Download complete. Extracting. Pull complete. IMAGE ID [0014a10ac7a2]: Pulling fs layer. Download complete. Extracting. IMAGE ID [e1091e29ea56]: Pulling fs layer. Download complete. IMAGE ID [4a0de8df1f80]: Pulling fs layer. Download complete. IMAGE ID [6fdc9aa00473]: Pulling fs layer. Download complete. IMAGE ID [2e39212cd8e6]: Pulling fs layer. Download complete. IMAGE ID [a9178ef1956c]: Pulling fs layer. Download complete. IMAGE ID [0828d163e125]: Pulling fs layer. Download complete. IMAGE ID [59304a045975]: Pulling fs layer. Download complete. IMAGE ID [1520d09c5763]: Pulling fs layer. Download complete. IMAGE ID [88f444ce6619]: Pulling fs layer. Download complete. IMAGE ID [fc60839e3db2]: Pulling fs layer. Download complete. IMAGE ID [0d598aeec96a]: Pulling fs layer. Download complete. And it's been sitting there. Server normal in other resepects. Tried at least 3 or 4 times.
  6. I've done a lot of things, but this helped the most: https://www.pixeleyes.co.nz/automounter/support/ It remounts shares if they get disconnected. That's all. I was having issues with losing the shares when backing up with Carbon Copy Cloner. Cautiously optimistic as my backups complete way more often now. SMB sucks and I wish AFP were not deprecated in 6.9 Also, I think not backing up folders with lots of files / long path names has helped. Such as the Mail folder. Don't back up Mail.
  7. Can this be used with data drives on 6.9.2? Don't have any cache drives.
  8. Can't view the 'bands' directory that Time Machine creates as part of a .sparsebundle In general, I'm finding Unraid and Mac OS backups to be just suck. Carbon Copy Cloner also dies most times saying the filesystem isn't responding. I just think Unraid in general chokes on too many files/dirs. I have two storj nodes running so that is perhaps part of it. I'm sure it has a fiar amount of open files. That said, storj works fine. Any ideas for this issue? 16 gigs of RAM, gigabit, Xeon X3440 with ECC. Should be a fine system for these few things. No media being served.
  9. I swapped the disk out for another one and no problems noted since.
  10. Recheck said 0 errors but was not present in the history button. Is this normal if you don't write corrections? Running another one.
  11. ECC. Dell T310H....have to see if there's a way to view status of the chips on Unraid...do you know it? Recheck of parity passed 0 errors.
  12. As I continue to research....hopefully this helps someone else: P is parity in the array and Q is parity 2 I presume? So, if Parity had no errors, and only 6 errors corrected on Parity 2, then I guess just monitor the situation? Absent of anything else? Theories as to what would cause errors only on Parity 1 and not Parity 2? Assuming I'm reading this correctly? Minor note...KINDA feel like Parity should be named Parity 1 if you have a Parity 2....TBC.
  13. I found this in the syslog, but doesn't help me much...matches the '6' count but how do I tell what disk these are on? May 2 00:03:34 BlackTower kernel: md: recovery thread: Q corrected, sector=32757816 May 2 00:12:46 BlackTower kernel: md: recovery thread: Q corrected, sector=125990984 May 2 00:20:01 BlackTower sSMTP[20691]: Creating SSL connection to host May 2 00:20:01 BlackTower sSMTP[20691]: SSL connection using TLS_AES_256_GCM_SHA384 May 2 00:20:04 BlackTower sSMTP[20691]: Sent mail for email@removed.com (221 2.0.0 closing connection i130sm2031438oif.49 - gsmtp) uid=0 username=xxx outbytes=1450 May 2 00:24:26 BlackTower kernel: md: recovery thread: Q corrected, sector=245737984 May 2 00:37:02 BlackTower kernel: md: recovery thread: Q corrected, sector=374158856 May 2 00:37:04 BlackTower kernel: md: recovery thread: Q corrected, sector=374658440 May 2 01:41:48 BlackTower kernel: md: recovery thread: Q corrected, sector=977077048
  14. I turned off 'write corrections to disk' in the scheduled now. Of course, I don't know what to suspect, since I have zero errors in Main, Pending Sectors, or SMART thumbs down... Is there a log or is this just that time when a cosmic particle hit my parity disks and the data on the data drives is fine?
  15. Disk 5 has 199 UDMA_CRC_Error_Count -O--CK 200 200 000 - 30 No pending sectors that I saw. Array has not been shut down (19 day uptime) so the error count on the main screen is accurate (0). Sooo....what now?