Hi I upgraded from Release 4.5.6 to Release 5.0-beta2 to check it out, and it is cool, but different bugs is giving me trouble, so I would like to downgrade to Release 4.5.6 again, is this possible ?

 

And if it is possible, how do I do it ?

 

Thanx in advance 

Dennis

Hi I upgraded from Release 4.5.6 to Release 5.0-beta2 to check it out, and it is cool, but different bugs is giving me trouble, so I would like to downgrade to Release 4.5.6 again, is this possible ?

 

And if it is possible, how do I do it ?

 

Thanx in advance 

Dennis

All you need to do is put the bzroot and bzimage files from the 4.5.6 release back and reboot.  You can seven rename the existing as bzroot.5b2 and bzimage.5b2 so you can easily switch back  if you find thet reverting to 4.5.6 does not solve your problems. (revert back by re-naming them as bzroot and bzimage, and rebooting)

 

Just curious....  What bugs are you experiencing?  I see no posts from you describing bugs with 5.0-b2.  Have they been reported as 5.0beta2 bugs by somebody else?  If not, and you keep them to yourself, then they'll not get fixed until somebody else has them occur on their server.

 

Joe L.

Thanx for the quick answer

 

I am doing a full bug report after trying out the beta for a 2 weeks now, and I will post it in the Beta forum 

 

Just one more question:

 

I am comparing the structure from  5.0-beta2 to Release 4.5.6 and there is a different structure in the "config" folder.

The "config" folder on 5.0-beta2 has an extra file named "drift" when comparing to the "config" folder on the 4.5.6 Release.

 

Should I just ignore that file when reverting back or should / could I delete it without doing any damage to my unRAID ?

 

Best Regards

Dennis

Thanx for the quick answer

 

I am doing a full bug report after trying out the beta for a 2 weeks now, and I will post it in the Beta forum 

That will help Tom

Just one more question:

 

I am comparing the structure from  5.0-beta2 to Release 4.5.6 and there is a different structure in the "config" folder.

The "config" folder on 5.0-beta2 has an extra file named "drift" when comparing to the "config" folder on the 4.5.6 Release.

 

Should I just ignore that file when reverting back or should / could I delete it without doing any damage to my unRAID ?

 

Best Regards

Dennis

I think you can ignore it.  It sounds as if the nntp package is using it to track how much your clock chip on your motherboard drifts. 

Hi I now downgraded and everything went fine, I choose to remove the "drift" file as well 

 

But now I am encountering a problem, my unRAID server is exporting my user shares, as before the upgrade and downgrade, but besides that it is exporting all my drives as separate drives ?

 

It should only be exporting my user shares for read/write, so I am at a loss here, did something go wrong in the upgrade / downgrade process or am I missing something ?

 

Best Regards

Dennis

Hi I now downgraded and everything went fine, I choose to remove the "drift" file as well 

 

But now I am encountering a problem, my unRAID server is exporting my user shares, as before the upgrade and downgrade, but besides that it is exporting all my drives as separate drives ?

 

It should only be exporting my user shares for read/write, so I am at a loss here, did something go wrong in the upgrade / downgrade process or am I missing something ?

 

Best Regards

Dennis

You just need to set your "disk" shares to not export.  It is on the shares page as

Disk shares (SMB):

you probably have the set to export.  It is a setting you control.  Many of us set it to

Hidden read/write

so we can explicitly move files to specific disks as long as we use the full path in window's file explorer.

Damn man, you are a savior 

 

That did the trick, funny that downgrading caused this, well I will ad it to my "bug" list, not even sure that it can be considered a bug....

 

Well thanks again 

 

Best Regards

Dennis