Sponsored Content
Full Discussion: missing disk
Operating Systems HP-UX missing disk Post 302147770 by C3000 on Wednesday 28th of November 2007 11:58:31 AM
Old 11-28-2007
Hi jpetrecca

Below is the output from the command you suggest.

# ioscan -fnCdisk
Class I H/W Path Driver S/W State H/W Type Description
=======================================================================
disk 0 10/0/14/0.0.0 sdisk CLAIMED DEVICE SAMSUNG CDRW/DVD SM-3
52F
/dev/dsk/c0t0d0 /dev/rdsk/c0t0d0
disk 1 10/0/15/1.5.0 sdisk CLAIMED DEVICE QUANTUM Atlas4-9LVD
/dev/dsk/c3t5d0 /dev/rdsk/c3t5d0
disk 2 10/0/15/1.6.0 sdisk CLAIMED DEVICE SEAGATE ST39103LC
/dev/dsk/c3t6d0 /dev/rdsk/c3t6d0
#

It seems to suggest that everything is OK I think, however I still can't see lvol9 in a bdf and attempting a cd to any of the directories on that drive freezes the system.

The disk was set up in sam adding the whole disk as lvol9 to the existing vg00.

As the boot procedes I catch sight of lvol9 but I really need to access the boot log, where is this please?

Is there a chance the disk is not long dead?

Thanks

Ed
 

7 More Discussions You Might Find Interesting

1. UNIX for Dummies Questions & Answers

Hard Disk drive space gone missing...

Sorry if this is totally the wrong place to post this but I have a question or something rather thats bugging me. I got a new Dell Inspiron laptop the other day and I was expecting it to have 80G on it, well atleast 70 or so after installation of OS and such but after looking carefully yesterday, I... (8 Replies)
Discussion started by: Ecclesiastes
8 Replies

2. AIX

missing disk

Hi I am getting this output # lsvg -p tempvg tempvg: PV_NAME PV STATE TOTAL PPs FREE PPs FREE DISTRIBUTION hdiskpower1 active 816 0 00..00..00..00..00 hdiskpower2 active 816 0 ... (3 Replies)
Discussion started by: magasem
3 Replies

3. Solaris

ZFS disk label missing

I 'm having problem in importing a zfs pool was getting error device missing and upon further digging found that labels on my disk for zpool are missing Does anyone know how to recover from it ? root@essapl020-u006 # zdb -l /dev/dsk/emcpower0c --------------------------------------------... (0 Replies)
Discussion started by: fugitive
0 Replies

4. Solaris

Disk space missing under SVM

Hi Gurus, I've got an issue here: (1) Hardware: Sun NetraT1, (2) OS: Solaris 10, (3) SVM metastat shows /var having 12 GB. df shows /var having 4 GB. Real space for /var is about 4 GB since I can't move a big file to it. How is 8 GB space missing? Does /var/run swap need to account? Can I... (5 Replies)
Discussion started by: aixlover
5 Replies

5. Solaris

hard disk broken, relocate user's home dir. All setting missing

Hi, guys I am a super newbie in solaris admin.... Now I got a problem. Due to the broken of one of Raid system, some user home directory is missing. Someone advises me to relocate the home directory on the new drive. I have googled and have tried " usermode -d " command. But I found a... (3 Replies)
Discussion started by: dr_dw
3 Replies

6. 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

7. Red Hat

Yum - resolving missing dependencies that are not missing

I am trying to install VirtualBox on RHEL 5 but I need the 32 bit version for 32 bit Windows. When I run yum I get the following: sudo yum localinstall /auto/spvtg-it/spvss-migration/Software/VirtualBox-4.3-4.3.2_90405_el6-1.i686.rpm Loaded plugins: fastestmirror Setting up Local Package... (13 Replies)
Discussion started by: gw1500se
13 Replies
disks(1M)						  System Administration Commands						 disks(1M)

NAME
disks - creates /dev entries for hard disks attached to the system SYNOPSIS
/usr/sbin/disks [-C] [-r rootdir] DESCRIPTION
devfsadm(1M) is now the preferred command for /dev and should be used instead of disks. disks creates symbolic links in the /dev/dsk and /dev/rdsk directories pointing to the actual disk device special files under the /devices directory tree. It performs the following steps: 1. disks searches the kernel device tree to see what hard disks are attached to the system. It notes the /devices pathnames for the slices on the drive and determines the physical component of the corresponding /dev/dsk or /dev/rdsk name. 2. The /dev/dsk and /dev/rdsk directories are checked for disk entries - that is, symbolic links with names of the form cN[tN]dNsN, or cN[tN]dNpN, where N represents a decimal number. cN is the logical controller number, an arbitrary number assigned by this program to designate a particular disk controller. The first controller found on the first occasion this program is run on a system, is assigned number 0. tN is the bus-address number of a subsidiary controller attached to a peripheral bus such as SCSI or IPI (the target number for SCSI, and the facility number for IPI controllers). dN is the number of the disk attached to the controller. sN is the slice number on the disk. pN is the FDISK partition number used by fdisk(1M). (x86 Only) 3. If only some of the disk entries are found in /dev/dsk for a disk that has been found under the /devices directory tree, disks creates the missing symbolic links. If none of the entries for a particular disk are found in /dev/dsk, disks checks to see if any entries exist for other disks attached to the same controller, and if so, creates new entries using the same controller number as used for other disks on the same controller. If no other /dev/dsk entries are found for slices of disks belonging to the same physical con- troller as the current disk, disks assigns the lowest-unused controller number and creates entries for the disk slices using this newly-assigned controller number. disks is run automatically each time a reconfiguration-boot is performed or when add_drv(1M) is executed. When invoking disks(1M) manually, first run drvconfig(1M) to ensure /devices is consistent with the current device configuration. Notice to Driver Writers disks considers all devices with a node type of DDI_NT_BLOCK, DDI_NT_BLOCK_CHAN, DDI_NT_CD, DDI_NT_BLOCK_WWN or DDI_NT_CD_CHAN to be disk devices. disks(1M) requires the minor name of disk devices obey the following format conventions. The minor name for block interfaces consists of a single lowercase ASCII character, a through u. The minor name for character (raw) inter- faces consists of a single lowercase ASCII character, a through u, followed by ,raw. disks translates a through p to s0 through s15, while it translates q through u to p0 through p4. SPARC drivers should only use the first 8 slices: a through h, while x86 drivers can use a through u, with q through u corresponding to fdisk(1M) partitions. q represents the entire disk, while r, s, t, and u represent up to 4 additional partitions. To prevent disks from attempting to automatically generate links for a device, drivers must specify a private node type and refrain from using a node type: DDI_NT_BLOCK, DDI_NT_BLOCK_CHAN, DDI_NT_CD, or DDI_NT_CD_CHAN when calling ddi_create_minor_node(9F). OPTIONS
The following options are supported: -C Causes disks to remove any invalid links after adding any new entries to /dev/dsk and /dev/rdsk. Invalid links are links which refer to non-existent disk nodes that have been removed, powered off, or are otherwise inaccessible. -r rootdir Causes disks to presume that the /dev/dsk, /dev/rdsk and /devices directory trees are found under rootdir, not directly under /. ERRORS
If disks finds entries of a particular logical controller linked to different physical controllers, it prints an error message and exits without making any changes to the /dev directory, since it cannot determine which of the two alternative logical-to-physical mappings is correct. The links should be manually corrected or removed before another reconfiguration-boot is performed. EXAMPLES
Example 1: Creating Block and Character Minor Devices The following example demonstrates creating the block and character minor devices from within the xkdisk driver's attach(9E) function. #include <sys/dkio.h> /* * Create the minor number by combining the instance number * with the slice number. */ #define MINOR_NUM(i, s) ((i) << 4 | (s)) int xkdiskattach(dev_info_t *dip, ddi_attach_cmd_t cmd) { int instance, slice; char name[8]; /* other stuff in attach... */ instance = ddi_get_instance(dip); for (slice = 0; slice < V_NUMPAR; slice++) { /* * create block device interface */ sprintf(name, "%c", slice + 'a'); ddi_create_minor_node(dip, name, S_IFBLK, MINOR_NUM(instance, slice), DDI_NT_BLOCK_CHAN, 0); /* * create the raw (character) device interface */ sprintf(name,"%c,raw", slice + 'a'); ddi_create_minor_node(dip, name, S_IFCHR, MINOR_NUM(instance, slice), DDI_NT_BLOCK_CHAN, 0); } } Installing the xkdisk disk driver on a Sun Fire 4800, with the driver controlling a SCSI disk (target 3 attached to an isp(7D) SCSI HBA) and performing a reconfiguration-boot (causing disks to be run) creates the following special files in /devices. # ls -l /devices/ssm@0,0/pci@18,700000/pci@1/SUNW,isptwo@4/ brw-r----- 1 root sys 32, 16 Aug 29 00:02 xkdisk@3,0:a crw-r----- 1 root sys 32, 16 Aug 29 00:02 xkdisk@3,0:a,raw brw-r----- 1 root sys 32, 17 Aug 29 00:02 xkdisk@3,0:b crw-r----- 1 root sys 32, 17 Aug 29 00:02 xkdisk@3,0:b,raw brw-r----- 1 root sys 32, 18 Aug 29 00:02 xkdisk@3,0:c crw-r----- 1 root sys 32, 18 Aug 29 00:02 xkdisk@3,0:c,raw brw-r----- 1 root sys 32, 19 Aug 29 00:02 xkdisk@3,0:d crw-r----- 1 root sys 32, 19 Aug 29 00:02 xkdisk@3,0:d,raw brw-r----- 1 root sys 32, 20 Aug 29 00:02 xkdisk@3,0:e crw-r----- 1 root sys 32, 20 Aug 29 00:02 xkdisk@3,0:e,raw brw-r----- 1 root sys 32, 21 Aug 29 00:02 xkdisk@3,0:f crw-r----- 1 root sys 32, 21 Aug 29 00:02 xkdisk@3,0:f,raw brw-r----- 1 root sys 32, 22 Aug 29 00:02 xkdisk@3,0:g crw-r----- 1 root sys 32, 22 Aug 29 00:02 xkdisk@3,0:g,raw brw-r----- 1 root sys 32, 23 Aug 29 00:02 xkdisk@3,0:h crw-r----- 1 root sys 32, 23 Aug 29 00:02 xkdisk@3,0:h,raw /dev/dsk will contain the disk entries to the block device nodes in /devices # ls -l /dev/dsk /dev/dsk/c0t3d0s0 -> ../../devices/[...]/xkdisk@3,0:a /dev/dsk/c0t3d0s1 -> ../../devices/[...]/xkdisk@3,0:b /dev/dsk/c0t3d0s2 -> ../../devices/[...]/xkdisk@3,0:c /dev/dsk/c0t3d0s3 -> ../../devices/[...]/xkdisk@3,0:d /dev/dsk/c0t3d0s4 -> ../../devices/[...]/xkdisk@3,0:e /dev/dsk/c0t3d0s5 -> ../../devices/[...]/xkdisk@3,0:f /dev/dsk/c0t3d0s6 -> ../../devices/[...]/xkdisk@3,0:g /dev/dsk/c0t3d0s7 -> ../../devices/[...]/xkdisk@3,0:h and /dev/rdsk will contain the disk entries for the character device nodes in /devices # ls -l /dev/rdsk /dev/rdsk/c0t3d0s0 -> ../../devices/[...]/xkdisk@3,0:a,raw /dev/rdsk/c0t3d0s1 -> ../../devices/[...]/xkdisk@3,0:b,raw /dev/rdsk/c0t3d0s2 -> ../../devices/[...]/xkdisk@3,0:c,raw /dev/rdsk/c0t3d0s3 -> ../../devices/[...]/xkdisk@3,0:d,raw /dev/rdsk/c0t3d0s4 -> ../../devices/[...]/xkdisk@3,0:e,raw /dev/rdsk/c0t3d0s5 -> ../../devices/[...]/xkdisk@3,0:f,raw /dev/rdsk/c0t3d0s6 -> ../../devices/[...]/xkdisk@3,0:g,raw /dev/rdsk/c0t3d0s7 -> ../../devices/[...]/xkdisk@3,0:h,raw FILES
/dev/dsk/* Disk entries (block device interface) /dev/rdsk/* Disk entries (character device interface) /devices/* Device special files (minor device nodes) ATTRIBUTES
See attributes(5) for descriptions of the following attributes: +-----------------------------+-----------------------------+ | ATTRIBUTE TYPE | ATTRIBUTE VALUE | +-----------------------------+-----------------------------+ |Availability |SUNWcsu | +-----------------------------+-----------------------------+ SEE ALSO
add_drv(1M), devfsadm(1M), fdisk(1M), attributes(5), isp(7D), devfs(7FS), dkio(7I), attach(9E), ddi_create_minor_node(9F) Writing Device Drivers BUGS
disks silently ignores malformed minor device names. SunOS 5.10 7 Nov 2002 disks(1M)
All times are GMT -4. The time now is 11:09 PM.
Unix & Linux Forums Content Copyright 1993-2022. All Rights Reserved.
Privacy Policy