[RESOLVED] Can't access web interface after upgrade to 6.1.8

[GortWillSaveUs]

I just upgraded smoothly from 5.0.4 to 6.1.8

Love the new UI!!

 

However, 2 hours after upgrade, I could not access the UI.

I came here and found a post about properly shutting down.

I did that and the UI came back.

 

Today,..I checked the UI and it's not available.

I tried the shutdown but that's not working at all.

All through this, my shares are accessible, I can ssh and telnet in, my memory looks good, top looks fine, and syslog shows not much of anything.

I don't have docker (or any other extras) running since I didn't have time to check out the new features.

 

I saw another post where someone converted the drives to XFS.

My only issue is that I can't access the user interface.

[danioj]

As indicated here: http://lime-technology.com/wiki/index.php/Troubleshooting#Creating_a_forum_post_about_your_problem

 

And of course, as mentioned in the section above, if diagnostics or a syslog would be useful to a troubleshooter, attach it now! Don't wait to be asked for it! The v6 diagnostics zip file is the most desired troubleshooting tool, as it includes the syslog, all SMART reports, and a lot of other helpful system info. Some problems don't need a syslog, but most do. It is our window into the internal workings of the Linux kernel and the unRAID driver, what it is seeing and what it is doing.

 

Please post a diagnostics file and let us know if you are running any plugins, containers, or VMs. Normally the diagnostics file is obtained via the Tools Tab in the WEB GUI - however seen as you can't access the Web GUI you can still get the diagnostics ZIP file created using the 'diagnostics' command from the command line.  The resulting zip file is put into the logs folder on the flash drive.

 

Grab it and post it. I'm sure someone will be able to help.

[GortWillSaveUs]

 

Please post a diagnostics file and let us know if you are running any plugins, containers, or VMs. Normally the diagnostics file is obtained via the Tools Tab in the WEB GUI - however seen as you can't access the Web GUI you can still get the diagnostics ZIP file created using the 'diagnostics' command from the command line.  The resulting zip file is put into the logs folder on the flash drive.

 

Grab it and post it. I'm sure someone will be able to help.

 

Thanks danioj! and apologies for not already posting diagnostics. The past few days have been crazy, and I hadn't had access to my server.

Even now,..my job has to take precedence.

 

I will say this,...very late last night, I decided to go back to 5.0.4 (you better believe I had a backup).

So I followed the steps to get back to the older release I had been running for a few years with no issues.

When I brought the server up, I was able to access my shares. Woohoo!

However,....I couldn't access the web interface. Makes no sense. After pulling out a few hairs,...I realized at 2am I was going no where that late.

Since my shares and files were all still accessible, I powered off the server properly.

 

So,..now my conundrum,...do I try and troubleshoot this version? Or, and my thought is to instead do this,...

Go back and make sure I follow the line-by-line procedures (I had thought I did) to install 6.1.8 and then apply my applicable config files and my key.

Power it on, and check shares and then the UI access.

Unfortunately, I won't be able to until later tonight.

 

I will make sure to get a syslog output, top screen shot, and diagnostics.

Uhhh,...come to think of it,...last night I copied all the 6.1.8 files off as a backup,..and I do have (or at least I should) the diagnostic zip from two days ago.

I'll see about posting that before I make any changes or even power on the server.

 

[GortWillSaveUs]

Attached is the diagnostic files.

 

Here's the sequence of events.

I followed procedures for doing a clean install upgrade.

Copied off my USB 5.0.4 file contents. (been up and running with 5.0.4 for longer than a year for sure, and don't remember prior version)

Formatted USB as per instruction

Copied over the 6.1.8 files to USB

Copied over the specific cfg files from my 5.0.4 backup folder as per instructions.

Ran the makebootable.

 

Plugged USB into server and started.

Booted fine with no issues.

Loaded user interface and was very happy with the UXD.

It was late that night, so I ran a file check.

In the morning, I could not load the UI.

Came here and found that I should try a reboot after clean shutdown.

Shutdown completed and UI is back.

Stepped out for a few hours, and when back, UI was not available.

Tried the shutdown procedures,...but this time no UI no way.

UI never came back.

I ran the diagnostics

 

I have shutdown the server and will wait for further intructions.

Didn't want to take the chance that, with my luck, 2 drives will go bad and I won't know about it.

media-diagnostics-20160220-0645.zip

[Frank1940]

How much memory do you have installed in your server?  Ver 6.X does require a bit more memory then ver 5.X did. 

[trurl]

Lots of this in your syslog, your parity drive

Feb 19 20:35:29 Media kernel: md: disk0 read error, sector=1107530312
Feb 19 20:35:29 Media kernel: md: disk0 read error, sector=1107530320
Feb 19 20:35:29 Media kernel: md: disk0 read error, sector=1107530328
Feb 19 20:35:29 Media kernel: md: disk0 read error, sector=1107530336
Feb 19 20:35:29 Media kernel: md: disk0 read error, sector=1107530344
Feb 19 20:35:29 Media kernel: md: disk0 read error, sector=1107530352

and its SMART

197 Current_Pending_Sector  0x0032   200   200   000    Old_age   Always       -       2
198 Offline_Uncorrectable   0x0030   200   200   000    Old_age   Offline      -       52

Replace ASAP.

 

Shouldn't affect webUI though. Probably not really enough RAM for v6.

[GortWillSaveUs]

I have 4G on the server.

Appreciate you guys trying to help.

 

Yes, I saw those errors in the diagnostic logs before I posted them. Darn it, just doesn't make sense. I had just done a scan last week and all was well. Ugh!!!

 

So now, let's say I add RAM, and replace the parity drive. Without the web interface, seems to me I'll be blind to how things are proceeding. I know it's going to take quite some time, but,...... Argh.

[RobJ]

Some comments -

 

* In your BIOS settings, check video RAM buffer, make sure it's at minimum (8MB?), currently 256MB reserved for onboard video.  unRAID console is text only, so doesn't need RAM.  This should give you a little more memory.  You also said you thought you had 4GB, but it's only showing 2GB in syslog (a good reason to run Memtest, see more below).

 

* While still in your BIOS settings, change the SATA mode to AHCI or a native SATA mode, NOT an IDE mode as it is now.  That should hopefully let the 2 drives in the 5th and 6th onboard SATA ports run a little better.  There was an interrupt lost related to the current config for this 2 port controller.  I think AHCI should be better.  You never want to see lost interrupts.

 

* I don't know how you accomplished it, but emhttp is not even running!  You must have crashed it pretty bad!  I think it's the first time I've seen that in a v6 system, so you win some kind of prize!  The syslog statements at the end of the syslog are rather wild, look OK at first glance until you look closer.

 

* Segfaults at the end, involving libc.  Sometimes that means dependency problems, but I don't see any addons.  Sometimes it means RAM issues, so a long Memtest is strongly recommended now.

 

* As he said, a number of bad sectors on the Parity drive, and the SMART report concurs, so not a false positive due to bad memory or unRAID crashing.  You should be able to unassign the Parity drive, then Preclear it, then re-assign it and build parity again (if no permanent issues found).

[GortWillSaveUs]

@RobJ: Thank you sir! Appreciate even more insight.

Well,...not sure why I said 4GB of RAM  ,...and yes, you're correct, I only have 2GB.

I can't believe I built this 4 years ago! At that time, and since I only needed a media server,...2GB was AOK.

I suppose it's time to rethink my hardware.

 

But before I even do that, I'll make those BIOS changes you recommend.

I just formatted the USB stick, loaded the backup copy of the 5.0.4 version I was running before I tried the upgrade.

Ran makebootable and once powered on,..I hope I get the UI back.

 

If I do get the 5.0.4 UI back,...I'll follow your suggestions for dealing with the Parity drive.

If I don't get the UI back,..I will be at a total loss,..and will probably seek help under the v5.x forum.

 

Once I clear those hurdles,...then it's hardware time.

 

Once again,...appreciate everyone's help and suggestions!!

[GortWillSaveUs]

Hurray!

 

Made the changes I mentioned in prior post, booted up, and I have the 5.0.4 web interface.

It's going through a full parity check so I'll let that finish.

 

After that,..well,...one step at a time.

 

But I can't help myself,...when I'm over this hump, I'll be looking into a new motherboard that supports the current processor. (I think)

I have an AMD Sempron CPU, which seems to be up to the task.

However, the RAM is an issue. At the time (2012), when I brought the MOBO, I needed as many SATA connectors as possible.

The only one I found at the time was an ASRock Socket AM3/AMD 785G

Problem is, it only has 2 RAM slots, and only supports up to *GB of RAM.

Plus,...there was only the CPU fan connector, and one other fan connector.

I have an additional two fans not even plugged in.

 

Hmmm,...I may just end up buying two sticks of compatible 4GB RAM and then upgrade to 5.1.8 edit 6.1.8,...we'll see.

Come on Parity Check,...fingers crossed.

[Frank1940]

Hurray!

 

Made the changes I mentioned in prior post, booted up, and I have the 5.0.4 web interface.

It's going through a full parity check so I'll let that finish.

 

After that,..well,...one step at a time.

 

But I can't help myself,...when I'm over this hump, I'll be looking into a new motherboard that supports the current processor. (I think)

I have an AMD Sempron CPU, which seems to be up to the task.

However, the RAM is an issue. At the time (2012), when I brought the MOBO, I needed as many SATA connectors as possible.

The only one I found at the time was an ASRock Socket AM3/AMD 785G

Problem is, it only has 2 RAM slots, and only supports up to *GB of RAM.

Plus,...there was only the CPU fan connector, and one other fan connector.

I have an additional two fans not even plugged in.

 

Hmmm,...I may just end up buying two sticks of compatible 4GB RAM and then upgrade to 5.1.8 edit 6.1.8,...we'll see.

Come on Parity Check,...fingers crossed.

 

With 8GB of RAM you would have basically the same setup as my Media server (see below).  And there are a lot of other folks who are running Dockers with 8GB of RAM without any issues. 

 

Now that I am making this post, I seem to recall that the GUI 'disappearing' (on servers having small amounts of RAM) after not being accessed for a few days was a big issue somewhere in the Ver 5 or  ver6 beta phase.  It was basically determined that it was a matter of running out of available RAM and the OS would decide to dump a process that 'time without access' and 'system priority' (forget the exact proper names) allowing the emhttp process to get killed to free up some RAM.  Unfortunately,  emhttp can not be restarted for some reason!  It was suggested at the time the LimeTech change the priority of the emhttp process to make that less likely but I don't know if it ever happened. 

[trurl]

Now that I am making this post, I seem to recall that the GUI 'disappearing' (on servers having small amounts of RAM) after not being accessed for a few days was a big issue somewhere in the Ver 5 or  ver6 beta phase.  It was basically determined that it was a matter of running out of available RAM and the OS would decide to dump a process that 'time without access' and 'system priority' (forget the exact proper names) allowing the emhttp process to get killed to free up some RAM.  Unfortunately,  emhttp can not be restarted for some reason!  It was suggested at the time the LimeTech change the priority of the emhttp process to make that less likely but I don't know if it ever happened.

There was a lot of this in the 32bit (before v6) era of unRAID. Not much said about it anymore with 64bit native support for >4GB RAM. Here is a link I still have.

[GortWillSaveUs]

Thanks for the suggestions about the Sempron 145 and the 8GB.

and I'm sure if nothing else, this thread might just help someone else that may face the same situation.

[NodNarb012]

I might be experiencing the same issue. Can you post the link on how to properly shutdown?

[Frank1940]

I might be experiencing the same issue. Can you post the link on how to properly shutdown?

 

Both of my systems have the Powerdown plugin installed (See    http://lime-technology.com/forum/index.php?topic=31735.0  )  but there is a powerdown function in the default install.  You could try typing:

 

  powerdown 

 

On the command line and I think that will work.

[NodNarb012]

My issue turned out to be an odd glitch. Just before I lost the Web GUI, I attempted to stop the array and it got stuck syncing and/or unmounting the disks. Before that I was copying files disk to disk using the console and didn't logoff. Once I logged off of the console, the Web GUI came back and I was able to shutdown properly.

 

Thanks for the help.

[GortWillSaveUs]

Hurray!

 

Made the changes I mentioned in prior post, booted up, and I have the 5.0.4 web interface.

It's going through a full parity check so I'll let that finish.

 

 

Well,..I had 5 hours left on the Parity check on the system locked up.

Can't get to UI, can't get to shares, and can't ssh,..and can't ping.

Will try a hard reboot, and start up just to make sure I can get on again.

If so, I'll shutdown via UI and then order a new 3T drive to replace current parity drive, as well as 8GB of RAM.

[GortWillSaveUs]

Reboot got me back the 5.0.4 UI.

Just ordered replacement RAM, and the new 3T parity drive.

[GortWillSaveUs]

Replaced the ram, booted and all looked great.

Replaced Parity drive with new 3T drive and the rebuild completed with no errors.

Ran non-correcting Parity check overnight and that looks good as well.

Just check the smart status and ran self-tests on all drives. All green.

 

Just backed up existing USB contents and took screen shots of drive placements and configs.

 

Should start the upgrade to 6.1.8 shortly and will post update after that.

If all goes well,...I'll keep my fingers crossed for a few day and then start to breathe easier.

 

Forgot to mention, I also have my entire unraid server backed up to an external drive.

[GortWillSaveUs]

2nd attempt and successfully upgraded to 6.1.8 from 5.0.4,..well,..kind of...

 

I used the instructions using wget to download the plg file.

Then after running the upgrade command,..the server was rebooted.

It came back up, but I got the "boot:" prompt, and that was it.

 

Searched forum and found that (and that's what confuses the crap out of me) I needed to copy of 4 files and a folder.

(note: I'm not detailing any commands run, or files I copied,..lest I stop someone from following the ACTUAL procedures)

and since I copied in files,..I ran the make bootable command.

 

Started server back up, and it's up and running on 6.1.8

I got the timezone errors and needed to look that up to get it to my timezone.

 

I then setup the Notifications and tested that,..it works.

So the next 2-3 days are burn in,..so we'll see how we do.

 

I like the UI,..very cool.

Good luck to all who upgrade. My initial problem was that I needed more RAM and my parity drive needed to be replaced.