12-23-2005
Quote:
Originally Posted by Just Ice
there is most likely a problem with the Storedge filesystems --- "non-existent" /etc/vfstab entries are being mounted ... boot the box from cdrom or from the network and fix your entries
Is there a need to boot from cdrom? I think that a single user mode boot will be just fine.
10 More Discussions You Might Find Interesting
1. UNIX for Advanced & Expert Users
I couldnt get my hands on my solaris 2.6 cd soo i used solaris 7 cd to boot to single user mode. I typed
boot cdrom -s
it bought me to my root prompt , but when i typed fsck.....nothing happened. It was as though it couldnt go ahead with fscking. it just bought up the prompt again,... (1 Reply)
Discussion started by: lealyz
1 Replies
2. Solaris
Hello everybody,
I installed sun solaris i86 , the programme installation install the
"Mini Root" and after that he doing shutdown.
the camputer coming up and he can't boot.
how i can to resuled this problem ???
Thenk you in advence..... (2 Replies)
Discussion started by: yanly
2 Replies
3. Solaris
I had this working before. I have a 120GB disk with Solaris on the first primary partition, Fedore Core 3 on the second, Slackware on the third, And FreeBSD 5.3 on the 4th. Booting was handled by grub, and everything was working fine.
I decided to wipe everything out and start from scratch... (6 Replies)
Discussion started by: lyonsd
6 Replies
4. Solaris
When I installed the SOLARIS 10 OS first time, the desktop would not start up, this was because of network setup. Reinstalled worked. After a week due to some problem I had to reinstall OS, installation went fine and but when i reboot I get this error.
cannot find mis/krtld
boot error loading... (0 Replies)
Discussion started by: johncy_j
0 Replies
5. Solaris
Hi All,
I am newbie in solaris, please guide me.
A week before i installed solaris10 on my x86 system, it was working fine i always used "init 5" to shutdown my system as per my collegue advice.
But yesterday when i started my system it gave me following message
... (6 Replies)
Discussion started by: imrankhan.in
6 Replies
6. Solaris
Okay, let me sketch the problem.
I did have a ubuntu / Windows XP dual boot scenario that ran grub as my boot loader. I decided I wanted to try out solaris, so I popped in the opensolaris CD and hit install and told it to format and install over my linux partition.
Of course it did that, and... (2 Replies)
Discussion started by: syndex
2 Replies
7. Solaris
Hi All,
I have an x86 system which I have just installed Solaris 10 on, I intend to use this as a database server for Oracle, I tried to patch the server with the latest updates from SUN in preparation for the Oracle installation as I wanted to make sure that I was running the latest patches.
... (0 Replies)
Discussion started by: platforminc
0 Replies
8. Solaris
Hi All
We have the Sun Solaris server ... Got a power cut suddenly .... Crash happened to the system almost
You can access through Termnl .. But it seems he did not boot ... How to Make the process of the boot correctly without losing information
Thanks for all (3 Replies)
Discussion started by: gogo888
3 Replies
9. Solaris
Hello,
Can any kind soul please answer this? I want to boot a SunFire v490 with a dvd image we use to boot v480's. Is this possible? Are there caveats to doing this?
Thanks muchly,
mgb (1 Reply)
Discussion started by: mgb
1 Replies
10. Solaris
Hi
I have a problem on a server, when he boot I have this type of message loop, do you know what it corresponds to ?
( requesting internet Adress for 0:3:ba:fa:33:91 )
Regards
Sun Fire V240, No Keyboard
Copyright 2007 Sun Microsystems, INC. All rights reserved.
openboot 4.22.33,... (10 Replies)
Discussion started by: yoyo-tns
10 Replies
lutab(4) lutab(4)
NAME
lutab - list of boot environments
SYNOPSIS
/etc/lutab
DESCRIPTION
The file /etc/lutab is a list of the boot environments (BEs) configured on a system. There are two entries for each BE. These entries have
the following form:
BE_id:BE_name:completion_flag:0
BE_id:root_slice:root_device:1
The fields in the lutab entries are described as follows:
BE_id A unique, internally generated id for a BE.
BE_name The user-assigned name of a BE.
completion_flag Indicates whether the BE is complete (C) or incomplete (NC). A complete BE is one that is not involved in any copy or
upgrade operation. A BE can be activated or compared only when it is complete.
0 Indicates first of two lines.
BE_id As described above.
root_slice Designation of the root slice.
root_device Device on which the root slice is mounted.
1 Indicates second of two lines.
The lutab file must not be edited by hand. Any user modification to this file will result in the incorrect operation of live upgrade.
SEE ALSO
lu(1M), luactivate(1M), lucreate(1M), lucurr(1M), lufslist(1M), lustatus(1M), luupgrade(1M), attributes(5), live_upgrade(5)
WARNINGS
The lutab file is not a public interface. The format and contents of lutab are subject to change. Use lufslist(1M) and lustatus(1M) to
obtain information about BEs.
SunOS 5.10 8 Jun 2001 lutab(4)