limetech Posted June 12, 2013 Share Posted June 12, 2013 Download | Release Notes This release fixes a number of Open Issues. Two things of note: 1. When you upgrade, please copy bzimage, bzroot, and syslinux.cfg from the release to your flash. This is because the 'default' boot now includes a kernel parameter that limits the amount of memory used by linux to 4GB. When the boot screen comes up you can hit a key and select the normal boot if your h/w platform doesn't have the "slow write" issue. This "slow write" issue is actually fixed in the latest linux kernel, but unfortunately, the latest linux kernel also exhibits a more serious regression that can cause a system crash when you try to Stop the array. I have posted info about this issue on the appropriate linux development mailing list, and when a patch is produced, I will resume periodic updates of the kernel to the latest release. 2. The 'Settings/NFS' page now includes a tunable parameter called (fuse_remember). Please click on the the page title bar to bring up the help that explains what this tunable is for. Please disregard the instructions from -rc13 that had you create a "extra.cfg" file - if you have this file, please delete it. Quote Link to comment
mrow Posted June 12, 2013 Share Posted June 12, 2013 Thanks Tom, I will load this up in a little bit and give it a go. Quote Link to comment
nars Posted June 12, 2013 Share Posted June 12, 2013 Thanks, will test it and post some feedback soon if any problem found. Quote Link to comment
nars Posted June 12, 2013 Share Posted June 12, 2013 I did found that every time I browse an hdd on web interface ( i.e. /Main/Browse?dir=/mnt/disk1 ) I do get error lines printed on console like: /file_path.... user.LOCATION: No such attribute Quote Link to comment
limetech Posted June 12, 2013 Author Share Posted June 12, 2013 I did found that every time I browse an hdd on web interface ( i.e. /Main/Browse?dir=/mnt/disk1 ) I do get error lines printed on console like: /file_path.... user.LOCATION: No such attribute Using simple features? or another webGui-changing add-on? That may be the problem. Quote Link to comment
limetech Posted June 12, 2013 Author Share Posted June 12, 2013 no, no addons at all. Ok, there's a bug, but it happens to work on my test system Do you know 'vi'? If so, edit the file /usr/local/emhttp/plugins/indexer/Browse.php and change line 32 which reads: 'disk' => show_disk ? `getfattr --only-values --absolute-names -n user.LOCATION "$path"` : "" ); to 'disk' => $show_disk ? `getfattr --only-values --absolute-names -n user.LOCATION "$path"` : "" ); (add a $ in front of 'show_disk') Then check to see if error message goes away. Quote Link to comment
nars Posted June 12, 2013 Share Posted June 12, 2013 Yes, it sorts it Btw, note that the error lines only seems to show on pc display (I did see them testing on a VM), not on telnet, that's maybe why you could not see them. Quote Link to comment
limetech Posted June 12, 2013 Author Share Posted June 12, 2013 Yes, it sorts it Btw, note that the error lines only seems to show on pc display (I did see them testing on a VM), not on telnet, that's maybe why you could not see them. Damn php $'s in front of variables... Quote Link to comment
garycase Posted June 12, 2013 Share Posted June 12, 2013 So is this a good release? ... or is there going to be a 14a to resolve the "$'s in front of variables" you noted? Also, I have not shut down since installing RC13 (didn't want to encounter the shutdown problem) ==> are there specific instructions for the shutdown/reboot when I switch versions that will reduce the likelihood of this crashing my system? Quote Link to comment
limetech Posted June 12, 2013 Author Share Posted June 12, 2013 So is this a good release? ... or is there going to be a 14a to resolve the "$'s in front of variables" you noted? Also, I have not shut down since installing RC13 (didn't want to encounter the shutdown problem) ==> are there specific instructions for the shutdown/reboot when I switch versions that will reduce the likelihood of this crashing my system? The 'crash' happens during un-mount of the data disks. By this time all data has been 'sync'ed to disk. The worst that can happen is that upon restart the s/w will think there's been an 'unclean' shutdown and start a parity-check. But it's ok to cancel this check because all the data is safe. Quote Link to comment
garycase Posted June 12, 2013 Share Posted June 12, 2013 Thanks Tom. Good to know there's no danger of data corruption from the shutdown (if I even have any issue). I'll upgrade tomorrow ... last thing I want before hitting the sack is a problem with UnRAID !! [Don't expect one ... but Murphy does seem to have a way ...] Does your comment "... Damn php $'s in front of variables... " have anything to do with this release? Wasn't clear to me what that discussion was about. Is this something that's going to result in a 14a "real soon now" to resolve it? Quote Link to comment
limetech Posted June 12, 2013 Author Share Posted June 12, 2013 Does your comment "... Damn php $'s in front of variables... " have anything to do with this release? Wasn't clear to me what that discussion was about. Is this something that's going to result in a 14a "real soon now" to resolve it? It's a minor nit that will be fixed in the next release. Quote Link to comment
NAS Posted June 12, 2013 Share Posted June 12, 2013 Can we post a one liner that users can use to patch this file and save having a new release for some a triviality? Quote Link to comment
johnodon Posted June 12, 2013 Share Posted June 12, 2013 The link at the top of the page needs to be changed. Latest beta release: v5.0-rc13 John Quote Link to comment
Joe L. Posted June 12, 2013 Share Posted June 12, 2013 Can we post a one liner that users can use to patch this file and save having a new release for some a triviality? This should do it: sed -i " s/ show_disk / \$show_disk /" /usr/local/emhttp/plugins/indexer/Browse.php You can put it at the end of your "config/go" script or just run it each time you reboot on the command line. It specifically looks for show_disk proceeded by a space, so it does no harm if run multiple times or on a subsequent repaired file. Quote Link to comment
jumperalex Posted June 12, 2013 Share Posted June 12, 2013 Can we post a one liner that users can use to patch this file and save having a new release for some a triviality? This should do it: sed -i " s/ show_disk / \$show_disk /" /usr/local/emhttp/plugins/indexer/Browse.php You can put it at the end of your "config/go" script or just run it each time you reboot. It specifically looks for show_disk proceeded by a space, si it does no harm if run multiple times or on a subsequent repaired file. Or just run it once in terminal??? EDIT: I suppose not huh? /usr/ is in ram isn't it? So this NEEDS to be run each boot to patch the file in ram? Quote Link to comment
nars Posted June 12, 2013 Share Posted June 12, 2013 Can we post a one liner that users can use to patch this file and save having a new release for some a triviality? This should do it: sed -i " s/ show_disk / \$show_disk /" /usr/local/emhttp/plugins/indexer/Browse.php You can put it at the end of your "config/go" script or just run it each time you reboot. It specifically looks for show_disk proceeded by a space, si it does no harm if run multiple times or on a subsequent repaired file. Or just run it once in terminal??? EDIT: I suppose not huh? /usr/ is in ram isn't it? So this NEEDS to be run each boot to patch the file in ram? correct. Quote Link to comment
neilt0 Posted June 12, 2013 Share Posted June 12, 2013 In rc14, is there a way to permanently enable RAM over 4GB without attaching a monitor? My servers run headless and I don't have a monitor in the server area. Cheers. Quote Link to comment
theone Posted June 12, 2013 Share Posted June 12, 2013 In rc14, is there a way to permanently enable RAM over 4GB without attaching a monitor? My servers run headless and I don't have a monitor in the server area. Cheers. You can edit the syslinux.cfg file Quote Link to comment
johnodon Posted June 12, 2013 Share Posted June 12, 2013 In rc14, is there a way to permanently enable RAM over 4GB without attaching a monitor? My servers run headless and I don't have a monitor in the server area. Cheers. Edit the syslinux.cfg file to look like the below. Notice that "menu default" is moved to the "label unRAID OS" section. default menu.c32 menu title Lime Technology LLC prompt 0 timeout 50 label unRAID OS menu default kernel bzimage append initrd=bzroot label unRAID OS (4G RAM limit) kernel bzimage append initrd=bzroot mem=4095M label Memtest86+ kernel memtest Quote Link to comment
Bitz69 Posted June 12, 2013 Share Posted June 12, 2013 Was the cache removed from from rc14 for basic edition? it didn't show back up as a option after I upgraded. I was growing to really love that option Quote Link to comment
johnodon Posted June 12, 2013 Share Posted June 12, 2013 Updated to RC14 (using the unlimited RAM option). Stopped array and rebooted 3 or 4 times...no hangs/crashes. Running a parity check now. Total size: 2 TB Current position: 53.52 GB (3%) Estimated speed: 102.18 MB/sec Estimated finish: 318 minutes Sync errors corrected: 0 I won't know if OpenELEC plays nicely with the NFS shares until I get home later but I don't expect any issues. John Quote Link to comment
joyless Posted June 12, 2013 Share Posted June 12, 2013 Was the cache removed from from rc14 for basic edition? it didn't show back up as a option after I upgraded. I was growing to really love that option yeah it was. tom stated here that it's rc13 only and it's coming back when cache pool feature is enabled (which i hope is coming sooner rather than later ) Quote Link to comment
Recommended Posts
Join the conversation
You can post now and register later. If you have an account, sign in now to post with your account.
Note: Your post will require moderator approval before it will be visible.