• Posts

  • Joined

  • Last visited


  • Gender

wsume99's Achievements


Enthusiast (6/14)



  1. I looked around this morning trying to solve the issue. I ran pwmconfig and the array fan can be controlled but there are no devices in sys/class/hwmon/hwmon1/device/. It appears something has changed in the new version and I can't figure it out yet. I reverted back to 6.8.3 and everything works correctly. More research is in my future.
  2. Today I upgraded to the latest unraid release (6.9.2). I also added a password to the root user account. Now the user script that I have controlling the array fan stopped working. I copied the output from the script below when it runs. Any recommendations on where to start? Script location: /tmp/user.scripts/tmpScripts/Fan Speed/script Note that closing this window will abort the execution of this script Disk /dev/sdc current temp is 0 Disk /dev/sdd current temp is 0 Disk /dev/sde current temp is 0 Disk /dev/sdf current temp is 0 Disk /dev/sdg current temp is 0 Disk /dev/sdh current temp is 27 /tmp/user.scripts/tmpScripts/Fan Speed/script: line 93: /sys/class/hwmon/hwmon1/device/pwm2_enable: Permission denied cat: /sys/class/hwmon/hwmon1/device/pwm2: No such file or directory cat: /sys/class/hwmon/hwmon1/device/fan2_input: No such file or directory /tmp/user.scripts/tmpScripts/Fan Speed/script: line 99: *100: syntax error: operand expected (error token is "*100") /tmp/user.scripts/tmpScripts/Fan Speed/script: line 104: [: : integer expression expected /tmp/user.scripts/tmpScripts/Fan Speed/script: line 106: [: : integer expression expected /tmp/user.scripts/tmpScripts/Fan Speed/script: line 128: [: : integer expression expected DONE
  3. Thanks for the reply. The script was working just fine all I needed was to get it running in cron. I was clicking Run In Background instead of Apply. Once I used Apply it was loaded into Cron and persistent across a reboot. Everything is working just like I need now. Thank you
  4. I have a working script that I'm now trying to run every 2 minutes via cron. I selected the Custom option from the scheduled drop down menu and enter */2 * * * * as the Custom Cron Schedule value and then click on Run In Background. A pop-up window opens telling me the script is running in the background which I then close. I have modified my script temporarily to write entries into the log file every time it runs. I know the script runs once because I see the output in the log file but it but does not run again. My settings do not remain after reboot or even if I navigate away from the User Scripts management page and then come back. I'm not sure how to fix this issue. What am I doing wrong here??
  5. Just upgraded to 6.8.1 and for whatever reason the code in my go file that loaded my custom array fan speed script into cron is now broken. Searching for cron help lead me to User Scripts, which I already had installed but was not using as a way to schedule my fan speed script. I'm trying to run a script on a custom cron schedule to have the script run every 2 minutes. I want this script to run automatically whenever the server is powered up and regardless of array state. A quick search of the forums didn't catch any posts on how to enter a custom cron schedule for a script. Do I select Custom from the schedule menu then enter "2 * * * *" into the Custom Cron Schedule box and then select either Run Script or Run Script in Background?
  6. My original post: And the original reply: Resurrecting this problem. I've been fighting issues with some new hardware and after a lot of work I'm back to my old MB/CPU to try this again. I have tried both remedies (rsync -rltgoDv and rsync -av --no-perms) and neither prevent the errors I outlined above. Any more suggestions?
  7. If I understand what you are suggesting correctly I have already done this. The controller on the motherboard is different than the controller on the pci-e card. I have the same problem when I'm connected to either controller.
  8. I found this post which discusses problems with UASP which affects portable USB drive operations. Is this what you were referring to?
  9. I have not. I was searching last night about USB3 problems in linux and there are a lot of posts on various distros and hardware where users had problems similar to mine. It appears that the kernel is very buggy with USB3 devices. Thanks for the suggestion I'll look into it.
  10. My problem - when I try to read from or write to a portable HDD over USB3 I get random hangups in the transfer. This is happening on both the on-board ports as well as a pcie USB expansion card. Background: I decided to do a hardware refresh on my server. I purchased a Supermicro X10SAE motherboard and an e3-1226v3 off ebay, both items were used. Everything else RAM, PSU, SATA cables, fans, etc were all existing hardware that I had and was not experiencing any issues with. As part of this refresh I also purchased 2 x 8TB HDDs to replace a 2TB and 3TB drive that were already in my array. After I got the hardware up and running I ran MS prime for 24 hours with no errors. I then installed the two new 8TB drives and a spare 2TB drive I had into the server and ran simultaneous preclears on all three drives until I had cleared both new drives 3 times. No issues were noted at all while running the preclears. I then moved the drives from my existing server into my new server. Three of the six drives in my array were still on RFS so I used the two new 8TB drives to go through the process of converting the three RFS drives over to XFS. Once that was complete I re-organized a pretty disorganized photography library. I mention all this because in order to do all of these things I exclusively used rsync via the terminal to move a ton of files around between array drives. In total I'd estimate that I performed around 15TB of total rsync transfers between array drives. I had no issues at all during this time. Once I had finished all of this on the server I then tried to add some files from a HFS+ formatted drive onto the array. That is when the problems started. I was transferring the files using rsync and the operation would just hang. The progress on terminal would just stop and the disk throughput on the main GUI would drop to zero. Nothing was reported in the log file. I took that same portable HDD, plugged it into a macbook and transferred about 500GB of files onto my array over the network using rsync from the mac with no issues. I thought it might be a problem with the HFS+ formatting but maybe it wasn't, see the next paragraph. At that point I now had all of my photo library organization done and I wanted to backup some files on my array to a different portable HDD. I formatted this HDD using exFAT. Using rsync I started copying files onto the portable HDD but the same thing happened - random hangs, I/O drops to zero on GUI, no errors in logfile. Again this happens with both onboard USB3 as well as the pcie USB expansion card. I plugged that same HDD into a windows machine and wrote ~250GB of files to it with no issues. So I am now scratching my head. I'm thinking it has to be one of the following possible issues: 1) Bad motherboard (something in the PCH)? 2) Driver or kernel issue with USB3? I doubt this is the issue because the pcie expansion card was in my old server and worked without issues for large file transfers just prior to the start of my hardware refresh. I'm eliminating the CPU and RAM because how could they only have problems when performing USB3 transfers but not SATA transfers?? Maybe I'm wrong here. My plan is to swap the array back into my old server (different MB, CPU, RAM, PSU, and case) and see if the problem goes away. After all that "background" I guess I'm just looking for any other ideas that the community might have as to how to isolate the culprit. Am I missing something? Any feedback would be greatly appreciated.
  11. I am using UD to mount and share a 4TB external drive on my server. I am trying to rsync files from my array to the drive. Here is the command to initiate the transfer: rsync -av /mnt/user/Photography/2005/ /mnt/disks/EasyStore_4/2005/ When the rsync finishes it displays the following message: rsync error: some files/attrs were not transferred (see previous errors) (code 23) at main.c(1189) [sender=3.1.3] The all are of the following type: rsync: chown "/mnt/disks/EasyStore_4/2005/12-25-2005/.12-25-05(2).JPG.nkTWa8" failed: Operation not permitted (1) I compared the source and destination paths after the operation and it looks like all the files were transferred - the count of files and folders along with total size are all equal. I searched and found a post where the discussion was about how the volume being written to was mounted and the root user wouldn't have permission to set ownership on a that volume. The suggested remedy was to run rsync -rltgoDv instead of the -a option. Would this correct my issue or is there a better way to correct this so I can run rsync without any errors. Having any error at the end of an rsync is not what I'd prefer to have.
  12. After more searching it looks like this is actually a known issue with the linux module that handles the hfs+ filesystem. Rsync is hanging due to a problem reading the hfs+ filesystem. I guess I just got lucky before when using this drive. Regardless, I'm switching to exFAT formatting on all my portable hard drives now since I have windows, linux and mac machines. Hopefully that will fix the problem.
  13. I'm beginning to think this issue is being caused by something on the server. The files on this drive were all written from a mac laptop. I plugged the HDD into the laptop and the laptop to ethernet and then rsynced the files from a terminal on the mac. I ran overnight without any problems. Of course it is slower copying over the network as compared to copying files onto the array from a device connected directly to the server. However since the HDD can be read by the mac without issues that leads me to believe the issue is on my server. Now if I can just figure out what the problem is. 😂
  14. I running v6.6.6 and am trying to copy ~600GB of data (DSLR photos) off a portable USB3 HDD onto my array. I'm using a rsync -avPX command via a terminal session to copy files from the drive (UD mounted) into a duplicate folder on my array. I have had the drive plugged into both USB3 and USB2 ports on the MB as well as a USB3 pcie card that I previously used in my old server. The problem persists no matter how the drive is connected. The transfer hangs on random files. If I close the terminal and open another and re-initiate the rsync it will start copying again and then not to long afterwards it will get stuck again. I used this same drive several weeks ago to copy nearly 1TB of files onto my old server using the same USB3 pcie card with no problems. I've searched the forums and have not yet found a solution or even anyone reporting a similar issue. I'm still trying to determine if this is an issue with my portable HDD or something on the server side. Any guidance would be appreciated. Is there a way to run a smart report on the portable HDD thru unraid?
  15. I needed more drive slots so I bought a new case. I figured why not just upgrade my MB and CPU while I'm at it. I had a spare stuff lying around to make a second server so that is what I'm in the middle of ATM. I bought a used supermicro X10SAE motherboard and an e3-1226 v3 CPU for $141 total. I am reusing a functional PSU and RAM along with misc fans, etc. I want to stress my new hardware to make sure everything is functional. Based on my research my plan is to complete the following: 1) 24 hr memtest (currently underway) 2) 4 hr prime CPU stress 3) I have 2 x 8TB HDDs that are new and one old 2TB HDD I plan to install and run a series of simultaneous preclears on. I plan to move them around on the on-board SATA ports between passes. Anything else I should do to make sure my new setup is good to go?