|
|
Sponsored Content
Operating Systems
Solaris
Live Upgrade Patching Error: Unable to write vtoc
Post 302725755 by Siralos on Friday 2nd of November 2012 02:50:08 PM
11-02-2012
Code:
It seems that the disk layout appears to be incorrect. * /dev/rdsk/c0t5000C50039FEF187d0s0 partition map * * Dimensions: * 512 bytes/sector * 63 sectors/track * 255 tracks/cylinder * 16065 sectors/cylinder * 17847 cylinders * 17845 accessible cylinders * * Flags: * 1: unmountable * 10: read-only * * Unallocated space: * First Sector Last * Sector Count Sector * 286678272 1653 286679924 * * First Sector Last * Partition Tag Flags Sector Count Sector Mount Directory 0 2 00 20352 286657920 286678271 2 5 00 0 286678272 286678271 8 1 01 0 20352 20351
but ( 16065*17845 = 286679925 ) and 286679925 - 286679924 = -1
The disk is currently only partitioned out to have 286678271 as the last sector. The unallocated space is the missing space that is now appears to be causing my or rather LU issue.
I guess I could make a flash archive of the system and use JET and the FLAR
|
|
6 More Discussions You Might Find Interesting
1. Solaris
Hello,
I have a doubt regarding patching and OS upgrade. What is the difference when i install a Recomended Patch Cluster using installcluster script on a solaris10 update 6 server vs Upgrading Solaris 10 update 6 to update 10 ?
I have applied update10 Recomended Patch Cluster on a... (1 Reply)
Discussion started by: fugitive
1 Replies
2. Solaris
I have Solaris-10 sparc box with ZFS file-system, which is running two non global zones. I am in process of applying Solaris Recommended patch cluster via Live Upgrade.
Though I have enough space in root file-system of both zones, everytime I run installcluster, it fails with complaining less... (7 Replies)
Discussion started by: solaris_1977
7 Replies
3. Red Hat
Hello,
Sorry for posting here..i know there is another section for Urgent...However, i could not locate it...
Issue: ) After patching rhel 5.8 with couple of patches. When user is trying to login via putty . They get login promt and when they type their username, screen get freezed kindaa... (3 Replies)
Discussion started by: saurabh84g
3 Replies
4. Solaris
Hello,
I was assigned some Solaris machines and need to patch them to N-1, where N is the latest OS realease, which means, upgrade till one version before the latest one.
I do not now a lot about Solaris. What I only know is that need to make use of live upgrade and be careful with VxVM... (4 Replies)
Discussion started by: feroccimx
4 Replies
5. Solaris
Hi all,
I would like to ask what will be the best practice for the following setup
/ - c0t0d0s0 - current BE (named First)
/ - c0t0d1s0 - alternate BE (name Second)
i have a non-global zone with zonepath in /zones/myzone
/mnt/opt - c0t0d2s6 (shared between the 2 BE)... (3 Replies)
Discussion started by: javanoob
3 Replies
6. Solaris
Hi,
I have Solaris-10 x86 (running on HP hardware), with 12 non-global zones running on this. I have to install latest patch cluster/set on this server. This server is not under backup schedule, so before installing patch cluster, I want to keep a backup. In case of any issue (bad patch or... (4 Replies)
Discussion started by: solaris_1977
4 Replies
LEARN ABOUT SUNOS
lurename
lurename(1M) System Administration Commands lurename(1M) NAME
lurename - change the name of a boot environment SYNOPSIS
/usr/sbin/lurename -e BE_name -n new_name [-l error_log] [-o outfile] [-X] DESCRIPTION
The lurename command is part of a suite of commands that make up the Live Upgrade feature of the Solaris operating environment. See live_upgrade(5) for a description of the Live Upgrade feature. The lurename command renames the boot environment (BE) BE_name to new_name. The string new_name must not exceed 30 characters in length and must consist only of alphanumeric characters and other ASCII characters that are not special to the Unix shell. See the "Quoting" section of sh(1). The BE name can contain only single-byte, 8-bit characters. It cannot contain whitespace characters. Also, new_name must be unique on the system. A BE must have the status "complete" before you rename it. Use lustatus(1M) to determine a BE's status. Also, you cannot rename a BE that has file systems mounted with lumount(1M) or mount(1M). Renaming a BE is often useful when you upgrade the BE from one Solaris release to another. For example, following an operating system upgrade, you might rename the BE solaris7 to solaris8. The lurename command requires root privileges. OPTIONS
The lurename command has the options listed below. -e BE_name Name of the BE whose name you want to change. -l error_log Error and status messages are sent to error_log, in addition to where they are sent in your current environment. -n new_name New name of the BE. new_name must be unique on a given system. -o outfile All command output is sent to outfile, in addition to where it is sent in your current environment. -X Enable XML output. Characteristics of XML are defined in DTD, in /usr/share/lib/xml/dtd/lu_cli.dtd.<num>, where <num> is the version number of the DTD file. EXIT STATUS
The following exit values are returned: 0 Successful completion. >0 An error occurred. FILES
/etc/lutab list of BEs on the system /usr/share/lib/xml/dtd/lu_cli.dtd.<num> Live Upgrade DTD (see -X option) ATTRIBUTES
See attributes(5) for descriptions of the following attributes: +-----------------------------+-----------------------------+ | ATTRIBUTE TYPE | ATTRIBUTE VALUE | +-----------------------------+-----------------------------+ |Availability |SUNWluu | +-----------------------------+-----------------------------+ SEE ALSO
lu(1M), luactivate(1M), lucancel(1M), lucompare(1M), lucreate(1M), lucurr(1M), ludelete(1M), ludesc(1M), lufslist(1M), lumake(1M), lumount(1M), lustatus(1M), luupgrade(1M), lutab(4), attributes(5), live_upgrade(5) SunOS 5.10 24 Jan 2002 lurename(1M)