Status of RAID

I have a MAC PRO 8 Core with MAC OS Server, and I have configured two raid, but I need to know if RAID status is OK, now I use a command line, I have executed diskutil checkraid, but I need an automatic system that when any error acourrs send an email, message, because I can't execute every day manually this command, I need an automatic system
What can I do? It is possible to send for mail every day with the result of this command? Exist any other option?
Thanks

I guess it is time to let the cat out of the bag. For the past few months I have been running a homemade script on my Tiger server to do precisely what it sounds like you are asking for. I have verified that this works also with Leopard Server. If you would like, you could head over to my site and read up on and if desired, use checkraid. It is completely free for use. Hope this helps!
Peter Scordamaglia

Similar Messages

Display status of raid disk

I have create a raid set with two disks.
I have disconnect 1 of them but the system didn't show no warning for this fact.
If I look into disk utility then I see that raid is degraded, but no warning in find.
This may be a problem because if a disk is in failure and the system don't warn it, then you use the raid set like it is ok.
But you work only with one disk and you can have problem if also the second disk goes in failure.
Do you know if there is a way to have a warning if raid set is degraded?
Thanks.

So you have a mirror, and they are on (FW, eSATA, soemthing else?) and each has its own interface cable, right?
And the RAID was created with Apple Disk Utility, maybe Leopard rather than new Snow Leopard (there are usually changes to partition tables and features, and rebuilding is often a good idea - ONCE you know you want to. You may even want to wait until next OS update too.
If you want better warnings and features, buy SoftRAID, and faster mirror read performance.
Rebuild degraded mirror
http://www.macfixit.com/article.php?story=20090623123621959

Has anyone upgraded the Ironport ESA to 8.5.6-074 and had the issues of Raid status showing unknown?

Has anyone upgraded the Ironport ESA to 8.5.6-074 and had the issues of Raid status showing unknown? After we upgraded our appliances we are having issues with our ESA appliances showing the RAID status as unknown. When we reported the issue to CISCO we were updated there were no issues reported at all. Could anyone please confirm if you have experienced the same issue.

You should see OPTIMAL - meaning the drives in the C170 are in good health/status:
myc680.local> version
Current Version
===============
UDI: C680 V FCH1611V0B2
Name: C680
Product: Cisco IronPort C680 Messaging Gateway(tm) Appliance
Model: C680
Version: 8.5.6-074
Build Date: 2014-07-21
Install Date: 2014-07-29 11:16:34
Serial #: xxx-yyy1611Vzzz
BIOS: C240M3.1.4.5.2.STBU
RAID: 3.220.75-2196, 5.38.00_4.12.05.00_0x05180000
RAID Status: Optimal
RAID Type: 10
BMC: 1.05
There are times post-reboot, that you'll see and get notification of RAID sub-optimal --- meaning that the appliance is running through on a health-check of the appliance's RAID. You should be getting a notification once RAID status has returned to OPTIMAL, or as per the older OS revisions, READY:
myc170.local> version
Current Version
===============
UDI: C170 V01 FCH1428V06A
Name: C170
Description: Cisco IronPort C170
Product: Cisco IronPort C170 Messaging Gateway(tm) Appliance
Model: C170
Version: 7.6.3-019
Build Date: 2013-06-09
Install Date: 2014-09-12 13:52:24
Serial #: xxxxxxD87B39-yyyyyy8V06A
BIOS: 9B1C115A
RAID: 02
RAID Status: READY
RAID Type: 1
BMC: 2.01

RAID status in Conky

I wrote a tiny script to monitor the status of RAID arrays. It is written in awk and is meant to be used with conky. I have this in my conky config file:
RAID: ${execi 60 gawk -f path-to-the-script /proc/mdstat}
#!/bin/gawk -f
# This script checks the status of RAID arrays from /proc/mdstat
/_/ { state = "Warning!"; exit }
/blocks/ { state = $NF }
END { print state }
If everything is working correctly the ouput will be: "RAID: [UU]". It means that both drives are Up and running.
If there is something wrong with the drive it will give an error message: "RAID: [WARNING!]".
Maybe someone will find this usefull.

Thanks!
I have multiple RAIDs so I used the following command to check the status of a specific RAID:
${execi 60 cat /proc/mdstat | grep md126 -A 1 | gawk -f path-to-the-script --}
(replace md126 with the array you want to check)

RAID 0 Roaming Disk Problem - Way To Recover?

I have the problem generally described in this archieved thread [RAID 0|discussions.apple.com/thread.jspa?threadID=2041271&tstart=-3] and will describe it below, the thread is more for point of reference.
A few days ago the RAID went down (RAID 0)along the same lines described in this thread [RAID Error|http://discussions.apple.com/thread.jspa?threadID=2141573&tstart=0]
which in a nutshell, threw this error
Drive 3:5000cca349e4743d missing - Replace immediately or acknowledge loss of RAID set RS1 and associated volumes.
I immediatelly pulled out all the hard drives and cloned them in external hardware enclosures. At that point none of the drives had a fail message. During putting the drives back in I noticed that a drive sled looked slightly warped and would not fit back in properly. When the sled was in the drive would not show up, although two of the drives appeared as "roaming."
Got new sleds, and put the drives in. Could not get it the machine to boot in Safe Mode or properly from an external drive which was hooked up via Firewire (This was the system drive at the time of the freeze. It showed up as bootable when holding down the option key) or the clone of that system when placed in the machine. (I was on the phone for awhile with Apple Tach Support, and by the end it seemed it was a RAID card issue.) So I made an appointment for the Apple Genius Bar. I pulled out the old system drive with data, images and the rest and did a bare bones install of 10.5.1 (which came with the machine) and rebooted before bringing it into the Store, and the computer booted fine.
The "problem" RAID set was paritioned into two volumes. On my reboot after the install of the OS (and without using the RAID Utility to change anything, the RAID drives were simply in their bays), the two volumes are still there, sort of, as R2V1 and R2V2. Additionally all the drives SMART Status and RAID status are fine. One of the three drives is roaming however,
was and is being reported as RS1. Additionally, each of the drives in the RAID reports SMART status as fine, and each of the three drives report a RAID status of good. Additionally the RAID 0 had two volumes and both are reported currently as R2V1 and R2V2 and as being "good" and one of the drives has status of roaming. This is the furthest I have gotten trying to save this. I did not want to shut down the machine on the off chance that there is something else I can do right now before bringing the machine into the store.
The following pictures may make it easier to follow
!http://www.dvdstepbystep.com/Raid2.jpg!
!http://www.dvdstepbystep.com/raid.jpg!
The tower is an Early 2008 tower and I upgraded the firmware on the RAID card with the newest firmware, which required 10.5.8. The base install is back to 10.5.1 on the reboot after reinstall. I am also waiting to hear back from tech support.
Didn't realize the Apple RAID Card had a bad rep until this happened. Sheesh. Missed that one
But if there is anything to try right now, it would be great.

A A P L wrote:
Good luck.
Thanks
I know that I have been pretty happy, and when I did lose one drive, it did what it was supposed to do.
I did have it RAID 5 at one point, but set it up for internal RAID 0 for the renders, and it has been fine for a long time. Urgh.
Early on, there were battery warnings all the time, and the battery did not charge unless the Mac was ON, which was totally stupid.
Hmmm, sounds alot like mine there.
I found that out two Christmas vacations ago when we do our two-week shutdown.
Came back in, and could not use the Mac for two days while it charged.
They've since changed it, and thankfully, it's been good since.
Good luck, let us know how the new card works out.
SB
Thanks again and will do. Bought a bunch more hard drives and if it comes back, the first thing I do is back up the 2+ Terrabytes plus of renders (all ongoing projects), slap new drives into the tower, make it RAID 5 and to heck with the hit on speed. Have enough externals to reconfigure things, now just keeping fingers crossed

Raid Utility wont Initialize a volume

Hi.
My Raid Utility won't initialize last two volumes. I have 3 tasks, 2 volume initialize tasks are Suspended, after that there is one Rebuild task that has a Scheduled status (the loading bar, no status bar). I did some digging and cleared all the events in the Controller status list. Both volumes are working, but won't initialize ? I tried rebooting, i got few more events that raid card started the rebuild process, then aborted it, then started it again, then aborted, and then started again. General status is Raid is rebuilding, but still I am not seeing the real status bar, like i saw last time. Is it really doing something or jammed?
It looks like the 2 suspended tasks would be preventing the rebuild to start, but the event log says it has started. Will the volumes initialize properly after the rebuild or do I need to get them to initialize them somehow before the rebuild can start?

Usually the drives have to be formatted separately as well as partitioned separately.
However, I don't quite understand what you are doing. You currently have four 500 GB drives configured as a RAID 0+1 which I would understand to mean two 500 GB drives striped, a second pair striped. That is two 1 TB striped arrays that are then combined into a mirrored array which would be 1TB. Now as I understand you want to resize one 500 GB drive that is already in the array. This I don't get.

Hardware RAID on V440 - RAIDCTL reports strange size.

Got 4 disks in my system. Solaris installed on disk2. Others not used.
So, did :- raidctl -c c1t2d0 c1t3d0
Now it looks like t3 has disappeared now when I do format (as expected). Output of raidctl is-
bash-3.00# raidctl
Controller: 1
Volume:c1t2d0
Disk: 0.0.0
Disk: 0.1.0
Disk: 0.2.0
Disk: 0.3.0
Controller: 2
However, the strange thing is if I do raidctl -l c1t2do its reporting the volume size as 744Mb
raidctl -l c1t2d0
Volume Size Stripe Status Cache RAID
Sub Size Level
Disk
c1t2d0 744.9M N/A SYNC OFF RAID1
0.2.0 744.9M GOOD
0.3.0 744.9M GOOD
Since both disk are 146Gb I assume the volume size would 146Gb?
Also, since these two disks are now mirrored (or will be when the sync completes), if I get a disk failure what happens?
At the moment boot-disk is set to disk2. Will this still work if say physical disk2 fails but the mirror disk3 is still up? Or would I then need to boot from disk3?
Alternatively, could I remove a faulty disk2, replace disk3 int disk2 slot and still boot disk2?

Hi,
Weather the server is up and running now .
If it is up and running then just change the parameters of boot-disk to disk3.
Why because if suppose the server reboots it will not come up . So do this first .
Before doing this just check weather you have a bootblk in the both disks.
if not just install it
* installboot /usr/platform/`uname -i`/lib/fs/ufs/bootblk <path of the disk3>*
If this has not installed the server will try to come up but will still staying at OK prompt.

X4200 hardware raid not syncing

I got a x4200 with a RAID 1 configuration. Had a bad disk. Saw this in /var/adm/messages:
Mar 22 17:37:00 vps3      Physical disk (target 1) is |missing|
Mar 22 17:37:00 vps3      Physical disk (target 1) is |out of sync||missing|
raidctl -S too showed a failed disk:
c0t0d0               67.9G     N/A     DEGRADED OFF     RAID1
          0.0.0     67.9G          GOOD
          N/A     67.9G          FAILED
So, I took it out and then replaced it with a new disk. This is what is being shown in the logs:
Mar 23 20:25:22 vps3      Physical disk (target 1) is |out of sync||online|
However, instead of showing a SYNC status, why does it just say DEGRADED but both disk are good:
root@vps3:/# /usr/sbin/raidctl -l c0t0d0
Volume               Size     Stripe     Status     Cache     RAID
     Sub               Size               Level
          Disk
c0t0d0               67.9G     N/A     DEGRADED OFF     RAID1
          0.0.0     67.9G          GOOD
          0.1.0     67.9G          GOOD
I am wondering if this command is just lieing to me? How can I ensure the RAID is working properly at this point? What is the best way to delete 0.1.0 device and replace it again?
Thanks

midhu wrote:
Hardware RAID is configured in one of the new T3-1B blade server from ok prompt and I am able to see the details using show-volumes from ok prompt. But from Solaris OS it is not visible using raidctl -l command. It doesn't return anything. Is there any way to check the RAID status from OS. Making the OS down is not an option everytime.
# echo|format
Searching for disks...done
AVAILABLE DISK SELECTIONS:
0. c0t3CF77D9D2CF0BA99d0 <LSI-LogicalVolume-3000 cyl 65533 alt 2 hd 64 sec 139>
/pci@400/pci@1/pci@0/pci@2/LSI,sas@0/iport@v0/disk@w3cf77d9d2cf0ba99,0
Specify disk (enter its number): Specify disk (enter its number):
# raidctl -l
Edited by: midhu on Jan 26, 2013 5:30 AMYour server seems a little confused as to whether it is a T3 or T4, as you reference T4 in the title and T3 in the body.
raidctl may not be the correct utility because either:-
- (1) A different utility is now needed to configurare the raid for these onboard controllers on newer tin.
or
- (2) You are using an add in raid card that requires different software:
Please see for example: http://docs.oracle.com/cd/E22985_01/html/E22986/z40001e11389320.html

Is this how I stop getting a RAID error message on startup?

I have been looking around trying to find out how to resolve an error message I get - just looking to see if you can help me by letting me know if I have this correct...
I (not mine actually, but have use this Mac Pro while I work on a project) have an Apple RAID card, and on startup get this message..
"The Apple Raid Card installed on your system required your attention"
And usually within a few minutes the black curtain comes down and I need to restart.
If I simply clear the error events log in the RAID utility, will I no longer get this message?
And secondly - in the RAID utility, the bottom left corner has an almost empty battery and a yellow light - am i supposed to wait till this goes green (charged) before I ever restart or shut down the Mac?
As you can probably tell I have little Raid knowledge...
Cheers
Hugh

If the battery status on Raid Utility is showing yellow or not completely charged then you should definitely leave the computer on til it's completely charged and showing green. I have the Apple Raid Card in my 2008 Mac Pro 2.8 8 core. The FAQ's say that the battery reconditions itself every 3 months or so. Mine seems to do it more often. Probably cause I don't leave it on 24/7 and don't use my Mac Pro every day.
Try leaving the computer on overnight. It shouldn't take that long to charge. After it's done charging and shows green for the status, clear the message status and you should be good to go.

Raid performance deteriorates, looses drive, but no messages in event log

We have a PATA XServer Raid running, which was fine until a few weeks ago. Suddenly performance tanked, writing a 70 MB file via a 100 Mbps network would take an hour.
The Raid volume, a 6 drive 250 GB raid with one hotspare, had 100 GB left.
First we thought it was the network, there was a loose DHCP server, but nothing was available that could really explain the performance deterioration. The only thing that was noticed was that with Helios Lan test the first write to the raid would take more time as the subsequent writes. So we decided to upgrade the firmware and do a volume test, with diskutility. That gave a interleaf problem.
After upgrading the network (which was planned anyway) to 1 GBps, we rebooted the Xserve and the Raid. Now, the 6th drive had an orange status in Raid Admin, a warning, saying it was part of an Unknown Array. The 7th drive, the hot-swap, was now part of the Raid.
The strange thing is that in the event log there are no messages what so ever about a failed drive, nor any other messages relating to this. All I get is Coprocessor offline/Online, Raid Controller Restarted and Riad Controller 1 Fibre LIP, and Firmwareupdate
I also noticed that the time was off to local time, so I synchronized both to time.euro.apple.com.
Shouldn't we be getting messages something is very wrong in the event log?
XServe G5 Xserve Raid Mac OS X (10.3.9)

We updated the firmware to 1.5.1. After that, the network switch was replaced by a 1Gbps switch, and the XServe and the XServe raid were rebooted. After that one of the people discovered that disk 6 had an orange led burning.
XServe G5, XServe Raid Mac OS X Server (10.3.9) Raid Firmware 1.5.1

How to get a lower boot time in eee?

I've managed to lower my boot time to 14 seconds on the asus eee, but I know it can get lower that that... Apart from recompiling the kernel (which I intend to do last), can you suggest anything else might help?
Bootchart
My rc.conf
# /etc/rc.conf - Main Configuration for Arch Linux
# LOCALIZATION
# LOCALE: available languages can be listed with the 'locale -a' command
# HARDWARECLOCK: set to "UTC" or "localtime"
# USEDIRECTISA: use direct I/O requests instead of /dev/rtc for hwclock
# TIMEZONE: timezones are found in /usr/share/zoneinfo
# KEYMAP: keymaps are found in /usr/share/kbd/keymaps
# CONSOLEFONT: found in /usr/share/kbd/consolefonts (only needed for non-US)
# CONSOLEMAP: found in /usr/share/kbd/consoletrans
# USECOLOR: use ANSI color sequences in startup messages
LOCALE="en_US.utf8"
HARDWARECLOCK="UTC"
USEDIRECTISA="no"
TIMEZONE="Europe/Athens"
KEYMAP="us"
CONSOLEFONT=
CONSOLEMAP=
USECOLOR="yes"
# HARDWARE
# MOD_AUTOLOAD: Allow autoloading of modules at boot and when needed
# MOD_BLACKLIST: Prevent udev from loading these modules
# MODULES: Modules to load at boot-up. Prefix with a ! to blacklist.
# NOTE: Use of 'MOD_BLACKLIST' is deprecated. Please use ! in the MODULES array.
MOD_AUTOLOAD="yes"
#MOD_BLACKLIST=() #deprecated
MODULES=()
# Scan for LVM volume groups at startup, required if you use LVM
USELVM="no"
# NETWORKING
# HOSTNAME: Hostname of machine. Should also be put in /etc/hosts
HOSTNAME="asuseee"
# Use 'ifconfig -a' or 'ls /sys/class/net/' to see all available interfaces.
# Interfaces to start at boot-up (in this order)
# Declare each interface then list in INTERFACES
# - prefix an entry in INTERFACES with a ! to disable it
# - no hyphens in your interface names - Bash doesn't like it
# DHCP: Set your interface to "dhcp" (eth0="dhcp")
# Wireless: See network profiles below
eth0="eth0 192.168.0.2 netmask 255.255.255.0 broadcast 192.168.0.255"
INTERFACES=(eth0)
# Routes to start at boot-up (in this order)
# Declare each route then list in ROUTES
# - prefix an entry in ROUTES with a ! to disable it
gateway="default gw 192.168.0.1"
ROUTES=(!gateway)
# Enable these network profiles at boot-up. These are only useful
# if you happen to need multiple network configurations (ie, laptop users)
# - set to 'menu' to present a menu during boot-up (dialog package required)
# - prefix an entry with a ! to disable it
# Network profiles are found in /etc/network.d
# This now requires the netcfg package
#NETWORKS=(main)
# DAEMONS
# Daemons to start at boot-up (in this order)
# - prefix a daemon with a ! to disable it
# - prefix a daemon with a @ to start it up in the background
DAEMONS=(syslog-ng @crond @hal gdm)
My rc.sysinit
#!/bin/bash
# /etc/rc.sysinit
. /etc/rc.conf
. /etc/rc.d/functions
echo " "
printhl "Arch Linux\n"
printhl "${C_H2}http://www.archlinux.org"
printhl "Copyright 2002-2007 Judd Vinet"
printhl "Copyright 2007-2009 Aaron Griffin"
printhl "Distributed under the GNU General Public License (GPL)"
printsep
# mount /proc, /sys and our RAM /dev
/bin/mount -n -t ramfs none /dev
/bin/mount -n -t proc none /proc
/bin/mount -n -t sysfs none /sys
# Create our default nodes that minilogd may need
/bin/mknod /dev/null c 1 3
/bin/mknod /dev/zero c 1 5
/bin/mknod /dev/console c 5 1
# More initial /dev setup that udev doesn't do
/bin/ln -snf /proc/self/fd /dev/fd
/bin/ln -snf /proc/self/fd/0 /dev/stdin
/bin/ln -snf /proc/self/fd/1 /dev/stdout
/bin/ln -snf /proc/self/fd/2 /dev/stderr
/bin/ln -snf /proc/kcore /dev/core
/bin/mkdir /dev/pts
/bin/mkdir /dev/shm
# start up our mini logger until syslog takes over
/sbin/minilogd
# anything more serious than KERN_WARNING goes to the console
# 'verbose' cmdline parameter enables more messages
if /bin/grep -q " verbose" /proc/cmdline; then
/bin/dmesg -n 8
else
/bin/dmesg -n 3
fi
# enable rtc access
/sbin/modprobe rtc-cmos >/dev/null 2>&1
RTC_MAJOR=$(/bin/grep -w rtc /proc/devices 2>/dev/null); RTC_MAJOR="${RTC_MAJOR%% *}"
if [ -n "$RTC_MAJOR" ]; then
/bin/mkdir /dev/misc/
/bin/mknod /dev/misc/rtc0 c $RTC_MAJOR 0
/bin/ln -s /dev/misc/rtc0 /dev/rtc
fi
HWCLOCK_PARAMS="--hctosys"
if [ "$HARDWARECLOCK" = "UTC" ]; then
HWCLOCK_PARAMS="$HWCLOCK_PARAMS --utc"
else
HWCLOCK_PARAMS="$HWCLOCK_PARAMS --localtime"
fi
if [ "$USEDIRECTISA" = "yes" -o "$USEDIRECTISA" = "YES" ]; then
HWCLOCK_PARAMS="$HWCLOCK_PARAMS --directisa"
fi
# Set clock early to fix some bugs with filesystem checks
# Clock is set again later to match rc.conf
if [ -f /etc/localtime ]; then
/sbin/hwclock $HWCLOCK_PARAMS --noadjfile
fi
echo > /proc/sys/kernel/hotplug
if [ -x /sbin/udevadm -a -d /sys/block ]; then
# We have udev and /sys appears to be mounted, use UDev
stat_busy "Starting UDev Daemon"
/sbin/udevd --daemon
/sbin/udevadm trigger
stat_done
else
# Static /dev, our last resort
status "Using static /dev filesystem" true
fi
# Load modules from the MODULES array defined in rc.conf
if ! [ "$load_modules" = "off" ]; then
if [ -f /proc/modules ]; then
stat_busy "Loading Modules"
for mod in "${MODULES[@]}"; do
if [ "$mod" = "${mod#!}" ]; then
/sbin/modprobe $mod
fi
done
stat_done
fi
if [ -d /proc/acpi ]; then
stat_busy "Loading standard ACPI modules"
ACPI_MODULES="ac battery button fan processor thermal"
k="$(echo $BLACKLIST ${MOD_BLACKLIST[@]} | /bin/sed 's|-|_|g')"
j="$(echo ${MODULES[@]} | /bin/sed 's|-|_|g')"
#add disabled MODULES (!) to blacklist - much requested feature
for m in ${j}; do
[ "$m" != "${m#!}" ] && k="${k} ${m#!}"
done
# add disablemodules= from commandline to blacklist
k="${k} $(echo ${disablemodules} | /bin/sed 's|-|_|g' | /bin/sed 's|,| |g')"
for n in ${ACPI_MODULES}; do
if ! echo ${k} | /bin/grep "\<$n\>" 2>&1 >/dev/null; then
/sbin/modprobe $n > /dev/null 2>&1
fi
done
stat_done
fi
fi
# run udev uevents
if /bin/pidof -o %PPID /sbin/udevd >/dev/null; then
stat_busy "Loading UDev uevents"
udevstart="$(/bin/date +%s%0N)"
# /sbin/udevadm trigger
/sbin/udevadm settle
stat_done
udevend="$(/bin/date +%s%0N)"
printhl " UDev uevent processing time: $((($udevend-$udevstart)/1000000))ms"
fi
# bring up the loopback interface
if [ -d /sys/class/net/lo ]; then
stat_busy "Bringing up loopback interface"
/sbin/ifconfig lo 127.0.0.1 up
if [ $? -ne 0 ]; then
stat_fail
else
stat_done
fi
fi
# If necessary, find md devices and manually assemble RAID arrays
#if [ -f /etc/mdadm.conf -a "$(/bin/grep ^ARRAY /etc/mdadm.conf 2>/dev/null)" ]; then
# # udev won't create these md nodes, so we do it ourselves
# for dev in $(/bin/grep ^ARRAY /etc/mdadm.conf | /bin/awk '{print $2}'); do
# path=$(echo $dev | /bin/sed 's|/[^/]*$||')
# node=$(echo $dev | /bin/sed "s|^$path/||")
# minor=$(echo $node | /bin/sed 's|^[^0-9]*||')
# [ ! -e $path/$node ] && /bin/mknod $path/$node b 9 $minor
# done
# status "Activating RAID arrays" /sbin/mdadm --assemble --scan
#fi
if [ "$USELVM" = "yes" -o "$USELVM" = "YES" ]; then
if [ -x /sbin/lvm -a -d /sys/block ]; then
# Kernel 2.6.x, LVM2 groups
/sbin/modprobe -q dm-mod 2>/dev/null
stat_busy "Activating LVM2 groups"
/sbin/lvm vgscan --ignorelockingfailure --mknodes >/dev/null
/sbin/lvm vgchange --ignorelockingfailure -a y >/dev/null
if [ $? -ne 0 ]; then
stat_fail
else
stat_done
fi
fi
fi
# Set up non-root encrypted partition mappings
#if [ -f /etc/crypttab -a -n "$(/bin/grep -v ^# /etc/crypttab | /bin/grep -v ^$)" ]; then
# /sbin/modprobe -q dm-mod 2>/dev/null
# stat_busy "Unlocking encrypted volumes:"
# csfailed=0
# CS=/sbin/cryptsetup.static
# do_crypt() {
# if [ $# -ge 3 ]; then
# cname="$1"
# csrc="$2"
# cpass="$3"
# shift 3
# copts="$*"
# stat_append "${cname}.."
# # For some fun reason, the parameter ordering varies for
# # LUKS and non-LUKS devices. Joy.
# if [ "${cpass}" = "SWAP" ]; then
# # This is DANGEROUS! The only possible safety check
# # is to not proceed in case we find a LUKS device
# # This may cause dataloss if it is not used carefully
# if $CS isLuks $csrc 2>/dev/null; then
# false
# else
# $CS -d /dev/urandom $copts create $cname $csrc >/dev/null
# if [ $? -eq 0 ]; then
# stat_append "creating swapspace.."
# /sbin/mkswap -L $cname /dev/mapper/$cname >/dev/null
# fi
# fi
# elif [ "${cpass}" = "ASK" ]; then
# printf "\nOpening '${cname}' volume:\n"
# if $CS isLuks $csrc 2>/dev/null; then
# $CS $copts luksOpen $csrc $cname < /dev/console
# else
# $CS $copts create $cname $csrc < /dev/console
# fi
# elif [ "${cpass:0:1}" != "/" ]; then
# if $CS isLuks $csrc 2>/dev/null; then
# echo "$cpass" | $CS $copts luksOpen $csrc $cname >/dev/null
# else
# echo "$cpass" | $CS $copts create $cname $csrc >/dev/null
# fi
# else
# if $CS isLuks $csrc 2>/dev/null; then
# $CS -d $cpass $copts luksOpen $csrc $cname >/dev/null
# else
# $CS -d $cpass $copts create $cname $csrc >/dev/null
# fi
# fi
# if [ $? -ne 0 ]; then
# csfailed=1
# stat_append "failed "
# else
# stat_append "ok "
# fi
# fi
# while read line; do
# eval do_crypt "$line"
# done </etc/crypttab
# if [ $csfailed -eq 0 ]; then
# stat_done
# else
# stat_fail
# fi
# # Maybe someone has LVM on an encrypted block device
# if [ "$USELVM" = "yes" -o "$USELVM" = "YES" ]; then
# if [ -x /sbin/lvm -a -d /sys/block ]; then
# /sbin/lvm vgscan --ignorelockingfailure --mknodes >/dev/null
# /sbin/lvm vgchange --ignorelockingfailure -a y >/dev/null
# fi
# fi
#fi
status "Mounting Root Read-only" /bin/mount -n -o remount,ro /
FORCEFSCK=
[ -f /forcefsck ] && FORCEFSCK="-- -f"
NETFS="nonfs,nonfs4,nosmbfs,nocifs,nocodafs,noncpfs,nosysfs,noshfs,nofuse,nofuseblk"
if [ -x /sbin/fsck ]; then
stat_busy "Checking Filesystems"
if /bin/grep -qw quiet /proc/cmdline; then
/sbin/fsck -A -T -C -a -t $NETFS $FORCEFSCK >/dev/null 2>&1
else
/sbin/fsck -A -T -C -a -t $NETFS $FORCEFSCK 2>/dev/null
fi
fsckret=$?
if [ ${fsckret} -gt 1 ]; then
stat_fail
if [ $((${fsckret}&2)) -eq 2 ]; then
echo
echo "********************** REBOOT REQUIRED *********************"
echo "* *"
echo "* The system will be rebooted automatically in 15 seconds. *"
echo "* *"
echo "************************************************************"
echo
/bin/sleep 15
else
echo
echo "***************** FILESYSTEM CHECK FAILED ****************"
echo "* *"
echo "* Please repair manually and reboot. Note that the root *"
echo "* file system is currently mounted read-only. To remount *"
echo "* it read-write type: mount -n -o remount,rw / *"
echo "* When you exit the maintenance shell the system will *"
echo "* reboot automatically. *"
echo "* *"
echo "************************************************************"
echo
/sbin/sulogin -p
fi
echo "Automatic reboot in progress..."
/bin/umount -a
/bin/mount -n -o remount,ro /
/sbin/reboot -f
exit 0
fi
stat_done
fi
stat_busy "Mounting Local Filesystems"
/bin/mount -n -o remount,rw /
/bin/rm -f /etc/mtab*
# make sure / gets written to /etc/mtab
/bin/mount -o remount,rw /
# Write /proc, /sys and /dev to /etc/mtab
if [ -e /proc/mounts ]; then
/bin/grep -e "/proc " -e "/sys " -e "/dev " /proc/mounts >> /etc/mtab
fi
# now mount all the local filesystems
/bin/mount -a -t $NETFS
stat_done
#status "Activating Swap" /sbin/swapon -a
stat_busy "Configuring System Clock"
if [ ! -f /var/lib/hwclock/adjtime ]; then
echo "0.0 0 0.0" > /var/lib/hwclock/adjtime
fi
if [ "$TIMEZONE" != "" -a -e "/usr/share/zoneinfo/$TIMEZONE" ]; then
/bin/rm -f /etc/localtime
/bin/cp "/usr/share/zoneinfo/$TIMEZONE" /etc/localtime
fi
/sbin/hwclock $HWCLOCK_PARAMS
stat_done
if [ -f /var/run/random-seed ]; then
stat_busy "Initializing Random Seed"
/bin/cat /var/run/random-seed >/dev/urandom
stat_done
fi
stat_busy "Removing Leftover Files"
/bin/rm -f /etc/nologin &>/dev/null
/bin/rm -f /etc/shutdownpid &>/dev/null
/bin/rm -f /var/lock/* &>/dev/null
/bin/rm -rf /tmp/* /tmp/.* &>/dev/null
/bin/rm -f /forcefsck &>/dev/null
(cd /var/run && /usr/bin/find . ! -type d -exec /bin/rm -f -- {} \; )
: > /var/run/utmp
/bin/chmod 0664 /var/run/utmp
# Keep {x,k,g}dm happy with xorg
/bin/mkdir /tmp/.ICE-unix && /bin/chmod 1777 /tmp/.ICE-unix
/bin/mkdir /tmp/.X11-unix && /bin/chmod 1777 /tmp/.X11-unix
stat_done
#status "Updating Shared Library Links" /sbin/ldconfig
if [ "$HOSTNAME" != "" ]; then
status "Setting Hostname: $HOSTNAME" /bin/hostname $HOSTNAME
fi
# Set the NIS domain name, if necessary
[ -f /etc/conf.d/nisdomainname ] && . /etc/conf.d/nisdomainname
if [ "$NISDOMAINNAME" != "" ]; then
status "Setting NIS Domain Name: $NISDOMAINNAME" /bin/nisdomainname $NISDOMAINNAME
fi
status "Updating Module Dependencies" /sbin/depmod -A
# Flush old locale settings
: >/etc/profile.d/locale.sh
/bin/chmod 755 /etc/profile.d/locale.sh
# Set user defined locale
[ -z "$LOCALE" ] && LOCALE="en_US"
stat_busy "Setting Locale: $LOCALE"
echo "export LANG=$LOCALE" >>/etc/profile.d/locale.sh
stat_done
if echo "$LOCALE" | /bin/grep -qi utf ; then
stat_busy "Setting Consoles to UTF-8 mode"
# UTF-8 consoles are default since 2.6.24 kernel
# this code is needed not only for older kernels,
# but also when user has set vt.default_utf8=0 but LOCALE is *.UTF-8.
for i in $(/usr/bin/seq 0 63); do
/usr/bin/kbd_mode -u < /dev/vc/${i}
printf "\e%%G" > /dev/vc/${i}
done
# the $CONSOLE check helps us avoid this when running scripts from cron
echo 'if [ "$CONSOLE" = "" -a "$TERM" = "linux" -a -t 1 ]; then printf "\e%%G"; fi' >>/etc/profile.d/locale.sh
stat_done
[ -n "$KEYMAP" ] && status "Loading Keyboard Map: $KEYMAP" /bin/loadkeys -q -u $KEYMAP
else
stat_busy "Setting Consoles to legacy mode"
# make non-UTF-8 consoles work on 2.6.24 and newer kernels
for i in $(/usr/bin/seq 0 63); do
/usr/bin/kbd_mode -a < /dev/vc/${i}
printf "\e%%@" > /dev/vc/${i}
done
# the $CONSOLE check helps us avoid this when running scripts from cron
echo 'if [ "$CONSOLE" = "" -a "$TERM" = "linux" -a -t 1 ]; then printf "\e%%@"; fi' >>/etc/profile.d/locale.sh
stat_done
[ -n "$KEYMAP" ] && status "Loading Keyboard Map: $KEYMAP" /bin/loadkeys -q $KEYMAP
fi
if [ -n "$CONSOLEFONT" ]; then
stat_busy "Loading Console Font: $CONSOLEFONT"
#CONSOLEMAP in UTF-8 shouldn't be used
if [ -n "$CONSOLEMAP" ] && echo "$LOCALE" | /bin/grep -qi utf ; then
CONSOLEMAP=""
fi
for i in $(/usr/bin/seq 0 63); do
if [ -n "$CONSOLEMAP" ]; then
/usr/bin/setfont -m $CONSOLEMAP $CONSOLEFONT -C /dev/vc/${i} >/dev/null 2>&1
else
/usr/bin/setfont $CONSOLEFONT -C /dev/vc/${i} >/dev/null 2>&1
fi
done
if [ $? -ne 0 ]; then
stat_fail
else
for i in $(/usr/bin/seq 0 63); do
printf "\e(K" > /dev/vc/${i}
done
# the $CONSOLE check helps us avoid this when running scripts from cron
echo 'if [ "$CONSOLE" = "" -a "$TERM" = "linux" -a -t 1 ]; then printf "\e(K"; fi' >>/etc/profile.d/locale.sh
stat_done
fi
fi
# Adding persistent network/cdrom generated rules
#if [ -f "/dev/.udev/tmp-rules--70-persistent-cd.rules" ]; then
# stat_busy "Adding persistent cdrom udev rules"
# /bin/cat /dev/.udev/tmp-rules--70-persistent-cd.rules >> /etc/udev/rules.d/70-persistent-cd.rules
# stat_done
#fi
if [ -f "/dev/.udev/tmp-rules--70-persistent-net.rules" ]; then
stat_busy "Adding persistent network udev rules"
/bin/cat /dev/.udev/tmp-rules--70-persistent-net.rules >> /etc/udev/rules.d/70-persistent-net.rules
stat_done
fi
# Save our dmesg output from this boot
if [ -f /var/log/dmesg.log ]; then
/bin/rm /var/log/dmesg.log
fi
/bin/dmesg > /var/log/dmesg.log
# End of file
# vim: set ts=2 noet:

DreamAxe wrote:
quarkup wrote:Once the modules are all loaded, by enabling this option I "consume" only ~70ms
I see that you mention milliseconds again, how exactly do you count these milliseconds? Since my last message, I've tried other I/O schedulers and three out of four get the same result. I believe that there IS a difference among schedulers but since bootchart displays the results in seconds, I can't compare them. If you could just tell me how you count in ms I could compare them and see which one is faster at booting the eee. In case you're wondering, noop is the slowest, requiring 16sec to boot the eee while cfq, anticipatory and deadline require 14sec according to bootchart.
I'm talking about "loading" modules, not the full-boot time..
After turning on the PC, there will be shown on the virtual terminal the time taken by Udev to load all modules.
as you can see
Last edited by quarkup (2009-02-20 13:49:55)

Verify physical hard disk drive health MCS 7825-H3 that installed CUCM inside it

Hi Everyone,
I have Cisco MCS 7825-3 that installed CUCM ver 6.1.1 inside it. A few days ago the system was crashed and have been recovered. And the symtomp why the system crashed is because corrupted hard disk drive. Now the system is running well.
I want to verify the health status of hard disk drive MCS 7825. The logical drive is RAID 1 with 2 chunks (channel 0,1 and channel 0,2). So that i did the test to shut down the cucm and unmount on of the physical hard disk drive. After that i power on the server and running the system with just 1 hard disk drive (example just channel 0,1 and after verify channel i do the same task with channel 0,2). With just 1 hard disk drive if i show hardware in cucm cli , it showed that status of logical drive is degraded. But the system can run well (IP Phone registered and can do pbx features). And after do verify test with 1 hard disk drive, i mount the physical hard disk drive again so that the system running with all of hard disk drive mounted (2 chunks).
At first it showed in cucm cli that status of logical drive is degraded, but with current operation rebuild (indicated RAID 1 is rebuild again by the system). After up to 1 hour the process finished and the status of logical drive is optimal again.
The question i wanna ask, is there any method to know if the health of physical hard disk drive of MCS good or not beside the task i have done ?
Maybe we can show in the BIOS or cucm cli because i didnt find diagnose of physical drive in cucm cli but it can diagnose status of RAID, hard disk space and list file in hard disk drive.
Thanks for your help.
Best Regards,
Luthfi
- See more at: https://supportforums.cisco.com/message/3871634#3871634

Hi Luthfi,
Do you find a way to check the hard drives and RAID of this CUCM server. I have also 7825-H3
Or it is as I think that I need to create remote access configuration ?
Thanks
Haitham

Verify physical hard disk drive health MCS 7825-H3

Hi Everyone,
I have Cisco MCS 7825-3 that installed CUCM ver 6.1.1 inside it. A few days ago the system was crashed and have been recovered. And the symtomp why the system crashed is because corrupted hard disk drive. Now the system is running well.
I want to verify the health status of hard disk drive MCS 7825. The logical drive is RAID 1 with 2 chunks (channel 0,1 and channel 0,2). So that i did the test to shut down the cucm and unmount on of the physical hard disk drive. After that i power on the server and running the system with just 1 hard disk drive (example just channel 0,1 and after verify channel i do the same task with channel 0,2). With just 1 hard disk drive if i show hardware in cucm cli , it showed that status of logical drive is degraded. But the system can run well (IP Phone registered and can do pbx features). And after do verify test with 1 hard disk drive, i mount the physical hard disk drive again so that the system running with all of hard disk drive mounted (2 chunks).
At first it showed in cucm cli that status of logical drive is degraded, but with current operation rebuild (indicated RAID 1 is rebuild again by the system). After up to 1 hour the process finished and the status of logical drive is optimal again.
The question i wanna ask, is there any method to know if the health of physical hard disk drive of MCS good or not beside the task i have done ?
Maybe we can show in the BIOS or cucm cli because i didnt find diagnose of physical drive in cucm cli but it can diagnose status of RAID, hard disk space and list file in hard disk drive.
Thanks for your help.
Best Regards,
Luthfi

Hi Luthfi,
Do you find a way to check the hard drives and RAID of this CUCM server. I have also 7825-H3
Or it is as I think that I need to create remote access configuration ?
Thanks
Haitham

Confused... Degraded raidset, no drive failure?

Hi I have an XServe (10.5.2) with a mirrored raid set (2 drives, 1TB). Recently someone accidently hit one of the bays while it was running and now the raidset has a degraded status.
RAID SETS
===============================================================================
Name:                 Untitled RAID Set 1
Unique ID:            A42A9310-FAAC-45CA-9BA9-11E7EE3C5CBE
Type:                 Mirror
Status:               Degraded
Size:                 999860895744 B
Device Node:          disk3
Apple RAID Version:   2
#   Device Node       UUID                                   Status
0   -none-            939868AF-E917-488C-B385-308E72ADDD06   Missing/Damaged
1   disk2s2           E18D836D-4EFF-4644-A223-79A277C772CC   Online
2   disk1s2           E4DB4277-965A-4B6E-9A95-EDC59D499640   Online
===============================================================================
mcserver:~ admin$
The slices look fine, no errors, smart ok and verified. It's 'just' the 'Mirrored Raid Set 1' that is red.
After looking around for help all I see it people hitting the rebuild button, but I don't seem to have one....
What is the correct way of rebuilding the set?
ANy help would be very much appreciated!

The raid set is degraded because, according to the report, the raid set consists of three disks, but one of them is missing.
While it's unsual to have a mirror raid using three disks, it is possible. The question is where that third drive went.
Were there three drives in the set and one is missing? (in which case the degraded status is valid)
Was the missing slice the disk that was bumped, and it got assigned a new UUID when it was re-inserted (maybe if someone incorrectly rebuilt the array using the new drive).
Either way, you should be able to remove the 'bogus' drive from the array using diskutil (or raidutil, depending on your OS version).

How to view disk space information

How to view disk space information in CLI

Perhaps you can share the output for the command ipcheck.
You should get an output like:
esalab.cisco.com> ipcheck
Ipcheck Rev           1
Date                  Mon Jun 18 10:43:20 2012
Model                 C150
Platform               (8066)
MGA Version           Version: 7.5.2-014
Build Date            2012-03-06
Install Date          2012-05-03 08:36:10
Burn-in Date          Unknown
Serial No.            001D09F09F6B-7xxxxx1
BIOS Version          A02I
RAID Version          02
RAID Status           READY
RAID Type             1
RAID Chunk            Unknown
BMC Version           1.70
Disk 0
Disk 1
Disk 2
Disk 3
Disk 4                233GB Seagate ST3250620NS 3BKH at ata2-master SATA300
Disk 5
Disk 6                233GB Seagate ST3250620NS 3BKH at ata3-master SATA300
Disk 7
Disk Total            466GB
Root                  400MB 43%
Nextroot              400MB 42%
Var                   400MB 0%
Log                   54GB 16%
DB                    2GB 0%
Swap                  6GB
Mail Queue            10GB
RAM 1 A               512M ECC 667MHz
RAM 1 B               512M ECC 667MHz
RAM 2 A               512M ECC 667MHz
RAM 2 B               512M ECC 667MHz
RAM Total             2G
CPU 1                 D 2G 800FSB 0.5M Cache
PCI 1                 PCI-X 64-bit Empty
PCI 2                 PCI-e 8x Empty
NIC Data 1            00:xx:xx:xx:xx:6b, NetXtreme Gigabit Ethernet PCI Express (BCM5721)
NIC Data 2            00:xx:xx:xx:xx:6c, NetXtreme Gigabit Ethernet PCI Express (BCM5721)
PS1                   Unknown
PS2                   Unknown
Key                   1da, IronPort Anti-Spam
Key                   1da, Receiving
Key                   expire, Bounce Verification
Key                   expire, Central Mgmt
Key                   expire, Intelligent Multi-Scan
Key                   expire, IronPort Email Encryption
Key                   expire, IronPort Image Analysis
Key                   expire, McAfee
Key                   expire, Outbreak Filters
Key                   expire, RSA Email Data Loss Prevention
Key                   expire, Sophos
esalab.cisco.com>

Status of RAID

Similar Messages

Maybe you are looking for