B Train

Members
  • Posts

    30
  • Joined

  • Last visited

Recent Profile Visitors

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

B Train's Achievements

Noob

Noob (1/14)

1

Reputation

  1. Good news everyone, it worked. The TEST share is now PROTECTED! Previously the data went from cache to array. Now the data goes from cache to array also? Thank you Juan x1000! trurl, I have not been able to access the cache drive as you describe but I will keep on working on it. Thank you so much all for your help you guys really make it happen for the average guys like me.
  2. I will try this first and see if it works thank you Juan.
  3. @trurl: I downloaded and applied Dynamix File Manager Plugin. I've seen a few tutorials and navigated around but I think that Dynamix is made for navigating directories, not editing shares. My issue is found on the 'shares' menu. Once I click the dropdown for my share named 'TEST' I see that it is somehow split between the Array and the Cache, see attached. Also, you can see on the attached image that there is no option for deleting the 6mb folder under 'TEST' share.
  4. Thank you, I will try and report back.
  5. Thank you for your insight it is greatly appreciated. You 'hit it on the nail' as some would say.
  6. Thank you trurl. Apologies for missing something so basic but I genuinely am way over my head reading the release notes. It might as well be greek for a n00b like me. Glad to have such an amazing community.
  7. Thank you Jorge, that is clear from reading the forums which are an excellent source of information. Unfortunately I remain very confused as to why my 'TEST' share is not protected, as it is supposed to be saved entirely on the array. Reason I mention the 'TEST' share is because for some reason there is a 6b folder, apparently under my 'TEST' share, that is on the cache? Would you say that is the cause for the 'TEST' share not being protect? Does unRaid create that 6b folder?
  8. Thank you Jorge. Was this clarified at some point somewhere? For future reference, do you recall when this change took place? Cheers and thank you so very much for your help
  9. Greetings unRaid community, I am trying to trouble shoot an unrelated issue and I see that many times people mention the ability to set shares as 'Prefer'. *Apparently 'Prefer' means data will be kept on the cache and not moved to array, but this is unrelated to this post. When I enter the share settings for each of my shares I do not see the option to set anything to 'Prefer'. After installing Photoprism, I think that there is something set to 'Prefer' because Photoprism's files are set to stay on the cache drive. For those not familiar with Photoprism: this program indexes all photos on the array and then creates thumbnails on the cache for creating a readily accessible image gallery for other computers on that network. Going back to the issue: can someone please clarify the location of the 'Prefer' setting? Attached: the settings for my 'appdata' share.
  10. Greetings unRaid community, I am looking at the shares on my unRaid setup and I see a note that reads 'some or all files are unprotected'. Having researched the message 'some or all files are unprotected' on this forum I have discovered that - I should first run the mover, - files in use will not be moved and - a parity check must be run succesfully. I would greatly appreciate some help in helping me interpret what is going on and why are my shares unprotected. Here is a screenshot of my shares: Thank you for your help, please let me know if I can provide any other information.
  11. ChatNoir thank you so much for that information. It is very very helpful to me. I guess it is time to throw that HDD away!
  12. Thank you very much ChatNoir. Do you recommend running this test several times? Is the result of 'read failure' always terminal for a hard drive? Could the 'read failure' be due to any other factor, such as a loose cable? Thank you once again for your help!
  13. Thank you very much for your response. I did run an extended SMART test, which I believe is attached to my original post. Hoping I provided the right thing, if not, I will check and provide an updated SMART test
  14. Greetings UnRaid community. I am adding an HDD to my UnRaid setup and I receivd a Post-Read Verification after running a 'Pre-Clear'. My plan for the new HDD is to add it to my existing setup as a second parity. After running the PRE CLEAR steps described in a video by SpaceInvader One (linked at the bottom of this post) I get a message saying: "Post-read verification - - - - FAILED". Further information specific to my case is shown below. For future reference, a similar thread was created but was not helpful to me. The thread is located on the link below, by a user named 'Twisted'. The S.M.A.R.T. report for my disk in question is attached as a .txt file I have the following report, facilitated by the UnRaid GUI by clicking on 'Preclear Disk Log': ###################################################### Unraid Server Preclear of disk WD-WCC4E5X4NS26 Cycle 1 of 1, partition start on sector 64. Step 1 of 5 - Pre-read verification: [9:20:32 @ 118 MB/s] SUCCESS Step 2 of 5 - Zeroing the disk: [9:39:37 @ 115 MB/s] SUCCESS Step 3 of 5 - Writing Unraid's Preclear signature: SUCCESS Step 4 of 5 - Verifying Unraid's Preclear signature: SUCCESS Step 5 of 5 - Post-Read verification: FAIL Cycle elapsed time: 19:06:40 | Total elapsed time: 19:06:40 # S.M.A.R.T. Status (device type: default) ATTRIBUTE INITIAL STATUS Reallocated_Sector_Ct 0 - Power_On_Hours 75262 - Temperature_Celsius 26 - Reallocated_Event_Count 0 - Current_Pending_Sector 0 - Offline_Uncorrectable 0 - UDMA_CRC_Error_Count 0 - ###################################################### Can someone please help me decipher or diagnose what is the error here and how to go about correcting the error? The video I mentioned above is from Youtube. Author: SpaceInvaderOne Tile: 'How and why to PreClear your hard drives before adding to your array' Thank you for your help! WDC_WD40EFRX-68WT0N0_WD-WCC4E5X4NS26-20231231-1406.txt