Solaris 11 Express bugs?

wheelz

Weaksauce
Joined
Feb 4, 2011
Messages
100
I'm having some issues with the new storage box I am testing using Solaris 11 Express. I've been busy so I haven't been testing with it for a number of days/weeks. I come back to the system and I notice that the dbus-daemon is using 100% CPU. That in itself is strange because I have a quad-core Xeon and the graphs show that all the core's percentages add up to 100% but each core is not at 100%. However I don't think it should be using even that much to begin with.

I did some googling and I see some references to a bug and possible memory leak... Great, just what I want in a stable storage platform. So I figure I'll just reboot it as I'm not using any of the storage yet. I reboot it through the GUI and now just trying to shut down is not working. It is scrolling the following down the screen:

svc.startd[9]: svc:/network/iscsi/target:default: Method or service exit timed out. Killing contract 19417.

It has been doing this for the last 45 minutes. Anyone have any ideas on this? I am a little reluctant to just hit the power because when I did that before, it took 2-3 days to boot up!! I don't know if it was doing some kind of thorough scrubbing of the disks or what but this is getting frustrating.
 
Well, after waiting over an hour and a half there was no sign of progress. I found that I have a graceful shutdown button on my IPMI viewer so I thought it couldn't hurt to try that. That stopped the messages and made it continue with the shutdown. It is back up and running but has anyone else seen behavior like this?
 
Ive never heard of it. Solaris has lately had an overhaul so it shuts down quick, and boots quick. My Solaris 11 Express shuts down in 70 seconds using a HDD, and shuts down in 10 seconds using a Vertex 3, 240GB. Maybe you have some hardware that Solaris does not like? That is not normal behavior. I have been using Solaris for 5 years in my home computer.

IBM has AIX servers that boots in 90 minutes. It seems to do most of the things serially, one at a time. Solaris boots/shuts down in parallell using the new SMF function.
 
One bug that is stopping me from using S11, and has me stuck on b130, is an SMB issue with aliases.

Multiple connections from a client to differing aliases to S11 SMB shares causes frequent disconnects. I don't know if its because the SPN isn't registered (which I keep forgetting to do), but for me I'm not going to upgrade until that's fixed.

I have to spin up a OpenIndiana VM and test that some time.
 
Hello,

This definitely sounds like Solaris is struggling with something the hardware it doesn't like.

There are a couple of 4 year old X4500's at one if the sites I work on which I upgraded earlier this year to Solaris 11 Express, they are used for D2D backup and as NAS devices for a couple of ESXi servers. these machine are running iSCSI, NFS and SMB shares to a variety of systems, and these can shutdown in about 4 minutes, and once they have POST'd will boot Solaris 11 Express (snv_151a to be precise) from the GRUB menu to login screen in around 2 minutes, and a simple reboot is now accomplished in around 90 seconds, so waits of hours to reboot and shutdown suggest a hardware or driver issue. Have you checked the syslog and FMD to see if they're reporting anything abnormal?

Best wishes,

Dave
 
I specifically picked the hardware to be compatible with Solaris. Here is my config:

1 x Chenbro RM23212 2U 12 bay chassis
1 x Chenbro 84H323210-004 SATA2/SAS Backplane
1 x 820W Redundant Psu 3Y 1+1
1 x Supermicro X8DT6-F
1 x Intel Quad Core Xeon E5606 2.13 Ghz
1 x Intel Thermal Solution STS100C Processor Cooler
3 x Samsung Dual Rank 8GB ECC RDIMMs
1 x PCI Riser ARC2-733-3X8
2 x Intel Dual GB PCIe NIC
2 x SFF 8087 to sata breakout cable
2 x Super Talent 16 GB MLC 7-pin SATA DOM (mirrored for OS)
4 x Seagate Barracuda 1 TB SATAII 300MB/s 7200rpm HD (existing drives for data)
1 x Seagate Constellation ES 1 TB SATAII 300 MB/s 7200rpm HD (added new data drive)
No SSD *Yet*

I must admit that I am new to Solaris and not sure where to look to find the syslog (I at least know what this is) and FMD (not sure what this is).
 
Back
Top