TS130 - Raid desync and failed

Hi
I got a error yesterday morning. Unable to boot on hdd. i verify the raid controller and i see in status failed. each drive have ' error occured (0) ' . i shutdown, reboot, enter in configuration utility raid. remove hdd , the failed one. reboot the server got windows server back on. i verify data written on them i see that everything written last friday have not been written (database and file and folders). i think for this peticular error friday, one hdd failed and raid havent been able to sync file to another one. but the failed one can be the one who have the most updated file on it ?.

I believe upon boot, it will flash a screen looking similar to your BIOS that gives the status of your raid configuration, It only holds for a few seconds but the text is either Green, Yellow, or I assume red based off of the status.

Similar Messages

How do I remove one failing hard drive from raid set and replace with new one

Last Friday apparently one of my raid drives started failing.
As I mentioned on this forum I started getting continous beeping.
I was finally able to get the raid working at a degraded level. I ordered a replacement hard drive which is arriving today.
(In the meantime I made twice daily backups of my work.....)
Below was the message I got from the browser based raid software:
Blahblah 09    1000.2GB   RaidSet Member SamSung HD103SJ
Blahblah 10    1000.2GB     Free                 SamSung HD103SJ
Blahblah 11    1000.2GB   RaidSet Member SamSung HD103SJ
Blahblah 12    1000.2GB   RaidSet Member SamSung HD103SJ
(See this earlier thread if you wish!)
http://forums.adobe.com/thread/727867?tstart=0
At one point when I did the checked the browser interface I saw the message Failed and Degraded
As I said, I was able to work over the weekend on the degraded system.
This morning I got the beeping again and did the rescue and now I am running a "full raid" without the notice that one raid was "Free".
In any case, the new hard drive is arriving today.
What steps should I take to incorporate the new drive into the raid system.
I have one OS drive
and 4 tb raid drives.   One needs to be replaced with the new one that I am getting today.
Thanks
Rowby

Harm,
Regarding your comment:
Re: How do I remove one failing hard drive from raid set and replace with new one
Please tell me how to read the serial number from an individual drive rather easily, without un-installing them:
If you select the proper drive to change out, you only need to remove one drive and look at its serial number...
Step 1: Identify bad drive serial number using Areca's tools
Step 2: Turn off the computer
Step 3: Remove what you think is the bad drive based on following your numbered cable method, marked hot-swap bays, whatever
Step 4: Verify that the serial number matches the "bad drive" serial number from step 1; if it does great, proceed; if it does not match, go back to step 3
Step 5: Change out the CORRECT drive - that's the bottom line for this whole procedure
Cheers,
Jim

Disk Utility claims Degraded and failed, Raid Admin says its all fine

My company has a server they haven't been able to use. The person who set it up is now gone. I was acquainting myself with the set up. I looked in the Disk Utility of my company's server to see if i could quickly determine the set up of the system and noticed several of the drives said Degraded and Failed
I downloaded Raid Admin to see what I could do about it and it says everything is fine.
Before I tell my company it is OK to begin using the server to house and share major account files I want to be sure there are no problems. They are already using it for time machine back-ups for everyone so I'm loathe to start from scratch right now.

Ok; so there is an Xserve RAID hardware here, though this case does look to be the software RAID that is centrally involved with this and not the hardware RAID.
The next part of the investigation will involve DU, and to determine why your disk(s) here have apparently been configured for software mirroring, and possibly also using what Apple calls "stacked RAID".
You can either add a volume back in for the failed volume and rebuild that and [here is the usual rebuild sequence (HT3305)|http://support.apple.com/kb/HT3305], though if you're not planning to use software RAID (anymore), then you may well end up archiving your data and then issuing a diskutil command to delete the software RAID volume (see +man diskutil+ for an introduction, and look specifically for the RAID delete command syntax there) (or if that should fail), reinitializing your disks and importing from your backup.
I'd suggest having an off-line backup of your data first. Command input, operational errors or volume corruptions that might arise while using DU can have, um, serious consequences for disk data. See the +diskutil appleRAID delete+ command, but I'd also personally want to have an off-line backup of all your data first. RAID command errors and low-level RAID errors can be quite nasty around unarchived data.

SATA Raid 0 and Overclocking Issues. Help!

I'm building out a machine that doesn't seem to want to overclock in the slightest bit. I think my Serial ATA RAID 0 array seems to be the problem with OC'ing. Each time I change the CPU FSB settings, when I boot up, it tries to detect my array. Then it reboots after it fails.
Does anyone know what's going on? Someone mentioned PCI Bus settings to me...???
On Anandtech they OC'd this chip to 2.6 Ghz (290x9) with an 8.3%+ in voltage. I can't even get to 220.
Any help would be much appreciated.
Thanks!
======================
System Setup:
Athlon 64 3000+ Socket 939
K8N Neo2 Platinum
2 Hitatchi 80 gig SATA HD's
Leadtek Winfast 6600 GT (AGP)
Zalman CNPS7000B-AlCu Heatsink
Seasonic Super Tornado 400W PS

Ok, I switched it to SATA 3/4 and then I couldn't boot. I kept getting some error which would cause it to boot again. It happened right after it detected the array successfully. The warning message happened so fast the first couple times I didn't even notice it. It would flash some sort of blue screen like error (only it was a black screen) and then reboot itself.
Frustrated, I decided to start from scratch again. I wiped out the discs and re-created the RAID 0 Array and put my WinXP CD back in. Now while setting up WinXP I hang at the "Setup is starting Windows" screen.
It won't go anywhere from that. It happens after I copy over the RAID Driver and Controller from the Floppy. It copies more files after that and then hangs...
I also reset the CMOS with the jumper settings, un-did and re-did my SATA connections, even unplugged the little MB battery... :(
Any suggestions? This is so frustrating.
TIA.

RAID 0 volume failed - Intel RST, W530 (wonder if it is hardware issue now)

Hi,
My laptop is about two years old. I got one of two intel RAID 0 volumes failed several months after I got this laptop. This problem has been on my laptop for a long time.
The functionality of my laptop started to become poor after this volume failed.In the beginning, windows explorer stopped working and restarted every time I opened the laptop. The windows repair tool said windows could not be repaired... So I reinstalled the OS and reset it to factory setting. However, the crashes persisted and gradually became more frequent. Many other error reports showed up. After searching for solutions, I finally did a clean windows install and used the BIOS Intel RST to repair the corrupted volume (I deleted old volumes created new ones).
Unfortunately, now, the same volume fail error appears again and the functionality of my laptop is impacted. Sometime I cannot save my excel or pdf file because program stop working, or cannot open a pdf file. I have to restart the OS.
The detail error message of Intel RST is: "your volume appears inaccessible. Try fixing any problems reported on the array disks. If this fails, review the Troubleshooting section under Help for more information. In all cases, back up any accessible data before taking action".
I'm now wondering if it is the hardware issue. If so, I'm thinking about buying an extended warranty because my orignal warranty has expired. However, I'm not sure if the warranty can cover this...
In this community, I find there are two types of extended warranty, one will start from the expiring date of the original one and the other will start from the date of purchase. I suppose I need to find the second one.
I'm also wondering the quality of the warranty. Will it take a long time to repair if I send it? or will it take a long time for them to ship?
Any idea, solution and experience in warranty / repairment would be appreciated.
Best Regards,
Haoyi
BTW, here is also my experience with Lenovo if you would like to have a look at:
I got my W530 two months after purchases... I found it was a common problem in Lenovo...
When my laptop was still in the original warranty, I contacted the lenovo customer service for repairment of the failed volume. Those people told me it was errors coming from my software. They said the repairment was not covered in the original warranty and I needed to buy a new type of warranty (related to software repairment). I had no confidence in the quality of lenovo's customer serivce... So I did not buy it.

Hi, Colonel,
Thank you for reply. I tried HD Tune, but it cannot show any information about my harddisk. It only shows Intel Raid 0 Volume, the firemware version is 1.0 and the capacity is 931.5GB. There is no other information, such as serial number, standard, supported, and buffer. I cannot choose supported features. HD Tune also cannot display the temperature of my drives. What should I do?

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.

Replace the Hot Spare that Shared between Raid 1 and raid 5

I have ProLiant ML370 G6 with Smart Array P410i Controller on System Board
I have two Logical Drive (Logical Drive 1 - Mirroring (RAID 1) And (Logical Drive 2 - Distributed Data Guarding (RAID 5)
The logical Drive 1- Mirroring (RAID 1) Have two Physical Drives
The Logical Drive 2 Distributed Data Guarding (RAID 5 Have three Physical Drives
And There Are One Spare Drive Shared btween RAID 1 and Raid 5
Controller Configuration Summary
2 Data Array(s)
2 Data Logical Drive(s)
5 Data Drive(s)
1 Spare Drive(s)
The problem :
there are that the spare Drive FAil and have warining To replace it
I replace this drive with new one but the repulid for the Drive not start and Give Inactive
How Repulid the Hot Spare drive ?

Hello Amostafa,
Welcome to the HP Forums, I hope you enjoy your experience! To help you get the most out of the HP Forums I would like to direct your attention to the HP Forums Guide First Time Here? Learn How to Post and More.
I understand that you are looking to rebuild the hot spare drive on your ProLiant system, and I would be happy to guide you towards a resolution!
I am sorry, but to get your issue more exposure, I would suggest posting it in the commercial forums, since this is a commercial product. You can do this at:
http://h30499.www3.hp.com/t5/ProLiant-Servers-ML-DL-SL/bd-p/itrc-264
I hope this helps!
Regards
MechPilot
I work on behalf of HP
Please click “Accept as Solution ” if you feel my post solved your issue, it will help others find the solution.
Click the “Kudos, Thumbs Up" on the right to say “Thanks” for helping!

KT3 Ultra2BR, MS-6280E Raid, suspend, and other issues

Hello!
Well, actually my box performs admirably. There are some annoying quirks tho, which you guys might have some solution to it.
1. My system have been working so fine, with ABSOLUTELY no problems. Things running fine means no errors, no BSOD, not even crashes, but one thing actually: SUSPEND. Everytime I purposedly or accidentally press the suspend button (either on windows' shutdown menu or the suspend button on my keyboar), the screen goes blank, suspended. When I wake it back, it throw a BSOD right on my face! I tried changing S1 suspend state to S3. With S3, things goes even worse with the system hangs on the videocard bios display. Anyone successfully implemented S1 and/or S3 suspend states? With this I had to disable/hide the suspend button, so no more accidents. Anyway if anyone can give me some solution I would gladly take.
2. This one refers to RAID versions of the mobo. I get to wait about 15 seconds on "Starting WindowsXP" boot screen because I enable the Promise Fasttrak133 RAID controller. I have to enable it cuz I have many IDE devices plugged to my mobo. When I disable it, the boot up screen only show for about 2 seconds (as most of you would already know in non-RAID versions). What's with this RAID thing? Before this mobo, I used ABIT VP6 with highpoint RAID controller and these extraordinary long wait times did not occur. Well, just the wait times though, after windowsxp booted, things went fine. But this is annoying sometimes.
That is all I think,
For anything from attention to solutions you guys are going to give, I would say Thank You.
d

Hello again,
Thank you for the quick response.
Well, I haven't tried reinstalling the windows since if I do so I would have to set up everything from scratch and that will waste much time. But again I think reinstalling windows can help fix things around, I hope. I will do if time allows. Thanks. Anyways I wonder whether YOU could implement the S1 and/or S3 state successfully with your system, can you?
Also I'd like to update that the wait time is not 15 seconds, but actually 40 seconds!!! Isn't that annoying? Well, the wait times diminishes if I restart my computer from hibernation, which provide no wait times and my system could start in merely seconds. Well, that makes me wonder tho. Is the wait time really necessary? If so, why restarting from hibernation need no such wait time at all? Could there be a driver update or bios update to address this problem?
And again there's another problem just risen lately. Its shutdown problem. Occasionally when I shutdown my system, it shuts down but immediately start up again. It's like the shutting down mechanism failed. This didn't happen before, just recently. Any clue why this is happening? I'm afraid the jump from immediate restart after shutdown will eventually break my harddrives.
Thank you for your attention,
regards
d

Quicktime RAID Intel Vista Failed

I've noticed a dozen posts regarding this issue. Intel says it's Quicktime causing the problem. How do we contact Quicktime Support to hear their side of the story. This is a major problem. Unsuspecting users can repeatedly lose data from these RAID failures caused by Quicktime.

There is a problem with RAID volumes and QuickTime and iTunes on Windows Vista - using Intel chipset. That isn't in contention.
As for what triggers it or not, hum... it's no fun if it affects you and your system. WHY is it that Quicktime and iTunes are an issue? is it related to choppy performance when playing back content from some (slower) boot drives?
Safari 3 was made available when it was still "alpha" which I think was too early and tarnished it some (I could see only if it was actually needed for iPhone, but that begs more questions).
+If you look in the Vista event viewer you will find event id 9 errors with a source of iastor, which is the intel raid driver. This is the source of the quicktime slowdown. If you leave quicktime running long enough it will fail both drives of a raid 1 array and Vista will crash.+
http://www.nvnews.net/vbulletin/showthread.php?t=86131
Intel RAID
QuickTime Vista RAID Havoc
As someone who runs Vista x64, and has all my media and data files on a RAID, I don't take things like this lightly. (I also will not be installing Quicktime or iTunes until x64 support looks better.)
UPDATE: So it looks like some of these issues could be related to using an Intel RAID array and that there could be fixes coming with the famous Vista Service Pack 1.
http://www.geekzone.co.nz/hadders/2273
Intel release notes for its Intel Matrix Storage Manager version 7.0.0.1020 that acknowledge a known problem with using iTunes and Quicktime to play video.
The only thing I could find on Apple was the article
iTunes Video Playback Performance
http://docs.info.apple.com/article.html?artnum=305392
which touches on QuckTime and DirectX and Direct3D.
Latest Cnet forum fix
Intel's Fix for Vista
edited: hatter

Mac Pro RAID Card and Western Digital drives

I'm having huge troubles with these items.
I first installed four WD7500AYYS (Raid Edition) to build a RAID 5 and install Leopard on it. At this point, one of the drives was probably DOA and didn't show up in the bay. I then reinstalled the Seagate that shipped with the machine, then proceeded to create another enhanced JBOD raid with one of the WD drives. After a couple of seconds, RAID utility reported an error (disk about to fail and such). I then tried with another one. The process ended with a kernel panic after two hours, while RAID utility was still marking the drive for enhanced JBOD. That disk never show up again, in any bay.
At this point, I'm left with two WD drives. I can't get past the creation of a RAID set with them, no matter what. Either RAID utility reports an error, or it says the disk has been ejected, or it keeps create the RAID for hours... The later usually ends with a "force quit", or a force shutdown. During these attemps, the RAID card went missing once, then it appeared again on the following reboot. The RAID battery, which was fully charged at first, is now being "repaired" (charging ?).
I then ran AHT to see whether there was something wrong. No errors reported.
Because all four drives were Raid Edition, I thought this could be the root of the problems. So I bought a Caviar SE16 (WD5000AAKS). To no avail. It fails too, in the very same way. And now it no longer appears in any bay.
The last step I took was to remove the RAID card (connecting the iPass connector to the motherboard). Out of the five WD drives, only two RE2 (the two that still show up with the RAID card) do appear in disk utility. But disk utility never ends "writing the partition map" or "preparing for initialization".
By now, I end up with five WD drives that appear to be just dead, as if they were killed by the RAID card trying to RAID them. The only drive that works, with or without the RAID card, in any bay, is the Seagate. I didn't try to fiddle with it though (I'm reluctant to format it just to see whether I can create an enhanced JBOD raid with it).
So the question is, are Western Digital drives compatible with this RAID card ? If they do, then how a RAID card can kill them in such a way while keeping the Seagate alive ?
I'm lost in conjectures. I don't even know if/how I can bring all the WD drives back to life. I'm not sure the RAID card is faulty, I've already lost a lot of time and money, I'm not willing to buy yet another drive to see it fail too, and my Mac Pro is kind of useless as I don't want to spend time on installing/configuring everything I need on a drive that is bound to be replaced by a larger RAID 5 array.
Any help is appreciated. Thank you.

Someone yesterday or Friday, had a system with 4 x 1TB drives and Pro RAID, but in their case, it was determined later Saturday that drive bay #1 was not functioning.
Hopefully these fully retail drives, not OEMs, and I would think they are fine. They are what I would use (Sonnet Tempo only supports RE of the WD drives). Someone else, Danish?, had 3 out of 4 WD drives were DOA.
I've never had trouble buying over a dozen from OWC, so it does seem odd.
If you have SoftRAID 3.6.6 I would use that to zero the first and last 100 sectors, or you can begin to zero the whole drive and cancel at any time, just to check the health of the drive and that it can zero and not produce I/O errors.
There are two other methods for accessing and managing Mac Pro RAID, ARD and CLI
http://docs.info.apple.com/article.html?artnum=306231
Originally, only Apple drives were supported. My understanding was that this changed. But the only article I found in KB dates back to Aug '07:
Question: What drives does Apple support with the Mac Pro RAID Card and the Xserve RAID Card?
Answer: +Only Apple drives are supported with the Mac Pro RAID Card and the Xserve RAID Card.+
My understanding that 3rd party retail drives such as WD RE2 750GB, Seagate, Hitachi were supported as well since the article was written - and I can't find where I read that, but sure that I did, as this was discussed in the past.
I'd like to find an official article. Even my friend Google was helpless

Apple Raid Card Battery Failed

Hey guys !
I have an early 2008 Mac Pro with a Raid Card and i get this message battery failure other than expired
actually i got this message again about an year or so back ... so yes it happened before ... Apple replaced my battery
Now im out of warranty coverage.
Questions are :
How does this affect my Raid Set ?
Can my Raid Set survive without the battery ?
If yes ... what are the downsides ?
What can i do to manage the situation without changing again the battery ?
Hope to get some advice soon on this matter
Thank you very much.
PS
Down below i pasted some specs for my machine
Mac Pro RAID Card:
PCI Slot:          Slot-4
Hardware Version:          1.00
Firmware Version:          M-2.0.5.5
Expansion ROM Version:          0018
Shutdown Status:          Normal shutdown
Write Cache Enabled:          No
Battery Info:
Firmware Revision:          1.0.2
First Installed:          1/1/01 2:16 AM
Last Date Conditioned:          2/24/12 3:47 PM
State:          Faulted Battery
Fault:          Battery failed (other than expired)
Status:
Charging:          No
Conditioning:          No
Connected:          Yes
Discharging:          No
Sufficient Charge:          No
Drives:
Bay 1:
Product ID:          ST3300655SS
Serial Number:          3LM35BGK00009827PBXY
Firmware Revision:          A005
Type:          SAS
SMART Status:          Unsupported
Capacity:          300 GB (299,999,999,488 bytes)
RAID Sets:          RS1
Status:
Assigned:          Yes
Failed:          No
Foreign:          No
Missing:          No
Reliable:          Yes
Roaming:          No
Spare:          No
Bay 2:
Product ID:          ST3300655SS
Serial Number:          3LM622YT00009923HP5Q
Firmware Revision:          A005
Type:          SAS
SMART Status:          Unsupported
Capacity:          300 GB (299,999,999,488 bytes)
RAID Sets:          RS1
Status:
Assigned:          Yes
Failed:          No
Foreign:          No
Missing:          No
Reliable:          Yes
Roaming:          No
Spare:          No
Bay 3:
Product ID:          ST3300655SS
Serial Number:          3LM2Y49T00009827PAZV
Firmware Revision:          A005
Type:          SAS
SMART Status:          Unsupported
Capacity:          300 GB (299,999,999,488 bytes)
RAID Sets:          R0-3
Status:
Assigned:          Yes
Failed:          No
Foreign:          No
Missing:          No
Reliable:          Yes
Roaming:          No
Spare:          No
RAID Sets:
R0-3:
RAID Level:          Enhanced JBOD
Capacity:          299.8 GB (299,798,364,160 bytes)
Available Capacity:          Zero KB
Drives:          Bay 3
Volumes:          Vol-R0-3
Status:          Viable (Good)
RS1:
RAID Level:          0
Capacity:          599.73 GB (599,730,946,048 bytes)
Available Capacity:          Zero KB
Drives:          Bay 1, Bay 2
Volumes:          R1V1
Status:          Viable (Good)
Volumes:
R1V1:
BSD Name:          disk1
Capacity:          599.73 GB (599,730,946,048 bytes)
Read Command Size:          2 MB
Read Ahead Margin:          16 MB
RAID Set:          RS1
Status:
Degraded:          No
Inited:          Yes
In Transition:          No
Viable:          Yes
Vol-R0-3:
BSD Name:          disk2
Capacity:          299.8 GB (299,798,364,160 bytes)
Read Command Size:          2 MB
Read Ahead Margin:          16 MB
RAID Set:          R0-3
Status:
Degraded:          No
Inited:          Yes
In Transition:          No
Viable:          Yes
Hardware Overview:
Model Name:          Mac Pro
Model Identifier:          MacPro3,1
Processor Name:          Quad-Core Intel Xeon
Processor Speed:          3.2 GHz
Number Of Processors:          2
Total Number Of Cores:          8
L2 Cache (per processor):          12 MB
Memory:          8 GB
Bus Speed:          1.6 GHz
Boot ROM Version:          MP31.006C.B05

The RAID card battery backs up the memory buffers on the card. These are needed for calculating the checksum blocks used in RAID 5 and similar schemes.
If you are not running RAID 5 or similar, you do not need the battery. For that matter, you do not need the RAID card, either (unless you are running SAS drives).

HP 17" 2070 n; raid 0 has failed per Intel Rapid Storage

have an HP 17" 2070 nr; has 2 HDD's in raid 0;
and the Intel rapid storage is indicating that something has failed;
unit is out of warranty so asking here. HDD says I have 1tb.
everything is working great so no problems.
I could (per Intel Rapid Strg.), "set to normal" the offending unit, but I am hesitant
Please could someone advise me on this
This question was solved.
View Solution.

Awesome! Glad to hear that it worked for you. If you have any other questions don't hesitate to ask. I appreciate the kudo
Thanks,
Sean
-------------How do I give Kudos? | How do I mark a post as Solved? --------------------------------------------------------

Z87 g45 gaming...raid 0 and an ssd. Not sure i understand

I have been reading up this while my part are on a ups truck somewhere. Not sure i understand.
I realize that for the ssd the Sata needs to be set to achi before I install windows. Then Install windows 7 pro on the ssd.
Then I am lost. I bought this board because of the feature of inboard raid setup. Maybe all boards have this? This is all new to me. Trying to learn.
If the Sata is set to achi, will that screw up the raid?
Planned on raid 0 with two WD 1tb blue drives.
I read the manual, but didnt make sense.
Will this show up as ONE drive +\- 2tb in My Computer?

Quote from: Goodteacher on 04-September-13, 11:51:05
I have been reading up this while my part are on a ups truck somewhere. Not sure i understand.
I realize that for the ssd the Sata needs to be set to achi before I install windows. Then Install windows 7 pro on the ssd.
Then I am lost. I bought this board because of the feature of inboard raid setup. Maybe all boards have this? This is all new to me. Trying to learn.
Nope. You Should set your MB SATA controller to RAID otherwise your OS dont know how to control it if you turn it to RAID mode after you have installed it in AHCI mode.
- In RAID mode it controls drives at RAID array(s), like they are set (RAID 0,1,5,6,10,...) and those that arent in any RAID array it controls like AHCI and so on OS installation it installs drivers and register for it like so.
- In AHCI mode it controls all drives like AHCI and so on OS installation it installs drivers and register for it like so.
Edit: So easyes thing is to set your SATA controller in RAID mode and install your OS thatway. Because, then you never have to worry about it as it has controllers to hole thing.
- But if you Install OS (Windows) in AHCI it wont have correct registery or drivers for that same controller if you someday want to use other drives in any RAID and so you would get BSOD on loading/starting screen.
Quote
If the Sata is set to achi, will that screw up the raid?
Nope it wont screw already existing RAID array, choose RAID to that controller again and you have your RAID array back. That is if you havent edit those drives in anyway.
Example: setting SATA controller back to AHCI is only way to upgrade drives Firmware if one is needed, as that software need to see the single drive in that array to do it.
Edit2: Seeing problem is on drives that are in RAID array and those that arent set in any RAID 0 array or so, should get thrue FW update just fine (there can be some exceptions on here) .
Quote
Planned on raid 0 with two WD 1tb blue drives.
I read the manual, but didnt make sense.
Will this show up as ONE drive +\- 2tb in My Computer?
Yes, on your setup, that SSD would show as one drive and that RAID array as one drive. So you would see 2 drives where choose your os drive if you have them already setuped before OS install.
- Every drive you add to RAID 0 array adds space without losing it and allso you get more speed after everey add to point where you get limits of cotrollers speed. That is, if you get there before you have populated all ports.
- Every drive you add to RAID 1 array would add more secure of your data, but you would get only the space to use that your smallest drive have as all drives have 1 to 1 copy of every file.
P.s. when you install the Windows I recormend to have only that drive installed where you want your sytem be in! or your files can be stripped in every drive and then if one drive fail you may get weard BSOD's that are hard to get to!
Most likely this mess happends when one of the drives has already have OS in it on onetime of its life (formating the drives wont make difference).
Edit3: i personaly have used RAID 0 years and never have hade a problems. But if one of those drives fail, then i lose all my data on that RAID 0 array and thats why i go with oldsaying from the time when PCs start to make in the homes "Allways backup your files ! "

Jabber for Windows - periodically tries to re-install and fails

Jabber 9.1
CUCM 7.1.3
Windows 7 32 bit
Cisco Presence 8.0.2.10000-30
Jabber for windows - periodically tries to re-install and fails. After install Jabber works for awhile but then when trying to open another program(Outlook, IE Explorer) it tries to re-install. If I go to the directory where the install files are and do repair it works. This seems like a conflict with another application.
I see this in the Windows application event log:
Detection of product '{4EB9D7DD-65B5-44ED-B877-CE3EF9B4530F}', feature 'Cisco_Jabber_Files', component '{7CB949BE-2270-4992-9C4C-8FDDB90F6FE2}' failed. The resource 'C:\Program Files\Cisco Systems\Cisco Jabber\JabberMeeting\DesktopShare\atgpcdec.dll' does not exist.
Jabber 9.1
CUCM 7.1.3
Windows 7 32 bit
Cisco Presence 8.0.2.10000-30

Hi,
Do you have WebEx Productivity plugin installed on the machine? I can reproduce this problem after exiting Jabber, creating a One-click meeting from Outlook and restarting Jabber. Please provide further information to help me open a defect.
- What was the version of Jabber on this machine prior to 9.1.0?
- What is the version of the WebEx productivity tool plugin (if it is installed)?
- Is there a particular sequence that you can follow to reproduce it everytime?
Thanks,
Maqsood

Cannot access to any site with ssl connection and fail to open safari and keychain, unless restart computer and login in with Guest account.

when Update to 10.7.2 ,I cannot access to any site with ssl connection and fail to open safari and keychain, unless restart computer and login in with Guest account.
OS:10.7.2
Macbook Pro 2010-mid 13inch

I also have the same problem, however if I use Firefox or Opera sites with ssl connection work fine. Still, I can't use Google Chrome (ssl), Safari (ssl), the Mac app store (generally), or the iTunes store (generally). Both the iTunes store, Safari and the app store won't respond, and Chrome displays this error: (net::ERR_TIMED_OUT). The problem persists regardless of what network I'm using. Also, when trying to access the keychain or iCloud, the process will not start (will hang). I didn't have these problems at all before updating to 10.7.2.
Sometimes rebooting helps, and sometimes not. If the problem disappears by rebooting, then it only lasts a few minutes before it reappears. It is very frustrating, especially since there doesn't seem to be any obvious or consistent way of which to fix it.
I'm also using a Macbook Pro 13-inch mid 2010.

TS130 - Raid desync and failed

Similar Messages

Maybe you are looking for