nars

It's normal it shows "File sytem type: unknown" when array is stopped.

All files... except menu.c32 else you may potentially cause the problem I described above... best procedure IMO is replace just bzimage, bzroot, readme.txt and syslinux.cfg.

This is from the first page in the thread - can you clarify please?: If you are currently running unRAID Server OS release 5.0-rc16c: ---------------------------------------------------------------- - Copy over 'bzimage', 'bzroot', and 'readme.txt' from the release zip file to your Flash and then reboot your server. If you are currently running an earlier unRAID Server OS 5.0-beta or 5.0-rc release: ------------------------------------------------------------------------------------ - Probably the best thing to do is backup your Flash, reformat, re-install, restore 'config' directory, and then reboot. I think Tom was trying to be conservative, and simplify the instructions, and perhaps he oversimplified. At some point, many long time UnRAID users have had to reformat and use make_bootable.bat, and it hasn't been predictable as to which upgrade it would occur for a particular user. What I would recommend is try copying the 3 files and reboot, and only if that doesn't work, go through the longer procedure. The one thing i would add to his instructions is that if you are upgrading from a much older release, say one of the v5.0 betas, you also need to run the Permissions tool on the Utility Menu. As far as I can understand, such issue RobJ refer that happened to a few users, months ago, with syslinux hanging at boot and not even showing menu, after upgrading, was caused because they apparently updated menu.c32 binary (some user confirmed it - wrongly thinking it was related to the new menu options, and maybe others just replaced all root files even...) without updating whole syslinux. It caused the problem as users ended with older syslinux version "installed" and menu.c32 binary from new syslinux version that were apparently not compatible... Deleting ldlinux.sys (that is created by make_bootable.bat and not included in unraid zip) is also probably bad idea, and may be easy mistake, for eg. if user wrongly deletes all root files from pen first and copy new ones from the zip... If user replaces just the 3 files (bzimage, bzroot and readme.txt... and... syslinux.cfg if wanting to get the new boot menu options...), and don't touch syslinux binaries at all, there should be no problems. Older syslinux should be able to boot any new bzimage without issues... I use an older syslinux myself on my unraid pen just because I don't bother updating it... it does it's task why should I bother? But I perfectly understand Tom, probably for support reasons, really trying to simplify it to the max., make sure users will do it simple and get the most clean thing possible. If user wants to do it by an unofficial way just because it's easier for him, to avoid needing to get the pen out of the server for eg., it's his own responsibility...

Are you using 5.0 final? AFAIK this problem was only present on rc11 and fixed on rc11a ( http://lime-technology.com/forum/index.php?topic=25609.msg222966#msg222966 ), and I did just tested now on 5.0 final and can't reproduce it, i.e. if I insert "aaa bbb" as FTP user(s) and then look at vsftpd.user_list I can see: aaa bbb then spaces are replaced by new lines, as they should. Also not sure if Simplefeatures or any other plugin that "hacks" webgui could somehow break this, may be worth checking, if you are using it...

If you already have the new webgui (i.e. if you manually "installed" it before upgrading unraid) I think you will not see that icon. Else if you really have 5.0 final with stock webgui you should see it.

See: http://lime-technology.com/forum/index.php?topic=28087.msg249430#msg249430

You are not alone If you noticed my post some pages back in this thread I did got same results you got... then unless there is something specific that may trigger it I can also not understand or reproduce it anymore on 5.0 final. I was curious about that issue as I reported it back on rc16c, did even asked on a post back in this thread what exact steps to reproduce it, but got no reply at all... and one of the posts about it from Patilan apparently disappeared, despite there are still quotes of it on this thread, then I can't understand if Patilan reported it by mistake and then removed it or what happened really..!?

Something strange... I did myself reported "1st parity check is always correcting" for rc16, it's posted on issues forum, i.e. the problem was actually present on rc16, but I can't reproduce it myself anymore on final. What exact steps you did to reproduce it? The problem that seems back on 5.0 final is the one after using "Parity is already valid." option... but that's a different one... P.S. I'm using stock gui, not sure if it does any difference.

Thanks and congratulations Tom, IMO I think you made the right decision to release just what most have been waiting for all this time and that proved to be stable by all the ones testing it... you have now all the time to look at new gui improve it etc. Btw, I think I did found a (returned) bug... see issues forum... maybe you should (please don't take this as criticism but as a suggestion for future...) have made one last rc, before release 5.0 final, to make absolute sure all 100%... then just rename rc to final as-is, with zero changes... but anyway it's not the end of the world and other small bugs may eventually arise and new versions should come, etc...

I have the file... could upload it to you no problem but I can tell you that you will not be able to compile the needed modules to use it with recent kernels on recent unraid versions... I would recommend you try virtualbox instead, much better support and works fine, search for it on the forum.

There are at least two bugs found after rc16c, "Modified Time not being set properly." and "cannot do non-correcting parity check after array stop/start.", posted on issues section, and in some specific situations these can be seen as moderately important issues, then rc16c is not exactly 5.0 final.

+1 again (like I posted on "Status - update" thread that is now closed) to release 5.0 as-is (with any known bugs fixed... this makes a difference not just rename rc16 to final as said above... there are at least two bugs found after rc16c, "Modified Time not being set properly." and "cannot do non-correcting parity check after array stop/start.") and add new gui on 5.1.

Yes, I'm a bit new here, 1 year, but "did the homework" and did read a lot over the forum before starting to post, then it's like I have been there for more time but got it on a concentrated way

Exactly, but I guess most comments from users (me included) opposing to new gui being added on last minute to 5.0 suppose that new gui may not be a plugin for final (i.e. being a plugin only now for testing), and no old gui may exist or be supported at all anymore, as I don't see Tom maintaining two gui's, would be no sense. Also the comments are not exactly against new design but against adding it last minute to 5.0, a version that was being polished for 2 years now, rc's are supposed to fix bugs only. Releasing it as-is and separate official plugin for now as Joe L. purposed would be an wise thing IMO, still screenshots and market things may be done with plugin installed, and even preinstall it on complete servers and ready to go pens. Later on 5.1 think on merge them as stock and eventually discontinue old gui. I don't see a reason to need to madly add all features on 5.0, supposing that it will not be last unraid version, 5.1, 5.2, etc will come, and doesn't necessarily need to take years for that.

I agree. It is FAR to late in the "rc" process to add a "half-baked" implementation of either simple-features and plugin-manager. Please release 5.0 WITHOUT the package manager/SF skin (which apparently breaks functions in existing SF instals), and then release the package-manager/simple-features plugin as an add-on that can optionally be applied. (it can then be tweaked until it no longer is "half-baked" (fully baked?)) +1 Definitely agree. I was surprised to see this change appear at this late point in the release cycle; and quite frankly am quite satisfied with the stock GUI. I thought RC16c was VERY close to being "final", with only a few minor issues to be resolved ==> changing the UI certainly seems to add nothing except higher risk to the stability. Also +1 that, with all respect to speeding_ant work, think it's crazy to do such changes on an rc... at this point... after 5.0 being polished for... 2 years? ok, only gui changes... still we can't say for sure that nothing can eventually get broken, even "cosmetically" talking, mainly doing it at rush. And imo it's strange ppl waiting something to go final as-is for 2 years and then suddenly release a different thing... I do like Joe L. idea to release new gui as separate (still official) plugin, for now, it will please all users (the ones that want it and the ones that don't want it) and even give speeding_ant more liberty to work on it, polish it, update it, with more time, etc. If later Tom wants to integrate it on stock, think on it for 5.1 or so... don't see why it needs to be on 5.0? I understand you may want a shiny gui to sell, maybe mainly on complete servers or pens fully ready for end user that is not an expert, if that is the case you can just integrate the separate plugin as default for these, if user doesn't want it or something.. then just needs to delete a plg file and reboot anyway.

No problem, fully understand it.

Sure, I understand. I did posted it just as a test script for anyone else having same trouble and wanting to try it... I did never even said anyone to add them on go file, but I can just edit my post and remove them to avoid future problems (feel free to remove quotes of it). Btw, what about I just add them on a .plg file that will "hack" normal webgui plugin, i.e. using same sed lines? or you don't really want that sort of hacks even from a .plg?

I did it on 'sed' lines just to make it easy to apply on future versions changing only really required lines, not just replacing whole css file by an old patched one that could obviously easily break something... you see what I mean... but I fully understand your idea for not liking "non standard mess" on go file.

I did found a problem, not sure if related to new gui or just a bug on latest rc's and didn't noticed it before? apparently right after starting array I'm unable to do a NOCORRECT parity check. Please anyone else can try these steps and confirm this: - stop array - start array - uncheck "Write corrections to parity disk" - start parity check isn't "Write corrections to parity disk" checkbox checked again? (and looking at syslog it is doing a 'check CORRECT') Then if I stop the parity check, uncheck Write corrections to parity disk" checkbox and try again I can't reproduce it again, until stop/start array, that's why I think it only happens on first time we attempt it right after starting array. Edit: I did now tested and can reproduce it on stock rc16c, on both baremetal and vmware workstation, then not related at all with the new gui... you may want to move it to issues... Also note that it doesn't happen after boot (with array auto-start), just after a stop/start as I did mention above.

Thanks

In part I understand you zoggy, but I would not go that far asking that, if header and bottom status is not always there, sticky, you just scroll a bit and you should have a lot of space to show whatever you want, like all hdd's (or almost in case of really many) even on small on screens... I think. Btw, one last suggestion, I was to ask that before but didn't wanted to be annoying for something that will probably not be useful for all... but now seeing that a lot of display options got added... would it be possible to add one more option to allow showing temperature for spindown disks? I know that many hdd's will wake with that... but some doesn't, I'm sure that at least wd red ones doesn't as sometimes I manually pool them manually with smartctl.

Yes, it appears like a frames page that's why I called it "frames-like" despite not using frames, but yes, exactly that Btw I did attached a screenshot of it on 800x600 after my small changes, you can see it is ok, and before changes it was a real pain to browse it as top header and the white space at bottom for status did take half screen... Again I recon there should be very very small % of users browsing it on 800x600 nowadays, but even on 1024x768 and similar it is not very confortable as PeterB and Dephcon also said above. Ah, just to add, I did also disabled the banner image as many also commented as it looks really bad along with the new design, just white background is surely a lot better. And one small suggestion: the top left lime-tech logo, I would prefer it to link to the 'Main' tab instead of limetech site (you could link site somewhere else... like on bottom copyright bar...), just because I'm used on many sites to click site logo to go to home/start page... big thing, easy to click to get home... sometimes I click it by mistake intending to go to start page but maybe just a bad habit I got from some sites, not sure And a small issue I did found on 'Info' on vmware workstation: System: Intel Corporation - 440BX Desktop Reference Platform CPU: 00000000000000000000000000000000 - Unknown Cache: 16 kB, 4096 kB, 16 kB, 4096 kB, 16 kB, 4096 kB, 16 kB, 4096 kB, 16 kB, 4096 kB, 16 kB, 4096 kB, 16 kB, 4096 kB, 16 kB, 4096 kB, 16 kB, 4096 kB, 16 kB, 4096 kB, 16 kB, 4096 kB, 16 kB, 4096 kB, 16 kB, 4096 kB, 16 kB, 4096 kB, 16 kB, 4096 kB, 16 kB, 4096 kB, 16 kB, 4096 kB, 16 kB, 4096 kB, 16 kB, 4096 kB, 16 kB, 4096 kB, 16 kB, 4096 kB, 16 kB, 4096 kB, 16 kB, 4096 kB, 16 kB, 4096 kB, 16 kB, 4096 kB, 16 kB, 4096 kB, 16 kB, 4096 kB, 16 kB, 4096 kB, 16 kB, 4096 kB, 16 kB, 4096 kB, 16 kB, 4096 kB, 16 kB, 4096 kB, 16 kB, 4096 kB, 16 kB, 4096 kB, 16 kB, 4096 kB, 16 kB, 4096 kB, 16 kB, 4096 kB, 16 kB, 4096 kB, 16 kB, 4096 kB, 16 kB, 4096 kB, 16 kB, 4096 kB, 16 kB, 4096 kB, 16 kB, 4096 kB, 16 kB, 4096 kB, 16 kB, 4096 kB, 16 kB, 4096 kB, 16 kB, 4096 kB, 16 kB, 4096 kB, 16 kB, 4096 kB, 16 kB, 4096 kB, 16 kB, 4096 kB, 16 kB, 4096 kB, 16 kB, 4096 kB, 16 kB, 4096 kB, 16 kB, 4096 kB, 16 kB, 4096 kB, 16 kB, 4096 kB, 16 kB, 4096 kB, 16 kB, 4096 kB, 16 kB, 4096 kB, 16 kB, 4096 kB, 16 kB, 4096 kB, 16 kB, 4096 kB, 16 kB, 4096 kB Memory: 512 Module (max. 1024 GB) Network: eth0: 10000Mb/s - Full Duplex Connections: Zero Uptime:0 days, 10:33:43

I do fully agree with PeterB and Dephcon comments above, the new frames-like gui is a real pain, mainly for small screens with low resolutions. You may not believe it but on one of my pc's, with xp, I still use 800x600, with an old crt, and I do often browse unraid gui from it, I know... I know... that almost no users probably use this res. nowadays... and I will not ask you support it. But even browsing it on larger screen honestly I don't like the frames*like gui always taking a lot of screen space for no reason, sorry. I did made a small script to apply some very very simple css changes that fixes it (i.e. remove the frames-like thing, shorten side padding and remove res limitation) for me (even making it reasonable for 800x600, with some wraping for sure, but still reasonable and avoiding scroll): #!/bin/bash sed -i '/#page-container {/,/}/ s/^[ \t]*position:/#&/' /usr/local/emhttp/plugins/webGui/css/default_layout.css sed -i '/#page-container {/,/}/ s/^[ \t]*top:/#&/' /usr/local/emhttp/plugins/webGui/css/default_layout.css sed -i '/#page-container {/,/}/ s/^[ \t]*bottom:/#&/' /usr/local/emhttp/plugins/webGui/css/default_layout.css sed -i '/#page-container {/,/}/ s/^[ \t]*left:/#&/' /usr/local/emhttp/plugins/webGui/css/default_layout.css sed -i '/#page-container {/,/}/ s/^[ \t]*right:/#&/' /usr/local/emhttp/plugins/webGui/css/default_layout.css sed -i '/#page-container {/,/}/ s/^[ \t]*overflow-x:/#&/' /usr/local/emhttp/plugins/webGui/css/default_layout.css sed -i '/#page-container {/,/}/ s/^[ \t]*overflow-y:/#&/' /usr/local/emhttp/plugins/webGui/css/default_layout.css sed -i '/#page-container {/,/}/ s/^\([ \t]*padding-left:\).*/\1 5px;/' /usr/local/emhttp/plugins/webGui/css/default_layout.css sed -i '/#page-container {/,/}/ s/^\([ \t]*padding-right:\).*/\1 5px;/' /usr/local/emhttp/plugins/webGui/css/default_layout.css sed -i '/#header-container {/,/}/ s/^\([ \t]*padding-left:\).*/\1 5px;/' /usr/local/emhttp/plugins/webGui/css/default_layout.css sed -i '/#header-container {/,/}/ s/^\([ \t]*padding-right:\).*/\1 5px;/' /usr/local/emhttp/plugins/webGui/css/default_layout.css sed -i '/#template {/,/}/ s/^\([ \t]*min-width:\).*/\1 780px;/' /usr/local/emhttp/plugins/webGui/css/default_layout.css WARNING: LIMETECH STRONGLY RECOMMENDS THIS SORT OF HACK DON'T BE ADDED ON GO FILE AS IT MAY BRING PROBLEMS WITH FUTURE VERSIONS!!! (note: if anyone else interesting in testing applying these changes, last 5 lines may be unneeded unless also wanting to browse it on 800x600... just 1st 7 lines get rid of the frames-like gui)

http://www.timeanddate.com/countdown/generic?iso=20130803T00&p0=137&csz=1

Normal users can't post on that area that's why I didn't posted there (despite on "General Support [unRAID OS 5.0-rc]" it would be probably more correct...) but some moderator should move it if finds it adequate.