Mavric1298

Having the same issue as many with inability to spin down one of my drives + my parity drive. Literally instantaneously spins back up and has half a million reads in the first minute of up time after a reboot. File activity is showing these random temp files being created as well opening of a VM disk image that isn't running and isn't showing as modified. Any ideas? Even in safe mode, will all dockers shut down, and no HBA card still having this issue Dec 11 11:03:54 OPEN => /mnt/disk1/domains/Macinabox BigSur2/macos_disk.img Dec 11 11:03:56 OPEN => /mnt/disk1/domains/Macinabox BigSur2/macos_disk.img Dec 11 11:03:56 OPEN => /mnt/disk1/domains/Macinabox BigSur2/macos_disk.img Dec 11 11:03:56 OPEN => /mnt/disk1/domains/Macinabox BigSur2/macos_disk.img Dec 11 11:03:56 OPEN => /mnt/disk1/domains/Macinabox BigSur2/macos_disk.img Dec 11 11:03:56 OPEN => /mnt/disk1/domains/Macinabox BigSur2/macos_disk.img Dec 11 11:05:06 OPEN => /mnt/disk1/domains/Macinabox BigSur2/macos_disk.img Dec 11 11:05:06 OPEN => /mnt/disk1/domains/Macinabox BigSur2/macos_disk.img Dec 11 11:05:06 OPEN => /mnt/disk1/domains/Macinabox BigSur2/macos_disk.img Dec 11 11:05:06 OPEN => /mnt/disk1/domains/Macinabox BigSur2/macos_disk.img Dec 11 11:05:06 OPEN => /mnt/disk1/domains/Macinabox BigSur2/macos_disk.img Dec 11 11:05:06 OPEN => /mnt/disk1/domains/Macinabox BigSur2/macos_disk.img Dec 11 11:06:15 OPEN => /mnt/disk1/domains/Macinabox BigSur2/macos_disk.img Dec 11 11:06:15 OPEN => /mnt/disk1/domains/Macinabox BigSur2/macos_disk.img Dec 11 11:06:15 OPEN => /mnt/disk1/domains/Macinabox BigSur2/macos_disk.img Dec 11 11:06:15 OPEN => /mnt/disk1/domains/Macinabox BigSur2/macos_disk.img Dec 11 11:06:15 OPEN => /mnt/disk1/domains/Macinabox BigSur2/macos_disk.img Dec 11 11:06:15 OPEN => /mnt/disk1/domains/Macinabox BigSur2/macos_disk.img Dec 11 11:09:04 CREATE => /mnt/disk1/1585664650.tmp Dec 11 11:09:04 OPEN => /mnt/disk1/1585664650.tmp Dec 11 11:09:04 MODIFY => /mnt/disk1/1585664650.tmp Dec 11 11:09:04 OPEN => /mnt/disk1/1585664650.tmp Dec 11 11:09:04 DELETE => /mnt/disk1/1585664650.tmp

This might be something simple, but how do you install a second VM with the same IOS? Can you edit the scripts (helper script and notify script) without affecting current VMs?

My node seems to be copying files to cache for transcode, but then never returning them even though they are completed and it is set to work in place with all output settings turned off. The media share itself is set to disk only yet now files in that share are on the ssd cache used for transcode

To revive this - important also when you first setup a sever, the above happens. GUI looked like it was pointed to the correct cache pool, but this was indicating it wasn't, and the turning off then back on corrected the error. I guess this would be because setting up a new cache/ssd when you first create the server is basically the same as renaming it? From all appearances it looked correct and I would have had no idea anything was wrong

This may be a dumb question, but is there a way to pull files off a VM from Krusader (lets say my VM stops working - I currently have my Big Sur pulling my photos down to photos app (ie original files going to the *.photolibrary which is ~90gb) and am trying to figure out how reliable of a second copy of my iCloud data this is or if it totally relies on a working VM