I'm always one of the slower kids on the block to upgrade and always for the same reason (I need something to support larger hard-drives). 

 

I am currently running UnRaid ver. 4.7

 

I've downloaded and extracted the files from ver. 5.0.5 to a folder on my main computers desktop.

The "readme" file is difficult to read in Notepad, with or without word-wrap on as the text is pushed together with no formatting/spacing.

 

I've taken a copy of the Flash drive from the server (in case I mess things up and need to go back to it).

 

I recall the way I upgraded last time was to just drag and drop some files from the 5.0.5 folder on my main PC, to the Flash drive on the server.  Please verify if this is all that is needed or if I am more files need moving:

bzimage

bzroot

memtest (no necessary, but I would like a newer version)

 

I realize many other releases have come out between 4.7 and 5.0.5 , so is there anything further I need to copy over?

 

I know its not in the file list, but I probably need to update "preclear_disk.sh" as well, as mine is dated Aug.28, 2011. 

 

Any confirmations/direction would be apprecaited before I take the plunge in to ver.5

 

Thanks

....

 

 

I know the title of the page says betas and RCs but the instructions, number 1-5 in the 4.7 sectiion, are the steps you need to follow. Ignore the parts below it that mention the betas and RCs.

 

http://lime-technology.com/wiki/index.php/UnRAID_Server_Version_5.0-beta_Release_Notes

Open the text in WORD or WORDPAD so it wraps.

It might open if you drag it onto a web browser.

 

 

You should SAVE your current flash drive to your PC in its entirety (in case you have to go back)

The new unRAID 5 has a larger 'boot' segment size...you need to run MAKEBOOTABLE (its a script in the new install package)

This may erase your existing files..(that's why you should back up existing config)

 

 

Do *not* just copy a few files...there's a lot of other, smaller changes to support files.

Once you have any of the 5. 0 versions installed, THEN, you only need to update a couple of files to go from 5.01->5.0.3 etc., but the first upgrade from 4.7 to any 5.0.x should be fresh..

At some point during the late 5 betas, syslinux was changed also. It is now a folder instead of just a file. If you decide to copy that also (recommended) then you will need to do make_bootable again. If you don't copy it you will not have the option to boot in safe mode, a mode that allows you to start without loading any addons. This can be very useful for troubleshooting.

 

I think the new syslinux may also be needed for some of the new boot features in the unRAID v6 betas.

The "readme" file is difficult to read in Notepad, with or without word-wrap on as the text is pushed together with no formatting/spacing.

Use Notepad2 or Notepad++ and I think you will find it readable.  Whenever I use windows and want to read a text file created on a linux box I use Notepad2.

 

 

Edit: fix app name

Notepad++ is the windows text editor of choice especially if you need to edit files destined for a *nix platform.

....

 

 

I know the title of the page says betas and RCs but the instructions, number 1-5 in the 4.7 sectiion, are the steps you need to follow. Ignore the parts below it that mention the betas and RCs.

 

http://lime-technology.com/wiki/index.php/UnRAID_Server_Version_5.0-beta_Release_Notes

 

The directions this link provided are for "UnRAID Server Version 5.0-beta Release Notes".

The file I've downloaded is called "unRAIDServer-5.0.5-i386"

 

I realize now that this isn't the simple move a couple files over, which is ok, but based on the other comments, the steps included in this link above aren't necessary for the file I've downloaded.  So, being at 4.7 currently, is their any particular version before 5.0.5 I should install first, then go to 5.0.5?

 

2013-12-07 unRAIDServer-5.0.4-i386.zip

2013-11-26 unRAIDServer-5.0.3-i386.zip

2013-11-18 unRAIDServer-5.0.2-i386.zip

2013-11-13 unRAIDServer-5.0.1-i386.zip

2013-08-28 unRAIDServer-5.0-i386.zip

 

As suggested, I've take an exact copy of the flash drive from the server and stored it on my main PC.

spinbot ---

 

Have a look at this link:

 

    http://lime-technology.com/wiki/index.php/Migrating_from_unRAID_4.7_to_unRAID_5.0

 

This link contains a lot of information and some of it pertains to installs that used a lot of plugins and advanced features of unRAID.  It pretty much covers all of the 'gotchas' that you might encounter. 

spinbot ---

 

Have a look at this link:

 

    http://lime-technology.com/wiki/index.php/Migrating_from_unRAID_4.7_to_unRAID_5.0

 

This link contains a lot of information and some of it pertains to installs that used a lot of plugins and advanced features of unRAID.  It pretty much covers all of the 'gotchas' that you might encounter.

 

Excellent - Thank you!

 

I hate how I always obsessively worry when I do these upgrades or if anything goes wrong with the server.  I think a lot of it has to with not being comfortable working with linux, so unless I have step by step instructions and everything goes exactly as it should, I am presented with doubt.    Fortunately, I am also a trusting guy, so whenever I post a question here and you guys say "do this, this and this", I do it blindly and hope for the best!  lol  The ultimate fear is losing all the data, as it took me soooooo long to convert all my DVD's to HDD, I just can't see spending another year doing it again.

 

Anyways.. I'm going to read through that link now!  Thanks again.  (You'll be hearing from me, I suspect.  If not for this, something else, as my new Parity drive arrived, although its going to take days to pre-clear at 4TB) 

One of the steps, I am not 100% sure of is this one:

 

Go to Users page and re-enter all of your users. If you plan on using SMB and/or AFP with either Secure or Private security mode, you must enter at least one user because the 'root' user name is no longer permitted for network share authentication.

 

Maybe someone can answer this question for me, if I give some information that may be related.  I have two Popcorn Hours as my front-end media centres.  I've always been able to navigate my "TOWER" from my Windows machine and the 11 physical drives and multiple virtual shares that span multiple drives.  Never am I asked to login to any of these drives.

 

So, I know that only "root" ever existed for a login, so I have no other users to add.  Its the part about "using SMB and/or AFP with either secure or private security mode" that I am unsure of how to proceed with.

 

Help...please!

One of the steps, I am not 100% sure of is this one:

 

Go to Users page and re-enter all of your users. If you plan on using SMB and/or AFP with either Secure or Private security mode, you must enter at least one user because the 'root' user name is no longer permitted for network share authentication.

 

Maybe someone can answer this question for me, if I give some information that may be related.  I have two Popcorn Hours as my front-end media centres.  I've always been able to navigate my "TOWER" from my Windows machine and the 11 physical drives and multiple virtual shares that span multiple drives.  Never am I asked to login to any of these drives.

 

So, I know that only "root" ever existed for a login, so I have no other users to add.  Its the part about "using SMB and/or AFP with either secure or private security mode" that I am unsure of how to proceed with.

 

Help...please!

Shares have 3 security levels, Public, Secure, and Private. If you don't set a security level then the share is Public. This means anyone can read/write the share. Secure means anyone can read, but only specified users can write. Private means only specified users can read or write.

One of the steps, I am not 100% sure of is this one:

 

Go to Users page and re-enter all of your users. If you plan on using SMB and/or AFP with either Secure or Private security mode, you must enter at least one user because the 'root' user name is no longer permitted for network share authentication.

 

Maybe someone can answer this question for me, if I give some information that may be related.  I have two Popcorn Hours as my front-end media centres.  I've always been able to navigate my "TOWER" from my Windows machine and the 11 physical drives and multiple virtual shares that span multiple drives.  Never am I asked to login to any of these drives.

 

So, I know that only "root" ever existed for a login, so I have no other users to add.  Its the part about "using SMB and/or AFP with either secure or private security mode" that I am unsure of how to proceed with.

 

Help...please!

 

If you don't understand the initialized part of the quote, you should not have any issues.  (If you don't restrict the share and that takes some work to do so on your part, anonymous users are allowed full access.)  Everything will work exactly as before.  Just be sure that you run the new permissions script and everything will be working for devices like the Popcorn Hours just as it does now.   

If you don't understand the initialized part of the quote, you should not have any issues.  (If you don't restrict the share and that takes some work to do so on your part, anonymous users are allowed full access.)  Everything will work exactly as before.  Just be sure that you run the new permissions script and everything will be working for devices like the Popcorn Hours just as it does now. 

 

I've run the resetting of permissions, as part of the directions in wiki.  I have been able to navigate my physical and virtual shares over the network with my laptop and desktop computers.  I had to add a user called "popcorn" with a password, so I could use those credentials and access "All Media" on my Popcorn Hour.  I've gone in to my new Popcorn Hour C-300's setup and I am able to save the credentials, so everything feels back to normal on it.

 

I clearly see that UnRaid 5.0.5 looks more polished than the old 4.7 I had been running.

 

I have to edit my "go" file, but I don't believe much needs to go back in to it.  I'm not sure I even need the email notification part, as I was using an APC UPS that would alert me when ever power was lost, but that APC UPS died and I am running a CyberPower UPS and its not connected to the server with any form of data cable.  I guess no harm will come from leaving it in there.    The first line, I am unsure of what it was put in for.

cd /boot/packages && find . -name '*.auto_install' -type f -print | sort | xargs -n1 sh -c

 

# This is used to send email notifications to me

echo "[email protected]" >/root/.forward

 

# This will auto-load unmenu

/boot/unmenu/uu

 

If I already have items installed like "UnMenu" and "Preclear_dish.sh", which I hope all work as before, although I guess they are dated now.    I did copy over the newest version of memtest (as it was just a simple drag and drop for the extracted files I had download for this upgrade).  I re-downloaded the lastest preclear_disk.sh and copied it over my older version a well.  UnMenu, looks like its been around for 4 years without any change, so I figure I can just leave it be (as long as I do the edit to the "Go" file, it should load up for me).

 

Ever get that feeling that you are missing something?  Before I venture too far, I am going to play around with things a bit more.  I have some work ahead of me as I have my new parity drive (4TB WD Red) to preclear and then replace my current parity with and then shuffling the old parity drive in to the place of my smallest drive and more work from there.

 

...

cd /boot/packages && find . -name '*.auto_install' -type f -print | sort | xargs -n1 sh -c

...

This line installs the "install on reboot" packages from unMenu Pkg Manager

Thanks for replies.

 

I tested out Putty, to make sure I still have access that way.  After making the changes mentioned, I did a reboot and although I can access UnMenu without issue, the array decided it wants to do a parity check.  I was going to abort it, but seeing as my next task is to pre-clear a new parity drive, i guess having a new parity check done now won't hurt.

Thanks for replies.

 

I tested out Putty, to make sure I still have access that way.  After making the changes mentioned, I did a reboot and although I can access UnMenu without issue, the array decided it wants to do a parity check.  I was going to abort it, but seeing as my next task is to pre-clear a new parity drive, i guess having a new parity check done now won't hurt.

Did you stop the array before you rebooted? You will always get a parity check unless you stop the array before reboot or powerdown.

Did you stop the array before you rebooted? You will always get a parity check unless you stop the array before reboot or powerdown.

 

That is a very good question that I cannot be certain if I did.  I didn't have access to UnMenu at the time (that was what I was rebooting the server for, as I updated my "Go" to automatically load it).  I would normal have used UnMenu to "Reboot".

 

I rebooted the server from the telnet session I had open to the server through Putty, using the "Restart" command.  If I had to bet, I likely did NOT stop the array before doing it.

 

I'm going to bed now anyways, so I was going to say "No harm in letting it run until morning", as its got about 6 hours left, BUT........I am finding my 8 of my 12 drives running hotter than ever reported before, even when the Parity Check ran during the hottest summer days with ambient temperature at 35 Celsius. 

 

Is their any reason my drives would run in the 50C to 59C range with UnRaid 5.0.5, but much cooler with UnRaid 4.7?

 

What's odd is that 4 of the drives are reported as running at 29C to 33C , which might make you believe those drives are my smaller one's and already done their part of the parity check or lower RPM drives.  Two of them are smaller and the other two are equal to the size of most of my other drives.  These two drives are both "WDC_WD15EARS" drives.  I have other model of Western Digital (WDC_WD15EADS) and its running at 58C.  The rest of my drives are Seagate drives.

 

I guess the concern is are some of these drives potentially mis-reporting temperature OR maybe they were being mis-reported all along while running 4.7 and now they are actually showing properly.

 

EDIT:

 

What bad luck I am having today!  I have 3 drive cages (4 drives in 3 bays).  Only 1 of the intake fans was working (which explains why 4 of the drives were running cooler).  I wiggled the power connector and I was able to get a 2nd fan working.  The third fan I cannot see the power connector for (its buried behind too many other SATA / Power cables).  I figured for now ,I would just hook up a regular house fan and have it blow in the front.  Sadly, not long after digging it out from the basement (summer isn't here yet, so fans are packed away), the parity checked haulted due to errors starting to appear on 2 of the drives.  One of these drives also has a "write" count in the 25 billion range, while all the other drives write counts are "10".

 

Not sure how to proceed now with respect to the one drive that caused the system to hault.  The error count on its:  764  , its the write count at 25904530850 that looks even worse.  Is the drive that was "Good", now "Bad" due to the 50-59C temperature I seen it hit.  The other possibility/contributing factor was that I bumped the sata cable enough on one of the drives, or both with errors, in my effort to track down the power cable to the drive cage fans.

 

I've stopped everything and powered down the server.  I checked the connections on all the drives, then powered it back up.  The only drive not to come back up is the one with all the "writes" (mentioned above).  When I go to "Device Status", the drive does appear and automatically appear in the row for "Disk 10", which is the one with the red dot beside it.

 

Here's where things get blurry for me.  I have the options to:

1.  Start will bring the array on-line (array will be unprotected)

2.  Check the box for Maintenance mode - if checked, Start array but do not mount disks.

 

I've done further reading and see the "Restore" option I had in ver 4.7 has been redone so it isn't a simple click (for reasons explained in the manual).    The question I have now is should I try and treat the drive that had the errors as one that needs the data rebuilt on it or do I just start the array back-up like nothing is wrong or do I replace that drive, despite it potentially only having the issues due to my hands poking around in the server while the parity check was running and very likely bumping a sata cable?

 

I am going to bed and await some feedback and stop my guessing for the night!

 

Thanks in advance!

 

 

Odds are you accidentally loosened/dislodged some cables as you moved connectors trying to get your fans running.

UnMenu, looks like its been around for 4 years without any change, so I figure I can just leave it be (as long as I do the edit to the "Go" file, it should load up for me).

Once you get the array running again, in unMENU click on the "Check-for-updates" button on the user-scripts page in it.  Then, click on the subsequent "Install Updates" button.    once the updates install themselves, click on the button to restart-unmenu.  unMENU has had constant changes, you might be surprised at how it now looks.

Odds are you accidentally loosened/dislodged some cables as you moved connectors trying to get your fans running.

 

That is my gut feeling as well.  With that assumption in mind, what is the easiest way to be functional again?  I want to click "Start", but the warning beside it "Start will bring the array on-line (array will be unprotected)." suggests that is not the path to go.  The Device Status does at least show the drive in my "Disk10" position.

 

I did a smart report on the drive and it comes back as "PASSED".  I also checked all my drives, specifically this one and it has a Reallocated_Sector_Ct = 53.  Most of the others are "0" as well, a few with single digits.  Current_Pending_Sector = 0. 

 

Smart Report Attached

 

Would this be the suggested course of action (pulled from another Wiki):

    Stop the array.

    Go to the Main page (Devices in version 4.7) and un-assign the disk.

    Go to the Main page and start the array.

    Stop the array again.

    Go to the Main page and re-assign the disk.

    Go to the Main page - system should indicate there is a "new" drive to replace the disabled one. Check the confirmation box and click Start to start a parity-reconstruct of the disk.

smartctl-report.txt

Open the system and reinsert the disk connections. Apply pressure to all of the SATA cables.  Take care not to loosen anything.

Open the system and reinsert the disk connections. Apply pressure to all of the SATA cables.  Take care not to loosen anything.

 

Ya, I've already done that.  Devices do show all the drives now, its just a question of do i trust its ok and if I do, what steps do I follow to get the array active and protected.

 

EDIT:  I've opted to remove the drive from "Devices", Start the array, Stop the array and then add the drive back, start the array and let parity rebuild the drive.  If I encounter any issue with the rebuild, I will get another drive for it.  Just bad timing as I am just about to have a 2TB drive come free as my next task is to replace the Parity drive with my 4TB one.

Open the system and reinsert the disk connections. Apply pressure to all of the SATA cables.  Take care not to loosen anything.

 

Ya, I've already done that.  Devices do show all the drives now, its just a question of do i trust its ok and if I do, what steps do I follow to get the array active and protected.

 

EDIT:  I've opted to remove the drive from "Devices", Start the array, Stop the array and then add the drive back, start the array and let parity rebuild the drive.  If I encounter any issue with the rebuild, I will get another drive for it.  Just bad timing as I am just about to have a 2TB drive come free as my next task is to replace the Parity drive with my 4TB one.

Continue as you described.  it will reconstruct the drive onto itself.

 

Joe L.

Thanks for the verification.

 

I'll keep an eye on the drive, as it did have the errors reported.  If it can survive long enough for me to pre-clear my new parity drive, then I can re-task the old parity drive in this potentially failing drives place.    Is there a value for " Reallocated_Sector_Ct" that is considered acceptable or should one worry if its anything greater than 0 ?  I can't say if this drives  Reallocated_Sector_Ct of 53 came at once or over time, but being aware of it now I can at least check back on it to see if it rises.

Thanks for the verification.

 

I'll keep an eye on the drive, as it did have the errors reported.  If it can survive long enough for me to pre-clear my new parity drive, then I can re-task the old parity drive in this potentially failing drives place.    Is there a value for " Reallocated_Sector_Ct" that is considered acceptable or should one worry if its anything greater than 0 ?  I can't say if this drives  Reallocated_Sector_Ct of 53 came at once or over time, but being aware of it now I can at least check back on it to see if it rises.

 

My rule of thumb on reallocated and pending sectors is to run some preclears. If the counts stay stable for 3 parity checks in a row, the drive is ok. Just continue to monitor. But if after 5 or 6 checks you are still seeing the numbers increase, even if only a few at a time, I would return or RMA it. It is just a matter of time, and no use delaying.

That seems like a decent test procedure.    Thanks for the suggestion.  I think its time I setup another PC with a free version of UnRaid to do tasks like this, as the only way I can test / pre-clear drives currently is to pop the side of the case open and set the drive on something (my case is at its drive capacity).  The largest drive I have cleared is a 2TB drive and I recall it taking a while to run it multiple times.  I can just imagine how many days its going to take to run it on my 4TB drive!