Connecting 5TB backup Drive = Immediate Server Power loss

Djchilto · January 30, 2024, 5:46pm

Hey everybody. I was attempting to backup my Server Pure using a Seagate 5TB external hard drive. As soon as I plugged it in to the SS USB port, the server lost all power. Anybody else have this issue? I know I could utilize a shared folder for the backup, but I would prefer to do these via a physically connected USB for speed. Thanks!

George · January 30, 2024, 7:15pm

Could it just be a fluke or electrical discharge? That should work, try it again perhaps and let us know.

What version of StartOS are you on? System > About > Version

Djchilto · January 30, 2024, 9:49pm

Hi George,

I tried it again this time through the front SS USB and the same thing occurred…instant power loss for the Server. I am using the latest Version 0.3.5~1. I tried a smaller 2 TB Seagate external hard drive and it worked with no issues. So, given that, I used the successful USB SS cord from the 2 TB drive with the 5 TB drive and, sure enough, the power loss happened again. The 5 TB drive works fine when connected to my computer/s, so I have to conclude that the amount of power being drawn from the 5 TB drive is tripping a power draw “breaker” and shutting down the Server Pure???

…it is double the size, but no power ratings on either of them to confirm the theory, but since the 2 TB is working, I am probably going to return it (the 5TB) and get a 2TB. Any assistance you may have on this would be greatly appreciated. Thanks!

George · January 31, 2024, 12:33am

Could you go to System > Kernel Logs before you plug the 5TB in and make sure you’re seeing the latest logs. Maybe you can catch the hardware event. If that doesn’t reveal anything, maybe setup ssh and do:

sudo journalctl -kf

Then plug in the 5TB and relay the log for us if you would, please!

Thanks

Djchilto · January 31, 2024, 4:13am

No problem…I’ll give it a go.

results to follow…

Djchilto · January 31, 2024, 4:22am

O.k man…here it is…

file:///Users/danchilton/Downloads/kernel-logs.html

Djchilto · January 31, 2024, 4:25am

2024-01-30T22:17:32-06:00 Received SIGTERM from PID 1 (systemd).
2024-01-30T22:17:32-06:00 Stopping systemd-journald.service - Journal Service…
2024-01-30T22:17:32-06:00 systemd-journald.service: Deactivated successfully.
2024-01-30T22:17:32-06:00 Stopped systemd-journald.service - Journal Service.
2024-01-30T22:17:32-06:00 Starting systemd-journald.service - Journal Service…
2024-01-30T22:17:32-06:00 File /var/log/journal/326c9b84164641e19e798e33878c4701/system.journal corrupted or uncleanly shut down, renaming and replacing.
2024-01-30T22:17:32-06:00 Started systemd-hostnamed.service - Hostname Service.
2024-01-30T22:17:32-06:00 Started systemd-journald.service - Journal Service.
2024-01-30T22:17:32-06:00 bridge: filtering via arp/ip/ip6tables is no longer available by default. Update your scripts to load br_netfilter if you need this.
2024-01-30T22:17:32-06:00 br-start9: port 1(veth0) entered blocking state
2024-01-30T22:17:32-06:00 br-start9: port 1(veth0) entered disabled state
2024-01-30T22:17:32-06:00 device veth0 entered promiscuous mode
2024-01-30T22:17:32-06:00 br-start9: port 1(veth0) entered blocking state
2024-01-30T22:17:32-06:00 br-start9: port 1(veth0) entered forwarding state
2024-01-30T22:17:32-06:00 br-start9: port 1(veth0) entered disabled state
2024-01-30T22:17:32-06:00 IPv6: ADDRCONF(NETDEV_CHANGE): veth0: link becomes ready
2024-01-30T22:17:32-06:00 br-start9: port 1(veth0) entered blocking state
2024-01-30T22:17:32-06:00 br-start9: port 1(veth0) entered forwarding state
2024-01-30T22:17:33-06:00 podman0: port 1(veth1) entered blocking state
2024-01-30T22:17:33-06:00 podman0: port 1(veth1) entered disabled state
2024-01-30T22:17:33-06:00 device veth1 entered promiscuous mode
2024-01-30T22:17:33-06:00 podman0: port 1(veth1) entered blocking state
2024-01-30T22:17:33-06:00 podman0: port 1(veth1) entered forwarding state
2024-01-30T22:17:33-06:00 IPv6: ADDRCONF(NETDEV_CHANGE): veth1: link becomes ready
2024-01-30T22:17:33-06:00 podman0: port 1(veth1) entered disabled state
2024-01-30T22:17:33-06:00 device veth1 left promiscuous mode
2024-01-30T22:17:33-06:00 podman0: port 1(veth1) entered disabled state
2024-01-30T22:17:34-06:00 zram: Added device: zram0
2024-01-30T22:17:34-06:00 zram0: detected capacity change from 0 to 16367616
2024-01-30T22:17:34-06:00 Adding 8183804k swap on /dev/zram0. Priority:5 extents:1 across:8183804k SSFS
2024-01-30T22:17:35-06:00 br-start9: port 2(veth1) entered blocking state
2024-01-30T22:17:35-06:00 br-start9: port 2(veth1) entered disabled state
2024-01-30T22:17:35-06:00 device veth1 entered promiscuous mode
2024-01-30T22:17:35-06:00 IPv6: ADDRCONF(NETDEV_CHANGE): eth0: link becomes ready
2024-01-30T22:17:35-06:00 IPv6: ADDRCONF(NETDEV_CHANGE): veth1: link becomes ready
2024-01-30T22:17:35-06:00 br-start9: port 2(veth1) entered blocking state
2024-01-30T22:17:35-06:00 br-start9: port 2(veth1) entered forwarding state
2024-01-30T22:17:35-06:00 br-start9: port 3(veth2) entered blocking state
2024-01-30T22:17:35-06:00 br-start9: port 3(veth2) entered disabled state
2024-01-30T22:17:35-06:00 device veth2 entered promiscuous mode
2024-01-30T22:17:35-06:00 br-start9: port 3(veth2) entered blocking state
2024-01-30T22:17:35-06:00 br-start9: port 3(veth2) entered forwarding state
2024-01-30T22:17:35-06:00 IPv6: ADDRCONF(NETDEV_CHANGE): veth2: link becomes ready
2024-01-30T22:17:35-06:00 br-start9: port 4(veth3) entered blocking state
2024-01-30T22:17:35-06:00 br-start9: port 4(veth3) entered disabled state
2024-01-30T22:17:35-06:00 device veth3 entered promiscuous mode
2024-01-30T22:17:35-06:00 br-start9: port 4(veth3) entered blocking state
2024-01-30T22:17:35-06:00 br-start9: port 4(veth3) entered forwarding state
2024-01-30T22:17:35-06:00 IPv6: ADDRCONF(NETDEV_CHANGE): veth3: link becomes ready

Djchilto · January 31, 2024, 4:25am

best I could do here bud…

Djchilto · January 31, 2024, 4:56am

set up as instructed…here we go…did the same thing. Immediate power loss.

Djchilto · January 31, 2024, 5:05am

(post deleted by author)

Djchilto · January 31, 2024, 5:07am

did that work?
Just trying to help man.

Djchilto · January 31, 2024, 2:46pm

Djchilto · January 31, 2024, 3:14pm

2024-01-30T22:56:50-06:00 Received SIGTERM from PID 1 (systemd).
2024-01-30T22:56:50-06:00 Stopping systemd-journald.service - Journal Service…
2024-01-30T22:56:50-06:00 systemd-journald.service: Deactivated successfully.
2024-01-30T22:56:50-06:00 Stopped systemd-journald.service - Journal Service.
2024-01-30T22:56:50-06:00 Starting systemd-journald.service - Journal Service…
2024-01-30T22:56:50-06:00 File /var/log/journal/326c9b84164641e19e798e33878c4701/system.journal corrupted or uncleanly shut down, renaming and replacing.
2024-01-30T22:56:50-06:00 Started systemd-hostnamed.service - Hostname Service.
2024-01-30T22:56:50-06:00 Started systemd-journald.service - Journal Service.
2024-01-30T22:56:50-06:00 bridge: filtering via arp/ip/ip6tables is no longer available by default. Update your scripts to load br_netfilter if you need this.
2024-01-30T22:56:50-06:00 br-start9: port 1(veth0) entered blocking state
2024-01-30T22:56:50-06:00 br-start9: port 1(veth0) entered disabled state
2024-01-30T22:56:50-06:00 device veth0 entered promiscuous mode
2024-01-30T22:56:50-06:00 br-start9: port 1(veth0) entered blocking state
2024-01-30T22:56:50-06:00 br-start9: port 1(veth0) entered forwarding state
2024-01-30T22:56:50-06:00 IPv6: ADDRCONF(NETDEV_CHANGE): veth0: link becomes ready
2024-01-30T22:56:51-06:00 podman0: port 1(veth1) entered blocking state
2024-01-30T22:56:51-06:00 podman0: port 1(veth1) entered disabled state
2024-01-30T22:56:51-06:00 device veth1 entered promiscuous mode
2024-01-30T22:56:51-06:00 podman0: port 1(veth1) entered blocking state
2024-01-30T22:56:51-06:00 podman0: port 1(veth1) entered forwarding state
2024-01-30T22:56:51-06:00 IPv6: ADDRCONF(NETDEV_CHANGE): veth1: link becomes ready
2024-01-30T22:56:51-06:00 podman0: port 1(veth1) entered disabled state
2024-01-30T22:56:51-06:00 device veth1 left promiscuous mode
2024-01-30T22:56:51-06:00 podman0: port 1(veth1) entered disabled state
2024-01-30T22:56:52-06:00 zram: Added device: zram0
2024-01-30T22:56:52-06:00 zram0: detected capacity change from 0 to 16367616
2024-01-30T22:56:52-06:00 Adding 8183804k swap on /dev/zram0. Priority:5 extents:1 across:8183804k SSFS
2024-01-30T22:56:53-06:00 br-start9: port 2(veth1) entered blocking state
2024-01-30T22:56:53-06:00 br-start9: port 2(veth1) entered disabled state
2024-01-30T22:56:53-06:00 device veth1 entered promiscuous mode
2024-01-30T22:56:53-06:00 br-start9: port 2(veth1) entered blocking state
2024-01-30T22:56:53-06:00 br-start9: port 2(veth1) entered forwarding state
2024-01-30T22:56:53-06:00 IPv6: ADDRCONF(NETDEV_CHANGE): veth1: link becomes ready
2024-01-30T22:56:53-06:00 br-start9: port 3(veth2) entered blocking state
2024-01-30T22:56:53-06:00 br-start9: port 3(veth2) entered disabled state
2024-01-30T22:56:53-06:00 device veth2 entered promiscuous mode
2024-01-30T22:56:53-06:00 IPv6: ADDRCONF(NETDEV_CHANGE): eth0: link becomes ready
2024-01-30T22:56:53-06:00 IPv6: ADDRCONF(NETDEV_CHANGE): veth2: link becomes ready
2024-01-30T22:56:53-06:00 br-start9: port 3(veth2) entered blocking state
2024-01-30T22:56:53-06:00 br-start9: port 3(veth2) entered forwarding state
2024-01-30T22:56:54-06:00 br-start9: port 4(veth3) entered blocking state
2024-01-30T22:56:54-06:00 br-start9: port 4(veth3) entered disabled state
2024-01-30T22:56:54-06:00 device veth3 entered promiscuous mode
2024-01-30T22:56:54-06:00 br-start9: port 4(veth3) entered blocking state
2024-01-30T22:56:54-06:00 br-start9: port 4(veth3) entered forwarding state
2024-01-30T22:56:54-06:00 IPv6: ADDRCONF(NETDEV_CHANGE): veth3: link becomes ready
2024-01-31T06:11:56-06:00 perf: interrupt took too long (2508 > 2500), lowering kernel.perf_event_max_sample_rate to 79500
Disconnected at 2024-01-31T08:48:26-06:00
Reconnected at 2024-01-31T08:48:26-06:00
2024-01-30T22:56:50-06:00 Received SIGTERM from PID 1 (systemd).
2024-01-30T22:56:50-06:00 Stopping systemd-journald.service - Journal Service…
2024-01-30T22:56:50-06:00 systemd-journald.service: Deactivated successfully.
2024-01-30T22:56:50-06:00 Stopped systemd-journald.service - Journal Service.
2024-01-30T22:56:50-06:00 Starting systemd-journald.service - Journal Service…
2024-01-30T22:56:50-06:00 File /var/log/journal/326c9b84164641e19e798e33878c4701/system.journal corrupted or uncleanly shut down, renaming and replacing.
2024-01-30T22:56:50-06:00 Started systemd-hostnamed.service - Hostname Service.
2024-01-30T22:56:50-06:00 Started systemd-journald.service - Journal Service.
2024-01-30T22:56:50-06:00 bridge: filtering via arp/ip/ip6tables is no longer available by default. Update your scripts to load br_netfilter if you need this.
2024-01-30T22:56:50-06:00 br-start9: port 1(veth0) entered blocking state
2024-01-30T22:56:50-06:00 br-start9: port 1(veth0) entered disabled state
2024-01-30T22:56:50-06:00 device veth0 entered promiscuous mode
2024-01-30T22:56:50-06:00 br-start9: port 1(veth0) entered blocking state
2024-01-30T22:56:50-06:00 br-start9: port 1(veth0) entered forwarding state
2024-01-30T22:56:50-06:00 IPv6: ADDRCONF(NETDEV_CHANGE): veth0: link becomes ready
2024-01-30T22:56:51-06:00 podman0: port 1(veth1) entered blocking state
2024-01-30T22:56:51-06:00 podman0: port 1(veth1) entered disabled state
2024-01-30T22:56:51-06:00 device veth1 entered promiscuous mode
2024-01-30T22:56:51-06:00 podman0: port 1(veth1) entered blocking state
2024-01-30T22:56:51-06:00 podman0: port 1(veth1) entered forwarding state
2024-01-30T22:56:51-06:00 IPv6: ADDRCONF(NETDEV_CHANGE): veth1: link becomes ready
2024-01-30T22:56:51-06:00 podman0: port 1(veth1) entered disabled state
2024-01-30T22:56:51-06:00 device veth1 left promiscuous mode
2024-01-30T22:56:51-06:00 podman0: port 1(veth1) entered disabled state
2024-01-30T22:56:52-06:00 zram: Added device: zram0
2024-01-30T22:56:52-06:00 zram0: detected capacity change from 0 to 16367616
2024-01-30T22:56:52-06:00 Adding 8183804k swap on /dev/zram0. Priority:5 extents:1 across:8183804k SSFS
2024-01-30T22:56:53-06:00 br-start9: port 2(veth1) entered blocking state
2024-01-30T22:56:53-06:00 br-start9: port 2(veth1) entered disabled state
2024-01-30T22:56:53-06:00 device veth1 entered promiscuous mode
2024-01-30T22:56:53-06:00 br-start9: port 2(veth1) entered blocking state
2024-01-30T22:56:53-06:00 br-start9: port 2(veth1) entered forwarding state
2024-01-30T22:56:53-06:00 IPv6: ADDRCONF(NETDEV_CHANGE): veth1: link becomes ready
2024-01-30T22:56:53-06:00 br-start9: port 3(veth2) entered blocking state
2024-01-30T22:56:53-06:00 br-start9: port 3(veth2) entered disabled state
2024-01-30T22:56:53-06:00 device veth2 entered promiscuous mode
2024-01-30T22:56:53-06:00 IPv6: ADDRCONF(NETDEV_CHANGE): eth0: link becomes ready
2024-01-30T22:56:53-06:00 IPv6: ADDRCONF(NETDEV_CHANGE): veth2: link becomes ready
2024-01-30T22:56:53-06:00 br-start9: port 3(veth2) entered blocking state
2024-01-30T22:56:53-06:00 br-start9: port 3(veth2) entered forwarding state
2024-01-30T22:56:54-06:00 br-start9: port 4(veth3) entered blocking state
2024-01-30T22:56:54-06:00 br-start9: port 4(veth3) entered disabled state
2024-01-30T22:56:54-06:00 device veth3 entered promiscuous mode
2024-01-30T22:56:54-06:00 br-start9: port 4(veth3) entered blocking state
2024-01-30T22:56:54-06:00 br-start9: port 4(veth3) entered forwarding state
2024-01-30T22:56:54-06:00 IPv6: ADDRCONF(NETDEV_CHANGE): veth3: link becomes ready
2024-01-31T06:11:56-06:00 perf: interrupt took too long (2508 > 2500), lowering kernel.perf_event_max_sample_rate to 79500
Disconnected at 2024-01-31T08:53:26-06:00
Reconnected at 2024-01-31T08:53:26-06:00
2024-01-30T22:56:50-06:00 Received SIGTERM from PID 1 (systemd).
2024-01-30T22:56:50-06:00 Stopping systemd-journald.service - Journal Service…
2024-01-30T22:56:50-06:00 systemd-journald.service: Deactivated successfully.
2024-01-30T22:56:50-06:00 Stopped systemd-journald.service - Journal Service.
2024-01-30T22:56:50-06:00 Starting systemd-journald.service - Journal Service…
2024-01-30T22:56:50-06:00 File /var/log/journal/326c9b84164641e19e798e33878c4701/system.journal corrupted or uncleanly shut down, renaming and replacing.
2024-01-30T22:56:50-06:00 Started systemd-hostnamed.service - Hostname Service.
2024-01-30T22:56:50-06:00 Started systemd-journald.service - Journal Service.
2024-01-30T22:56:50-06:00 bridge: filtering via arp/ip/ip6tables is no longer available by default. Update your scripts to load br_netfilter if you need this.
2024-01-30T22:56:50-06:00 br-start9: port 1(veth0) entered blocking state
2024-01-30T22:56:50-06:00 br-start9: port 1(veth0) entered disabled state
2024-01-30T22:56:50-06:00 device veth0 entered promiscuous mode
2024-01-30T22:56:50-06:00 br-start9: port 1(veth0) entered blocking state
2024-01-30T22:56:50-06:00 br-start9: port 1(veth0) entered forwarding state
2024-01-30T22:56:50-06:00 IPv6: ADDRCONF(NETDEV_CHANGE): veth0: link becomes ready
2024-01-30T22:56:51-06:00 podman0: port 1(veth1) entered blocking state
2024-01-30T22:56:51-06:00 podman0: port 1(veth1) entered disabled state
2024-01-30T22:56:51-06:00 device veth1 entered promiscuous mode
2024-01-30T22:56:51-06:00 podman0: port 1(veth1) entered blocking state
2024-01-30T22:56:51-06:00 podman0: port 1(veth1) entered forwarding state
2024-01-30T22:56:51-06:00 IPv6: ADDRCONF(NETDEV_CHANGE): veth1: link becomes ready
2024-01-30T22:56:51-06:00 podman0: port 1(veth1) entered disabled state
2024-01-30T22:56:51-06:00 device veth1 left promiscuous mode
2024-01-30T22:56:51-06:00 podman0: port 1(veth1) entered disabled state
2024-01-30T22:56:52-06:00 zram: Added device: zram0
2024-01-30T22:56:52-06:00 zram0: detected capacity change from 0 to 16367616
2024-01-30T22:56:52-06:00 Adding 8183804k swap on /dev/zram0. Priority:5 extents:1 across:8183804k SSFS
2024-01-30T22:56:53-06:00 br-start9: port 2(veth1) entered blocking state
2024-01-30T22:56:53-06:00 br-start9: port 2(veth1) entered disabled state
2024-01-30T22:56:53-06:00 device veth1 entered promiscuous mode
2024-01-30T22:56:53-06:00 br-start9: port 2(veth1) entered blocking state
2024-01-30T22:56:53-06:00 br-start9: port 2(veth1) entered forwarding state
2024-01-30T22:56:53-06:00 IPv6: ADDRCONF(NETDEV_CHANGE): veth1: link becomes ready
2024-01-30T22:56:53-06:00 br-start9: port 3(veth2) entered blocking state
2024-01-30T22:56:53-06:00 br-start9: port 3(veth2) entered disabled state
2024-01-30T22:56:53-06:00 device veth2 entered promiscuous mode
2024-01-30T22:56:53-06:00 IPv6: ADDRCONF(NETDEV_CHANGE): eth0: link becomes ready
2024-01-30T22:56:53-06:00 IPv6: ADDRCONF(NETDEV_CHANGE): veth2: link becomes ready
2024-01-30T22:56:53-06:00 br-start9: port 3(veth2) entered blocking state
2024-01-30T22:56:53-06:00 br-start9: port 3(veth2) entered forwarding state
2024-01-30T22:56:54-06:00 br-start9: port 4(veth3) entered blocking state
2024-01-30T22:56:54-06:00 br-start9: port 4(veth3) entered disabled state
2024-01-30T22:56:54-06:00 device veth3 entered promiscuous mode
2024-01-30T22:56:54-06:00 br-start9: port 4(veth3) entered blocking state
2024-01-30T22:56:54-06:00 br-start9: port 4(veth3) entered forwarding state
2024-01-30T22:56:54-06:00 IPv6: ADDRCONF(NETDEV_CHANGE): veth3: link becomes ready
2024-01-31T06:11:56-06:00 perf: interrupt took too long (2508 > 2500), lowering kernel.perf_event_max_sample_rate to 79500
Disconnected at 2024-01-31T08:58:26-06:00
Reconnected at 2024-01-31T08:58:26-06:00
2024-01-30T22:56:50-06:00 Received SIGTERM from PID 1 (systemd).
2024-01-30T22:56:50-06:00 Stopping systemd-journald.service - Journal Service…
2024-01-30T22:56:50-06:00 systemd-journald.service: Deactivated successfully.
2024-01-30T22:56:50-06:00 Stopped systemd-journald.service - Journal Service.
2024-01-30T22:56:50-06:00 Starting systemd-journald.service - Journal Service…
2024-01-30T22:56:50-06:00 File /var/log/journal/326c9b84164641e19e798e33878c4701/system.journal corrupted or uncleanly shut down, renaming and replacing.
2024-01-30T22:56:50-06:00 Started systemd-hostnamed.service - Hostname Service.
2024-01-30T22:56:50-06:00 Started systemd-journald.service - Journal Service.
2024-01-30T22:56:50-06:00 bridge: filtering via arp/ip/ip6tables is no longer available by default. Update your scripts to load br_netfilter if you need this.
2024-01-30T22:56:50-06:00 br-start9: port 1(veth0) entered blocking state
2024-01-30T22:56:50-06:00 br-start9: port 1(veth0) entered disabled state
2024-01-30T22:56:50-06:00 device veth0 entered promiscuous mode
2024-01-30T22:56:50-06:00 br-start9: port 1(veth0) entered blocking state
2024-01-30T22:56:50-06:00 br-start9: port 1(veth0) entered forwarding state
2024-01-30T22:56:50-06:00 IPv6: ADDRCONF(NETDEV_CHANGE): veth0: link becomes ready
2024-01-30T22:56:51-06:00 podman0: port 1(veth1) entered blocking state
2024-01-30T22:56:51-06:00 podman0: port 1(veth1) entered disabled state
2024-01-30T22:56:51-06:00 device veth1 entered promiscuous mode
2024-01-30T22:56:51-06:00 podman0: port 1(veth1) entered blocking state
2024-01-30T22:56:51-06:00 podman0: port 1(veth1) entered forwarding state
2024-01-30T22:56:51-06:00 IPv6: ADDRCONF(NETDEV_CHANGE): veth1: link becomes ready
2024-01-30T22:56:51-06:00 podman0: port 1(veth1) entered disabled state
2024-01-30T22:56:51-06:00 device veth1 left promiscuous mode
2024-01-30T22:56:51-06:00 podman0: port 1(veth1) entered disabled state
2024-01-30T22:56:52-06:00 zram: Added device: zram0
2024-01-30T22:56:52-06:00 zram0: detected capacity change from 0 to 16367616
2024-01-30T22:56:52-06:00 Adding 8183804k swap on /dev/zram0. Priority:5 extents:1 across:8183804k SSFS
2024-01-30T22:56:53-06:00 br-start9: port 2(veth1) entered blocking state
2024-01-30T22:56:53-06:00 br-start9: port 2(veth1) entered disabled state
2024-01-30T22:56:53-06:00 device veth1 entered promiscuous mode
2024-01-30T22:56:53-06:00 br-start9: port 2(veth1) entered blocking state
2024-01-30T22:56:53-06:00 br-start9: port 2(veth1) entered forwarding state
2024-01-30T22:56:53-06:00 IPv6: ADDRCONF(NETDEV_CHANGE): veth1: link becomes ready
2024-01-30T22:56:53-06:00 br-start9: port 3(veth2) entered blocking state
2024-01-30T22:56:53-06:00 br-start9: port 3(veth2) entered disabled state
2024-01-30T22:56:53-06:00 device veth2 entered promiscuous mode
2024-01-30T22:56:53-06:00 IPv6: ADDRCONF(NETDEV_CHANGE): eth0: link becomes ready
2024-01-30T22:56:53-06:00 IPv6: ADDRCONF(NETDEV_CHANGE): veth2: link becomes ready
2024-01-30T22:56:53-06:00 br-start9: port 3(veth2) entered blocking state
2024-01-30T22:56:53-06:00 br-start9: port 3(veth2) entered forwarding state
2024-01-30T22:56:54-06:00 br-start9: port 4(veth3) entered blocking state
2024-01-30T22:56:54-06:00 br-start9: port 4(veth3) entered disabled state
2024-01-30T22:56:54-06:00 device veth3 entered promiscuous mode
2024-01-30T22:56:54-06:00 br-start9: port 4(veth3) entered blocking state
2024-01-30T22:56:54-06:00 br-start9: port 4(veth3) entered forwarding state
2024-01-30T22:56:54-06:00 IPv6: ADDRCONF(NETDEV_CHANGE): veth3: link becomes ready
2024-01-31T06:11:56-06:00 perf: interrupt took too long (2508 > 2500), lowering kernel.perf_event_max_sample_rate to 79500
Disconnected at 2024-01-31T09:03:27-06:00
Reconnected at 2024-01-31T09:03:27-06:00
2024-01-30T22:56:50-06:00 Received SIGTERM from PID 1 (systemd).
2024-01-30T22:56:50-06:00 Stopping systemd-journald.service - Journal Service…
2024-01-30T22:56:50-06:00 systemd-journald.service: Deactivated successfully.
2024-01-30T22:56:50-06:00 Stopped systemd-journald.service - Journal Service.
2024-01-30T22:56:50-06:00 Starting systemd-journald.service - Journal Service…
2024-01-30T22:56:50-06:00 File /var/log/journal/326c9b84164641e19e798e33878c4701/system.journal corrupted or uncleanly shut down, renaming and replacing.
2024-01-30T22:56:50-06:00 Started systemd-hostnamed.service - Hostname Service.
2024-01-30T22:56:50-06:00 Started systemd-journald.service - Journal Service.
2024-01-30T22:56:50-06:00 bridge: filtering via arp/ip/ip6tables is no longer available by default. Update your scripts to load br_netfilter if you need this.
2024-01-30T22:56:50-06:00 br-start9: port 1(veth0) entered blocking state
2024-01-30T22:56:50-06:00 br-start9: port 1(veth0) entered disabled state
2024-01-30T22:56:50-06:00 device veth0 entered promiscuous mode
2024-01-30T22:56:50-06:00 br-start9: port 1(veth0) entered blocking state
2024-01-30T22:56:50-06:00 br-start9: port 1(veth0) entered forwarding state
2024-01-30T22:56:50-06:00 IPv6: ADDRCONF(NETDEV_CHANGE): veth0: link becomes ready
2024-01-30T22:56:51-06:00 podman0: port 1(veth1) entered blocking state
2024-01-30T22:56:51-06:00 podman0: port 1(veth1) entered disabled state
2024-01-30T22:56:51-06:00 device veth1 entered promiscuous mode
2024-01-30T22:56:51-06:00 podman0: port 1(veth1) entered blocking state
2024-01-30T22:56:51-06:00 podman0: port 1(veth1) entered forwarding state
2024-01-30T22:56:51-06:00 IPv6: ADDRCONF(NETDEV_CHANGE): veth1: link becomes ready
2024-01-30T22:56:51-06:00 podman0: port 1(veth1) entered disabled state
2024-01-30T22:56:51-06:00 device veth1 left promiscuous mode
2024-01-30T22:56:51-06:00 podman0: port 1(veth1) entered disabled state
2024-01-30T22:56:52-06:00 zram: Added device: zram0
2024-01-30T22:56:52-06:00 zram0: detected capacity change from 0 to 16367616
2024-01-30T22:56:52-06:00 Adding 8183804k swap on /dev/zram0. Priority:5 extents:1 across:8183804k SSFS
2024-01-30T22:56:53-06:00 br-start9: port 2(veth1) entered blocking state
2024-01-30T22:56:53-06:00 br-start9: port 2(veth1) entered disabled state
2024-01-30T22:56:53-06:00 device veth1 entered promiscuous mode
2024-01-30T22:56:53-06:00 br-start9: port 2(veth1) entered blocking state
2024-01-30T22:56:53-06:00 br-start9: port 2(veth1) entered forwarding state
2024-01-30T22:56:53-06:00 IPv6: ADDRCONF(NETDEV_CHANGE): veth1: link becomes ready
2024-01-30T22:56:53-06:00 br-start9: port 3(veth2) entered blocking state
2024-01-30T22:56:53-06:00 br-start9: port 3(veth2) entered disabled state
2024-01-30T22:56:53-06:00 device veth2 entered promiscuous mode
2024-01-30T22:56:53-06:00 IPv6: ADDRCONF(NETDEV_CHANGE): eth0: link becomes ready
2024-01-30T22:56:53-06:00 IPv6: ADDRCONF(NETDEV_CHANGE): veth2: link becomes ready
2024-01-30T22:56:53-06:00 br-start9: port 3(veth2) entered blocking state
2024-01-30T22:56:53-06:00 br-start9: port 3(veth2) entered forwarding state
2024-01-30T22:56:54-06:00 br-start9: port 4(veth3) entered blocking state
2024-01-30T22:56:54-06:00 br-start9: port 4(veth3) entered disabled state
2024-01-30T22:56:54-06:00 device veth3 entered promiscuous mode
2024-01-30T22:56:54-06:00 br-start9: port 4(veth3) entered blocking state
2024-01-30T22:56:54-06:00 br-start9: port 4(veth3) entered forwarding state
2024-01-30T22:56:54-06:00 IPv6: ADDRCONF(NETDEV_CHANGE): veth3: link becomes ready
2024-01-31T06:11:56-06:00 perf: interrupt took too long (2508 > 2500), lowering kernel.perf_event_max_sample_rate to 79500
Disconnected at 2024-01-31T09:08:27-06:00
Reconnected at 2024-01-31T09:08:27-06:00
2024-01-30T22:56:50-06:00 Received SIGTERM from PID 1 (systemd).
2024-01-30T22:56:50-06:00 Stopping systemd-journald.service - Journal Service…
2024-01-30T22:56:50-06:00 systemd-journald.service: Deactivated successfully.
2024-01-30T22:56:50-06:00 Stopped systemd-journald.service - Journal Service.
2024-01-30T22:56:50-06:00 Starting systemd-journald.service - Journal Service…
2024-01-30T22:56:50-06:00 File /var/log/journal/326c9b84164641e19e798e33878c4701/system.journal corrupted or uncleanly shut down, renaming and replacing.
2024-01-30T22:56:50-06:00 Started systemd-hostnamed.service - Hostname Service.
2024-01-30T22:56:50-06:00 Started systemd-journald.service - Journal Service.
2024-01-30T22:56:50-06:00 bridge: filtering via arp/ip/ip6tables is no longer available by default. Update your scripts to load br_netfilter if you need this.
2024-01-30T22:56:50-06:00 br-start9: port 1(veth0) entered blocking state
2024-01-30T22:56:50-06:00 br-start9: port 1(veth0) entered disabled state
2024-01-30T22:56:50-06:00 device veth0 entered promiscuous mode
2024-01-30T22:56:50-06:00 br-start9: port 1(veth0) entered blocking state
2024-01-30T22:56:50-06:00 br-start9: port 1(veth0) entered forwarding state
2024-01-30T22:56:50-06:00 IPv6: ADDRCONF(NETDEV_CHANGE): veth0: link becomes ready
2024-01-30T22:56:51-06:00 podman0: port 1(veth1) entered blocking state
2024-01-30T22:56:51-06:00 podman0: port 1(veth1) entered disabled state
2024-01-30T22:56:51-06:00 device veth1 entered promiscuous mode
2024-01-30T22:56:51-06:00 podman0: port 1(veth1) entered blocking state
2024-01-30T22:56:51-06:00 podman0: port 1(veth1) entered forwarding state
2024-01-30T22:56:51-06:00 IPv6: ADDRCONF(NETDEV_CHANGE): veth1: link becomes ready
2024-01-30T22:56:51-06:00 podman0: port 1(veth1) entered disabled state
2024-01-30T22:56:51-06:00 device veth1 left promiscuous mode
2024-01-30T22:56:51-06:00 podman0: port 1(veth1) entered disabled state
2024-01-30T22:56:52-06:00 zram: Added device: zram0
2024-01-30T22:56:52-06:00 zram0: detected capacity change from 0 to 16367616
2024-01-30T22:56:52-06:00 Adding 8183804k swap on /dev/zram0. Priority:5 extents:1 across:8183804k SSFS
2024-01-30T22:56:53-06:00 br-start9: port 2(veth1) entered blocking state
2024-01-30T22:56:53-06:00 br-start9: port 2(veth1) entered disabled state
2024-01-30T22:56:53-06:00 device veth1 entered promiscuous mode
2024-01-30T22:56:53-06:00 br-start9: port 2(veth1) entered blocking state
2024-01-30T22:56:53-06:00 br-start9: port 2(veth1) entered forwarding state
2024-01-30T22:56:53-06:00 IPv6: ADDRCONF(NETDEV_CHANGE): veth1: link becomes ready
2024-01-30T22:56:53-06:00 br-start9: port 3(veth2) entered blocking state
2024-01-30T22:56:53-06:00 br-start9: port 3(veth2) entered disabled state
2024-01-30T22:56:53-06:00 device veth2 entered promiscuous mode
2024-01-30T22:56:53-06:00 IPv6: ADDRCONF(NETDEV_CHANGE): eth0: link becomes ready
2024-01-30T22:56:53-06:00 IPv6: ADDRCONF(NETDEV_CHANGE): veth2: link becomes ready
2024-01-30T22:56:53-06:00 br-start9: port 3(veth2) entered blocking state
2024-01-30T22:56:53-06:00 br-start9: port 3(veth2) entered forwarding state
2024-01-30T22:56:54-06:00 br-start9: port 4(veth3) entered blocking state
2024-01-30T22:56:54-06:00 br-start9: port 4(veth3) entered disabled state
2024-01-30T22:56:54-06:00 device veth3 entered promiscuous mode
2024-01-30T22:56:54-06:00 br-start9: port 4(veth3) entered blocking state
2024-01-30T22:56:54-06:00 br-start9: port 4(veth3) entered forwarding state
2024-01-30T22:56:54-06:00 IPv6: ADDRCONF(NETDEV_CHANGE): veth3: link becomes ready
2024-01-31T06:11:56-06:00 perf: interrupt took too long (2508 > 2500), lowering kernel.perf_event_max_sample_rate to 79500
Disconnected at 2024-01-31T09:13:27-06:00
Reconnected at 2024-01-31T09:13:27-06:00
2024-01-30T22:56:50-06:00 Received SIGTERM from PID 1 (systemd).
2024-01-30T22:56:50-06:00 Stopping systemd-journald.service - Journal Service…
2024-01-30T22:56:50-06:00 systemd-journald.service: Deactivated successfully.
2024-01-30T22:56:50-06:00 Stopped systemd-journald.service - Journal Service.
2024-01-30T22:56:50-06:00 Starting systemd-journald.service - Journal Service…
2024-01-30T22:56:50-06:00 File /var/log/journal/326c9b84164641e19e798e33878c4701/system.journal corrupted or uncleanly shut down, renaming and replacing.
2024-01-30T22:56:50-06:00 Started systemd-hostnamed.service - Hostname Service.
2024-01-30T22:56:50-06:00 Started systemd-journald.service - Journal Service.
2024-01-30T22:56:50-06:00 bridge: filtering via arp/ip/ip6tables is no longer available by default. Update your scripts to load br_netfilter if you need this.
2024-01-30T22:56:50-06:00 br-start9: port 1(veth0) entered blocking state
2024-01-30T22:56:50-06:00 br-start9: port 1(veth0) entered disabled state
2024-01-30T22:56:50-06:00 device veth0 entered promiscuous mode
2024-01-30T22:56:50-06:00 br-start9: port 1(veth0) entered blocking state
2024-01-30T22:56:50-06:00 br-start9: port 1(veth0) entered forwarding state
2024-01-30T22:56:50-06:00 IPv6: ADDRCONF(NETDEV_CHANGE): veth0: link becomes ready
2024-01-30T22:56:51-06:00 podman0: port 1(veth1) entered blocking state
2024-01-30T22:56:51-06:00 podman0: port 1(veth1) entered disabled state
2024-01-30T22:56:51-06:00 device veth1 entered promiscuous mode
2024-01-30T22:56:51-06:00 podman0: port 1(veth1) entered blocking state
2024-01-30T22:56:51-06:00 podman0: port 1(veth1) entered forwarding state
2024-01-30T22:56:51-06:00 IPv6: ADDRCONF(NETDEV_CHANGE): veth1: link becomes ready
2024-01-30T22:56:51-06:00 podman0: port 1(veth1) entered disabled state
2024-01-30T22:56:51-06:00 device veth1 left promiscuous mode
2024-01-30T22:56:51-06:00 podman0: port 1(veth1) entered disabled state
2024-01-30T22:56:52-06:00 zram: Added device: zram0
2024-01-30T22:56:52-06:00 zram0: detected capacity change from 0 to 16367616
2024-01-30T22:56:52-06:00 Adding 8183804k swap on /dev/zram0. Priority:5 extents:1 across:8183804k SSFS
2024-01-30T22:56:53-06:00 br-start9: port 2(veth1) entered blocking state
2024-01-30T22:56:53-06:00 br-start9: port 2(veth1) entered disabled state
2024-01-30T22:56:53-06:00 device veth1 entered promiscuous mode
2024-01-30T22:56:53-06:00 br-start9: port 2(veth1) entered blocking state
2024-01-30T22:56:53-06:00 br-start9: port 2(veth1) entered forwarding state
2024-01-30T22:56:53-06:00 IPv6: ADDRCONF(NETDEV_CHANGE): veth1: link becomes ready
2024-01-30T22:56:53-06:00 br-start9: port 3(veth2) entered blocking state
2024-01-30T22:56:53-06:00 br-start9: port 3(veth2) entered disabled state
2024-01-30T22:56:53-06:00 device veth2 entered promiscuous mode
2024-01-30T22:56:53-06:00 IPv6: ADDRCONF(NETDEV_CHANGE): eth0: link becomes ready
2024-01-30T22:56:53-06:00 IPv6: ADDRCONF(NETDEV_CHANGE): veth2: link becomes ready
2024-01-30T22:56:53-06:00 br-start9: port 3(veth2) entered blocking state
2024-01-30T22:56:53-06:00 br-start9: port 3(veth2) entered forwarding state
2024-01-30T22:56:54-06:00 br-start9: port 4(veth3) entered blocking state
2024-01-30T22:56:54-06:00 br-start9: port 4(veth3) entered disabled state
2024-01-30T22:56:54-06:00 device veth3 entered promiscuous mode
2024-01-30T22:56:54-06:00 br-start9: port 4(veth3) entered blocking state
2024-01-30T22:56:54-06:00 br-start9: port 4(veth3) entered forwarding state
2024-01-30T22:56:54-06:00 IPv6: ADDRCONF(NETDEV_CHANGE): veth3: link becomes ready
2024-01-31T06:11:56-06:00 perf: interrupt took too long (2508 > 2500), lowering kernel.perf_event_max_sample_rate to 79500

George · January 31, 2024, 7:17pm

Thanks for the log, but I’m not seeing anything that looks out of place, and don’t see the USB plug event either, which is what I was hoping I could glean anything at all from.

I don’t imagine this issue is actually related to the filesystem, but what filesystem has the 5TB been formatted with out of curiosity?

Djchilto · January 31, 2024, 9:53pm

I formatted the drive to ExFAT. Is that still the recommended format?

Djchilto · January 31, 2024, 9:57pm

I am going to return this one and get a 2TB back up since I know that one works with no issues. I just
tried it one more time and got the same result. I attached the most current kernel log. Hope it helps. Thanks!

freedom · February 2, 2024, 4:55am

Are they both USB powered (not wall powered)?
Can’t you just look up the specs for each drive’s model number to find the exact amperage draw through the USB?
Are they both SSD? Looks like the 5TB is a spinning drive, which obviously would take much more amperage. And if they are both spinning drives, then obviously the 5TB has multiple more platters, and thus mass, which requires a larger in-rush current to start spinning (like any stationary motor).
Um, why Seagate? Junk. If you are going to get your money back to buy a new drive, I sure wouldn’t be wasting it on Seagate. I’ve had 5 of them fail. Never again.

Djchilto · February 2, 2024, 3:16pm

Well…I returned the 5TB drive and picked up a 2 TB drive. Admittedly, it is a Seagate drive…if you have a recommendation for a different brand, that would be great. There was not any power characteristics that I could find and I didn’t visit any Seagate websites to try and find out…

That said, let me format this drive and lets see what happens… more to follow.

Djchilto · February 2, 2024, 3:42pm

Well…shit…I am at a loss here. The 2 TB drive is resulting in the same immediate server power loss as soon as I plug it in to the USB SS port as the 5 TB was having. Even more maddening is that I can plug in an 2 TB drive (same brand…Seagate) that I bought from Costco a couple of years ago, with no issues other than it doesn’t have enough free space left on it to back up my server. I formatted the drive to ExFAT and once again, it has no issues plugging into my desktop. Any ideas? Thanks!

freedom · February 2, 2024, 3:45pm

ANY brand other than Seagate.
Granted, I haven’t bought their crap for 5 years now. Who knows, maybe they changed all their quality. Some companies in the past were the best, then coasted on their reputation and let things deteriorate with cheap parts, then lost the ranking, then had new management turn things around again. Cyclical. Computer, vehicle, etc companies.

But from the Seagate price point in the market still being about the lowest, then I’d say their quality is the lowest too. And when I repeatedly lost my data, I found it’s just not worth it. Definitely get what you pay for. I have hard drives from other manufacturers literally over a decade old still spinning fine. Not a single Seagate though.

What were the model numbers of the two original drives?