NewDisplayName

So i posted a thread about not getting a notice today when my power in town went off (bc of storm). Bc my unraid and network was online thru USP, but my isp network not. So notifications cvouldnt be sent... my suggestion is to resent the notifications when network is reachable again AND also after a reboot... atleast the ALERT or ERROR notifications... bc, if this isnt handled, your server could theoreticle crash every day and you dont notice it.

I dont get it, how can i be the only one with this problem? Jan 18 18:59:54 Unraid-Server shfs: error: shfs_rmdir, 1517: Directory not empty (39): rmdir: /mnt/cache/Kamera/Kinderzimmer/2018-01-18 Jan 18 19:04:54 Unraid-Server shfs: error: shfs_rmdir, 1517: Directory not empty (39): rmdir: /mnt/cache/Kamera/Kinderzimmer/2018-01-16 Jan 18 19:04:54 Unraid-Server shfs: error: shfs_rmdir, 1517: Directory not empty (39): rmdir: /mnt/cache/Kamera/Kinderzimmer/2018-01-17 Jan 18 19:04:54 Unraid-Server shfs: error: shfs_rmdir, 1517: Directory not empty (39): rmdir: /mnt/cache/Kamera/Kinderzimmer/2018-01-18 Jan 18 19:09:54 Unraid-Server shfs: error: shfs_rmdir, 1517: Directory not empty (39): rmdir: /mnt/cache/Kamera/Kinderzimmer/2018-01-16 Jan 18 19:09:54 Unraid-Server shfs: error: shfs_rmdir, 1517: Directory not empty (39): rmdir: /mnt/cache/Kamera/Kinderzimmer/2018-01-17 Jan 18 19:09:54 Unraid-Server shfs: error: shfs_rmdir, 1517: Directory not empty (39): rmdir: /mnt/cache/Kamera/Kinderzimmer/2018-01-18 Jan 18 19:14:54 Unraid-Server shfs: error: shfs_rmdir, 1517: Directory not empty (39): rmdir: /mnt/cache/Kamera/Kinderzimmer/2018-01-16 Jan 18 19:14:54 Unraid-Server shfs: error: shfs_rmdir, 1517: Directory not empty (39): rmdir: /mnt/cache/Kamera/Kinderzimmer/2018-01-17 Jan 18 19:14:54 Unraid-Server shfs: error: shfs_rmdir, 1517: Directory not empty (39): rmdir: /mnt/cache/Kamera/Kinderzimmer/2018-01-18 Jan 18 19:15:10 Unraid-Server kernel: vethd061a06: renamed from eth0 Jan 18 19:15:10 Unraid-Server kernel: docker0: port 10(vethf8e64c2) entered disabled state Jan 18 19:15:10 Unraid-Server kernel: docker0: port 10(vethf8e64c2) entered disabled state Jan 18 19:15:10 Unraid-Server avahi-daemon[3714]: Interface vethf8e64c2.IPv6 no longer relevant for mDNS. Jan 18 19:15:10 Unraid-Server avahi-daemon[3714]: Leaving mDNS multicast group on interface vethf8e64c2.IPv6 with address fe80::c4d6:8cff:fe01:ba2d. Jan 18 19:15:10 Unraid-Server kernel: device vethf8e64c2 left promiscuous mode Jan 18 19:15:10 Unraid-Server kernel: docker0: port 10(vethf8e64c2) entered disabled state Jan 18 19:15:10 Unraid-Server avahi-daemon[3714]: Withdrawing address record for fe80::c4d6:8cff:fe01:ba2d on vethf8e64c2. (after stopping xeoma, the problem dissapeared) Xeoma is set to delete after 1 week and or 100 gb, both is not true.

Thanks for the docker, now i have another problem Jan 14 02:02:04 Unraid-Server shfs: error: shfs_rmdir, 1517: Directory not empty (39): rmdir: /mnt/disk4/Kamera/somedir/2018-01-12 Jan 14 02:02:04 Unraid-Server shfs: error: shfs_rmdir, 1517: Directory not empty (39): rmdir: /mnt/cache/Kamera/somedir/2018-01-13 Jan 14 02:07:04 Unraid-Server shfs: error: shfs_rmdir, 1517: Directory not empty (39): rmdir: /mnt/disk4/Kamera/somedir/2018-01-12 Jan 14 02:07:04 Unraid-Server shfs: error: shfs_rmdir, 1517: Directory not empty (39): rmdir: /mnt/cache/Kamera/somedir/2018-01-13 Jan 14 02:12:04 Unraid-Server shfs: error: shfs_rmdir, 1517: Directory not empty (39): rmdir: /mnt/disk4/Kamera/somedir/2018-01-12 Jan 14 02:12:04 Unraid-Server shfs: error: shfs_rmdir, 1517: Directory not empty (39): rmdir: /mnt/cache/Kamera/somedir/2018-01-13 Jan 14 02:17:04 Unraid-Server shfs: error: shfs_rmdir, 1517: Directory not empty (39): rmdir: /mnt/disk4/Kamera/somedir/2018-01-12 Jan 14 02:17:04 Unraid-Server shfs: error: shfs_rmdir, 1517: Directory not empty (39): rmdir: /mnt/cache/Kamera/somedir/2018-01-13 Jan 14 02:22:04 Unraid-Server shfs: error: shfs_rmdir, 1517: Directory not empty (39): rmdir: /mnt/disk4/Kamera/somedir/2018-01-12 Jan 14 02:22:04 Unraid-Server shfs: error: shfs_rmdir, 1517: Directory not empty (39): rmdir: /mnt/cache/Kamera/somedir/2018-01-13 server log is full of this, app log doesnt show anything... i created a share for this app /Kamera/ with cache setting "Yes"

U can set the default spin down time, but if im right its 15min with 6.4 I have set it to 15, but most i do anyway on the cache drives, so it really just needs to spin up for mover or if i play a movie (and then it wont spin down anyway) Just btw, i dont think its good if you post to 8 year old threads... bc this information here is very outdated.. it also depends on your energy bill, i have high energy cost here, so i try to save as many watt as possible.

I cant say, it was in the first minutes i used unraid bc i didnt understand how the structure worked...

The simplest and easiest and fastest way probably is to start new i would follow the guides this guy makes

yeah, again you need to specify the .img

Dont know, i did it, without problems, is this still a thing in 6.4?

As far as i know all dockers are stored inside the docker.img, so all you need to backup and replace is this file. How i added the cache: - stopped server - added ssd - startet server - looked at "MAIN" - there was option to let parity run (or unraid asked me to do so, cant remember) i did - took ~7 h - then i could tick "format?" - clicked start, after some minutes it was finished and all was working... - the whole time all dockers plugins was running, without problems. But i guess all problems startet becase you didnt understand the file structure of unraid. You should put all things in /mnt/user/<name>/ e.g. i have it like this /mnt/user/Archiv (added share with name Archiv) there i have simply created normal directory via SMB /mnt/user/Archiv/Movies /mnt/user/Archiv/Games u get the idea... All dirs in /mnt/user/here u should create via add share Via "use cache disk" you tell the system how to use the directory... e.g. in Archiv i set it to "Yes" = this means fast transfer speeds to the array, and one time a day it gets moved to the real HDDs. "Always" means it stays always at cache (i do it for all VMs, Images, plugins, and so on - so hdds dont need to spin up). "no" wont use cache atall. (but everything is also explainted if you click it in the UI [as i were new i didnt know that!]) For the system /mnt/cache/Archiv is the same like /mnt/user/Archiv Or /mnt/disk1/Archiv But if u put it in /mnt/cache it will stay there, if you put it in /mnt/user/here you can controll it via settings from share. If you dont understand mover, you can also manually transfer the files via "mv" in terminal. (thats how i did it after i initially didnt understand the structure, bc its nothing i ever saw before- but its brilliant!) like "mv /mnt/cache/dir /mnt/user/dir" Will move dir from cache to user directory (but before add a share with that name) But attention, dont write anything in terminal you dont understand and dont write it wrong, one command can delete everything :)) One extra tip: if you put the .imgs on the hdds, then you should delete the .img in the VM (cd drive), else the hdd spins everytime up.

So i bought hte one i said and installed it some days ago, working like a charm, but best is (i didnt know) u can now read the watt used in interface of unraid... pretty happy, gives me about 20 of downtime, which is more then i need.

Yea, that would m ake sense. I need to look at power because here in ermany power is not cheap. I pay ~0,8usd per kwh. So this make a difference. Before unraid my server took nearly 200 watt now between 60-75 if no work on hdds done.

Yo,i plugged now all ssds to the MB, power saving may seem to work, im not sure, but i guess 65 Watt is in margin of error compared to 59 without raid controller...

I just wonder whats the problem. Yesterday i added a new ssd to my cache. I let parity run, then i could tick "format" and it formatted it.

I dont think so. But johnnie might know more. (or u just try it) Worst thing could happen is all gets delted edit: okay then i also dont know, but maybe a restart can fix it?

Under "Main" Mine looks like this Parity HGST_HDN726040ALE614_K4KGBS0B - 4 TB (sdj) * 83 118 0 Disk 1 TOSHIBA_DT01ACA200_X3NGGG6GS - 2 TB (sdc) * 366 5 0 xfs 2 TB 509 GB 1.49 TB Disk 2 WDC_WD30EFRX-68EUZN0_WD-WCC4N3YNARE3 - 3 TB (sdh)

No. Thats a good idea. I guess your cache is a ssd, so much faster and lower energy consumption (bc disk spin all time if u run VM or dockers from it)

If i understand correct, you want to remove a drive and add a new? If the drive you want to add is not bigger or atleast the same size as your parity, you could just replace them and rebuild parity. or?

Like i said, crazy.

I did said NOTHIGN wrong, thats what you dont get in your brain. YOU did understand it WRONG. Not my problem. You are WRONG! w/o adjusting that setting my transfer speed was 60 MB/sec, now it is @ 110 MB/sec

Hi, im happy new owner of a fresh new 9201-16e. Currently i have one cache (ssd) on MB and one cache (ssd) on the raid controller. Now i wonder, since cache is active all time, this would also mean the controller is on all time, would it save power when i move the 2. ssd also to the MB? I mean does unraid power down the pcie if not used?

Dont know what it costs at your country. I would go with CPU i7 8700, GPU 1080 (or Ti, if budget), atleast 16gb ram (doenst really matter what, but atleast 2, same size, for dual channel), id suggest onboard GPU for unraid and the 1080 for your gaming/working VM. Atleast 1 SSD for cache (unraid)/windows boot drive 500gb (250 would probably also work, better more then too less) 850 EVO. HDDs as you need them. Dont know SFF cases, but i would check here: https://geizhals.de/?cat=gehatx easy to filter MB doesnt matter, just check what you want, as cheap as possible PSU doesnt really matter too, any 500-600 watt should be enaught, if u like energy efficience i can recommend you this: i bought it for my unraid server, dropped Watt from 112 to 65 (bc not all PSUs have good effience if they only 10-20% used)

U asked the whole world for help when posting online a question. "Then you came here trashing their suggestions" I even explained it to you. I didnt trashed their suggestions, i jsut want to tell you that it has nothing to do with disks spinning up - which is correct - so you dont waste energy. I called you crazy because how you treat someone who trys to help you. Just because you dont understand it, it doesnt mean its wrong. But be sure, i wont help again.

Yeah, thats what i mean, its surprisingly fast on old machines, i just did like i said a test with windows 10 ulti and a unraid vm servert with cheap 100 year old celeron... worked like a charm. Designs you can get everywhere. If i need fast, i just disable all optical things.

If he wants to make it look like windows 7, he can do it with it