Sponsored Content
Full Discussion: disk replacment, SUN M3000
Homework and Emergencies Emergency UNIX and Linux Support disk replacment, SUN M3000 Post 302594994 by DukeNuke2 on Wednesday 1st of February 2012 07:17:46 PM
Old 02-01-2012
the disk on target 1 is visible... have you tried a
Code:
# devfsadm -Cv
# devfsadm -v

?
if this won't work, you might need a reconfigure boot...
Code:
# touch /reconfigure
# init 6

 

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... (4 Replies)
Discussion started by: raju
4 Replies

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... (1 Reply)
Discussion started by: shafeeq
1 Replies

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 Replies)
Discussion started by: rajasekg
4 Replies

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... (7 Replies)
Discussion started by: cabaiste
7 Replies

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 ? (2 Replies)
Discussion started by: crosbymook
2 Replies

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... (3 Replies)
Discussion started by: phanidhar6039
3 Replies

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: ... (6 Replies)
Discussion started by: insatiable1610
6 Replies

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,... (3 Replies)
Discussion started by: landrjos
3 Replies
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)
All times are GMT -4. The time now is 07:10 AM.
Unix & Linux Forums Content Copyright 1993-2022. All Rights Reserved.
Privacy Policy