For some reason... UNMENU was able to start.  I was able to download the attached syslog from UNMENU... can anyone assist?  Nothing appears to be mounted when I log in remotely.

 

-----

 

SOLVED.

 

I went back to v6.0-beta10a and it worked just as before.

 

Thanks for the help.

 

syslog-2016-04-24.txt

unMenu out of the box isn't compatible with 6.1.x  There are some "hacks" you can make to it to make it compatibile, but the needs for unMenu is really diminished nowadays.

 

Did you upgrade from 6.x or 5.x?

I was on v6.0-beta10a.

 

I originally tried to upgrade to the latest beta.  When it failed I tried to upgrade to the last stable release, which is what this is.

 

So is the problem UNMENU?  If so, how do I remove it?

 

Best solution is to edit your "go" file on the stick via windows and remove the command that starts unmenu (uu)

 

Ideally, remove any packages in /extra and /packages.

 

With unMenu installed, it really messes up diagnosing why things are not working.

 

 

Another thought here:

 

Delete dynamix.plg from the flash drive (config/plugins)  I know that there was at least one user who upgraded to 6.2 then chose to downgrade, and the different versions of the plg caused some issues.

Hmmm... Thanks for your help so far, but no fix yet.

 

1. I emptied the packages folder.

2. I cleaned up the go script.  I even commented out /boot/cache_dirs  -w

 

I get the same result.

 

unraid won't start.  I can putty in but nothing is mounted.  Strange thing tho... there is nothing new in the log files.  the last log file is from yesterday before I tried to reboot the first time. 

Strange that UNMENU showed me a log file.. but I cannot find one on the thumb drive.  Do you know where I should find it?  Could it be a problem with the flash drive itself?  unraid maybe can't write to it?

Anyway I am just guessing.  I appreciate the help.

 

Also, I do not see dynamix.plg.  Only dynamix.cfg. 

 

The log file is stored in RAM (/var/log/syslog)

 

 

Its not quite clear to me if you tried to reboot after making those changes however.

If you have rebooted, then try from the console

diagnostics

(ignore any errors)  If the command itself doesn't work, then

cp /var/log/syslog /boot/syslog.txt

 

With a new syslog we can begin to diagnose

 

Thanks.  I was able to run diagnostics.

 

Here it is...

 

megatron-diagnostics-20160424-1425.zip

BTW.. Not sure if it matters, but I am running from a kicker disk.  I put all of the same files on the kicker disk.

 

ok.  That now throws things for a big loop.  Why are you running like that? ESXi? Can't boot via USB?

 

Can you access the webUI at 192.168.1.79? (instead of http://MEGATRON)?

 

The array won't start because you've got a bunch of drives missing (parity, disk3, disk 8, disk 10)

 

*Possibly* the drivers included with v6b10 were compatible with your sata controller those disks are on but later versions they are not (doubtful, but a possibility) -> you've got

Apr 24 14:24:06 MEGATRON kernel: kernel BUG at drivers/ata/sata_mv.c:2120!

  but I really can't help any further because of the kicker disk simply because that throws a major variable into the equation of which I have zero knowledge of.

Ok.  I will try to go back to the version I was running, maybe that will work again.

 

I use 192.168.1.79//Main

 

I use a kicker disk because my machine will not boot from a flash drive.  Its an ancient supermicro.  But it has always worked just fine.

 

 

 

SOLVED.

 

I went back to v6.0-beta10a and it worked just as before.

 

Thanks for the help.

 

SOLVED.

 

I went back to v6.0-beta10a and it worked just as before.

 

Thanks for the help.

definitely a driver issue then.  Sucks, but at least you're up and running.

No worries at all.  I am happy you were able to provide me with the support to figure it out.  Thanks again.