rkotara

I found the offending cookie and deleted it, now my UI customization is saving as before.

Replaced the sata power cable extension I had on hand (Monoprice 108794) with one from Cable Matters and all is well so far. No more drops on the drives after 24 hours of running preclear on all 3 drives so far. Will update if anything changes.

Thanks for the diag on this. I do recall that I was not very confident of the Molex to Sata power connector but everything powered up fine. I'll swap things out until its stable, thanks!!

Thanks, just added that and the other preclear error logs.

TLDR: I've had Preclear fail on all 3 drives I just installed in my system using a Dell Perc H310 controller flash to IT mode. No smart errors, does that mean its the controller? I just installed a Dell H310 6Gbps SAS HBA (LSI 9211-8i) with IT MODE firmware. I added it to a free PCIe 16x slot and cabled up 3 refurb drives (which is why I want to preclear). I started Preclear on one, then seeing how long it would take (days), started the other two. All have failed since and that seems very unlikely. The failures all seem to be read errors and different points. There are no SMART issues from the data I can see. Breakout cables are new and all 3 drives failing seem to point to the controller. I guess its a bad controller? Any insight would be appreciated, thanks! preclear_disk_8DJGT6JH_21015.txt tower-diagnostics-20240226-1401.zip preclear_disk_9JH30AWT_27151.txt preclear_disk_8DJGT6JH_21015.txt

Yes! Finding this out through other posts, for sure. Not always a simple click-n-upgrade depending on your customization.

Ah, great to know. I have not made the move to 6.12.x yet but will soon.

It seems like he is running 6.12.4. I thought the macvlan issue is fixed in that version?

Saw this in your syslog. I'm just a newbie and do not know your setup, but maybe disk3 having issues could be part of the problem? Also, I use the plugin "CA Auto Update Applications" to auto update many of my plugins/dockers that are not critical (probably dont use it for Adguard in your list). Sep 23 11:43:14 Odyssey root: Fix Common Problems Version 2023.07.29 Sep 23 11:43:24 Odyssey root: Fix Common Problems: Error: disk3 (WDC_WD30EFRX-68EUZN0_WD-WCC4N7VNY6K8) has read errors Sep 23 11:43:25 Odyssey root: Fix Common Problems: Warning: Plugin unassigned.devices.plg is not up to date Sep 23 11:43:25 Odyssey root: Fix Common Problems: Warning: Docker Application AdGuard-Home has an update available for it Sep 23 11:43:25 Odyssey root: Fix Common Problems: Warning: Docker Application bazarr has an update available for it Sep 23 11:43:25 Odyssey root: Fix Common Problems: Warning: Docker Application Chromium has an update available for it Sep 23 11:43:25 Odyssey root: Fix Common Problems: Warning: Docker Application overseerr has an update available for it Sep 23 11:43:25 Odyssey root: Fix Common Problems: Warning: Docker Application plexautoskip has an update available for it Sep 23 11:43:25 Odyssey root: Fix Common Problems: Warning: Docker Application prowlarr has an update available for it Sep 23 11:43:25 Odyssey root: Fix Common Problems: Warning: Docker Application radarr has an update available for it Sep 23 11:43:25 Odyssey root: Fix Common Problems: Warning: Docker Application sabnzbd has an update available for it Sep 23 11:43:25 Odyssey root: Fix Common Problems: Warning: Docker Application sonarr has an update available for it Sep 23 11:43:25 Odyssey root: Fix Common Problems: Warning: Docker Application tautulli has an update available for it Sep 23 11:43:25 Odyssey root: Fix Common Problems: Warning: Docker Application UptimeKuma has an update available for it Sep 23 11:45:11 Odyssey root: Fix Common Problems: Other Warning: Unassigned Devices Plus not installed Sep 23 11:45:11 Odyssey root: Fix Common Problems: Other Warning: Background notifications not enabled Sep 23 11:45:11 Odyssey root: Fix Common Problems: Warning: Jumbo Frames detected on eth0 ** Ignored

Will do and thanks for the quick reply!

I have a btrfs cache pool of two SSD drives and got an alert about a CRC error on one drive (which shows up in smart data as 1 total). Is there any action to take here if this does not repeat? From what I've read and from the logs, it seems like it reset the link and wrote the data and I'm good for now unless it keeps happening, which is when I should reseat cables, etc... Just wanted to check with the forum if this is the right information. Thanks! (log of entire event below) Aug 15 18:57:56 Tower kernel: ata4.00: exception Emask 0x10 SAct 0x7000000 SErr 0x400100 action 0x6 frozen Aug 15 18:57:56 Tower kernel: ata4.00: irq_stat 0x08000008, interface fatal error Aug 15 18:57:56 Tower kernel: ata4: SError: { UnrecovData Handshk } Aug 15 18:57:56 Tower kernel: ata4.00: failed command: WRITE FPDMA QUEUED Aug 15 18:57:56 Tower kernel: ata4.00: cmd 61/20:c0:e0:17:46/00:00:00:00:00/40 tag 24 ncq dma 16384 out Aug 15 18:57:56 Tower kernel: res 40/00:d0:a0:15:46/00:00:00:00:00/40 Emask 0x10 (ATA bus error) Aug 15 18:57:56 Tower kernel: ata4.00: status: { DRDY } Aug 15 18:57:56 Tower kernel: ata4.00: failed command: WRITE FPDMA QUEUED Aug 15 18:57:56 Tower kernel: ata4.00: cmd 61/20:c8:a0:16:46/00:00:00:00:00/40 tag 25 ncq dma 16384 out Aug 15 18:57:56 Tower kernel: res 40/00:d0:a0:15:46/00:00:00:00:00/40 Emask 0x10 (ATA bus error) Aug 15 18:57:56 Tower kernel: ata4.00: status: { DRDY } Aug 15 18:57:56 Tower kernel: ata4.00: failed command: WRITE FPDMA QUEUED Aug 15 18:57:56 Tower kernel: ata4.00: cmd 61/20:d0:a0:15:46/00:00:00:00:00/40 tag 26 ncq dma 16384 out Aug 15 18:57:56 Tower kernel: res 40/00:d0:a0:15:46/00:00:00:00:00/40 Emask 0x10 (ATA bus error) Aug 15 18:57:56 Tower kernel: ata4.00: status: { DRDY } Aug 15 18:57:56 Tower kernel: ata4: hard resetting link Aug 15 18:57:56 Tower kernel: ata4: SATA link up 6.0 Gbps (SStatus 133 SControl 300) Aug 15 18:57:56 Tower kernel: ata4.00: supports DRM functions and may not be fully accessible Aug 15 18:57:56 Tower kernel: ata4.00: supports DRM functions and may not be fully accessible Aug 15 18:57:56 Tower kernel: ata4.00: configured for UDMA/133 Aug 15 18:57:56 Tower kernel: ata4: EH complete Aug 15 18:57:56 Tower kernel: ata4.00: Enabling discard_zeroes_data

I believe any of the 4.x versions, which also can run on non-UEFI systems as a bonus. Here is a link to the usb installer version of that: https://www.memtest86.com/downloads/memtest86-4.3.7-usb.img.zip

My single threaded memtest will not run a full cycle in 6 hours, but is very accurate on testing. Might be best to let it run a full cycle and ensure your using the single threaded (older) memtest86. The newer multi-threaded version will miss some ram issues in my experience.

Seems like a logic issue when a mount point (directory) is present and not a "mount". The code in this line is looking for a directory: if [[ -d /var/lib/docker_bind ]]; then umount /var/lib/docker_bind || logger -t docker Error: RAM-Disk bind unmount failed while docker stops!; fi\ But maybe something like this would work better since it actually checks for a mount: mount | awk '{if ($3 == "/var/lib/docker_bind") { exit 0}} ENDFILE{exit -1}' && umount /var/lib/docker_bind || logger -t docker Error: RAM-Disk bind unmount failed while docker stops!\ Of course, I cant really test this since I'm not using the script yet, I'm just following along until I upgrade and add this afterward or hope its part of future "improvements".

Anyone else getting "not available" for this plugin when looking at update status on the plugin page?

I've created a quick script to log my SSD write accumulation so I can watch it without having to grab it manually. This works great for my Samsung SSDs, which I prefer, may not work for other brands. Since people watching this issue might find it useful, I'm thought I'd posting it here. Just change the /dev/sd? to your devices (I have two SSDs in a pool, sde and sdg). This outputs to a csv files in my /mnt/user/down folder (change down to your favorite folder for this) called SSD.csv. I run it daily using the user scripts plugin. This makes it easy to just open with Excel and check it from time to time and add formulas to compute daily accumulation, etc. This is pretty basic, so I didnt include any header row in the script itself, but its this (LBAW=LBA written, GBW=Gigabyte Written): Date,Time,sde LBAW,sde GBW,sdg LBAW,sdg GBW #!/bin/bash dt=`date +"%D,%T"` sdeLBA=`smartctl -Ai /dev/sde | grep LBA | awk '{print $NF}'` sdeGB=$(($sdeLBA*512/1024**3)) sdgLBA=`smartctl -Ai /dev/sdg | grep LBA | awk '{print $NF}'` sdgGB=$(($sdgLBA*512/1024**3)) echo "$dt,$sdeLBA,$sdeGB,$sdgLBA,$sdgGB" >> /mnt/user/down/SSD.csv Update: After several days of mixed but typical usage (normal runtime writes and a few container updates), I found that writes are under 10GB per day to cache for my setup. This is after implementing several of the mods people have mentioned in this thread and with about 6 active containers only.

Bump! Very interested in this as should all other users. I know I'm new here, but all the more reason as I immediately discovered this is a pain point for my SSD cache once I set it up.

Is there any regular cadence on unraid releases? I've just started so wondering how long that might be since I've only got one docker not upgrading due to this.

I just had this same issue and had to reboot to see my USB 3 connected drive.