there is a problem with the mover script and the special netatalk (afp) directories:

Feb 6 16:59:45 Tower logger: ./Movies/.AppleDB/lock

Feb 6 16:59:45 Tower logger: Cannot stat file /proc/30023/fd/2: No such file or directory

Feb 6 16:59:45 Tower logger: Cannot stat file /proc/30023/fd/3: No such file or directory

Feb 6 16:59:45 Tower logger: Cannot stat file /proc/30023/fd/4: No such file or directory

Feb 6 16:59:45 Tower logger: Cannot stat file /proc/30026/fd/2: No such file or directory

Feb 6 16:59:45 Tower logger: Cannot stat file /proc/30026/fd/3: No such file or directory

Feb 6 16:59:45 Tower logger: Cannot stat file /proc/30026/fd/4: No such file or directory

Feb 6 16:59:45 Tower logger: Cannot stat file /proc/30230/fd/2: No such file or directory

Feb 6 16:59:45 Tower logger: Cannot stat file /proc/30230/fd/3: No such file or directory

Feb 6 16:59:45 Tower logger: Cannot stat file /proc/30230/fd/4: No such file or directory

Feb 6 16:59:45 Tower logger: ./Movies/.AppleDB/cnid2.db

Feb 6 16:59:45 Tower logger: Cannot stat file /proc/30023/fd/2: No such file or directory

Feb 6 16:59:45 Tower logger: Cannot stat file /proc/30023/fd/3: No such file or directory

Feb 6 16:59:45 Tower logger: Cannot stat file /proc/30023/fd/4: No such file or directory

Feb 6 16:59:45 Tower logger: Cannot stat file /proc/30026/fd/2: No such file or directory

Feb 6 16:59:45 Tower logger: Cannot stat file /proc/30026/fd/3: No such file or directory

Feb 6 16:59:45 Tower logger: Cannot stat file /proc/30026/fd/4: No such file or directory

Feb 6 16:59:45 Tower logger: Cannot stat file /proc/30230/fd/2: No such file or directory

Feb 6 16:59:45 Tower logger: Cannot stat file /proc/30230/fd/3: No such file or directory

Feb 6 16:59:45 Tower logger: Cannot stat file /proc/30230/fd/4: No such file or directory

Feb 6 16:59:45 Tower logger: ./Movies/.AppleDB/db_errlog

Feb 6 16:59:45 Tower logger: Cannot stat file /proc/30023/fd/2: No such file or directory

Feb 6 16:59:45 Tower logger: Cannot stat file /proc/30023/fd/3: No such file or directory

Feb 6 16:59:45 Tower logger: Cannot stat file /proc/30023/fd/4: No such file or directory

Feb 6 16:59:45 Tower logger: Cannot stat file /proc/30026/fd/2: No such file or directory

Feb 6 16:59:45 Tower logger: Cannot stat file /proc/30026/fd/3: No such file or directory

Feb 6 16:59:45 Tower logger: Cannot stat file /proc/30026/fd/4: No such file or directory

Feb 6 16:59:45 Tower logger: Cannot stat file /proc/30230/fd/2: No such file or directory

Feb 6 16:59:45 Tower logger: Cannot stat file /proc/30230/fd/3: No such file or directory

Feb 6 16:59:45 Tower logger: Cannot stat file /proc/30230/fd/4: No such file or directory

Feb 6 16:59:45 Tower logger: ./Movies/.AppleDB

Feb 6 16:59:45 Tower logger: .d..t...... Movies/

Feb 6 16:59:45 Tower logger: cd+++++++++ Movies/.AppleDB/

Feb 6 16:59:45 Tower logger: rsync: stat "/mnt/user/Movies/.AppleDB" failed: No such file or directory (2)

Feb 6 16:59:45 Tower logger: rsync error: some files/attrs were not transferred (see previous errors) (code 23) at main.c(1042) [sender=3.0.7]

Feb 6 16:59:45 Tower logger: ./Movies

If you have installed the s2-ram , then you need to change the script

 

Replace echo -n 3 > /proc/acpi/sleep or echo -n mem >/sys/power/state with /boot/custom/bin/s2ram -f -p -m

 

You perhaps need to change the folder to where you have installed the s2-ram  

 

More info here -> http://lime-technology.com/forum/index.php?topic=3657.msg50365#msg50365

 

And add the below line to your go file, but remember to change your path to the script 

/boot/custom/bin/s3_notHrHdTcpIp.sh & #| at now + 1 minute

 

 

Thanks Peter,

 

One thing that confuses me is that if I probe the HDDs then do I need to alter the lines

 

if [ $checkHDDs = $yes ]
then
	# probe the flash drive at your peril
	HDDs=$((for d in $(ls /dev/[hs]d? | grep -v "$flash"); do hdparm -C $d | grep active ; done) | wc -l)
else
	HDDs=0
fi
echo $HDDs

 

If so how do I get round the problem of the drives being allocated different sd values each time I reboot? 

I can't answerer that.. I can't see that I have a problem.

In next beta, is the NFS fixed so it's possible to use NFS on some share?

 

The error I get right now is

 

Feb  8 19:40:07 Tower emhttp: shareExportNfsFsid.5 not found (Other emhttp)

Feb  8 19:40:07 Tower kernel: emhttp[11548]: segfault at 0 ip b744c96c sp bfcbe83c error 4 in libc-2.11.1.so[b741c000+15c000] (Errors)

In next beta, is the NFS fixed so it's possible to use NFS on some share?

 

The error I get right now is

 

Feb  8 19:40:07 Tower emhttp: shareExportNfsFsid.5 not found (Other emhttp)

Feb  8 19:40:07 Tower kernel: emhttp[11548]: segfault at 0 ip b744c96c sp bfcbe83c error 4 in libc-2.11.1.so[b741c000+15c000] (Errors)

 

Yes it's fixed.

In next beta, is the NFS fixed so it's possible to use NFS on some share?

 

The error I get right now is

 

Feb  8 19:40:07 Tower emhttp: shareExportNfsFsid.5 not found (Other emhttp)

Feb  8 19:40:07 Tower kernel: emhttp[11548]: segfault at 0 ip b744c96c sp bfcbe83c error 4 in libc-2.11.1.so[b741c000+15c000] (Errors)

 

Yes it's fixed.

 

In next beta, is the NFS fixed so it's possible to use NFS on some share?

 

The error I get right now is

 

Feb  8 19:40:07 Tower emhttp: shareExportNfsFsid.5 not found (Other emhttp)

Feb  8 19:40:07 Tower kernel: emhttp[11548]: segfault at 0 ip b744c96c sp bfcbe83c error 4 in libc-2.11.1.so[b741c000+15c000] (Errors)

 

 

Yes it's fixed.

 

 

Double   ;D

 

I have teh same issue with enabling NFS killing the webgui.  I really rely on NFS for my XBMC.  It absolutely destroys smb for streaming blu-ray movies!  Anxiousl;y awaiting BETA4.

 

TY for your hard work Tom!

 

I have updated unMENU to deal with the vol_id command being missing and the new presence of "wwn" devices in /devdisk/by-id

The changes are available by using The "Check for Updates" button and are backwards compatible with older releases of unRAID.  With the updates, it should now work as before.

 

Joe L.

 

How did you work around the vol_id missing Joe?  I'm needing to do the same thing in SNAP.

I thought I posted the replacement commands from vol_id in one of the threads discussing updates to the new Slackware distro. I'll try to find it again.

Here we go all the way on page 1 of this thread...

 

Correct. The vol_id program was removed and replaced with other means when the udev subsystem was upgraded. It is no longer supported on current udev subsystems. The replacement for 'vol_id' is 'blkid' and "vol_id --export" becomes "blkid -o udev". The user community addon SNAP will need to be updated if it wants to support the final 5.0 series.

Here we go all the way on page 1 of this thread...

 

Correct. The vol_id program was removed and replaced with other means when the udev subsystem was upgraded. It is no longer supported on current udev subsystems. The replacement for 'vol_id' is 'blkid' and "vol_id --export" becomes "blkid -o udev". The user community addon SNAP will need to be updated if it wants to support the final 5.0 series.

 

Even after I searched for vol_id earlier I didn't find that.  Thanks.