Sponsored Content
Full Discussion: boot-archive issue
Operating Systems Solaris boot-archive issue Post 302297666 by pupp on Saturday 14th of March 2009 10:55:59 AM
Old 03-14-2009
you need to boot off the failsafe archive. bring system down to obp. then use
Code:
boot -F failsafe

and follow instructions.

fyi - from the times i remember doing this, i had to perform this several times before it became stable. no clue why. however, if the system comes up and looks stable, make sure you reboot to confirm. also, you may need to remove any metadevices first before hand.
 

10 More Discussions You Might Find Interesting

1. UNIX for Dummies Questions & Answers

boot up issue

Could somone please tell me what happened when I reboot my computer, it take too long to pass the part it said "starting sendmail" I only changed the server name and when I reboot the server, all of the services are running except when it got to : starting sendmail it take toooo long to... (1 Reply)
Discussion started by: lapnguyen
1 Replies

2. Shell Programming and Scripting

Tar archive issue

Hi, I make a tar archive: tar -czvf /path_to/cucu.tar.gz /path/dir_to_archive/ In the archive the /path/dir_to_archive/ is maintained for every file. I need that the archive to be made without the /path/dir_to_archive/ to contain only the files in /path/dir_to_archive/. Thanks,... (4 Replies)
Discussion started by: potro
4 Replies

3. HP-UX

hp-ux 10.20 boot issue

Hello, have HP Visualize C3600 workstation. Issue is as follows: When I attempt to boot, unit will not boot successfully and will halt at a menu, the same menu as when during a boot one hits any key within 10 seconds to discontinue. When I attempt to boot with Boot primary, both with IPL... (17 Replies)
Discussion started by: davel1000
17 Replies

4. Solaris

Cannot mount boot archive

hi, I' ve found an error while starting up solaris 10, so I booted in safe mode from grub and modified the menu.lst with vi, to obtain a verbose output of the error. It says failed to readsuperblock diskread reading beyound end of ramdisk start = 0x800 size=0x800 ... ... panic: cannot... (9 Replies)
Discussion started by: freeware
9 Replies

5. Solaris

zfs root flash archive issue

I have created a flash archive from a Ldom on T5220 with zfs root solaris 10_u8. But after creation of flar the info shows the content_architectures=sun4c,sun4d,sun4m,sun4u,sun4us,sun4s but not sun4v due to which i 'm unable to install this flash archive on another Ldom on the same host. Is... (0 Replies)
Discussion started by: fugitive
0 Replies

6. Solaris

Boot-archive Problem

I disabled the boot-archive service by using #svcadm disable svc:/system/boot-archive:default then i rebooted my system but i am unable to boot. It throws the following errors CONSOLE LOGIN SERVICE(S) CANNOT RUN then it automatically asked me for the maintenance mode passwd. i logged... (3 Replies)
Discussion started by: dinu
3 Replies

7. UNIX for Advanced & Expert Users

scp/untar in parallel issue tar : Unexpected EOF in archive

Hi Guys, I am facing a strange issue while doing parallel (using & for background) scp/untar operation from my unix box to multiple unix boxes... I am getting tar : unexpected EOF in archive error the code is as follows.,,, for i in 10 do sh -c "scp <command> ; ssh tar -xf <tar> -C... (1 Reply)
Discussion started by: mihirvora16
1 Replies

8. Solaris

Boot archive file sizes are different on cluster units

Hi experts, I would have a question on boot archive files on solaris10 platform running on T5220 cluster servers. When we check the /platform/sun4v directory , and perform boot archive-list , we see that on both units same files exist. And when we mount the boot archive we see that all files... (0 Replies)
Discussion started by: dyavuzy1
0 Replies

9. Solaris

V100 boot issue

In the server room at my new job, there is a V100 with a problem. When power is turned on, the machine goes to the lom prompt. Entering poweron yields an endless supply of this message with no way to break out of it. ********************************************** PSTATE=0000000000000015... (3 Replies)
Discussion started by: chilinski
3 Replies

10. SCO

Issue during boot

Hi, I am using SCO OpenServer 5 During boot I get this message: PANIC: HTFS: Bad directory ino 2 (offset 0) on HTFS dev hd (1/42) Cannot dump 8095 pages to dumpdev hd (1/41): Space for only 0 pages Dump not completed How can I fix this? I have no boot/root floppy. If it is a "disk... (8 Replies)
Discussion started by: nubian_sundance
8 Replies
STABLERESTART(5)					      BSD File Formats Manual						  STABLERESTART(5)

NAME
nfs-stablerestart -- restart information for the NFSv4 server SYNOPSIS
nfs-stablerestart DESCRIPTION
The nfs-stablerestart file holds information that allows the NFSv4 server to restart without always returning the NFSERR_NOGRACE error, as described in the NFSv4 server specification; see Network File System (NFS) Version 4 Protocol RFC 3530, Section 8.6.3. The first record in the file, as defined by struct nfsf_rec in /usr/include/fs/nfs/nfsrvstate.h, holds the lease duration of the last incar- nation of the server and the number of boot times that follows. Following this are the number of previous boot times listed in the first record. The lease duration is used to set the grace period. The boot times are used to avoid the unlikely occurrence of a boot time being reused, due to a TOD clock going backwards. This record and the previous boot times with this boot time added is re-written at the end of the grace period. The rest of the file are appended records, as defined by struct nfst_rec in /usr/include/fs/nfs/nfsrvstate.h and are used represent one of two things. There are records which indicate that a client successfully acquired state and records that indicate a client's state was revoked. State revoke records indicate that state information for a client was discarded, due to lease expiry and an otherwise conflicting open or lock request being made by a different client. These records can be used to determine if clients might have done either of the edge conditions. If a client might have done either edge condition or this file is empty or corrupted, the server returns NFSERR_NOGRACE for any reclaim request from the client. For correct operation of the server, it must be ensured that the file is written to stable storage by the time a write op with IO_SYNC speci- fied has returned. This might require hardware level caching to be disabled for a local disk drive that holds the file, or similar. FILES
/var/db/nfs-stablerestart NFSv4 stable restart file /var/db/nfs-stablerestart.bak backup copy of the file SEE ALSO
nfsv4(4), nfsd(8) BUGS
If the file is empty, the NFSv4 server has no choice but to return NFSERR_NOGRACE for all reclaim requests. Although correct, this is a highly undesirable occurrence, so the file should not be lost if at all possible. The backup copy of the file is maintained and used by the nfsd(8) to minimize the risk of this occurring. To move the file, you must edit the nfsd sources and recompile it. This was done to discour- age accidental relocation of the file. BSD
April 10, 2011 BSD
All times are GMT -4. The time now is 10:44 PM.
Unix & Linux Forums Content Copyright 1993-2022. All Rights Reserved.
Privacy Policy