BC2112

Just about ready to give up on CloudBerry. Works fine uploading to Backblaze but I cannot restore. I would like restores to go to a read/write share called Restores. But all I get are errors stating that "Error on process some files". I would really like to be able to specify that restores go to a specific place. I have the share set up but the errors appear. Any step-by-step advice? BTW /mnt/user for the storage in the docker settings has been set to read/write. Thanks.

I noticed that the pop-up explanation in the Cache settings tab on minimum free space states: This defines a "floor" for the amount of free space remaining in the volume. If the free space becomes less than this value, then new files written via user shares will fail with "not enough space" error. I had thought that if this was set to, say, 80GB that if the cache had less than 80GB it would simple write to the array instead as opposed to cache first then Mover later. Does the copy of file really fail (i.e., nothing is written to the array) or is this just bad wording on the pop-up? thanks

Hello, I seen some here use the following SATA expansion card successfully (IO Crest Internal 5 Port Non-Raid Sata III 6GB/S PCI-E X4 Controller Card for Desktop PC Support SSD and HDD with Low Profile Bracket. JMB585 Chipset): https://www.amazon.ca/dp/B07ST9CPND/?coliid=IZCGYOR098LC9&colid=2B5NIDRTU9KBI&psc=1&ref_=lv_ov_lig_dp_it My question is, are there any issues with using such simpler devices and not a dedicated HBA like a LSI 6Gbps SAS HBA LSI 9211-8i (=9201-8i) P20 IT Mode I'm just a home user so I am not sure I need something like an HBA card or not. Thanks in advance!

I have intermittent disk errors that seem to pop up every so often. They are of the type: Oct 15 03:41:49 UNRAID-1-BAK kernel: ata2.00: exception Emask 0x0 SAct 0x3c3800 SErr 0x0 action 0x0 Oct 15 03:41:49 UNRAID-1-BAK kernel: ata2.00: error: { UNC } Oct 15 03:42:40 UNRAID-1-BAK kernel: blk_update_request: I/O error, dev sdc, sector 1095829232 op 0x0:(READ) flags 0x0 phys_seg 168 prio class 0 Oct 15 03:42:40 UNRAID-1-BAK kernel: md: disk0 read error, sector=1095829168 Oct 15 03:42:40 UNRAID-1-BAK kernel: md: disk0 read error, sector=1095829176 Oct 15 03:42:40 UNRAID-1-BAK kernel: md: disk0 read error, sector=1095829184 Parity checks have no errors and three extended SMART tests are good. Both show 0 reallocated sector count and 0 current sector pending. Seek error is 1. Drive is WD Red 6TB (parity disk). Given the tests, can I assume that these errors are cables? Errors showed up on Oct 4, 9, and 15 only. Thanks

thanks!

I cannot seem to remember (duh) what the drive numbers mean and I cannot find them in the GUI. I have a read error on disk0 from the log: Oct 25 03:42:40 UNRAID-1-BAK kernel: md: disk0 read error, sector=1095830176 Oct 25 03:42:40 UNRAID-1-BAK kernel: md: disk0 read error, sector=1095830184 what is disk 0 and how does one identify this number with a drive in the GUI. I should know this but am drawing a blank! I'm assuming it is parity.