Raid manager and format utility inconsistency

Hi,
I have two A1000 module attached to Sun Fire 280 R with X6541A through both channels. Here is raidutil info for (c3t4d0 and c4t8d0)
# raidutil -c c3t4d0 -i
LUNs found on c3t4d0.
LUN 0 RAID 3 381620 MB
Vendor ID Symbios
ProductID StorEDGE A1000
Product Revision 0301
Boot Level 03.01.02.33
Boot Level Date 06/16/99
Firmware Level 03.01.02.35
Firmware Date 08/12/99
raidutil succeeded
# raidutil -c c4t8d0 -i
LUNs found on c4t8d0.
LUN 0 RAID 5 172345 MB
Vendor ID Symbios
ProductID StorEDGE A1000
Product Revision 0205
Boot Level 03.01.04.00
Boot Level Date 04/05/01
Firmware Level 03.01.04.68
Firmware Date 06/22/01
raidutil succeeded!
# lad
c3t4d0 1T04469376 LUNS: 0
c4t8d0 1T03843281 LUNS: 0
Those output actually reflecting the settings,
But what format command gave me is inconsistent with raid manager:
AVAILABLE DISK SELECTIONS:
0. c1t0d0 <SUN36G cyl 24620 alt 2 hd 27 sec 107>
/pci@8,600000/SUNW,qlc@4/fp@0,0/ssd@w21000004cf092afe,0
1. c1t1d0 <SUN36G cyl 24620 alt 2 hd 27 sec 107>
/pci@8,600000/SUNW,qlc@4/fp@0,0/ssd@w2100002037cd9c32,0
2. c3t4d0 <Symbios-StorEDGEA1000-0205 cyl 43084 alt 2 hd 128 sec 64>
/pseudo/rdnexus@3/rdriver@4,0
Select 2 -->partition-->print
Part Tag Flag Cylinders Size Blocks
0 root wm 0 - 43083 168.30GB (43084/0/0) 352944128
1 swap wu 0 0 (0/0/0) 0
2 backup wu 0 - 43083 168.30GB (43084/0/0) 352944128
so in format, c3t4d0 is actually reflecting c4t8d0
Anyone can give me a hint,
Thanks,
Wei

Yeah, you probably want to go through rebuilding the device paths. This amounts to removing everything in /dev/osa/dev/dsk, /dev/osa/dev/rdsk, and /devices/pseudo/rdnexus. Then performing
a reconfiguration boot.
If you're uncomfortable with this, open a service call, or look for
the string hot_add, under Infodocs and Symptoms and Resolutions in the Sunsolve search engine.
Another string is "Syncing lad and format".
Good luck!

Similar Messages

RAID Admin and Disk Utility show different sizes

Hello all,
I have tried searching through these forums for a resolution to this, but did not really find one. Here is my situation:
I have an XServe Dual G4 in a branch office. It has attached to it an XServe RAID. Last week, when I was down working in the office I added a new drive to the RAID. The lower channel on the RAID had 4 172GB drives in it, and I added a 5th and and told RAID admin to resize the RAID.
The next day, the RAID was finished resizing. RAID admin was reporting that the array was now 690GB. However, after rebooting the server and RAID multiple times, Disk Utility in OS X is still showing that the Volume on the RAID is only 517GB.
So, I have a couple of questions:
1. How is it possible that by adding a 172GB drive to a RAID 5 array that was about 520GB I ended up with an array that is 690 GB? That would imply that there is no parity (since 690 - 520 = 170 and the drive I added in was 172GB).
2. How do I get the server to see the additional space? The server is at the newest version of the OS and the RAID it as the newest version of the firmware.
Please help.
Mac OS X (10.4.8)

I've run into the same issue with a newer PPC XServe. However, after I tried to reformat, I still only show up with the orginal size, and not the new size, even after I restarted the server and XRAID.
Did you have any success with your reformat?

RAID 5 and Disk utility problems - wrong volume size for formatting

Hi ..
I seem to have an odd problem with setting up our new RAID 5 solution. We just bought the SR6600 with seperately bought Western Digital 750Gb servergrade SATA disks.
Through the console I configured the RAID set to be RAID5 with a total capacity of 2750Gb and with a volumeset of 3000Gb (4 discs capacity and 1 disc parity).
Here's the problem:
When I'm trying to format the new volume for HFS+ usage, I open Disk Utility and it shows the volume, but the capacity is only 750Gb - similar to 1 disc's capacity. I find this odd and I've searched all over the net for a solution and answer.
Please advice if anyone know of any management software, explaination, etc.
Much appreciated, thanks!

I've run into the same issue with a newer PPC XServe. However, after I tried to reformat, I still only show up with the orginal size, and not the new size, even after I restarted the server and XRAID.
Did you have any success with your reformat?

Satellite A135-SP4088: Need XP drivers for power management and Hotkey utility

Hello
I couldn't find drivers for the toshiba A135-SP4088, we bought 3 of them for the office and it's almost impossible to use with vista, so we go to XP SP2, and manage to get almost all of the drivers from other models, but i cannot find 2 utilities that work with this machine, they are:
Toshiba Power Management (the bulb in the task bar, remember?) :D
Hotkey Utility (so I can change Screen brightness, and go to hibernation (Fn+F4)
I have al the rest working, quite nicely but these two are a real problem, none of the ones I tested worked, some even crash the XP and have to go back to a previous restore point.
also, I didn't install any ACPI drivers, are they required?, which ones show I look for? since the model doesn't exist in csd.toshiba.com site.
Now, How one of the greatest notebooks manufacturers in the world can build such a nice computer without making drivers for the most widely used operating system?, can anyone explain me this because i sincerely don't understand it.
thanks a lot!.
Indkt.

Hi
The Satellite A135-SP4088 seems to be designed for the US market so you should use the Toshiba US driver page for the driver download!!!!
But why you need the Toshiba power saver for XP? The XP supports an own power options and also the hibernation option. This option must be enabled in the control panel -> power options -> hibernate tab
> didn't install any ACPI drivers, are they required
Toshiba page does not provide any special ACPI drivers. The OS uses own Microsoft drivers and the installation of any 3rd applications is not necessary!!!!
regards

Envy 4-1130US access Intel RAID Manager and reinstall back into hybrid Drive.

So I was trying to dual boot Linux and windows 7 on my HP ENVY 4. I foud the only way was to remove the raid so that there was two seperate hard drives apperently. before I did this I made the recovery disks to be able to set it back to normal once I was done my linux work.
Once I tried to recover my computer the disks say that: "this software cannot be used to recover the systems" or somthing like that. I dont know why they dont work though as I had to use 5 disks to burn them.
I want to reinstall the raid and notice you said you cant access this. So how do I go about making it back into a hybrid drive. This seems increadibly poor design that it wont let people fully use the hardware that they purchased. I have installed windows 8 myself but there is now just two different drives.
So please tell me how to fix this problem.

Ok, I just now review your PC details. your PC has a 32GB mSATA driver and another one is 500GB(as standard shipping).
raid is created for the HDD and mSATA drive to work together and give you max performance. this is customized by HP using internal utility(at the time of recovery also) and there is no option for users to configure/change RAID settinigs. no access for consumers to change RAID as playing with it may cause PC/OS issues.
i am afraid, expert users may not be able to cinfigure much on it due to no options at BIOS level to configure RAID.
Regards,
WW
“I am an HP Employee“
***** Click the KUDOS star on the left to say 'Thanks'**
Make it easier for other people to find solutions by marking a Reply 'Accept as Solution' if it solves your problem***

Best Way to Media Manage and Setup Disks?

Hi Guys,
I have a job coming up soon. It would be great to have some advice on how to manage the media properly and setup the Scratch disks.
It will be shot on RED @ 24fps, with audio recorded separately, to be synced in FCP (6.0.5 I believe).
We will have 4 internal SATA drives on the 3 Mac Pros (2 editors, 1 assist), all independent of each other, not on a SAN or other network.
What would be the best way to setup these disks as scratch disks? Partitioning, with picture dailies on one drive's partitions, then sound dailies on another drive's partitions? Then perhaps Renders on another drive's partitions, with the project itself running off the system drive?
Or perhaps a striped RAID 0 of all the 4 internal SATA drives?
I'm thinking that we may transcode the R3D Raw files to Apple ProRes 422 before syncing/cutting.
I will need to be copying media and projects between stations, to update each editor with latest dailies media, dailies bins and latest cut sequences.
Any help would be greatly appreciated!
Many thanks!

What would be the best way to setup these disks as scratch disks
Get a good drive or Raid array and format it as one drive. Then go to the System Settings and choose that drive as your Capture Scratch drive.
Partitioning, with picture dailies on one drive's partitions, then sound dailies on another drive's partitions?
No. Why do that? What is the point of partitioning and doing that? Just make folders on the Capture Scratch for what you need. FCP makes them automatically for footage you capture via Log and Capture or Log and Transfer. If there is footage you just Import...like audio files...then make a folder for the audio files and organize it like you think you should. Then Import.
Then perhaps Renders on another drive's partitions, with the project itself running off the system drive?
No...Renders can be on the same drive and partition. Where are you getting this idea that you need your media spread all over ****-and-gone? But you are right about your project file, that resides on your system drive, and you need to back that up daily onto your RAID, or other separate drive.
Or perhaps a striped RAID 0 of all the 4 internal SATA drives?
LORD no. You have 4 drive bays...one is used for the Operating System...do NOT raid that drive and then store media on it. And Raid 0 is fast, but not secure. One drive goes, the entire raid goes. Get the CalDigit RAID card and stripe THREE of the internal drives as a RAID 5...then you can get the HD ELEMENT as an external add-on if you need to expand. Or start out with an external RAID, like the Caldigit HD One, or Maxx Digital EVO HD.
I'm thinking that we may transcode the R3D Raw files to Apple ProRes 422 before syncing/cutting.
That is wise. Or edit with the proxies, then conform when you are done, saving drive space.
I will need to be copying media and projects between stations, to update each editor with latest dailies media, dailies bins and latest cut sequences.
Sort by DATE...that way you can grab all the new stuff. KEEP THE DRIVE NAME THE SAME...and keep the drive file and folder structure EXACTLY the same, and you will never need to re-connect.
Shane

[solved] power management without HAL and pm-utils

hi guys! i got rid of hal and pm-utils, but i'm having some troubles now with the powersaving settings.
i'm using hibernate-script with uswsusp tools to hibernate etc, and laptop-mode-tools with acpi for the power management, but this looks like it isnt working anymore.
for example the screen backlight wont shut down anymore when i close the lid, despite the acpi action scripts are all ok.
far more importantly the cpu fan doen't ever start!! earlier this morning the cpu hit 77°C (while it's normally 40°) but the fan didn't kick in!
what can i do?
EDIT:
wait, maybe it's just the new kernel i've installed this morning! it's some days now that i've uninstalled hal and i think i would have noticed before!
Last edited by v43 (2011-02-23 11:25:10)

disabling laptop-mode-tools temporarily solved the problem. i mean the fan is now spinning free ^^
i'll try reinstalling it or downgrading the kernel later

RAID mirror with software utility caused kernel panic every time

Using disc utility to make a mirror of 2 drives, click create and i get kernel panic and have to power off machine. if i try to start the machine with either of the two disks in it (together or individually) i get same kernel panic and have to power off.
The disks are in an external storage array (sonnet d500). I have a second storage array with raided disks in and i have raided disk inside the mac too. these all work fine..
originally 2 weeks ago i had the 2 disks working in a group of 4 disks set as a mirror of 2 striped disks. One disk in this setup failed and with this config you can never 'recover'or rebuild it - you get a degraded mirror and you can backup the data, but you must completely rebuild the raid again as the mirror of stripes never lets you add a new disk in again.period. not good.
I replaced the failed disk and rebuilt the mirror of stripes. this lasted a day until a second disk failed (all 4 were bought at same time so i was kind of expecting that to happen once one failed).
i replaced the second faulty hdd and thought about my disk usage and decided i would not make another mirror of stripes and i would make 2 mirrors instead for safe-ish storage and then transfer data to a striped raid set for editing from instead of direct from the mirror of stripes volume.
i tried to delete the raid but got a kernel panic
if i started the machine with any of the 4 disks i would get a kernel panic.
i moved the disks one by one into an older G5 running Tiger and managed to erase the raid info on 2 of them. The two new ones had some strange raid info and the Tiger machien thought there was an extra disk in the machine and would not erase or partition or allow me to destroy the raid whatever i tried.
I will be moving these now into an old XP PC to try to erase the boot records etc and erase them to be able to use them again in either mac pro or G5. painful..
so.. i ended up with 2 erased drives and have 2 new drives with dodgy raid info that causes kernel panics on the leopard machine and wont go in the Tiger machine.
The two erased drives are what ive now been trying to use in the mac pro to create a mirror - this now caused kernel panics when creating the mirror to start with and when installed in the machine at all. so i will be erasing them again in the tiger machine soon (its busy erasing with zeros another new disk that i added to the Tiger machine 2 weeks ago which seems to have some fault when raided!!! but thats another story).
so.. is anyone else having problems with creating basic mirror in 10.5.4 or is it just me??
i have a sonnet tempo e4p card with 2 external sata disk enclosures, latest firmware for the e4p card. all other previously existing raid volumes are working fine. i have one set of 2 striped disks, one set of 3 striped disks and one set of 2 stripes which are mirrored - all happy and working fine. but i cant make a new mirror of 2 disks...
I phoned Apple support and they said all raid info was kept on the disk itself and nothing on the actual machine and suggested i take the machine to an apple care centre for some tlc (although its disk i am having a problem with). since all my other disk arrays work fine i don't really want to rebuild the whole machine from scratch if i can avoid it.
Any suggestions of what i can try ??

well it turns out the new disk i bought just werent any good. my g5 powermac raid mirror issue was related to one new disk with lots of bad blocks (speed tools showed that up) so i have learnt my lesson on cheap non raid disks for raid..
am waiting on a couple of new ultrastar enterprise disks to tuen up so i can go back to the macpro and try to add a mirror again.
i am still stuck wih several new disks that i cannot format now in the macpro on leopard or on the g5 powermac with tiger.
ive tried softraid and that cant do it, speedtools pcformat util cant do it, disk utility crashes when i try to eras them and diskutil from termianl starts then doenst get anywhere and my pc sata card doesnt work so my last resort pc option still doesnt help me clear the partition map on these drives - ones that diskutility on leopard made for me - and drives which still cause kernel panics on the macpro if i put them in it..
here is what diskutil says on my g5:
/dev/disk0
#: type name size identifier
0: GUIDpartitionscheme *465.8 GB disk0
1: EFI 200.0 MB disk0s1
2: Apple_RAID 465.4 GB disk0s2
3: Apple_Boot 128.0 MB disk0s3
/dev/disk1
#: type name size identifier
0: Applepartitionscheme *233.8 GB disk1
1: Applepartitionmap 31.5 KB disk1s1
2: Apple_HFS Macintosh HD 233.6 GB disk1s3
/dev/disk2
#: type name size identifier
0: *465.4 GB disk2
/dev/disk3
#: type name size identifier
0: Applepartitionscheme *931.5 GB disk3
1: Applepartitionmap 31.5 KB disk3s1
2: Apple_HFS backup1T 931.4 GB disk3s3
/dev/disk4
#: type name size identifier
0: Applepartitionscheme *931.5 GB disk4
1: Applepartitionmap 31.5 KB disk4s1
2: Apple_HFS tempi 931.4 GB disk4s3
disk0 is the one with the bad partition info.
it thinks it has a double raid as the console shows on startup:
(both store45 and cache it thinks are on this disk - cache was my old mirror of stripes set on other machine, store45 was new name for my mirror, so seems like it hadnt deleted the original raid partition info before making new info which now kernel panics)
Jul 18 18:48:05 localhost kernel[0]: AppleRAID::degradeSet - starting the set "STORE45" (B9C48619-6B2C-4547-A01E-4864754EA7E2).
Jul 18 18:48:35 localhost kernel[0]: AppleRAID::degradeSet - starting the set "CACHE" (64F914A5-5556-4A44-AEE2-DC437868766B).
Jul 18 18:48:35 localhost kernel[0]: AppleRAID::completeRAIDRequest - error 0xe00002c2 detected for set "STORE45" (C0E139A4-2A6D-49C6-8F77-202AF7F9285D), member 50207BE5-E487-410E-8E8E-C4C4DCD2687B, set byte offset = 999527018496.
Jul 18 18:48:35 localhost kernel[0]: AppleRAID::completeRAIDRequest - error 0xe00002c2 detected for set "CACHE" (64F914A5-5556-4A44-AEE2-DC437868766B), member C0E139A4-2A6D-49C6-8F77-202AF7F9285D, set byte offset = 999527018496.
so currently i have 2 new 500gb disks which cant be partitioned back to anything at all on either machine. looks like i will have to buy a new pc to reformat them..
any suggestions of how to clear the partition map info and get them back to freespace ??

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

Format utility unable to select labeled disk

I have a system running Solaris 10 x86, booted with 64 bit kernel.
Recently, i decided to add a second hard drive to the system.
The drive is Seagate ST340014A (40GB ATA drive). I ran format and managed to fdisk, partition & label the disk, but later, i found the partition scheme ineffective and decided to re-partition the disk. Here my troubles have started.
When i ran format utiltity again, and select the drive number it gave me:
"selecting c1d0"
and freezed.
On the system console and in /var/adm/messages i had the following:
     Apr 17 19:01:20 host.tld.com scsi: WARNING: /pci@0,0/pci-ide@f,1/ide@1 (ata5):
     Apr 17 19:01:20 host.tld.com timeout: abort request, target=0 lun=0
     Apr 17 19:01:20 host.tld.com scsi: WARNING: /pci@0,0/pci-ide@f,1/ide@1 (ata5):
     Apr 17 19:01:20 host.tld.com timeout: abort device, target=0 lun=0
     Apr 17 19:01:20 host.tld.com scsi: WARNING: /pci@0,0/pci-ide@f,1/ide@1 (ata5):
     Apr 17 19:01:20 host.tld.com timeout: reset target, target=0 lun=0
     Apr 17 19:01:20 host.tld.com scsi: WARNING: /pci@0,0/pci-ide@f,1/ide@1 (ata5):
     Apr 17 19:01:20 host.tld.com timeout: reset bus, target=0 lun=0
     Apr 17 19:01:20 host.tld.com gda: WARNING: /pci@0,0/pci-ide@f,1/ide@1/cmdk@0,0 (Disk4):
     Apr 17 19:01:20 host.tld.com Error for command '<undecoded cmd>' Error Level: Informational
     Apr 17 19:01:20 host.tld.com gda: Requested Block 8065, Error Block: -27779
     Apr 17 19:01:20 host.tld.com gda: Sense Key: aborted command
     Apr 17 19:01:20 host.tld.com gda: Vendor 'Gen-ATA ' error code: 0x3
     Apr 17 19:01:20 host.tld.com genunix: ata_disk_iosetup: byte count zero
This set of messages was repeated on a regular time intervals.
The format utility neither exited nor seleted the disk. I had to kill -9 it several times in order to stop it.
I have created the filesystems on the drive, without problems and i can use it, but i can't re-partition it :(
Could someone point me to the root of the problem and/or its decision ?
Thanks in advance!

i'm encountering exactly the same problem.
One question : How does your partition table looks like ?

I would like to migrate from Aperture. What happens to my Masters which are on a RAID array and then what do I do with my Vault which is on a separate Drive please ?

I am sorry, but I do noisy understand what happens to my RAW original Master files, which I keep offline on a RAID array and then what I do with my Vault which as all my edited photos ? Sorry for such a simple question, but would someone please help my lift the fog ?
Thanks,
Rob

Dear John ,
Apologies, as I am attempting to get to the bottom of this migration for my wife ( who is away on assignment ) and I am not 100% certain on the technical aspects of Aperture, so excuse my ignorance.
She has about 6TB worth of RAW Master images ( several 100 thousand ) which, as explained, are on an external RAID drive. She uses a separate Drive as a Vault . Can I assume that this Vault contains all of her edits, file structures , Metadata, etc ?
So, step by step........She can Import into Lightroom her Referenced Masters from her RAID and still keep them there ? Is that correct ?
The Managed Files that are backed up by her Vault , are in the pictures folder of her MacPro, but not in a structure that looks like her Aperture library ? This means Lightroom will just organize all the Managed files, simply by the date in the Metadata ? Am I correct ( Sorry for being so tech illiterate ).
How do I ensure she imports into Lighgtroom in exactly the same format as she runs her workflow in Aperture ? ( Projects, that are organized by year and shoot location and Albums within those projects with sub-locations, or species , etc ). What exactly do I need to do in Aperture please to organize Managed Files to create a mirror structure of Aperture on my internal Hard Drive ?
There are a couple of points I am unsure about in regard to Lightroom. Does it work in the same way as Aperture ? Meaning, can she still keep Master Files on an external RAID and Lightroom will reference them ? If the answer is yes, how do you back up your Managed ( edited ) work in Lightroom ? ( Can you still use an external Drive as a Vault ? ) . Will the vault she uses now be able to continue to back up Managed Files post migration ?

Setting up RAID 0 and scratch disk from blank drives?

Folks,
Howdy again from NC. I've been setting up an AMD Phenom II 955 to handle PPro CS5 as well as possible, within limits. I built four of these machines for my math class, and am going to give CS5 a go on one of them before caving in and migrating my Production Premium to an i7/X58 platform. Maybe I'll get lucky and find this computer works acceptably with PPro, especially if I transcode my T2i AVCHD footage (likely Neoscene).
I put three new disks into my build yesterday and would like some pointers on setting them up, if I may ask. I have read through a number of posts on this, but don't find direct answers, unfortunately. I've never set up a RAID and want to get it right.
I have two Caviar Black drives for my RAID and a Hitachi Deskstar for my scratch disk. The Blacks are new out of the pack and the Hitachi has had zeros written to the drive. How to begin?
Anticipated issues:
* Do I need to format the drives in a certain way? I had planned on going into Disk Management and setting up a volume on each as my first move. Right now, they aren't even recognized under My Computer. Under Disk Management, all three show as unallocated.
From memory, I right click in the unallocated space and select an option for setting up the volume. Prior to this I only used straight-up drives, no RAID, and after writing zeros to a drive selected "New Simple Volume". It seems to me this is the move to make on the single scratch disk.
But how about the two RAIDed drives? We also have options to set up as "New Striped Volume" or "New Spanned Volume". If the answer is to set as as "New Striped Volume" for the RAID 0 I have planned, do I do this before or after installing the RAID software?
* My documentation for setting up the RAID on my motherboard doesn't indicate when to change my BIOS setting for the two SATA channels from IDE to RAID. Should I do this before or after running the software to set up the RAID? Do I need to go into the software setup with the two SATA channels already configured as RAID?
Right now, all SATA channels are configured as IDE.
* After getting my disks set up, I'd like to optimize my system for editing (turning off unwanted features, etc.). I've been looking all over for a link to an outside site I had bookmarked from a prior post, but lost it on re-install. Anyone recall what the favored link was? It started as a long page of instructions in simple typeface.
In the end, my disks are as follows (unless someone makes a case to use them differently):
OS/Programs - 1TB Caviar Green. Yes, I know the deal on green drives, but I needed to use this drive somewhere. I figured using it as the OS drive would be the best spot for the slowest drive. Maybe I botched this and should have used the following drive for the OS? I had transfer rates in mind and thought the Scratch drive should be faster?
Scratch - 750GB Deskstar 7K100 series. This drive was tops 18 months back when I bought it.
RAID 0 - Two 640GB Caviar Blacks (32 meg cache, twin processors). A bit older in the Black lineup, but the drive charts show them working quickly.
To ask one dumb last question, which will really show my newbieness, I use the scratch drive for page files (right? and what else?) and the RAID for holding any media to be worked upon and for encoding the final project?
I've been reading on this forum for over a month and am amazed that as I have the drives for a RAID, I can't find good links to tell me what to do. I know I am asking redundant questions here but have already spent two hours with the search engine and am only getting tangential anwers (ha! math joke).
Sorry to be asking such newbie questions all over again, but my luck with the search engine hasn't been so good of late. Maybe Bill's idea of creating a sticky section for common questions is a good idea.

about 75-80% of the systems we ship, ship with this config (others would be bigger arrays or no array)
1)OS
2) project drive 2 x raid 0
3) render to/export drive 2 x raid 0
4) back up (pick your poison)
while i cant speak to the older WDs (we have not used them for 3-4 yrs until now)
i can tell you with Seagate and now WD we have not seen the issue that applies to this inRaid 0
we are aware of the timeout issue this happens with controller cards and seagate or WD with large raid 5/6
simple answer use enterprise drives for raid 5/6
if you look at all the external raid resellers Sonnet etc they all use enterprise drives (mostly seagate)
so do we for large raids.
(drobo does not so buyer beware (green), we like to sell drobo without drives in it and use ours)
again BACK UP do not assume your raid 3/5/6/10/1 whatever is bullet proof, trust me its not
so even if you have a loss it should be at best nominal
something i dont think i have seen mentioned enough either
the single most common cause of drive failure (or any component failure) is Dirty Power!
dirty power can be spikes but are usually brown outs (very common in large older cities) or even low voltage coming into the home/office
this is the most common.
rather than a clean 120v you could see it as low as 105v
the other is being on a circuit with a large appliance.
ever see your lilghts flicker when the AC kicks on?
buy a good inline filter UPS. add 20% MORE wattage than your power supply
dont forget to add accessories LCDs, Audio interfaces, speakers/studio monitors etc.
Scott
ADK

Format utility in Solaris 10

During the preparation of my SCSA exam I found the folowing:
Place each format utility by the right function
Updates the disks VTOC ---- Partition
Reads and displays labels ---- Disk
Allows you to select a new disk ---- Label
Saves disk and slice information to a file ---- Save
Alters size slices ---- Fomat
Formats and analyzes the disk ---- Verify
My answers are:
Updates the disks VTOC --> Label
Reads and displays labels --> Verify
Allows you to select a new disk --> Disk
Saves disk and slice information to a file --> Save
Alters size slices --> Partition
Formats and analyzes the disk --> Format
But the answers in the course are:
Updates the disks VTOC --> Save
Reads and displays labels --> Label
Allows you to select a new disk --> Verify
Saves disk and slice information to a file --> Format
Alters size slices --> Partition
Formats and analyzes the disk --> Disk
So can someone tell me what the real answers are because I don't know it anymore. ;-)

I would say your answers are correct:
FORMAT MENU:
disk - select a disk
type - select (define) a disk type
partition - select (define) a partition table
current - describe the current disk
format - format and analyze the disk
fdisk - run the fdisk program
repair - repair a defective sector
label - write label to the disk
analyze - surface analysis
defect - defect list management
backup - search for backup labels
verify - read and display labels
save - save new disk/partition definitions
inquiry - show vendor, product and revision
volname - set 8-character volume name
!<cmd> - execute <cmd>, then return
quit
format>
Your instructor agrees with the answers in the course???

RAID MANAGER for X86?

I am currently working on a project , in which I am connecting an x86 W1100Z Sun server, running Solaris 10, to an A1000 through using an LM320 Dual SCSI card.
The theory is to use SAMBA to share the A1000's file systems across a network consisting of Solaris and Windows hosts.
Despite the proper connection (and termination) of the A1000 to the SCSI card , I am unable to see the A1000 from the "format" command.
I am also unable to find a copy of RAID Manager 6.22.1 which will run on an x86 architecture.
Can someone please advise on how to proceed?
Thanks.

Thanks for the info.
I know that Sun doesn't support A1000 any more, and that it is old-school (plus isn't supported on Solaris 10). However, just 'cos it ain't supported, don't mean it doesn't work!!!!
I had the same A1000 hooked onto the same W1100Z, running Windows Server 2003 and it had no problems seeing it (as a JBOD rather than a RAID, but that's not really a problem once you set up the A1000 to manage itself).
I just find it very hard to believe that there would be a curcumstance where Windows could do something / support something that Solaris doesn't!!!!
I'll try hooking the A1000 onto one on my v880's and re-configuring it as RAID 5 using RM6.22.1, then attach it to the W1100Z and see what happens there.
Any more advice would still be appreciated.

Two ssd 64gb raid 0 and two sata 320 w d hd raid 0

Hello
I am having issues getting the WD 320Gig hard drive's to run in raid 0
System see the SSD in raid 0 .......but not the WD's in windows 7..... during boot up it see the WD's in the boot up and in the raid screen
Thermal Take Dokker Case
AMD x4 970 Black clocked to 3.9GHz with OC genie lite .... just enabled it in the bio's and let it do it on it's own.
Corsair H50 water cooled
MSI 890FXA-GD70 mother board
1.80 bio's updated already
Diamond HD6850 GDDR5 1024MB Vid card
Two 4 Gig Kit's Crucial DDR3 Ballistix 1280 CL8 1.65VW/XMP
Two Micro Center Re-Badged ADATA S599 2.5 SATA SSD 64GB Hard drives running RAID 0
flashing utility has been done to the drive’s already
http://www.adata.com.tw/upload/downloadfile/ADATA%20S599%20Firmware%20Upgrade%20Tool%20V1.0.rar
Two WD 320 Gig Hard Drives Sata2 16meg's cache
Sony lightscribe DVD.
ViewSonic 27inch HDMI 1080p 100,000 to 1 contrast and 1 ms
Thank's for any help with this system... boots up to log on screen in 30 sec's and then after entering pass word it is on desk top in 10 sec's

I am not having any luck at all with this.... when I do get it to see the SSD's and I load the RAID driver at win7 driver install screen it all loads up fine and when it get's ready to go into win7 after rebooting I get a blue screen and reboot's..... blue screen flashes by so fast i can not read it...... also i took back the the Micro Center Re-Badged ADATA S599 2.5 SATA SSD HDD's 64GB and exchanged them for two OCZ Vertex 80GB SSD and swapped out the two WD 320GB for one WD Caviar Black 1TB 7,200 RPM SATA 6.0Gb/s 64meg's.... I am looking to RAID 0 the two SSD's and I just can not get it using the RAID hardware on the MB .... I have been able to do it in windows manager but it will not let me load OS on to them... I do have Win7 loaded onto the WD 1TB SATA HDD at this point hoping I could get the two SSD's in RAID 0 and did.... but only as dynamic and it will not let me load OS on to them... I had hoped to do and then delete the OS on the WD 1TB SATA hard drive
Thank you in Adv. for any assistance

Raid manager and format utility inconsistency

Similar Messages

Maybe you are looking for