RAID reconfiguration and change to GPT

Hi I have 2x HP DL 380 G6 Servers with Windows 2008 R2 Datacenter and Windows server 2012 R2 datacenter which are hyper V servers. Until now everything was fitting 2TB RAID 5 . Recently I added new HDDs and nothing above 2TB is recognized. I assume that
it is because at the beginning I formatted drive as MBR. Now I assume that I need to convert to GPT.
The question is what would you do (or even better what you did and your experience in that manner)
Online conversion MBR to GPT with some software (if you have any proposal I would be thankful)
Offline conversion - to delete and recreate raid format as GPT .......

I don't think it's possible to perform an online conversion from MBR to GPT. You are changing the structure of on-disk partitions. Backup. Re-initialize/format. Restore.
You might be able to find some third-party tool that says it can do it. But, it's your data.
. : | : . : | : . tim

Similar Messages

Completely messed up Raid-Array and Partition! How to delete and create new Raid-Array?

Hello,
I am using Ideapad U310 and tried to clean install Windows 8 and use my SSD as CACHE and Hibernate-Partition.
So, I was able to get to the Intel CTRL+I-RAID Config Menu and there I was able to create and delete my RAIDS.
Unfortunately I did not setup the Partition Size correctly, thus I only have a 50 GB Partition combined with my SSD and my HDD. This is what it looks like in the Intel Storage Manager:
As you can see both, my SSD and HDD appears, but only have small partitions on the right. And Windows 8 only recognizes this small partitions, as you can see here:
And now I am NOT able to get to the Intel RAID CTRL+I-menu before Windows starts, where I could delete this array.
My Partitions are "empty", so I dont care if anything is delete. I just want to use raid with FULL CAPACITY of my harddrives. But how can I delete the RAID Arrays and reconfigure them correctly?
When I change in the BIOS from RAID to AHCI I am able to install Windows 8 again with the whol CAPACITY of my SSD and HDD. But then I will not be able to use the RAID via Intel Storage Manager...
Hopefully someone could help me.
Thank you in advance.

Hi
Please see this thread
http://forums.lenovo.com/t5/IdeaPad-Y-U-V-Z-and-P-series/The-Guide-on-How-To-Reformat-Repartition-AN...
Hope this helps
Ishaan Ideapad Y560(i3 330m), Hp Elitebook 8460p!(i5-2520M) Hp Pavilion n208tx(i5-4200u)
If you think a post helped you, then you can give Kudos to the post by pressing the Star on the left of the post. If you think a post solved your problem, then mark it as a solution so that others having the same problem can refer to it.

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

K8N DIAMOND: New Raid array and old HD... I'm going crazy!!! Please

Hi guys
First, sorry for my poor english...
My problem is:
I bought two Raptor 36 Gb for my new raid array.
I have my old HD Hitachi 250 Gb connected on sata 1.
I connected my two raptor, on sata 3 and 4, I enabled all sata port and raid config for ports 3 and 4.
I restart PC, typed F10 and set a stripe array with two raptor. All run ok...
Restarted and boot with my copy of WinXP with SP2 and NF4 raid drivers.
Installation found my array and my Hitachi;
Hitachi with 4 partitions; C (os), D (driver), E (films), F (music)
I create one partitions on my raid array, and it takes I: letter... So I formatted and start to copy os...
Errors occurs when, restarting pc and resetting the boot to Hard disk (the order of booting is 1 - nvidia array, 2 - hitachi 250 gb), just before loading installation, It shows a black screen with an error: "there is an error in your hard disk bla bla bla.. try to control your connection or connect to windows help....bla bla..."
The Raid array works properly, infact I try to disconnect my Hitachi from sata port 1 and all installation works (I'm writing from Win xp on the raid array).
I tried to connect the hitachi on port 1 of silicon image controller.... same error..!!
I'm desperate... I have all my life on my hitachi...
I think that there's a sort of conflict in drive letter assignement... I cant find a solution ..
PLEASE HELP ME!!!

Glad it worked, I had a feeling it would.
Quote
One question for you.. on G: partition, there's a directory called "Windows", do you suggest me to format this partition??
You can format it if you want to free up space, but unless you moved things around the My documents folder and everything in it is on that partition, along with anything you might of had on the old desktop during that Windows install. You might have something you want there, I usually leave mine for a few month, and figure out if I have everything I need.
Quote
What I have to do, if I need to reinstall WIn XP on first partition of raptor array??
Things should be fine now as Windows marked the Hitachi drive as G. You should be able to reinstall without issue. But if you have a lot of sensitive info on the Hitachi, I would always disconnect the Hitachi if doing a fresh install. Once windows is done installing, hook it back up. But next time you shouldn't have to reconfigure NVRAID after disconnecting and reconnecting.

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

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

Copy command fails after installing Raid system and new user accounts

Any help is appreciated. We installed a Raid to an existing Xserve at our school. We have created new accounts on the server.All other commands such as observe, control, sending messages and so works OK.
When I try to copy files, pictures, and so on... it immediately fails. It gives me no explanation or anything.
Any help?

Hi Tilly,
We had this same exact problem at our school. Copying to network users always failed, everything else worked fine.
We changed the owner of the Sharepoint where the student accounts reside from our Administrator user to 'Root'
We changed this through Workgroup Manager -> Sharing, selected the Sharepoint in the left column, clicked on the Access tab and changed the owner to 'root' and click save.
Also found this link:
http://lists.apple.com/archives/remote-desktop/2007/Nov/msg00009.html
Hope this helps!

Errorlog filling with changed language setting and changed database context messages

On one of my servers, the ERRORLOG is filling with messages for "Changed language setting to..." and "Changed database context..." for every single connection. They are generated for any kind of connection--such as Management Studio.
How did this get turned on? How do I suppress the messages in the errorlog? This is the only server that's having the problem.
Example at the bottom.
SQL is: SQL 2008 R2 SP2
Trace flags set on this server are 3226, 1118, 1117
Date,Source,Severity,Message
01/24/2014 11:23:14,spid65,Unknown,Changed language setting to us_english.
01/24/2014 11:23:14,spid65,Unknown,Changed database context to 'master'.
01/24/2014 11:23:14,spid64,Unknown,Changed language setting to us_english.
01/24/2014 11:23:14,spid64,Unknown,Changed database context to 'master'.
01/24/2014 11:23:13,spid64,Unknown,Changed language setting to us_english.
01/24/2014 11:23:13,spid64,Unknown,Changed database context to 'master'.
01/24/2014 11:23:13,spid55,Unknown,Changed language setting to us_english.
01/24/2014 11:23:13,spid55,Unknown,Changed database context to 'master'.
01/24/2014 11:23:11,spid55,Unknown,Changed language setting to us_english.
01/24/2014 11:23:11,spid55,Unknown,Changed database context to 'master'.
01/24/2014 11:23:05,spid61,Unknown,DBCC execution completed. If DBCC printed error messages<c/> contact your system administrator.
01/24/2014 11:23:05,spid61,Unknown,The error log has been reinitialized. See the previous log for older entries.
01/24/2014 11:23:05,spid61,Unknown,Logging SQL Server messages in file 'F:\SysDB\Program Files\Microsoft SQL Server\MSSQL10_50.ETL\MSSQL\Log\ERRORLOG'.
01/24/2014 11:23:05,spid61,Unknown,Authentication mode is MIXED.
01/24/2014 11:23:05,spid61,Unknown,System Manufacturer: 'HP'<c/> System Model: 'ProLiant DL580 G5'.
01/24/2014 11:23:05,spid61,Unknown,Server process ID is 20096.
01/24/2014 11:23:05,spid61,Unknown,All rights reserved.
01/24/2014 11:23:05,spid61,Unknown,(c) Microsoft Corporation.
01/24/2014 11:23:05,spid61,Unknown,Microsoft SQL Server 2008 R2 (SP2) - 10.50.4000.0 (X64) <nl/>
Jun 28 2012 08:36:30 <nl/> Copyright (c) Microsoft Corporation<nl/>
Developer Edition (64-bit) on Windows NT 6.1 <X64> (Build 7601: Service Pack 1)

Here's the relevant parts of the startup from today. I snipped out some specific database info (noted with ...), but the main events are still there.
... [Several lines of changed database context/changed language]
01/24/2014 10:03:33,spid52,Unknown,Changed database context to 'master'.
01/24/2014 10:03:33,spid51,Unknown,Changed language setting to us_english.
01/24/2014 10:03:33,spid51,Unknown,Changed database context to 'master'.
01/24/2014 09:59:44,spid6s,Unknown,Recovery is complete. This is an informational message only. No user action is required.
01/24/2014 09:59:40,spid11s,Unknown,Service Broker manager has started.
01/24/2014 09:59:39,spid11s,Unknown,The Database Mirroring protocol transport is disabled or not configured.
01/24/2014 09:59:39,spid11s,Unknown,The Service Broker protocol transport is disabled or not configured.
01/24/2014 09:59:35,spid28s,Unknown,CHECKDB for database 'userdb' finished without errors on 2014-01-19 12:19:29.640 (local time). This is an informational message only; no user action is required.
01/24/2014 09:59:25,spid10s,Unknown,Starting up database 'tempdb'.
01/24/2014 09:59:25,spid14s,Unknown,CHECKDB for database 'msdb' finished without errors on 2014-01-19 12:20:23.410 (local time). This is an informational message only; no user action is required.
01/24/2014 09:59:25,spid16s,Unknown,CHECKDB for database 'userdb' finished without errors on 2014-01-19 12:21:44.847 (local time). This is an informational message only; no user action is required.
01/24/2014 09:59:23,Server,Unknown,SQL Server is now ready for client connections. This is an informational message; no user action is required.
01/24/2014 09:59:23,Server,Unknown,The SQL Server Network Interface library could not register the Service Principal Name (SPN) for the SQL Server service. Error: 0x2098<c/> state: 15. Failure to register an SPN may cause integrated authentication to
fall back to NTLM instead of Kerberos. This is an informational message. Further action is only required if Kerberos authentication is required by authentication policies.
01/24/2014 09:59:23,spid10s,Unknown,Clearing tempdb database.
01/24/2014 09:59:23,spid31s,Unknown,Starting up database 'userdb'.
01/24/2014 09:59:23,spid14s,Unknown,Starting up database 'msdb'.
01/24/2014 09:59:23,spid10s,Unknown,CHECKDB for database 'model' finished without errors on 2014-01-19 12:20:20.393 (local time). This is an informational message only; no user action is required.
01/24/2014 09:59:23,spid11s,Unknown,A new instance of the full-text filter daemon host process has been successfully started.
01/24/2014 09:59:23,Server,Unknown,Dedicated admin connection support was established for listening locally on port 53067.
01/24/2014 09:59:23,Server,Unknown,Server is listening on [ 127.0.0.1 <ipv4> 53067].
01/24/2014 09:59:23,Server,Unknown,Server is listening on [ ::1 <ipv6> 53067].
01/24/2014 09:59:23,Server,Unknown,Server named pipe provider is ready to accept connection on [ \\.\pipe\MSSQL$ETL\sql\query ].
01/24/2014 09:59:23,Server,Unknown,Server local connection provider is ready to accept connection on [ \\.\pipe\SQLLocal\ETL ].
01/24/2014 09:59:23,Server,Unknown,Server is listening on [ 'any' <ipv4> 50537].
01/24/2014 09:59:23,Server,Unknown,Server is listening on [ 'any' <ipv6> 50537].
01/24/2014 09:59:23,Server,Unknown,Server is listening on [ 'any' <ipv4> 5427].
01/24/2014 09:59:23,Server,Unknown,Server is listening on [ 'any' <ipv6> 5427].
01/24/2014 09:59:23,Server,Unknown,A self-generated certificate was successfully loaded for encryption.
01/24/2014 09:59:22,spid6s,Unknown,Server name is 'MYSRV\ETL'. This is an informational message only. No user action is required.
01/24/2014 09:59:22,spid10s,Unknown,Starting up database 'model'.
01/24/2014 09:59:22,spid6s,Unknown,The resource database build version is 10.50.4000. This is an informational message only. No user action is required.
01/24/2014 09:59:22,spid6s,Unknown,Starting up database 'mssqlsystemresource'.
01/24/2014 09:59:22,spid6s,Unknown,SQL Trace ID 1 was started by login "sa".
01/24/2014 09:59:21,spid6s,Unknown,FILESTREAM: effective level = 0<c/> configured level = 0<c/> file system access share name = 'ETL'.
01/24/2014 09:59:21,spid6s,Unknown,SQL Server Audit has started the audits. This is an informational message. No user action is required.
01/24/2014 09:59:21,spid6s,Unknown,SQL Server Audit is starting the audits. This is an informational message. No user action is required.
01/24/2014 09:59:21,spid6s,Unknown,Resource governor reconfiguration succeeded.
01/24/2014 09:59:21,spid6s,Unknown,CHECKDB for database 'master' finished without errors on 2014-01-19 12:20:10.410 (local time). This is an informational message only; no user action is required.
01/24/2014 09:59:21,spid6s,Unknown,Recovery is writing a checkpoint in database 'master' (1). This is an informational message only. No user action is required.
01/24/2014 09:59:21,spid6s,Unknown,1 transactions rolled back in database 'master' (1). This is an informational message only. No user action is required.
01/24/2014 09:59:20,spid6s,Unknown,Starting up database 'master'.
01/24/2014 09:59:20,Server,Unknown,Node configuration: node 0: CPU mask: 0x000000000000ffff:0 Active CPU mask: 0x000000000000ffff:0. This message provides a description of the NUMA configuration for this computer. This is an informational message only. No user
action is required.
01/24/2014 09:59:20,Server,Unknown,Lock partitioning is enabled. This is an informational message only. No user action is required.
01/24/2014 09:59:20,Server,Unknown,Using dynamic lock allocation. Initial allocation of 2500 Lock blocks and 5000 Lock Owner blocks per node. This is an informational message only. No user action is required.
01/24/2014 09:59:20,Server,Unknown,Using locked pages for buffer pool.
01/24/2014 09:59:19,Server,Unknown,Large Page Allocated: 32MB
01/24/2014 09:59:19,Server,Unknown,Large Page Granularity: 2097152
01/24/2014 09:59:19,Server,Unknown,Large Page Extensions enabled.
01/24/2014 09:59:19,Server,Unknown,Detected 16 CPUs. This is an informational message; no user action is required.
01/24/2014 09:59:19,Server,Unknown,SQL Server is starting at normal priority base (=7). This is an informational message only. No user action is required.
01/24/2014 09:59:19,Server,Unknown,Registry startup parameters: <nl/>
-d F:\SysDB\Program Files\Microsoft SQL Server\MSSQL10_50.ETL\MSSQL\DATA\master.mdf<nl/>
-e F:\SysDB\Program Files\Microsoft SQL Server\MSSQL10_50.ETL\MSSQL\Log\ERRORLOG<nl/>
-l F:\SysDB\Program Files\Microsoft SQL Server\MSSQL10_50.ETL\MSSQL\DATA\mastlog.ldf<nl/>
-T 3226<nl/> -T 1118<nl/>
-T 1117
01/24/2014 09:59:19,Server,Unknown,This instance of SQL Server last reported using a process ID of 1060 at 1/24/2014 9:57:16 AM (local) 1/24/2014 3:57:16 PM (UTC). This is an informational message only; no user action is required.
01/24/2014 09:59:19,Server,Unknown,Logging SQL Server messages in file 'F:\SysDB\Program Files\Microsoft SQL Server\MSSQL10_50.ETL\MSSQL\Log\ERRORLOG'.
01/24/2014 09:59:19,Server,Unknown,Authentication mode is MIXED.
01/24/2014 09:59:19,Server,Unknown,System Manufacturer: 'HP'<c/> System Model: 'ProLiant DL580 G5'.
01/24/2014 09:59:19,Server,Unknown,Server process ID is 20096.
01/24/2014 09:59:19,Server,Unknown,All rights reserved.
01/24/2014 09:59:19,Server,Unknown,(c) Microsoft Corporation.
01/24/2014 09:59:19,Server,Unknown,Microsoft SQL Server 2008 R2 (SP2) - 10.50.4000.0 (X64) <nl/>
Jun 28 2012 08:36:30 <nl/> Copyright (c) Microsoft Corporation<nl/>
Developer Edition (64-bit) on Windows NT 6.1 <X64> (Build 7601: Service Pack 1)

Apple Xserver Raid, 1 raid mounts and the other raid does not mount

Apple Xserver Raid, 1 raid mounts and the other raid does not mount but all the lights on the drives are green

Kind of lacking in detail there...
Did the other volume mount in the past? and it stopped working? When? What changed?
What does Raid Admin.app have to say about it?
Does it see the drives? a RAID set on those drives? A link on the fiber channel connection?

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 and 3TB Drives only show 2.2 TB

I tried a 3TB Seagate Barracuda XT drive in the July 2010 Mac Pro (and a Jan 2008 Mac Pro) on the RAID Card that came with the machines (so one is the RAID Card now shipping) and both show a maximum of 2.2 TB with a 3TB drive.
I'm curious if anyone else has tried this with different results. Any luck in getting the RAID Card to see the full 3TB in the drives?
By the way, without the RAID Card, the Mac (OS 10.6.4) sees the full 3TB, but not with it.
Anyone else seeing this?

Okay. Seems Apple didn't plan for or certify 3TB.
However, Apple doesn't support using 3rd party drives. Some do, and in some situations, drives you would think work don't, or they work but only briefly.
When I said read FAQ I was thinking of all the points like this:
Question: *Which drives does Apple support for the Mac Pro RAID Card and the Xserve RAID Card?*
Answer: Only Apple SATA drives and Promise 450GB SAS Drive modules sold through the Apple Store are supported for use with the Mac Pro RAID Card (Early 2009) and the Xserve RAID Card (Early 2009).
Apple 300GB SAS Drive modules are supported with the Mac Pro RAID Card (Late 2007) and Xserve RAID Card (Early 2007).
Drives must be either all Serial ATA (SATA) or all Serial Attached SCSI (SAS) drives. SSD drive modules are not recommended for the Apple RAID Card because these drives use their own on-disk cache and cannot take advantage of the protection provided by the battery-backed cache on the RAID card.
http://support.apple.com/kb/HT1346#faq8
http://www.apple.com/support/macpro/
Apple Knowledge Base: recent changes:
http://support.apple.com/kb/index?page=articles

Catching (and changing) transparent tooltips maps is a pain.

If i create a tooltip that's just acting as an image map, or helper, i don't want to have the rectangle shown. Wether i put the rectangle with color = none, or opactiy = 0, it's just becoming impossible to catch in my layout and change position.
Since we don't have a mechanism as in inDesign to catch "next object" in a group, or a list of everything that's on a page (layer panel), i don't see a practical way to do this.

With the latest version of Muse, you will see that the images used as the tooltip triggers and targets have changed and reconfigured. They no longer resemble the video http://tv.adobe.com/watch/muse-feature-tour/muse-define-trigger-and-target-interactions/ and function differently? I'm applying an image onto a target and trying to place these into position in my design. I cannot get the both as a group to show within states or disappear together ungrouped? I've tried pasting and inserting elements with no luck. I used these prior to the new version of Muse without difficulty unless made transparent and trying to relocate them which is next to impossible. Then I find the target area expands to a larger size than the image I'm using and again they will not disappear or reappear in unison. I can't find a way to figure these out as in paint me a picture cause I surely don't understand their functionality.

Onboard promise raid-controller and promise add-on sata-controller

Can anybody help me with the following problem.
I have 4 SATA hard disks.
2 Western Digital Raptors and 2 Seagate Barracuda V of 80 gig.
I would like to do the following:
I would like to put the 2 raptors in raid-striping for my OS on my onboard raid-controller and use the 2 barracuda's for data and connect them the promise add-on card (promise ultra150 tx2).
I have the following with this config: the raid-controller is no problem but when i connect a hard-drive to the add-on card, windows won't boot anymore and i have no possibility in the bios to choose to boot from the raid-controller.
I'm using an MSI K7N2G-ILSR motherboard with the latest MSI-bios.

I'm having the same problem but I can't switch my drives. I have my 2 200 gig maxtors full of data that i can't let go of. I've installed a new silicon images pci card with 2 sata channels. if i hook up the drives both bios recognize the drives correctly but it tell me invalid system disk. pretty sure that it's reading the pci card, not seeing a os installed and not even looking at my onboard controller. I was told that i can change irq priority, but i can't get it right or it doesn't work. I can install os on pci card but would really rather not. I'm very happy with the setup i have for once.
msi k7n2 delta promise 376 onboard controller

SATA/RAID connecting and applying

hi,
i've just bought a whole new computer, MSI motherboard VIA K8T800 neo series (MS6702 v1.0).
i'm having problems setting my SATA hdd.. from the manual i see that there should be some options during bootup where i enter the BIOS and activate the onboard option to enable using the SATA.. my problem is that i can't find the proper option under the Integrated Peripherals ->OnBoard PCI Controllers, it only shows the LAN and AC97 options with no RAID or SATA option to enable.
i've checked the connectors and everything is connected just fine, tried the other connector for the SATA hdd and changed between the power supply sockets.. no results :(
should i try to update the BIOS to some newer version, and if so which one do you recommend upon due to yer experience.
appreciated.

i've already did that :(
im however not sure about my SATA hdd if it's SATA I or II .. i got this one without a jumper, im not sure if its missing (and its SATA II) or if its SATA I and it should have nothing with the jumper.
from my last post ''I do have the VT8237 SATA enabled (also the PATA) but I still don't see any SATA hdd detected''
the scan doesn't detect any hdd upon booting. shouldnt it find the hdd after enabling the option from the BIOS?
ive tried approxmatily everything that could be the problem and i still cant find out what wrong !

RAID reconfiguration and change to GPT

Similar Messages

Maybe you are looking for