PSteward

Ok I don't know what the hell is going on, now my disk 1 is getting read errors during this rebuild....what is happening?? First disk 2 now disk 1 (both 16tb Seagate). I removed disk 2 again and am copying all data off, and I am copying disk 1 off to another drive too temporarily. This is nuts all this time and copying and copying, why if I never had issues with these drives EVER does this OS have issues? I am copying ALL data from both these drives with ZERO errors but the moment parity check or build is involved they have read/write errors. homeserver-diagnostics-20230512-1920.zip

Hello! I finally completed the parity drive addition and everything was a success. I was curious what happens when I pressed the check parity button after this completion (to see how long it would take) and suddenly a drive got an x and started having errors (newer never had issues before). I don't want to lose any data and am not sure how to proceed from here to get it back into the array (without out an X). Edit: I read a ton and removed/re-added and now it's rebuilding but I don't understand what happened as the drive was fine up until I clicked on parity check (I saw write errors after it was disabled, unfortunately didn't save log before rebooting). There were no physical changes, the drive has been fine for it's 1.5 years of existence, and it was perfect when added to the array, data moved to it, during parity creation. What could cause this by clicking "parity check"?? Please let me know! Thanks, --Phil homeserver-diagnostics-20230512-1832.zip

@Manuel-DG Switch to disk shares, after doing that all my SMB issues were solved (so far). User shares SMB can move individual files but expect constant freezing in Windows explorer when just trying to view folder contents. There is a thread on speeding up things and one the first items it to stop using user shares. Thanks, --Phil

Hello! Is there a way to change the port from 9993 to 9994 (and unbind from 9993)? I tried with a local.conf file inside the container but it didn't work. Thanks! --Phil

Hey Itimpi, Hmmm....that is true (125 MB/s). Not sure why Windows transfer speeds (Teracopy) would have reflected differently, but also on the transfer side internally. Any thoughts for that? Thanks, --Phil

Hello! I just made the leap into Unraid from Windows and am mostly setup (no parity drive just yet as I still have some copying between unassigned and pool drives). I am having some issues that I would like to resolve: 1. I setup an SMB share and when I am connected to the share in Windows (10 PRO) my mouse is constantly alternating between a normal cursor and loading cursor. Never seen this behavior, what would cause it? Connection doesn't seem stable. 2. Drive to drive seems slower, when I was backing up my main drives to other drives to empty them (In Windows) to get them into the pool they would copy 170-200 MB/s internally, and now using MC (in Unraid) moving the data back (No Parity drive yet) after pooling they are around 120-150 MB/s (NTFS to XFS). Notes: I setup link aggregation and this did not improve my copying (shouldn't have as before I just used 1G ethernet in Windows and it was faster but thought I would try.) I am linked at 1G on both ethernet ports (as per Unraid). I am not copying from a drive that is in use. I am not using Parity just yet, again I am copying FROM the server so shouldn't make a difference. Copy TO the server, the same speed (105 MB/s) persists. Any assistance would be appreciated! Thanks, --Phil