Sponsored Content
Operating Systems Solaris Solaris x86 on vmware workstation panic and almost crashing Post 302667871 by snchaudhari2 on Saturday 7th of July 2012 10:05:14 PM
Old 07-07-2012
Solaris x86 on vmware workstation panic and almost crashing

Hello Admins,

Howz it going?
Coming to our forum after long time.

Well, a solaris x86 system on my vmware workstation is facing a big trouble.

I did a file system check on root file system. And after reboot, I am getting an error for both normal mode and fail safe mode.

I have attached the screenshot with this thread.

Looking for ward to any possible solutions.

Thanks in advance.
Solaris x86 on vmware workstation panic and almost crashing-sol-x86-errorjpg
 

8 More Discussions You Might Find Interesting

1. Solaris

How to install Sun Solaris 10 inside VMware Workstation 5.5

Some members asked about this way, click Here u will find what u want (1 Reply)
Discussion started by: Sound Of Wisdom
1 Replies

2. Solaris

How to get Solaris 8 x86 (32 bits) ethernet up on Vmware 6.x.x?

Hello professional, I am using Solaris 8 x86 (32 bits) running on Vmware 6.x.x my vmware configuration: config.version = "8" virtualHW.version = "6" scsi0.present = "TRUE" memsize = "1024" ide0:0.present = "TRUE" ide0:0.fileName = "Other.vmdk" ide1:0.present = "TRUE"... (0 Replies)
Discussion started by: draggy
0 Replies

3. Solaris

NIS on vmware workstation

Hi Admins, I just have a doubt on NIS that, is it possible to run NIS on vmware workstation running more than 1 solaris instances. i.e. can we setup one solaris instance as master and others as slaves...?? I have vista on my laptop. I am concern about the domain name it will ask while... (8 Replies)
Discussion started by: snchaudhari2
8 Replies

4. Solaris

Error opening PAM libraries : solaris 10 on vmware workstation

Hi Admins, I am facing an issue with Solaris 10 sitting on vmware workstation... When I start it, it gives me an error : "Error opening PAM libraries, contact system administrator" Also I can reach it via putty, but none of the id/passwd working. I did revert pam.conf. But still no... (2 Replies)
Discussion started by: snchaudhari2
2 Replies

5. Solaris

Solaris 10x86 on VMware Workstation

Is it possible to create metadevices and soft partitions using Solaris Volume Manager on Solaris 10 x86 that is running on VMware Workstation. It would a low cost method to practice extending soft partitions and metadevices. If anyone has an experience with this please share. Regards (1 Reply)
Discussion started by: Tirmazi
1 Replies

6. Linux

vmware workstation

i have following :- fedora 16 x 64bit kernel 3.2.7-1 vmware workstation 8.0.2. Steps to install vmware workstation to access ESX machine 1- sh vmware name.bundle 2- setup started and completed with out any warning. 3- when i type "vmware " then "VMware Module Updater Started" and the... (2 Replies)
Discussion started by: engrtahir2007
2 Replies

7. Solaris

Copy via samba on vmware workstation with Solaris taking much longer than usual

i have a vmware workstation with solaris 10 installed on this. i copying 2 gb data via samba from windows to this vmware workstation. copy speed is 24 kb/sec. how i can speed up this copy process ? (7 Replies)
Discussion started by: rehantayyab82
7 Replies

8. Solaris

Solaris x86 guest in vmware workstation

I swear I have no other devices on the vmnet 192.168.142.2, but after I configured one of the solaris x86 os, I kept getting warning ..node xx xxxxx have our ip addresss 192.168.142.2, and it scrolled thru it forever .. I tried to boot it into single user mode , still having the same issue.. ... (1 Reply)
Discussion started by: ppchu99
1 Replies
REBOOT(8)						      System Manager's Manual							 REBOOT(8)

NAME
reboot - stopping and restarting the system SYNOPSIS
/sbin/reboot [ -lqnhdarsfRD ] /sbin/halt [ -lqndars ] /sbin/fastboot [ -lqndarsRD ] DESCRIPTION
2.11BSD is started by placing it in memory at location zero and transferring to its entry point. Since the system is not reentrant, it is necessary to read it in from disk or tape each time it is to be boot strapped. Rebooting a running system: When the system is running and a reboot is desired, shutdown(8) is normally used to stop time sharing and put the system into single user mode. If there are no users then /sbin/reboot can be used without shutting the system down first. Reboot normally causes the disks to be synced and allows the system to perform other shutdown activities such as resynchronizing hardware time-of-day clocks. A multi-user reboot (as described below) is then initiated. This causes a system to be booted and an automatic disk check to be performed. If all this succeeds without incident, the system is then brought up for multi-user operation. Options to reboot are: -l Don't try to tell syslogd(8) what's about to happen. -q Reboot quickly and ungracefully, without shutting down running processes first. -n Don't sync before rebooting. This can be used if a disk or the processor is on fire. -h Don't reboot, simply halt the processor. -d Dump memory onto the dump device, usually part of swap, before rebooting. The dump is done in the same way as after a panic. -a Have the system booter ask for the name of the system to be booted, rather than immediately booting the default system (/unix). -r Mount the root file system as read only when the system reboots. This is not supported by the kernel in 2.11BSD. -s Don't enter multi-user mode after system has rebooted - stay in single user mode. -f Fast reboot. Omit the automatic file system consistency check when the system reboots and goes multi-user. This is accomplished by passing a fast reboot flag on to the rebooting kernel. This currently prevents the use of -f flag in conjunction with the -h (halt) flag. -D Set the autoconfig(8) debug flag. This is normally not used unless one is debugging the autoconfig program. -R Tells the kernel to use the compiled in root device. Normally the system uses the device from which it was booted as the root/swap/pipe/dump device. Reboot normally places a shutdown record in the login accounting file /usr/adm/wtmp. This is inhibited if the -q or -n options are present. Note that the -f (fast reboot) and -n (don't sync) options are contradictory; the request for a fast reboot is ignored in this case. Halt and fastboot are synonymous with ``reboot -h'' and ``reboot -f'', respectively. Power fail and crash recovery: Normally, the system will reboot itself at power-up or after crashes if the contents of low memory are intact. An automatic consistency check of the file systems will be performed, and unless this fails, the system will resume multi-user operations. SEE ALSO
autoconfig(8), sync(2), utmp(8), shutdown(8), syslogd(8) 3rd Berkeley Distribution May 24, 1996 REBOOT(8)
All times are GMT -4. The time now is 02:54 AM.
Unix & Linux Forums Content Copyright 1993-2022. All Rights Reserved.
Privacy Policy