Harrywong
-
Posts
23 -
Joined
-
Last visited
Content Type
Profiles
Forums
Downloads
Store
Gallery
Bug Reports
Documentation
Landing
Posts posted by Harrywong
-
-
8 hours ago, johnnie.black said:
du is unreliable with btrfs, value on the GUI will be correct, you can also get more detailed info with:
btrfs fi usage -T /mnt/cacheThanks! Do you know why there are 94.76GiB / 93.76GiB unallocated, and how to allocate them?
Overall:
Device size: 931.52GiB
Device allocated: 743.00GiB
Device unallocated: 188.52GiB
Device missing: 0.00B
Used: 655.24GiB
Free (estimated): 137.68GiB (min: 137.68GiB)
Data ratio: 2.00
Metadata ratio: 1.00
Global reserve: 33.61MiB (used: 0.00B)Data Metadata System
Id Path RAID1 single single Unallocated
-- -------------- --------- -------- -------- -----------
2 /dev/nvme0n1p1 371.00GiB - - 94.76GiB
1 /dev/nvme2n1p1 371.00GiB 1.00GiB 4.00MiB 93.76GiB
-- -------------- --------- -------- -------- -----------
Total 371.00GiB 1.00GiB 4.00MiB 188.52GiB
Used 327.58GiB 77.39MiB 80.00KiB -
Hi Unraid community,
The cache pool used size seems to be wrong.
du -h /mnt/cache/ shows 259G used. However, web UI shows 352G used.
My configuration is 2 500G nvme SSD btrfs RAID1.
One thing might be related is I removed the docker vDisk, if I remember correctly, the default docker vDisk is 100G? Which almost aligns with the size difference.
Any ideas?
Thanks!
-
On 8/2/2019 at 1:52 PM, jwblant said:
I've followed @SpaceInvaderOne's video guide for both High Sierra and Mojave VM's and have gotten everything pretty much working, including the GPU pass through. The thing I can't figure out is that FCPX and Compressor are STRUGGLING during render/exports. In fact, my 2012 MacBook Pro with NVIDIA GT650M is almost TWICE as fast as the VM's. Does anyone have any ideas on how to speed this up?
I've tried geekbench and I'm scoring about 150K, which is similar to my bare metal windows score. I just can't get my video editing software to use it properly, which is literally the only reason I'm messing with it at all! lol
Try this post:
Notice the screenshot in the post: H264 and HEVC acceleration is ON.
-
On 5/14/2018 at 5:08 AM, ars92 said:
ASRock x399 taichi
RAM is that trident z RGB made for threadripper (can’t remember the name ) Wish they had made a non rgb one as my case is fully closed. I can confirm this ram is able to get to 3200 with the flick of the XMP switch
Thought you should know that as Zen is RAM sensitive in both enabling XMP and its own performance.
Sent from my iPhone using Tapatalk
Does 8 x 8GB flare 3200 works at 3200 for you? 4 x 8GB worked for me. I have to change to 3000 for 8 x 8GB to be able to boot into unraid.
-
Hi Leoyzen,
Could you help elaborate what you did to make videoproc showing GPU has hardware acceleration for Mojave?
Is it because the SIMBIOS that you are using, or the patches, or the fact that you are not using any kexts?
Thanks!
-
9 hours ago, ghost82 said:
You fill find the files in the post you quoted above; it contains qcow2 files.
I meant EFI, sorry not familiar with qcow2. Does it contains the EFI folder? Thanks!
Could you help post a screenshot of your drivers and kexts? I think the ones we are using should be the same since we are all using QEMU.
Unfortunately using the qcow2 I got clover stuck at "scanning" error. So I thought knowing your EFI structure, especially the files in drivers folder and kexts folder would help.
-
On 9/19/2019 at 2:14 AM, ghost82 said:
I found out what was the problem with my attempts to update clover without success, I'm sharing it here, maybe it will be of some help for other people.
My problem was that clover hanged at "scan entries": thanks to Leoyzen who shared its working EFI folder I could find out that my EFI folder structure was wrong.
To update clover I always downloaded the iso image from sourceforge, made my modifications, mounted the EFI folder inside osx and copied the new updated efi folder.
Somewhere in the past the folder structure of clover changed, more into details folder CLOVER/drivers64UEFI changed into CLOVER/drivers/UEFI.
So I maintained the new folder structure inside my efi folder (CLOVER/drivers/UEFI) : the error is here, CLOVER/drivers/UEFI is not the correct structure, CLOVER/drivers64UEFI is the correct one!
The scan entries error was because no driver was loaded and clover couldn't find any hd to boot from! With the new folder structure I'm able to update clover without problems; v.5089 works for me on mojave.
Thanks again Leoyzen!
Hi, you mentioned Leoyzen shared his EFI folder. I wanted to take a look as well. I wonder where is the post, since I could not find it. Thank you!
-
On 9/18/2019 at 9:02 PM, Leoyzen said:
Here U are, those files attached are my clover files for Catalina and Mojave as nearly bare metal VM, both works for VNC or Real Monitor with Graphics passthrough:
Something should notice:
* Catalina: MacPro7,1(which iMacPro1,1 not works for me it get reboot cyclely with "x86_topo_lock error")
* Mojave: iMacPro1,1
** It do not need any kext to make function work **
Both files contains OOB patch (for AMD RX560/570/580 patch to make hardware acceralation(HEVC & H264) work also to avoid black screen (make graphics in acpi gfx0 position should avoid this)) and Clover as new as possible (v5058, the latest wont boot for me).
Remember you should change SMBios UUID to avoid conflict.
Using this then you can get an OOB Hackintosh(Mojave or Catalona) works like charm.
As I explained above, you should take some patches from clover to make iMacPro1,1 work for Mojave, also MacPro7,1 for Catalina(check my clover.plist).
mojave.clover.qcow2 12.56 MB · 14 downloads catalina.clover.qcow2 22 MB · 13 downloads
Edit:
some steps to make rx560/570/580 works natively in mojave and catalina to support hevc/h264 hardware acceraltion without IGPU:
- change your SMBios to iMacPro1,1(mojave) or MacPro7,1(Catalina)
- select ACPI --> Add DTGP in clover：add some method in acpi for later use.
- select ACPI --> FixDisplay: in order to change your grahpic to gfx0
- select KernalAndDriverPathes --> Black Screen Patch Vega 56/64, RX580 etc. (c)Pike R. Alpha: fix blackscreen issues
- (Optional)If not work, then add LILU/WEG to you kexts directory.
Here are some screen shots about my VM:
Geekbench 5 with 4 cores/ 8 threads of my 3700x:
You mentioned "Both files contains OOB patch (for AMD RX560/570/580 patch to make hardware acceralation(HEVC & H264) work also to avoid black screen (make graphics in acpi gfx0 position should avoid this))". So does mojave.clover.qcow2 that you uploaded works with Vega 64? You only mentioned RX580. If not, what should I do to patch it for Vega 64?
Thank you!
-
Hi David,
I am not getting (unchanged from before updating Majave) the expected performance with Vega 64 on FCPX. Could I have some suggestions from you on the possibility to fix it?
- We are using QEMU, I am not sure if disabling iGPU would help. Threadripper does not have a iGPU, but I think without disabling it, QEMU will emulate an iGPU, which is suboptimal.
- Curious what is the clover configurator SIMBIOS configuration that you are using? I know you are using 18,3, could you share some specifics?
This is mine:
- do you know what does clover's CPU->QEMU mean? Should I select it? I could not find documentation regarding it.
Thanks!
-
What's best, after the update, I don't need to use a custom vbios for graphics card anymore. And the fan issue is resolved
-
Thanks! Update now works, and is able to shutdown correctly.
Not sure if random black screen problem went away because did not have a chance to use it for a long period of time.
What I did:
Removed kexts, the remaining kexts were the same 3 you have.
I tried to update the drivers (.efi files) to match what you have, but unfortunately after that clover can not see any boot drive, which is strange.
So I am keeping my old drivers, unupdated.
Thanks!
-
21 minutes ago, david279 said:
These are the only kext i use on my Mojave and Catalina VMs
Thanks. I am backing up my image and then will try changing the kexts to match yours. Since we are all using qemu, I think the required kexts will be similar.
Do you add additional arguments to clover? I am not familiar with clover, but I vaguely remember that arguments can be passed to Lilu / WhateverGreen.
Btw, do you use APFS for your MacOS?
-
12 minutes ago, david279 said:
what kext are you using?
Thanks, here are the kexts:
-
Dear unraid community,
Does anyone have the similar problem?
- can't reboot / shutdown: goes to black screen when rebooting from MacOS, or from unraid web UI. I have to force stop the VM from unraid web UI.
- randomly black screen: goes to black screen randomly, around once per day of heavy use. Sometimes can't visit unraid web UI as well. <- this is the most annoying issue.
- can't update OS: when updating by clicking the prompt in MacOS does not work, after reboot (reboot into black screen and force stop VM and start VM), MacOS says it can't update. Anyone has the experience of successfully updating?
I use MacOS very frequently, so any tip will be very helpful. Thank you!
My setup: Threadripper 1950x, Vega 64. I have to use custom GPU vbios, without it the fan is very loud, but with the custom vbois, the fan never runs - that's why I want to update Mojave, the lasted version solves the fan issue.
Here is my config:
<?xml version='1.0' encoding='UTF-8'?> <domain type='kvm' id='2' xmlns:qemu='http://libvirt.org/schemas/domain/qemu/1.0'> <name>OSX</name> <uuid>ffe0f7c5-6016-1ff2-80a0-66fc0e550ff8</uuid> <metadata> <vmtemplate xmlns="unraid" name="OpenSUSE" icon="opensuse.png" os="opensuse"/> </metadata> <memory unit='KiB'>60817408</memory> <currentMemory unit='KiB'>60817408</currentMemory> <memoryBacking> <nosharepages/> </memoryBacking> <vcpu placement='static'>32</vcpu> <cputune> <vcpupin vcpu='0' cpuset='0'/> <vcpupin vcpu='1' cpuset='16'/> <vcpupin vcpu='2' cpuset='1'/> <vcpupin vcpu='3' cpuset='17'/> <vcpupin vcpu='4' cpuset='2'/> <vcpupin vcpu='5' cpuset='18'/> <vcpupin vcpu='6' cpuset='3'/> <vcpupin vcpu='7' cpuset='19'/> <vcpupin vcpu='8' cpuset='4'/> <vcpupin vcpu='9' cpuset='20'/> <vcpupin vcpu='10' cpuset='5'/> <vcpupin vcpu='11' cpuset='21'/> <vcpupin vcpu='12' cpuset='6'/> <vcpupin vcpu='13' cpuset='22'/> <vcpupin vcpu='14' cpuset='7'/> <vcpupin vcpu='15' cpuset='23'/> <vcpupin vcpu='16' cpuset='8'/> <vcpupin vcpu='17' cpuset='24'/> <vcpupin vcpu='18' cpuset='9'/> <vcpupin vcpu='19' cpuset='25'/> <vcpupin vcpu='20' cpuset='10'/> <vcpupin vcpu='21' cpuset='26'/> <vcpupin vcpu='22' cpuset='11'/> <vcpupin vcpu='23' cpuset='27'/> <vcpupin vcpu='24' cpuset='12'/> <vcpupin vcpu='25' cpuset='28'/> <vcpupin vcpu='26' cpuset='13'/> <vcpupin vcpu='27' cpuset='29'/> <vcpupin vcpu='28' cpuset='14'/> <vcpupin vcpu='29' cpuset='30'/> <vcpupin vcpu='30' cpuset='15'/> <vcpupin vcpu='31' cpuset='31'/> </cputune> <resource> <partition>/machine</partition> </resource> <os> <type arch='x86_64' machine='pc-q35-3.1'>hvm</type> <loader readonly='yes' type='pflash'>/usr/share/qemu/ovmf-x64/OVMF_CODE-pure-efi.fd</loader> <nvram>/etc/libvirt/qemu/nvram/ffe0f7c5-6016-1ff2-80a0-66fc0e550ff8_VARS-pure-efi.fd</nvram> </os> <features> <acpi/> <apic/> </features> <cpu mode='custom' match='exact' check='full'> <model fallback='forbid'>EPYC-IBPB</model> <vendor>AMD</vendor> <topology sockets='1' cores='32' threads='1'/> <feature policy='require' name='x2apic'/> <feature policy='disable' name='tsc-deadline'/> <feature policy='require' name='hypervisor'/> <feature policy='disable' name='tsc_adjust'/> <feature policy='require' name='cmp_legacy'/> <feature policy='require' name='perfctr_core'/> <feature policy='disable' name='virt-ssbd'/> <feature policy='disable' name='monitor'/> <feature policy='disable' name='sha-ni'/> <feature policy='disable' name='cr8legacy'/> <feature policy='require' name='topoext'/> <feature policy='require' name='invtsc'/> </cpu> <clock offset='utc'> <timer name='rtc' tickpolicy='catchup'/> <timer name='pit' tickpolicy='delay'/> <timer name='hpet' present='no'/> </clock> <on_poweroff>destroy</on_poweroff> <on_reboot>restart</on_reboot> <on_crash>destroy</on_crash> <devices> <emulator>/usr/local/sbin/qemu</emulator> <disk type='block' device='disk'> <driver name='qemu' type='raw' cache='writeback'/> <source dev='/dev/nvme1n1'/> <backingStore/> <target dev='hdd' bus='sata'/> <alias name='sata0-0-3'/> <address type='drive' controller='0' bus='0' target='0' unit='3'/> </disk> <disk type='file' device='disk'> <driver name='qemu' type='raw' cache='writeback'/> <source file='/mnt/user/domains/Mojave/1_17_2019_rsync.img'/> <backingStore/> <target dev='hde' bus='sata'/> <boot order='1'/> <alias name='sata0-0-2'/> <address type='drive' controller='0' bus='0' target='0' unit='2'/> </disk> <disk type='block' device='disk'> <driver name='qemu' type='raw' cache='writeback'/> <source dev='/dev/nvme0n1'/> <backingStore/> <target dev='hdg' bus='sata'/> <alias name='sata0-0-4'/> <address type='drive' controller='0' bus='0' target='0' unit='4'/> </disk> <controller type='usb' index='0' model='ich9-ehci1'> <alias name='usb'/> <address type='pci' domain='0x0000' bus='0x00' slot='0x07' function='0x7'/> </controller> <controller type='usb' index='0' model='ich9-uhci1'> <alias name='usb'/> <master startport='0'/> <address type='pci' domain='0x0000' bus='0x00' slot='0x07' function='0x0' multifunction='on'/> </controller> <controller type='usb' index='0' model='ich9-uhci2'> <alias name='usb'/> <master startport='2'/> <address type='pci' domain='0x0000' bus='0x00' slot='0x07' function='0x1'/> </controller> <controller type='usb' index='0' model='ich9-uhci3'> <alias name='usb'/> <master startport='4'/> <address type='pci' domain='0x0000' bus='0x00' slot='0x07' function='0x2'/> </controller> <controller type='sata' index='0'> <alias name='ide'/> <address type='pci' domain='0x0000' bus='0x00' slot='0x1f' function='0x2'/> </controller> <controller type='pci' index='0' model='pcie-root'> <alias name='pcie.0'/> </controller> <controller type='pci' index='1' model='pcie-root-port'> <model name='pcie-root-port'/> <target chassis='1' port='0x8'/> <alias name='pci.1'/> <address type='pci' domain='0x0000' bus='0x00' slot='0x01' function='0x0' multifunction='on'/> </controller> <controller type='pci' index='2' model='pcie-root-port'> <model name='pcie-root-port'/> <target chassis='2' port='0x9'/> <alias name='pci.2'/> <address type='pci' domain='0x0000' bus='0x00' slot='0x01' function='0x1'/> </controller> <controller type='pci' index='3' model='pcie-root-port'> <model name='pcie-root-port'/> <target chassis='3' port='0xa'/> <alias name='pci.3'/> <address type='pci' domain='0x0000' bus='0x00' slot='0x01' function='0x2'/> </controller> <controller type='pci' index='4' model='pcie-root-port'> <model name='pcie-root-port'/> <target chassis='4' port='0xb'/> <alias name='pci.4'/> <address type='pci' domain='0x0000' bus='0x00' slot='0x01' function='0x3'/> </controller> <controller type='pci' index='5' model='pcie-root-port'> <model name='pcie-root-port'/> <target chassis='5' port='0xc'/> <alias name='pci.5'/> <address type='pci' domain='0x0000' bus='0x00' slot='0x01' function='0x4'/> </controller> <controller type='pci' index='6' model='pcie-root-port'> <model name='pcie-root-port'/> <target chassis='6' port='0xd'/> <alias name='pci.6'/> <address type='pci' domain='0x0000' bus='0x00' slot='0x01' function='0x5'/> </controller> <controller type='pci' index='7' model='pcie-root-port'> <model name='pcie-root-port'/> <target chassis='7' port='0xe'/> <alias name='pci.7'/> <address type='pci' domain='0x0000' bus='0x00' slot='0x01' function='0x6'/> </controller> <controller type='virtio-serial' index='0'> <alias name='virtio-serial0'/> <address type='pci' domain='0x0000' bus='0x02' slot='0x00' function='0x0'/> </controller> <interface type='bridge'> <mac address='52:54:00:17:19:69'/> <source bridge='br0'/> <target dev='vnet1'/> <model type='e1000-82545em'/> <alias name='net0'/> <address type='pci' domain='0x0000' bus='0x01' slot='0x00' function='0x0'/> </interface> <serial type='pty'> <source path='/dev/pts/1'/> <target type='isa-serial' port='0'> <model name='isa-serial'/> </target> <alias name='serial0'/> </serial> <console type='pty' tty='/dev/pts/1'> <source path='/dev/pts/1'/> <target type='serial' port='0'/> <alias name='serial0'/> </console> <channel type='unix'> <source mode='bind' path='/var/lib/libvirt/qemu/channel/target/domain-2-OSX/org.qemu.guest_agent.0'/> <target type='virtio' name='org.qemu.guest_agent.0' state='disconnected'/> <alias name='channel0'/> <address type='virtio-serial' controller='0' bus='0' port='1'/> </channel> <input type='mouse' bus='ps2'> <alias name='input0'/> </input> <input type='keyboard' bus='ps2'> <alias name='input1'/> </input> <hostdev mode='subsystem' type='pci' managed='yes'> <driver name='vfio'/> <source> <address domain='0x0000' bus='0x0b' slot='0x00' function='0x0'/> </source> <alias name='hostdev0'/> <rom file='/mnt/user/backup/mojave/Sapphire.RXVega64.8192.180125.rom'/> <address type='pci' domain='0x0000' bus='0x03' slot='0x00' function='0x0'/> </hostdev> <hostdev mode='subsystem' type='pci' managed='yes'> <driver name='vfio'/> <source> <address domain='0x0000' bus='0x0d' slot='0x00' function='0x3'/> </source> <alias name='hostdev1'/> <address type='pci' domain='0x0000' bus='0x04' slot='0x00' function='0x0'/> </hostdev> <hostdev mode='subsystem' type='pci' managed='yes'> <driver name='vfio'/> <source> <address domain='0x0000' bus='0x0c' slot='0x00' function='0x3'/> </source> <alias name='hostdev2'/> <address type='pci' domain='0x0000' bus='0x05' slot='0x00' function='0x0'/> </hostdev> <hostdev mode='subsystem' type='pci' managed='yes'> <driver name='vfio'/> <source> <address domain='0x0000' bus='0x44' slot='0x00' function='0x3'/> </source> <alias name='hostdev3'/> <address type='pci' domain='0x0000' bus='0x06' slot='0x00' function='0x0'/> </hostdev> <memballoon model='none'/> </devices> <seclabel type='dynamic' model='dac' relabel='yes'> <label>+0:+100</label> <imagelabel>+0:+100</imagelabel> </seclabel> <qemu:commandline> <qemu:arg value='-usb'/> <qemu:arg value='-device'/> <qemu:arg value='usb-mouse,bus=usb-bus.0'/> <qemu:arg value='-device'/> <qemu:arg value='usb-kbd,bus=usb-bus.0'/> <qemu:arg value='-device'/> <qemu:arg value='isa-applesmc,osk=<REDACTED>'/> <qemu:arg value='-smbios'/> <qemu:arg value='type=2'/> <qemu:arg value='-cpu'/> <qemu:arg value='Penryn,vendor=GenuineIntel,kvm=on,+invtsc,+fpu,+vme,+de,+pse,+tsc,+msr,+pae,+mce,+cx8,+apic,+sep,+mtrr,+pge,+mca,+cmov,+pat,+pse36,+clflush,+mmx,+fxsr,+sse,+sse2,+syscall,+nx,+mmxext,+fxsr_opt,+pdpe1gb,+rdtscp,+lm,+pni,+pclmulqdq,+ssse3,+fma,+cx16,+sse4_1,+sse4_2,+movbe,+popcnt,+aes,+xsave,+avx,+f16c,+rdrand,+lahf_lm,+cmp_legacy,+svm,+abm,+sse4a,+misalignsse,+3dnowprefetch,+osvw,+topoext,+perfctr_core,+ibpb,+fsgsbase,+bmi1,+avx2,+smep,+bmi2,+rdseed,+adx,+smap,+clflushopt,+xsaveopt,+xsavec,+xgetbv1,+arat,+npt,+nrip_save,vmware-cpuid-freq=on,'/> </qemu:commandline> </domain>
-
Quote
Dec 9 01:36:27 Tower afpd[33541]: afp_createfile("3020"): CNID error Dec 9 08:36:38 Tower afpd[33541]: afp_createfile("6148"): CNID error Dec 9 15:48:15 Tower afpd[47589]: afp_openvol(/mnt/user/time_machine): Fatal error: Unable to get stamp value from CNID backend Dec 9 17:30:11 Tower afpd[39327]: afp_openvol(/mnt/user/time_machine): Fatal error: Unable to get stamp value from CNID backend Dec 9 17:31:10 Tower afpd[41795]: afp_openvol(/mnt/user/time_machine): Fatal error: Unable to get stamp value from CNID backend Dec 9 17:33:15 Tower afpd[47014]: afp_openvol(/mnt/user/time_machine): Fatal error: Unable to get stamp value from CNID backend Dec 9 18:41:44 Tower afpd[90094]: afp_openvol(/mnt/user/time_machine): Fatal error: Unable to get stamp value from CNID backend Dec 9 19:49:30 Tower afpd[130379]: afp_openvol(/mnt/user/time_machine): Fatal error: Unable to get stamp value from CNID backend Dec 9 20:57:15 Tower afpd[37413]: afp_openvol(/mnt/user/time_machine): Fatal error: Unable to get stamp value from CNID backend Dec 9 22:08:33 Tower afpd[83985]: afp_openvol(/mnt/user/time_machine): Fatal error: Unable to get stamp value from CNID backend Dec 9 23:51:15 Tower afpd[78311]: afp_openvol(/mnt/user/time_machine): Fatal error: Unable to get stamp value from CNID backend Dec 10 00:52:15 Tower afpd[99541]: afp_openvol(/mnt/user/time_machine): Fatal error: Unable to get stamp value from CNID backend Dec 10 01:56:53 Tower afpd[129835]: afp_openvol(/mnt/user/time_machine): Fatal error: Unable to get stamp value from CNID backend Dec 10 03:01:30 Tower afpd[29561]: afp_openvol(/mnt/user/time_machine): Fatal error: Unable to get stamp value from CNID backend Dec 10 03:02:28 Tower afpd[31987]: afp_openvol(/mnt/user/time_machine): Fatal error: Unable to get stamp value from CNID backend Dec 10 05:05:55 Tower afpd[77584]: afp_openvol(/mnt/user/time_machine): Fatal error: Unable to get stamp value from CNID backend
I think it causes my time machine backup act abnormally. Does anyone has tip fixing it?
Thank you!
-
9 minutes ago, trurl said:
raid1 is the default setting for the btrfs cache pool so no command needed. Other settings are discussed in the Cache Pool section of the Unraid V6 FAQ
I had one ssd in the beginning, later I added one for raid1. Had to manually type in the command, because when the second ssd got inserted, the system set up raid0 for the two ssd (unraid 6.6.5).
-
Strange, one data point here:
I am using Threadripper 1950x with Vega 64 (upgraded from RX580) and GTX 1080, everything is perfectly fine.
-
18 minutes ago, ufopinball said:
I have a cache drive. An array drive means I get Parity protection in case of a drive failure, and cache or UD doesn't offer that. The performance boost I'm looking for is on the Read end of things. Writing to this drive will likely be relatively rare, it's just data I don't want to wait for a HDD to spin up for.
Cache pool with RAID1 does offer protection. I forgot the command, but I have set up RAID1 cache pool on my system.
-
Thanks, dynamix plugins are great, thanks for creating them
I guess I am just paranoid...
-
Thanks!
Among all the plugins, the only one that I actually need is SSD trim (fstrim -v /mnt/cache/).
I am personally concerned with the risk that my data could be exposed by a malicious plugin or some malicious code accidentally introduced during a plugin update. So I ended up removing all the plugins and set the SSD trim manually using crontab.
-
5 hours ago, trurl said:
What plugin do you mean?
Plugin in general, for example, if the plugin is sandboxed / have no API or permission to access user data.
If accessing user data is possible, I will reduce the number of plugin I use to a bare minimal to reduce the risk.
-
Same as topic, thanks!
Cache pool used size wrong
in General Support
Posted
Thank you! Seems now it is redundant:
Overall:
Device size: 931.52GiB
Device allocated: 744.06GiB
Device unallocated: 187.46GiB
Device missing: 0.00B
Used: 656.83GiB
Free (estimated): 136.39GiB (min: 136.39GiB)
Data ratio: 2.00
Metadata ratio: 2.00
Global reserve: 34.42MiB (used: 0.00B)
Data Metadata System
Id Path RAID1 RAID1 RAID1 Unallocated
-- -------------- --------- -------- -------- -----------
2 /dev/nvme0n1p1 371.00GiB 1.00GiB 32.00MiB 93.73GiB
1 /dev/nvme2n1p1 371.00GiB 1.00GiB 32.00MiB 93.73GiB
-- -------------- --------- -------- -------- -----------
Total 371.00GiB 1.00GiB 32.00MiB 187.46GiB
Used 328.34GiB 78.42MiB 80.00KiB