nars

Please note that the warning you get on syslog doesn't mean that the job is not running, just means that it is not mailing the output of the executed thing... if you handle mailing on the script itself you may not need to fix that anyway you need something like sendmail (I don't recommend it, it is overkill for what you need and I did tried to install it once on unraid and got some problems with it always telling me that there was no space on queue folder, despite there was... I guess maybe related to unraid running on a "live" filesystem...) or ssmtp anyway (and apparently you don't have it from the errors you posted above). There is a plugin on unMenu for mailx and ssmtp it may be the easiest way you get it. Btw, you could maybe set a more appropriate title for this topic Edit: Opps, I did missed part of your posts, sorry, you apparently could run ssmtp then you must already have it. I did got the bad idea you didn't had it because of the errors when trying to run sendmail / mail and I guessed there should exist these as symlinks.. Edit2: Re mail subject you may use something like this: echo -e "Subject: test\n\n`cat file.md5`" | ssmtp -d root

Think it will not help.. most probably ntp server will always return utc on router exactly like a public ntp server. If I understand the thing can be most probably related to kernel behaving like system clock is set to utc and getting/setting time on it as that... may be related to UTC param on /etc/adjtime or /etc/sysconfig/clock... anyway on unRaid may be a bit complex to properly fix this as when go file runs the clock is probably already adjusted (system time already set from rtc time as if rtc time is utc...), maybe there could be an workaround changing this from go file but it would most probably need time being set incorrectly at startup and only then fixed... but maybe some linux expert can comment more on that or maybe tom could add an option for that if you ask him

You didn't needed to remove super.dat to upgrade from rc5 to rc11 (maybe you looked at instructions to upgrade from beta5 and not from rc5?)... Anyway I think you should be able to start the array with "Parity is already valid" option enabled and then manually run a parity check and see if all ok (0 errors).

Yes, it's normal (for now), Tom did mention it.

Maybe it is trying to boot one of the new HDD's and not the flash drive?

http://lime-technology.com/forum/index.php?topic=12698.0

May be good you look at syslog and see if there was something added on it when you run modprobe as it may really not print anything on console.

Should UnRAID be 32bit, 64bit, or maintain a version of both? Where is the option for "maintain a version of both" ? My server is 64bit capable but I guess many other people may still run some 32bit only p4's that are still good for unraid... my vote would be support both, if possible, or at least maintain a 5.0 32bit version by just fixing important bugs etc even if no new features get added on it...

Separate with spaces, but remember current implementation does not implement share-level protection. Hope to change that in the future but it will take some work, e.g., creating directories and using mount --bind. Thank you for looking at my suggestion Btw spaces do not work, you will need to convert them to/from newlines for the vsftpd.user_list file and you are not apparently doing it. Btw also upgraded to rc11, so far all ok on my server.

Then you get such speeds from internal desktop hdd to your external hdd (nothing related to unraid) ?

Did you setup the second eth interface? This may help you: http://lime-technology.com/forum/index.php?topic=14988.msg141655#msg141655 Anyway not sure if you will get the network performance you want for pfSense using emulated network interfaces, unless using virtio with pfSense maybe? but no idea if that would be easy... maybe esxi would be better for such setup if you hardware is ok for that...

What happens if you copy from unRaid server to internal hdd on your desktop pc first and then from it to the external hdd?

did you tested speed for all your hdd's? you can use something like: for d in /dev/sd?; do echo $d:; dd if=$d of=/dev/null iflag=direct bs=10M count=20; done (make sure all drives are spinning before doing it or run it twice else it may show lower values than real due to the time hdd's take to spinup...) anyway you problem may be some bottleneck when reading them all at same time...

If you didn't even got the screen to select unraid or memtest then the problem was at syslinux. See my post (including quotes) at: http://lime-technology.com/forum/index.php?topic=25250.msg222168#msg222168

Note that you may need to re-run the .bat to reinstall syslinux. Thanks, somehow I missed it. I'm using Mac, so I guess finding Windows machine to run .bat is just too much hassle, I'll wait for the 5.0 final It may be better you test it before final as I'm not sure if that is really the problem that you are having Also I did checked better and in fact from rc9a to rc10 there is no syslinux change (it is from rc8a to rc9a) then I think it makes no sense it require running the .bat, unless you didn't also ran it when you updated to rc9a? Also are you just trying to replace bzimage and bzroot (and readme.txt if you want...) ? You should not need to replace any other files... if your existing syslinux is working fine then you don't probably need to update it BUT then you should also NOT update menu.c32 (part of syslinux) and make sure you don't delete the existing ldlinux.sys on the flash (created when you did ran the .bat), I guess that is what caused these problems with these guys that had to re-run the .bat.

Not sure if this can be useful... I did enabled samba log (log level = 2), attached. Did booted true image, selected a few backup files (you will see multiple backup file names showing) it didn't freezed at just doing that (sometimes it does) then I did tried to start diff backup to BackupC.tib (there is also BackupC2.tib and BackupC3.tib on server already from previous tests), it would be supposed it create BackupC4.tib but it did hang/freeze at 0% doing nothing (I guess that at this time it should read existing backup file). lsof: root@unRAID:~# lsof | grep pub shfs 8354 root 4u REG 9,1 15190548722 12439 /mnt/disk1/pub/BackupC.tib smbd 8456 root cwd DIR 0,13 320 7 /mnt/user/pub smbd 8456 root 31u REG 0,13 15190548722 27 /mnt/user/pub/BackupC.tib Then I did hard reset the PC running true image, at 04:02 windows boots at that PC... "handles" still visible on lsof on unraid server and file access is locked until near 04:21 then there is a timeout entry at log and they disappear, file is unlocked again. I did noticed that there is on log some successive and fast file opens/closes, maybe related? also as file get's locked (because it is open for write?) maybe there is an attempt to open the yet locked file or something similar... just guesses... Btw, despite I'm posting these infos to try to help checking this issue, as I did stated above I don't want to push you looking at this problem with great priority, most of times I will really create backups on the cache drive for performance I'm just reporting it as it may be useful to identify a possible problem that may eventually also be triggered by something other than true image (despite so far I didn't found any) log.smbd.txt

Note that you may need to re-run the .bat to reinstall syslinux.

Did and re-did a few more tests and: - accessing \\tower\tmp (set as cache-only user share) works fine - accessing \\tower\pub (set as an user share on parity protected array and no cache enabled for this share) gives me the weird problems I described. After reading Electron286 post I did also tried to edit this user share to use only 1 hdd (Included disk(s): disk1), then it haves only 600GB free but that doesn't help. - accessing \\tower\disc1\pub works fine may it be shfs/fuse related? but \\tower\tmp also go through it right? but I think it also seems timing related, as for eg.: 1. if right after unraid server restart (no files cached at all) I access \\tower\pub with true image then the problem happens, and in fact I don't even need to actually start the diff backup, just on the step to select existing backup file (it will read it and show some infos about the selected backup, partitions structure, etc) then it hangs immediately (tested 3 times), and lsof on unraid shows this: root@unRAID:~# lsof | grep Backup shfs 4207 root 4u REG 9,1 15190548722 12439 /mnt/disk1/pub/BackupC.tib smbd 8351 nobody 30u REG 0,13 15190548722 25 /mnt/user/pub/BackupC.tib no data being transferred on network, just freezed and these handles open... if I reset true image pc handles remain for some time... if instead of reset true image pc I stop array on unraid server then hadles get closed and true image unfreezes. 2. however after I access \\tower\disc1\pub directly, then if I access \\tower\pub (exactly like in 1.) then it will work now, until I restart unraid server or stop/start array (I guess because file at disc1\pub get's cached? that's why I suspect it may be timming related). I did repeated these tests at least 3 times to make sure I could always reproduce what I'm posting here. Did some more tests and found that this is not correct, there was some confusion on my 1st tests on this, sorry for that, teracopy really shows a message about file in use by other process and there is an option to unlock it (but in this case not correct... teracopy probably "thinks" it can't access file as it is open by other process on the pc that teracopy is running at, but this is not obviously the case as this is a 3rd pc and the file is locked at unraid server, not at this 3rd pc). I did probably got the (wrong) idea that unlock would unlock it because in the mean time the lock disappeared on unraid server (it disappears after some minutes).

Sorry if it was not clear I did tried to add many details and maybe it got confuse/bloated I meant "a)", an user share set on unRaid as "Use cache disk: only". In all my tests I did always tried to access the user shares, never discX or cache shares directly. In sum: - accessing \\tower\tmp (set as cache only) works fine - accessing \\tower\pub (set as a share on parity protected array and no cache enabled for this share) gives me the weird problems I described Will test true image accessing cache and discX shares directly soon and let you know what happens. Anyway these problems only really happen with true image as I did already had all kinds of apps reading/writing from these same user shares on parity protected array, even vm's running live with hdd image files stored remotely on the protected array and stressing read/write on it a lot as you can imagine... and no problems at all... only really true image seems to cause this.

First I should say that my unRaid server is running fully stable for some time now and I do have no problems at all to remotely read/write data on it from Windows 7 or XP PC's using smb or ftp, I do get good network speed and there is no lost packets or any problem. I did already copy 100's of GB's on both directions, verified them with md5 etc ( yes I'm integrity paranoiac ) and never had any kind of corruption. However I'm having some strange problems when on any of my PC's instead of Windows I do run Acronis True Image (running it from it's bootable media, based on Linux) and try to do an HDD backup and set it to read/write image file on unRaid server (via smb) directly on an user share that is part of the parity protected array (problems described below), however if I set it to read/write image file to an unRaid cache user share (set on unRaid as Use cache disk: only) then it works fine no problem at all, also if I set it to read/write image file on a share on another Windows PC I do also get no problem at all, then in sum the problems only really seem to happen when Acronis True Image needs to read/write to an user share that is part of parity protected array. The problems on Acronis True Image Echo Workstation 9.5 are mostly (permanent) freezes when Acronis True Image tries to read/write from unRaid, for eg. one situation that I could easily reproduce and I did tested it a lot of times to be sure is the following: - I do already have a full hdd image file (from one of my windows pc's hdd obviously) saved on unRaid server, I do have that image file duplicated and available on two unraid user shares, one is on a cache only share (I did created it there initially to avoid problems to create it...) then did cp it to the protected array... - Boot True Image disc on the PC that image was created from... and want to create a differential image (only with changes made after creating the previous/existing image file), I do select the existing image file from the unRaid server (via smb) and select that I want to create differential image, then true image should read parts of the already created image file (probably something like included files structure, checksums etc) and the local hdd so that it can identify what is new/changed... - on the step above If I select the existing image file as the one available on the cahe-only user share and it works fine and creates a new file with differences as expected... however if I select existing image file as the one available on the parity protected user share then true image hangs/freezes when trying to read the remote existing image file. If I wait something like 30 mins it will show an error that there was a problem to read file. Also during hang if from a 3rd pc (windows) I do try to read that same image file from unraid (try to md5 it for eg. or copy using windows shell, teracopy is different I will explain below) I can't read it, file looks like locked on the unraid server. Also I did a lsof on unRaid and could see this: root@unRAID:~# lsof|grep BackupC shfs 9679 root 4u REG 9,1 15190548722 12439 /mnt/disk1/pub/BackupC.tib shfs 9679 root 5u REG 9,1 15190548722 12439 /mnt/disk1/pub/BackupC.tib shfs 9679 root 7u REG 9,1 15190548722 12439 /mnt/disk1/pub/BackupC.tib smbd 9912 root 31u REG 0,13 15190548722 14 /mnt/user/pub/BackupC.tib smbd 9912 root 32u REG 0,13 15190548722 14 /mnt/user/pub/BackupC.tib smbd 9912 root 33u REG 0,13 15190548722 14 /mnt/user/pub/BackupC.tib One other thing I did noticed is that if I do not want to wait and hit reset button on the pc running true image then such lock (and these "handles" on lsof remain for some minutes, until they disappear and the lock is lifted also, I can then read the image file on the 3rd pc running windows) Also if during that lock on a 3rd pc (windows) I do try to use teracopy to copy that somehow locked file then teracopy tells me something like that the file is locked and asks me if I want to unlock it, doing it also lifts that lock (I can post a screenshot showing that if you don't know what I'm talking about). I do ask myself what can be different for samba to access a protected or a cache share? just a timming issue that may trigger a problem on true image? or is there something else that may cause it like... is it ok to open a file from protected array multiple times at same time a read multiple parts of time (multiple handles)? any idea? This is not a major problem to me as most of times I will just want to write image files to the cache drive really, and only then move them to parity protected (as it is obviously faster to create images that way), anyway I'm posting this as I do find it strange what the hell true image may be doing to cause this problem with unraid parity protected shares. Sorry if I have been too long but I did tried to put all details I could on my message, if you need I test something more please just ask.

I do have BitFenix Recon controller on my server, so far I'm happy with it (there is some videos about it on youtube) and also I know ( in fact I did suggested it ) that Phoebetria (sourceforge) project guys are working on a simple Linux command line tool that will allow to control Recon, set fan speeds, get temperatures, etc. So that you have an idea this was my proposed syntax for the tool (one of the programmers asked me to suggest it): phoebetria -h Usage: phoebetria [OPTIONS] ... -h, --help Display this help and exit -i, --info [ch] Show current temperatures and fan speeds -m, --manual-speed [ch] [value_to_set] Show/Set manual fan speed values in RPM -a, --alarm-temp [ch] [value_to_set] Show/Set alarm temperatures -s, --device-settings [auto=0/1] [celcius=0/1] [sound=0/1] Show/Set device settings -d, --display-channel <ch> Set current device display channel -c, --celcius Show/Set temperatures in degrees celcius -f, --fahrenheit Show/Set temperatures in degrees fahrenheit Note: On --manual-speed, --alarm-temp and --device-settings omit [value_to_set] to get the currently set values. You can also omit the [ch] parameter to get values for all channels. with -i returning something like: Ch Temp Speed 1 35ºC 1000 RPM (max: 1300 RPM) 2 35ºC 1000 RPM (max: 1300 RPM) 3 35ºC 1000 RPM (max: 1300 RPM) 4 35ºC 1000 RPM (max: 1300 RPM) 5 35ºC 1000 RPM (max: 1300 RPM) anyway note that the tool is not available yet, but one of the Phoebetria project guys said that is working on it for soon, basically it is not hard task as Phoebetria project already haves all code (available on sourceforge) to interface Recon hardware, it's just a matter of build the code to parse command line params, print inofs and some small changes to handle asynchronous calls that are made on current Phoebetria gui version to get data from the device...

I would recommend you maybe have a look at a Intel Gxxx (sandy/ivy bridge based), they are good low power cpu's and still have good performance if/when required. If you look at my sign you can see that I have a G620 myself, you can see some comments and links I did posted at other topic: http://lime-technology.com/forum/index.php?topic=25130.msg218545#msg218545 On my system I have it with stock cooler, and motherboard is set to auto control cooler's fan speed (usually always it at 1000rpm with default fan control settings, even when at full load for some hours), also my case (for now) have just 1 rear 120mm fan running also at 1000rpm (despite even lower rpm's like 600/700 seems fine and make very little difference on temperatures, from some tests, however I do run it at 1000rpm as it is still inaudible for me, only at 1300rpm I can notice a little turbulence but still only on very quiet rom). I can tell you that my whole system is near inaudible at 1m from it (so that you have an idea my case haves only 1 led, intended for power led, however I did connected it as hdd led as I find it more useful, and sometimes I have trouble to find if it is turned on or not, I really need to get very close to it to check that )

I didn't read for 3220 vs 3220T specifically, but... if same as for 2100 vs 2100T then the T model is basically just an underclocked model... both will have same exact power consumption at idle, the difference will be at full load... also note that the T model may have a low profile cooler (less efficient and noisier... at least this was the case on 2100T), I ended getting a G620 for my system, almost same as 2100T, a lot cheaper, and comes with a better (bigger) cooler.

The reason for it not showing files on previous versions was that vsftpd config was set in a way that only world readable files would get listed/acessible (to sort it we had to add "anon_world_readable_only=NO" to vsftpd config), however since 5.0-rc9 all files are now world readable (as long as user run's "New Permissions" script as advised by Tom) then the issue is sort of fixed, however this opens a new security problem that Tom said that will be fixed for final, see: http://lime-technology.com/forum/index.php?topic=25250.msg219648#msg219648 and my suggestion to sort it: http://lime-technology.com/forum/index.php?topic=25250.msg219701#msg219701

Yes, my motherboard is similar and I can confirm that Realtek NIC works very well, running it since September and no problems at all (and no slow write problem with latest kernels, despite 8GB). In fact I was also to get something smaller like PC-Q25 or PC-Q08 and also P8H77-I but... thinking better on it I ended choosing something bigger... Define R3... there is no limitations on PSU (at least on pc-q25 psu needs to have some max length else it will not fit the case... many psu's will not fit it if I can remember...), it is better for expanding on future, runs probably cooler and more silent, easier to build (no confusion to fit it all on small case)... but they are indeed good looking cases and if you already own it then go with it I still had there two links about systems with PC-Q25 on my bookmarks, there is some photos there and info I did found interesting at the time I was choosing what to get: http://lime-technology.com/forum/index.php?topic=17345.0#top http://www.silentpcreview.com/forums/viewtopic.php?f=23&t=63654 Other than that differences for my system I did got G620 cpu instead (very similar to i3 2100T, but you may need more performance for the addons you pointed, I can't comment on that as I don't use them) and got CML8GX3M2A1600C9 ram, but the one you pointed is probably very similar other than the different heat spreaders.