I recently had my server down for a while when I was out of town for a week, and when I returned, things looked a little odd to me. I assume it started because my cmos battery must be dead. On boot, I had to re-assign boot order to the thumb drive, time, etc. 

 

Unraid Pro 6.7.2

 

Under Disk management it warns "array management - array status"  : Not started, unRAID ARRAY is STOPPED 0 disks in array.    Array is not protected by a parity disk: Parity disk not configured. (Photo attached)

 

However, under "Dashboard," everything is loaded and states it is protected by my parity. (Photo attached)

 

Can someone help explain this to me along with the red warning blocks? The drive that it refers to is my parity drive. 
 

Also, if I post any log or diagnostics files, is there someone willing to take a look through them? Please let me know what I should post.

 

Thank you

Array looks normal to me, where's this from? It's not stock Unraid.

It's saying parity doesn't have a filesystem, as it shouldn't, same for a floppy device.

 

If something isn't working correctly please post the diagnostics: Tools -> Diagnostics

I never remembered till now, but it is a very old plugin called unmenu, circa 2013 or so when I first put it together. I don't even know how to get rid of it!

 

It seems to be working correctly but if I can do anything to make it better/faster/ or help futureproof it, that would help. 

 

Thank you

tower-diagnostics-20191210-1622.zip

3 minutes ago, xdriver said:

I never remembered till now, but it is a very old plugin called unmenu, circa 2013 or so when I first put it together. I don't even know how to get rid of it!

 

It seems to be working correctly but if I can do anything to make it better/faster/ or help futureproof it, that would help. 

 

Thank you

tower-diagnostics-20191210-1622.zip 76.31 kB · 0 downloads

UnMenu is not compatible with current versions of Unraid and has not been for some time.    I am extremely surprised if it is not causing major problems.

8 minutes ago, xdriver said:

It seems to be working correctly

unMenu is not compatible with Unraid version 6 and higher.

Please remove it (edit your 'go' file)

16 minutes ago, xdriver said:

called unmenu

I suspected it could be that, but it looks different from what I remember, you should definitely remove it from Unraid 6.

4 minutes ago, bonienl said:

unMenu is not compatible with Unraid version 6 and higher.

Please remove it (edit your 'go' file)

I meant that unraid seems to be working correctly, not unmenu. I wasn't very clear. 

11 minutes ago, bonienl said:

unMenu is not compatible with Unraid version 6 and higher.

Please remove it (edit your 'go' file)

# Start the Management Utility
/usr/local/sbin/emhttp -p 90 &
/boot/unmenu/uu

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

That is everything in the config/go file. What should I specifically remove?

You only need this one line

/usr/local/sbin/emhttp &

Note: if you want the GUI to work on a different TCP port, see Settings -> Management access

(I recommend to use the regular TCP ports unless there is a port conflict)

 

See also this for upgrade instructions and get rid of legacy stuff

 

Edited December 10, 20196 yr by bonienl

4 hours ago, bonienl said:

You only need this one line

/usr/local/sbin/emhttp &

Note: if you want the GUI to work on a different TCP port, see Settings -> Management access

(I recommend to use the regular TCP ports unless there is a port conflict)

 

See also this for upgrade instructions and get rid of legacy stuff

 

Thank you. I will check this out for sure. I posted my diag file and hope someone can take a look at it for me. I only know enough to be dangerous, not to know what I am doing. 

You first need to get rid of unMenu from the 'go' file and reboot the server to see what things look like.   Not much point attempting to diagnose anything when you are running code known to be incompatible with the current Unraid release.

One thing I notice is your appdata share is cache-only, but has some files on the array.

 

After cleaning things up and rebooting, stop docker service, change appdata to cache-prefer, and run mover to get it moved to cache where it belongs.

What should I move? unraid has been so stable since I first set it up, that I literally don't do anything with it, and totally forget everything about its workings. 

16 minutes ago, xdriver said:

What should I move?

  

Did you read the link bonienl gave? Perhaps before even looking at that one you should look at the Upgrading to V6 wiki since you apparently didn't get rid of some things from previous versions:

 

https://wiki.unraid.net/Upgrading_to_UnRAID_v6

16 minutes ago, xdriver said:

I literally don't do anything with it, and totally forget everything about its workings. 

Do you have Notifications setup to alert you immediately by email or other agent as soon as a problem is detected?

Also, you need to plan to convert your reiserFS disks to XFS. This will require reformatting them so you will need to copy all their data elsewhere.

 

But, first things first.

 

 

Have you fixed your go file and rebooted as suggested? If so post new diagnostics so we can get a better picture before making more detailed recommendations.