I started many moons ago with a 5.0 beta something.  after several updates and finally 5.0 final, shes a very unstable girl.  All i have running is unmenu, simplefeatures, sicbeard, and sabnzbd.  It seems shfs or smbd will start creeping up in cpu usage till user shares are useless (dies 5-30min into movie/show, cant access the episode from user shares, can still watch the same file from disk1 etc) and then eventually simplefeatures fails to respond, cant unmount smbd shares, and have to shut down the array from unmenu.  The log never shows anything.

 

So i would like to wipe the usb stick and start from scratch with just the official 5.0 final image and my pro key.  What else would i need other than to write down the order of hard drives and maybe user share settings?  I assume it will pick up the user share names on first boot, just with blank settings.

Would be easier to replace bzimage and bzroot with the final version  on your flashdrive and remove the contents out of /config/plugins  and /plugins

 

If you added anything in your GO file you should remove that also (if that doesnt sound familiar you did not do it).

 

Reboot and you are stock again.

I think you should also replace/update your current syslinux.cfg file with the one from v5.0 final. It has the added "Safe Boot" entry for the initial boot screen. That option comes in handy while troubleshooting.

Well I have downloaded the final yesterday,  formated the new flash and put all there. Copyed my config over and removed unmenu references from it.

The new flash boots at first  but once I start the array it starts parity check and eventually all dies. I can see the login prompt on the console but no drive activity and the whole server just drops out of the network. No ip no webste, no share access.

I boot from old flash all is good.

I am comming drom v5 betta13 that have been running all good for 2 years.

 

Sent from my SGH-T889 using Tapatalk 4

 

 

Im going to try one last hope, ditch simple features and its cache plugin, and run the new ui without the dir_cache script.

 

As for the AMD user.  unraid is a 32bit os, and acts "funny" when more than 4gb is used.  For a trial, have your syslinux.cfg file on the root of your usb stick say:

 

label unRAID OS

  menu default

  kernel bzimage

  append mem=4095M initrd=bzroot

 

The mem=4095M will limit the os to the 32bit memory limit.

 

 

PS:  your unraid key for Plus is keyed to the usb stick when you bought the key.  You can not just move your plus.key file to a new stick.  You have to be issued another key from lime-tech.  I assume you knew this but am double checking, i dont know what happens when you pop your key on a new stick...