Just upgraded my N36L microserver from 5.0.6 up to 6.0 and I cannot get the array to start.  I used a new freshly formatted/installed flash drive, copying the config directory (minus the plugin directory).

 

Upon hitting Start I get the below quickly, it then goes back to the same screen listing changeable device assignments:

 

Spinning up all drives ... Restart SMB ... Start NFS

 

Attached is the diagnostics zip.

 

Thanks for the help

Ian

hp1-diagnostics-20150620-2126.zip

Not sure if this is your problem or not, but its a line I don't have in my logs

 

Jun 20 21:26:12 hp1 emhttp: get_message: /boot/config/._Pro.key (-4)

 

Do you have a file named ._Pro.key in your config folder?

 

I'm wondering if the ._ maybe messing everything up?

 

 

Can't see anything unusual, there are no hidden/temporary files I can see in the config folder.

 

Thought you may be onto something as this key was made using OS X when all my previous have been on Windows.

from a telnet console, type in the following:

 

ls -a /boot/config

Ah, thought I changed a setting to show hidden files but apparently it didn't work in Finder.

 

There was a ._Pro.key and ._go and ._plugins, I have removed these now.  Tried restarting but the issue still persists, only change to my eyes is that line has dropped from the syslog.

 

Attached is a new diagnostics set but I don't think there is anything other than the dropped line.

hp1-diagnostics-20150620-2255.zip

Then I have no clue...  Maybe try redownloding your .key from from the email or PM limetech or jonp for assistance.

Don't think it is key related, it comes up Pro as expected with the full compliment of slots.

 

I have tried a different key, and also creating the key in Windows instead of OS X with the same result.

 

Will PM jonp and see if I can get him to look at the thread.

 

Also just tried my 5.0.6 key and the array starts as it should with no problems.

The problem is this line in system log:

 

Jun 20 21:21:28 hp1 emhttp: stale configuration

 

Not sure why that should be happening.  Please go to Tools/Vars, select/copy/paste content and post here.

Hi Tom,

 

Full copy/paste is too long (>20K characters) so I have attached a txt file with the vars content.

 

Thanks

Ian

vars.txt

It looks like your cache drive is reporting as "not present.

 

Did you assign and remove a cache drive?

It looks like your cache drive is reporting as "not present.

 

Did you assign and remove a cache drive?

 

I noticed that too, have never had a cache drive in this machine.  The drive in the vars file may have been in the server but it would have been a long time ago!  I would have moved from 1TB WD to 2TB WD then 4TB Seagate.

 

I have tried changing the cache drive to no slots on the main page but this makes no difference.

 

It's very frustrating, 5.0.6 had a persistent issue with not shutting down cleanly.  No plugins at all as I run a separate XenServer, no solutions in the previous support thread.  Now I cannot perform an upgrade to the latest version.

your best bet is to email limetech for support.

Please edit the file 'config/disk.cfg' on your flash.  The top of it will look like:

 

# Generated settings:
spindownDelay="15"
queueDepth="1"
spinupGroups="no"
defaultFormat="2"
startState=""
md_num_stripes="1280"
md_write_limit="768"
md_sync_window="384"

 

Completely delete this line:

 

startState=""

 

Post back if this solves the problem.

Please edit the file 'config/disk.cfg' on your flash.  The top of it will look like:

 

# Generated settings:
spindownDelay="15"
queueDepth="1"
spinupGroups="no"
defaultFormat="2"
startState=""
md_num_stripes="1280"
md_write_limit="768"
md_sync_window="384"

 

Completely delete this line:

 

startState=""

 

Post back if this solves the problem.

 

Woohoo!

 

Yes Tom, that resolved the issue.  Many thanks for solving the issue.

 

Cheers

Ian

Worked for me also!

 

I was upgrading from 5.0 to 6.0.1 and could not get the array to start.  After removing startState="" the array started with no problem.

 

Thanks for the help! 

 

Albin

Thank you for this.  I've added a note about it to the Troubleshooting section of the Upgrade guide.  Let me know of any further improvements.