Storage 3310 RAID array as JBOD

Hi,
I have Storage 3310 RAID array. I want to use it as JBOD, half of the disks connected to
one controller channel, the other half to other controller channel.
I connected cables as it's is shown on FIGURE 4-16 (http://docs.sun.com/source/816-7290-19/ch04_cable.html#pgfId-999796)
but without expansion unit and with one host.
Seems that's not ok since disks are not recognize by format command.
There was RAID 5 was configured. I erased it. What should be configured at storage?
Thanks
Mario

AFAIK that's not the question. The question is can we convert (from a H/W standpoint) a RAID array to JBOD. And the answer is no.
You can use NRAID, but this remains a 3310 RAID array. BTW, please have a look at http://dlc.sun.com/pdf/817-3711-17/817-3711-17.pdf page 100:
"Note NRAID does not provide data redundancy. The NRAID option that appears
in some firmware menus is no longer used and is not recommended. "
Nicolas

Similar Messages

Converting Storedge 3310 RAID unit to act as JBOD?

Hello, I have been struggling with this configuration, any advice is appreciated.
I have 4 x Storedge 3310 RAID units each with it own controller. I have 1 x Linux host and 1 x HBA in the host, with ch0 and ch1. I want to be able access to all 4 Storedge 3310s. Normally if this were 2 x Storedge 3310 RAID + 2 x JBOD then I just connect each RAID unit to a JBOD then each RAID to ch0 and ch1 respectively to the host. Instead what I have is 4 x Storedge 3310 RAID units, is there a way to convert two of the Storedge 3310 unit to make it act exactly like a JBOD? So that I can daisy-chain them to make them all accessible to the host?
Or adding another HBA card to the host is the only option?
thank you.

What is the difference between the host/drive channel? Besides the fact that they are their for connecting to disk drive or to host. Because lets say I connect the first RAID controller to the second one, host-to-host configuration from one RAID to another, will the host see this transparently?
By the way, I tried the JBOD method you mention so basically just connect one of the RAID unit to the other one just as a JBOD and the RAID controller can see the disks on a difference channel but only half of the disk because the RAID I/O actually have internal conneciton to half of the disk, while the other half is jumper.

Support for 3310 scsi array in 2-node cluster

is the 3310 scsi array supported in a 2-node cluster
for oracle HA

Yes , Se3310 jbod or h/w raid is supported in
a 2 node cluster . Se3310 jbod behave like a D1000 .
For se3310 raid , performing LUN creation and mapping .

Raid array being seen as 2 individual drives

Hi. Here is the issue as posted in other places. Still searching for the answer to this one.
Specs:
K7n2 delta2 platinum with b50 bios
2x1gb crucial pc3200 2.5cas ram
AMD Barton 2500
2 x 160gb 7200rpm 8mb cache SATA Samsung Hdd's
Thermaltake 430w psu
Gainward fx5700 ultra graphics
OS's: original xp corp, slipstreamed xp corp sp2
raid drivers: nvraid.sys v4.27, 5.10, 5.11 (also the needed nvatabus.sys with those)
I am NOT overclocked.
fsb 166
1:1 ram/cpu
no spread spectrum or other garbage
ddr400 patch disabled
PSU gives presumably stable reading (according to what I see), with amperage ratings above the required.
checked and rechecked cables for bad ones
ran mulitple scans on drives, all come up drives OK
I HAVE installed into Raid 0 already, this is not an issue of hardware failure as far as I am concerned.
So here is the scenario
I have properly set up the array, using correct bios settings and the raid setup utility, for a raid 0 array of those 2 hdd's listed. When booting into xp, either version, I have used all 3 of the driver sets listed. I have been reinstalling to do some performance tests on different configurations.
Anyway, for the last few nights I have been trying to get the windows setup to see the raid 0 array as one 300gb drive. It does not, no matter what I try. It sees them as 2 drives, each being 160gb (or thereabouts). These drives are matched, same firmware, same lot, so that should not be an issue.
I have used numberous tools to delete the mbr on the drives, both in an array and as single drives. I have done the same as well as tried an install and formatted each drive individually, still the same effect when the raid array is recreated.
Basically, I can find no good reason why the array is seen as individuals and not as an array. It is interesting to note, that even though xp setup sees the the array as 2 drives, I can complete the text based portion of setup. However, rebooting to start the GUI portion of setup, it will not boot. Obviously becuase the bios has the controller as the nvraid controller and it is supposed to be a raid 0 array, so I expected that.
Short of rewriting the mbr, either by deleting it or by changing each drive by formatting/partitioning/installing an OS on them, I cannot think of how to fix this. I know the drives and xp cd's work because I have already installed with them.
I understand what to do in the bios portion, and in the raid setup utility portion. I know that I can boot into windows as a single drive and use the nvraid tool to set it up, but that is not the way it should be, and that is not the way I am going to learn WHY this is happening.
Roger that. First set in bios enable raid (in this bios I have to enable IDE array, then choose which controller to actually enable raid on, which happens to have been SATA 1 & 2).
Second, upon reboot, I use the F10 key to enter raid utility. Then, set to striping, set stripe size (which was one of the things I am testing), and add the drives to the array. Next step is to create it. It asks to clear disc data, and it is done.
Have deleted that array as well as just cleared it. Have deleted it and reboot and rebuild it. Have deleted it, reboot, change bios back to non-raid, reboot. Reboot. Change bios back to raid enabled. Reboot. Rebuild array in raid utility, reboot. Run setup, only see 2 hdd's, not one array.
Umm, yep, that is about it.
More to the story now.
From some other posts I tried this.
1. destroy array. reboot. disable raid in bios. reboot. verify sata's visible as singles in bios.
2. power down. pull plugs on sata's. reboot. no drives visible.
3. pull power. jumper clear cmos. wait 60 seconds. re-pin jumper. power up.
4. verify no drives. verify default bios settings. all is good
5. plug drives in. reboot. seen as singles. erase mbr on both drives. reboot
6. enable raid in bios, and choose sata 1 & 2 as "enabled". reboot.
7. use F10 key to setup raid. Here is the interesting part. Even though I deleted the array prior to all of this, and removed the drives to force an ESCD update, and cleard the cmos with the board jumper, and then before raid was enabled, cleared the mbr on the drives, when I started the raid utility, the array was already set up. That is the problem, whatever that is. I have read snippets where it is claimed that this chip or bios or whatever stores some kind of a table on this stuff, but this is a bit out of hand.
That combination, IMO, should have cleared anything out. But, the saga continues.
Thanks for you help BWM
[Edit] BTW, I have finally found a utility that will see a raid array and allow me to clear the arrays mbr. It is called SuperFdisk and is at ptdd.com. So far the only one that see's the 2 drives as 1.
Yeppers.
Started with v5.10 which came on a floppy with the mobo. Told setup to use both, nvatabus.sys and nvraid.sys. Even switched which one of the 2 I picked first, just to see.
Same thing with v4.27 and v5.11. Also tried it with just the nvraid.sys and just the nvatabus.sys (which obviously does squat for raid, lol)
Trying some new things now. Post in a little bit.
I am officially at 'Wit's End'.
Here is what I have tried now.
1.pull drive cables. pull power. jumper clear cmos. wait. power up. no drives
2.plug sata 1 in. boot. drive detected.
3.boot to command.com, run MHDD, which is a nice russian utility similar to Spinrite. Used this to clear the mbr at hardware level, and do a complete erase.
4. reboot to command.com. run superfdisk. erase mbr.
5. pull plug on sata 1, and plug in sata 2 with sata 1 cable. repeat the erasure steps listed above.
6. pull plug on sata 2, no sata plugged in. reboot
7. change bios to raid enable on sata 1 & 2. power down
8. plug in sata 1 & 2. power up.
9. inspect raid utility. no listing of any arrays. reboot
10. in raid utility, build array. did NOT clear discs. reboot
11. attempt install. single drives found again (used both drivers).reboot
12. in raid utility, optioned to CLEAR discs (funny, rebuild option is never valid).reboot
13. attempt install, both drivers, still seen as 2 individuals.
Things to note. When creating an array when presumably there are none, it assigns the raid array an ID of 2. Upon reboot, the ID is now 1. Don't know what difference that makes.
Also, tried the install listed above with APIC functionality both off and on. Also, when on, set MPS to both 1.1 and 1.4. In addition to this, each variant I tried manual HAL layers of, in this order, ACPI (the one that actually spells ACPI out), ACPI Uniprocessor, MPS Uniprocessor, and let it choose it for me.
So, here I sit in a barca-lounger at 'Wit's End', with a warm cup of java and a dinner mint.

Here is the final product on the floppy disk that I used to successfully install a stable raid 0 on the MSI K7N2 Delta 2 Ultra 400 Platinum ms-6570e motherboard.
On root of floppy, from driverset 6.70. (after much testing, I used driver pack 5.10 for my nic and smbus. I used the realtek sound drivers off the cd for audio. I have used every driver pack I could find, and while some did offer better I/O or read/write latency, this set in general provided the most stable environment. The only drivers I used were these floppy drivers for SATA, the nic and smbus just mentioned, the sound just mentioned, and updating the nvide drivers to mside drivers)
<from sataraid directory>
disk1
idecoi.dll
nvatabus.sys
nvraid.cat
nvraid.inf
nvraid.sys
nvraidco.dll
<from legacy directory>
nvata.cat
nvatabus.inf
I used the txtsetup.oem from the sataraid directory, but edited this:
[Files.scsi.RAIDCLASS]
driver = d1,nvraid.sys,RAIDCLASS
inf = d1,nvraid.inf
dll = d1,nvraidco.dll
catalog = d1,nvraid.cat
[Files.scsi.BUSDRV]
driver = d1,nvatabus.sys,BUSDRV
inf = d1, nvraid.inf
dll = d1,idecoi.dll
catalog = d1, nvraid.cat
To this:
[Files.scsi.RAIDCLASS]
driver = d1,nvraid.sys,RAIDCLASS
inf = d1,nvraid.inf
dll = d1,nvraidco.dll
catalog = d1,nvata.cat
[Files.scsi.BUSDRV]
driver = d1,nvatabus.sys,BUSDRV
inf = d1, nvatabus.inf
dll = d1,idecoi.dll
catalog = d1, nvata.cat
Now, it is important to note that I installed or attempted to install at least 50 times. Bare minimum. I noticed when I use this custom driver disc that in the GUI portion of setup, XP asks me for files from the disc. I tried lot's of different things to alleviate this, and denied some of them.
One thing that really bugged me was that the bios would see my #2 optical, slave on secondary IDE channel. A dvd/rw drive. And I could even start the setup from it. But, once I got about 3/4 through copy file stage on text setup portion, I would hang. Becuase the drive was no longer accessible. Booting from the master would get me to the desktop, but the slave optical was nowhere to be found. Updating the ATA/IDE controller to the ms ide drivers would get it visible, but I kept having issues with stability after I did that.
The most stable method I found was to use my above listing of driver files for the floppy, and when in GUI mode setup asks about NVCOI.DLL, I skipped it, ignored it, and did not let setup install it. That actually got me to the desktop, with access to the slave optical as a "removable drive". It even knew what the hardware was. It just could not access it. On a reboot however, back to not seeing it. This method however did allow me to update the nvide driver with the mside driver with no stability issues. So, for me it was a raving success.
Here are some links regarding the SATA RAID driver workaround:
http://66.102.7.104/search?q=cache:jHbX5bNfGx4J:www.msfn.org/board/lofiversion/index.php/t51140.html+nforce2+nvraid.sys+ms+ide&hl=en&client=opera
http://www.aoaforums.com/frontpage/index.php?option=content&task=view&id=292&Itemid
http://66.102.7.104/search?q=cache:J9UhG2Kd8W4J:www.short-media.com/forum/showthread.php%3Ft%3D32751+xp+2+sata+raid+0+seen+as+individual&hl=en&client=opera
Early on one problem I noticed was that in text setup mode of xp installation, there were long pauses that I have never seen before. I noticed that with both ide and sata installs. Also I noticed that when booting there was a really long pause when the xp logo is first seen in a sort of dim state till when it became bright and vivid.
Come to find out that this is a more or less typical scenario. Most instances that I read about were all pointing to the nvide driver. So, I found if I just updated the PATA controller to the standard ms ide driver, that went away and the whole system ran better.
It took awhile to figure out that if you install a driver with the nForce2 chip, you had to uninstall it or you will have issues. Herein was the main problem I encountered with the SATA RAID installs. The nvatabus.sys driver was required for an SATA RAID install. Omitting the ata driver was impossible. And for awhile I had no success updating the ms ide driver once I was to the desktop without major instability. Here are some links regarding the drivers for this chipset:
http://www.nforcershq.com/forum/latest-drivers-for-nforce-3-vt60240.html
In my browsing I came across some pretty interesting articles regarding ACPI. One thing I started playing with was the different HAL layers that xp installs on it's own, vs. me picking one manually (F5 key). I must have started the setup at least 50 times to figure out this: that this particular board does not give me the bios settings to install xp with anything but the ACPI Uniprocessor Hal. For instance, the MPS Uniprocessor HAL is much more responsive, but it lacks the IRQ's needed for setup to see the raid array. I booted to each one, some locking the system up, some booting OK. The one I found the best performance with early on was the one that spells out ACPI, not just initialized. (sorry, I don't want to look it up).
I seemed to be getting closer, but I could not find the needed bios settings to properly manage my ACPI, and since I was trying for RAID, I could not use the one that did work. Here is a link for that kind of stuff.
http://www.fceduc.umu.se/~jesruv98/info/acpi/acpi.html
Another thing that I did not like was being forced to use the dynamic overclocking feature of this board. I have a 333mhz barton core, and I have ddr400 ram. In optimized (fool proof) mode in bios, I was running asynchronous. I did not want that. So I set it down to run at 166mhz, with very slow and conservative settings on everything. Unfortunately, if I did this "manual" method, I was forced to use the dynamic overclocking. I thought I had that figured out. So I set everything to "optimized". But, as it turns out, the system had terrible stability without the dynamic overclocking set to at least Private. What this meant is that I could not rule out that my stability issues (corruptions and hangs and bsod) were from being overclocked even a tiny bit or not. And as if that were not enough, this bios has a special set of settings you must unlock to see. And one of those is paramount in achieving a stable system. It is called the DDR400 patch, and it is enabled by default. So, by pressing SHIFT+f2 AND CTRL+F3, these settings are now available. Like I said, I had to disable that DDR400 patch setting.
I also found out from the first day that my board shipped with the latest bios. I flashed the 2 prior versions with no success in more stability. After about 6 weeks of getting whipped on by this board, I found mention of some modded bios's for this board. I have used modded bios's in the past, some worked wonders, others required some serious effort to recover from. What I found out about this board is that there are 2 players who make the modded bios's. Here is the first index I found from a german website. This one actually is for the older B4 version only for the Platinum.
http://storage-raid-forum.de/viewtopic.php?t=2824
And here is an english forum for pretty much the same thing
http://www.nforcershq.com/forum/bios-mods-for-k7n-and-k8-boards-vt55014.html
These links have a bit more information, and I decided to go with these. I tried versions b61,b62 and b71. I found b71 to work the best for me. Mind you I am not into overclocking or what-have-you. Just a rig that performs as well as it was advertised to do. Try these out for the bios information:
http://forums.pcper.com/showthread.php?t=385480
https://forum-en.msi.com/index.php?topic=84715.0B62
Here is a page that had a bunch of misc stuff I found interesting:
http://66.102.7.104/search?q=cache:QkvLeKcbwjQJ:www.amdzone.com/modules.php%3Fop%3Dmodload%26name%3DPNphpBB2%26file%3Dviewtopic%26p%3D75383+nforce2+ultra+nvraid+driver+freeze&hl=en&client=opera
In the end, I have, I think, conquered this board. My findings can be summed up as follows, all in my opion only I guess.
1. There are some ACPI/APIC issues with this board or this chipset. I believe it also included drivers and some can be attributed to XP.
2. There are some major bios issues with this board.
3. There are some major driver issues concerning SATA/RAID. I am not sure who get's the boob prize, nVidia or MSI.
The only way I have found to get RAID 0 installed and stable is to modify my bios (which is a modded beta version), modify my driver disk for SATA/RAID, modify my install sequence for those drivers, modify my drivers within windows after setup, use different drivers from different driver packs for different pieces of hardware, and modify my HAL layer after everything else is done, to achieve peak performance.
If I had not spent soooo much time trying to get a stable install, I would have built up an Unattended CD, which has some possibilities for forcing non WHQL drivers. But, hey man, I am totally burn out on this board. And all it was for is a spare LAN box for when I go to a lanparty. Sheesh. Murphy's law.
Oh, and I also found out, with my own eyes, that the Soyo KT600 Dragon+ that I dumped for this wonderful board, is way faster. Faster read/writes, faster throughput on the nic, faster booting, much faster installs of xp. As a matter of fact, I could get my KT600 to get a consistent thruput on the network to my older KT266a board at 99%. That is pretty fast. 2 of these Platinum boards, on a sweet switch that is tweaked, will only go up to 91%, no matter how much I tweak them. The gigabit connects via a crossover cable at about 38% of full bore. This is tweaked stuff, but still. I listened to the hype. Dual channel memory, giglan, etc etc.
I hope this may help anyone else out there who is still fighting with these issues.
Out.
sul

Updating a Hardware RAID array

I'm running a recent Mac Pro model with Hardware RAID and four 1TB SATA drives.
Seagate 1.5TB drives are now available, and they're cheaper than the 1TB drives were just a few months ago.
My Infrant/Netgear ReadyNAS NV+ implements a proprietary form of RAID that they called X-RAID, similar to RAID-5 but with the feature that you can swap larger drives into the array one at a time, and when you're done, the RAID will be re-synced to make use of the additional storage without requiring that you dump and restore the contents of the array. The final re-sync is an admittedly long process (it took three days for mine to update from 4x750GB to 4x1TB) but it's still a very convenient feature.
Does Hardware RAID on Mac OS X have anything like this, i.e. can I replace 1TB drives one at a time with 1.5TB drives and preserve my data? And when I'm done, will the system recognize and use the new storage?
If not, could someone please describe the procedure that I would need to go through in order to achieve this? I presume that I would need to recreate the RAID array entirely, re-install the OS, and then restore the system from my Time Machine backup. But I'm not sure of the details.
I'd appreciate any help with this. Thanks.
An aside: I was more than a little upset a few months ago when I called Apple Support for help with initial setup of my RAID array (I have Apple Care) and was told "Sorry, we don't support Hardware RAID." So Apple was quite happy to sell me an $800 piece of hardware for my lavish new system but didn't bother to tell me at time of purchase that my configuration was "unsupported." It seems a little outrageous to me.
Given Apple's refusal to help me I need to ask the community for help with problems like this.

Hi rrgomes;
Never having heard of X-RAID but going by your comment that is similar to RAID5 I would have to say that you will not be able to upgrade by replacing one disk at a time.
As to no support for the RAID card, I personally would not have taken his word for that. Instead I would have escalated it up through Customer Service just to be sure before I gave up on that point. To me the response you got there sounds bogus.
Allan

Disk utility doesn't show xServe RAID Array

I have a new (to me) xServe RAID box and I'm stuck, the stays lights are green the fiber link light is green on the RAID and not lit on the PCI card but shows up as green in the fiber link section of the settings tool but the RAID array doesn't show up in Disk Utility so I can't format the drives.
I set up the disks as Enhanced JBOD using RAIDadmin and I've deleted and created it a couple of times, I'm just not sure what else I should try, I've read the manual but. Can't find any suggestions of what's going wrong.
Thanks

If you have tried restarting a few times and it still doesn't show up I'm afraid you are gonna have to go back in and check the connections. I know they just slot into the carriage, but possibly it is not in tight. I can only suggest you open it up and check everything thoroughly. If after a thorough check, if it still does not mount you may want to take the hard drive back and swap it. Are you sure it was only a hard drive failure in the first place? I only ask this because WD hard drives have quite a solid reputation.

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.

Image Software on nVidia RAID arrays

Has anyone been able to get a disk imaging program to work with the nVidia RAID array? I have tried Acronis True Image, Norton Ghost 9.0 and the old Drive Image. I have been unable get the rescue/recovery disks to recognize the RAID Array. With Acronis, it appears that they don't have the Linux drivers for the RAID array. Ghost 9.0 is supposed to support RAID arrays, but when I try to load the drivers, I get a message that it can't find nvraid.sys, despite the fact that I supply that file on the floppy disk. I spent 1.5 hours on the phone with Symantec Technical Support and their only answer was that I would receive a phone call from a supervisor in 3 days.
I can get Norton Ghost to work from within windows, but in order to restore an image of my C: drive I need to gain access to the RAID array from the recovery disk.

I have sort of got it to work with ghost9 .
I have written a plug-in for nvraid/nvide for the bartWinPE cd made with PEBuilder 3032.
V2I Images can then be browsed with imagebrowser and files/catalogs be restored
to arrays partitions .
The thing that does not yet work properly is the V2I protector executable cause the bart plug-in for .Net gives problems .(not sorted out this yet)
The BartWinPE cd is also of course equipped with ghost9 plugin .
So basicly the PC is booted with bootable Windows PE cd (like the ghost9 CD) ,
windows runs from cd&ram . And all the nvraid arrays is visible .Restoration made
with V2I image browser .
The plug-in ( INF file ) :
Code: [Select]
; PE Builder v3 plug-in INF file
; NVIDIA RAID (Windows XP)
; Created by Syar2003
[Version]
Signature= "$Windows NT$"
[PEBuilder]
Name="DSK_NvRaid"
Enable=1
[SourceDisksFiles]
nvraid.sys=4,,1
nvatabus.sys=4,,1
[SetValue]
"txtsetup.sif","SourceDisksFiles","nvraid.sys", "1,,,,,,_x,4,1,0,0"
"txtsetup.sif","SourceDisksFiles","NvAtaBus.sys", "1,,,,,,_x,4,1,0,0"
"txtsetup.sif","SCSI.Load","nvatabus", "nvatabus.sys,4"
"txtsetup.sif","SCSI.Load","nvraid", "nvraid.sys,4"
"txtsetup.sif","SCSI","nvatabus", """NVIDIA NForce Storage Controller"""
"txtsetup.sif","SCSI","nvraid", """NVIDIA RAID CLASS DRIVER"""
"txtsetup.sif","HardwareIdsDatabase","PCI\VEN_10DE&DEV_008E", """nvatabus"""
"txtsetup.sif","HardwareIdsDatabase","PCI\VEN_10DE&DEV_0085", """nvatabus"""
"txtsetup.sif","HardwareIdsDatabase","PCI\VEN_10DE&DEV_00D5", """nvatabus"""
"txtsetup.sif","HardwareIdsDatabase","PCI\VEN_10DE&DEV_00EE", """nvatabus"""
"txtsetup.sif","HardwareIdsDatabase","PCI\VEN_10DE&DEV_00E3", """nvatabus"""
"txtsetup.sif","HardwareIdsDatabase","PCI\VEN_10DE&DEV_00E5", """nvatabus"""
"txtsetup.sif","HardwareIdsDatabase","*_NVRAIDBUS", """nvraid"""
"txtsetup.sif","HardwareIdsDatabase","GenNvRaidDisk", """nvraid"""
If the BartWinPE cd is equipped with ghost8 you should be able to restore
full disks/partitions with the *.gho extension .
But then the images must be buildt with ghost8 (from the BartWinPE cd first).
Though i have not had the time to test that yet .
Links:
Plug-in repository
http://www.reatogo.de/BartPE/BartPE_plugins/repository.htm
PeBuilder
http://www.nu2.nu/pebuilder/

Xsan 2.3 qualified RAID Arrays

Hi there - I've been searching for documentation on "qualified RAID arrays" to work with the new Xsan 2.3 in lion. As Apple says in their release of lion that "Lion also supports industry-standard multipathing and failover, so Xsan can be used with a variety of Fibre Channel RAID storage arrays." (http://www.apple.com/macosx/server/) at the bottom. I pulled up mr. Manual and searched "qualified RAID Arrays" and I get to the section in chapter 3 "Supported Storage devices", and warned to make sure to use only an apple certified RAID array... For the latest information see www.apple.com/xsan/
So I click there... and it still only has the Promise Vtrak system labeled that was supported in v2.2.... Anybody had any luck finding a list of other supported arrays? Anybody currently running any other fibre arrays?
Would love to know! Thanks Everybody!
Kyle

Well and it's not to say that the Promise's are bad - that's not what I'm saying at all, I just want the option. I'm just looking for other people that either have done the same research I'm doing - or are personally using a different array. There are many other arrays out there that are just as reliable and fast that have a much nicer price tag than Promise's stuff. Currently we are living off of 3 XserveRAID arrays, which is fast enough for our 3 workstations. But we're looking to add 5 more (1 final cut and 4 animation stations using AE and Maya/nuke). We are running an OLLldddd Xsan version (like 1.4.2 maybe?? don't have it in front of me) but Everything is needing a giant face lift... and with each lion box allowed to use Xsan the only thing holding us back is After Effects being compatible with Lion. Maya and nuke boxes actually can use AFP to get to the SAN and would be fine.
Anyways. I'll give you credit for a helpful answer - but I'm looking for more concrete choices
Thanks

NAS Raid Array

I have a NAS Raid Array and when I try to set up time machine, it does not come up in the options list for storage devices. Where is it?
Thanks,
Scott

A disk image is treated by the OS as a local file. So look into how to create a growable sparse image (specify a size of 1 TB or something and if it's a sparse image the initial size will be small). This trick also works for Aperture Vaults. The caveat being that the file will be opaque to any non-Apple clients... on the NAS it will just look like a huge "block" called <name>.sparseimage. Fire up Disk Utility and search the help on creating images, or go to Apple's Knowledge Base:
http://search.info.apple.com/
And search for sparse image.
One example is here:
http://docs.info.apple.com/article.html?path=DiskUtility/10.5/en/duh1527.html
Note you don't have to use encryption on the image... and it's faster if you don't.
One of the main issues in using a NAS is the file system of the NAS. HFS+ supports all manner of characters in the file name. You can have spaces, and many characters which are "illegal" on Windows (NTSF || FAT32) or Linux/UNIX (UFS, EXT2, EXT3, ReiserFS) file systems. So if you try and run Time Machine over an SFP or AFP backup to a NAS that uses some other file system, you've got issues. Hence the reason not to support any NAS other than OS X Server (which is obviously running OS X and thus has HFS+).

3310 RAID + 3310 Expansion + SunFire 440 Question?

HI all, I am new here.
I just set up my first SunFire 440 database server with one 3310 RAID (12 x 36GB) controller and one EXPANSION (12 x 36GB) controller.
I am using the Ultra3 SCSI PCI card (with the most recent drivers). Updated solaris 9 patch cluster. Updated 3310 firmware (I think it is 325W or something like that) and patches. Single Bus setting where one 3310 is used for expansion and the other used for RAID. The set up is just like the "Quick Install Guide" in Single Bus setting. The two 3310 arrays were used.
Question: How do I reset each 3310 disk array config? is it the sccli "reset nvram" command?
I can only see one 3310 when I do the sccli command. It does not give me the option to select the 2nd 3310 (therefore I wasn't able to upload the new 325 firmware). I don't think my servers see it. When I run the ssconsole, it only sees one 3310. Where is my 2nd 3310? I am thinking that I messed up with the physical SCSI connections in the rear panel of the 3310 for single bus in RAID and EXPANSION setting. Can someone tell me how they set it up or tell me what I am doing worng? Or Could it be the /kernel/config (something like that) where I add the LUN number... can someone tell me what that is for? Is LUN only for FC or can SCSI use it to?
Thank you for your time.
-Tony

OKAY. Forget the question above. I found some the Configuration User Guide that will help me set up RAID and Logic Drives.
BUT I still can't see all 24 hard disk (12 hard disk on each array) using the Quick Install Guide for "Connecting Cables for Single Bus Configuration." I can see 12 hard disk on channel 0 and 6 hard disk on channel 2. When I do a show disk, I get
sccli> show disk
Ch Id Size Speed LD Status IDs Rev
0 0 33.92GB 160MB ld1 ONLINE FUJITSU MAP3367N SUN36G 0401
S/N 00N0ANJ4
0 1 33.92GB 160MB ld1 ONLINE FUJITSU MAP3367N SUN36G 0401
S/N 00N0APCR
0 2 33.92GB 160MB ld1 ONLINE FUJITSU MAP3367N SUN36G 0401
S/N 00N0APCL
0 3 33.92GB 160MB ld1 ONLINE FUJITSU MAP3367N SUN36G 0401
S/N 00N0APEE
0 4 33.92GB 160MB ld1 ONLINE FUJITSU MAP3367N SUN36G 0401
S/N 00N0APDN
0 5 33.92GB 160MB GLOBAL STAND-BY FUJITSU MAP3367N SUN36G 0401
S/N 00N0APDV
0 8 33.92GB 160MB ld0 ONLINE FUJITSU MAP3367N SUN36G 0401
S/N 00N0AP9N
0 9 33.92GB 160MB ld0 ONLINE FUJITSU MAP3367N SUN36G 0401
S/N 00N0APRC
0 10 33.92GB 160MB ld0 ONLINE FUJITSU MAP3367N SUN36G 0401
S/N 00N0APTL
0 11 33.92GB 160MB ld0 ONLINE FUJITSU MAP3367N SUN36G 0401
S/N 00N0AP85
0 12 33.92GB 160MB ld0 ONLINE FUJITSU MAP3367N SUN36G 0401
S/N 00N0APR8
0 13 33.92GB 160MB GLOBAL STAND-BY FUJITSU MAP3367N SUN36G 0401
S/N 00N0APEL
2 0 33.92GB 160MB ld2 ONLINE SEAGATE ST336607LSUN36G 0507
S/N 3JA6RJBF00007424
2 1 33.92GB 160MB ld2 ONLINE SEAGATE ST336607LSUN36G 0507
S/N 3JA29KTX00007402
2 2 33.92GB 160MB ld2 ONLINE SEAGATE ST336607LSUN36G 0507
S/N 3JA29F3G00007402
2 3 33.92GB 160MB ld2 ONLINE SEAGATE ST336607LSUN36G 0507
S/N 3JA6RKVJ00007424
2 4 33.92GB 160MB ld2 ONLINE SEAGATE ST336607LSUN36G 0507
S/N 3JA6RMEN00007425
2 5 33.92GB 160MB GLOBAL STAND-BY SEAGATE ST336607LSUN36G 0507
S/N 3JA6RK2B00007424
What happened to channel 2 hard drives 8-13??
I read on another post use command "drvconfig;devlinks;disks" but I can't find any info on that command.
Thanks.
-Tony

Dmraid not recognizing raid arrays.

Ran pacman -Syu, and part of the update was to the new dmraid. After rebooting, my /dev/mapper directory only has "control" in it. I looked through these two forum posts, but I still don't have any idea where to even begin to try and fix this.
http://bbs.archlinux.org/viewtopic.php?id=57579
http://bbs.archlinux.org/viewtopic.php?id=56641
The output from dmraid -ay:
ERROR: isw: Could not find disk /dev/sdc in the metadata
ERROR: isw: Could not find disk /dev/sdb in the metadata
no raid disks
The raid array is a 500GB array that is only used for storage, so I can still boot fine. dm_mod is loaded. Everything still seems to work, with the exception of my raid array. Any kind of help would be appreciated.

I have the same problem.
Unfortunetly my root partition is on fakeraid, so i can't boot.
Output from dmraid -ay:
ERROR: isw: Could not find disk /dev/sdb in the metadata
ERROR: isw: Could not find disk /dev/sdc in the metadata
ERROR: isw: Could not find disk /dev/sdd in the metadata
ERROR: isw: Could not find disk /dev/sda in the metadata
no raid disks
There are no devices in /dev/mapper.
Disk and raid are fine, becouse Vista works as usual.
I'm downloading usb boot image so i can revert kernel to previous one.
Ekimino wrote:This was the output of dmraid. So you should just change in fstab and in Grub your device name from /dev/sda1 to /dev/sdap1
I upgraded dmraid before kernel upgrade, and i saw this notice. I update acording files, and system didn't boot, becouse naming schema didn't change! Revert back to old ones, and arch was runining fine until evening upgrade(including kernel update).
edit
usb pen with arch image freez my pc on bios screen
Last edited by extcake (2008-11-11 10:59:46)

Help setting up raid array

Can someone please help me setup a raid array. I bought another SATA hdd and I would like to set it up in raid but I'm clueless. Any help is appreciated.

First I apologize for being a noob raider. Well, I have a new 200gig sata I want to add and I want best performance not just extra storage, so would raid 0 be the answer? I'm clueless. Also, I enabled raid in my bios now I get a install new hardware wizard. I try to install the drivers with the CD that came with mobo but it fails every time.

Booting from external SATA firewire800 hardware RAID array

Just a quick post to update on a new toy and how it's being used.
Recently obtained a hardware RAID array which contains 5 drives at 250 GB each. Currenly setup as RAID 5, providing 1TB of storage.
After formating via DISk image I did a drive restore from my normal boot disk to the new array.
I changed the startup options to boot from the array.
So basically I am running my system from this new device.....I may later reconfig the array to 0+1 with a floating spare.
Cost of the box was 500. New and unused off ebay.

..

WinXP-64 bit corrupts existing RAID array

I've got an MSI K8N Neo2 Platinum motherboard running Win XP Pro SP2 on two 36 gig SATA Raptors. Everything was working fine, but I wanted to try the 64 bit version of XP. Grabbed an old 80 gig PATA drive and threw that in the case. Unplugged the SATA drives so as not to risk messing with the existing working OS. Installed the latest 1218 x64 beta and it worked well.
The problem was that when I shut down and reconnected my old RAID array, windows wouldn't boot from it. I lost everything and had to rebuild Windows from scratch. So now I know to never unplug the SATA drives
Rebuilt WinXP on the RAID array and then tried rebooting with the PATA drive with the 64 bit OS. Came up with the "drive needs checking" screen, and proceeds to "fix" the RAID array while ignoring my frantic pounding on the Logitech USB keyboard to stop. Rebooted and yes, the new install was nuked. Okay, since it's gone anyway, reboot to the 64 bit OS and make sure it's got the 64 bit RAID drivers installed.
Reinstall WinXP on the RAID array, reboot to the 64 bit OS on the other drive and the same old scandisk comes and nukes it AGAIN!
So now the PATA drive is sitting on the shelf again, unless someone here can suggest what is causing this problem.
System Specs
Athlon64 3500
gig of PQI 3200 at 2-2-2-5 2.6
2x36 gig Raptors on ports 3-4
Plextor PX-716a DVD+_RW
Visiontek X800 Pro.

The first time you re-installed Win 32 on the raid that was a bit drastic. A repair ought to have done the job.
The problem was probably that you disconnected the array but that's where the boot.ini was and that file needed to be modified to add the path to the Win64 install.
Since you took out the array the Win64 install created a new boot.ini on the PATA drive. Even when you tell BIOS to boot off the array, Windows has a bad habit of looking at the IDE channels & using the boot.ini if it finds one there - but the file it found didn't point to the array of course.
So basically if you already have Win32 on the array I would leave that array connected normally when installing Win64 on the PATA drive and all should be well.
I've installed Win64 on the same array as my Win32 install and they co-exist happily. I reckon that's the most efficient way to do it. The main thing is to make separate partitions for Win32, Win64 and data files when you install Win32 in the first place. The two OSs can share the same data files, incuding stuff like email.

Storage 3310 RAID array as JBOD

Similar Messages

Maybe you are looking for