SimonAG

I bought one of those plugin dust air blowers and clean the case out twice a year now and my temps are looking perfect since 6.12.6 and in winter I can even remove the front fans now if I wanted to, which looks a lot better. Still planning on moving to a new case at some point.

Is there any way to make the files while they are still on the cache writeable? If I download something and then want to remove it, I can't delete it until it has been synced to the main array. Is there a way to change the permissions on the cache drive so that I can delete through SMB?

2023 update on my build Unraid Logic Case SC-43400-8HS Gigabyte GA-Z87X-UD4H Intel 4670k 3.8ghz 8GB corsair unbuffered 8 Port SilverStone ECS04 3x 12TB SEAGATE 5x 6TB SEAGATE 550W Seasonic Focus Gold PSU 2x 140mm fan 1x 512gb cache drive Pfsense in-Win IW-RF100 Supermicro A2SDi-4C-HLN4F 4gb 2133mhz Unbuffered 60gb SSD TPLINK EAP660HD 8 port netgear switch UPS Cyberpower 780w Interesting to see the entire setup including another windows media pc, vero 4k, my LG CX and the unraid nas only uses 110watts at idle.

I finally bought a 512gb SSD for a cache drive cost me £25 and I couldn't believe how much it allowed for my main array to not be spun up and reduced disk temperatures of the array overall.

I did it I live another day.

You can understand my hesitancy though? the button is in the same list as the start stop array etc.

I can see it shows format will create a file system in all unmountable disks and then shows the new cache drive on the left side as the only disk. When I click are you sure box it warns me it is going to wipe the disk etc. I just want to be sure this is not going to touch the main array, I don't think it will but I don't think it is clear enough for me to just do it without posting this for confirmation. Its only going to format the cache right and is there any other way I can format the disk, like with the array unmounted and just that disk selected?

OK thanks, sorry for being blind and doing no research on this one. Seems like I might have a justification to add a cache SSD now though.

Am I correct in saying that there are no system logs prior to a reboot? Is there an app I can use to backup syslog across the network then? I had a weird power cut and not sure what my UPS did and wanted to investigate the cause but it seems the logs start at the current boot up time. Alternatively if the system logs could be copied to persistent storage that could help to solve it as well, is that possible. I could keep a copy on the main array.

Adding one more array would be a great addition because would allow for different controller on the same Pc to manage the drives. After 1 or 2 arrays is not realy feasible. The cache is useflul but having a few more arrays would be even more useful. I like unraid in how the data sits on the disks compared to zfs.

At the moment my main array is done through the pcie HBA connector but it would be possible to add more sata disks or pcie disks using ssd now that they are coming down in price. Is adding a second array on the roadmap or will that never happen in unraid?

There was some bad firmware that caused slow disks years ago on HP controller. https://community.hpe.com/t5/ProLiant-Servers-ML-DL-SL/Smart-Array-P420i-extremely-slow-writes/td-p/6497596 Might be the cause, try in MC over ssh between disks, that should cut out network as the cause.

Does it always throw up a parity check when there is an unclean shut down? Is that just a precaution or is there something that happens on a clean shutdown that makes parity integrity better?

By mistake I turned off the mains power and my unraid lost power and rebooted afterwards and started up without issue. When I started the array it kicked off a parity check, I only just parity checked a few weeks ago as done some new drives and with the weather being hot at the moment, it is not ideal for me to run a parity check. I did cancel the parity check, am I taking a big risk there? There was no writing to data drives going on when the power cut and all the data is fine.

never mind, I see you use the scheduling to add the cron for you...

Looks like I found the problem with the delete access. The Ownership of the files is set to user "nobody" instead of the user "windows username" which is the user for the rest of the files. Interesting that these files were created by the filezilla docker with the folder mounted in to the docker image. Previously everything was downloaded through my windows PC to the NAS shares and that is why they end up with the owner "windows username" group "users" that allows me to delete those files. So a simple chown -R username:users might be sufficient here? I wonder if there is a way to force that user on to those docker downloaded files. So again completely unrelated to the parity change, just doing too many changes at the same time I guess Chown worked fine so now just need to post in to the filezilla docker thread and try get those files to default to the correct user. otherwise have to setup a cron job to chown it i guess.

What i do is I add a user to Unraid with the exact username and password that I use in windows and then I have no problem adding the mapped drives after that. Then apply read write for that username to all the shares. Seems to do the job for me without changing the guest access gpo. Then if you want a private share, you can set private on the permissions and then set no access on guest access but read write on your user that you added.

NFS problems definitely caused by vero 4k and changing network config. So not related. SMB delete problem i think is smb permissions as i can delete over nfs. it says tower/nobody lacks permission. i tried reexporting the smb. All shares are public so not sure the issue, Not urgent so i will wait for any advice before doing anything else. sorry for triple post.

From what I can see, it is only affecting files and folders that were shared to a filezilla docker, I have removed the docker completely but they are still read only. I can remove other files and folders from other shares. Strange one.

Data drive replaced fine but still have the read only on windows over SMB, not deleted over nfs. Is there an issue? Any reason for me not being able to delete folders/files over SMB after a parity drive change? Do I need to reboot? NFS seems fine now but not tested deleting from NFS.

Does the array need to be stopped or not in an array operation in order to get a good backup? To what extent will I need to keep the backup up to date, will it only be array operations like replacing disks or do I need to do it after every parity check?

OK, I see there is a way to move the license in the options. If I set up a auto backup of the config folder to my windows PC, in future if it fails I can just copy that back to a new usb? It did say in the documentation that if i use the flash drive backup it will break the existing USB drive. Can I load the license in once I have copied the config folder back over to a new USB without using that export option and breaking the existing usb? What is the path to the config folder, I connected over sftp but don't see it. Sorry if that is in the documentation.

If the USB drive holding unraid failed (unlikely but if it did) could I just install a new USB with unraid and then select the same disk configuration and it will detect the configuration and work? That didn't see possible to me as when you create a new array it needs to wipe the hard drives or am i missing something? If not what is needed to backup the disk configuration only?

Just to follow up, replacing the parity went through without a problem and took 25 hours to rebuild 40TB of data to parity whilst also going from 6TB to 12TB parity. I did however run in to a few strange problems. After rebuilding the parity, I was unable to delete anything from the array over SMB from windows, said I lacked permission. What could cause that? I am restarting again now. Just using the old parity 6TB to replace the final 4TB in the array and bringing total space up to 42TB. I also had an issue with NFS after the parity rebuild, where it seemed to freeze up my vero 4k when accessing NFS shares. When I stopped the array vero 4k unfroze immediately, so it was like a stuck connection? It was working fine, i was watching content over NFS, then I noticed that some of the latest content was not showing up over NFS, from SMB in windows it was displaying fine. Then when I restarted Vero and went back to NFS shares that is when it started freezing up. I have since rebooted and will wait until this data rebuild has finished and then I will test the deleting over SMB and NFS from vero again.

OK thanks.