Frank1940

Check the version of the Samba client on the Android device.

You have to run a correcting parity check to fix those 2476 errors. (To double check that all is well, you might want to run a non-correcting one after that.) If the correcting one finds more than 2476 errors, I would be really concerned at that point. I would not care that much if they are older by several hundred hours if they are healthy. (CRC errors are not an indication of disk health! 99.99% of all CRC errors are caused by something besides the hard drive.) Personally, I would get that parity drive out of my server. I might want to test it by doing a couple of preclear cycles on it or a full SMART disk on it. (You could do this with the Unassigned Devices plugin if you have space in your server for another drive.) Of course, it is over 3.5 years old... I confused, too. What 55 errors????

I suspect that the power being off had something to do with it. You may not realize it but shutting it down does not really 'shut' everything down! In fact, your NIC will be active if the BIOS is set up to 'wake up on LAN'. (The NIC might have gotten itself in some mode that a simple reset would not correct...) I have watched one of my servers when it is rebooted. It appears that it completely shuts down but I know that the PS is still active and it does supply some power to the MB during this period.

I am assuming that you have already purchased and have the professional license installed on your server. (You will find a file named Pro.key in the /config directory on your boot/flash drive. That file is your license!) First thing, make a backup of your current boot drive. Main >>> Boot Device (left click on 'Flash') >>> Flash Device Settings Find the 'FLASH BACKUP' button and click it. That will make a backup of your flash drive to your local computer. (This is your safety net in case things go badly.) Now make a print out of the MAIN tab of the GUI. This will show the current disk assignments. I would also make printouts of any of the SETTINGS tabs that you have changed. Shutdown the server using the GUI. You can now format that flash drive and reload Unraid on it. Copy the Pro.key file into the /config directory. Put the flash drive in the server and boot it up. Use the printouts to assign the drives (by serial number) to the same position. Start the array. (Do NOT format any disk--- even if Unraid suggests it ---as you could lose data!!!!!!) Make changes to the SETTINGS tab as required. There are ways to copy over portions of the /config directory (to save some of this grunt work) but since you have problems with corruption in your PLEX setup, it might be best to avoid that. (If you have a share set up for data that PLEX uses internally, you might want to address that issue.--- renaming the share would be my first choice.)

The Gurus are going to need the Diagnostics file. Post it up in a new post in this thread. You added six more drives. Which ones are they in the screen capture above? Did you get a HBA to add more SATA ports? If so, what are the details on it? EDIT: Did you 'retire' an HBA?

You are basically right on both counts. Without checking the unused area of the parity disk, you would not have advance warning that there was a problem until you actually encountered it. (Finding out that one can't restore a data disk because of a previously undetected problem is something most of us do not want to deal with!) While the normal periodical parity check would catch it, it is always unsettling to the user when it happens. And usually there is no way to determine where the problem is on the disk and, in many cases, there is no indications as to what disk has the problem if it is not a bad sector issue. (Unclean shutdowns often results in parity errors being found on the force parity check on the restart. More than 90% of these are fixed by rebuilding parity. Apparently, the parity update is the last thing written to the array and more often than not, a correcting check brings parity into sync without data loss.) You can make an argument both ways. Doing so would add to the complexity of the parity-checking function because the code required to implement it. It would require a setting up a default (check or not check the unused area) setting. A decision to be made by perhaps a neophyte. (The discussion on this topic alone might fill several pages of heated opinions in the forum...)

If it does, it will cause a read failure on that drive. The drive will attempt to fix the problem through its error-correcting software. If it can not be corrected, then the disk will be flagged with one of the 190-series SMART attribute codes. (Depends on the drive manufacturer which one.) Remember that a new data drive is added to the array by zeroing every byte (offline), added to the array and formatted (updating parity). It is assumed at this point that parity is correct (and that the parity disk has no errors)! Checking parity is not a part of adding a new data disk. IF the parity disk has a bad sector, the array will not have parity protection and you will not be aware of it until the next parity check after adding the new data disk.

Have a look at the Appdata Backup plugin. I believe it will do what you want. If you have questions, ask them in the Support Thread.

Personally, I would be looking for .5m cables. There is much less excess cable to position inside of the case. Tying excess cable in a tight bundle is not a good idea. It concentrates the mass and increases potential for vibrations that can loosen the connector and increase the potential for cross-talk which are another cause of CRC errors. As to quality. There is nothing but your due diligence in looking for a quality vendor. Read the user reviews and ratings. Don't base your decision on price. Super low prices should be a warning flag and super high prices are not an true indicator of superior quality!

I would suggest that you look into a USB Motherboard Header like this: https://www.amazon.com/dp/B0B936Y2TR/ref=sspa_dk_detail_1?ie=UTF8&pd_rd_i=B0B936Y2TRp13NParams&s=electronics&sp_csd=d2lkZ2V0TmFtZT1zcF9kZXRhaWxfdGhlbWF0aWM&th=1 (This is not a recommendation for this particular unit but the item shows what I mean by the term.) This would put the USB drive inside of the server where it is better protected from several different potential problems-- including some one deciding that they need a USB drive for some other purpose!

If you want changes to stick in Unraid, you have to make them in the /boot/config/smb-extra.conf file. It is called quite late in the smb.conf file, so any changes in that file will update any previous or default samba settings. The easiest place to edit this file is from Settings >>> SMB >>> SMB Extras Since you are playing around with SMB/Samba settings, you might want to have a look at the output of these Linux Samba commands: smbstatus testparm testparm -v netstat They may also work in Android.... EDIT: I seem to recall that there are some command line commands that can stoop and restart the samba process in Linux. Google to find them.

This appeared on the Ask Woody website: Here is the link to the Intel website: https://www.intel.com/content/www/us/en/support/articles/000096448/processors.html

Diagnostics 🙂

It depends on how paranoid you are about data loss from any possible cause. (A random high energy photon could swap a data bit in RAM...) But remember, there are more ways to lose data than a simple file corruption. Think about fires, floods, Lightening, malware, theft of hardware, etc. You should make sure that multiple backups of any irreplaceable data with some of these backups off-site.

I am not sure how you rebuild your Unraid Flash drive when the other one was corrupted. I am also not sure how long your server has used that Flash drive. But you joined the forum back in 2018 so I assume that it might have been that old. One of the problems is that certain Samba settings from those days were carried forward as 'Grandfathered' settings. (Most these 'Grandfathered' had security issues associated with them and MS was banning their use in SMB.) I am going to point you to a thread where there are instructions on how to set things using the current recommended settings. I would suggest that you download the PDF file in the first post in this thread: https://forums.unraid.net/topic/110580-security-is-not-a-dirty-word-unraid-windows-10-smb-setup/ Also make sure that your Win11 computer is setup to be on a Private network. The steps to do are shown below: Steps 1 & 2 will get to the place where you can check. Step 3 shows the setting you want. Use step 4 to make a change if required.