Comments for blog.yo61.com http://blog.yo61.com Web Operations & System Administration in the wilds of North Yorkshire Mon, 13 May 2013 19:48:35 +0000 hourly 1 http://wordpress.org/?v=3.5.1 Comment on Building RPMs from ruby gems with fpm by Building RPMs from Ruby gems « blog.yo61.com http://blog.yo61.com/building-rpms-from-ruby-gems-with-fpm.html/comment-page-1#comment-3253 Building RPMs from Ruby gems « blog.yo61.com Mon, 13 May 2013 19:48:35 +0000 http://blog.yo61.com/?p=354#comment-3253 [...] see my recent post describing a better way to do [...]

]]> Comment on Mount NFS 4 shares from OSX by Robin Bowes http://blog.yo61.com/mount-nfs4-shares-from-osx.html/comment-page-1#comment-3240 Robin Bowes Sat, 11 May 2013 16:20:07 +0000 http://yo61.com/?p=321#comment-3240 This was on Mountain Lion.

]]> Comment on Mount NFS 4 shares from OSX by Petter Blomberg http://blog.yo61.com/mount-nfs4-shares-from-osx.html/comment-page-1#comment-3239 Petter Blomberg Sat, 11 May 2013 13:47:38 +0000 http://yo61.com/?p=321#comment-3239 Which version of OSX are you using?
On snow leopard, I’m getting this:
mount_nfs: sorry, you must specify vers=4.0alpha to use the alpha-quality NFSv4 support

]]> Comment on Samsung Note 2 freezing – here’s the fix by Robin Bowes http://blog.yo61.com/samsung-note-2-freezing-heres-the-fix.html/comment-page-1#comment-3141 Robin Bowes Fri, 26 Apr 2013 09:11:12 +0000 http://blog.yo61.com/?p=337#comment-3141 Arnold,

No, I didn’t make any writes that big – the internal flash is pretty full.

However, I’ve recently had an OTA update and the device has been stable for some time now.

Currently on:
4.1.2
N7100XXDLK7
3.0.31-1071214
se.infra@SEP-117 #1
SMP PREEMPT Wed Mar 27 10:33:53 KST 2013
JZO54K.N7100XXDMC3

R.

]]> Comment on Samsung Note 2 freezing – here’s the fix by Arnold http://blog.yo61.com/samsung-note-2-freezing-heres-the-fix.html/comment-page-1#comment-3140 Arnold Fri, 26 Apr 2013 09:06:05 +0000 http://blog.yo61.com/?p=337#comment-3140 For the dummy file method, have you succeeded in making several 2x8gb write without any freeze yet?

I also found that post and tried the method. Along with all the other solution possible I can find. It is seem now to be a bit better, One thing also they said when you got the freeze, do not hard reset or remove battery as it will make it worst. Just wait for it to unfreeze (2-25 minutes) and hopefully it will get better with each and each automatic unfreeze.

]]> Comment on Samsung Note 2 freezing – here’s the fix by Robin Bowes http://blog.yo61.com/samsung-note-2-freezing-heres-the-fix.html/comment-page-1#comment-3039 Robin Bowes Fri, 12 Apr 2013 19:27:35 +0000 http://blog.yo61.com/?p=337#comment-3039 Damn. I spoke too soon. It's still freezing. :(

]]> Comment on Updating Dell iDRAC6 firmware on linux by Robin Bowes http://blog.yo61.com/updating-dell-idrac6-firmware-linux.html/comment-page-1#comment-2917 Robin Bowes Thu, 14 Mar 2013 09:08:26 +0000 http://yo61.com/?p=228#comment-2917 Try using bash instead of sh?

What OS is this on? The article didn’t say, but I was running on CentOS 5.x which symlinks /bin/sh -> bash.

R.

]]> Comment on Updating Dell iDRAC6 firmware on linux by Sakhi http://blog.yo61.com/updating-dell-idrac6-firmware-linux.html/comment-page-1#comment-2916 Sakhi Thu, 14 Mar 2013 07:48:59 +0000 http://yo61.com/?p=228#comment-2916 I tried to follow your steps to update our PowerEdge R510 firmware. But it's failing with the below error:
 
root@skipper:/tmp/dell# sh IDRAC6_FRMW_LX_R299265.BIN –extract ./idrac6-1.70.21IDRAC6_FRMW_LX_R299265.BIN: 38: [: Linux: unexpected operator
IDRAC6_FRMW_LX_R299265.BIN: 52: IDRAC6_FRMW_LX_R299265.BIN: typeset: not found
IDRAC6_FRMW_LX_R299265.BIN: 53: IDRAC6_FRMW_LX_R299265.BIN: typeset: not found
IDRAC6_FRMW_LX_R299265.BIN: 56: IDRAC6_FRMW_LX_R299265.BIN: typeset: not found
IDRAC6_FRMW_LX_R299265.BIN: 57: IDRAC6_FRMW_LX_R299265.BIN: typeset: not found
IDRAC6_FRMW_LX_R299265.BIN: 58: IDRAC6_FRMW_LX_R299265.BIN: typeset: not found
IDRAC6_FRMW_LX_R299265.BIN: 59: IDRAC6_FRMW_LX_R299265.BIN: typeset: not found
IDRAC6_FRMW_LX_R299265.BIN: 97: IDRAC6_FRMW_LX_R299265.BIN: typeset: not found
IDRAC6_FRMW_LX_R299265.BIN: 100: IDRAC6_FRMW_LX_R299265.BIN: typeset: not found
IDRAC6_FRMW_LX_R299265.BIN: 103: IDRAC6_FRMW_LX_R299265.BIN: typeset: not found
IDRAC6_FRMW_LX_R299265.BIN: 104: IDRAC6_FRMW_LX_R299265.BIN: typeset: not found
IDRAC6_FRMW_LX_R299265.BIN: 105: IDRAC6_FRMW_LX_R299265.BIN: typeset: not found
IDRAC6_FRMW_LX_R299265.BIN: 108: IDRAC6_FRMW_LX_R299265.BIN: typeset: not found
IDRAC6_FRMW_LX_R299265.BIN: 109: IDRAC6_FRMW_LX_R299265.BIN: typeset: not found
IDRAC6_FRMW_LX_R299265.BIN: 110: IDRAC6_FRMW_LX_R299265.BIN: typeset: not found
IDRAC6_FRMW_LX_R299265.BIN: 111: IDRAC6_FRMW_LX_R299265.BIN: typeset: not found
IDRAC6_FRMW_LX_R299265.BIN: 112: IDRAC6_FRMW_LX_R299265.BIN: typeset: not found
IDRAC6_FRMW_LX_R299265.BIN: 113: IDRAC6_FRMW_LX_R299265.BIN: typeset: not found
IDRAC6_FRMW_LX_R299265.BIN: 116: IDRAC6_FRMW_LX_R299265.BIN: typeset: not found
IDRAC6_FRMW_LX_R299265.BIN: 117: IDRAC6_FRMW_LX_R299265.BIN: typeset: not found
IDRAC6_FRMW_LX_R299265.BIN: 118: IDRAC6_FRMW_LX_R299265.BIN: typeset: not found
IDRAC6_FRMW_LX_R299265.BIN: 119: IDRAC6_FRMW_LX_R299265.BIN: typeset: not found
IDRAC6_FRMW_LX_R299265.BIN: 120: IDRAC6_FRMW_LX_R299265.BIN: typeset: not found
IDRAC6_FRMW_LX_R299265.BIN: 121: IDRAC6_FRMW_LX_R299265.BIN: typeset: not found
IDRAC6_FRMW_LX_R299265.BIN: 122: IDRAC6_FRMW_LX_R299265.BIN: typeset: not found
IDRAC6_FRMW_LX_R299265.BIN: 123: IDRAC6_FRMW_LX_R299265.BIN: typeset: not found
IDRAC6_FRMW_LX_R299265.BIN: 124: IDRAC6_FRMW_LX_R299265.BIN: typeset: not found
IDRAC6_FRMW_LX_R299265.BIN: 125: IDRAC6_FRMW_LX_R299265.BIN: typeset: not found
IDRAC6_FRMW_LX_R299265.BIN: 126: IDRAC6_FRMW_LX_R299265.BIN: typeset: not found
IDRAC6_FRMW_LX_R299265.BIN: 129: IDRAC6_FRMW_LX_R299265.BIN: typeset: not found
IDRAC6_FRMW_LX_R299265.BIN: 130: IDRAC6_FRMW_LX_R299265.BIN: typeset: not found
IDRAC6_FRMW_LX_R299265.BIN: 131: IDRAC6_FRMW_LX_R299265.BIN: typeset: not found
IDRAC6_FRMW_LX_R299265.BIN: 132: IDRAC6_FRMW_LX_R299265.BIN: typeset: not found
IDRAC6_FRMW_LX_R299265.BIN: 133: IDRAC6_FRMW_LX_R299265.BIN: typeset: not found
IDRAC6_FRMW_LX_R299265.BIN: 134: IDRAC6_FRMW_LX_R299265.BIN: typeset: not found
IDRAC6_FRMW_LX_R299265.BIN: 135: IDRAC6_FRMW_LX_R299265.BIN: typeset: not found
IDRAC6_FRMW_LX_R299265.BIN: 138: IDRAC6_FRMW_LX_R299265.BIN: typeset: not found
IDRAC6_FRMW_LX_R299265.BIN: 141: IDRAC6_FRMW_LX_R299265.BIN: typeset: not found
IDRAC6_FRMW_LX_R299265.BIN: 144: IDRAC6_FRMW_LX_R299265.BIN: typeset: not found
IDRAC6_FRMW_LX_R299265.BIN: 147: IDRAC6_FRMW_LX_R299265.BIN: typeset: not found
IDRAC6_FRMW_LX_R299265.BIN: 148: IDRAC6_FRMW_LX_R299265.BIN: typeset: not found
IDRAC6_FRMW_LX_R299265.BIN: 149: IDRAC6_FRMW_LX_R299265.BIN: typeset: not found
IDRAC6_FRMW_LX_R299265.BIN: 150: IDRAC6_FRMW_LX_R299265.BIN: typeset: not found
IDRAC6_FRMW_LX_R299265.BIN: 151: IDRAC6_FRMW_LX_R299265.BIN: typeset: not found
IDRAC6_FRMW_LX_R299265.BIN: 152: IDRAC6_FRMW_LX_R299265.BIN: typeset: not found
IDRAC6_FRMW_LX_R299265.BIN: 155: IDRAC6_FRMW_LX_R299265.BIN: typeset: not found
IDRAC6_FRMW_LX_R299265.BIN: 156: IDRAC6_FRMW_LX_R299265.BIN: typeset: not found
IDRAC6_FRMW_LX_R299265.BIN: 157: IDRAC6_FRMW_LX_R299265.BIN: typeset: not found
IDRAC6_FRMW_LX_R299265.BIN: 158: IDRAC6_FRMW_LX_R299265.BIN: typeset: not found
IDRAC6_FRMW_LX_R299265.BIN: 159: IDRAC6_FRMW_LX_R299265.BIN: typeset: not found
IDRAC6_FRMW_LX_R299265.BIN: 160: IDRAC6_FRMW_LX_R299265.BIN: typeset: not found
IDRAC6_FRMW_LX_R299265.BIN: 161: IDRAC6_FRMW_LX_R299265.BIN: typeset: not found
IDRAC6_FRMW_LX_R299265.BIN: 162: IDRAC6_FRMW_LX_R299265.BIN: typeset: not found
IDRAC6_FRMW_LX_R299265.BIN: 163: IDRAC6_FRMW_LX_R299265.BIN: typeset: not found
IDRAC6_FRMW_LX_R299265.BIN: 193: IDRAC6_FRMW_LX_R299265.BIN: typeset: not found
IDRAC6_FRMW_LX_R299265.BIN: 263: [: Linux: unexpected operator
IDRAC6_FRMW_LX_R299265.BIN: 959: IDRAC6_FRMW_LX_R299265.BIN: typeset: not found
IDRAC6_FRMW_LX_R299265.BIN: 960: IDRAC6_FRMW_LX_R299265.BIN: typeset: not found
IDRAC6_FRMW_LX_R299265.BIN: 963: [: Linux: unexpected operator
IDRAC6_FRMW_LX_R299265.BIN: 969: IDRAC6_FRMW_LX_R299265.BIN: typeset: not found
IDRAC6_FRMW_LX_R299265.BIN: 970: IDRAC6_FRMW_LX_R299265.BIN: typeset: not found
IDRAC6_FRMW_LX_R299265.BIN: 971: IDRAC6_FRMW_LX_R299265.BIN: typeset: not found
IDRAC6_FRMW_LX_R299265.BIN: 976: IDRAC6_FRMW_LX_R299265.BIN: typeset: not found
IDRAC6_FRMW_LX_R299265.BIN: 977: IDRAC6_FRMW_LX_R299265.BIN: typeset: not found
IDRAC6_FRMW_LX_R299265.BIN: 1000: IDRAC6_FRMW_LX_R299265.BIN: typeset: not found
IDRAC6_FRMW_LX_R299265.BIN: 1001: IDRAC6_FRMW_LX_R299265.BIN: typeset: not found
IDRAC6_FRMW_LX_R299265.BIN: 1004: IDRAC6_FRMW_LX_R299265.BIN: typeset: not found
IDRAC6_FRMW_LX_R299265.BIN: 1006: IDRAC6_FRMW_LX_R299265.BIN: typeset: not found
IDRAC6_FRMW_LX_R299265.BIN: 1007: [: -eq: unexpected operator
IDRAC6_FRMW_LX_R299265.BIN: 1019: IDRAC6_FRMW_LX_R299265.BIN: typeset: not found
IDRAC6_FRMW_LX_R299265.BIN: 943: IDRAC6_FRMW_LX_R299265.BIN: typeset: not found
IDRAC6_FRMW_LX_R299265.BIN: 1141: IDRAC6_FRMW_LX_R299265.BIN: arithmetic expression: expecting primary: "_LIMIT++"
IDRAC6_FRMW_LX_R299265.BIN: 353: IDRAC6_FRMW_LX_R299265.BIN: typeset: not found
sleep: missing operand
Try `sleep –help' for more information.
 
 
Please help
 

]]> Comment on Dell DRAC BBU auto-learn tests kill disk performance by Andy Agarwal http://blog.yo61.com/dell-drac-bbu-auto-learn-tests-kill-disk-performance.html/comment-page-1#comment-2904 Andy Agarwal Thu, 07 Mar 2013 16:56:00 +0000 http://yo61.com/?p=152#comment-2904 We've been bitten by this too and also learned the hard way that disabling the learn cycle does not help. In our case it seemed like the controller had a wrong estimation of battery health and it disabled write caching without warning
http://en.community.dell.com/support-forums/servers/f/906/p/19491953/20303835.aspx

]]> Comment on Dell OMSA on CentOS 5.4 x86_64 – No Controllers found error by Mimi http://blog.yo61.com/dell-omsa-on-centos-5-4-x86_64-no-controllers-found-error.html/comment-page-1#comment-2608 Mimi Tue, 20 Nov 2012 20:49:24 +0000 http://yo61.com/?p=135#comment-2608 Hi Sphinx Khan,You raise a good point: as both are Linux distros, I don’t think they’ll difefr much w.r.t performance if not for their difefrences in defaults for such things like filesystems etc. I haven’t benchmarked them to compare the two on the same hardware, nor have I found a benchmark that compares the two, so I can’t really say if there’s a difefrence.As for security: the security of any server depends on the services running on the server and how they’re set up. It is possible to set up a very tight server with either distro, just as it is possible to set up a very leaky server with either distro. Personally, I find the Debian documentation for securing a server better w.r.t. accessibility, findability and thoroughness, but that might just be because I have more experience with Debian than I do with CentOS.W.r.t. the user community: both have a very wide and very active user community and, as both are Linux distros, there is some overlap between the two communities.Thanks for the comment,Ronald

]]>