lemoncurry

Members
  • Posts

    26
  • Joined

  • Last visited

Recent Profile Visitors

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

lemoncurry's Achievements

Newbie

Newbie (1/14)

1

Reputation

  1. Ahh, yes, I got confused between Cache settings and Array share settings. Obvious now really. Maybe I did add the zeros back when I first set it up, assuming the setting is bytes. ie 200000000=200MB not 204GB! Cheers. Thanks for the very fast assistance.
  2. Thanks for the very fast assistance.
  3. Hi, Global Cache set to YES, Min. free space: 200,000,000, which I incorrectly assume as Bytes, but apparently its 1024byte blocks (confusing)! So that means the global floor is set to >200GB! I don't recall ever looking at this setting so it must be the default. Q1 - Is 200000000 the default upon installation, if so why so high ? Q2 - Why do global settings override local settings, isn't that the wrong way around ? I've set the Global Share Settings - Cache Settings - Min. free space: 100MB Now fixed.
  4. Heres the Zip unnap-diagnostics-20200317-0126.zip
  5. Ive got the same issue, but with a 120G SSD cache. Checked all the share settings Ok. Cache disk has the appdata and system folders. the Domain and ISOs shares are not used as the box cant run VMs. The only share is "Backup" . Writing files to the Backup share never uses cache! Share is set to High-water, 1MB min, Cache: Yes. What should I look for to troubleshoot this?
  6. So, It just keeps getting worse. I installed the replacement drive, and booted up the unraid box. Now unraid has unassigned EVERYTHING! Parity, Cache all Disks, even the off-array disks! All assignments lost, I'm sure that shouldnt happen!
  7. !!! This whole process is ambiguous, illogical, there's got to be a better way! Well unraid decided the disk was not healthy, hence all this trouble ! The documentation on this is is poor to say the least. I have limited time to waste on this! I appreciate the help, thanks Just ordered a replacement disc, and now discover its pointless.. faarrrk!
  8. Actually, I thought I'd formatted it, but somehow it didnt do it, the data is still there. Just not sure if its all there. So I recon its still rebuild-able, worth trying. Speed wont be an issue. Does it need to copy to a unassigned disk or can it be copied to the array? Im guessing the former, if so that means buying a new disk anyway, so might as well replace rather than remove Disk1
  9. You've misunderstood what I am saying. One purpose of having Parity "Content Emulation" is to recover from Disk failure. The failed disk is a "small" 4TB disk, so I dont want to replace it, just convert the Emulated Content of the removed disk back to Real content , placed instead on the remaining disks. Can this not be done?
  10. Damit this is confusing.! Ive follows the Doc'c procedure for "Remove a disk", Removed Faulty Disk 1, Preserved the Parity and Cache assignments. Reassigned Disk 2, 3 as per previous assignment. Leaving out Disk 1 I'm now presented with a warning for Parity Disk: "All existing data on this device will be OVERWRITTEN when array is Started" Which means the Parity will Be recreated for Disk2 & 3 data, the exact opposite of what I need! What the! This process is supposed to preserve Content, not overwrite it! What do I do to rebuild the array from current emulated content ?
  11. @itimpi Thanks for the detailed explanation. That's clear now, unfortunately I thought a disabled disk was treated differntly. Will replace the drive, rebuild and the recover data outside of the array. The key factor here is that the content of the ‘emulated’ drive is really still "linked" to the physical drive even if disabled. ie A disabled drive is still part of the array. Format a disabled drive and you effect the array content likewise. I think it would be useful for the unraid GUI to offer a tool to make the process of removing and/or replacing a drive simplified and streamlined, as someone that will only log on to unraid when there is an issue, the current processes and doc's are a bit ambiguous, one tends to forget how it all works. Cheers
  12. So according to the Doc's, 1. I need to follow the "Remove a drive" procedure (instructions are a bit non-explicit) - Remove (physically?) the drive . - Reset the array configuration - What to set for Preserve current assignments: All? 2. Try to recover content from disk 1, if its lost.
  13. Thanks. Well only half of that make logical sense to me. To my logic, if unraid disables a drive then it should be assumed as not part of the array, thus formatting a disabled drive should Not remove any content being emulated! Logically, a parity update after disabling a disk should convert emulated content to real! Not just dump emulated content associated with the disabled disk. Otherwise whats the point of having parity ?! Anyway, The drive is still showing as "Device is disabled, contents emulated" so data may not be lost. How to re-build the array to real content from emuated content? ie exercise the redundancy protection function , recreating the content on the enabled drives .
  14. Thanks. Where are you seeing errors on disk2? I assumed that "contents emulated" meant the data had been shifted to other drives , before unraid disabled the drive, is that not the case? If not what does "contents emulated" mean then? Parity check completed without Disk1 active in the array, I assumed formatting Disk1 should not lose data from the array, am I wrong?
  15. Having similar issue . Disk 1 "Device is disabled, contents emulated" Error: UDMA CRC error count So have done : 0. Replaced PSU with 650W unit that has SATA power connectors, 3 drives/power cable , 1. Formatted Disk 1 2. xfs_repair status now reports no faults. 3. Smart Check: Completed without error 4. Reboot, start array. However, the Disk1 is still showing as Disabled. How to enable it?