bally12345

Members
  • Posts

    667
  • Joined

  • Last visited

Everything posted by bally12345

  1. Had my reset confirmed from teamviwer but still didnt work, quick read on their forums and seems like they have thousands of users in same boat and working through a backlog.
  2. Anydesk didnt work on work laptop as it cant connect to its servers. The entry ninja is no good for me either as I am just looking for remote access to my VM rather than unraid. Emailed teamviewer to have account reset so see what happens.
  3. Wow any desk was really poor experience. So much lag and weird response to clicks when in full screen mode. I tried a different settings and found no where as good despite having a good connection. Is there any recommended settings? Sent from my SM-G973F using Tapatalk
  4. I used to use TeamViewer to connect to my VM from work. But now I keep getting disconnected as it thinks im using for commercial use. What's the best alternative? The problem I have is on my work laptop, I am on corporate LAN which means I cant use any vpn and [myhash.undraid.net] does get passed the firewall. Any suggestions for something that has a portable version as I cant install either
  5. I have this same board and have no issues with booting into unraid. I would suggest another USB.
  6. Revisiting this Can anyone advise how I can add a spare GT710-SL-1GD5 gfx so I can use it for vm? Sent from my SM-G973F using Tapatalk
  7. Noticed today I have been disconnected from the mothership unraid-api restart API restart didn't work and I have the latest version of plugin, is there a wider issue? Hopefully nothing related to this
  8. Took me all of 10mins to set up including looking here root@Server:~# unraid-api restart Sending process 23909 SIGKILL. Starting unraid-api in "production" mode. Daemonizing process. Daemonized successfully! root@Server:~# Everything seems to be up and running, might see if I can set up a subdomain on mydomain.com if I get some time later. Thanks team 😄
  9. I had to delete my origial docker and reinstall as mine is using the old template. All sorted now getting 60MB/s Sent from my SM-G973F using Tapatalk
  10. Maybe I need to delete the docker and template and start a fresh as I am not seeing openvpn or wireguard option I have drop down for pia, airvpn or custom Current speedtest results show sh-5.1# speedtest-cli Retrieving speedtest.net configuration... Testing from Datacamp Limited (138.199.27.191)... Retrieving speedtest.net server list... Selecting best server based on ping... Hosted by ONLINE S.A.S. (Vitry-sur-Seine) [135.61 km]: 44.914 ms Testing download speed................................................................................ Download: 72.53 Mbit/s Testing upload speed...................................................................................................... Upload: 27.98 Mbit/s sh-5.1# UPDATE Changed Peer Connection Protocol to just TCP and now getting 18MB/s
  11. Not using wireguard. Using France nextgen but recently it's gone so slow. Looks like I will need to figure out how to switch to wireguard Sent from my SM-G973F using Tapatalk
  12. Anyone else suffering from super slow speeds? I use Pia but nothing downloads faster 500-600Kb/s Normally get around 20Mb/s Sent from my SM-G973F using Tapatalk
  13. So I thought I had a bad sata cable to my cache disk that was replaced today but I got following notification Event: Unraid Cache disk SMART health [199] Subject: Warning [sERVER] - udma crc error count is 13 Description: CT1000MX500SSD1_1910E1EE9FE0 (sdb) Importance: warning Looking at other threads it look like some people had issue with there lsi controllers but mine is connected directly to motherboard. Do I continue to monitor to see if it increases or start looking at a new replacement SSD? Server only been back up an hour so maybe too soon to tell. Sent from my SM-G973F using Tapatalk
  14. Just got the following alert Event: Unraid Cache disk SMART health [199] Subject: Warning [sERVER] - udma crc error count is 1 Description: CT1000MX500SSD1_1910E1EE9FE0 (sdb) Importance: warning Pretty sure this related to bad sata connection. I have a replacement coming from amazon tomorrow. It's just my luck when I need a spare cable I can't find it [emoji23] Sent from my SM-G973F using Tapatalk
  15. Shut down, unplugged and replugged SSD. Unraid showed it as unmounted, after remount I started docker. All sorter [emoji106] Cable wise everything looks fine, might just order another SATA cable just in case. Sent from my SM-G973F using Tapatalk
  16. Appdata share seems to be missing. If SSD is corrupt surely it should still be visible under shares tab? Sent from my SM-G973F using Tapatalk
  17. I think the SSD is dead! But it's showing online but nothing seems to be available in there and appdata share is missing. Before I go into full panic mode. I am pretty certain I have appdata backed up atleast weekly to my array. But still not sure what is going on as I'm on my mobile and have to vpn on to server. Sent from my SM-G973F using Tapatalk
  18. Just noticed on the docker tab One or more paths do not exist (view) So checked the cache SSD and that's online and accessible So I'm guessing the next step would be to create a new docker.img with a new name? If course would like to get to root cause too. Sent from my SM-G973F using Tapatalk
  19. All of a sudden got plex down notification. So logged on to my dashboard and noticed all the dockers are stopping. Checked error log and saw this Feb 16 22:00:53 Server kernel: blk_update_request: I/O error, dev loop2, sector 8085008 op 0x0:(READ) flags 0x0 phys_seg 1 prio class 0 Feb 16 22:00:53 Server kernel: btrfs_dev_stat_print_on_error: 1 callbacks suppressed Feb 16 22:00:53 Server kernel: BTRFS error (device loop2): bdev /dev/loop2 errs: wr 26, rd 2464, flush 0, corrupt 0, gen 0 Feb 16 22:00:53 Server kernel: blk_update_request: I/O error, dev loop2, sector 8085008 op 0x0:(READ) flags 0x0 phys_seg 1 prio class 0 Feb 16 22:00:53 Server kernel: BTRFS error (device loop2): bdev /dev/loop2 errs: wr 26, rd 2465, flush 0, corrupt 0, gen 0 Feb 16 22:00:54 Server kernel: blk_update_request: I/O error, dev loop2, sector 8085008 op 0x0:(READ) flags 0x0 phys_seg 1 prio class 0 Feb 16 22:00:54 Server kernel: BTRFS error (device loop2): bdev /dev/loop2 errs: wr 26, rd 2466, flush 0, corrupt 0, gen 0 Feb 16 22:00:54 Server kernel: blk_update_request: I/O error, dev loop2, sector 8085008 op 0x0:(READ) flags 0x0 phys_seg 1 prio class 0 Feb 16 22:00:54 Server kernel: BTRFS error (device loop2): bdev /dev/loop2 errs: wr 26, rd 2467, flush 0, corrupt 0, gen 0 Feb 16 22:00:55 Server kernel: blk_update_request: I/O error, dev loop2, sector 8085008 op 0x0:(READ) flags 0x0 phys_seg 1 prio class 0 Feb 16 22:00:55 Server kernel: BTRFS error (device loop2): bdev /dev/loop2 errs: wr 26, rd 2468, flush 0, corrupt 0, gen 0 Feb 16 22:00:55 Server kernel: blk_update_request: I/O error, dev loop2, sector 8085008 op 0x0:(READ) flags 0x0 phys_seg 1 prio class 0 Feb 16 22:00:55 Server kernel: BTRFS error (device loop2): bdev /dev/loop2 errs: wr 26, rd 2469, flush 0, corrupt 0, gen 0 Feb 16 22:00:56 Server kernel: blk_update_request: I/O error, dev loop2, sector 8085008 op 0x0:(READ) flags 0x0 phys_seg 1 prio class 0 Feb 16 22:00:56 Server kernel: BTRFS error (device loop2): bdev /dev/loop2 errs: wr 26, rd 2470, flush 0, corrupt 0, gen 0 Feb 16 22:00:56 Server kernel: blk_update_request: I/O error, dev loop2, sector 8085008 op 0x0:(READ) flags 0x0 phys_seg 1 prio class 0 Feb 16 22:00:56 Server kernel: BTRFS error (device loop2): bdev /dev/loop2 errs: wr 26, rd 2471, flush 0, corrupt 0, gen 0 Feb 16 22:00:57 Server kernel: blk_update_request: I/O error, dev loop2, sector 8085008 op 0x0:(READ) flags 0x0 phys_seg 1 prio class 0 Feb 16 22:00:57 Server kernel: BTRFS error (device loop2): bdev /dev/loop2 errs: wr 26, rd 2472, flush 0, corrupt 0, gen 0 Feb 16 22:00:57 Server kernel: blk_update_request: I/O error, dev loop2, sector 8085008 op 0x0:(READ) flags 0x0 phys_seg 1 prio class 0 Feb 16 22:00:57 Server kernel: BTRFS error (device loop2): bdev /dev/loop2 errs: wr 26, rd 2473, flush 0, corrupt 0, gen 0 Feb 16 22:00:58 Server kernel: blk_update_request: I/O error, dev loop2, sector 8085008 op 0x0:(READ) flags 0x0 phys_seg 1 prio class 0 Feb 16 22:00:58 Server kernel: BTRFS error (device loop2): bdev /dev/loop2 errs: wr 26, rd 2474, flush 0, corrupt 0, gen 0 Feb 16 22:00:58 Server kernel: blk_update_request: I/O error, dev loop2, sector 8085008 op 0x0:(READ) flags 0x0 phys_seg 1 prio class 0 Feb 16 22:00:58 Server kernel: BTRFS error (device loop2): bdev /dev/loop2 errs: wr 26, rd 2475, flush 0, corrupt 0, gen 0 Feb 16 22:00:58 Server kernel: blk_update_request: I/O error, dev loop2, sector 2667536 op 0x0:(READ) flags 0x0 phys_seg 1 prio class 0 Feb 16 22:00:58 Server kernel: BTRFS error (device loop2): bdev /dev/loop2 errs: wr 26, rd 2476, flush 0, corrupt 0, gen 0 Feb 16 22:00:59 Server kernel: blk_update_request: I/O error, dev loop2, sector 8085008 op 0x0:(READ) flags 0x0 phys_seg 1 prio class 0 Feb 16 22:00:59 Server kernel: BTRFS error (device loop2): bdev /dev/loop2 errs: wr 26, rd 2477, flush 0, corrupt 0, gen 0 Feb 16 22:00:59 Server kernel: blk_update_request: I/O error, dev loop2, sector 8085008 op 0x0:(READ) flags 0x0 phys_seg 1 prio class 0 Feb 16 22:00:59 Server kernel: BTRFS error (device loop2): bdev /dev/loop2 errs: wr 26, rd 2478, flush 0, corrupt 0, gen 0 Feb 16 22:01:00 Server kernel: blk_update_request: I/O error, dev loop2, sector 8085008 op 0x0:(READ) flags 0x0 phys_seg 1 prio class 0 Feb 16 22:01:00 Server kernel: BTRFS error (device loop2): bdev /dev/loop2 errs: wr 26, rd 2479, flush 0, corrupt 0, gen 0 Feb 16 22:01:00 Server kernel: blk_update_request: I/O error, dev loop2, sector 8085008 op 0x0:(READ) flags 0x0 phys_seg 1 prio class 0 Feb 16 22:01:00 Server kernel: BTRFS error (device loop2): bdev /dev/loop2 errs: wr 26, rd 2480, flush 0, corrupt 0, gen 0 Feb 16 22:01:01 Server kernel: blk_update_request: I/O error, dev loop2, sector 8085008 op 0x0:(READ) flags 0x0 phys_seg 1 prio class 0 Feb 16 22:01:01 Server kernel: BTRFS error (device loop2): bdev /dev/loop2 errs: wr 26, rd 2481, flush 0, corrupt 0, gen 0 Feb 16 22:01:01 Server kernel: blk_update_request: I/O error, dev loop2, sector 8085008 op 0x0:(READ) flags 0x0 phys_seg 1 prio class 0 Feb 16 22:01:01 Server kernel: BTRFS error (device loop2): bdev /dev/loop2 errs: wr 26, rd 2482, flush 0, corrupt 0, gen 0 Feb 16 22:01:02 Server kernel: blk_update_request: I/O error, dev loop2, sector 8085008 op 0x0:(READ) flags 0x0 phys_seg 1 prio class 0 Feb 16 22:01:02 Server kernel: BTRFS error (device loop2): bdev /dev/loop2 errs: wr 26, rd 2483, flush 0, corrupt 0, gen 0 Feb 16 22:01:03 Server kernel: print_req_error: 1 callbacks suppressed Feb 16 22:01:03 Server kernel: blk_update_request: I/O error, dev loop2, sector 8085008 op 0x0:(READ) flags 0x0 phys_seg 1 prio class 0 Feb 16 22:01:03 Server kernel: btrfs_dev_stat_print_on_error: 1 callbacks suppressed I have attached diagnostics. Is the docker.img the issue all my drives are XFS so assuming it's has to be the docker? server-diagnostics-20210216-2203.zip
  20. Will monitor for a week but it looks fine now
  21. Looks like like the error has stopped!! Not sure what changed Feb 5 13:25:56 Server kernel: w83795 0-002f: Failed to write to register 0x040, err -6 Feb 5 13:25:59 Server kernel: i2c /dev entries driver Feb 5 13:26:06 Server kernel: i5500_temp 0000:00:14.3: Sensor seems to be disabled Is there a command to clear the log
  22. Started seeing log filling up again Feb 5 11:27:11 Server kernel: w83795 0-002f: Failed to read from register 0x027, err -6 Feb 5 11:27:11 Server kernel: w83795 0-002f: Failed to read from register 0x03c, err -6 Feb 5 11:27:11 Server kernel: w83795 0-002f: Failed to set bank to 130, err -6 Feb 5 11:27:11 Server kernel: w83795 0-002f: Failed to set bank to 130, err -6 Feb 5 11:27:11 Server kernel: w83795 0-002f: Failed to read from register 0x040, err -6 Feb 5 11:27:11 Server kernel: w83795 0-002f: Failed to read from register 0x046, err -6 Feb 5 11:27:11 Server kernel: w83795 0-002f: Failed to write to register 0x040, err -6 Feb 5 11:27:11 Server kernel: w83795 0-002f: Failed to read from register 0x041, err -6 Feb 5 11:27:11 Server kernel: w83795 0-002f: Failed to read from register 0x042, err -6 Feb 5 11:27:12 Server kernel: w83795 0-002f: Failed to read from register 0x043, err -6 Feb 5 11:27:12 Server kernel: w83795 0-002f: Failed to read from register 0x044, err -6 Feb 5 11:27:12 Server kernel: w83795 0-002f: Failed to read from register 0x045, err -6 Feb 5 11:27:12 Server kernel: w83795 0-002f: Failed to read from register 0x046, err -6 Feb 5 11:27:12 Server kernel: w83795 0-002f: Failed to write to register 0x040, err -6 Feb 5 11:27:20 Server kernel: w83795 0-002f: Failed to read from register 0x010, err -6 Feb 5 11:27:20 Server kernel: w83795 0-002f: Failed to read from register 0x03c, err -6 Feb 5 11:27:20 Server kernel: w83795 0-002f: Failed to read from register 0x011, err -6 Feb 5 11:27:20 Server kernel: w83795 0-002f: Failed to read from register 0x03c, err -6 Anyone know if this is memory related?
  23. Changed the PSUs and server has almost been up 24hours, I will give it to the weekend. This seems to have resolved the issue, nothing to do with the RAM. Faulty PSU
  24. I have a couple of spare PSUs, I am going to swap them over I think and run memtest, the only other thing is to perhaps drop the number of dimms in use and see if that makes any difference.
  25. Getting this 7408 02/01/2021 14:16:42 Fan3 Fan Lower Non-Critical - Going Low - Deasserted 7407 02/01/2021 14:16:42 Fan3 Fan Lower Critical - Going Low - Deasserted 7406 02/01/2021 14:16:42 Fan3 Fan Lower Non-Recoverable - Going Low - Deasserted 7405 02/01/2021 14:16:39 Fan3 Fan Lower Non-Recoverable - Going Low - Asserted 7404 02/01/2021 14:16:39 Fan3 Fan Lower Critical - Going Low - Asserted 7403 02/01/2021 14:16:39 Fan3 Fan Lower Non-Critical - Going Low - Asserted 7402 02/01/2021 14:15:02 Fan3 Fan Lower Non-Critical - Going Low - Deasserted 7401 02/01/2021 14:15:02 Fan3 Fan Lower Critical - Going Low - Deasserted 7400 02/01/2021 14:15:02 Fan3 Fan Lower Non-Recoverable - Going Low - Deasserted 7399 02/01/2021 14:14:59 Fan3 Fan Lower Non-Recoverable - Going Low - Asserted 7398 02/01/2021 14:14:59 Fan3 Fan Lower Critical - Going Low - Asserted 7397 02/01/2021 14:14:59 Fan3 Fan Lower Non-Critical - Going Low - Asserted 7396 02/01/2021 07:25:25 OEM Physical Security (Chassis Intrusion) General Chassis Intrusion - Asserted 7395 02/01/2021 07:23:31 VBAT Voltage Upper Non-Recoverable - Going High - Asserted 7394 02/01/2021 07:23:31 VBAT Voltage Upper Critical - Going High - Asserted 7393 02/01/2021 07:23:30 VBAT Voltage Upper Non-Critical - Going High - Asserted 7392 02/01/2021 07:23:26 +5V Voltage Upper Non-Recoverable - Going High - Asserted 7391 02/01/2021 07:23:26 +5V Voltage Upper Critical - Going High - Asserted 7390 02/01/2021 07:23:25 +5V Voltage Upper Non-Critical - Going High - Asserted 7389 02/01/2021 07:23:23 +3.3VSB Voltage Upper Non-Recoverable - Going High - Asserted 7388 02/01/2021 07:23:23 +3.3VSB Voltage Upper Critical - Going High - Asserted 7387 02/01/2021 07:23:22 +3.3VSB Voltage Upper Non-Critical - Going High - Asserted 7386 02/01/2021 07:23:20 +3.3V Voltage Upper Non-Recoverable - Going High - Asserted 7385 02/01/2021 07:23:20 +3.3V Voltage Upper Critical - Going High - Asserted 7384 02/01/2021 07:23:19 +3.3V Voltage Upper Non-Critical - Going High - Asserted 7383 02/01/2021 07:23:15 CPU2 DIMM Voltage Upper Non-Recoverable - Going High - Asserted 7382 02/01/2021 07:23:15 CPU2 DIMM Voltage Upper Critical - Going High - Asserted 7381 02/01/2021 07:23:15 CPU2 DIMM Voltage Upper Non-Critical - Going High - Asserted 7380 02/01/2021 07:23:12 CPU1 DIMM Voltage Upper Non-Recoverable - Going High - Asserted 7379 02/01/2021 07:23:12 CPU1 DIMM Voltage Upper Critical - Going High - Asserted 7378 02/01/2021 07:23:12 CPU1 DIMM Voltage Upper Non-Critical - Going High - Asserted All the sensors are showing as normal right now.