graywolf

The Drives/configuration doesn't care what mobo/cpu (as long as it's supported). You could switch the hard drives/flash drive around to as many different machines/motherboards as you wish and it doesn't care. So at least 1 less thing to worry about. If you have another computer, can you try doing a boot from your flash drive just to make sure that is all well

Yep. Been retired (GySgt) for over 12 years now and still get a high and tight every 2 weeks. Not as lean, not as mean, but still a US Marine Semper Fi to any other Devil Dogs that visit here

Semper Fi

http://lime-technology.com/forum/index.php?topic=28462.msg253499#msg253499 Per Tom Great work and even better communication lately. Greatly appreciated by many

unRaid version: 5.0-beta11 VM Trying to do the following. Not getting OOM but would like to have it in place just in case: pgrep -f "/usr/local/sbin/emhttp" | while read PID; do echo -1000 > /proc/$PID/oom_adj; done Gives me: root@Tower:/root -> pgrep -f "/usr/local/sbin/emhttp" | while read PID; do echo -1000 > /proc/$PID/oom_adj; done -bash: echo: write error: Invalid argument So stepping thru it: root@Tower:/root -> pgrep -f "/usr/local/sbin/emhttp" | while read PID; do echo $PID; done 1378 root@Tower:/root -> ls -l /proc/ | grep 1378 dr-xr-xr-x 6 root root 0 2013-07-10 09:16 1378/ dr-xr-xr-x 6 root root 0 2013-07-10 11:02 13785/ dr-xr-xr-x 6 root root 0 2013-07-10 11:00 13786/ root@Tower:/root -> ls -l /proc/1378 total 0 -r-------- 1 root root 0 2013-07-10 11:08 auxv --w------- 1 root root 0 2013-07-10 11:08 clear_refs -r--r--r-- 1 root root 0 2013-07-10 11:08 cmdline -rw-r--r-- 1 root root 0 2013-07-10 11:08 comm -rw-r--r-- 1 root root 0 2013-07-10 11:08 coredump_filter lrwxrwxrwx 1 root root 0 2013-07-10 11:08 cwd -> // -r-------- 1 root root 0 2013-07-10 11:08 environ lrwxrwxrwx 1 root root 0 2013-07-10 11:08 exe -> /usr/local/sbin/emhttp* dr-x------ 2 root root 0 2013-07-10 11:08 fd/ dr-x------ 2 root root 0 2013-07-10 11:08 fdinfo/ -r--r--r-- 1 root root 0 2013-07-10 11:08 limits -r--r--r-- 1 root root 0 2013-07-10 11:08 maps -rw------- 1 root root 0 2013-07-10 11:08 mem -r--r--r-- 1 root root 0 2013-07-10 11:08 mountinfo -r--r--r-- 1 root root 0 2013-07-10 11:08 mounts -r-------- 1 root root 0 2013-07-10 11:08 mountstats dr-xr-xr-x 4 root root 0 2013-07-10 11:08 net/ -rw-r--r-- 1 root root 0 2013-07-10 11:08 oom_adj -r--r--r-- 1 root root 0 2013-07-10 11:08 oom_score -rw-r--r-- 1 root root 0 2013-07-10 11:08 oom_score_adj -r-------- 1 root root 0 2013-07-10 11:08 pagemap -r-------- 1 root root 0 2013-07-10 11:08 personality lrwxrwxrwx 1 root root 0 2013-07-10 11:08 root -> // -r--r--r-- 1 root root 0 2013-07-10 11:08 smaps -r--r--r-- 1 root root 0 2013-07-10 11:08 stat -r--r--r-- 1 root root 0 2013-07-10 11:08 statm -r--r--r-- 1 root root 0 2013-07-10 11:08 status -r-------- 1 root root 0 2013-07-10 11:08 syscall dr-xr-xr-x 4 root root 0 2013-07-10 11:02 task/ -r--r--r-- 1 root root 0 2013-07-10 11:08 wchan root@Tower:/root -> cat /proc/1378/oom_adj 0 root@Tower:/root -> echo -1000 -1000 root@Tower:/root -> echo -1000 > /proc/1378/oom_adj -bash: echo: write error: Invalid argument root@Tower:/root ->

Playing with cache_dirs and finding something strange. Start it by: cache_dirs -p 200 -i Specials -i UnArchived -i FanArt Runs fine for awhile and I see the processes ps -ef | grep cache root@Tower:/root -> ps -ef | grep cache root 14369 1 0 10:49 pts/1 00:00:00 /bin/bash /boot/scripts/cache_dirs -p 200 -i Specials -i UnArchived -i FanArt root 14370 1 0 10:49 pts/1 00:00:00 /bin/bash /boot/scripts/cache_dirs -p 200 -i Specials -i UnArchived -i FanArt root 14372 1 0 10:49 pts/1 00:00:00 /bin/bash /boot/scripts/cache_dirs -p 200 -i Specials -i UnArchived -i FanArt root 14373 1 0 10:49 pts/1 00:00:00 /bin/bash /boot/scripts/cache_dirs -p 200 -i Specials -i UnArchived -i FanArt root 14375 1 0 10:49 pts/1 00:00:00 /bin/bash /boot/scripts/cache_dirs -p 200 -i Specials -i UnArchived -i FanArt root 14376 1 0 10:49 pts/1 00:00:00 /bin/bash /boot/scripts/cache_dirs -p 200 -i Specials -i UnArchived -i FanArt root 14377 1 0 10:49 pts/1 00:00:00 /bin/bash /boot/scripts/cache_dirs -p 200 -i Specials -i UnArchived -i FanArt root 14378 1 0 10:49 pts/1 00:00:00 /bin/bash /boot/scripts/cache_dirs -p 200 -i Specials -i UnArchived -i FanArt root 14379 1 0 10:49 pts/1 00:00:00 /bin/bash /boot/scripts/cache_dirs -p 200 -i Specials -i UnArchived -i FanArt root 14380 1 0 10:49 pts/1 00:00:00 /bin/bash /boot/scripts/cache_dirs -p 200 -i Specials -i UnArchived -i FanArt root 14381 1 0 10:49 pts/1 00:00:00 /bin/bash /boot/scripts/cache_dirs -p 200 -i Specials -i UnArchived -i FanArt root 14382 1 0 10:49 pts/1 00:00:00 /bin/bash /boot/scripts/cache_dirs -p 200 -i Specials -i UnArchived -i FanArt root 14383 1 0 10:49 pts/1 00:00:00 /bin/bash /boot/scripts/cache_dirs -p 200 -i Specials -i UnArchived -i FanArt root 14384 1 0 10:49 pts/1 00:00:00 /bin/bash /boot/scripts/cache_dirs -p 200 -i Specials -i UnArchived -i FanArt root 14385 1 0 10:49 pts/1 00:00:00 /bin/bash /boot/scripts/cache_dirs -p 200 -i Specials -i UnArchived -i FanArt root 14386 1 0 10:49 pts/1 00:00:00 /bin/bash /boot/scripts/cache_dirs -p 200 -i Specials -i UnArchived -i FanArt root 14387 1 0 10:49 pts/1 00:00:00 /bin/bash /boot/scripts/cache_dirs -p 200 -i Specials -i UnArchived -i FanArt root 14388 1 0 10:49 pts/1 00:00:00 /bin/bash /boot/scripts/cache_dirs -p 200 -i Specials -i UnArchived -i FanArt root 14389 1 0 10:49 pts/1 00:00:00 /bin/bash /boot/scripts/cache_dirs -p 200 -i Specials -i UnArchived -i FanArt root 14390 1 0 10:49 pts/1 00:00:00 /bin/bash /boot/scripts/cache_dirs -p 200 -i Specials -i UnArchived -i FanArt root 14472 1 0 10:49 pts/1 00:00:00 /bin/bash /boot/scripts/cache_dirs -p 200 -i Specials -i UnArchived -i FanArt After awhile though, if I check again, it appears that cache_dirs has died. Nothing in syslog to let me know what happened though. If I do a cache_dirs -q it tells me that #### is not running. unRaid version: 5.0-beta11 VM 4GB Ram Any thoughts?

Are you getting into unRaid boot up when you get that or machine boot up? Sounds to me like you are not even getting to unRaid startup. Your BIOS may be trying to boot from one of the Disks instead of the flash drive. Go into your BIOS config and ensure your Flash Drive is the boot drive. You may also want to take your Flash Drive to a Windows machine and run Checkdisk on it

attach your entire syslog so that folks can review it

Could it be the same thing as here http://lime-technology.com/forum/index.php?topic=28353.msg252045#msg252045 VirtualBox related it looks like

So for us non-gurus, is there an easy way/command to tell what the current kernel version is and what kernel version the vmwaretools supports?

unMenu is JoeL's baby, not Tom's

I agree. There are already plugins for UPS and e-mail. I would prefer Tom spending time on core features at this point (highest on my wish list would be double-parity and plugin manager) These are items that have been on the "Roadmap" for a lot longer and are items that Tom needs to handle whereas UPS/e-mail plugins exist and could be enhanced, rewritten, etc without taking Tom's time. The squeaky wheel doesn't always get the grease, sometimes it just gets replaced

I don't do XBMC but you might want to check out this thread http://lime-technology.com/forum/index.php?topic=27545.0 since it talks about the XBMC SALUD plugin Asking your question there might get a better response/help

unRaid VM under ESXi

I definitely wouldn't be happy with this solution. There is a right way and an easy way, rarely do the two meet. So with your "easy" solution, I would need to set up a gmail account account just for unRaid? Then figure out the forwarding to my actual account? Open up another avenue for additional spam? What about those folks that just don't want to deal with Google? (I know a few). Are they to be left out in the wind?

http://lime-technology.com/forum/index.php?topic=28382.0 unRAID Server Release 5.0-rc16c Available Includes the transport endpoint fix

unfortunately it appears to be an in-store price only

Well, the shipment is supposed to get to the states in a week or two according to the post. Glad I got mine in yesterday. Don't see moving from SageTV anytime soon and wanted some spares in case of extender failure.

IF you were going to have a VM setup with ESXi, then would recommend a Cyberpower UPS and get the VM Appliance. Nice, simple, just simply works for shutting down VMs and ESXi cleanly

Attached is the script mrow was referring to. I haven't used it but thought it was a good idea so downloaded it before he got banned in case I ever needed it. keeplogs.zip

You can run both without issue.

It has been awhile since I've used 4.7. I know with 5.x it wouldn't be an issue. Even if you had a Parity drive, you would just need to know which was the parity drive. A good safety measure would be to take a screen shot of your drive assignments for the order. As far as physically which drive location, it shouldn't matter.

Was this used in an unRaid 4.7 system before and was logically shrunk down to 2.2 TB to work in the v4.7 system?

can you attach your syslog? do you have anything in your syslog like Jun 28 17:29:56 Tower emhttp: shcmd (161): mkdir '/mnt/user/pmm2' Jun 28 17:29:56 Tower emhttp: shcmd (162): chmod 770 '/mnt/user/pmm2' Jun 28 17:29:56 Tower emhttp: shcmd (163): chown nobody:users '/mnt/user/pmm2' Jun 28 17:29:56 Tower emhttp: shcmd (164): :>/etc/samba/smb-shares.conf Jun 28 17:29:56 Tower emhttp: Restart SMB... Jun 28 17:29:56 Tower emhttp: shcmd (165): killall -HUP smbd Jun 28 17:29:56 Tower emhttp: shcmd (166): ps axc | grep -q rpc.mountd Jun 28 17:29:56 Tower emhttp: _shcmd: shcmd (166): exit status: 1 Jun 28 17:29:56 Tower emhttp: shcmd (167): /usr/local/sbin/emhttp_event svcs_restarted Jun 28 17:29:56 Tower emhttp_event: svcs_restarted

did you fill in the fields before hitting the Add Share button?