B-Series Disk details RAID rebuild issues after disk removal

Hi,
after removing and reinserting one disk from a RAID-1 on our B-Series blades for testing, the disk details for the reinserted disk will not be fully shown.
Only the disk itself gets detected and "Presence" shows "equipped" (see attached screenshot).
It also doen not look like the RAID would be rebuilt.
So does anyone know how to:
* Get all disk details again.
* (Automatically) reinitialize the RAID rebuild.
* Monitor the RAID status.
* Be notified of a RAID failure.
Ralph

Hi,
not very happy with the fact that UCSM doesn't display a disk or RAID status.
Any chance that we might see that in an upcoming release?
We are using ESX 4.0 U2, RHEL 6 and W2K8 R2.
Hope that MegaRAID tools would work and can be queried by SNMP (or so).
I found out how to get the disk data again and get rid of the following warning that obviously comes with not getting the disk details:
Description:
* Server sys/chassis-1/blade-6 does not fullfill Service profile vmw66 due to incompatible-number-of-local-disks
* ID: 828447
* Cause: server-failed
* Code: F0337
Solution -> re-aknowledge the server...
Any chance that this might be a bug (in 1.4.1i)?
edit: Seems that has been around for a while:
-> http://terenceluk.blogspot.com/2010/12/fixing-cisco-ucs-b-series-raid-1-mirror.html
Ralph

Similar Messages

AD replication issue after forced remove of secondary DC

So is this DC a GC? That would explain both problems.

My domain is down on the last remaining DC which holds the FMSO roles and failure suggests its because the DNS is awaiting AD to sync and the sync cant take place as the secondary server has been forceably removed using ntfsutil. adsiedit cant access the data and i've no idea how to tell active directory not to replicate as its the only DC left! Any ideas?
This topic first appeared in the Spiceworks Community

Disk Utility RAID Issue

I'm trying to determine if the problems that I'm encountering are a software issue or a hardware issue.
I'm setting up a Mac Pro with Leopard and have four Maxtor 6G160E0 160GB hard drives that I'm trying to set up as two Mirrored drive sets. Everything seemed to go fine, created the two mirror sets, installed Leopard, configured and tested two user accounts and Office 2004, then updated everything to the latest version. When done I shut it down planning on moving it to it's final home tonight.
But, when I turned it on both mirror sets were degraded - all four drives were still recognized as RAID slices but came up as failed in the RAID tab. I saw no errors reported in the log so I assumed that those two drives were faulty. I shut down, moved the good drives to bays 1 & 2 and rebooted.
First reboot gave me a prohibition symbol instead of the usual Apple. Powered down and on and it booted fine but the second drive came up as a failed RAID slice. Rebooted again and both were fine.
I reinstalled the two "failed" drives and reformatted them - both reformatted fine and mounted without problems. I unmounted the new partition just in case, but, when I tried to rebuild the RAIDs I get the following in the error log:
11/1/07 7:26:00 PM Disk Utility[141] Preparing to erase : “Untitled”
11/1/07 7:26:00 PM Disk Utility[141] Partition Scheme: GUID Partition Table
11/1/07 7:26:00 PM Disk Utility[141] 1 volume will be created
11/1/07 7:26:00 PM Disk Utility[141] Name : “Untitled”
11/1/07 7:26:00 PM Disk Utility[141] Size : 149.1 GB
11/1/07 7:26:00 PM Disk Utility[141] Filesystem : Mac OS Extended (Journaled)
11/1/07 7:26:00 PM Disk Utility[141] Creating partition map.
11/1/07 7:26:03 PM Disk Utility[141] Formatting disk1s2 as Mac OS Extended (Journaled) with name Untitled.
11/1/07 7:26:06 PM Disk Utility[141] Erase complete.
11/1/07 7:26:12 PM Disk Utility[141] Unmount of “Untitled” succeeded
11/1/07 7:26:31 PM Disk Utility[141] Rebuilding RAID
11/1/07 7:26:31 PM Disk Utility[141] Filesystem: Mac OS Extended (Journaled)
11/1/07 7:26:31 PM Disk Utility[141] RAID type: Mirrored RAID Set
11/1/07 7:26:31 PM Disk Utility[141] RAID set name: “Yorktown”
11/1/07 7:26:31 PM Disk Utility[141] RAID set status before rebuild: “”
11/1/07 7:26:31 PM Disk Utility[141] RAID chunk size: 32K (default)
11/1/07 7:26:31 PM Disk Utility[141] Mirror Auto Rebuild: Disabled (default)
11/1/07 7:26:31 PM Disk Utility[141] 2 members
11/1/07 7:26:31 PM Disk Utility[141] RAID Slice (disk0s2) - Online
11/1/07 7:26:31 PM Disk Utility[141] Maxtor 6G160E0 Media (disk1) - New
11/1/07 7:26:32 PM Disk Utility[141] Error rebuilding RAID: Unrecognized Filesystem.
11/1/07 7:26:33 PM Disk Utility[141] RAID failed: Unrecognized Filesystem.
I'm at a loss at the moment. I am leaning towards bad drives, but FOUR bad drives all at once is suspicious.
I've searched for similar issues and found none so I thought I'd check here and see if anyone had any ideas.

G'day Zeekm,
Thank you for that. I did this and it seems to work. The Disk Utility GUI does not seem to work.
Hope this helps some one,
#Checked the RAID status
root# diskutil checkRAID
RAID SETS
===============================================================================
Name: Server_HD
Unique ID: 7E31E20E-F53D-4D76-AD37-139C4E1440AB
Type: Mirror
Status: Degraded
Size: 1000070610944 B
Device Node: disk2
Apple RAID Version: 2
# Device Node UUID Status
0 disk1s3 BAC72F86-B05F-4B0F-97D3-58A6207E7DFA Failed
1 disk0s3 2BFB55BB-EFF9-438C-A1F9-A8ED7A93D385 Online
===============================================================================
#Told it to resync
root# diskutil repairMirror disk2 disk1s3
Note: Syncing data between mirror partitions can take a very long time.
Note: The mirror should now be repairing itself. You can check its status using 'diskutil listRAID'.
temp:~ root# diskutil listRAID
RAID SETS
===============================================================================
Name: Server_HD
Unique ID: 7E31E20E-F53D-4D76-AD37-139C4E1440AB
Type: Mirror
Status: Degraded
Size: 1000070610944 B
Device Node: disk2
Apple RAID Version: 2
# Device Node UUID Status
0 disk1s3 9D955C85-7EC0-4E92-848A-62D9F7C12EED 0% (Rebuilding)
1 disk0s3 2BFB55BB-EFF9-438C-A1F9-A8ED7A93D385 Online
===============================================================================
Hope this helps,
Cheers,
Arthur

Raid Performance and Rebuild Issues

Rebuilding a Raid array
What happens when you have a Raid array and one (or more) disk(s) fail?
First let's consider the work-flow impact of using a Raid array or not. You may want to refresh your memory about Raids, by reading Adobe Forums: To RAID or not to RAID, that is the... again.
Sustained transfer rates are a major factor in determining how 'snappy' your editing experience will be when editing multiple tracks. For single track editing most modern disks are fast enough, but when editing complex codecs like AVCHD, DSLR, RED or EPIC, when using uncompressed or AVC-Intra 100 Mbps codecs, or using multi-cam or multiple tracks the sustained transfer speed can quickly become a bottleneck and limit the 'snappy' feeling during editing.
For that reason many use raid arrays to remove that bottleneck from their systems, but this also raises the question:
What happens when one of more of my disks fail?
Actually, it is simple. Single disks or single level striped arrays will lose all data. And that means that you have to replace the failed disk and then restore the lost data from a backup before you can continue your editing. This situation can become extremely bothersome if you consider the following scenario:
At 09:00 you start editing and you finish editing by 17:00 and have a planned backup scheduled at 21:00, like you do every day. At 18:30 one of your disks fails, before your backup has been made. All your work from that day is lost, including your auto-save files, so a complete day of editing is irretrievably lost. You only have the backup from the previous day to restore your data, but that can not be done before you have installed a new disk.
This kind of scenario is not unheard of and even worse, this usually happens at the most inconvenient time, like on Saturday afternoon before a long weekend and you can only buy a new disk on Tuesday...(sigh).
That is the reason many opt for a mirrored or parity array, despite the much higher cost (dedicated raid controller, extra disks and lower performance than a striped array). They buy safety, peace-of-mind and a more efficient work-flow.
Consider the same scenario as above and again one disk fails. No worry, be happy!! No data lost at all and you could continue editing, making the last changes of the day. Your planned backup will proceed as scheduled and the next morning you can continue editing, after having the failed disk replaced. All your auto-save files are intact as well.
The chances of two disks failing simultaneously are extremely slim, but if cost is no object and safety is everything, some consider using a raid6 array to cover that eventuality. See the article quoted at the top.
Rebuilding data after a disk failure
In the case of a single disk or striped arrays, you have to use your backup to rebuild your data. If the backup is not current, you lose everything you did after your last backup.
In the case of a mirrored array, the raid controller will write all data on the mirror to the newly installed disk. Consider it a disk copy from the mirror to the new disk. This is a fast way to get back to full speed. No need to get out your (possibly older) backup and restore the data. Since the controller does this in the background, you can continue working on your time-line.
In the case of parity raids (3/5/6) one has to make a distinction between distributed parity raids (5/6) and dedicated parity raid (3).
Dedicated parity, raid3
If a disk fails, the data can be rebuild by reading all remaining disks (all but the failed one) and writing the rebuilt data only to the newly replaced disk. So writing to a single disk is enough to rebuild the array. There are actually two possibilities that can impact the rebuild of a degraded array. If the dedicated parity drive failed, the rebuilding process is a matter of recalculating the parity info (relatively easy) by reading all remaining data and writing the parity to the new dedicated disk. If a data disk failed, then the data need to be rebuild, based on the remaining data and the parity and this is the most time-consuming part of rebuilding a degraded array.
Distributed parity, raid5 or raid6
If a disk fails, the data can be rebuild by reading all remaining disks (all but the failed one), rebuilding the data and recalculating the parity information and writing the data and parity information to the failed disk. This is always time-consuming.
The impact of 'hot-spares' and other considerations
When an array is protected by a hot spare, if a disk drive in that array fails the hot spare is automatically incorporated into the array and takes over for the failed drive. When an array is not protected by a hot spare, if a disk drive in that array fails, remove and replace the failed disk drive. The controller detects the new disk drive and begins to rebuild the array.
If you have hot-swappable drive bays, you do not need to shut down the PC, you can simply slide out the failed drive and replace it with a new disk. Remember, when a drive has failed and the raid is running in 'degraded' mode, there is no further protection against data loss, so it is imperative that you replace the failed disk at the earliest moment and rebuild the array to a 'healthy' state.
Rebuilding a 'degraded' array can be done automatically or manually, depending on the controller in use and often you can set the priority of the rebuilding process higher or lower, depending on the need to continue regular work versus the speed required to repair the array to its 'healthy' status.
What are the performance gains to be expected from a raid and how long will a rebuild take?
The most important column in the table below is the sustained transfer rate. It is indicative and no guarantee that your raid will achieve exactly the same results. That depends on the controller, the on-board cache and the disks in use. The more tracks you use in your editing, the higher the resolution you use, the more complex your codec, the more you will need a high sustained transfer rate and that means more disks in the array.
Sidebar: While testing a new time-line for the PPBM6 benchmark, using a large variety of source material, including RED and EPIC 4K, 4:2:2 MXF, XDCAM HD and the like, the required sustained transfer rate for simple playback of a pre-rendered time-line was already over 300 MB/s, even with 1/4 resolution playback, because of the 4 4 4 4 full quality deBayering of the 4K material.
Final thoughts
With the increasing popularity of file based formats, the importance of backups of your media can not be stressed enough. In the past one always had the original tape if disaster stroke, but no longer. You need regular backups of your media and projects. With single disks and (R)aid0 you take risks of complete data loss, because of the lack of redundancy. Backups cost extra disks and extra time to create and restore in case of disk failure.
The need for backups in case of mirrored raids is far less, since there is complete redundancy. Sure, mirrored raids require double the number of disks but you save on the number of backup disks and you save time to create and restore backups.
In the case of parity raids, the need for backups is more than with mirrored arrays, but less than with single disks or striped arrays and in the case of 'hot-spares' the need for backups is further reduced. Initially, a parity array may look like a costly endeavor. The raid controller and the number of disks make it expensive, but if you consider what you get, more speed, more storage space, easier administration, less backups required, less time for those backups, continued working in case of a drive failure, even though somewhat sluggish, the cost is often worth more with the peace-of-mind it brings, than continuing with single disks or striped arrays.

Raid3 is better suited for video editing work, because it is more efficient when using large files, as clips usually are. Raid5 is better suited in high I/O environments, where lots of small files need to be accessed all the time, like news sites, webshops and the like. Raid3 will usually have a better rebuild time than raid5.
But, and there is always a but, raid3 requires an Areca controller. LSI and other controller brands do not support raid3. And Areca is not exactly cheap...
Keep in mind that a single disk shows declining performance when the fill rate increases. See the example below:
A Raid3 or Raid30 will not show that behavior. The performance remains nearly constant even if fill rates go up:
Note that both charts were created with Samsung Spinpoint F1 disks, an older and slower generation of disks and with an older generation Areca ARC-1680iX-12.

RAID Issues - Standby Disk

I am running a PowerMac G4 with the two disks configured as a single mirrored Raid disk.
Today, the system will not boot; unable to find a disk to boot from.
Restarted system from the 10.4 install CD and using the Disk Utility I have discoverd the following:
1. Running first aid, no problems found.
2. Looking at the Raid Option, the following is displayed:
a. Raid Disk status - Degraded
b. Disk 1 Status - Standby
c. Disk 2 Status - no problem.
I started the process of rebuilding the Disk 1 and I am waiting for it to completed (over 100GBs of info storage on system).
I have several questions>
1. Why doesn't the system continue to run from a single disk - Disk 2? Does one have to do something?
2. I cannot find any information about running a system with Raid disks (software version). What do these status name mean - standy, degraded, etc. and what do you solve these issues/problems?
Steve

good question - now if someone who only provide an answer
I just set up a mirrored FW Raid and made the array bootable. It booted but I can not tell which drive is actaully booting and which is the mirror
1. I can't tell if the second (mirror) drive is being written to or NOT (No volume info is available/provided in disk utility). So how does one actually tell if the mirrored RAID is actually writing.
2. If (when) Drive A (a startup drive) fails, how does one boot from the other?
IMO, Apple needs to do a MUCH better job of explaining their RAID utility and it's use.

Mail, Keychain & Disk Utility Issues After Install

My clean install of Leopard seem to go fine. After restart it wanted to grab an Apple Remote Desktop update, I believe, via software update. Re-installed clean copies of further mac software and known Leopard compatible 3rd party apps.
My problems started to appear when I used migration assistant to transfer 2 accounts from my 10.4.10 backup. Both accounts went over, but on one the mail upgrade process consistently failed and on the other the keychain seemed to be of no use.
All's fine now, I manually imported the errant mail acount and just started with a fresh keychain on the other offending account. I know the backup was sound as I subsequently used it to restore a Tiger install as a fallback on another disk.
My last issue appears every-time I run Disk Utility to verify and repair permissions. I get the following text displayed part way through a verify and or repair.
Warning: SUID file "System/Library/CoreServices/RemoteManagement/ARDAgent.app/Contents/MacOS/ARDAg ent" has been modified and will not be repaired.
The verify/repair completes and I can quit Disk Utility. I'm presuming this is as a result of the early software update Leopard wanted to perform and the current shipping version of Disk Utility has no idea of the desired permission state of this file?
Was just wondering if anyone else had experienced any of the above or had any explanation?
Hope you're all having more fun than headaches with Leopard.

Nerowolfe,
I have installed Leopard and have had nothing but problems as well. Perhaps you can help me. I am ready to roll back to Tiger. These are just a few:
1. I cannot mount my external firewire drives. I have separately tested each and they work fine, I booted with the Tiger disk and they mounted fine, I reset the firewire port and when I connected them they mounted on my desktop, but not in the finder window and when I tried to open one, it just hung. I have been unsuccessful after many attempts to mount one of them with Leopard.
2. I appear to get random hangs. I have a 160GB hard drive and 2GB memory. I have 42 GB space left on the hard drive....yet I continue to have random hangs, especially when I try to open disk utility
3. Spotlight just does not work, period
4. I keep finding locked folders. Right now my CS3 is locked and even after going into get info and unlocking it, it just locks back and I am unable to open the application. I am a photographer and have been unable to do any work for the past 2 weeks while I am messing around with my computer. Now I have Christmas photos to sort and can't access the photos on the external drives or even open CS3
I have searched the forums, tried many of the recommendations, but nothing is working for me....perhaps since you have been successful you could give me a hand with these issues.
I wait for help.......
Other than that, how do I uninstall Leopard and reinstall Tiger????

After creating RAID 5 for hard disks, CIMC shows Modrate fault

Dear all,
There are two UCS servers which the model is C240 M3
When I created RAID 5 for hard disks, CIMC shows Modrate fault.
The warring message is
storage virtual drive 0 degraded: please check the storage controller, or reseat the storage drive ucs
anybody has idea for this case? Thank you!

Is it an solution? Thank you!
The warning message appears if you do not have a Battery BAckup Unit Instllated on the server. I just worked with Cisco TAC and following is the solution.:
1. Launch KVM Console of the server
2. Power Cycle the Server
3. When LSI RAID configuration window displays, press CTRL+H and start the RAID Configuration Utility.
4. Click on Virtual Drive. Example Virtual Drive 0.
5. Change Default Write Mode to "Write Through" and click "Change"
6. Press "Yes" to take the effect.
7. Exit from RAID Configuration Utility nad restart the server.
From:
https://supportforums.cisco.com/discussion/11842501/ucs-c220-m3-megaraid-9266-8i-cache-degraded

Working on raid while raid rebuild process ( Raid 5 configration)

I am using xserve raid (4 no.) with Xsan( for FCP-Editing ) and raid for data is configured for *raid 5* and for meta *raid 1*.
In one of my Raid (raid 5 configured) Disk 9 was showing offline and which I have swapped with new disk, after that raid rebuild process got started .
In this situation (while rebuilding ) can I do work ( access volume for Ingest and editing) or is there is any performance issue will come ?.
or we should start working after rebuild process got completed. Plz suggest ?

It's fine to work with the volume while the array is getting rebuilt. Just be aware that performance may be degraded - but it was already degraded when the first disk failed, so it shouldn't be too bad.

P45 Platinum Raid 1 issues Intel vs Jmicron ?

I have been experiencing intermittent problems with Raid 1 installation using the Intel Controller.
Several problems were definitely due to HD errors and I have had two failed drives swapped out over the last six months.
However after the last drive replacement things seemed to be stable for several weeks before problems started to emerge again.
The interesting thing is that the problem had switched to the oldest drive in the system which until now had been completely stable and I'm now wondering if it’s an Intel Raid related issue rather than the drives.
What’s Happening:
I boot and both drives are recognised by the Bios.
Both drives show up in the Raid Bios screen
Once booted into windows one of several things happen.
1) Once drive is not visible and is reported in the Intel Raid Console as missing. Reboot and its back in a rebuild state
2) Windows boot proceeds normally and then one of the drives (always the same one) will go off line and be reported as missing. reboot and again the drive will be visible in the Bios and Raid Bios screen and be marked for rebuild
Once the drive has rebuilt it may be stable for hours or days or disappear again during the rebuild.
Drives are Maxtor STM31000340AS and a Seagate ST41000340AS, so essentially the same drive and both running the latest firmware updates.
Interestingly the port numbers reported in the Intel Raid Console for the drives is different from that reported in the Bios discovery and the Raid BIOS.
It is now always the Maxtor drive that goes offline where as previously it was always the Seagate. I’m now starting to wonder if its actualy a raid Bios/Console issue rather than the drives.
Has anyone else experienced similar problem in a Raid 1 configuration ?
I had been thinking about moving both drives over onto the JMicron Raid Controller but was uncertain if this can be done as a straight swap or if it’s likely screw up any data on the disks.
Again any experiences of advice would be welcome.

Thanks for the replies guys.
I have tried changing the SATA cables for the new types with the locking clips and ensured that there are no major bends in them, with no improvement.
I have also tested the integrity of the drives with Seagate’s test software using both the short and long tests, which show no problems when connected as IDE or ACHI (won’t allow me to test in RAID mode).
No problems reported but the drive still goes offline when reconnected in RAID mode. Which is partly what has made me wonder if there is a problem with the RAID BIOS, Drivers of Console Software.
Coupled with the fact that the drive which was being affected by the disconnections suddenly changed to one which had been stable for months and the drive that had previously caused problems has now become stable.
I’m also running the latest drivers and Intel Matrix Storage Console 8.8.0.1009, although I’m a little concerned by the number of outstanding bugs that are listed in the release notes, just indicates a poor product with almost 40 unresolved issues.
Currently I’m using standard RAID settings in the BIOS for the Intel ports with the Jmicron controller set to IDE but nothing connected.
The drives are essentially identical apart from the model number strings and the labels on the drives, both are at the equivalent level of drive firmware. Originally they were two Maxtor drives one of which failed with a hardware problem and was replaced by the Seagate equivalent, which is the same hardware and software with just the manufacturers branding being different.
Over the weekend I isolated the drive that was having problems, reformatted completely, performed a BIOS reset, re-added and rebuilt the drive into the RAID array.
So far its only been two days but things have been stable so far, although I have had periods of weeks without a problem before it reappears.
Sliksta, when you suggested updating the BIOS were you suggesting one of the Beta BIOS’s ? As I’m currently on the latest official release .

Sync strangeness after disk replacement and OS reinstall

This was posted in someone elses thread but I didn't want to hijack his thread so I started my own.
I'm having a similar issue after a hard drive upgrade and OS reinstall. I added a 500G disk to my older g5 imac, which I sync my iphone to and ever since the reinstall I've had weird sync problems. After a Time Machine restore of my Addressbook to it's proper location and my iPhoto and iTunes library to the shared folder with a symlink in my $home/Music, it's yielded weird problems and only half works.
Symptoms include:
Sync of contacts that never finishes (I chose "merge" when it complained that it was sync'd to another iTunes instance). I've left it for several hours and it never finishes.
I can no longer subscribe on my iPhone to a subscribed calendar
iSync never finishes starting up, it yields "Refreshing contact groups information" forever and never really opens enough to allow for use.
Things I've tried:
Reboot imac
Open iSync (see above)
Restore iPhone
Let it sit for hours to see if it will finish
I suspect that it has to do with it thinking that this is a new iTunes library but I'd really like to get it back to the way it was.
Details:
iTunes 7.6.1
MacOS 10.5.1 (PPC)
iPhone firmware 1.1.3
Any help appreciated, I did a little searching (probably not enough), but didn't come up with much. Any help appreciated.
Thanks,
nb

Back up Contacts using File > Back up Address Book
Delete all contacts in Address Book
Move ~/Library/Application Support/AddressBook, ~/Library/Caches, and ~/Library/Preferences/com.apple.AddressBook.plist to the Trash, but do not empty (just in case)
Log out of your user, then log back in
Launch iSync, Choose iSync > Preferences. Click on the Reset Sync History button. Click Reset Sync History.
Log out of your user, then log back in
Launch Address Book, create a few test cards, then try to sync. It should be successful.
Now try restoring from your backup with File > Revert to Address Book Backup.

MAC PRO (Early 2008) RAID CARD ISSUE - SYSTEM FREEZEHello (hopefully someone can shed some light on my issue) I own as above a MAC PRO (Early 2008) this has a RAID card installed along with two 15k.7 cheetah hdd (320gb) and a spare drive, (which i m

Hello (hopefully someone can shed some light on my issue)
I own as above a MAC PRO (Early 2008) this has a RAID card installed along with two 15k.7 cheetah hdd (320gb) and a spare drive, (which i made a regular drive)
a while ago i had to replace the RAID card battery, so i did this, over a year later the same thing happened again, but as previous just left it and the system seemed fine for ages, until last night i was working in PHOTOSHOP and everything just froze and the screen kind of appeared GREEN, could not do a single thing. So restarted the mac, this time grey screen for ages and a message appeared, (macs version of blue screen) (see attached).
I restarted the machine and this time a flashing question mark folder!
could not do a thing.
so i found my copy of snow leopard and got the computer to run this and at least launch the DISK UTILITY and (Interestingly in the drop down menu RAID UTILITY was also in the menu) but it did not matter which utility i used the (RAID or DISK) neither could see any of drives, just the dvd drive.
so looked around on you tube and various forums and discovered if i take out the RAID CARD and re-plug the main lead from the RAID card back in to the LOGIC BOARD I would be reverting the MAC to a normal regular non-RAID computer.
After performing this HARDWARE task and inserting all three HDD, and running the DISK utility from the drop down menu via the SNOW LEOPARD disc.
(interestingly since the RAID card had been removed the RAID UTILITY from the drop down menu no longer appeared). running disk utility I can now only see the regular (spare) hdd and DVD Drive, but the two RAID HDD , again, still do not show up DISK UTILITY?
O.K. so i could chuck out the RAID card (AND RAID HDD) and just go with a regular set-up, and run a back restore from Time Machine on a NEW hdd purchased.
but what is wrong with the RAID, is the card at fault or are both HDD used for the RAID knackered? can i perform any tests, to see whats what?
thanks for your help in advanced.

hello people, the issue was in fact the GRAPHICS card nothing to do with the HDD or RAID system ( although this did cause issues with the RAID system it basically lost its way) below is my replay to another similar problem some one else had!
working in photoshop and then everything stopped working and the lot froze! only option was to force shutdown (via button).
and try to restart, hoping all was fine, this was not the case :-(
I had the added issue of the RAID card system, that i have, this was confused to say the lease and would not behave or work, causing the start up to hang.
so i thought the HDD must be bust and the root cause. ( but soon learnt it was not the cause )
...bought a new HDD removed the RAID card and replugged the cable from RAID card into LOGIC board, ( making the computer act like any normal non-RAID system). I managed to install the OSX, using the snow leopard disk way. once the mac was running, i started to notice the screen would flicker and started to see 'artefacts'. so i started to reveal my symptoms to the web and forums and soon discovered that my graphics card could be the issue all along?.
(nvidia geforce 8800gt 2x dvi).
I read up on that a fix, could be either A. reply the thermal paste, as the card could be over heating or B. stick the card in the oven trick.
Tried option A. first and nothing still issues, so last night took the plunge carried out option B. and ta da it worked! i even managed to run
from my new HDD my lasted install OS X, absolutely fine. I then thought, maybe i could repair my RAID so replugged all the HARDWARD back in and
carried out a disk repair and disk permissions on drives( took a small amount of time), via the SNOW LEOPARD disc - (Disk utilities) and this worked and now have my system working as it was just over 6 days ago.
what was the cost to get this? bought a new hdd so 40.00gbp and thermal paste and cleaner kit ( your still need to do this ) search video card trick on you tube.
and renew thermal paste, approx 15.00gbp, technically i don't need the new HDD, but it was all part of the trial and error way i went. ( i do have extra storage as a result!)"

Anyone know Disk Utility, Ignore Ownership, and disk image DL DVD issues?

I am currently having issues with backup DVD's I burned using Disk Utility. I can put the dual layer DVD's in and the system reads them. When I try to pull a file off the Dual Layer DVD a circle with an X appears notifying me that I cannot copy the files to my desk top.
When I check the DVD's permissions it reads Admin (me) read and write with the ignore ownership checkbox checked...which means I should be able to pull files off the DVD. The only way I can currently get information off the DVD is to duplicate the entire disk to a new folder by selecting the DVD while holding down the Cntrl key and selecting duplicate. I have had other issues with DVD's and disk images in Leopard....including having to eject either through disk utility or by selecting the image with the Cntrl key held down. Finder eject, keyboard eject, and the menu eject selections suddenly report that the disk is in use.
The DVD's were burned by creating a dual layer dvd image through disk utility with the read/write option checked.
After duplicating 2-3 disks, the system itself is unable to mount any more disks from the series of backups. When I look at disk utility it reads that the disk is not mountable. I have to restart my computer so the system can continue to read the backups.
My Itunes disk backups are marked the same way (ignore ownership) with admin read/write privlages....I have no problem pulling files off these disks.
I have tried both logging in as root and booting from an external drive...same problem. Is this some nasty Disk Utility bug? Is anyone else having bizarre permission related issues with Disk Utility and Disk Images.

When you create the image in Disk Utility, did you
change the 'Partitions' setting?
If you leave it to read 'CD/DVD', it will create a ISO9660/UDF image.
To be able to maintain permission and extended file attributes, you
need to select 'GUID Partition Map'.
I assume you used iTunes to create your music backup?
It seems it creates the correct image type for you.
Before sending this message, I actually created a single layer image,
copied some files to it and gave additional permissions to other users on my system.
Afterwards I copied the files to my Desktop, verifying that the attributes are still intact.
Best regards
(It took quite a while to burn this 4x DVD-RW Anyways, I hope I could help)

Strange Application Issues after Mountain Lion Upgrade!

I'm having, what I believe to be, strange issues with a clean install of Mountain Lion from 10.6.8
It's for my boss' computer at work so I can't afford to have it down for very long at a time. It's hard to pinpoint the issue(s).
Computer:
Mac Pro - Early 2009
OS X 10.8.3
2 x 2.6 GHz Quad-Core Intel Xeon
32 GB 1066 MHz DDR3
The startup disk is 4x2TB RAID 5 using Apple RAID card (Firmware version: E-1.3.2.0; Hardware Revision: 2.00; Driver version: 124
The following is what happened/is happening:
1. (Tuesday)
Created a bootable backup of system drive using Disk Utility
Performed a Clean install
Used migration assistant to copy over applications from backup
Downloaded (from Amazon) and installed Microsoft Office 2011
Imported Addresses (including imported Previous Recipients that were imported into Contacts before exporting on old system)
Setup email & copied over mailboxes from backup
Moved all files back onto the system (User folders)
Everything worked fine from Wednesday - Sunday.
Problems reported to me (Sunday)
"Chinese characters" on save dialogue box in Microsoft Excel
Mail crashed while dragging a photo from safari to it
After a restart, Mail, all Microsoft Office apps, and Final Cut Pro wouldn't open.
Tried to reset preference files, but nothing worked.
2. (Monday night)
Performed another Clean Install
Migrated Applications
Transferred mailboxes (not old emails at this time)
Imported same group of addresses as before into Contacts
Installed Microsoft Office
Moved user data back
Transferred old email mailboxes (Tuesday afternoon)
Everything worked fine Tuesday - Thursday early morning)
Problems reported to me (Thursday morning)
When typing in an email address to send an email, it didn't autofill. Mail crashed.
Mail wouldn't open. Different from last, this time it said the ~/Library/Mail folder was moved. I checked and the folder was there with everything in it fine.
The Microsoft applications that were open at the time of the Mail crash still worked, but others wouldn't open. After closing the open applications then they wouldn't open back up (same as before)
Final Cut Pro opened fine.
Fixed Mail by deleting the ~/Library/Containers/com.apple.mail folder.
Later found out that though Final Cut would open it would crash when loading a project and that Quicklook wouldn't work for quicktime files across the network & codecs were missing (this could have been cause by me when trying to test problems).
3. (Sunday)
Restored from a different bootable backup I made after 2nd clean install and migrated applications.
Repaired Permissions using Disk Utility
Moved over Mail data
Copied over user data
*Didn't import the addresses
Checked to make sure all the fonts were validated and no duplicates
Everything worked fine after install and through Monday.
Problems to me (Tuesday morning)
Microsoft Office disappeared completely from the computer. No folder in Applications or dock icons.
Slower to connect to network files
Re-installed Microsoft Office to keep work progress going.
What would be causing this peculiarity? It works after I fix it and for a little afterwards but then strange things happen.
Would repairing disk permissions on bootable backup (of 10.6.8) before using migration assistant help?
What is the best way to track down what is causing these issues?
Thanks!

I suggest that the best way to upgrade from 10.6.8 to Mountain Lion is one of the following:
(1) Simply perform an upgrade install. This is in fact Apple's recommended approach. I am not sure why you have not yet tried that. I have done this myself successfully.
(2) Make a backup of the working 10.6.8 system; better yet is to make two complete backups, one being a "clone," the other being a Time Machine backup. Use of two different methods gives you options should something go wrong. Then erase the original disk and install Mountain Lion, and on the first boot up run Setup Assistant (which is better than Migration Assistant) and transfer over EVERYTHING, including user accounts, settings, applications. I have also used this approach, also successfully.
You did neither (1) nor (2), but seem to have done some sort of hybrid by transfering applications and then manually moving over some mail files and moving over some user files. I don't think this is a recommended approach. It can result in permissions issues, which can cause things to "disappear" or otherwise behavior oddly.
I do not understand how your use of a RAID setup and a RAID card might affect any procedures which otherwise might work smoothly. Are you 100% certain that your RAID hardware and firmware are compatible with Mountain Lion?
Assuming that the RAID is not the issue and it behaves to the OS just like a normal disk, I would try the full disk erase and install of Mountain Lion followed by a Setup Assistant on first boot up to move over everything from your clone backup.
If this does not work, then I would erase and restore back from your clone, so you get your 10.6.8 system working again. Then I would try a simple upgrade install of Mountain Lion.
If that fails, then I would erase and install Mountain Lion with one new administrative user created who has a different user name than the person whose stuff you need to restore. Then with that new administrative user I would make sure the RAID is all up and running. Then I would use Migration Assistant to migrate over users only and would reinstall all software from scratch. If that is not to your liking, I'd as a less desirable alternative use Migration Assistant to migrate over everything, applications and users. You will have that new, extra administrative user as well as the original user(s), but that should cause no harm.

Best Practice to troubleshoot a Crawler Issue after SQL Server restarts

Hi Everyone
I am after some general advice or a suggested place to start when troubleshooting crawler issues after an unplanned, out-of-sequence server restart.
Specifically, the SQL Database in the SharePoint 2010 farm. Better yet, is there a standard practice way of resolving such issues?<o:p></o:p>
So far articles I have found suggest options from reviewing the crawl logs, creating a new crawl component, right through to using fiddler to monitor the crawler.
Are these sufficient places to start / methodologies to follow, what else should be considered?
Any advice greatly appreciated.
Thanks,
Mike

Well, as I said before, there are lots of different potential issues & resolutions for crawlers. It really depends on the issue. I would say that the base troubleshooting steps start the same no matter which service/feature you are looking
at. So, I'll try to keep this sort of generic, but beyond finding the details of the problem, the SOP or process will vary greatly based on what the error is. I hope this helps, and sorry if it's not specific enough.
1 - check the ULS logs
2 - check the windows application logs
3 - verify related services are running (get-spserviceinstance), possibly stop/start them to reprovision the instance on the affected server
4 - clear the config cache (this alone will clear about 30% of your basic problems)
6 - verify disk space & resource consumption on affected server (& SQL, SQL is always the potential to be the true "affected" server)
7 - iisreset
8 - verify connectivity between all servers in the farm and SP
9 - verify requir3ed features activated
10- check if any changes were made to environment recently (new hardware, updates to OS or apps, updates to GPOs, new solutions, etc)
11- check if the issue is reproducible in another environment (only reliable if this is a similar environment, i.e. same patch level test farm or dr farm). see if it occurs in other site collections within the web app, different web apps, different
servers/browsers, etc, basically just try to nail down the scope of the problem
There is a whole slew of thiings you could check from verifying certificates & perms, to rerunning psconfig, to checking registry keys, again I go back to it depends. hopefully this can get you started though. in the end ULS is where all
the real info on the issue is going to be, so make sure you check there. don't go in with tunnel vision either. if you see other errors in ULS, check them out, they may or may not be related; SharePoint is an intricate product with way more moving
parts than most systems. fix the little quick ones that you know you can handle, this will help to keep the farm clean and healthy, as well as crossing them off the list of potential suspects for your root cause.
Christopher Webb | MCM: SharePoint 2010 | MCSM: SharePoint Charter | MCT | http://christophermichaelwebb.com

Raid and replacing a disk, do i need to reinstall software? (RAID 10)

I have 4 250GB disks inside the Mac Pro, the first two are striped and the second two mirror the first two.
This gives me, perfprmance and some redundancy (I think) I have only 500GB available in this config so it is quite expensive, but works for me, my question is
"Can I replace the first disk from the set of four and then rely on the mirrord disks (3+4) to write data to the first disk, therby negating my need to do a restore?
Can I use he mirror function (almost a hot swap scenario)?
Views appreciated

The final chapter is this saga,
I replaced the disk and restarted my system, Disk utility was showing "degraded" for the raid config, I formatted the new drive created a new striped set but could not get the mirror to resynchronize , I tried the command line approach but after some time I was unsuccessful in getting the mirror to rebuild. So I thought this would be a good time to scratch all four disks and try softRAID as a solution, I purchased a full license but I discovered that softRaid only supports RAID 0 or RAID 1 and is not able to create a RAID 10 configuration. (James from SoftRAID explained that this was something being looked at for the future but one of the complexities was how to best represent RAID 10 graphically).
In the end I went back to Apples Disk Utility tool to create my RAID 10 config (ie disk 1 and 2 striped to create set A, disk 3 and 4 striped to create set B and then set A and B mirrored together), restored from backup and all is well.
I still need to figure out/learn how to add a replacement disk and then get the mirror to rebuild, but I proved that I could remove any one disk and still have a fully working/bootable system. Almost there......

B-Series Disk details RAID rebuild issues after disk removal

Similar Messages

Maybe you are looking for