I going to upgrade from 4.7 to unRAID Server OS basic but have fe simple question.

 

I'm going to start-over, clean start.

 

1. If I've read this right, I can upgrade for free if I use my original USB thumbdrive and reg key?

 

2. If I want to upgrade not using my original thumbdrive (it is getting on a bit and small in size in todays terms), can I transfer my reg key to a new thumbdrive?

 

3. With UnRAID Server OS basic I understand it has a device limit of 6, does this include cache drives?

 

I may just buy a new reg key and keep the old one as a  backup and rsync between them.

Probably easiest to use your original key to upgrade, then when it's complete, obtain another key, and then use either one as a backup.

Thanks, I will do that.

I one more question about the upgrade.

 

I'm going to do the "clean install", but, if possible copy over a few cfg files from 4.7, namely  ident.cfg, network.cfg, share.cfg.

 

In the upgrade guide under the "How to do a clean install" sections it says:

There are a few configuration files that are safe to keep and restore, ident.cfg, network.cfg, share.cfg, and any .cfg files in the config/share folder.

 

Which sounds great and is just what I need, but later on it says under "Restore saved configuration files":

It may be safe to copy network.cfg and ident.cfg, but no others! These 2 files would get your system quickly back on the network

 

So does that mean I cannot/shouldn't copy over my share.cfg? And what about the share/config folder?

I just happen to be the guy that made that mistake!  My apologies, I just recently added the first section, and missed correcting that older part.  Thanks for bringing that to my attention, I'll fix it now.

 

Originally I wasn't sure about share.cfg, as it's very different now.  I had Tom take a look at an old share.cfg, and he has said that it is safe to bring forward, but not backward.  In other words, the old share.cfg is compatible enough, and can bring some of its share settings into the new version, but once you use it in v6, it is drastically changed and can't be restored if you ever wanted to revert to v4.7 (you would have to use an old backup).  That is probably true of other config files too.

No worries RobJ, glad I helped in someway! 

 

I'm not planning on go back to 4.7,  I have backup of it anyway, (as is the data) so if something doesn't work out can always eyeball the .cfg files for my old settings.

 

I know I said "one more question"....but I have another; may license for unRAID 4.7 plus supported 7 devices, I take it that then I switch to unRAID6 it will go down to 6?

I know I said "one more question"....but I have another; may license for unRAID 4.7 plus supported 7 devices, I take it that then I switch to unRAID6 it will go down to 6?

 

According to the LimeTech license page, the Plus license now has a limit of 12!

Okay, started my upgrade.

 

Copied over to the new config directory the following,  share/*,  ident.cfg, network.cfg, share.cfg, and know you said that was it, but I also copied passwd, secrets.tdb and smbpasswd figuring it is worth a try.  I renamed the original ident.cfg, network.cfg, share.cfg to back them up.

 

Booted new unRAID6, it booted fine, I then assigned the drives to the same as they were on 4.7, started the array, it starts.

 

Users, user shares and network config appears to be intact, I have not been able to fully check the share access yet so I don't know if copy the Samba stuff has worked yet, but I'll keep you posted.

 

I'm now running the new permissions script

 

I have a question about this statement though:

Just remember though that you will have to re-configure everything, including identification and network settings, user shares, users and passwords, etc. Since you will need to re-assign all of your drives, make sure you know which drives are which, ESPECIALLY which drive is the parity drive! If you assign a drive that already has data on it from v4 or v5, then unRAID OS 6 will recognize it and the data should be intact.

 

Now I actually want to change to using XFS, and don't care about losing my data, but I'm a bit confused as when I go into the disk it says they are XFS, I thought it would see my old disk as reiserfs?

 

So, if it is really now XFS how heck would it have kept my old data?

 

As say, I don't care about losing the data as I restoring afresh from backups

 

Sidenote: for some unknown reason, my old thumdrive is running very slow, it wasn't like this when I first got it, most odd, it is "old" though, been running unRAID pretty much non stop for 5 years.  I thought reformatting and starting over may fix but it made no difference, it's like some of the memory cells have corrupted - disk check run fine though.

 

UPDATE: Okay, after the new perms finished it looks like it is now seeing the filesystem as reiserfs, so all is good, except I will reformat to XFS, once the parity check has competed.

UPDATE: Okay, after the new perms finished it looks like it is now seeing the filesystem as reiserfs, so all is good, except I will reformat to XFS, once the parity check has competed.

Good - I was a bit worried that you thought it was XFS as that might have indicated that data loss had occurred.  When you assigned the disks they should have been set to 'auto' which will detect an existing file system when you first start the array, and if the format cannot be detected then set to unmountable with the format as whatever is specified in Settings for new drives (which in v6 now defaults to XFS) so the disk can be formatted.

 

There is no capability within unRAID to an in-place conversion of a disk from reiserfs to XFS.  The only way is to copy data off; stop the array; change the format to XFS; start the array; format to an empty XFS file system; copy the data back.

The basics are working fine but do have several minor issues.

 

No comms to the CyberArk UPS reported, worked fine with 4.7, hopefully something simple

 

In 'Notifications' I trying to set my email up,using gmail, some of the settings under SMTP don't stick, by that I mean I enter sender and recipient address etc, hit apply and the fields immediately blank out as if you hadn't entered anything, and the 'test' button is greyed out - need to figure way that isn't working, worked fine on 4.7.

 

The share themselves have restored fine but the security settings have gone, I guess I may need to change the share settings from what looks to be the default of 'public' to something like I had before - typically I had this config

 

Allocation - highwater

Min free space - 65560

Include disk - disk1, disk4

Export - Read only

Exception - user1, user2

Valid user - me1, me2

 

I used the above so I only spin-up certain disks and certain types of data go to the largest disk, it worked well for, and after the trouble I had losing data recently on 4.7 I'm glad I used this method as I instantly knew that when diskX crapped out it was the one that had 50% of my Movies on it, the remainder being on disk1 or whatever.

 

Another issue, it doesn't appear to like my flash GUID as I've just seen a warning about too many devices and have an error message under Registration > Flash GUID, and yes my key file is in 'config'. I'm using the same flash drive I've used for nearly 5 years.

Jul 24 19:41:10 rutland emhttp: Plus key detected, GUID: 13FE-1A00-0000-077B07370346 FILE: /boot/config/Plus.key  - so that looks good, but then

 

Jul 25 10:29:09 rutland kernel: read_file: error 2 opening /boot/config/super.dat

Jul 25 10:29:09 rutland kernel: md: could not read superblock from /boot/config/super.dat

Jul 25 10:29:09 rutland kernel: md: initializing superblock

Jul 25 10:29:09 rutland emhttp: Unregistered (-1)

Jul 25 10:29:09 rutland emhttp: Device inventory:

Jul 25 10:29:09 rutland emhttp: shcmd (293): udevadm settle

Jul 25 10:29:09 rutland emhttp: WDC_WD2003FYYS-02W0B0_WD-WMAY02903410 (sdb) 1953514584

Jul 25 10:29:09 rutland emhttp: WDC_WD20EARS-00MVWB0_WD-WCAZA2249512 (sdc) 1953514584

Jul 25 10:29:09 rutland emhttp: WDC_WD6400AACS-00D6B1_WD-WCAU4D286821 (sdd) 625131864

Jul 25 10:29:09 rutland emhttp: WDC_WD6400AADS-00M2B0_WD-WMAV51001544 (sde) 625131864

Jul 25 10:29:09 rutland emhttp: WDC_WD2003FYYS-02W0B0_WD-WMAY03182452 (sdf) 1953514584

Jul 25 10:29:09 rutland emhttp: array slots: 24

Jul 25 10:29:09 rutland emhttp: cache slots: 1

Jul 25 10:29:09 rutland emhttp: read_tokens: fopen /boot/config/disk.cfg: No such file or directory

 

...which doesn't look good.

 

As a side note, I do have a brand new SanDisk Cruzer 16Gb (looks to be like the one LimeTech supply) which I would like to use.

 

UPDATE

 

So I decided to reboot the server, and it now says my license is now valid!

 

Thank you for choosing unRAID Server OS!

 

Plus.key registered to:

    mike brooker

Date Registered:

    Tue 30 Nov 2010 11:01:49 AM CST

 

Replaceable:

    Anytime

 

Flash GUID:

    13FE-1A00-0000-077B07370346

 

Not sure what is going on here, it also now states that my parity is invalid.

 

Also, the email settings and UPS are all working after the reboot.

 

I've sent an email to LimeTech as what I really would like to do is transfer my license to the new flashdrive and really start afresh.

rutland-diagnostics-20150725-1022.zip

I've sent an email to LimeTech as what I really would like to do is transfer my license to the new flashdrive and really start afresh.

That part is now easy and automated. Set up your new flash like you want it, and put the old flash license file in place on the new key. It will detect the valid key for the old flash drive, and step you through getting your new key license in place and the old key blacklisted. Quick and easy, no need to bug Tom any more.

Yeah I should have read the tips first.  All credit to Tom, he got back too me within minutes - this sort of service, a great community of users and a great product are all the things that have made me never regret buying unRAID.