Sponsored Content
Full Discussion: raidctl on SUN T5240
Operating Systems Solaris raidctl on SUN T5240 Post 302224218 by DukeNuke2 on Tuesday 12th of August 2008 02:20:10 PM
Old 08-12-2008
you have booted from c0t0d0? if so, you can't use raidctl on this disk cause it is already in use. you have to boot from cd/dvd and setup the raid BEFORE the os installation!
 

9 More Discussions You Might Find Interesting

1. UNIX for Dummies Questions & Answers

disksuite and raidctl used together

I have a live Sunfire v440 server with 4 drives and I want to mirror drive 0 & 1 to 2 & 3. The on-board raid controller only allows for 1 live mirror. I was thinking of disksuite, but unfortunately the second disk is just one large partition with no free slices. I was thinking of using... (0 Replies)
Discussion started by: csgonan
0 Replies

2. UNIX for Dummies Questions & Answers

raidctl and resync when reboot

I am using raidctl on a v440 disk and noticed it resyncs after every boot, which takes about 30 minutes because of the size of the partition. I am concerned with what happens during the resync if "writes" happen to the disk before it is complete? Any info would be helpful. Thanks (0 Replies)
Discussion started by: csgonan
0 Replies

3. Solaris

raidctl

At my own eys I can see 4 disks inside of server. Previous admin told me that hardware mirror is done. What I see with "format" is 2 disks - I suspect that these are 2 MIRRORS. I just cant be sure because raidctl show this: # raidctl -l c0t0d0 Volume Size Stripe ... (0 Replies)
Discussion started by: czezz
0 Replies

4. UNIX for Advanced & Expert Users

Solaris 10 Raidctl

Hello World: Recently I ran into an issue where a collegue had installed a Sun T5140 with twin 136GB disks in them. However, he forgot to execute the raidctl command first to mirror c1t0d0 to c1t1d0 boo hoo:) So along I come and try to mirror the disks by booting to sigle user... (1 Reply)
Discussion started by: rambo15
1 Replies

5. UNIX for Dummies Questions & Answers

Information About raidctl

Hello people i have a question, when i put raidctl -l on sun fire show this Volume Size Stripe Status Cache RAID Sub Size Level Disk ... (0 Replies)
Discussion started by: enkei17
0 Replies

6. Solaris

Raidctl - Sun T5240 Solaris 10 Problem

I tried using raidctl earlier today to use my 2 disks in a RAID1 setup and I totally destroyed my OS install. I'm sure I did something funky and it freaked out. No big deal...right? This is what I was seeing after a reboot. I decided to just reinstall the OS. It let me go through all of... (3 Replies)
Discussion started by: kingdbag
3 Replies

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

8. Shell Programming and Scripting

help in a script using raidctl

getStatusi86() { #storing logical volume name volumelist=`cfgadm -val | grep "Logical Volume" | awk '{print substr($1,9,14)}'` controller=`echo $volumelist | awk '{print substr($1,2,1)}'` #errordisk="" volume1=`echo $volumelist | awk '{print $1}'` for volume in $volumelist do... (1 Reply)
Discussion started by: frintocf
1 Replies

9. Solaris

Bizarre Sun T5240 behavior

Hi - I have a T5240 with 7 LDOMS configured. One night, network comm was broken somehow. Nobody was doing anything on the machine at the time. Here is what I saw in messages: WARNING: nxge3 : nxge_dma_mem_alloc: ddi_dma_mem_alloc kmem alloc failed WARNING: nxge3 : nxge_alloc_rx_buf_dma:... (2 Replies)
Discussion started by: pyroman
2 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 11:08 AM.
Unix & Linux Forums Content Copyright 1993-2022. All Rights Reserved.
Privacy Policy