June 7, 20251 yr I am sharing my last reboot start up. Ive been having a ton of disk issues that started a month ago and has gotten more odd. One of my HD #5 went disabled with a red x mark. I did a few fs fixes and then rebuilt the drive and it would work for a few days before going back to disabled. I changed 4 of my sata cables with new ones. It still occurred after and then I replaced my PCIe sata card. This is my new card, I believe its supported. After changing the cables it became clear I plugged one sata cable in a different order as now disk 2 was being disabled and not 5. But now disk 2 is saying Unmountable: wrong or no file system, and disk 1 is now disabled wit the red x. Is this a power issue or something else?Jun 7 00:14:02 Tower rc.docker: container_add_route AirConnectJun 7 00:14:02 Tower rc.docker: AirConnect: started successfully!Jun 7 00:14:03 Tower kernel: docker0: port 1(vethe51ed72) entered blocking stateJun 7 00:14:03 Tower kernel: docker0: port 1(vethe51ed72) entered disabled stateJun 7 00:14:03 Tower kernel: vethe51ed72: entered allmulticast modeJun 7 00:14:03 Tower kernel: vethe51ed72: entered promiscuous modeJun 7 00:14:03 Tower kernel: docker0: port 1(vethe51ed72) entered blocking stateJun 7 00:14:03 Tower kernel: docker0: port 1(vethe51ed72) entered forwarding stateJun 7 00:14:03 Tower kernel: docker0: port 1(vethe51ed72) entered disabled stateJun 7 00:14:03 Tower dnsmasq[31728]: started, version 2.90 cachesize 150Jun 7 00:14:03 Tower dnsmasq[31728]: compile time options: IPv6 GNU-getopt DBus no-UBus i18n IDN2 DHCP DHCPv6 no-Lua TFTP conntrack ipset no-nftset auth cryptohash DNSSEC loop-detect inotify dumpfileJun 7 00:14:03 Tower dnsmasq-dhcp[31728]: DHCP, IP range 192.168.122.2 -- 192.168.122.254, lease time 1hJun 7 00:14:03 Tower dnsmasq-dhcp[31728]: DHCP, sockets bound exclusively to interface virbr0Jun 7 00:14:03 Tower dnsmasq[31728]: reading /etc/resolv.confJun 7 00:14:03 Tower dnsmasq[31728]: using nameserver 100.100.100.100#53Jun 7 00:14:03 Tower dnsmasq[31728]: read /etc/hosts - 3 namesJun 7 00:14:03 Tower dnsmasq[31728]: read /var/lib/libvirt/dnsmasq/default.addnhosts - 0 namesJun 7 00:14:03 Tower dnsmasq-dhcp[31728]: read /var/lib/libvirt/dnsmasq/default.hostsfileJun 7 00:14:03 Tower kernel: qemu-system-x86[31734]: memfd_create() called without MFD_EXEC or MFD_NOEXEC_SEAL setJun 7 00:14:03 Tower kernel: eth0: renamed from vethe6c8ba2Jun 7 00:14:03 Tower kernel: docker0: port 1(vethe51ed72) entered blocking stateJun 7 00:14:03 Tower kernel: docker0: port 1(vethe51ed72) entered forwarding stateJun 7 00:14:03 Tower tips.and.tweaks: Tweaks AppliedJun 7 00:14:03 Tower unassigned.devices: Mounting 'Auto Mount' Remote Shares...Jun 7 00:14:04 Tower unassigned.devices: Using Gateway '192.168.1.1' for Remote Shares.Jun 7 00:14:04 Tower unassigned.devices: Waiting 5 secs before mounting Remote Shares...Jun 7 00:14:04 Tower rc.docker: container_add_route Backblaze_Personal_BackupJun 7 00:14:04 Tower rc.docker: Backblaze_Personal_Backup: started successfully!Jun 7 00:14:04 Tower rc.docker: container_add_route binhex-plexJun 7 00:14:04 Tower rc.docker: binhex-plex: started successfully!Jun 7 00:14:05 Tower kernel: docker0: port 2(veth855d5d5) entered blocking stateJun 7 00:14:05 Tower kernel: docker0: port 2(veth855d5d5) entered disabled stateJun 7 00:14:05 Tower kernel: veth855d5d5: entered allmulticast modeJun 7 00:14:05 Tower kernel: veth855d5d5: entered promiscuous modeJun 7 00:14:05 Tower dnsmasq[31728]: reading /etc/resolv.confJun 7 00:14:05 Tower dnsmasq[31728]: using nameserver 100.100.100.100#53Jun 7 00:14:05 Tower kernel: eth0: renamed from veth386bf23Jun 7 00:14:05 Tower kernel: docker0: port 2(veth855d5d5) entered blocking stateJun 7 00:14:05 Tower kernel: docker0: port 2(veth855d5d5) entered forwarding stateJun 7 00:14:06 Tower rc.docker: container_add_route binhex-radarrJun 7 00:14:06 Tower rc.docker: binhex-radarr: started successfully!Jun 7 00:14:06 Tower kernel: docker0: port 3(veth3ba7b0a) entered blocking stateJun 7 00:14:06 Tower kernel: docker0: port 3(veth3ba7b0a) entered disabled stateJun 7 00:14:06 Tower kernel: veth3ba7b0a: entered allmulticast modeJun 7 00:14:06 Tower kernel: veth3ba7b0a: entered promiscuous modeJun 7 00:14:06 Tower kernel: docker0: port 3(veth3ba7b0a) entered blocking stateJun 7 00:14:06 Tower kernel: docker0: port 3(veth3ba7b0a) entered forwarding stateJun 7 00:14:06 Tower kernel: docker0: port 3(veth3ba7b0a) entered disabled stateJun 7 00:14:07 Tower kernel: eth0: renamed from vethea54035Jun 7 00:14:07 Tower kernel: docker0: port 3(veth3ba7b0a) entered blocking stateJun 7 00:14:07 Tower kernel: docker0: port 3(veth3ba7b0a) entered forwarding stateJun 7 00:14:07 Tower kernel: cp210x ttyUSB0: cp210x converter now disconnected from ttyUSB0Jun 7 00:14:07 Tower kernel: cp210x 3-2:1.0: device disconnectedJun 7 00:14:07 Tower kernel: cp210x ttyUSB1: cp210x converter now disconnected from ttyUSB1Jun 7 00:14:07 Tower kernel: cp210x 3-2:1.1: Failed to retrieve ACPI GPIO chipJun 7 00:14:07 Tower kernel: cp210x 3-2:1.1: device disconnectedJun 7 00:14:07 Tower rc.docker: container_add_route binhex-sabnzbdJun 7 00:14:07 Tower rc.docker: binhex-sabnzbd: started successfully!Jun 7 00:14:07 Tower dnsmasq[31728]: reading /etc/resolv.confJun 7 00:14:07 Tower dnsmasq[31728]: using nameserver 100.100.100.100#53Jun 7 00:14:07 Tower kernel: docker0: port 4(vethe7a020c) entered blocking stateJun 7 00:14:07 Tower kernel: docker0: port 4(vethe7a020c) entered disabled stateJun 7 00:14:07 Tower kernel: vethe7a020c: entered allmulticast modeJun 7 00:14:07 Tower kernel: vethe7a020c: entered promiscuous modeJun 7 00:14:07 Tower kernel: docker0: port 4(vethe7a020c) entered blocking stateJun 7 00:14:07 Tower kernel: docker0: port 4(vethe7a020c) entered forwarding stateJun 7 00:14:08 Tower kernel: docker0: port 4(vethe7a020c) entered disabled stateJun 7 00:14:08 Tower dnsmasq[31728]: reading /etc/resolv.confJun 7 00:14:08 Tower dnsmasq[31728]: using nameserver 100.100.100.100#53Jun 7 00:14:08 Tower kernel: 8021q: adding VLAN 0 to HW filter on device macvtap0Jun 7 00:14:08 Tower kernel: eth0: renamed from veth67f4179Jun 7 00:14:08 Tower kernel: docker0: port 4(vethe7a020c) entered blocking stateJun 7 00:14:08 Tower kernel: docker0: port 4(vethe7a020c) entered forwarding stateJun 7 00:14:09 Tower rc.docker: container_add_route binhex-sonarrJun 7 00:14:09 Tower rc.docker: binhex-sonarr: started successfully!Jun 7 00:14:09 Tower kernel: docker0: port 5(veth4108512) entered blocking stateJun 7 00:14:09 Tower kernel: docker0: port 5(veth4108512) entered disabled stateJun 7 00:14:09 Tower kernel: veth4108512: entered allmulticast modeJun 7 00:14:09 Tower kernel: veth4108512: entered promiscuous modeJun 7 00:14:09 Tower dnsmasq[31728]: reading /etc/resolv.confJun 7 00:14:09 Tower dnsmasq[31728]: using nameserver 100.100.100.100#53Jun 7 00:14:11 Tower kernel: eth0: renamed from veth343adb4Jun 7 00:14:11 Tower kernel: docker0: port 5(veth4108512) entered blocking stateJun 7 00:14:11 Tower kernel: docker0: port 5(veth4108512) entered forwarding stateJun 7 00:14:11 Tower rc.docker: container_add_route GrafanaJun 7 00:14:11 Tower rc.docker: Grafana: started successfully!Jun 7 00:14:12 Tower rc.docker: Containers started.Jun 7 00:14:12 Tower dnsmasq[31728]: reading /etc/resolv.confJun 7 00:14:12 Tower dnsmasq[31728]: using nameserver 100.100.100.100#53Jun 7 00:14:16 Tower kernel: usb 3-2: reset full-speed USB device number 2 using xhci_hcd
Join the conversation
You can post now and register later. If you have an account, sign in now to post with your account.
Note: Your post will require moderator approval before it will be visible.