glennv

I have no awnser for you unfortunately, but why do you want to switch out of curiocity ? See a lot mentioned lately but what is the exact benefit you are looking for when moving to opencore. I am more of a , if it works stable dont change it, kind of guy when it relates to hackintosh. But am very curious by all the rumours lately.

Yeah i am with you. The only thing you could theoreticaly do is use some hardware raid under a normal xfs cache for redundancy, but its not realy the most ellegant way and has its own issues . Guess we better stick with btrfs for now and wait it out untill zfs comes there. Eventualy it will have to.

Nope zfs is only for unassigned devices. Dont mess with the cache !! Cache is part of the array. Keep that btrfs if you want a fault tollerant option either raid1 or if more drives raid10. It was on my wishlist (1st sentence)

With copy on write filesystems and readonly snapshot its pretty hard for ransomewhare to affect old snapshots. As even deleing all data curently accessible stil follows the copy on write rules, not actualy deleting your old data. But it is possible for sure when your host is fully compromised with root access.But to be totaly safe you can do what i do and have a second mostly isolated system that "exposes/shares NO data via any sharing protocol" smb/nfs/etc) and "pulls" snapshots(deltas via zfs/btrfs send recieve over secure ssh connection) from the primary every night for example. Dont mistakenly "push" data to it from primary as that means if your primary is compromised a hacker or hacker software has access to stored credetials that you use on that primary to acess the backup host and will just use those to jump to it.

As snapshots are already possible with btrfs and zfs (if using the plugin and as i do since a while with just scrips and commandline incl send recieve to remote unraid box and works great), i vote for zfs support on cache and array. It would unlock more supported and rock solid zfs raid features on the cache then the current limited (stable) options on btrfs and finaly would allow zfs features for the array itself. btrfs is nice and all and i dabled with it for a while , but after the 3rd unrecoverable corruption issue i moved to unaasigned devices and zfs plugin for all docker,appdata,vms etc and never looked back since nor ever had an issue anymore. Lastly and maybe the most important of all, zfs is extremely user friendly and btrfs is not. Specialy when stuff goes wrong. Then is "the" moment where you need simplicity and not complexity. Anyone who had to deal with cache corruption issues on btrfs by now will now this. Typicaly in most cases its sorry just rebuild the cache. You have to almost nuke zfs from orbit to get to that point while a simple cable connection hickup or bad shutdown on a raided btrfs is easily busting you up. Did dozens of distructive tests and would not trust my critical data to btrfs anymore. Unfortunately for multi ssd cache its my only option currently. Multiple cache pools is a close second.

I put a small noctua blowing on the dual 10g in my supermicro so it stay at between 45-50C during load. They can get crazy hot fast and even shutdown when too hot. Upwards from 70's is pretty toasty. Not sura at what temp i saw it shutdown.

Ah, did not realise that. Never learned how to do SSDT patching as never needed it. Had issue with a passedthru USB3 devices only working at USB2 speed . Did lots of things and it started working when i just dropped this kext in the mix. So never looked back . May revisit this at some point but hackintosh lessons from the past say, if it works, dont touch it

ah cool. tnx. I am already using the usbinjectall so guess i dont need that. Was just curious.

Just out of curiosity while reading along here. What is the function/purpose of the USBPower kext ? Is it generaly recommended or only applicable for specific situations/setups

if killing the specific docker still did not clear the iowait situation then its not as simple to find the culprit. check this for some ideas how to approach it https://bencane.com/2012/08/06/troubleshooting-high-io-wait-in-linux/ The required commands/tools for deeper troubleshooting you can install using the nerdtools plugin. Like iotop for example, which is in there and which may be usefull. Its not a simple problem that can easily be identified remote. edit: iostat is part of the sysstat package of nerdtools

did you try killing them like normal linux processes with kill pid or kill -9 pid. ? If they wont die with this , its difficult as likely completely hanging. You can see this effect also when a process is hanging on an hard nfs mount that is not there anymore. Typicaly only a reboot can kill these sessions. You dont happen to have any mounted external shares that they can be hanging on ?

yes Cpu usage is always split in user/system/wait/idle . Together its ~100% (ignoring the other smaller indicators) Meaning its x% of the time either serving the user, bussy with internal system activities, waiting for something , or idle doing nothing.

Although you mistakenly may think that top shows no activity, check the cpu wait . Its at around 50% indicating cpu is waiting on something (typicaly i/o). So its in line with what the gui is showing namely about 50% load (2 of the 4 cores are in wait state)

Tnx, yeah that second question was not specific to this docker (just played with this docker for fun to see if it behaves different to my exsiting OSX VM's). Will try and play with it by just changing the bios rez. Already had just created 2 identical VM tempates pointing to the same vdisks etc, one with VNC and one with GPU so i can play and experiment without every time having to boot the server. edit: just changed only the bios to 2560x1440p and it worked. Not sure what i did wrong the last time. Tnx

@SpaceInvaderOne Not sure if i read over it somewhere , but what exactly is custom about the 2 ovmf files ? Is it just the unraid 3.1 version but with preset screen resolution or is there more modified ? Second (not specific to this docker), when i use vnc the 1920x1080 works fine and i see all boot logs ungarbled , but when i replace it with my vega 56 , its all garbled after the initial clover boot disk selection part. Tried changing the resolution on clover side and bios side to 2560x1440, but cant seem to get it to work so i can read the debug logs. Is there a limit in the bios to only be able to use 1920x1080 during boot or can it also work in a different resolution with connected monitor/gpu. (due to the reset bug its not easy to just test all combination as have to reboot the whole server everytime, but a few tries failed so before i spend 5 days trying all combos i thought i would ask how you do it) Tnx again for the cool docker.

Dont forget thats a (small) performance loss vs a huuuuuuuuge gain of flexibility and features. I host them now on ssds in a zfs pool using the great zfs plugin and make daily plus on demand snapshots plus remote send / recieve to second unraid for incremental backups from the vdisks. And clones for all kinds of test that use virtualy zero extra storage space. So with the flick of a finger i can get a broken vm back to working state. Its such a freedom to not worrie about braking your vm or clover partition with experimenting or upgrades. You loose all this when passing the whole device to your vm. So keep that in mind when planning your setup. Btw its easy oneliner to convert between physical drive and virtual using the inbuild qemu commands . I started physical passthru and migrated all to virtual eventualy.

If its a sector allignement issue on certain ssds as suggested in this post , how can that be fixed then in the rc's ?

@kron Did you ever figure this out for your supermicro ?

same here . also had trim problems with my samsung 960's btrfs but after reading on this forum about the issues and solution i replaced my lsi card with a 9300-8i model all trim issues solved. The motherboard satas where all used already but that would have been an alternative solution.

this last f up regarding exluding certain customer data type, the move from me paying 10 per month to suddenly 50 ( 5 servers) the crazy slow speed (even with all tricks) and the final straw when i lost 6tb of uploaded data from a share that moved to a different server and i used the nice feature to take over uploaded data from another server which wiped all the uoloaded data from the existing server instead of adding it to it, made me move to backblaze b2 instead of waiting for months for a new upload. Billion times faster as they recently opened a new dc next door and i pay roughly the same adding it all up. Also feels like i have way more control over my data instead of some black box with crashplan on the other side. Use my old faithfull syncovery to do all the backups to b2 now. One more week to go and all my uploads are already finished (crazy fast) and will trash the last crashplan node after 6 years with them. Time to move on......

very nice gesture bro ✌️✌️✌️✌️✌️✌️✌️

ps no need to stop the array dor any zfs stuff. Typicaly i wipe the drives first with a dummy unassigned devices format if they protest when trying to create a pool. Could be some remnants of earlier use on them that gets you that message. But stopping the pool is not needed as not part of the pool. Be very carfull however to select the right drive ids as to not accidentaly destroy the unraid array drives.

Nope , unassigned devices is not involved in zfs other then like any other non array drive its show the drives there. Drives involved in zfs pools do show up as zfs_member in unassigned devices but dont touch them there or use mount button. Its all commandline baby ✌️

1. Yes you can have multiple zpools. 2. Not sure about the self healing of single drive zpools, but i use them (large spindle) for snapshot send / recieve targets . 3. regarding tips. - auto mounting on a specific set mountpoint does not work for me on reboot (while mountpoint is properly set on datasets) so i created a user scripts to start after reboot to export/import on the target mountpoint. - for appdata to work properly you need to mount your datasets under /mnt. i use /mnt/disks/appdata for example. - for trimming i run nightly zpool trim commands using user scripts plugin. - i heavily use zfs snapshot , send /recieve etc triggered by user scipt plugin , rollbacks , cloning etc and all working great. - use the user scripts plugin to limit arc after boot as described in the beginning of this topic. - read this whole topic and check the usefull tips for monitoring and sending notifications on zfs events or used in you own snapshot scripts etc. - do not upgrade unraid unless a new zfs plugin version has become available (ouch)