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!