Stubbs

Members
  • Posts

    115
  • Joined

  • Last visited

Recent Profile Visitors

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

Stubbs's Achievements

Apprentice

Apprentice (3/14)

3

Reputation

  1. Alright, I'm not 100% sure this is what caused it, but when removing the tray, I noticed the front two screws holding the hard drive in had slightly thicker heads than the back two. It was still connected to the SATA and power connecter in the drive bay, but it probably wasn't the most stable connection. I replaced those two thicker screws with the correct thinner-head ones, and all of a sudden it works fine.
  2. Well, looks like I fixed my problem. Thanks for the help. I have a hunch for what caused it, but it's too stupid for words.
  3. I've just taken the drive out, connected it to my Windows computer with an HDD docking bay, formatted it as NTFS and it seems to be working fine. At this point, I honestly have no clue what's going on. I'll try formatting it again on Unraid in yet another slot.
  4. I can't remember if the previous diagnostics was before or after I tried the rebuild. This one attached is after the failed rebuild and completed read check: tower-diagnostics-20220124-2349.zip
  5. Yeah, I tried rebuilding, and at the 2% mark, it stopped, disabled the drive and started another "read check". I'm just going to have to RMA and replace.
  6. According to people in the Unraid Discord, it's literally a failed disk that needs to be replaced.
  7. I don't have the time to open up the server and adjust the cabling right now, but I did try putting the problem drive in a different bay (with a different cable). Same problem, same drive. Just for the sake of it, I'm attaching the diagnostics .zip for when the problem disk is actually in the array, but not functioning. tower-diagnostics-20220123-1728.zip
  8. It's just weird that it was working perfectly fine for the last 6 or so months in this very bay, only to stop working now. Are you sure it's not some kind of xfs filesystem error? Because I actually did manage to re-mount the drive into my array, it's just marked with a red x saying "device disabled, contents emulated"- cue to it starting a "Read check" which will take about 26 hours to complete. Also my parity drive currently has 144 read errors, disk 3 has 168 read errors and disk 4 (the broken one) has 1024 read errors.
  9. I forgot about the diagnostics log, sorry. Here it is (attached). This drive is also in one of the hotswap bays. I had no had this issue before and it has only just occurred abruptly. Unraid also just automatically initiated a "read check". I don't know if that will help or not. tower-diagnostics-20220124-0251.zip
  10. Disk 4 in my array seems to have issues. It automatically dismounted at some point in the last day, and I don't know why or what's going on. Trying to remount it does not work. When I rebooted the server, it started a file system check. It prompted me to open a certain log, which kept going on and on infinitely: Again, I do not understand what any of this means. My Unraid's main log looks like this: Jan 24 02:18:13 Tower kernel: md4: writeback error on inode 98313, offset 125083648, sector 674783544 Jan 24 02:18:13 Tower kernel: XFS (sdg1): Filesystem has duplicate UUID 0fb26a6d-0040-405b-92c9-4fe171b93e9b - can't mount Jan 24 02:18:13 Tower unassigned.devices: Mount of 'sdg1' failed: 'mount: /mnt/disks/WD-WX22DB0KE762: wrong fs type, bad option, bad superblock on /dev/sdg1, missing codepage or helper program, or other error. ' Jan 24 02:18:13 Tower unassigned.devices: Partition 'WD-WX22DB0KE762' cannot be mounted. Jan 24 02:18:33 Tower kernel: ata6.00: exception Emask 0x0 SAct 0x40 SErr 0x0 action 0x0 Jan 24 02:18:33 Tower kernel: ata6.00: irq_stat 0x40000008 Jan 24 02:18:33 Tower kernel: ata6.00: failed command: WRITE FPDMA QUEUED Jan 24 02:18:33 Tower kernel: ata6.00: cmd 61/20:30:20:35:d2/00:00:3b:00:00/40 tag 6 ncq dma 16384 out Jan 24 02:18:33 Tower kernel: res 41/10:00:20:35:d2/00:00:3b:00:00/40 Emask 0x481 (invalid argument) <F> Jan 24 02:18:33 Tower kernel: ata6.00: status: { DRDY ERR } Jan 24 02:18:33 Tower kernel: ata6.00: error: { IDNF } Jan 24 02:18:33 Tower kernel: ata6.00: configured for UDMA/133 Jan 24 02:18:33 Tower kernel: ata6: EH complete Jan 24 02:18:52 Tower emhttpd: cmd: /usr/local/emhttp/plugins/dynamix.plugin.manager/scripts/plugin update community.applications.plg Jan 24 02:18:52 Tower root: plugin: running: anonymous Jan 24 02:18:52 Tower root: plugin: running: anonymous Jan 24 02:18:52 Tower root: plugin: creating: /boot/config/plugins/community.applications/community.applications-2022.01.22-x86_64-1.txz - downloading from URL https://raw.githubusercontent.com/Squidly271/community.applications/master/archive/community.applications-2022.01.22-x86_64-1.txz Jan 24 02:18:53 Tower root: plugin: checking: /boot/config/plugins/community.applications/community.applications-2022.01.22-x86_64-1.txz - MD5 Jan 24 02:18:53 Tower root: plugin: running: /boot/config/plugins/community.applications/community.applications-2022.01.22-x86_64-1.txz Jan 24 02:18:53 Tower root: plugin: running: anonymous Jan 24 02:18:56 Tower emhttpd: cmd: /usr/local/emhttp/plugins/dynamix.plugin.manager/scripts/plugin update unassigned.devices.plg Jan 24 02:18:56 Tower root: plugin: running: anonymous Jan 24 02:18:56 Tower root: plugin: creating: /boot/config/plugins/unassigned.devices/unassigned.devices-2022.01.21.tgz - downloading from URL https://github.com/dlandon/unassigned.devices/raw/master/unassigned.devices-2022.01.21.tgz Jan 24 02:18:56 Tower nginx: 2022/01/24 02:18:56 [error] 5625#5625: *4570 FastCGI sent in stderr: "Primary script unknown" while reading response header from upstream, client: 192.168.1.217, server: , request: "POST /plugins/unassigned.devices/UnassignedDevices.php HTTP/1.1", upstream: "fastcgi://unix:/var/run/php5-fpm.sock:", host: "192.168.1.5", referrer: "http://192.168.1.5/Main" Jan 24 02:18:56 Tower nginx: 2022/01/24 02:18:56 [error] 5625#5625: *4086 FastCGI sent in stderr: "Primary script unknown" while reading response header from upstream, client: 10.10.20.217, server: , request: "POST /plugins/unassigned.devices/UnassignedDevices.php HTTP/1.1", upstream: "fastcgi://unix:/var/run/php5-fpm.sock:", host: "192.168.1.5, referrer: "http://192.168.1.5/Main" Jan 24 02:18:57 Tower root: plugin: checking: /boot/config/plugins/unassigned.devices/unassigned.devices-2022.01.21.tgz - MD5 Jan 24 02:18:57 Tower root: plugin: creating: /tmp/start_unassigned_devices - from INLINE content Jan 24 02:18:57 Tower root: plugin: setting: /tmp/start_unassigned_devices - mode to 0770 Jan 24 02:18:57 Tower root: plugin: skipping: /boot/config/plugins/unassigned.devices/unassigned.devices.cfg already exists Jan 24 02:18:57 Tower root: plugin: skipping: /boot/config/plugins/unassigned.devices/samba_mount.cfg already exists Jan 24 02:18:57 Tower root: plugin: skipping: /boot/config/plugins/unassigned.devices/iso_mount.cfg already exists Jan 24 02:18:57 Tower root: plugin: skipping: /tmp/unassigned.devices/smb-settings.conf already exists Jan 24 02:18:57 Tower root: plugin: skipping: /tmp/unassigned.devices/config/smb-extra.conf already exists Jan 24 02:18:57 Tower root: plugin: skipping: /tmp/unassigned.devices/add-smb-extra already exists Jan 24 02:18:57 Tower root: plugin: setting: /tmp/unassigned.devices/add-smb-extra - mode to 0770 Jan 24 02:18:57 Tower root: plugin: skipping: /tmp/unassigned.devices/remove-smb-extra already exists Jan 24 02:18:57 Tower root: plugin: setting: /tmp/unassigned.devices/remove-smb-extra - mode to 0770 Jan 24 02:18:57 Tower root: plugin: running: anonymous I've attached the SMART reports for both Disk 4 and the Parity Drive (which also has read errors). Can someone please explain to me the problems? Did my disk fail? Is there anything that I should be doing? tower-smart-20220124-0219 (disk 4).zip tower-smart-20220124-0221 (parity).zip tower-diagnostics-20220124-0251.zip
  11. Delugevpn has simply stopped working for me. Same applies to the other binhex vpn torrent clients. Here is a log excerpt: 2022-01-20 03:12:04,177 DEBG 'start-script' stdout output: [info] Attempting to get external IP using 'http://checkip.amazonaws.com'... 2022-01-20 03:12:32,216 DEBG 'start-script' stdout output: [info] Failed on last attempt, attempting to get external IP using 'http://whatismyip.akamai.com'... 2022-01-20 03:13:00,257 DEBG 'start-script' stdout output: [info] Failed on last attempt, attempting to get external IP using 'https://ifconfig.co/ip'... 2022-01-20 03:13:28,295 DEBG 'start-script' stdout output: [info] Failed on last attempt, attempting to get external IP using 'https://showextip.azurewebsites.net'... 2022-01-20 03:13:56,336 DEBG 'start-script' stdout output: [warn] Cannot determine external IP address, performing tests before setting to '127.0.0.1'... [info] Show name servers defined for container 2022-01-20 03:13:56,337 DEBG 'start-script' stdout output: nameserver 209.222.18.222 nameserver 84.200.69.80 nameserver 37.235.1.174 nameserver 1.1.1.1 nameserver 209.222.18.218 nameserver 37.235.1.177 nameserver 84.200.70.40 nameserver 1.0.0.1 2022-01-20 03:13:56,337 DEBG 'start-script' stdout output: [info] Show contents of hosts file 2022-01-20 03:13:56,338 DEBG 'start-script' stdout output: 127.0.0.1 localhost ::1 localhost ip6-localhost ip6-loopback fe00::0 ip6-localnet ff00::0 ip6-mcastprefix ff02::1 ip6-allnodes ff02::2 ip6-allrouters 172.17.0.2 1d6c45f7f19a vpnip vpndomain 2022-01-20 03:13:56,340 DEBG 'start-script' stdout output: [info] Application does not require port forwarding or VPN provider is != pia, skipping incoming port assignment 2022-01-20 03:13:56,392 DEBG 'watchdog-script' stdout output: [info] Deluge listening interface IP 0.0.0.0 and VPN provider IP 10.8.8.7 different, marking for reconfigure 2022-01-20 03:13:56,397 DEBG 'watchdog-script' stdout output: [info] Deluge not running 2022-01-20 03:13:56,401 DEBG 'watchdog-script' stdout output: [info] Deluge Web UI not running Torrenting works fine on my desktop with the exact same VPN, but not on the Deluge container on my Unraid server. Every other container is functioning normally.
  12. Sorry for the late response. I didn't realize there was a way to manually update the lists by inputting pihole -g into the console. That fixed the issue.
  13. Are updates for containers currently broken? All my containers are listed as "not available" under version in the docker tab. In my Unraid logs, I get the error: Jan 18 19:21:56 Unraidserver nginx: 2022/01/18 19:21:56 [error] 5536#5536: *1645538 upstream timed out (110: Connection timed out) while reading response header from upstream, client: 192.168.5.5, server: , request: "POST /plugins/dynamix.docker.manager/include/DockerUpdate.php HTTP/1.1", upstream: "fastcgi://unix:/var/run/php5-fpm.sock", host: "192.168.5.5", referrer: "http://192.168.5.5/Docker/" I have disabled all my firewalls and DNS sinkholes, and I still get this problem. I cannot update containers or plugins.
  14. Actually I'm not even sure it's an issue with my firewall. I just turned everything off and I still got that error in the log. What gives?