coolspot

Hi All, I was testing my unRAID system this afternoon and one of my data drives went offline due to a read error. My data drive and parity drive is 2TB. I have 4TB replacement drives on hand. I obviously can't just replace the data drive with the 4TB since my parity drive is smaller. Do I upgrade my parity drive first, resync, then replace the failed data drive? Thanks.

I have two SSD, a Samsung EVO 840 250GB and Samsung EVO 840 500GB. Even if I wanted to get 2x500GB SSDs, it would be hard to find a matching EVO 840. I would have assumed, since unRAID is doing software mirroring, that it would have created the cache partition size based on the smallest drive size (250GB in this case).

Thank you for the clarification, will unRAID properly detect the file system as getting full and switch over to the array or will it get confused because of the wrong size reported? Thanks.

Hello Everyone, When I first configured unRAID a few days ago I used a 250GB SSD as my cache drive. I pulled a 500GB SSD today and installed it into my unRAID server as a secondary cache drive. I was expecting unRAID to report that I have 250GB of cache space (RAID 1/smallest drive size?) but instead, unRAID reports 375GB which seems to be the mid-point between 250GB and 500GB. How is unRAID providing redundancy larger than the smallest drive? Does BTRFS redundancy work differently and is more efficient than RAID 1? Thanks.

That's something I'd like to know too. I suppose since this is Linux, you are expected to unmount the file system yourself, before detaching. And probably Linux GUI's (KDE, etc) provide a button or function that will execute the appropriate unmounts, comparable to 'safely remove'. I think stop array is pretty much the equivalent of "safely remove" for assigned devices.

Hot-swap works with unRAID - I was able to pop new drives into the free slots in unRAID and it was detected by the system. This worked fine with my Intel H61M SATA Ports, AsMedia ASM-1061 onboard controller, and a HighPoint RocketRaid 2720SGL (Marvel 88SE9840). If using SATA ports, you have to set them to ACHI mode in your bios for hot-swap to work properly. As for pulling assigned devices and hot-swapping them, I don't think that is supported by unRAID.

The reason for the seemingly quick rescan time is so that it won't have to spin up the drives. Cache-dirs attempts to keep the directory structures in memory by rescanning all the time. (Linux if the directory structure isn't used in a while will automatically drop it from memory) Ah - so it's primarily a memory scan to keep the data in RAM and prevent a flush. If the data is flushed, cache_dir will then do a physical scan and reload the data. Thanks for the clarification, I was wondering how it worked.

Hi all, What does the Minimum interval between folder scans (sec) and Maximum interval between folder scans (sec) do? Does cache_dir physically scan based on these parameters? So will it spin up the drives every 10 seconds (default maximum interval) to search directories for new entries? Thanks.

Hello Everyone, I just started building an unRAID server and it's going pretty well. I installed a cache drive and started to copy my data from a Synology NAS over to unRAID. However, after a few hundred GBs, I realized I it's probably best to disable the cache temporary to preserve the endurance of the drive during my initial migration. However, the cache file had 150GBs of files that were not transferred by mover yet. If a share has "Cache Drive" set to No, it seems Mover ignores the folder and leaves files on the SSD? Shouldn't mover clear out the cache contents if a folder has been set to No? So in short, mover only processes a folder if Cache Drive is set to Yes/Prefer/etc.? Thanks.

Was yours a Rocket or RocketRaid 2720SGL? Both cards I think have the same model # but one is a RAID controller and the other a HBA. Thanks.