Sponsored Content
Operating Systems Solaris Disks missing from /devices folder. Not sure why. Post 302836329 by DukeNuke2 on Wednesday 24th of July 2013 02:54:33 AM
Old 07-24-2013
Looks ok to me... Here is what I would do to check the system:

- boot from cd/dvd and check the format output for all disks (if this works try next point)
- boot to single user mode from your internal disk

if none of that works:

- update ALL firmware on the machine
- reseat all drives in their slots (the V440 diskbackplane has some known issues)

Last edited by DukeNuke2; 07-25-2013 at 03:34 AM..
 

9 More Discussions You Might Find Interesting

1. UNIX for Dummies Questions & Answers

checking missing files in side a folder

Dear all, Every hour i am receiving several data files to one folder for 24 hours each day.But some times some hours i do not have the files because of some problem.So i want to check the files inside the folder at the end of the day wether how many files i received in each hour like this.so i... (4 Replies)
Discussion started by: Nayanajith
4 Replies

2. UNIX for Dummies Questions & Answers

passthrough devices vs. named devices

I am having trouble understanding the difference between a passthrough device and a named device and when you would use one or the other to access equipment. As an example, we have a tape library and giving the command "camcontrol devlist" gives the following output: akx# camcontrol... (1 Reply)
Discussion started by: thumper
1 Replies

3. SCO

No stp SCSI devices configured (unit 0 missing)

Hi I've done migration of my SCO 5.0.6 from SCSI to IDE hard disk and now I'm getting in X windows this message: CONFIG: No Stp SCSI devices configured (unit 0 missing) Howto configure to get this message away? (4 Replies)
Discussion started by: ccc
4 Replies

4. Solaris

How to find missing disks on Sun x4150 without reboot?

Hi, Here is the issue: There are 4 disks on this Sun x4150 system under Solaris 10, but only 1 disk can be seen by the OS. I've tried commands disks and devfsadm but not working. It's an important production server, so 'reboot -r' is not a choice. # format < /dev/null Searching for... (6 Replies)
Discussion started by: aixlover
6 Replies

5. AIX

/dev/rmt devices are missing

Hello, I attached a tape drive to one of my partitions but i cannot find the device. I run the command lsdev|grep rmt but i dont get anything in return. When i run lsslot -c slot i can see the slot number and the device that belongs to the tape drive but i cannot find any rmt files in /dev.... (6 Replies)
Discussion started by: omonoiatis9
6 Replies

6. Solaris

Solaris 10 Installation - Disks missing, and Raid

Hey everyone. First, let me start by saying I'm primarily focused on linux boxes, and just happened to get pulled into building two T5220's. I'm not super educated on sun boxes. Both T5220's have 8 146GB 15k SAS drives. Inside the service processor, I can run SHOW /SYS/HDD{0-7} and they all come... (2 Replies)
Discussion started by: msarro
2 Replies

7. SuSE

How to resolve missing missing dependencies with opensuse 11.3 and 12.3?

Hello, This is a programming question as well as a suse question, so let me know if you think I should post this in programming. I have an application that I compiled under opensuse 12.2 using g77-3.3/g++3.3. The program compiles and runs just fine. I gave the application to a colleague who... (2 Replies)
Discussion started by: LMHmedchem
2 Replies

8. Solaris

Missing ASM Disks in Solaris 11.3 LDOM

Hi Guys, Just a quick question hopefully someone will have seen this before and will be able to enlighten me. I have been doing some Infrastructure Verification Testing and one of the tests was booting the primary domain from alternate disks, this all went well - however on restarting one of... (7 Replies)
Discussion started by: gull04
7 Replies

9. Shell Programming and Scripting

Bash to check directory and create missing folder from file

In the below bash I am trying to ensure that all folders (represented by $folders) in a given directory are created. In the file f1 the trimmed folder will be there somewhere (will be multiple trimmed folders). When that trimmed folder is found (represented by $S5) the the contents of $2 printed... (19 Replies)
Discussion started by: cmccabe
19 Replies
bootconf(4)						     Kernel Interfaces Manual						       bootconf(4)

NAME
bootconf - boot device configuration table DESCRIPTION
The file contains the address and disk layout type of the system's boot devices or lif volumes. It is used by the and HP-UX kernel control scripts (fileset to determine how and where to update the initial boot loader. Normally the kernel's script queries the system's hardware and creates the file. In rare cases when either the system configuration cannot be automatically determined or additional and/or alternate boot devices should be automatically updated, the administrator must edit the file manually. There is one line in the file for each boot device. Each line contains the following blank-separated fields in the order shown: disk type A flag indicating how the file system(s) on the disk are laid out. The flag must be one of the following: Indicates that the root disk is in LVM or VERITAS Volume Manager (VxVM) format. If LVM or VxVM mirrors are used, then each of the "mirrors" must have its own line in the file. Indicates that the root disk is in the "whole disk" format with no partitions, but boot and swap space are reserved outside the file system. device file The absolute path of the device special file that accesses the physical device where the boot area is located. For LVM root disks, the device special file is the physical volume(s) returned by the command. For "whole disks" this is the device file that references the entire disk. Blank lines are permitted. Any line beginning with a is considered to be a comment. DIAGNOSTICS
The Software Distributor log file contains diagnostic messages under the fileset if the file is incorrect. Most of the messages are self- explanatory; a few warrant additional explanation: If there are no other messages about the file is probably empty. Otherwise, the file is not in the proper format, and the other messages will explain what the problem is. The specified device file does not point to a disk where there is a lif which contains the file Some character other than or is in the first field of a line. As of release 10.0, the boot areas in must all be on the same type of disk layout. There are characters after the device file specification. EXAMPLES
The boot area is on an LVM root disk: l /dev/disk/disk7_p2 The boot area is on a whole disk layout: w /dev/disk/disk7 WARNINGS
All of the boot devices in the file must have the same disk layout. AUTHOR
was developed by the Hewlett-Packard Company. FILES
SEE ALSO
mediainit(1), hpux(1M), hpux.efi(1M), mkboot(1M), vgdisplay(1M), lif(4), intro(7). documentation. bootconf(4)
All times are GMT -4. The time now is 07:40 AM.
Unix & Linux Forums Content Copyright 1993-2022. All Rights Reserved.
Privacy Policy