Parigot

Yeah I realized this after I deleted them. There wasn't that many anyway. But I'll keep your suggestion in mind for next time. To your first question, I wonder if this happens when sub-folders of a Share are created through cli or using a UI like Krusader.

so my media share is set to No for 'Use Cache Pool' but I still see 151Gb of files on the cache. Deleted it and now back to normal. Thanks for the help!

There you go. Thank you! diagnostics-20210709-1010.zip

Which files from the diags would help? All of them?

So this has probably been answered many times but I cannot find anything that would make sense to my issue. Last week, I've upgraded from 6.8.(don't remember) to 6.9.2. Right away after the update, my single cache drive of 500gb was almost full (64gb available). I didn't modified any settings on the shares regarding cache use. Does 6.9.X modifies anything that could cause this? If anyone has any idea what is happening here, I would really appreciate it. Happy to share any log/config required. Thanks community!

Confirmed this fixed the UI access issue.

After changing cable and port, running Preclear worked this time. Took long but it seems ok. Thx for the help everyone. ================================================================== 1.15 = unRAID server Pre-Clear disk /dev/sdb = cycle 1 of 1, partition start on sector 1 = Disk Pre-Clear-Read completed DONE = Step 1 of 10 - Copying zeros to first 2048k bytes DONE = Step 2 of 10 - Copying zeros to remainder of disk to clear it DONE = Step 3 of 10 - Disk is now cleared from MBR onward. DONE = Step 4 of 10 - Clearing MBR bytes for partition 2,3 & 4 DONE = Step 5 of 10 - Clearing MBR code area DONE = Step 6 of 10 - Setting MBR signature bytes DONE = Step 7 of 10 - Setting partition 1 to precleared state DONE = Step 8 of 10 - Notifying kernel we changed the partitioning DONE = Step 9 of 10 - Creating the /dev/disk/by* entries DONE = Step 10 of 10 - Verifying if the MBR is cleared. DONE = Disk Post-Clear-Read completed DONE Disk Temperature: 36C, Elapsed Time: 32:38:55 ========================================================================1.15 == WDCWD30EFRX-68EUZN0 WD-WCC4N5YF2774 == Disk /dev/sdb has been successfully precleared == with a starting sector of 1 ============================================================================ ** Changed attributes in files: /tmp/smart_start_sdb /tmp/smart_finish_sdb ATTRIBUTE NEW_VAL OLD_VAL FAILURE_THRESHOLD STATUS RAW_VALUE Temperature_Celsius = 114 123 0 ok 36 No SMART attributes are FAILING_NOW 0 sectors were pending re-allocation before the start of the preclear. 0 sectors were pending re-allocation after pre-read in cycle 1 of 1. 0 sectors were pending re-allocation after zero of disk in cycle 1 of 1. 0 sectors are pending re-allocation at the end of the preclear, the number of sectors pending re-allocation did not change. 0 sectors had been re-allocated before the start of the preclear. 0 sectors are re-allocated at the end of the preclear, the number of sectors re-allocated did not change.

Thanks RobJ I'm currently running a preclear using a new sata cable and using a different sata port on the motherboard. Will see how it goes. I'll try the SMART report right after. As for the parity drive, the 3TB RED will replace it. I made this build with parts I had laying around. The 3TB RED is the only brand new part. But more new parts will come around to improve it.

To add to this issue, I checked the System Logs and found the following for my drive. Wondering more and more if my drive is DOA... Apr 7 16:57:09 r2d2 kernel: Buffer I/O error on dev sdb, logical block 603280139, lost async page write Apr 7 16:57:09 r2d2 kernel: Buffer I/O error on dev sdb, logical block 603280140, lost async page write Apr 7 16:57:09 r2d2 kernel: Buffer I/O error on dev sdb, logical block 603280141, lost async page write Apr 7 16:57:09 r2d2 kernel: Buffer I/O error on dev sdb, logical block 603280142, lost async page write Apr 7 16:57:09 r2d2 kernel: Buffer I/O error on dev sdb, logical block 603280143, lost async page write Apr 7 16:57:09 r2d2 kernel: Buffer I/O error on dev sdb, logical block 603280144, lost async page write Apr 7 16:57:09 r2d2 kernel: Buffer I/O error on dev sdb, logical block 603280145, lost async page write Apr 7 16:57:09 r2d2 kernel: Buffer I/O error on dev sdb, logical block 603280146, lost async page write Apr 7 16:57:09 r2d2 kernel: Buffer I/O error on dev sdb, logical block 603280147, lost async page write Apr 7 16:57:09 r2d2 kernel: Buffer I/O error on dev sdb, logical block 603280148, lost async page write

I got that when I needed to update the firmware of my SAS Expander. But I think it could be almost anything. Maybe someone else has more ideas. Attaching a Syslog (v5 unRAID) or Diagnostics (v6 unRAID) would help someone else as well. I attached the Diagnostics to this post. r2d2-diagnostics-20160407-2044.zip

I just received a WD RED 3TB drive that I will use to replace my 1TB parity drive. I ran a preclear on it twice and got the same result. But I don't know what is the issue (if it is one). Any help would be greatly appreciated. Thanks ================================================================== 1.15 = unRAID server Pre-Clear disk /dev/sdb = cycle 1 of 1, partition start on sector 1 = = Step 1 of 10 - Copying zeros to first 2048k bytes DONE = Step 2 of 10 - Copying zeros to remainder of disk to clear it DONE = Step 3 of 10 - Disk is now cleared from MBR onward. DONE = Step 4 of 10 - Clearing MBR bytes for partition 2,3 & 4 DONE = Step 5 of 10 - Clearing MBR code area DONE = Step 6 of 10 - Setting MBR signature bytes DONE = Step 7 of 10 - Setting partition 1 to precleared state DONE = Step 8 of 10 - Notifying kernel we changed the partitioning DONE = Step 9 of 10 - Creating the /dev/disk/by* entries DONE = Step 10 of 10 - Verifying if the MBR is cleared. DONE = Elapsed Time: 5:39:04 ========================================================================1.15 == == SORRY: Disk /dev/sdb MBR could NOT be precleared == == out4= 00000 == out5= 00000 ============================================================================ 0000000