Skip to content
View in the app

A better way to browse. Learn more.

Unraid

A full-screen app on your home screen with push notifications, badges and more.

To install this app on iOS and iPadOS
  1. Tap the Share icon in Safari
  2. Scroll the menu and tap Add to Home Screen.
  3. Tap Add in the top-right corner.
To install this app on Android
  1. Tap the 3-dot menu (⋮) in the top-right corner of the browser.
  2. Tap Add to Home screen or Install app.
  3. Confirm by tapping Install.

unRAID 5.0b6a - "Stable" Beta

Featured Replies

So any of the users we create for SMB/NFS/AFP are really just masked as nobody?

  • Replies 51
  • Views 37.4k
  • Created
  • Last Reply

You do not. It's only for upgrades.

Almost true... 

 

It is ALSO needed if you log in as "root" and move or copy any files between disks using native command line commands or "mc"

That is because they would end up owned by "root" and not visible to the LAN which is logging in as "nobody"

 

Joe L.

 

Hi Joe

 

I am intriqued that you said that. I log into the unraid box as root using putty, and have copied numerous files using MC (but always using the user share paths and not the mnts direct) and the copied files have always been seen on the network without using the permissions utility. So why?

 

Wayne

I can never see files when connecting via FTP.  And I'm logging on as root. Seems weird that they won't show, no?

  • 5 months later...

I want to try the new plugin installer for sabnz sickbeard and also slimserver so want to test 5 latest beta. I have stable 4.7 unraid running.

 

I though best thing maybe to create another usb key with latest 5 on it and keep my 4.7 incase i need to revert.

 

or copy the 4.7 working key to a new key and upgrade that to 5.0

 

THen I can add my plugins

 

Is that the recommended approach?

  • 2 months later...

I want to try the new plugin installer for sabnz sickbeard and also slimserver so want to test 5 latest beta. I have stable 4.7 unraid running.

 

I though best thing maybe to create another usb key with latest 5 on it and keep my 4.7 incase i need to revert.

 

or copy the 4.7 working key to a new key and upgrade that to 5.0

 

THen I can add my plugins

 

Is that the recommended approach?

the v5 read me has the recommended approach. I backed up my 4.7 key and did a fresh install. If I need to go back I can wipe and restore. What I read is you can go back even after running the permissions script.

Good post - since this was shared a while ago, are there any of the betas after 8d that could also be considered a "stable beta"?

 

The reason I ask is that 5.0 Beta 8d contains a fix for the Data Rebuild Bug which is present in prior 5.0 betas as well as 4.7 and prior stable releases (well, depending on Your definition 4.7 might no longer really be considered stable).

 

In Tom's own words, "There's a critical bug fix in this release having to do with data rebuild.  There is a corner case that comes up where, if during a data rebuild of a disabled disk (or disk replaced with a larger one), if a write-request occurs for another disk in the same stripe for the disk currently being rebuilt, it's possible the data for the disk being rebuilt is not actually written.  Later, this will cause a Parity Check 'sync error'. If you are running any previous 5.0-beta release, please upgrade to this release. In addition, I will be updating the 4.7 series (to 4.7.1) with the same parity sync bug fix." (see here: http://lime-technology.com/forum/index.php?topic=13866.0)

 

For me personally, upgrading to a beta release on my production server is against my philosophy, but in this case, since I've been having this data corruption myself, and because 4.7.1 still hasn't come out (been 5 months now), I just might entertain that idea to run a beta to get the Data Rebuild Bug fix.

 

Any takers on post-8d betas? Have people been running one long enough to call is stable (even with the quotation marks..)? Has it been tried with SASLP-MV8 controller? Is there something about a specific issue with an LSI controller?

I've been running beta12a with an IBM BR10i for a couple months now, as beta13/14 have problems with the LSI controllers.

A couple of people have started reporting their experiences with 12a here:

http://lime-technology.com/forum/index.php?topic=16099.0

 

Maybe I'll have a look the 12a release thread when I get the time... I sure with someone would maintain a "Known Issues" list of acknowledged bugs instead of me having to wade through 24 pages of forum posts, trying to wade out user errors from actual bugs to get some kind of overview.

somebody with the right powers should change the title for this thread to 5b12A :P

 

 

somebody with the right powers should change the title for this thread to 5b12A :P

 

 

I beg to disagree.

 

I am running 5b6a on my production machine right now as it has been the most stable for me.

Just so it's clear - beta 6 has the Data Rebuild Bug that Tom disclosed in the beta 8 release notes.

 

Pro, did You have problems with 12a or is it just that You haven't tried it haven't experienced the data rebuild bug Yourself?

Pro, did You have problems with 12a or is it just that You haven't tried it haven't experienced the data rebuild bug Yourself?

I have never hit the data rebuild bug, and I tend not to touch my production server unless I have to.

 

I was running 5b2 but hit a bug (race condition if I remember correctly) after I updated to the faster and beefier Q9300

...and I tend not to touch my production server unless I have to.

 

Me either, man. That's why I've been on the so-called 'stable' release branch until now. The Data Rebuild Bug, which I have run into myself, is the only thing that has me considering running a beta on my production server.

Same here. I just had too much invested in my server to mess with betas. That said, we are up to 5b14 and it's been a long time since 4.7.

  • 3 months later...

Has anyone tried the Supermicro AOC-USAS2-L8i controller with this version of software?

As I recal. Lsi support was not implemented until beta 7x. The. Card might work, but it will not support spindown and temperature support. 

 

 

Thanks for the info, looks like I will hold off a little longer on buying another LSI controller.

  • 5 weeks later...

If one was to start a new build thats not necessarily mission critical--its a home server, but I do want to not constantly worry about crashes and bugs. Best to keep with 4.7 or use one of the 5.0 betas? I do run a mac home so AFP and Time Machine support would be a big deal.

If one was to start a new build thats not necessarily mission critical--its a home server, but I do want to not constantly worry about crashes and bugs. Best to keep with 4.7 or use one of the 5.0 betas? I do run a mac home so AFP and Time Machine support would be a big deal.

 

As long as you don't have a LSI controller use the latest beta (14).

If one was to start a new build thats not necessarily mission critical--its a home server, but I do want to not constantly worry about crashes and bugs. Best to keep with 4.7 or use one of the 5.0 betas? I do run a mac home so AFP and Time Machine support would be a big deal.

 

As long as you don't have a LSI controller use the latest beta (14).

 

Thanks! I don't have a RAID controller card...so I guess I'll go for beta 14.

  • 1 year later...

whats considered to be the best stable beta at the moment?

5.0-rc16c

5.0-rc16c

 

Why do you say rc16c? Isn't the most recent rc rc16b? I notice you mentioned rc16c in the unmenu thread as well...

 

Sent from my Nexus 4 using Tapatalk 2

 

 

I suspect that as a Global Moderator Joe had a bit of insight into the future  :)

 

Note the current release  :)

I suspect that as a Global Moderator Joe had a bit of insight into the future  :)

 

Note the current release  :)

 

Lol... Yeah that's why I asked because I did a search but couldn't find any other references to it other than Joe's.

 

Sent from my Nexus 4 using Tapatalk 2

 

 

Archived

This topic is now archived and is closed to further replies.

Account

Navigation

Search

Search

Configure browser push notifications

Chrome (Android)
  1. Tap the lock icon next to the address bar.
  2. Tap Permissions → Notifications.
  3. Adjust your preference.
Chrome (Desktop)
  1. Click the padlock icon in the address bar.
  2. Select Site settings.
  3. Find Notifications and adjust your preference.