January 28Jan 28 So I threw together this array with a retired SAN full of SSD. It's fantastic, but massive overkill. What's the best method for removing some disks from the array? I figure it's best to pull a bunch out and sell them off rather than have them sit here empty for the better part of forever.
January 28Jan 28 Community Expert I always say each additional disk is an additional point of failure.Looks like many may be empty. Diagnostics would tell us which disks are used by each user share.Attach Diagnostics ZIP to your NEXT post in this thread.
January 28Jan 28 Community Expert 1 hour ago, jamesmcg said:array with a retired SAN full of SSDSSDs in the array cannot be trimmed, and can only be written at parity speed. The usual place for SSDs is in pools. Unraid V7 doesn't require an array.appdata, domains, isos, system shares are using disk22. Probably you did that on purpose, but some of those also have files on other disks. Ideally, docker/VM related shares - appdata, domains, system - would have all files on cache or other pool with nothing on the array, so dockers/VMs will perform better, and so array disks can spin down since these file are always open. Of course some of that is irrelevant since these are all SSDsOther than that, only disks 1-6 have any user share data on them. User shares are the combined top level folders on array and pools. If there are any files at the top level and not in a folder I can't tell that from diagnostics. Not really any good reason to have files at the top level anyway.Your share names are anonymized in the diagnostics so I can't really see what they are called except for those defined by your docker/VM settings. There are 2 that I wonder about though.b-----s shareUseCache="no" # Share exists on disk1, disk4, disk5 B-----S shareUseCache="no" # Share exists on disk2, disk3, disk4, disk5, disk6Do these have the same name except for upper/lower case, or are they different? Linux is case-sensitive, so they are different as far as linux is concerned, but maybe you meant for them to be the same?You have given 500GB to docker.img. That is at least 10 x larger than reasonable.
Join the conversation
You can post now and register later. If you have an account, sign in now to post with your account.
Note: Your post will require moderator approval before it will be visible.