After close to 1TB of data added and 20+ virtual machine installs over iSCSI, it is still running and performs better than expected at this point. (the server was running windows storage server for a few months before, stable but, disappointed performance wise so I know it is not hardware related). I am going to assume it was related to the vbox install failures and move on, do not have the time to dig into it. Thanks,
On Thu, Feb 28, 2013 at 2:41 PM, Heinrich van Riel < heinrich.vanr...@gmail.com> wrote: > It had the same behavior with 151a5 and 151a7. It is not really doing > anything. Come to think of it the problem only started after attempting to > installing Virtualbox. I only ran the server for 1 or 2 hours before trying > to install it, locks up when loading kernel modules. I tried a few > different releases. > I re-installed it last night and did not attempt to install vbox. It is > configured as an iSCSI target and have been hit by VMware quite a bit since > last night (installing test machines) and it is not have the problem so > far. The strange thing is that I did go back and uninstall vbox each time > after the failed attempt (for a5 & a7) and it locked up every few hours. > iSCSI was not configured, was plain installs with failed attempts of vbox. > Currently it appears to be all good. Load will be increase quite a bit in > the next few days. > I will respond with the results. I am also still waiting for the sas disks > for the rpool, so a reinstall will happen at that point. > > > > On Wed, Feb 27, 2013 at 9:33 PM, Bob Friesenhahn < > bfrie...@simple.dallas.tx.us> wrote: > >> On Wed, 27 Feb 2013, Heinrich van Riel wrote: >> >> I am using the same board with 20 disks. I seem to have some stability >>> issues, all are SAS disks except for the >>> 2x rpool disks (SATA) that I have connected on the the backplane in the >>> back of the chassis since according to the supermicro documentation >>> SATA/SAS should not be mixed in the same backlpane. The board is in >>> the 6047R-E1R36L storage server from Supermicro. >>> The system would lockup after a few hours and also as soon as it tries to >>> load the kernel modules for Virtualbox during install. >>> >> >> What version of OpenIndiana are you using (uname -v)? >> >> Is the system doing anything significant (other than starting VirtualBox) >> when it locks up? >> >> Bob >> -- >> Bob Friesenhahn >> bfrie...@simple.dallas.tx.us, http://www.simplesystems.org/** >> users/bfriesen/ <http://www.simplesystems.org/users/bfriesen/> >> GraphicsMagick Maintainer, http://www.GraphicsMagick.org/ >> >> >> ______________________________**_________________ >> OpenIndiana-discuss mailing list >> OpenIndiana-discuss@**openindiana.org<OpenIndiana-discuss@openindiana.org> >> http://openindiana.org/**mailman/listinfo/openindiana-**discuss<http://openindiana.org/mailman/listinfo/openindiana-discuss> >> > > _______________________________________________ OpenIndiana-discuss mailing list OpenIndiana-discuss@openindiana.org http://openindiana.org/mailman/listinfo/openindiana-discuss
