Failing to boot - DMVA problem


 
Thread Tools Search this Thread
Top Forums UNIX for Dummies Questions & Answers Failing to boot - DMVA problem
# 8  
Old 03-21-2006
Looks like reloading the OS and software corrected the problem (at least for now.) I'm wondering if the invalid memory map caused the system to lose its marbles and reloading OS & software put its marbles back in place. Whatever....just glad it's fixed. Thanks again for the assistance, it's appreciated.
 
Login or Register to Ask a Question

Previous Thread | Next Thread

10 More Discussions You Might Find Interesting

1. Solaris

Problem boot 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

2. Solaris

Boot problem

Hi all, I have the the following SCSI diagnostic codes shown in the attached photo I suspect disk drive failure what can I do further to diagnose the disk. and if possible to boot into OS again. (5 Replies)
Discussion started by: h@foorsa.biz
5 Replies

3. Solaris

boot problem

hello i have a sun server V890 and it stops booting after adding 2 CPUs modules and gives me the following error message: Enabling system bus....... Done Initializing CPUs......... Done Initializing boot memory.. RAM-Copy CRC failure!Can't start: No image found FATAL: Can't find/decompress... (12 Replies)
Discussion started by: bahjatm
12 Replies

4. UNIX for Dummies Questions & Answers

boot problem

hello i have a sun server V890 and it stops booting after adding 2 CPUs modules and gives me the following error message: Enabling system bus....... Done Initializing CPUs......... Done Initializing boot memory.. RAM-Copy CRC failure!Can't start: No image found FATAL: Can't find/decompress... (0 Replies)
Discussion started by: bahjatm
0 Replies

5. Solaris

flar restore with svm mirrors failing to create boot image

In a Solaris9 environment I'm trying to restore flash archive (flar) with SVM mirrored devices to same server via jumpstart server and it is failing to create boot file and drops down to a command prompt in single user mode, metastat -i and metastat -p output looks good when compared to the ones... (0 Replies)
Discussion started by: mbak
0 Replies

6. Solaris

Boot problem

Hi everyone, I have sun fire280R machine before i it is installed with solaris5.9 now i want to upgrade it but it not booting from the cd rom ....OK prompt also not comming i dont have solaris keyboard to press stop-A key...i have a intel supported keyboard ...what may be the problem it is... (1 Reply)
Discussion started by: alakshmanrao
1 Replies

7. UNIX for Advanced & Expert Users

unix server failing to boot

i have unix 5.4 running on team server hs failing to boot. when i turn it on, it prints the following lines on the screen and just stops: module ID 01: (0011) Main power supply ok module ID 01: (0012) checks ok module ID 01: (0020) test of SCSI device 0 x 0 in progress module ID 01:... (4 Replies)
Discussion started by: ronst
4 Replies

8. Solaris

solaris boot problem boot error loading interpreter(misc/krtld)

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

9. UNIX for Advanced & Expert Users

Boot Problem

Hi All. Yesterday my pc worked fine. Today when booting the sequence gets just past mounting the root filesystem - it then says ' Module dependencies up to date (no new kernel modules found).' At this point it hangs and goes no further! Does this sound familiar to anyone? I am running... (2 Replies)
Discussion started by: silvaman
2 Replies

10. UNIX for Advanced & Expert Users

Boot problem

we have a problem with a server UNIX SUN OS 5.7 : we tried to reboot it and we have the following error message : "boot load failed the file just loaded does not appear to be executable " we booted the server in single user mode with the cdrom we made the mirrored disk bootable we tried... (2 Replies)
Discussion started by: farzolito
2 Replies
Login or Register to Ask a Question
fverify(8)						      System Manager's Manual							fverify(8)

Name
       fverify - verify software subsets

Syntax
       fverify [-yn]

Description
       The  command  reads  subset  inventory  records	from standard input and verifies that the attributes for the files on the system match the
       attributes listed in the corresponding records.	Invoking with no arguments causes it to report errors to the standard  output  and  prompt
       the user for confirmation before making corrections.

       Missing	files and inconsistencies in file size, checksum, user id, group id, mode, and file type are reported.	If inconsistencies in user
       id, group id or mode are detected the user is asked if they are to be corrected. If a missing file is a directory, it will be created.  All
       errors and informational messages are logged to the file

       The utility uses when installing subsets to guarantee correct installation.

Options
       Specifying both options will cause the -y option to be ignored.

       -n     Error reporting only. When specified, reports errors and does not perform any fixes.

       -y     Fixes  only. When specified, fixes modes, UIDs and GIDs on any files which have incorrect values for these attributes. No user input
	      is required.

Restrictions
       Problems with file size, file type, and file checksum cannot be corrected.

       Because the subset inventories give file names as relative paths, run in the root directory to which the software is installed.

       Many of the files on the system cannot be read or modified without appropriate privilege. Attempting to run without  appropriate  privilege
       may result in an excess of access errors being reported.

Examples
       To use to report verification problems with the BASE subset on ULTRIX, Version 4.0 (VAX), use the following command:
       % cd /
       % /etc/stl/fverify -n </usr/etc/subsets/ULTBASE400.inv

       To correct all problems with the same subset without being presented any prompts or diagnostic output, type:
       % cd /
       % /etc/stl/fverify -y < /usr/etc/subsets/ULTBASE400.inv

       To  interactively  repair  verification	problems with the COMM subset on ULTRIX, Version 4.0 (RISC), use the fverify command with no argu-
       ments:
       % cd /
       % /etc/stl/fverify < /usr/etc/subsets/UDTCOMM400.inv

Diagnostics
       fverify: out of memory
       Not enough memory is available from the system.

       pathname: cannot stat (error-message)
       The file pathname is listed in the inventory but is not on the system.  The error-message explains why.

       pathname: file type `x' should be `y'
       The file is listed in the inventory as being of type `y', but the copy of the file on the disk is type `x'.  The file type codes are:

	      b  block device files
	      c  character device files
	      d  directory files
	      f  regular files
	      l  hard links
	      p  fifos (named pipes)
	      s  symbolic links

       pathname: checksum n should be m
       There is a checksum error on pathname.  The values n and m are the actual and expected values.

       pathname: size n should be m
       The size of file pathname is not as expected. The numbers n and m are the actual and expected values.

       pathname: gid n should be m
       The group id for pathname is not as expected. The group ids n and m are the actual and expected values.

       pathname: uid n should be m
       The user id for pathname is not as expected. The user ids n and m are the actual and expected values.

       pathname: permissions string1 should be string2
       The permissions for pathname are not as expected.  String1 and string2 are the actual and expected permissions. The format of  string1  and
       string2 is the same as that used by the command.

       Creating directory pathname
       The  directory  pathname  is listed in the input inventory but does not exist on the system.  The command will attempt to create the direc-
       tory.

       cannot correct pathname (error-message)
       A problem reported with pathname could not be corrected. The error-message explains why.

       pathname corrected
       A problem with pathname was successfully corrected.

       Cannot create dir pathname (error-message)
       The program could not create a directory it was attempting to create.  The accompanying error-message explains why.

       n verification errors encountered.
       m corrections performed.
       Before exiting, the program prints these statistics describing what had been done.

       The exit status from is the total number of errors detected minus the total number of successful fixes.

Files
       Subset inventory files

       Log File

See Also
       ls(1), stl_inv(5), setld(8)
       Guide to Preparing Software for Distribution on ULTRIX Systems

																	fverify(8)