je82

I have issues with SMB on my Unraid install, both windows 2012 r2 and windows 10 pro are behaving the same. Samba is accessible and fine with my credentials i have setup but randomly when i write data to the array via smb the connection drops and smb stops responding, Unraid still responds to ping from the computer though so it's a not a connectivity issue but a SMB issue. I am preclearing some drives so i cannot enable smb logging for now but i will report back with what i find in the smb logs once i have time to do so, i really hope to resolve this as smb is a major part of my network. Unraid is built on linux, i have 3 linux installs all that have smb, they all work properly so not sure what's specific with the smb on unraid.

thanks! array must be stopped doing some pre clears will have to report back with findings tomorrow.

but why would a post from 2017 be relevant to a plugin written summer 2019? EDIT: ah i see its a browser session issue.

Hello, I have a weird issue with my new unraid install that i did not experience on my test install with different hardware. First i though it was a network issue but it is not, the box never stops responding to ping, only SMB locks up and is unaccessible randomly when writing files to the array. How do i go about to diagnose the issue? Tried finding a SMB log file but i couldn't find it, usually it is in /var/log/samba but the files appear emtpy?

Hi, Suddenly my log is flooding with : Nov 5 20:07:43 NAS root: error: /plugins/unassigned.devices/UnassignedDevices.php: wrong csrf_token I have the latest stable build of unraid and latest version of UnassignedDevices, what could be causing this?

After more checking it's definitely not a network or connectivity issue, i setup a simple ping to run while it's running the filesync and ping never looses any packages but it still is occurs. I believe the issue is with the samba protocol. I SSH'd into the unraid install and went to /var/log/samba/ and checked the logs but they appear empty, where can i find logging for samba? Thanks

Alright, i though there might be something at the unraid end that checks for signal that written file has been completed and it want to apply some meta to the file and the file gets locked by the unraid system for a very short period of time and sometimes ffs is so quick it tries to rename the file at the exact same time as unraid is applying the meta resulting in file being locked and permission denied. I have not noticed any network drops from neither unraid or the server sending the files and it seems to only occur when using ffs that has this thing where it writes a temp file first then renames it. It's not a big problem, i've setup ffs to retry if it occurs.

Hi, I've started migrating my data over to unraid and i've came across some weird issue. I've setup FreeFileSync to simply mirror a path locally to a path on the unraid setup via a smb share. Mirror d:/mystuff1/ > //unraid/mystuff1/ For each file FreeFileSync writes a filename.randomhash.tmp first and starts building the file, then once the file is build it checks crc and then renames the file to filename.extension Sometimes during this renaming process the file becomes inaccessible and freefilesync tells me it has no permission to rename the file. This does not occur for every file and appears to be random. The SMB share has no caching enabled, and i have enabled "CA Turbo Mode" plugin for faster write speeds. Any ideas? Thanks.

very nice thanks, looks like someone already done something like this, "Catalog Drive Contents"

Hi everyone. I've given up trying to build an unraid server using conventional chassis, i am now looking for a server mounted chassi, 20/24bay 3U or 4U. I've found plenty of older super micro chassis that seem good but the problem is i see these fans are like 80mm and they also sound like jet engines. This is my main problem with actual server hardware, i understand that under stressed conditions these chassis can cool everything properly, but for me i do not need these high efficiency cooling solutions. I am wondering if it possible to swap these fans for other traditional noctua fans? Or are there server chassis build in this form factor that support 140mm fans? To me it is enough to have the air moving, it does not have to be a wind tunnel. Do you have any ideas in good chassis to look at ? I need at least 20bays.

Hello. I want to have a script that runs every night and simply outputs all the files/folders on target drives specified to a text file on a share somewhere outside of unraid. Why you may ask? In the highly unlikely scenario of actual data loss i want to be able to see what was lost after the fact... It's very difficult to keep track of what data is on which drive when you have a large array and once data is gone how are you suppose to know what you lost? Knowing what data is lost mitigates the pain a lot. Anyone know how i could go about doing this?

Hi, Anyone using this beautiful chassi for Unraid? I acutally want to do a dual build with one Unraid server and then another server i use for otherstuff, the only problem i have with the Thermaltake chassi is that it only seems to support 10 interla 3.5mm drives if you are making a dual build, it seems strange as the chassi is absolutely huge. Does anyone here own the addon case P200 which you can put on the bottom or the top? The speficications for this part does not say it can hold any drives but maybe it is possible to mod it do hold all the drives? If not going fot the W200/P200 case for unraid which are your recommendations? I prefer to not use rack mounted chassis for now, but perhaps i should just do rack mount? Budget is not an issue. But i need at least 20 3.5mm hd slots and i would really love to have a case where i can insert dual psu and motherboard for that dual build. EDIT: Sorry, can a mod please move this thread to the Hardware section, i missed that it existed.

Alright, thanks for the info. I guess the pre-clear is a good way of finding out the drive is actually healthy if it is indeed writing to all the sectors.

Considering i have around 100tb terabyte of data to add to unraid and only 1 spare 8tb drive +2 parity drives that will be used for the project i would like to know the most efficient way of building the array one disk at a time. What i have to do is start unraid with the 2x parity drives and the 1x 8tb drive i have spare, then move data of one of my 8tb drives and fill the 8tb drive in unraid, then power of, add the empty 8tb drive to array, and continue doing so until over 100tb is added. What would be the best way of doing this? Am i doing this correctly or am i loading the system with a lot of uneccessary write/reads? Thanks for the continous support!

It was not pre-cleared, does pre-clear have to occur before adding a drive even though the drive was empty? I did format now and you are correct, the format process was instant, it looks correct now.

Hello, I am trying to figure out how unraid works. This time i did with my lab: Power of the system when everything was green. Add harddrive physically to the machine. Power on machine Add the unassigned device to an open array slot. Once array was mounted it asks for format the new disk to use it in the array. Once this completed (took 4 hours) it now shows me the following: Disk 3 is the new disk. My question is, why is the new disk that was just formated for 4 hours asking to be formated again? I've set the default filesystem to be XFS Encrypted, so i took for granted that the system understood what was going to be done with the disk and i was asuming it was applying the encryption to the disk when it formated it for 4 hours but now it shows as unmountable (?) and it doesn't look like it used XFS Encrypted file system even though the config is set to have XFS Encrypted as default filesystem. When inspecting Disk 3 it tells me "File system type: auto", what does that even mean? I figured auto = whatever default configuration in unraid is set to? What did unraid do for 4 hours? Help me understand what i did wrong.

Thanks for the info. I guess the follow up question would be, what happens if a whole controller card starts being trouble and instantly drops 8 drives, i cannot rebuild because 8 drives were lost/disabled. What do i do in this scenario to save the data? I guess what i am asking, how do i go about mounting an encrypted unraid XFS disk directly in linux in order to access the data as a "jbod" drive instead of in an array, in case of an emergency. Thanks.

Thank you! I will try this after the rebuild is complete and simulate a drop again. I am only doing this for testing, i want to know how this stuff works exactly before i migrate my data over so i have an idea what to do when shit hits the fan. You're saying that using the parity correction check and only let it run for a couple of minutes will safetly cover whatever was done very recently after the drive may have dropped? That is good to know. Thanks for the info!

Ok so serial number it is, thanks for the heads up! Will save me a ton of time in the future once a drive decides to give in.

Hi, I am in the process of building a box with 20+ drives, what do you suggest i do to label each cable so i know which drive i need to pull if one fails later on? Does the tags "sda,sdb,sdc,sdd,sde" etc stand for the static port numbers on the sata controller? So these never change? Whats the best way to approach labeling these cables, my guess is just identify once which one is SDA, SDB etc and that should never change, am i correct?

In my test lab i have 2 parity drives 2 drives in raid array that is active 1 drive which is same make/model as the other 2 in the array but is not active in the array. 1 cache device I wanted to remove the 1 drive which was the same make/model as the other 2 that are active in the array. I didn't know which disk was which so i accidentally pulled one of the drives that were active in the raid array (while system was on and array mounted) The drive became emulated, which is expected. I shutdown the system and pulled out the correct device that i wanted to remove. I power on the system, now 1 drive that was pulled earlier from the array is emulated and disabled even though its a working drive. I unassign the device, power on the array, shut down tha array, reassign the device. Now it has to rebuild? Why do i have to rebuild when the data is there already? TLDR: How to enable a disabled device without having to rebuild all the data on it?

Yeah but how can it emulate it on the fly? I though it had to be "rebuilt" using the parity, not that the data would be instantly available via emulation, it's actually very impressive. I also do not understand if i have 2x 12tb parity drives, and then i have an over 100tb array, how can the parity devices of 24TB total cover all that data? To a mortal like myself it simply does not makes sense, but i thank you all for developing this incredible piece of software, i will be purchasing 2 full licences very soon!

Yeah i have setup unraid in a test lab with crap stuff i had laying around, just trying to understand my way around it completely before i migrate my actual real stuff over to it. I still have no idea what kind of wizard you have to be to make this kind of software. I setup a smb share which exclusively put data on one of the drives and ignoring the other, after i had sent 400gb and the parity was built i simulated that the drive crashed by disconnecing it via sata cable, suprirsingly all the data was still available via smb, i have absolutely no idea how that is possible.

Okey, problem is, i tried to add a drive to my already configured array and only way to successfully do it was to do "new config" then keep the settings for the old drives. If i didnt do new config and adding the unassigned device to the array unraid would not let me start the array. How exactly do you expand your array without doing new config? Note: during the time i tried to add a new device my parity drives were not completely built, was this the reason i could not add the device without doing new config?

Hi, i just want to make sure i understand this correctly. Pairity rebuild is only needed when you replace a disk to an already configured array or create a new array. If you add another drive to an array (expand the array) rebuilding the parity is not needed. Is this correct?