capler

I can't figure out how to do LAN sync either. Anyone?

is there a setting in the simple features web ui to email me when the disks are full? I have Critical and Warning percentages both set to default values in "Stats Settings", but I don't seem to receive any notifications/email when crossing that threshold

YES! I got AirPrint working to my Samsung SCX-4623FW - printing straight to my printer (via unraid) from my iPhone and iPad mikezs - thanks for pointing me in the right place. Here's what I needed to get my printer working, but the changes are likely the same for all the other printer models that are supported in Samsung's Unified Linux Drivers: CLP*, CLX*, MFP*, ML*, SCX*, SF531P - I've posted a full list here: http://pastebin.com/7jQmEpLA The main differences to what's already been posted above are: [*]uses drivers found in Samsung's unified drivers so no need to use foomatic or to build your own PPD [*]you'll need some different libraries, mentioned below. You can download the Unified Linux Drivers from Samsung's website, and then extract it using: tar -zxvf UnifiedLinuxDriver_0.95.tar.gz The files you'll need in UnifiedLinuxDriver_0.95.tar.gz are your printer's ppd driver file (mine's called scx4623fw.ppd) and the filters. Place all the filters from the extracted Samsung's Unified Printer Drivers (/cdroot/Linux/x86_64/at_root/usr/lib64/cups/filter/) in /boot/config/cups/filter/ Also, place your PPD printer driver (scx4623fw.ppd in my case) in /boot/config/cups/ppd - you'll find the drivers in Samsung's Unified Printer Drivers mentioned above: Place the cupsd.conf file (downloadable from one of the posts above) in /boot/config/cups/ Note: in cupsd.conf you'll probably need to add this one line below just under "Port 631" to print from an iDevice, otherwise you'll get an error. If you make changes to this .conf file whilst CUPS is running, use "/etc/rc.d/rc.cups restart" for the changes to take effect. ServerAlias * Now for the 1st time installation: cd /boot/packages wget http://slackware.cs.utah.edu/pub/slackware/slackware-13.1/slackware/l/libtiff-3.9.2-i486-1.txz wget http://slackware.cs.utah.edu/pub/slackware/slackware-13.1/slackware/l/libpng-1.4.2-i486-1.txz wget http://slackware.cs.utah.edu/pub/slackware/slackware-13.1/slackware/l/libjpeg-v8a-i486-1.txz wget http://slackware.cs.utah.edu/pub/slackware/slackware-13.0/slackware/l/libjpeg-6b-i486-5.txz wget http://slackware.cs.utah.edu/pub/slackware/slackware-13.1/slackware/x/fontconfig-2.8.0-i486-1.txz wget http://slackware.cs.utah.edu/pub/slackware/slackware-13.1/slackware/l/freetype-2.3.12-i486-1.txz wget http://slackware.cs.utah.edu/pub/slackware/slackware-13.1/slackware/a/cups-1.4.3-i486-3.txz wget http://slackware.cs.utah.edu/pub/slackware/slackware-13.1/slackware/l/poppler-0.12.4-i486-1.txz #need this to get pdftops and pstops working wget http://slackware.cs.utah.edu/pub/slackware/slackware-13.1/slackware/l/lcms-1.19-i486-1.txz wget http://slackware.cs.utah.edu/pub/slackware/slackware-13.1/slackware/ap/ghostscript-8.71-i486-2.txz wget http://slackware.cs.utah.edu/pub/slackware/slackware-13.1/slackware/l/pycups-1.9.48-i486-1.txz installpkg libtiff-3.9.2-i486-1.txz installpkg libpng-1.4.2-i486-1.txz installpkg libjpeg-v8a-i486-1.txz installpkg libjpeg-6b-i486-5.txz installpkg fontconfig-2.8.0-i486-1.txz installpkg freetype-2.3.12-i486-1.txz installpkg poppler-0.12.4-i486-1.txz installpkg lcms-1.19-i486-1.txz installpkg ghostscript-8.71-i486-2.txz installpkg cups-1.4.3-i486-3.txz # Install pycups - Only needed this one time for airprint-generate.py installpkg pycups-1.9.48-i486-1.txz [ ! -d "/etc/cups" ] && mkdir /etc/cups [ ! -d "/etc/cups/ppd" ] && mkdir /etc/cups/ppd [ ! -d "/usr/lib/cups/filter" ] && mkdir /usr/lib/cups/filter [ ! -d "/usr/share/cups/model/samsung" ] && mkdir /usr/share/cups/model/samsung cp /boot/config/cups/ppd/* /usr/share/cups/model/samsung/ #not strictly necessary #I needed to call it 'Samsung_SCX-4623FW' because I named it as that in CUPS's webUI admin, and hence it's defined as this in printers.conf as 'Samsung_SCX-4623FW' cp /boot/config/cups/ppd/scx4623fw.ppd /etc/cups/ppd/Samsung_SCX-4623FW.ppd rm /etc/cups/cupsd.conf ln -sf /boot/config/cups/cupsd.conf /etc/cups/cupsd.conf cp /boot/config/cups/filter/* /usr/lib/cups/filter/ chmod +x /etc/rc.d/rc.cups /etc/rc.d/rc.cups start go to http://tower:631/admin in the browser to see if CUPS is now working, and add & configure your printer via the webUI admin, then... #create a backup copy of the printer config for next time... cp /etc/cups/printers.conf /boot/config/cups/ Generate the avahi service scripts for your printer that points to the CUPS printer. See mikezs's post above regarding the airprint-generate.py python script that does this automatically. You'll need to install python via unmenu just to run this script the one time - you don't need python or airprint-generate.py after it's generated the .service file in /boot/config/cups/service/ cp /boot/config/cups/service/*.service /etc/avahi/services/ Now it should all be working. Make sure you get the "Test Print" function in CUPS's admin console working (http://tower.local:631) before trying to print from your iDevice. If the test print doesn't work, use "cat /var/log/cups/error_log" to check for detailed errors. Finally, if it's all working & printing from your iPhone, for persistance on the next reboot place the following in the Go script... ####################### # Printer START ####################### cd /boot/packages installpkg libtiff-3.9.2-i486-1.txz installpkg libpng-1.4.2-i486-1.txz installpkg libjpeg-v8a-i486-1.txz installpkg libjpeg-6b-i486-5.txz installpkg fontconfig-2.8.0-i486-1.txz installpkg freetype-2.3.12-i486-1.txz installpkg poppler-0.12.4-i486-1.txz installpkg lcms-1.19-i486-1.txz installpkg ghostscript-8.71-i486-2.txz installpkg cups-1.4.3-i486-3.txz [ ! -d "/etc/cups" ] && mkdir /etc/cups [ ! -d "/etc/cups/ppd" ] && mkdir /etc/cups/ppd [ ! -d "/usr/lib/cups/filter" ] && mkdir /usr/lib/cups/filter [ ! -d "/usr/share/cups/model/samsung" ] && mkdir /usr/share/cups/model/samsung cp /boot/config/cups/ppd/* /usr/share/cups/model/samsung/ #not strictly necessary #need to call it 'Samsung_SCX-4623FW' because it's defined in printers.conf as 'Samsung_SCX-4623FW' cp /boot/config/cups/ppd/scx4623fw.ppd /etc/cups/ppd/Samsung_SCX-4623FW.ppd rm /etc/cups/cupsd.conf ln -sf /boot/config/cups/cupsd.conf /etc/cups/cupsd.conf rm /etc/cups/printers.conf ln -sf /boot/config/cups/printers.conf /etc/cups/printers.conf cp /boot/config/cups/filter/* /usr/lib/cups/filter/ chmod +x /etc/rc.d/rc.cups /etc/rc.d/rc.cups start cp /boot/config/cups/service/*.service /etc/avahi/services/ ####################### # Printer END #######################

unfortunately I get a 404 following that link. Looks like only Samsung printers with an "ML" model number are supported. Are there any solutions for other samsung printers? Mine is a Samsung scx-4623fw

not sure if this helps you, but I originally had the same issue when doing a Reboot. However, after I completely shutdown my server, off at the mains & restarted the NIC set itself to Gigabit. Don't know why, but it worked for me.

All working well here thanks. Gigabit and all. Network card: PCI Tenda Gigabit NIC TEL9901G which utilises a Realtek r8169 chip

also, just realised that this works better: -newer $HOME/filelist_lastBackup.txt , -cnewer $HOME/filelist_lastBackup.txt

Thanks WeeboTech - that captures the renamed files. Shame about deletes never getting translated, but that's not such a big concern for me - at least all the data is backed up in case of emergency.

Ok, all seems to be going hunky dory with this approach, aside from one problem I'm experiencing: If I rename a file (after it has been backed up) the change does not get reflected on the backup - because this method only backs up new/changed files, and renaming a file does not modify the file's modification date. Any ideas how to ensure my backup filenames truly reflect the source?

Thanks that really helped me. Think I've got it working now... #!/bin/bash # filelist_allBackups.txt contains log of all backups # filelist_lastBackup.txt contains log of most recent backup # note: to reset the backup & recopy all files in SOURCE locations irrespective of when they were updated, use: touch -t 197001010000 $HOME/filelist_lastBackup.txt date=`date "+%Y-%m-%d_%H-%M-%S"` LOG=/var/log/rsyncBackup.log HOME=/boot/rsyncBackup SOURCEROOT="/mnt/user/" SOURCE1="Media/Pictures" SOURCE2="Media/Videos" SOURCE3="Time Machine" SOURCE4="Backup" EXTERNALDISK=/mnt/disk/ExternalBackupDisk EXTERNALDISKPATH=$EXTERNALDISK/BACKUPS/Location1 BACKUPDESTINATION=$EXTERNALDISKPATH/rsyncBackup # check that the expected path exists... if [ -d $EXTERNALDISKPATH ] then echo "$date STARTING" >> $LOG echo "$date Looking for changed files since last sync..." >> $LOG # look for changed files since last sync (i.e since the modification time of filelist_lastBackup.txt) cd "$SOURCEROOT" find "$SOURCE1" \ "$SOURCE2" \ "$SOURCE3" \ "$SOURCE4" \ -newer $HOME/filelist_lastBackup.txt -print > $EXTERNALDISKPATH/filelist_lastBackup.txt # create local log of filelist echo "" >> $HOME/filelist_allBackups.txt echo $date >> $HOME/filelist_allBackups.txt date=`date "+%Y-%m-%d_%H-%M-%S"` echo "$date done" >> $LOG echo "$date Copying files..." >> $LOG # copy changed files across... CMD=`rsync -aP \ --exclude-from=$HOME/exclude.txt \ --files-from=$EXTERNALDISKPATH/filelist_lastBackup.txt \ "$SOURCEROOT" $BACKUPDESTINATION 2>&1` # error capture & report logging... if [ $? != 0 ] then echo "BACKUP ERROR: problem syncing $SOURCEROOT to $BACKUPDESTINATION" echo "BACKUP ERROR: problem syncing $SOURCEROOT to $BACKUPDESTINATION" >> $LOG echo $CMD >> $LOG echo "" >> $LOG exit 1 else # on successful copy update reference file... echo "SUCCESS: syncing $SOURCEROOT to $BACKUPDESTINATION" echo "SUCCESS: syncing $SOURCEROOT to $BACKUPDESTINATION" >> $LOG cp -p $EXTERNALDISKPATH/filelist_lastBackup.txt $HOME/filelist_lastBackup.txt cat $HOME/filelist_lastBackup.txt >> $HOME/filelist_allBackups.txt echo $CMD fi # place filelist in correct folder (one level deeper)... mv $EXTERNALDISKPATH/filelist_lastBackup.txt $BACKUPDESTINATION/filelist_lastBackup.txt date=`date "+%Y-%m-%d_%H-%M-%S"` echo "$date FINISHED" >> $LOG echo "" >> $LOG else echo "$date Destination Path does not exist... skipping backup" >> $LOG echo "" >> $LOG fi

I can't get my head around a way to do this: I want to backup my most critical unRAID data (photos & HD videos of my kids & documents) to an offsite location (NAS box) using a USB key as the transport device... But here's the catch: I don't want my old data left on the USB key indefinitely, just new/changed files due to: A) security reasons - what if I lose the key? Those keys are pretty small. B) filesize - I'd eventually run out of space on the key. So, to summarize, I really want the USB key to act as a temporal transport system where the changed files are deleted from it once successfully moved to the destination NAS box. I've had some fun getting incremental backups working with rsync using the 'link-dest' parameter, but rsync requires access to the destination structure when determining which files have changed. Unless I'm missing something?

Just tried beta12a after using beta12. Unfortunately my write speed has dropped significantly with this release [EDIT: I've checked and my wiring is not at fault]. Now I'm getting a write speed of only 8 MB/s max when transferring a 1.5Gb file. I'm guessing it's because of the new Realtek driver in this release. My network card is Gigabit capable (and speed was indeed Gigabit on release 12). My NIC is a PCI Tenda Gigabit TEL9901G which utilises a Realtek r8169 chip. Ok, it's conclusive - the problem is with this release afterall - see my findings report below. My Gigabit NIC is still only getting 100MB/s and I've noticed that WOL isn't working either which means I can't automatically save energy using the S3 scripts because the server no longer wakes when I send a magic packet. After conducting various hardware tests, I've localised the problem down to this beta12a release. The issue is not the cabling (tried 4, all connected to different switch ports) or my Switch (tried power-cycling it), or my PCI slot (I've tried 3). My Findings: The only thing I've changed is the bzroot and bzimage files between boots... beta12a - no gigabit (100Mb/s is my max speed) and WOL doesn't work beta12 - gigabit speed & WOL working beta11 - gigabit speed & WOL working beta10 - this NIC doesn't work at all with any drivers beta9 - gigabit speed & WOL working beta6a - gigabit speed & WOL working Syslog & ethtool & ifconfig & lsmod reports attached for all above betas. One related thing I've noticed with beta12a: it appears to try to make a Gigabit connection when unraid is booted (I notice the Gigabit light on the NIC blinks just a few times, see the the sequential "eth0: link up" and "eth0: link down" messages in the syslog) before falling back to a permanent 100Mb/s speed. syslogs.zip ethtool_ifconfig_lsmod_reports.zip

v 1.13 is latest ver of preclear_disk.sh Link is at bottom of first post here: http://lime-technology.com/forum/index.php?topic=2817.msg23246#msg23246 - first google result for "preclear_disk.sh" "If you are running unRAID 5.0beta4 onward, you must use at least version 1.6 of preclear_disk.sh for all features to work properly." from that thread. I already have a copy of 1.13, why does that say 1.6? Will 1.13 be ok for running unraid 5.0b12a? v 1.13 is a later version than v1.6. I think you are misreading "v 1.13" as "v 1.1.3", but they are not the same: "13" is a higher number than "6". On the same site take a look at the release dates and their corresponding version numbers

v 1.13 is latest ver of preclear_disk.sh Link is at bottom of first post here: http://lime-technology.com/forum/index.php?topic=2817.msg23246#msg23246 - first google result for "preclear_disk.sh"

I tried both of the above suggestions. The first suggestion resulted in ethtool reporting 1000MB/s speed for a second or so, until reverting back to 100MB/s The second suggestion: r8168 driver doesn't work with this NIC. Ok, I've reverted back to beta12 and it seems that I don't have Gigabit on that release either! This leaves me with two options: 1) check wiring (which has not changed since I last noticed I had gigabit) 2) revert to older beta (perhaps beta9) and see if I get gigabit with that driver.