dlandon

Community Developer
  • Posts

    10157
  • Joined

  • Last visited

  • Days Won

    19

Everything posted by dlandon

  1. Thanks for the info - very helpful. I can spend a little time with this and see if I can figure it out. I think I understand what you are saying. I got very confused because it looks like Dynamix puts its own version of rc.unRAID in the /etc/rc.d. I think that this can potentially cause some issues of who gets there fist and installs their version. I'll start with a bare metal unRAID and see if I can figure out what is happening. I notice that the official version is still 1.02 hosted at Google Code. Is this being maintained/updated there any longer?
  2. Yes it is but powerdown appears to be replacing it. I think I am wrong about the rcdstock file. It is installed with the powerdown package. I've been working on this too long and I've gotten myself very confused about the stock and powerdown rc.unRAID. I guess I need to let the author of powerdown take a look.
  3. I don't think this is a Tom problem. I have found a problem in the powerdown package.
  4. I've narrowed it down to rc.unRAID in the powerdown package. The 'stop' operation appears to have some issues. I can get the system to hang up by issuing "rc.unRAID stop" in a telnet session. I have found the problem. There is a powerdown file missing from the /etc/rc.d directory. The file 'rcdstock' is missing. If I copy that file to the /etc/rc.d/ directory, the problem is solved. Can the author please update the package with this fix?
  5. I've narrowed it down to rc.unRAID in the powerdown package. The 'stop' operation appears to have some issues. I can get the system to hang up by issuing "rc.unRAID stop" in a telnet session.
  6. Unfortunately there is no standard in motherboards for temperature monitoring. The temperatures are dependent on the chip set used to monitor the temperatures and each chip set requires a unique driver. There is no way to write a plugin for temperature monitoring and cover every motherboard. It has to be done manually.
  7. I've been trying to keep up with all the v6 posts. I haven't seen anything about this issue so far. I apologize if this is a duplicate. Boot selection "Xen/unRAID OS Safe Mode (no plugins)" installs plugins.
  8. The drive I am mounting is formatted ntfs. I did not load the ntfs-3g driver, so the unRAID read only driver is the one being used. I haven't tried this with v6 Beta3. I'll give that a go to see if anything has changed. EDIT: Still happening.
  9. Can anyone offer assistance here? This will be an issue for anyone mounting a drive outside unRAID.
  10. Make these changes: rsync -a -r --update /mnt/user/Pictures\ Backup/Family\ Photos/ $MOUNTPOINT/familypics 2>&1 >> $LOGFILE rsync -a -r --update /mnt/user/Pictures\ Backup/Scouts\ photos/ $MOUNTPOINT/scoutpics 2>&1 >> $LOGFILE The space characters must be preceeded with the '\' character.
  11. Blank lines for readability are fine. They will be ignored. rsync error: some files/attrs were not transferred (see previous errors) (code 23) at main.c(1042) [sender=3.0.7] ntfs-3g driver does not handle extended file attributes. rsync: change_dir "/mnt/user/Pictures_Backup/Scouts_photos" failed: No such file or directory (2) Do a telnet session to your server and see if you can ls the directory. i.e. ls /mnt/user/Pictures_Backup/Scouts_photos Is it possibly Scouts_Photos? rsync error: some files/attrs were not transferred (see previous errors) (code 23) at main.c(1042) [sender=3.0.7] ntfs-3g driver does not handle extended file attributes. rsync: change_dir "/mnt/user/Pictures_Backup/Family_Photos" failed: No such file or directory (2) Do a telnet session to your server and see if you can ls the directory. i.e. ls /mnt/user/Pictures_Backup/Family_Photos
  12. In looking at your code once more I see a syntax issue. if [ ! -d $MOUNTPOINT/flash ] then mkdir $MOUNTPOINT/flash should be if [ ! -d $MOUNTPOINT/flash ] then mkdir $MOUNTPOINT/flash fi the syntax for the if statement is: if [...] then fi The missing closing 'fi' causing your issues. Each 'if' statement must be closed with a 'fi'.
  13. It is mounted because the 'M' icon is highlighted in SNAP.
  14. Take smaller steps to get this working. Take the basic hotPlugAfterEvent.sh script and rename the "Lexar" to "External_1" and add logging lines that log the fact that the case "External_1" has been executed. Then hot plug the drive and see what is logged. i.e. 'External_1') logger External_1 hot plug event -t$PROG_NAME echo "External_1 hot plug event" >> $LOGFILE ;; esac If that works then add your other script lines in small pieces to get the complete script working. If that doesn't work, try a drive name without the underscore - i.e. External1.
  15. It's cleaner to use $MOUNTPOINT for all references to the drive. e.g. if [ ! -d $MOUNTPOINT/flash ] then mkdir $MOUNTPOINT/flash I'm not a Linux script guru, but I think this should be the proper syntax: ;; esac I'm don't think Linux likes white space before the two semi-colons. If you still have the error, comment out all the lines in the case statement and then fix the syntax error if it still occurs. If it doesn't, then uncomment pieces at a time and find which line is causing the error.
  16. Read the "Hot Plug Operation" in this post: http://lime-technology.com/forum/index.php?topic=29519.msg264817#msg264817 It will give you some direction on how to set up the script to do your copies.
  17. I'm running everything except DNS Server and S3 Sleep. So far so good.
  18. I get a file not found error when executing the webgui installplg. dynaminx-webGui-2.1.0-x86_64-1.txz file not found.
  19. Do you have a picture Sent from my iPhone using Tapatalk It's IE9 on one of my computers. Doesn't happen with IE10.
  20. Why does my server name show "Tower • 192.168.1.3"?
  21. This issue does not relate to unRAID 5.0, but I don't know where else to post it. I am working on getting SNAP to work on unRAID 6.0 and I'm having a problem with powerdown shutting down properly. I installed unRAID 6.0 and the powerdown 1.04 package and nothing else. I can create a hangup on shutdown by mounting and unmounting an sata disk outside of the array. I execute the following in a telnet session and then do a normal shutdown using the WebGUI and powerdown hangs. mkdir -m 777 -p /mnt/disk/Test mount -r -o umask=111,dmask=000 -t ntfs /dev/disk/by-id/ata-ST9500325AS_S2W8BSWG-part1 /mnt/disk/Test umount /mnt/disk/Test rmdir /mnt/disk/Test Let me know if you see anything wrong with how I am mounting the drive, or if there is further information I can provide. I can't get a log when the situation occurs because the system hangs and is no longer accessible. Any help would be appreciated.
  22. Mine is on 24/7 and is never turned off except to do maintenance like changing drives. It's out of the way in my basement so I don't hear any noise. Just the way I like it - out of the way so I don't even know it's running, but available when needed.
  23. As I said before - if it doesn't work for you, use the alternatives - there is no need to keep telling/asking me to change the current design. Bonienl and others offer their services with no compensation to help enhance the unRaid product. Based on the professionalism I see in Dynamix, I'd say bonienl knows what he is doing and is doing an excellent job. Continuing to hammer him on a feature you may not appreciate does nothing to further the cause of enhancing unRaid. As he said, if you don't appreciate the features he has built into Dynamix, find an alternative that does things the way you want. Bonienl - keep up the good work. Dynamix is an excellent enhancement to unRaid and I like it just fine the way it is.