krisha

Regarding the cache replacement procedure as described here in the FAQ: I had problems with the mover moving some symbolic links of docker data, due to: - wrong permissions. This was solved using 'New permissions' on just the cache drive - symbolic links to content in docker. Those were never moved. I finally used the plugin 'CA Backup / Restore Appdata' to backup and restore the docker data. The procedure mentioned in the FAQ I followed any way (Backup before moving, restore after moving back), but think this is not really necessary. Maybe it's possible to extend the FAQ post by those 2 hints.

yes a bug tracker would be a nice thing - I found so many ideas and some bugs, but it's hard to follow and you never know if Tom will ever read it. There's a lot of stuff spread on forum. I think there might be also people helping maintaining the system, removing duplicates etc. It would be also nice to let the community vote about stuff on any feature/bug list. E.g. a driver rework for faster writes :-)

I'm copying some files to my new unraid, in generally this is 200 GB splitted into ~500k files. At startup it was copying mostly small files, with a rate of ~30 MB/s (which is slow already but acceptable). After some hours it dropped to less than 8 MB/s. Currently it's transfering files in the size of 500 MB - which do not need much seek. The harddisk can be written with ~100 MB/s, Ethernet connection (Realtek 811E) is 1 GBit/s. The drive leds of origin (desktop PC) and unRaid blinks in an interval of ~2 seconds. Why is this? Also on 'top' I see that 3,9 GB of RAM out of 4 GB is used. CPU is idle at around 80%. Could it be that there is a memory leak? Attached a picture of 'top' sorted by memory :-)

Hm ok, so it's kind of protection. But should be changed, maybe replace the endless waiting with an output "Currently clearing disks, estimated finished in xx min. Do NOT power off.". New users might think that the system is stuck and just force a reboot.

the last times I shutdown by power press there was no parity check after rebooting. Using the power button the PC beeps twice and then after some seconds it is powered off. Can't be that after an parity sync/rebuild the next time it will do a parity check?

I'm running beta14 :-) Where to post features? The annoucement thread has 23 pages, I would recommend something like a bugtracker. PS: Very nice support in the forum. Thanks!

Hope this is the right thread. Two bugs (posted also on seperate threads): 1) On clearing a new disk the webGUI is not available 2) I saw on local screen "run_cmd.... share_size" as login, probably after setting include disks to "disk1 disk2" or after clearing and formatting finished.

I had this issue also twice. webGUI was just showing 'powering of system...'. Log in locally and force a shutdown with "shutdown -h now" Parity check did not occur for me. PS: I have completly different hardware, but I used the physical power button w/o stopping the array first.

I did not choose my words wisely. Your preclear script I used once and like it very much. Will use this from now on for all new disks. In this case (last post) I let unRAID clear the disk. Offtopic: What is the best way to report bugs/issues and features? webGUI not responding during the time of clearing is a bug. I want to help to improve this product (also bought two Pro licenses some days ago ).

I saw a "run_cmd: ... share_size" on the login name. Not sure if it should be there ;-) Just added a new disk, trying that the existing shares will use all new disks I wrote "disk1 disk2 disk3" on the include. probably this was wrong. Actually you need to repower and after the new size is shown correct.

Old topic I know, but beta 14 has same problem. I add a new disk and the GUI hangs till finished (in preclearing step). And I also think it was written, that the array is useable during preclear - I did not try that. so don't know if it is working

just to complete information here: I replaced my parity drive. The next boot after parity sync it automatically started a parity check. And after parity check is complete, the timestamp for the check looks updated.

As i understood the regular way to replace a (good) drive is to remove it from the controller and let unRAID rebuild it. But if something happens to the array during this time, what will happen? Can I just connect the old drive again and it will work? I saw around 8-9 writes to the data drives during a parity sync. Best way probably is to just clone the drive before. Is this supported? What happens if the drive is larger in size? I'm currently replacing the parity and I take the risk. But maybe it would be nice feature to implement.

Is there a way to read out the vars over the webGUI (http://tower/Utils/Vars) without any HTML header? Best would be XML, but I would be also satisfied with the output there. What can be the content of the variable [status]?

maybe ;-) For sure shut down when it was not complete.