disk replacment, SUN M3000 Post: 302594988

Sponsored Content

Homework and Emergencies Emergency UNIX and Linux Support disk replacment, SUN M3000 Post 302594988 by robsonde on Wednesday 1st of February 2012 05:51:07 PM

02-01-2012

Registered User

disk replacment, SUN M3000

we have a SUN M3000 server.
setup as only 1 domain.

disk c0t0d0 and c0t1d0 and setup as SVM mirrors.

a few days ago disk T1 failed.
new we have replaced the disk, but can's see the disk in format.

have done cfgadm and devfsadm.
still can't access the new disk in format.

the output of some command that maybe of help...

Code:

# uname -a
SunOS server_name 5.10 Generic_144488-08 sun4u sparc SUNW,SPARC-Enterprise

# cfgadm -al
Ap_Id                          Type         Receptacle   Occupant     Condition
SB0                            System_Brd   connected    configured   ok
SB0::cpu0                      cpu          connected    configured   ok
SB0::memory                    memory       connected    configured   ok
SB0::pci0                      io           connected    configured   ok
SB0::pci1                      io           connected    configured   ok
SB0::pci8                      io           connected    configured   ok
c0                             scsi-sata    connected    configured   unknown
c0::dsk/c0t0d0                 disk         connected    configured   unknown
c0::dsk/c0t1d0                 disk         connected    configured   unknown
c0::dsk/c0t2d0                 disk         connected    configured   unknown
c0::dsk/c0t3d0                 disk         connected    configured   unknown
c0::dsk/c0t4d0                 CD-ROM       connected    configured   unknown
c1                             fc-fabric    connected    configured   unknown
c1::50001fe1500d1f78           array-ctrl   connected    configured   unknown
c1::50001fe1500d1f7c           array-ctrl   connected    configured   unknown

# format
Searching for disks...done


AVAILABLE DISK SELECTIONS:
       0. c0t0d0 <FUJITSU-MBD2147RC-3701 cyl 14087 alt 2 hd 24 sec 848>
          /pci@0,600000/pci@0/pci@0/scsi@0/sd@0,0
       1. c0t2d0 <FUJITSU-MBD2300RC-3701-279.40GB>
          /pci@0,600000/pci@0/pci@0/scsi@0/sd@2,0
       2. c0t3d0 <FUJITSU-MBD2300RC-3701-279.40GB>
          /pci@0,600000/pci@0/pci@0/scsi@0/sd@3,0
       3. c1t50001FE1500D1F7Cd1 <HP-HSV200-6240-25.00GB>
          /pci@1,700000/pci@0/pci@9/SUNW,qlc@0/fp@0,0/ssd@w50001fe1500d1f7c,1
       4. c1t50001FE1500D1F78d1 <HP-HSV200-6240-25.00GB>
          /pci@1,700000/pci@0/pci@9/SUNW,qlc@0/fp@0,0/ssd@w50001fe1500d1f78,1
Specify disk (enter its number): ^D

what magic is needed to make Solaris access the disk?

50K bits to anyone who can solve this problem.

robsonde

View Public Profile for robsonde

Find all posts by robsonde

8 More Discussions You Might Find Interesting

1. UNIX for Dummies Questions & Answers

multiple disk in sun os

i have unix box , which currently has 2 scsi disk , as shown by format command, one at target 1 and another at target3 (which is current boot disk). can i use both the disk , if so will df -k show usage of both ? can any one guide me how to span file system across multiple disk. i m using sun 5.7...

2. UNIX for Advanced & Expert Users

Help: Sun Disk partitioning for Sun V240 & StorEdge 3300

Dear Sun gurus, I have Sun Fire V240 server with its StorEdge 3300 disk-array. Following are its disks appeared in format command. I have prepared its partitions thru format and metainit & metattach (may be i have made wrong steps, causing the errors below because I have done thru some document...

3. Solaris

SUN T5240 vs M3000

Hi, We are planning to buy new server for our data center. Sun T5240 or M3000 which one have better performance, we are going to create many dt sessions in this server. So, i need your suggestions. RJS

4. Solaris

XSCF on M3000

Hi, I've updated a few M3000s to new firmware without any hassle, but on one of them the following is happening: XSCF> getflashimage -u wayner ftp://10.16.122.200/tftpboot/IKXCP1102.tar.gz Error: insufficient free space Any idea how to delete whatever old firmware is on there so I can...

5. SCO

sco 5.0.5 5.0.6 openscource replacment ?

is there a version of anything linux distro that could clone/emulate sco close enough to run the 1 software program we keep this server for ? boil this question down some if a program is running on a sco system now are there any alternatives ?

6. Solaris

Help with faulty Disk on Sun OS

Hi, Recently i came across a disk that seems to be faulty and need help. I have gathered some information by running below commands and any help on how to solve this will be great. # uname –a SunOS XYZ 5.7 Generic_106541-16 sun4u sparc SUNW,Ultra-4 #df -k Filesystem kbytes used...

7. Solaris

Application running too slow on Sun SPARC T5440 but run normal on sun M3000

Hi all, I have application running on sun server T5440 4x8x1.4 GHz, 64 GB RAM, application running very slow though load average too low. when I install my application on another server SUN M3000 (One CPU 1x8x2.5GHz, 8GB RAM), application run smoothly. Here is my server T5440 info: ...

8. UNIX for Beginners Questions & Answers

Help with sed replacment

Hi All, I am new to Unix and have a simple question. I would like to do three sed replacements in a large text file. The command I am using is as follows.... sed –n –e ‘s/:A/:X/’ –e ‘s/:B/:Y/’ –e ‘s/:C/:Z/’ myfile.txt > myfile_SED.txt The : need to be the search to identify specific :A, :B,...

LEARN ABOUT SUNOS

systemd-machine-id-commit.service

SYSTEMD-MACHINE-ID-COMMIT.SERVICE(8)			 systemd-machine-id-commit.service		      SYSTEMD-MACHINE-ID-COMMIT.SERVICE(8)

NAME

       systemd-machine-id-commit.service - Commit a transient machine ID to disk

SYNOPSIS

       systemd-machine-id-commit.service

DESCRIPTION

       systemd-machine-id-commit.service is an early boot service responsible for committing transient /etc/machine-id files to a writable disk
       file system. See machine-id(5) for more information about machine IDs.

       This service is started after local-fs.target in case /etc/machine-id is a mount point of its own (usually from a memory file system such
       as "tmpfs") and /etc is writable. The service will invoke systemd-machine-id-setup --commit, which writes the current transient machine ID
       to disk and unmount the /etc/machine-id file in a race-free manner to ensure that file is always valid and accessible for other processes.
       See systemd-machine-id-setup(1) for details.

       The main use case of this service are systems where /etc/machine-id is read-only and initially not initialized. In this case, the system
       manager will generate a transient machine ID file on a memory file system, and mount it over /etc/machine-id, during the early boot phase.
       This service is then invoked in a later boot phase, as soon as /etc has been remounted writable and the ID may thus be committed to disk to
       make it permanent.

SEE ALSO

       systemd(1), systemd-machine-id-setup(1), machine-id(5), systemd-firstboot(1)

systemd 237												      SYSTEMD-MACHINE-ID-COMMIT.SERVICE(8)