RAID 10 upgrading

I've got 2 1TB drives in a RAID 0 in my MP now. I just got 2 more, and was thinking of making all four drives a RAID 10.
If I install the new drives, and Mirror them, can I then copy my existing data from the other drives onto the new Mirror Raid 1, and then reformat the original 2 drives to another Mirror (RAID 1), and then stripe the two mirrors together as a RAID 10, without losing the data on the first Mirrored pair?
Will the new RAID 10 then go about copying the data from the first Mirror to the second Mirror on it's own?
Or, do I need to just copy all my data onto a firewire drive, and then reformat all the drives and wipe them out, build the RAID 10, and copy my media back to it?
I hope it's clear what I'm asking.
Thanks,
Jim

Hi. I was emboldened by this thread, to which you contributed, and had the last word, last time I checked:
<http://discussions.apple.com/thread.jspa?messageID=4038978&#4038978>
I failed to mention that I was going to try this with internal drives. I got the MaxPower sled thingie that let me put my boot disk and a backup in the 2nd DVD drive space.
Did you ever get around to testing whether the rebuilding after putting in a new disk was working?
Or, are you aware of anybody who has been able to get the Auto-Rebuild function in Disk Utility to work?
I am going to look at that CalDigit card when it comes out. But, I was reading a thread in another forum to which I subscribe, and some of the propellor hats over there say that with the newer superfast CPUs, that a hardware RAID isn't going to improve things that much over a software RAID. I can install the cards and drives and stuff, but my knowledge of how it works is woefully inadequate.
Thanks for your help!
Jim

Similar Messages

FCP video freezes - RAID upgrade problem?

Last week, the 4 drives in my RAID were replaced with 750GB drives, Mac OS Extended (Journaled), RAID 5. Initialization took about 36-40 hours, as expected. Previously, my 4 drives were 250 GB, Mac OS Extended (Journaled), RAID 0.
With this upgrade/change, my captures through FCP now have freezing video. I can see the video freeze in the FCP capture window, when I play the clip in FCP and when I play the clip in QT 7.4. By freezing video, I mean the video plays appropriately for a few seconds, then freezes for a couple of seconds, then plays appropriately for 10-15 seconds, then repeats. The audio is fine. Re-capturing yields the same problem, although with freezes in different places.
Could this be a result of the RAID upgrade? QT 7.4? For what it's worth, I have another Mac running on the other side of the RAID (FCP 5.0.4, QT 7.3, RAID 0) that is having no problem at all.
Any thoughts and suggestions are appreciated.
I am posting this on the RAID discussion board as well.
Thank you!

QT 7.4 still has issues...added new ones as a matter of fact...
http://prolost.blogspot.com/2008/01/thanks-again-apple.html
Shane

Dropped frames on Xserve RAID upgraded w/750GB drives.

I'm capturing in 10-bit uncompressed standard definition 720x480. I just upgraded one side of my Apple XRAID, (connected directly via fibre channel) with seven, 750GB hard drives from Apple, drives designed for the XRAID, (came with there own sleds.)
Current Xserve RAID firmware version is at version 1.5.1/1.51c
Before the upgraded drives, no issues with dropped frames, (drives 1-7) the other side of the same RAID has no problems, (currently running 250GB drives, drives 8-14.) All sleds are populated with drives of the same capacity, (respective to each side.)
The drives were formated using the Xserve RAID Admin software and mounted using Apples Disk Utilities, Journaling turned off. The final formated capacity of the RAID on drives 1-7 is 4.1TB.
When I capture to the drives on the upgrade side, I get dropped frames. When capturing to the other side, no issues, works great. I checked the settings for performance and they are the same for both sides, as follows:
Use Controller Write Cashe - ON
Allow Host Cashe Flushing - OFF
Use Drive Write Cashe - ON
Use Steady Streaming Mode - OFF
Read Prefetch: 128 stripes (8 MB/disk)
My capture box is an AJA I/o and has never given me dropped frames till now, but only on the side of the RAID that has the new 750GB drives. I also have another RAID that uses 500GB drives on both sides and it work just fine as well, (no dropped frames) using the same performance settings in XRAID utilities.
Any suggestion on why these new Apple drives modules are dropping frame would be very much appreciate. Again 7 new 750GB drives from Apple w/sleds having dropped frame issues.

I'm capturing in 10-bit to avoid loss of quality from analog sources like BetaCam SP as well as line 21 must be part of the captured file, because it contains line 21 for captioning. Eight bit has a banding issue that I can't have in the final product and 10-bit doesn't have this issue.
Source quality is maintained completely when working in 10-bit uncompressed, as well as the captioning data that I need, which is stripped out of the captured video latter. Captioning software can read line 21 of the raster area, of the captured file.
Source video is from BetaCam SP, DVC Pro and DVCam.
The RAID is an Apple Xserve RAID, connected via Fibre channel directly, (no xsan.)
I also create high quality QuickTime Streaming files from these source files, the higher the quality of the source video the the better the streaming files look when created.
I have never had any problem capturing till I installed these new drives from Apple.
The RAID is as stated above, is an Apple Xserve RAID, connect via a fibre channel card in a Mac Pro 3.0GHz tower, (no xsan is used, due to connecting directly to the XRAID.)

K9N2 SLI Platinum RAID Upgrade

I just upgraded my system from the K9N to the K9N2 (see sig for details). The only components changed were the motherboard and the processor - all of the other components were operating fine on the old system. The new system seems to be running OK (with some issues).
My problem is that the new system could not work with the old RAID disks. I had to turn off RAID in the BIOS to get any where. Once I did that - Vista booted up and installed tons of new files (as expected to support the new motherboard).
Now I want to re-enable RAID - but expect it to fail. I am guessing that the new RAID controller (10.0.33) is incompatible with the old system (6.94 or something like that)?
Would a solution like re-enabling RAID, breaking the RAID configuration at boot - and then re-establishing (AND re-syncing) after Vista boot solve the problem?
Just looking for a bit of reassurance here before I do any thing drastic. (I also have some other issues but will start other threads if I can not figure them out.)

Sorry about the confusion - I forgot to hit change profile! (dummy) Hope I got it correct this time.
I expected to have to do at least a repair of Vista. The trouble was the Visa install disk could not see ANY windows installation.
I thought I had installed the new motherboard drivers. Now I am not so sure that went correctly. I am now - as I have gone to the Nvidia site and installed all the latest stuff.
I hope not to have to do a complete new install - too much stuff to update. In fact the Vista install would not even LET me do a new install (it wanted drivers - and I fed it the new RAID drivers - it still did not like it).
My question still is: can I (now) re-enable RAID and do a rebuild?

RAID upgrade on late 2009 Macbook

Just thought I'd share this as I was unable to find any help on the topic. I replaced my optical drive with a 2nd hdd. I then installed 2 80gb Intel X25m ssd's. I used a usb boot flash drive to boot OS X 10.8.2. From there I was able to use the disk utility to create a raid0 stripe array. I then installed mountain lion on the raid array. It worked like a charm and I was really pleased with how easy it was to setup. Performance is noticebly increased. I'm only posting this because any raid info I found only pertained to the Macbook Pro.

You need to do this first. Of course you will boot from your flash drive rather than the Recovery HD.
Install Lion/Mountain Lion on a New HDD/SDD
Be sure you backup your files to an external drive or second internal drive because the following procedure will remove everything from the hard drive.
Boot to the Internet Recovery HD:
Restart the computer and after the chime press and hold down the COMMAND-OPTION- R keys until a globe appears on the screen. Wait patiently - 15-20 minutes - until the Recovery main menu appears.
Partition and Format the hard drive:
1. Select Disk Utility from the main menu and click on the Continue button.
2. After DU loads select your external hard drive (this is the entry with the mfgr.'s ID and size) from the left side list. Click on the Partition tab in the DU main window.
3. Under the Volume Scheme heading set the number of partitions from the drop down menu to one. Click on the Options button, set the partition scheme to GUID then click on the OK button. Set the format type to Mac OS Extended (Journaled.) Click on the Partition button and wait until the process has completed. Quit DU and return to the main menu.
Reinstall Lion/Mountain Lion: Select Reinstall Lion/Mountain Lion and click on the Install button. Be sure to select the correct drive to use if you have more than one.
Note: You will need an active Internet connection. I suggest using Ethernet if possible because it is three times faster than wireless.

RAID 5 upgraded, now video freezes

Last week, the 4 drives in my RAID were replaced with 750GB drives, Mac OS Extended (Journaled), RAID 5. Initialization took about 36-40 hours, as expected. Previously, my 4 drives were 250 GB, Mac OS Extended (Journaled), RAID 0.
With this upgrade/change, my captures through FCP now have freezing video. I can see the video freeze in the FCP capture window, when I play the clip in FCP and when I play the clip in QT 7.4. By freezing video, I mean the video plays appropriately for a few seconds, then freezes for a couple of seconds, then plays appropriately for 10-15 seconds, then repeats. The audio is fine. Re-capturing yields the same problem, although with freezes in different places.
Could this be a result of the RAID upgrade? Any thoughts and suggestions are appreciated.
Thank you!

OK...
The tech switched the RAID from 5 to 0+1, and the problem is solved. Perhaps 5 was too slow to keep up with my video; perhaps something went awry in the initialization of 5. Regardless, it's now fixed.
If you find yourself in this situation, consider your RAID set-up, and consider switching from 5 to 0+1. It will affect the amount of available space on the RAID (1.3 TB for me, still a lot of space but less than the 2.7 TB or so that I would have with 0), but it might well solve your problem.

RAID firmware upgrade -- 750 gb disk capability

Has anyone heard anything about Apple's potentially upgrading its RAID firmware so that 750 gb disks can be used? Would such an update likely coincide with the release of Leopard?
Thanks for any insights

Based on the history of Xserve RAID, I believe it's possible. They start from 180 and change to 250, 400, 500. The latest drive available is 750GB. But the question is I do not know if many drive vendors make PATA interface for these drives. It may not be a big deal for drive vendors slap a PATA interface to it.
It's all speculation here. I personally would like to see upgrade in the entire array with more beefy controller and use SATA II or SAS drives instead. Maybe changing to infiniband interface would finally give some real performance to the storage.
I do not think there is any relationship between Leopard release and Xserve RAID upgrade (if there is ever any).
So my suggestion is to think really hard on what you need and when you need it,if the answer is now, then buy it.
Facts: Xserve RAID was released in 2003 February
500GB drives were made available to Xserve RAID in 2005 September.

OS 10.5 upgrade...FiberChannel card

I am wanting to upgrade to OS 10.5, but before we do, 1 question. I have a Apple Fibre Channel card connected to my Ciprico MediaVault RAID array. What is the process of upgrading the OS? Do I need to unplug the card from the RAID, upgrade, plug the card back in and reboot? Will the OS recognize the RAID array? Are there any updates that need to be done for fibre channel card?
Any help would be appreciated!
m

I am wanting to upgrade to OS 10.5, but before we do, 1 question. I have a Apple Fibre Channel card connected to my Ciprico MediaVault RAID array. What is the process of upgrading the OS? Do I need to unplug the card from the RAID, upgrade, plug the card back in and reboot? Will the OS recognize the RAID array? Are there any updates that need to be done for fibre channel card?
Any help would be appreciated!
m

Recommended system improvements after GTX470 died

After 4 years of using my system with no major issues and only minor tweaks, I started to get several BSOD errors. I eventually realised that my ASUS GTX 470 was dead. This is never a good thing, however I had already been thinking that it was time to investigate some upgrades and I'd very much appreciate the thoughts and wisdom of the forum to work out which path to take.
As well as editing HD DSLR footage I am now editing 4K footage from the Panasonic GH4. I also work in After Effects and plan to do more in Cinema 4D. The PC is also used for Photoshop and graphic design tasks.
I currently have:
MB: Asus P6X58D-E
CPU: Intel Core i7 930 2.8GHz
CPU FAN: Noctua NH-D14 Dual Radiator CPU Cooler
RAM: 12GB (6 x 2GB) Corsair Dominator DDR
Graphics: NOW DEAD BUT DID HAVE - 1.28GB Asus GTX 470 3.3GHz
Case: Coolermaster ATCS 840
OS (Win 7 64bit)
WD Velociraptor
300GB
10,000rpm
Storage
WD Black
2TB
7,200rpm
Media
WD Black
2TB
7,200rpm
Project/Source Video
WD Black
1TB
7,200rpm
Media Cache/Page File/Export
Samsung SSD EVO 840
120GB
Drive Bay (back-up and archive)
Various bare drives
Back-ups
4 Bay Silverstone USB3
4 x 3TB WD Red
I also have a Samsung EVO 840 250GB drive which I plan to use as the System drive, but I’ve just not gotten around to installing everything on it yet.
My motherboard has 6 x 3Gb/s and 2 x 6Gb/s SATA ports and has an onboard RAID, using an Intel ICH10R Southbridge controller. I have a DVD drive using one of the SATA ports.
So the main questions are:
Which graphics card should I get to replace the GTX470?
What other upgrades should I be looking at to improve performance?
Your feedback would be very much appreciated.

that website shows other gtx 960's from evga and msi available if needed. if you want to spend more on a gtx 970 it is reasonably priced for its performance over the gtx 960, unlike the gtx 980.
intel has been switching cpu sockets constantly lately, so its the norm when upgrading an intel cpu it will require a new motherboard. that is the situation you are in with that motherboard. so when you decide to upgrade the cpu, you will be looking at new cpu, motherboard, and possibly even new ddr4 ram.
if you are looking for smooth editing it depends on the media codecs being used and how many fx are being applied. premiere is pretty efficient for video playback on the timeline with a good video card and fast hdds. you can add the video card and hdd raid upgrades now and see how the system works for you, then decide if and when you want to upgrade the cpu/mbd/ram.

790FX-GD70, upgrade bios to 1.7 and now raid 5 hangs.

Here are my system specs:
mobo: 790fx-gd70
cpu: quad 955 at stock
ram: gskill trident 6gb of ddr3-1600 8-8-8-21
video: xfx 4850/512 in CF
on j-micron: 2x 320g wd3200jb western digitals for raid 0 (scratch disk)
on amd raid: 4x500gb in raid 5 (data), 2x73g raid 0 (boot)
So back when I was running bios 1.4 everything works fine. I tested it and it works fine up to 1.6. So the system did work.
About two months ago, one of the 500g drives takes a poop. I send it off to rma, I get a new one back. I install it and tell the raid it is a hotspare. The raid rebuilds and life goes on. Then one month ago I try to upgrade to 1.7 so I can run windows 7. No luck. The bios hangs on the amd raid, but if I pull that hotspare/rebuild drive, it works. Call tech support. They give me 1.8beta. I try it, board cooks. No post. Rma the board. I get the board back, drop the bios back to 1.6, install xp, everything works. Jump to 1.7, same issue. Then I delete the raid config, and build a 3x500 without the problem drive. Everything works. Win7 screams, life goes on.
I tested the drive with data life guard, no problems. no smart errors. nothing. I write zeros to the drive in hopes it is a bad partition table or something. No luck.
Western digital and I agree that the problem is not the drive. The drive works fine when you downgrade the bios. Works fine with 1.7 if you turn off the raid and map it as ide.
What have I not thought of?

Fredirk: Scratch....I guess it is a reference to the old photoshop days when you would use a separate disk to hold the swap file and the files you were editing separate from the boot drive. I run torrents, irc, vmware, and keep raw dv there. The raid 5 is for anything I want to save, so it is not to much of a waste. Disks fail. I used to run seagate, but after sending back three 1tb drives to RMA I gave up on them. I transfer over 4tb per month over the internet, so that is a lot of disk io.
Hans: The tech support at MSI told me it was needed when I called them after seven would not install the first time on 1.4 (what mine shipped with). It wouldn't be the first time they were wrong. If it works for you the question is: Do you run raid? How is our setup different? 32bit or 64bit? Does your raptor run off the jmicron or the sb750? What is your mode: ide, raid, ahci?

Lost External RAID 5 after upgrading to Windows 8.1

I have a Proavio EB4FR External RAID 5 connected through the eSATA port. It worked with my Windows 7 Pro and Windows 8 Pro no problem, tonight I've upgraded to Windows 8.1. I can no longer see the RAID 5 drive.
It is detected as an "Other" device with question mark. Cannot see it in Disk Management at all.
Proavio is very bad in returning back to customers so I'm not expecting any response back from them, I was hoping that somebody here can suggest some good ideas that I can chase...
Thanks in advance,
Akin

Hi Kate,
Copying below from setupapi.dev.log;
>>> [Device Uninstall (Device Manager) - SCSI\DISK&VEN_&PROD_EXTERNALRAID\4&2F621F8A&0&050000]
>>> Section start 2014/02/02 12:54:07.432
cmd: "C:\Windows\system32\mmc.exe" C:\Windows\system32\devmgmt.msc
dvi: {DIF_REMOVE} 12:54:07.447
dvi: No class installer for 'ExternalRAID'
dvi: No CoInstallers found
dvi: Default installer: Enter 12:54:07.447
dvi: {Remove DEVICE}
dvi: InstanceID = 'SCSI\DISK&VEN_&PROD_EXTERNALRAID\4&2F621F8A&0&050000'
dvi: Query-and-Remove succeeded
dvi: {Remove DEVICE exit (0x00000000)}
dvi: Default installer: Exit
dvi: {DIF_REMOVE - exit(0x00000000)} 12:54:07.463
<<< Section end 2014/02/02 12:54:07.463
<<< [Exit status: SUCCESS]
External drive still working when I boot from my Windows 7 drive.
Thanks a lot for looking into this...

Lost RAID 5 array on upgrade to Leopard

I have a Highpoint RocketRAID 2314 controller connected to an external 4 drive RAID 5 array (1.5 terabytes). This device was working just fine with 10.4.10, and disappeared right after my upgrade to Leopard.
When I go in to Disk Utility, it says the partition map scheme is "Unformatted", it's locked, not writable, not ejectable, but does show 1.4 terabytes of total capacity. All options on this drive in Disk Utility are greyed out. I can't erase, partition, repair, etc... nothing.
I have the latest driver from Highpoint for the 2314 card, and it IS Leopard compatible.
Any idea how I can make my 1.5 terabyte array readable again? I have a lot of data on it, and dearly hope I haven't lost anything. I also tried moving the card to another slot to no avail. Anyone who has an ideas, I would very much welcome the help. I really don't care what my options are provided that I can get my data back. Thanks!

I've had terrible experiences with Highpoint. Their technical support is pretty bad and they don't go out of their way to help. I've completely lost confidence with their drivers and their software development. I've had to rebuild my RAID 5 a couple of times even though all the drives are fine. I'm constantly worrying that something like this is going to happen to me. Are there any other solutions for external drives and eSATA connectors for RAID 5??

Upgrading Controllers firmware on a degraded RAID 5 array

Hi guys
I have been told that upgrading the controllers firmware on a degraded raid array can cause a loss of configuration. I have been doing this for over 1 year and it has never happened, it sounds more like a myth to me that anything else but i would like some advice on it, if possible.
Is it true that the RAID Configuration can be lost by upgrading the RAID Controller? In theory isnt the RAID configuration kept on the hard drives?
Thanks in advance,
Pedro

No - this is not a myth. It is entirely possible to lose access to the storage either temporarily or permanently.
It is extremely bad practice to upgrade any system with a degraded component no matter how small.
Which particular array have you been upgrading?
In most arrays, the configuration is saved on multiple disks - on some arrays as a n-way mirror where n is the number of disks in the tray. However unless you know exactly what the implications are, it is extremely important that firmware updates are not carried out on degraded arrays.

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

[Solved] RAID 5 degraded after 3.13 upgrade

Hi there,
after upgrading my home server to the latest kernel 3.13 I've found out, that my RAID 5 got degraded. One of the drives has been kicked out, but I don't know why. The drive seems okay, I've also done a SMART short test, completed without any errors. The only suspicious looking error message, when upgrading to Linux 3.13 was:
ERROR: Module 'hci_vhci' has devname (vhci) but lacks major and minor information. Ignoring.
This is mdstat output:
[tolga@Ragnarok ~]$ cat /proc/mdstat
Personalities : [raid6] [raid5] [raid4]
md127 : active raid5 sda1[0] sdc1[3] sdb1[1]
5860145664 blocks super 1.2 level 5, 512k chunk, algorithm 2 [4/3] [UUU_]
unused devices: <none>
smartctl:
[tolga@Ragnarok ~]$ sudo smartctl -a /dev/sdd
smartctl 6.2 2013-07-26 r3841 [x86_64-linux-3.13.4-1-ARCH] (local build)
Copyright (C) 2002-13, Bruce Allen, Christian Franke, www.smartmontools.org
=== START OF INFORMATION SECTION ===
Model Family: Western Digital Red (AF)
Device Model: WDC WD20EFRX-68AX9N0
Serial Number: [removed]
LU WWN Device Id: 5 0014ee 2b2cd537a
Firmware Version: 80.00A80
User Capacity: 2,000,398,934,016 bytes [2.00 TB]
Sector Sizes: 512 bytes logical, 4096 bytes physical
Device is: In smartctl database [for details use: -P show]
ATA Version is: ACS-2 (minor revision not indicated)
SATA Version is: SATA 3.0, 6.0 Gb/s (current: 3.0 Gb/s)
Local Time is: Fri Feb 21 22:26:30 2014 CET
SMART support is: Available - device has SMART capability.
SMART support is: Enabled
=== START OF READ SMART DATA SECTION ===
SMART overall-health self-assessment test result: PASSED
General SMART Values:
Offline data collection status: (0x00) Offline data collection activity
was never started.
Auto Offline Data Collection: Disabled.
Self-test execution status: ( 0) The previous self-test routine completed
without error or no self-test has ever
been run.
Total time to complete Offline
data collection: (26580) seconds.
Offline data collection
capabilities: (0x7b) SMART execute Offline immediate.
Auto Offline data collection on/off support.
Suspend Offline collection upon new
command.
Offline surface scan supported.
Self-test supported.
Conveyance Self-test supported.
Selective Self-test supported.
SMART capabilities: (0x0003) Saves SMART data before entering
power-saving mode.
Supports SMART auto save timer.
Error logging capability: (0x01) Error logging supported.
General Purpose Logging supported.
Short self-test routine
recommended polling time: ( 2) minutes.
Extended self-test routine
recommended polling time: ( 268) minutes.
Conveyance self-test routine
recommended polling time: ( 5) minutes.
SCT capabilities: (0x70bd) SCT Status supported.
SCT Error Recovery Control supported.
SCT Feature Control supported.
SCT Data Table supported.
SMART Attributes Data Structure revision number: 16
Vendor Specific SMART Attributes with Thresholds:
ID# ATTRIBUTE_NAME FLAG VALUE WORST THRESH TYPE UPDATED WHEN_FAILED RAW_VALUE
1 Raw_Read_Error_Rate 0x002f 200 200 051 Pre-fail Always - 0
3 Spin_Up_Time 0x0027 164 163 021 Pre-fail Always - 6766
4 Start_Stop_Count 0x0032 100 100 000 Old_age Always - 273
5 Reallocated_Sector_Ct 0x0033 200 200 140 Pre-fail Always - 0
7 Seek_Error_Rate 0x002e 200 200 000 Old_age Always - 0
9 Power_On_Hours 0x0032 098 098 000 Old_age Always - 1954
10 Spin_Retry_Count 0x0032 100 100 000 Old_age Always - 0
11 Calibration_Retry_Count 0x0032 100 100 000 Old_age Always - 0
12 Power_Cycle_Count 0x0032 100 100 000 Old_age Always - 273
192 Power-Off_Retract_Count 0x0032 200 200 000 Old_age Always - 6
193 Load_Cycle_Count 0x0032 200 200 000 Old_age Always - 266
194 Temperature_Celsius 0x0022 115 104 000 Old_age Always - 35
196 Reallocated_Event_Count 0x0032 200 200 000 Old_age Always - 0
197 Current_Pending_Sector 0x0032 200 200 000 Old_age Always - 0
198 Offline_Uncorrectable 0x0030 100 253 000 Old_age Offline - 0
199 UDMA_CRC_Error_Count 0x0032 200 200 000 Old_age Always - 0
200 Multi_Zone_Error_Rate 0x0008 100 253 000 Old_age Offline - 0
SMART Error Log Version: 1
ATA Error Count: 306 (device log contains only the most recent five errors)
CR = Command Register [HEX]
FR = Features Register [HEX]
SC = Sector Count Register [HEX]
SN = Sector Number Register [HEX]
CL = Cylinder Low Register [HEX]
CH = Cylinder High Register [HEX]
DH = Device/Head Register [HEX]
DC = Device Command Register [HEX]
ER = Error register [HEX]
ST = Status register [HEX]
Powered_Up_Time is measured from power on, and printed as
DDd+hh:mm:SS.sss where DD=days, hh=hours, mm=minutes,
SS=sec, and sss=millisec. It "wraps" after 49.710 days.
Error 306 occurred at disk power-on lifetime: 1706 hours (71 days + 2 hours)
When the command that caused the error occurred, the device was active or idle.
After command completion occurred, registers were:
ER ST SC SN CL CH DH
04 61 02 00 00 00 a0 Device Fault; Error: ABRT
Commands leading to the command that caused the error were:
CR FR SC SN CL CH DH DC Powered_Up_Time Command/Feature_Name
ef 10 02 00 00 00 a0 08 22:17:38.065 SET FEATURES [Enable SATA feature]
ec 00 00 00 00 00 a0 08 22:17:38.065 IDENTIFY DEVICE
ef 03 46 00 00 00 a0 08 22:17:38.064 SET FEATURES [Set transfer mode]
ef 10 02 00 00 00 a0 08 22:17:38.064 SET FEATURES [Enable SATA feature]
ec 00 00 00 00 00 a0 08 22:17:38.064 IDENTIFY DEVICE
Error 305 occurred at disk power-on lifetime: 1706 hours (71 days + 2 hours)
When the command that caused the error occurred, the device was active or idle.
After command completion occurred, registers were:
ER ST SC SN CL CH DH
04 61 46 00 00 00 a0 Device Fault; Error: ABRT
Commands leading to the command that caused the error were:
CR FR SC SN CL CH DH DC Powered_Up_Time Command/Feature_Name
ef 03 46 00 00 00 a0 08 22:17:38.064 SET FEATURES [Set transfer mode]
ef 10 02 00 00 00 a0 08 22:17:38.064 SET FEATURES [Enable SATA feature]
ec 00 00 00 00 00 a0 08 22:17:38.064 IDENTIFY DEVICE
ef 10 02 00 00 00 a0 08 22:17:38.063 SET FEATURES [Enable SATA feature]
Error 304 occurred at disk power-on lifetime: 1706 hours (71 days + 2 hours)
When the command that caused the error occurred, the device was active or idle.
After command completion occurred, registers were:
ER ST SC SN CL CH DH
04 61 02 00 00 00 a0 Device Fault; Error: ABRT
Commands leading to the command that caused the error were:
CR FR SC SN CL CH DH DC Powered_Up_Time Command/Feature_Name
ef 10 02 00 00 00 a0 08 22:17:38.064 SET FEATURES [Enable SATA feature]
ec 00 00 00 00 00 a0 08 22:17:38.064 IDENTIFY DEVICE
ef 10 02 00 00 00 a0 08 22:17:38.063 SET FEATURES [Enable SATA feature]
ec 00 00 00 00 00 a0 08 22:17:38.063 IDENTIFY DEVICE
Error 303 occurred at disk power-on lifetime: 1706 hours (71 days + 2 hours)
When the command that caused the error occurred, the device was active or idle.
After command completion occurred, registers were:
ER ST SC SN CL CH DH
04 61 02 00 00 00 a0 Device Fault; Error: ABRT
Commands leading to the command that caused the error were:
CR FR SC SN CL CH DH DC Powered_Up_Time Command/Feature_Name
ef 10 02 00 00 00 a0 08 22:17:38.063 SET FEATURES [Enable SATA feature]
ec 00 00 00 00 00 a0 08 22:17:38.063 IDENTIFY DEVICE
ef 03 46 00 00 00 a0 08 22:17:38.063 SET FEATURES [Set transfer mode]
ef 10 02 00 00 00 a0 08 22:17:38.063 SET FEATURES [Enable SATA feature]
ec 00 00 00 00 00 a0 08 22:17:38.062 IDENTIFY DEVICE
Error 302 occurred at disk power-on lifetime: 1706 hours (71 days + 2 hours)
When the command that caused the error occurred, the device was active or idle.
After command completion occurred, registers were:
ER ST SC SN CL CH DH
04 61 46 00 00 00 a0 Device Fault; Error: ABRT
Commands leading to the command that caused the error were:
CR FR SC SN CL CH DH DC Powered_Up_Time Command/Feature_Name
ef 03 46 00 00 00 a0 08 22:17:38.063 SET FEATURES [Set transfer mode]
ef 10 02 00 00 00 a0 08 22:17:38.063 SET FEATURES [Enable SATA feature]
ec 00 00 00 00 00 a0 08 22:17:38.062 IDENTIFY DEVICE
ef 10 02 00 00 00 a0 08 22:17:38.062 SET FEATURES [Enable SATA feature]
SMART Self-test log structure revision number 1
Num Test_Description Status Remaining LifeTime(hours) LBA_of_first_error
# 1 Short offline Completed without error 00% 1954 -
# 2 Short offline Completed without error 00% 0 -
# 3 Conveyance offline Completed without error 00% 0 -
SMART Selective self-test log data structure revision number 1
SPAN MIN_LBA MAX_LBA CURRENT_TEST_STATUS
1 0 0 Not_testing
2 0 0 Not_testing
3 0 0 Not_testing
4 0 0 Not_testing
5 0 0 Not_testing
Selective self-test flags (0x0):
After scanning selected spans, do NOT read-scan remainder of disk.
If Selective self-test is pending on power-up, resume after 0 minute delay.
This is my mdadm configuration:
[tolga@Ragnarok ~]$ cat /etc/mdadm.conf
ARRAY /dev/md/Asura metadata=1.2 UUID=34bab60a:4d640b50:6228c429:0679bb34 name=Ragnarok:Asura
I've checked all partition tables, everything seems ok. "Error 30[x] occurred at disk power-on lifetime: 1706 hours (71 days + 2 hours)" seems to be a one-time event, which happened on 1706 hours (I don't know why; no power loss or something similar). Other than those smartctl errors, everything seems fine. I've also inspected the drive; no suspicious noises or anything else, works like the other 3 drives. Am I safe to simply re-add the drive using "sudo mdadm --manage --re-add /dev/md127 /dev/sdd1" and let it re-sync or should I flag it as failed and then re-add it to the RAID?
I am using 4x 2TB Western Digital Red drives in a RAID 5, which are about 1 year old and they ran perfectly fine until now. The server is currently shut down until this problem is fixed. I currently got a partial backup of my data (most important ones) and will make a full backup, before attempting a repair. At the moment, I'm still able to access all my data, so nothing's wrong there.
So, what do you guys think, what should I do?
Last edited by tolga9009 (2014-09-13 12:48:13)

Thank you brian for the fast reply. I've backed up all my important data and tried the command. It's not working ...
[tolga@Ragnarok ~]$ sudo mdadm --manage --re-add /dev/md127 /dev/sdd1
mdadm: --re-add for /dev/sdd1 to /dev/md127 is not possible
[tolga@Ragnarok ~]$ lsblk
NAME MAJ:MIN RM SIZE RO TYPE MOUNTPOINT
sda 8:0 0 1.8T 0 disk
ââsda1 8:1 0 1.8T 0 part
ââmd127 9:127 0 5.5T 0 raid5 /media/Asura
sdb 8:16 0 1.8T 0 disk
ââsdb1 8:17 0 1.8T 0 part
ââmd127 9:127 0 5.5T 0 raid5 /media/Asura
sdc 8:32 0 1.8T 0 disk
ââsdc1 8:33 0 1.8T 0 part
ââmd127 9:127 0 5.5T 0 raid5 /media/Asura
sdd 8:48 0 1.8T 0 disk
ââsdd1 8:49 0 1.8T 0 part
sde 8:64 0 59.6G 0 disk
ââsde1 8:65 0 512M 0 part /boot/efi
ââsde2 8:66 0 4G 0 part [SWAP]
ââsde3 8:67 0 54.6G 0 part /
ââsde4 8:68 0 512M 0 part /boot
Out of curiosity, I've compared "mdadm -E" of the corrupted and a healthy drive. Here's the output:
[tolga@Ragnarok ~]$ diff -u sdc sdd
--- sdc 2014-02-21 23:28:51.051674496 +0100
+++ sdd 2014-02-21 23:28:55.911816816 +0100
@@ -1,4 +1,4 @@
-/dev/sdc1:
+/dev/sdd1:
Magic : a92b4efc
Version : 1.2
Feature Map : 0x0
@@ -14,15 +14,15 @@
Data Offset : 262144 sectors
Super Offset : 8 sectors
Unused Space : before=262064 sectors, after=1167 sectors
- State : clean
- Device UUID : 4ce2ba99:645b1cc6:60c23336:c4428e2f
+ State : active
+ Device UUID : 4aeef598:64ff6631:826f445e:dbf77ab5
- Update Time : Fri Feb 21 23:18:20 2014
- Checksum : a6c42392 - correct
- Events : 16736
+ Update Time : Sun Jan 12 06:40:56 2014
+ Checksum : bf106b2a - correct
+ Events : 7295
Layout : left-symmetric
Chunk Size : 512K
- Device Role : Active device 2
- Array State : AAA. ('A' == active, '.' == missing, 'R' == replacing)
+ Device Role : Active device 3
+ Array State : AAAA ('A' == active, '.' == missing, 'R' == replacing)
So, I guess my only way to fix this is remove the faulty drive from the RAID, zero out the superblock and then re-add it as a new drive. Or is there any other way to fix this?
//Edit: I've used "mdadm --detail /dev/md127" and found out, that the faulty drive wasn't even listed anymore. So instead of using "re-add", I simply added it as a new drive and it's resyncing now. In about 220mins, I'll know more ! Is there a way to check for corruption after syncing the drives?
//Edit: ^ this worked. My drive probably didn't got kicked after the 3.13 upgrade, but I've simply noticed it then. The drive seems to be kicked after ~1700 hours for some unknown reason - I've now disconnected and reconnected all drives to opt out any wiring issues. Since the drive was out of sync, simply re-adding it didn't work. I had to manually add it to the array again and this caused a resync, which took around 3,5 hours. I think that's okay for a 4x 2TB RAID 5 array. Everything is working fine again, no data corruption, nothing. I'll mark it as solved.
Last edited by tolga9009 (2014-09-13 12:59:22)

RAID Utility does not work after Vista upgrade

Hi,
I have a Qosmio G30 with 2 HD 120GB each. After I upgraded to Windows Vista from Windows XP, the Toshiba RAID Utility does not work anymore. In WXp it worked OK, but in Vista there is no way I can mirror the HD. That is, the utility itself work, but the button that should say Mirror, or something like that is not shown. I have set the drives to RAID-1 in the BIOS, but no go.
Is there any way to get the software RAID to work again?

Hi,
just a little question: While installing vista, did you installed the RAID-driver at installation time? Maybe this could be the reason why RAID cannot be activated properly.
Please give some feedback, if you installed the RAID drivers for Vista during the installation..
Cheers

RAID 10 upgrading

Similar Messages

Maybe you are looking for