Hinatanko

Hi, Software unRAID Version 6.5.3 Hardware Supermicro X10SRi-F Intel Xeon E51650 v4 @ 3.6ghz 64GB ECC Ram Array 18x 8TB NAS HDDs (2 of these are parity) 2x 4TB Desktop HDDs 2x 512GB Samsung 850 Pro Cache Pool Issue After using unRAID for almost 2 years I got my first notification about a drive throwing an error. The disk was put offline and after doing some research I saw some threads mentioning turning off dockers and not writing to the disks. I have done this already. Attached are the syslogs. The drive that was taken offline is disk9. The server uses a Norco 24 bay case. I am using 20 drives currently (18x 8tb and 2x 4tb) 2 of the 8tb are used as parity. I recently ran extended smart reports about 2 weeks ago and did not get any notifications about issues. I checked my disks again and found that another drive had some 199 errors as a warning. Could someone take a look at my logs and let me know if I just need to replace the drive or is their more steps I need to take to fix this issue? Is their any other drives that might look like they need replaced? Thank you nas48-diagnostics-20180807-2224.zip

I have been getting errors off and on for the past few weeks when transferring files from another server onto this unRAID server. I have noticed this happens with any server I have tried to connect with. I only seem to get this error when i have dockers enabled. I notice my deluge daemon has 0.0kbs and SMB cant access files or directories. Sometimes the web ui is slow and unresponsive too. Sometimes my file transfer eventually gets a network error in teracopy. Generally when this error happens I dont get much in the logs. But I noticed this time when i was transferring files, running dockers (mainly deluge and plex) and preclearing 2 new drives I got a lot of errors in the logs. I also noticed one of the drives I was preclearing disappearing from unassigned devices. This is just a snippet of my errors. Any help at all is appreciated. Jun 21 00:29:59 NAS48 kernel: Buffer I/O error on dev sds, logical block 476760372, lost async page write Jun 21 00:29:59 NAS48 kernel: Buffer I/O error on dev sds, logical block 476760373, lost async page write Jun 21 00:29:59 NAS48 kernel: Buffer I/O error on dev sds, logical block 476760374, lost async page write Jun 21 00:29:59 NAS48 kernel: Buffer I/O error on dev sds, logical block 476760375, lost async page write Jun 21 00:29:59 NAS48 kernel: Buffer I/O error on dev sds, logical block 476760376, lost async page write Jun 21 00:29:59 NAS48 kernel: Buffer I/O error on dev sds, logical block 476760377, lost async page write Jun 21 00:29:59 NAS48 kernel: Buffer I/O error on dev sds, logical block 476760378, lost async page write Jun 21 00:29:59 NAS48 kernel: Buffer I/O error on dev sds, logical block 476760379, lost async page write Jun 21 00:29:59 NAS48 kernel: Buffer I/O error on dev sds, logical block 476760380, lost async page write Jun 21 00:29:59 NAS48 kernel: Buffer I/O error on dev sds, logical block 476760381, lost async page write Jun 21 00:30:04 NAS48 kernel: buffer_io_error: 15468 callbacks suppressed Jun 21 00:30:04 NAS48 kernel: Buffer I/O error on dev sds, logical block 476780239, lost async page write Jun 21 00:30:04 NAS48 kernel: Buffer I/O error on dev sds, logical block 476780240, lost async page write Jun 21 00:30:04 NAS48 kernel: Buffer I/O error on dev sds, logical block 476780241, lost async page write Jun 21 00:30:04 NAS48 kernel: Buffer I/O error on dev sds, logical block 476780242, lost async page write Jun 21 00:30:04 NAS48 kernel: Buffer I/O error on dev sds, logical block 476780243, lost async page write Jun 21 00:30:04 NAS48 kernel: Buffer I/O error on dev sds, logical block 476780244, lost async page write Jun 21 00:30:04 NAS48 kernel: Buffer I/O error on dev sds, logical block 476780245, lost async page write Jun 21 00:30:04 NAS48 kernel: Buffer I/O error on dev sds, logical block 476780246, lost async page write Jun 21 00:30:04 NAS48 kernel: Buffer I/O error on dev sds, logical block 476780247, lost async page write Jun 21 00:30:04 NAS48 kernel: Buffer I/O error on dev sds, logical block 476780248, lost async page write Jun 21 00:30:10 NAS48 kernel: buffer_io_error: 12031 callbacks suppressed Jun 21 00:30:10 NAS48 kernel: Buffer I/O error on dev sds, logical block 476794096, lost async page write Jun 21 00:30:10 NAS48 kernel: Buffer I/O error on dev sds, logical block 476794097, lost async page write Jun 21 00:30:10 NAS48 kernel: Buffer I/O error on dev sds, logical block 476794098, lost async page write Jun 21 00:30:10 NAS48 kernel: Buffer I/O error on dev sds, logical block 476794099, lost async page write Jun 21 00:30:10 NAS48 kernel: Buffer I/O error on dev sds, logical block 476794100, lost async page write Jun 21 00:30:10 NAS48 kernel: Buffer I/O error on dev sds, logical block 476794101, lost async page write Jun 21 00:30:10 NAS48 kernel: Buffer I/O error on dev sds, logical block 476794102, lost async page write Jun 21 00:30:10 NAS48 kernel: Buffer I/O error on dev sds, logical block 476794103, lost async page write Jun 21 00:30:10 NAS48 kernel: Buffer I/O error on dev sds, logical block 476794104, lost async page write Jun 21 00:30:10 NAS48 kernel: Buffer I/O error on dev sds, logical block 476794105, lost async page write Jun 21 00:30:23 NAS48 kernel: buffer_io_error: 1190 callbacks suppressed Jun 21 00:30:23 NAS48 kernel: Buffer I/O error on dev sds, logical block 476797167, lost async page write Jun 21 00:30:23 NAS48 kernel: Buffer I/O error on dev sds, logical block 476797168, lost async page write Jun 21 00:30:23 NAS48 kernel: Buffer I/O error on dev sds, logical block 476797169, lost async page write Jun 21 00:30:23 NAS48 kernel: Buffer I/O error on dev sds, logical block 476797170, lost async page write Jun 21 00:30:23 NAS48 kernel: Buffer I/O error on dev sds, logical block 476797171, lost async page write Jun 21 00:30:23 NAS48 kernel: Buffer I/O error on dev sds, logical block 476797172, lost async page write Jun 21 00:30:23 NAS48 kernel: Buffer I/O error on dev sds, logical block 476797173, lost async page write Jun 21 00:30:23 NAS48 kernel: Buffer I/O error on dev sds, logical block 476797174, lost async page write Jun 21 00:30:23 NAS48 kernel: Buffer I/O error on dev sds, logical block 476797175, lost async page write Jun 21 00:30:23 NAS48 kernel: Buffer I/O error on dev sds, logical block 476797176, lost async page write

Currently it is running a parity sync/data-rebuild. I read about running a non-correcting parity check. I am not sure if thats the best way to do the parity check after this or not. But I will definitely run one after it is done tomorrow.

I ended up removing 4 of the 6 newly HDDs that had any SMART errors. The two I kept had no SMART errors and passed extend tests without a problem. I referred this page for removing these https://wiki.lime-technology.com/Shrink_array and rebuilt a new config. I don't appear to have lost any data and everything looks okay. However, the two drives that remained are disk 8 and disk 10. In my Main tab I am seeing Party 1 & 2, Drive 1 - 6 and Drive 8 and Drive 10. No Drive 7 and 9 are being shown. I want to make sure this is the way it should be. I also changed the global share settings (as mentioned in the guide) to Include all the disks I would be retaining (disks 1-6, 8 and 10). Should I keep this way for the future? If I add a new HDD later on should I change this? Thanks for the help!

Software unRAID Version 6.3.5 Dockers (all running) binhex-delugevpn glances Handbrake jackett JDownloader2 Krusader Netdata ombi openvpn-as organizr Plex plexpy radarr sonarr transmission VMs Windows 10 (not running) Hardware Supermicro X10SRi-F Intel Xeon E51650 v4 @ 3.6ghz 64GB ECC Ram Array 8x 8TB NAS HDDs (2 of these are parity) 1x 3TB Desktop HDD 5x 4TB Desktop HDDs 2x 512GB Samsung 850 Pro Cache Pool Issue When copying files to this unRAID server via SMB after a few minutes the following happens: The web GUI becomes unresponsive Teracopy reports a network error has occurred Dockers no longer work (e.g I lose connection to my deluge deamon and cant connect via thin client or web UI) Browsing files in Windows Explorer through Windows 10 stops and freezes When I stop the transfer through Teracopy everything works again within 10-15 seconds. I have tried different files to see if it somehow was related to a particular file but it hangs on different files and not just the same file. I have tested this out 4 times over the last 2 days and it just happened twice in the past hour when trying to copy over files from a different server. With this exact same setup a couple of months ago I was able to move 11TB of data over via the network with no issues with packets being loss or network errors according to Teracopy. I have posted the diagnostics logs. Let me know if you need any additional information. Thanks! nas48-diagnostics-20170612-1252.zip

I ran short and extended SMART tests on all of the new drives I added and they all passed with no errors. Would it be safe to assume these drives are okay to keep? Also I posted a screenshot of the stats page for disk usage. When will the newer drives start to get used by unRAID?

All drives including the newer 3T and 4T drives have been precleared. Nothing on the server is irreplaceable. Do you recommend I bother with the extended SMART tests on the older drives at this point? 2 of these drives don't have any warning when I go into the drive and check for SMART errors. Should these be replaced as well? You mentioned just removing the drives and doing a new config. Is their a video or post with instructions on how to do this step by step?

Thanks for looking at my logs! I assume the drives in question are the newer drives I added and not the 8TB drives? Is their a faster or better way of running extended SMART tests then going to the drive and clicking run extended self test? You mentioned it is difficult to remove drives after they had been added. Would it be easier to replace them with new drives?

Here is the file. Thanks! nas48-diagnostics-20170605-1140.zip

Thanks for the help! Some of the drives I added had 187 errors after preclear, but after looking into other threads it seemed like they were okay to keep as long as they didn't continue to increase. Is this correct? Going forward I plan to only use brand new NAS drives and only after I need more space. I just wanted to these drives out of my main PC.

Thanks for the help!

So the way I understand it the reason it went back to the 8TB drives is because it looks the amount of data rather than the percentage free? If so that makes sense. I checked before posting to make sure the two main shares I have been using are both high water and they are set to high water. I never thought about waiting to the drives until they were needed. In the future when would you suggest I add more drives? When all drives are at 50%? 70%? Thanks for the info!

I have an 8TB Desktop Archive drive from Seagate (the ones that are suppose to be slow on write I believe). I am just wondering if adding this is a bad idea and will hurt performance of the array. I already have 8x 8TB NAS HDDs, 1x 3TB Desktop HDD and 6x 4TB Desktop HDDs in my array. I also have 2 512GB Samsung 850 Evo Pro SSDs for cache drives. I generally would have no problem adding the drive but wanted to see anyone had experience with this drive and if it has caused any issues with performance.

I have had my unRAID server running smoothly for 4 months so far. I initially added 8 NAS HDDs (2 for parity). Everything went well so I went ahead and added some older desktop drives 1x 3TB and 6x 4TB HDDs. They have been in the array for about a month. My drives have been filling up to 50% and then going to the next drive which is fine. When the server filled up the last 8TB hard drive it went back to the first 8TB and started filling it up and ignoring the smaller hard drives. Below is a screenshot of my array looks like: I am sure this is something with a setting but I can't find it. Any help is greatly appreciated! Thanks!

Thats good to know! Thanks for the info!