taflix

Woke up this morning to this error, is my drive toast? Diags attached. Thank you! taflix-unraid-diagnostics-20251001-1015.zip

Thanks and dependable as always JorgeB!

UUID: 7a09f9b9-bc8c-4c79-ae3e-660e1eea5a90 Scrub started: Wed May 28 11:07:12 2025 Status: finished Duration: 0:05:59 Total to scrub: 219.04GiB Rate: 624.77MiB/s Error summary: no errors foundAnd diags attached, thank you @JorgeB ! taflix-unraid-diagnostics-20250528-1126.zip

Got this error this morning: Diagnostics attached. Rebooted in the meantime. Thank you! taflix-unraid-diagnostics-20250526-0823.zip

Thanks JorgeB!

Hi JorgeB, Cables are good, but the parity drive is still disabled? New diagnostics attached. Thank you! taflix-unraid-diagnostics-20250519-1931.zip

I started moving data from cache onto the array and noticed this: It will not spin up? Is my parity drive toast or something else? Thank you! taflix-unraid-diagnostics-20250518-2156.zip

Hello, just recently upgrade a HDD in my array from 14TB to 28TB. The swap completely without any errors. However, when I try to write new content to array, I get this error: No issues writing data to the cache. Diagnostics attached. Thank you! taflix-unraid-diagnostics-20250518-1130.zip

Thank you JorgeB!

ran check ran fix attached results ran check again: Phase 1 - find and verify superblock... Phase 2 - using internal log - zero log... - scan filesystem freespace and inode maps... - found root inode chunk Phase 3 - for each AG... - scan (but don't clear) agi unlinked lists... - process known inodes and perform inode discovery... - agno = 0 - agno = 1 - agno = 2 - agno = 3 - agno = 4 - agno = 5 - agno = 6 - agno = 7 - agno = 8 - agno = 9 - agno = 10 - agno = 11 - agno = 12 - process newly discovered inodes... Phase 4 - check for duplicate blocks... - setting up duplicate extent list... - check for inodes claiming duplicate blocks... - agno = 0 - agno = 1 - agno = 2 - agno = 3 - agno = 4 - agno = 5 - agno = 6 - agno = 7 - agno = 8 - agno = 9 - agno = 10 - agno = 11 - agno = 12 No modify flag set, skipping phase 5 Phase 6 - check inode connectivity... - traversing filesystem ... - traversal finished ... - moving disconnected inodes to lost+found ... Phase 7 - verify link counts... No modify flag set, skipping filesystem flush and exiting. I think it's fixed now? Thank you JorgeB. check file system.txt

Recently upgraded an HDD in my array to a larger capacity drive. Everything rebuilt just fine and parity is good. Then, updated to 7.0.1 Then, noticed this error on the HDD that I upgraded? Tried stopping and restarting the array but that didn't fix it. Diags attached. Any ideas how to fix? Thank you! taflix-unraid-diagnostics-20250408-2317.zip

If I understand correctly, when I replace an existing parity drive with a larger parity drive, then UNRAID will write to EVERY SECTOR of the new drive as part of the parity building process? Which is similar to a "torture test" to make test every sector of the drive? This seems like a good practice because if there's an issue with the new drive, then we'll know right away. Also, we will still have the existing parity drive as a backup. If building parity on the new larger drive is successful, then is it okay to clear the old parity drive and add it to the array as another data drive? Thanks TRURL!

You mention that adding a new hard drive as parity, UNRAID will write to every section of the new drive? I use pre-clear or clear to torture test new drives for failure withing the return period. Does adding a new hard drive as a parity do the same thing? Thank you!

Thanks, your explanation is much easier to understand. The "?" should be updated to something like: Run the mover until storage used on the cache pool reaches this amount. Example, 0% means move everything off the cache pool.

I'm going to try to manually move everything off the global_cache pool following your steps. Then, I'll redo the entire cache pool. I'm also going to upgrade the parity drive from 14 TB to 24 TB while I'm at it, so I can increase the ceiling for future storage upgrades. Any tips for that are appreciated! Thanks Jorge and everyone else who contributed!

Thank you. If there is an actual file in each folder, then how does this affect things?

Does anyone know what the second part of this image means? Free down/prime up to this level of used Primary (cache) space: Goal: To activate the mover when over 75% of cache drive is used Am I doing this right? Thank you!

And is this how you delete the duplicates? And is there an automated way to find and delete duplicates? Thank you!

Stopping the array causing my server to do this: EDIT: I figured this out. The gray "copy paste" looking icon actually opens a popup that lets you view currently running jobs and cancel them. That icon looks like "copy paste". Next update should just change it to text: View currently running jobs...

Sorry I don't understand, do you mean this? What services, would that be, for example? Do you mean just stop anything that would write to the shares? And then try the Mover again? The mover hasn't been working but do you think it will if we do all the preceding steps? Thanks Jorge!

Thanks! I'll look into what single mode is. Meanwhile, any ideas to get the cache pool working again?

Another diagnostics, just in case you need it. taflix-unraid-diagnostics-20250302-1044.zip

This diagnostics is taking a while, it seems to be stuck at? mkdir -p /boot/logs /usr/local/emhttp/plugins/fix.common.problems/scripts/scan.php diagnostics Fix Common Problems Scan: Downloading Support Files Fix Common Problems Scan: 1% HPApresent Fix Common Problems Scan: 2% checkServerDate Fix Common Problems Scan: 3% eth0NoIP Fix Common Problems Scan: 4% isArrayStarted Fix Common Problems Scan: 5% impliedArrayFilesOnCache Fix Common Problems Scan: 7% cacheOnlyFilesOnArray Fix Common Problems Scan: 8% arrayOnlyFilesOnCache Fix Common Problems Scan: 9% pluginUpdateCheck Fix Common Problems Scan: 10% dockerUpdateCheck Fix Common Problems Scan: 11% autoUpdateCheck Fix Common Problems Scan: 13% sameShareDifferentCase Fix Common Problems Scan: 14% outsideCommunication Fix Common Problems Scan: 15% dockerAppdataCacheOnly Fix Common Problems Scan: 16% disabledDisksPresent Fix Common Problems Scan: 17% missingDisksPresent Fix Common Problems Scan: 19% readErrorsPresent Fix Common Problems Scan: 20% fileSystemErrors Fix Common Problems Scan: 21% pluginsUpToDate Fix Common Problems Scan: 22% dockerUpToDate Fix Common Problems Scan: 23% dockerConfigUserShare Fix Common Problems Scan: 25% varLogFilled Fix Common Problems Scan: 26% dockerImageFull Fix Common Problems Scan: 27% rootfsFull Fix Common Problems Scan: 28% scheduledParityChecks Fix Common Problems Scan: 29% shareIncludeExcludeSet Fix Common Problems Scan: 30% shareIncludeExcludeSameDisk Fix Common Problems Scan: 32% UDmountedSlaveMode Fix Common Problems Scan: 33% checkNotifications Fix Common Problems Scan: 34% blacklistedPluginsInstalled Fix Common Problems Scan: 35% illegalShareName Fix Common Problems Scan: 36% writeToDriveTest Fix Common Problems Scan: 38% flashDriveFull Fix Common Problems Scan: 39% checkForHack Fix Common Problems Scan: 40% checkForModeration Fix Common Problems Scan: 41% pluginNotCompatible Reboot and try again? Or, wait it out? Nevermind, I tried it again in a new tab and diagnostics worked! Thank you. taflix-unraid-diagnostics-20250302-0932.zip I tried to do a 3rd scrub after reboot and the scrub button did nothing. This time, the scrub button on my machine only worked after I stopped the array and start it again. Here are results of 3rd scrub: UUID: 72b21186-bd49-4186-a5c2-8710c07e0875 Scrub started: Sun Mar 2 08:43:06 2025 Status: finished Duration: 0:22:46 Total to scrub: 909.58GiB Rate: 681.85MiB/s Error summary: no errors found And what is says under Balance Status (in case you need this too?) Device size: 1.07TiB Device allocated: 921.75GiB Device unallocated: 171.88GiB Device missing: 0.00B Device slack: 0.00B Used: 909.58GiB Free (estimated): 183.98GiB (min: 98.04GiB) Free (statfs, df): 0.00B Data ratio: 1.00 Metadata ratio: 2.00 Global reserve: 512.00MiB (used: 0.00B) Multiple profiles: no Data Metadata System Id Path RAID0 RAID1 RAID1 Unallocated Total Slack -- --------- --------- ---------- -------- ----------- --------- ----- 1 /dev/sdj1 292.85GiB 1.00GiB 32.00MiB 171.88GiB 465.76GiB - 2 /dev/sdk1 231.85GiB 1.00GiB 32.00MiB 1.05MiB 232.88GiB - 3 /dev/sdh1 167.68GiB - - 1.02MiB 167.68GiB - 4 /dev/sdl1 167.68GiB - - 1.02MiB 167.68GiB - 5 /dev/sdi1 59.62GiB - - 1.02MiB 59.62GiB - -- --------- --------- ---------- -------- ----------- --------- ----- Total 919.69GiB 1.00GiB 32.00MiB 171.88GiB 1.07TiB 0.00B Used 907.59GiB 1020.73MiB 80.00KiB Thank you guys!

Is there a "Device Manager" equivalent in UNRAID that we can use to look up device names? Oh wait nvm, I found it in my Amazon purchase history: LSI 9207-8i 6Gbs SAS HBA P20 IT Mode For ZFS FreeNAS unRAID +2* 8087 SATA Cable Thanks! I had no idea these "best practices" existed when I first started using UNRAID and setting up this cache pool. I like the "?" feature and best practices would do well there besides explaining what the feature does. I set up 10% of the total space to be minimum free, is that a "best practice" amount? I also found some posts about scrubbing and set that to once/month as that seems to be the "best practice" recommendation. Thanks for the help over the weekend guys!

The scrub button didn't appear until I stopped the array and then start it again. UUID: 72b21186-bd49-4186-a5c2-8710c07e0875 Scrub started: Sun Mar 2 06:36:20 2025 Status: finished Duration: 0:22:41 Total to scrub: 908.82GiB Rate: 683.79MiB/s Error summary: no errors found Tried to do a second scrub, but again, had to start/stop array to see the scrub button appear. But, new problem... pressing the button just reloaded the page and it didn't show that scrub was running. Had to reboot and it finally did a second scrub: UUID: 72b21186-bd49-4186-a5c2-8710c07e0875 Scrub started: Sun Mar 2 07:46:51 2025 Status: aborted Duration: 0:02:15 Total to scrub: 910.50GiB Rate: 692.01MiB/s Error summary: no errors found