Solaris / OpenSolarisThis forum is for the discussion of Solaris, OpenSolaris, OpenIndiana, and illumos.
General Sun, SunOS and Sparc related questions also go here. Any Solaris fork or distribution is welcome.
Notices
Welcome to LinuxQuestions.org, a friendly and active Linux Community.
You are currently viewing LQ as a guest. By joining our community you will have the ability to post topics, receive our newsletter, use the advanced search, subscribe to threads and access many other special features. Registration is quick, simple and absolutely free. Join our community today!
Note that registered members see fewer ads, and ContentLink is completely disabled once you log in.
If you have any problems with the registration process or your account login, please contact us. If you need to reset your password, click here.
Having a problem logging in? Please visit this page to clear all LQ-related cookies.
Get a virtual cloud desktop with the Linux distro that you want in less than five minutes with Shells! With over 10 pre-installed distros to choose from, the worry-free installation life is here! Whether you are a digital nomad or just looking for flexibility, Shells can put your Linux machine on the device that you want to use.
Exclusive for LQ members, get up to 45% off per month. Click here for more info.
Distribution: Solaris 11.4, Oracle Linux, Mint, Debian/WSL
Posts: 9,789
Rep:
The boot sequence capture you posted shows "skipping system dump : no dump device configured". Enabling it would be the first thing to do in your case.
Without crashdump files to analyze but just a stacktrace from a screenshot, there is probably no way for anyone to successfully investigate the issue.
There's no greed at play here, just a technical limitation. With just this report, I'm almost sure you wouldn't have had more help should you had paid for support, unless the support had the very same hardware and was able to reproduce the problem.
Sorry about that, I did not mean to indicate people involved there were in any way greedy. I was expressing a distinct but general feeling I acquired after almost 2 years interacting with illumos/joyent environment. A feeling I did not experience with FreeBSD or Linux community.
It is only normal for developers of that calibre (like some of illumos/joyent's which I esteem real geniuses) to give priority to issues other than dealing with newbies like myself, well-meaning but not bringing much to the table beside eagerness to learn.
In the end, I was very sorry we had to drop illumos. To me, it is the best OS in many aspects. But without much chance to learn and grow, it is impossible to consider it as an option, unless of course one is already an expert.
But, long live illumos!
Last edited by priyadarshan_; 02-29-2020 at 03:47 AM.
Coming back to this after 6 weeks: we did not give up on illumos yet.
In a way, I am grateful OmniOS botched that server upgrade. It forced us to either go back to FreeBSD world or try SmartOS. We are testing SmartOS and it has been quite good. Currently setting up an AMD server with Hetzner. SmartOS gives piece of mind by solving the upgrade problem tout cour.
So, if your server's hardware can use SmartOS, give it a try.
For some yet unknown reason, OmniOS stopped finding the (virtual) e1000 adapter a week ago. A few reboots later, it was back again.
The problem seems to be a bug somewhere in OmniOS itself, finally having been confirmed in a debugging session with a friendly stranger from the #OmniOS IRC channel. Basically, if you change the (virtual?) network adapter after installing OmniOS, the old adapter will remain set up for the DHCP route (as seen in ipadm). You'll need to disable it manually and add /dhcp for the new adapter.
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.