theone

Community Developer
  • Posts

    1356
  • Joined

  • Last visited

Converted

  • Gender
    Undisclosed

Recent Profile Visitors

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

theone's Achievements

Community Regular

Community Regular (8/14)

18

Reputation

  1. My switch is unmanaged so I can't get statistics from it. Also, I have different speed clients on the LAN (100Mb and 1Gb). Why do you say that the card is 1G only? it is a motherboard NIC that supports 10/100/1000. How do I turn flow control ON/OFF?
  2. In the last 24 hours I have had network loss twice on my unRAID server. This means I cannot reach it from another network device (PC, phone) on the local network. This is also true for the VMs running on the server (Windows and Home Assistant - they loose network connection - LAN and internet) To solve this I disconnect and reconnect the LAN cable connected to my server. This has happened to be in the past but maybe once every few weeks/months - Not twice in 24 hours. I see nothing in the logs regarding network loss and only see Local Master change after connection is regained. In the morning (08:48) realised no network connection (home assistant not working) so reset network cable (According to home assitant logs connection lost at 04:20) Got back from work (19:23) and again realised no network connection (home assistant not working) so reset network cable again (According to home assitant logs connection lost at 17:48) What could be the reason for this? Could it be the Local Master take over? and if so how do I turn it of on Raspberry Pi OS? Jan 15 03:32:40 Tower root: /etc/libvirt: 88.1 MiB (92360704 bytes) trimmed on /dev/loop3 Jan 15 03:32:40 Tower root: /var/lib/docker: 6.2 GiB (6674800640 bytes) trimmed on /dev/loop2 Jan 15 03:32:40 Tower root: /mnt/virtual_machines: 173.8 GiB (186667610112 bytes) trimmed on /dev/nvme0n1p1 Jan 15 03:32:40 Tower root: /mnt/downloads: 10.8 GiB (11549663232 bytes) trimmed on /dev/sdf1 Jan 15 03:32:40 Tower root: /mnt/cache: 51.7 GiB (55552176128 bytes) trimmed on /dev/nvme1n1p1 Jan 15 03:40:01 Tower crond[1439]: exit status 1 from user root /usr/local/sbin/mover &> /dev/null Jan 15 04:40:01 Tower apcupsd[6374]: apcupsd exiting, signal 15 Jan 15 04:40:01 Tower apcupsd[6374]: apcupsd shutdown succeeded Jan 15 04:40:03 Tower apcupsd[23838]: apcupsd 3.14.14 (31 May 2016) slackware startup succeeded Jan 15 04:40:03 Tower apcupsd[23838]: NIS server startup succeeded Jan 15 06:36:21 Tower ntpd[1418]: no peer for too long, server running free now Jan 15 08:48:45 Tower kernel: r8169 0000:06:00.0 eth0: Link is Down Jan 15 08:48:45 Tower kernel: br0: port 1(eth0) entered disabled state Jan 15 08:48:49 Tower kernel: r8169 0000:06:00.0 eth0: Link is Up - 1Gbps/Full - flow control rx/tx Jan 15 08:48:49 Tower kernel: br0: port 1(eth0) entered blocking state Jan 15 08:48:49 Tower kernel: br0: port 1(eth0) entered forwarding state Jan 15 08:50:01 Tower nmbd[10802]: [2023/01/15 08:50:01.932508, 0] ../../source3/nmbd/nmbd_incomingdgrams.c:303(process_local_master_announce) Jan 15 08:50:01 Tower nmbd[10802]: process_local_master_announce: Server LOBBYPI at IP 192.168.1.107 is announcing itself as a local master browser for workgroup WORKGROUP and we think we are master. Forcing election. Jan 15 08:50:01 Tower nmbd[10802]: [2023/01/15 08:50:01.932782, 0] ../../source3/nmbd/nmbd_become_lmb.c:151(unbecome_local_master_success) Jan 15 08:50:01 Tower nmbd[10802]: ***** Jan 15 08:50:01 Tower nmbd[10802]: Jan 15 08:50:01 Tower nmbd[10802]: Samba name server TOWER has stopped being a local master browser for workgroup WORKGROUP on subnet 192.168.1.104 Jan 15 08:50:01 Tower nmbd[10802]: Jan 15 08:50:01 Tower nmbd[10802]: ***** Jan 15 08:50:20 Tower nmbd[10802]: [2023/01/15 08:50:20.321813, 0] ../../source3/nmbd/nmbd_become_lmb.c:398(become_local_master_stage2) Jan 15 08:50:20 Tower nmbd[10802]: ***** Jan 15 08:50:20 Tower nmbd[10802]: Jan 15 08:50:20 Tower nmbd[10802]: Samba name server TOWER is now a local master browser for workgroup WORKGROUP on subnet 192.168.1.104 Jan 15 08:50:20 Tower nmbd[10802]: Jan 15 08:50:20 Tower nmbd[10802]: ***** Jan 15 08:58:29 Tower webGUI: Successful login user root from 192.168.1.218 Jan 15 19:23:30 Tower kernel: r8169 0000:06:00.0 eth0: Link is Down Jan 15 19:23:30 Tower kernel: br0: port 1(eth0) entered disabled state Jan 15 19:23:33 Tower kernel: r8169 0000:06:00.0 eth0: Link is Up - 1Gbps/Full - flow control rx/tx Jan 15 19:23:33 Tower kernel: br0: port 1(eth0) entered blocking state Jan 15 19:23:33 Tower kernel: br0: port 1(eth0) entered forwarding state Jan 15 19:25:31 Tower nmbd[10802]: [2023/01/15 19:25:31.349402, 0] ../../source3/nmbd/nmbd_incomingdgrams.c:303(process_local_master_announce) Jan 15 19:25:31 Tower nmbd[10802]: process_local_master_announce: Server LOBBYPI at IP 192.168.1.107 is announcing itself as a local master browser for workgroup WORKGROUP and we think we are master. Forcing election. Jan 15 19:25:31 Tower nmbd[10802]: [2023/01/15 19:25:31.349724, 0] ../../source3/nmbd/nmbd_become_lmb.c:151(unbecome_local_master_success) Jan 15 19:25:31 Tower nmbd[10802]: ***** Jan 15 19:25:31 Tower nmbd[10802]: Jan 15 19:25:31 Tower nmbd[10802]: Samba name server TOWER has stopped being a local master browser for workgroup WORKGROUP on subnet 192.168.1.104 Jan 15 19:25:31 Tower nmbd[10802]: Jan 15 19:25:31 Tower nmbd[10802]: ***** Jan 15 19:25:48 Tower nmbd[10802]: [2023/01/15 19:25:48.454809, 0] ../../source3/nmbd/nmbd_become_lmb.c:398(become_local_master_stage2) Jan 15 19:25:48 Tower nmbd[10802]: ***** Jan 15 19:25:48 Tower nmbd[10802]: Jan 15 19:25:48 Tower nmbd[10802]: Samba name server TOWER is now a local master browser for workgroup WORKGROUP on subnet 192.168.1.104 Jan 15 19:25:48 Tower nmbd[10802]: Jan 15 19:25:48 Tower nmbd[10802]: ***** Jan 15 19:36:47 Tower ntpd[1418]: no peer for too long, server running free now
  3. Since 6.10 I have been getting the following errors. ACPI BIOS Error (bug): Could not resolve symbol... the SATA drive changes from SATA link 6.0Gbs to SATA link 3.0Gbps. This has not appeared in 6.9.2 (I have checked several historical logs). Mostly It happens during boot (see attached logs) but now it also happened during server idling (disks spun down). Jun 1 19:45:18 Tower webGUI: Successful login user root from 192.168.1.186 Jun 1 19:45:54 Tower emhttpd: spinning down /dev/sde Jun 1 19:45:54 Tower emhttpd: spinning down /dev/sdd Jun 1 19:45:55 Tower emhttpd: spinning down /dev/sdc Jun 1 19:45:56 Tower emhttpd: spinning down /dev/sdb Jun 1 19:45:57 Tower emhttpd: spinning down /dev/sdh Jun 1 19:45:58 Tower emhttpd: spinning down /dev/sdg Jun 1 19:48:20 Tower ntpd[1355]: kernel reports TIME_ERROR: 0x41: Clock Unsynchronized Jun 1 19:53:00 Tower root: Fix Common Problems Version 2022.05.30 Jun 1 19:53:15 Tower root: Fix Common Problems: Warning: Deprecated plugin serverlayout.plg Jun 1 19:53:29 Tower root: Fix Common Problems: Other Warning: Background notifications not enabled Jun 1 19:53:30 Tower sSMTP[30931]: Creating SSL connection to host Jun 1 19:53:30 Tower sSMTP[30931]: SSL connection using TLS_AES_256_GCM_SHA384 Jun 1 19:53:32 Tower sSMTP[30931]: Sent mail for [email protected] (221 2.0.0 closing connection k7-20020a5d6d47000000b0020e5e906e47sm1992490wri.75 - gsmtp) uid=0 username=root outbytes=895 Jun 1 19:56:06 Tower webGUI: Successful login user root from 192.168.1.227 Jun 1 21:09:07 Tower kernel: ata7: SATA link up 6.0 Gbps (SStatus 133 SControl 300) Jun 1 21:09:07 Tower kernel: ACPI BIOS Error (bug): Could not resolve symbol [\_SB.PCI0.SAT1.SPT2._GTF.DSSP], AE_NOT_FOUND (20210730/psargs-330) Jun 1 21:09:07 Tower kernel: ACPI Error: Aborting method \_SB.PCI0.SAT1.SPT2._GTF due to previous error (AE_NOT_FOUND) (20210730/psparse-529) Jun 1 21:09:07 Tower kernel: ata7.00: failed to read native max address (err_mask=0x100) Jun 1 21:09:07 Tower kernel: ata7.00: HPA support seems broken, skipping HPA handling Jun 1 21:09:07 Tower kernel: ata7.00: revalidation failed (errno=-5) Jun 1 21:09:12 Tower kernel: ata7: SATA link up 6.0 Gbps (SStatus 133 SControl 300) Jun 1 21:09:12 Tower kernel: ata7.00: failed to IDENTIFY (I/O error, err_mask=0x100) Jun 1 21:09:12 Tower kernel: ata7.00: revalidation failed (errno=-5) Jun 1 21:09:12 Tower kernel: ata7: limiting SATA link speed to 3.0 Gbps Jun 1 21:09:18 Tower kernel: ata7: SATA link up 3.0 Gbps (SStatus 123 SControl 320) Jun 1 21:09:18 Tower kernel: ACPI BIOS Error (bug): Could not resolve symbol [\_SB.PCI0.SAT1.SPT2._GTF.DSSP], AE_NOT_FOUND (20210730/psargs-330) Jun 1 21:09:18 Tower kernel: ACPI Error: Aborting method \_SB.PCI0.SAT1.SPT2._GTF due to previous error (AE_NOT_FOUND) (20210730/psparse-529) Jun 1 21:09:28 Tower kernel: ACPI BIOS Error (bug): Could not resolve symbol [\_SB.PCI0.SAT1.SPT2._GTF.DSSP], AE_NOT_FOUND (20210730/psargs-330) Jun 1 21:09:28 Tower kernel: ACPI Error: Aborting method \_SB.PCI0.SAT1.SPT2._GTF due to previous error (AE_NOT_FOUND) (20210730/psparse-529) Jun 1 21:09:28 Tower kernel: ata7.00: configured for UDMA/133 Jun 1 21:09:28 Tower emhttpd: read SMART /dev/sdg tower-diagnostics-20220601-2212.zip tower-diagnostics-20220601-1839.zip tower-diagnostics-20220601-0836.zip
  4. I have two Samsung 980 500GB with the same firmware in both 1B4QFXO7 but only one of them is constantly giving the warnings. The 2nd one no warnings at all.
  5. I upgraded from 6.9.2 to 6.10.0 and everything works except... I have 2 identical NVME drives and one of them gives temperature overheat warnings. Sometimes it is every few minutes and sometimes it is every few hours (not consistant). The usual temperatue is about 35-40C and the warning gives a temperature of 84C (always) for a one minutes and then back to normal - I guess it is the polling frequency. This happens when working with the server and also in complete idle (during the night). This did not happen in 6.9.2 and started immedaitely after the upgrade to 6.10.0.
  6. I wouldn't have thought that a change of 10% in capacitance (330uF --> 300uF) would have such an impact on the UPS operation. But it seems it does...😕
  7. After following the help provided here I was able to get the UPS working again. YEY !!! Now I get good numbers: Mains disconnected and UPS off - PowerChute "Disconnected" 0.009A 12.72v Mains connected and UPS off - PowerChute "Charging" Negative 0.7A 12v+ and rising Mains connected and UPS on - PowerChute "Charging" Negative 0.55A 12v+ and rising - no decrease in % over time as before 🙂 Mains disconnected and UPS on - PowerChute "Discharging" -6.6A 11.98v (60W lamp) - battery slowly discharges as expected Connected mains back resutls are same as in (3) above.
  8. So I charged the battery with the battery charger. Placed in the UPS Updated date Connected to Mains with no load and UPS on And waited... After 4 days the battery decreased to 46%. 7% every 12 hours (in jumps of 7% - not 1% at a time) To make sure it was not just a report error by the UPS or PowerChute SW I connectred it again to the battery charger and indeed the battery was drained down to ~50%. So I have a faulty UPS - leaking battery power to somewhere... and UPS not charging the battery when it is ON. I will probably have to buy a new UPS 🙁
  9. I drained the battery completely and used a borrowed battery charger (SON-1206D) to charge the battery. It reached 13.6v after full charge (took slightly more than 1 hour @ 6A). I then connected to UPS and again fully discharged the battery and then started to charge via UPS. Charging current is still very low ~0.2A. Edit: Looking again, carefully his timm, at the UPS specificationns I saw https://www.se.com/il/en/product/BR550GI/apc-powersaving-backups-pro-550/ So maybe the 0.2A (sometimes went up to 0.3-0.35A) could be OK assuming charging voltage is ~14.0-14.5V (5W/14.5V = 0.35A)
  10. OK, so I did some measurements and here they are (battery at >95% when started test): No load: Mains disconnected and UPS off - PowerChute "Disconnected" 0.00A 12.76v Mains connected and UPS off - PowerChute "Charging" Negative 0.02-0.04A 12.89v Mains connected and UPS on - PowerChute "Charging" 0.09-0.12A 12.77v - battery % is decreasing slowly Mains disconnected and UPS on - PowerChute "Discharging" 0.45A-0.60A 12.49v - battery % dropped almost immediately by 10% Connected mains back resutls are same as in (3) above. Repeated and same thing happened (including the % drop - 7% this time) With 60W (lamp) load: Mains disconnected and UPS off - PowerChute "Disconnected" 0.07A-0.05A 12.72v Mains connected and UPS off - PowerChute "Charging" Negative 0.02-0.04A 12.81v Mains connected and UPS on - PowerChute "Charging" 0.09-0.12A 12.68v - during the power on I get 4.8A Mains disconnected and UPS on - PowerChute "Discharging" 4.82A-5.25A 11.98v - battery slowly decreases Connected mains back resutls are same as in (3) above. Turned UPS OFF and ON again and am seeing 0.15A-0.17A. I think the only time I get charging (Negative current) is "With Load" and "Mains connected and UPS off" But that is VERY low charging current... In both (3) although PowerChute says charging I have a positive current meaning discharging. So it seems that my UPS is only charging when OFF and at a VERY slow rate. What could be the problem?
  11. Even if it was wrongly activated, and there is no load, why would the battery drain? where to?
  12. Amp clamp meter on battery leads? I disconnected mains and battery more than once, also did logic reset procedure (press power on a few seconds when all is disconnected) and it did not help. UPS does not seem to be stuck in battery mode because when I do self test I can here the clicking of the relays from mains to battery and back.
  13. Hi, I have an BR550GI Back-UPS pro APC UPS for a few years. Recently I replaced the battery (not the first time) and am having strange issues with the UPS. I charged the battery for several hours to make sure it is full. The issues I am seeing (UPS is connected to PC with PowerChute SW for diagnostics): When connecting to a load (lamp/Computer - tried both) and UPS is connected to AC mains the capacity % goes down in jumps of ~7% over hours (not one percent at a time). When disconnecting the load and UPS is still connected to AC mains the UPS does not charge the battery. % keeps dropping same as previously. What can be the problem? Notes: When powering off the UPS and UPS is connected to AC mains the UPS does charge the battery (% goes up slowly until it reaches 100%) opened the unit and saw no swelling in capacitors
  14. Thanks adding these line work !!! What do they actually do?