scot

FYI it worked great. I did the new config change.

Working fine. I had tried a dedicated docker/smb, but moved back to the stock unraid 7 system and continue with ZFS and a SLOG device. Just make sure power doesn't die in a backup, this is critical it will kill your backup.

I have unraid setup that was upgraded from 6, using zfs as the primary storage. I do not use the array drive, but have one just because it was required in unraid 6. All shares are in zfs. There are no files on the array. Without assuming I know anything, how do I get rid of the array and usb drive that makes it up, with no other changes? I've seen discussions around 3 different methods, new config, array shrinking, and stopping the array and changing the array to no drive. None of which sound exactly right, or at leave enough doubt that I don't know what the end result will be. Not to mention "new config" being a bit scary sounding looking at its warnings to be honest.

this is way off topic but you can downgrade the IPMI/iDRAC and get more granular control of the fans. I'm not an expert, but search and you will find a few resources on how to do it and what to expect. This is *not*perfect as the downgrade has its own issues, but as far as I know is the only way to go.

After a ton of attempts and failures, just wanted to give up some basic advice. TLDR: Use a SLOG with ZFS to make TimeMachine work, may have some Mac based benefits as well. Issue: Using Time Machine over SMB writing to a ZFS based storage system works at first, but then starts to take longer and longer as time goes on. Eventually it gets so slow that a failure occurs. My guess: If you let it continue it will seemingly start trying to backup when a previous backup is ongoing causing a corruption in the backup. Your only option at that point is to delete and start over. This only happens when you have a long history, maybe a few months with a lot of changing data backed up and a large space dedicated (5tb in my case, failures start at around 2tb in stored space used). Initial solution: Tried every setting under the sun and eventually switched to mortizf's Time Machine Unraid app. This has its own dedicated samba system and worked initially (like every time I restarted my backups) but eventually failed. Increased system speed and added 2.5gbe ports, no effect. Then a thought occurred:: Time Machine over SMB forces Write Sync. This is important and relates to ZFS. If the issue is the system binding up, would this be the one place an SLOG device would actually help? Popped in an SLOG device, did it wrong (command line, causing Unraid heartburn) but ZFS worked and accepted the SLOG as its own. See another post I made about fixing Unraid's visual of the SLOG device. Backups went from ~11hrs per single daily update, down to about 20-30 minutes or less if doing hourly. This is just due to how ZFS works and inefficiencies in the overall system including SMB and the like, but it no longer gets hung up on the millions of small write and commit requests. I can't say for sure this will solve all of your issues, and probably won't make a huge difference otherwise, but in my case *everything* works faster from Mac, including directory listing. I have no idea why directory listing would involve a synchronous write, but... I cant argue the difference. In my case I am using a 6 drive array (4+2 raidz2) 20tb per disk, with a single nvme with 128gb in the SLOG. Eventually I will change that to a mirrored pair and only 64gb. I make no claims about XFS and other file systems or the fuse style file system or anything else. This is purely a ZFS based file system directly shared.

Perfect, came up and everything shows as active.

When you say unassign, I am assuming you mean to go the pool devices on the "Main" tab, then select each drive one by one under identification, then select no device. Repeat for each one. When that is done go to the bottom and hit start under array operation. I attempted to do this, but start remains grey stating "missing cache disk", it does offer a checkbox to force proceeding. "Start will remove the missing cache disk and then bring the array on-line. Yes, I want to do this" Double checking since the terminology you are using isn't precisely matching the UI. Apologies.

I believe I went over the drive limit with the addition of the SLOG due to the fact the "array" has to have a single drive in the system (usb) that I use for nothing else. So rather than try to work around that, I upgraded the license. I am pretty sure I can start the array, but your instruction made it seem like i should add the SLOG to the pool device list. I added it, but it gave me an error about wanting to expand the array, which i certainly don't want to do as it was working and the UI makes me believe it is trying to expand the space in the pool, not just recognize that there is a SLOG. I just want it as a slog which has an INCREDIBLE effect on speeding up time machine backups as they get larger. (probably about 90% drop in time to backup) tower-diagnostics-20240118-1050.zip

pool: zfs id: 373615592619169231 state: ONLINE action: The pool can be imported using its name or numeric identifier. config: zfs ONLINE raidz2-0 ONLINE sdg1 ONLINE sdh1 ONLINE ata-ST20000NM007D-3DJ103_ZVT8NRQ5 ONLINE sdc1 ONLINE sdd1 ONLINE logs ata-Samsung_SSD_850_EVO_250GB_S2R5NX0J542745K ONLINE tower-diagnostics-20240118-0845.zip

Unraid is currently not able to start my array, too many drives error, though i've rebooted a few times since replacement and addition of a slog. It also doesn't show the replaced drive in the pool of devices. I have 5 drives in my array and 1 slog, plus a boot usb. I replaced via the standard cli, so maybe I screwed it up and it thinks I have 6 in the array? need to figure out how to get unraid to clean up and see the zfs pools as they exist. Any ideas on what I should do next?

Same issue here. If all of the dockers are stopped, it works properly.