otisk

My go script is no longer executed properly. emhttp starts normally but my own commands are not executed. Systemlog does not give any errors regarding the go-script. This is my go script: #!/bin/bash # Start the Management Utility /usr/local/sbin/emhttp & % Copy the edited mover script to ram cp /boot/config/mover /usr/local/sbin % Start the p910nd Printserver /boot/p910nd -f /dev/usb/lp0 -b Any ideas why it only starts emhttp? EDIT: I guess the problem was that I missed the "&" after /usr/local/sbin/emhttp. Now everything seems to work fine again.

I guess I found out why it does not work. I'm running the webGui on port 8008 because plexconnect needs port 80. The powerdown script states that it needs the webGui to be running on port 80.

I tried running the powerdown script in /usr/local/sbin manually through ssh but nothing happened either. shouldn't the server shutdown in this case?

I just installed an ups and experience the exact same thing on 6.1 final. Is there already a solution for this?

That sounds like cache_dirs should improve the scanning speed drastically?! I guess I'll try that out. I haven't tested crashplan on other client operating systems but mac yet. Is it just a mac thing/issue that crashplan writes to some files when the mac wakes up or is this also happening with other operating systems?

Install Dynamix Cache Directories / Cache_dirs are you sure this solves the problem? There are some files that are being written to so I don't think cache_dirs would do anything about it.

I set up crashplan yesterday to make backups of my mac's user folder on my unraid server. I configured it to only run once a day intending not to spin up the array drives permanently. Unfortunately everytime I wake up my mac from sleep, crashplan is spinning up my backup and parity disk and is editing some files in the backup folder. How can I prevent it from doing this? I don't want the drives to spin up everytime a client connects to the server but only when an actual backup is made. Is anyone else experiencing this behavior? EDIT: For anyone else who experience this issue: I've got a workaround for this. I set my backup share to cache only and started a new backup so crashplan created its backup folder on the cache disk. Then I set the share to not cache and copied over the one big file that obviously is the actual backup to a corresponding folder on my array. All the small files that are accessed and being written to during the connection stay on the cache disk and my array does not spin up unless an actual backup is made.

Hi gfjardim, I had still no luck getting my printer to work properly. I attached the error log of what happens when I try to print a test page. Maybe you could have a look at it and tell me how to resolve it? I guess the problem is this: PID 41 (/usr/lib/cups/filter/Xerox_Phaser_6000_6010/XRM_MF) stopped with status 108 (Exec format error) cups_testpage_errorlog.txt

I only added support for HP and Samsung printers, those which I have how to test it. I'll try to add Xerox too. Took a look at your printer model, and apparently it's divers are 32bits only. Did you took a look at openprinting.org? The driver I downloaded is stated to work on 32 and 64 bit systems. http://www.support.xerox.com/support/phaser-6000/file-download/engb.html?operatingSystem=linux&fileLanguage=en_GB&contentId=116070&from=downloads&viewArchived=false I was able to load the entire driver into the cups docker. My printer is detected correctly and I can select the driver in the cups drivers list. When the printer is set up, it shows no error in the status as it did before. Up to this point everything seems fine. Anyway, whenever I try to print something it says "filter failed" in the status. I haven't been able to find out at which point it fails yet. I found this guide for my printer model: https://wiki.archlinux.org/index.php/Dell_1250c Unfortunately I have absolutely no idea how to make it work. If you could give me a hint or even implement a working driver into the container I'd really appreciate it.

Hi gfjardim, how do I install drivers into the cups container? I have a Dell 1250c printer which uses the Xerox Phaser 6000b driver for Linux that is not included in cups. I have already downloaded the rpm driver file and tried to use the PPD file but when I print a test page the error log says that some filters are missing. Edit: I figured out that the missing filter files are inside the rpm file and that I can change the directory inside the ppd file to point to a different directory. Unfortunately if I put the filters into a different directory and point to the changed directory through the ppd file, cups throws an error, stating that the directory has insecure permissions. I guess I need to place the files into the /usr directory but if I try to point that folder to some place on my app-drive, Cups won't even start. How do I get access to that folder so I can put my filter files in there? Edit: Solved the permission error but still no luck. I guess there is something wrong with the drivers. When I try to print the test page, cups always throws out the error "filter failed".

I have a problem with your pyload docker. It won't update any plugins because of a permission error. ERROR UpdateManager: Error removing: /opt/pyload/module/plugins/hooks/Ev0InFetcher.py | [Errno 13] Permission denied: '/opt/pyload/module/plugins/hooks/Ev0InFetcher.py' Do you have an idea why this happens and how to solve it?

I think I lost my Data. During the rebuild it showed that the disk was unformatted and it stayed unformatted after the rebuild was finished. I formatted the disk a second time, disconnected the drive and started the array again without the drive connected. After reconnecting the blue dot appeared again. The only difference now is that the drive is not shown as unformatted during the rebuild. Anyway, I think this doesn't matter as I already lost my data during the first formatting because I saw some writing to the parity disk after formatting. It seems very likely and logical to me that the parity information has been overwritten at that point. Shame on me...

Thanks for the replies. It seems that you are right, that the problem was that unraid did not know that the drive was missing. The last thing I did after recognizing that the files are not showing up without the drive connected, was stopping the array because I didn't want my files to be further damaged. I just wanted to run dgaschk's command and therefor reconnected the drive and unraid immediately showed a blue dot in front of it and gave me the option to rebuild from parity. At the moment it's rebuilding. I'll report back when it's finished. Sorry for the misleading subject line. I rather meant something like "overwrite" than "delete". Couldn't it be possible that the parity files for the disk have been overwritten with parity for the empty disk? I don't know how to explain it better We'll see when the rebuild is finished.

Hi, I use a small 2,5" 250gb drive, I had laying around, in my array as a temporary solution because my 3tb drives are full and I don't want to buy another one at the moment. The problem is that I needed a hard drive to test something on my mac, so I shut down my unraid server, took out the 250gb drive, formatted it and did my stuff. I thought unraid would rebuild the drive when I put it back into my server, but it didn't. When I put it back in, unraid told me that it was unformatted and only gave me the option to format it, which I did. It took just a few seconds. There was no option to rebuild. After formatting and starting the array, unraid showed me 250gb free space on it. When I start the array with that drive disconnected, the shares that have previously been on that drive are also not shown. It seems that unraid deleted all files that have been on that disk from the parity disk when I hit "format" instead of rebuilding them. Am I right or is there any possibility that the files are still on my parity disk and I could rebuild them? best regards, Otis

What needs to be changed to use python 2.7.3? Apparently pycurl doesn't accept it as it looks for files that are located at the python 2.6 folder.