LSI1064 RAID 1 V215 HowTo?

So I've got a shiny new V215 server, jumpstarted to Solaris 10 Update 3. I try to mirror the OS disk:
# raidctl -f -c c1t0d0 c1t1d0
Cannot create RAID volume, disk "c1t0d0" is mounted .
Are we for real? I feel a rant coming on. Every box Sun builds has some insane defect or some engineering flaw that just makes it so hard to stand behind their hardware. Why can't they get it? Something as simple as a RAID controller! Look at an HP DL-360. The RAID controller is flawless. It's controlled in the BIOS, which makes OS interaction with the controller moot. We were set to buy a few hundred of the V215's, but guess what? Not on your life.
Sorry, vent off.
Does anyone know of a (argh...) work-around? How do I mirror the OS disk with this piece of dung RAID controller? (Is there a secret document somewhere?)
TIA....

Hello,
incidiently you already explained why creating a RAID works on the x64 system: When you configure the RAID in the BIOS none of the volumes is mounted. Invoking raidctl from the disk that is/becomes member of the RAID won't work.
Have you tried to boot from the Solaris CD and invoke raidctl to create the RAID ?
Alernatively you can add this disk preparation to jumpstart.
The procedure is to create the RAID and then install the OS.
I don't have access to a Sun with this (hardware) RAID capability, therefore I can't try if it works (and destroy the disk contents).
There are basically few choices:
- Try the above procedure
- Post to the next thread and maybe get an answer from Toze (who didn't return)
- Open a service case with Sun, either on contract or paid per incident
- Someone else post a direct answer
This is link to another thread about the LSI1064
http://forum.java.sun.com/thread.jspa?threadID=5135052&tstart=135
Quote from a quote from the above thead
The LSI1064 HBA can enable up to two RAID volumes and, in
addition to IM volumes, also supports the RAID 0 volume
type, called an Integrated Stripe, or IS. Volumes of either
RAID type can be created on an LSI1064 only when no member
disks have mounted file systems, as the volume initializa-
tion destroys any data on member disks.
Michael
Message was edited by:
MAALATFT

Similar Messages

Solaris 10 X86 - Hardware RAID - SMC/SVM question...

I have gotten back into Sun Solaris System Administration after a five year hiatus... My skills are a little rusty and some of the tools have changed, so here is are my questions...
I have installed Solaris 10 release 1/06 on a Dell 1850 with an attached PowrVault 220v connected to a Perc 4 Di controller. The RAID is configured via BIOS interface to my liking, Solaris is installed and see's all my partitions which I created during install.
For testing purposes, the servers internal disk is used for the OS, the PowerVault is split into 2 RAID's - one is a mirror, one is a stripe...
The question is; do I manage the RAID using Sun Management Console and the tools OR do I use SMC?
When I launch SMC and go into Enhanced Storage... I do not see any RAID's... If I select "Disks" I do see them, but when I select them, it wants to run "FDISK" on them... now this is OK since they are blank but I want to ensure I am not doing sometinhg I should not be concerned with...
If the PERC controller is controlling the RAID, what do I need SMC for?

You can use SMC for other purposes but it won't help your with RAID.
Sol 10 1/06 has raidctl which handles LSI1030 and LSI1064 RAID�enabled controllers (from raidctl(1M)).
Some of the PERCs (most?) are LSI but I don't know if they are chipsets used by your PoweEdge (I doubt it).
Generally you can break it down like this for x86:
If you are using hardware RAID with Solaris 10 x86 you have to use pre-Solaris (i.e. on the RAID controller) managment or hope that the manufacturer of the device has a Solaris managment agent/interface (good luck).
The only exception to this that I know of is the RAID that comes with V20z, V40z, X4100, X4200.
Otherwise you will want to go with SVM or VxVM and manage RAID within Solaris (software RAID).
SMC etc are only going to show you stuff if SVM is involved and VxVM has its own interface, otherwise the disks are controlled by PERC and just hanging out as far as Solaris is concerned.
Hope this helps.

Solaris possibly preventing RAID BIOS launch

Hello
I have installed a STLab A-230 2-Channel Serial ATA & ATA-133 RAID Combo and tried to boot into its RAID BIOS with no luck. The initial loading menu quickly switches to the multi-boot menu where you select to boot into Solaris or another OS. I am supposed to press Ctrl-Z, but it just switches to the boot menu without bringing up RAID BIOS. Please let me know if this would be to do with the installed Solaris and its uninstallation would solve it.
Regards,
Dai

You can use SMC for other purposes but it won't help your with RAID.
Sol 10 1/06 has raidctl which handles LSI1030 and LSI1064 RAID�enabled controllers (from raidctl(1M)).
Some of the PERCs (most?) are LSI but I don't know if they are chipsets used by your PoweEdge (I doubt it).
Generally you can break it down like this for x86:
If you are using hardware RAID with Solaris 10 x86 you have to use pre-Solaris (i.e. on the RAID controller) managment or hope that the manufacturer of the device has a Solaris managment agent/interface (good luck).
The only exception to this that I know of is the RAID that comes with V20z, V40z, X4100, X4200.
Otherwise you will want to go with SVM or VxVM and manage RAID within Solaris (software RAID).
SMC etc are only going to show you stuff if SVM is involved and VxVM has its own interface, otherwise the disks are controlled by PERC and just hanging out as far as Solaris is concerned.
Hope this helps.

Solaris 10 x86 - software RAID

I try make software RAID on x86 server with Solaris 10.
2 ata/ide disks on Intel i865 board.
I make mirroring all data partitions - it normally working.
make 2-nd disk bootable.
What I can do with BOOT partition ? mirror ? format on pcfs and copy data from 1-st disk? copy it with dd ?

You can use SMC for other purposes but it won't help your with RAID.
Sol 10 1/06 has raidctl which handles LSI1030 and LSI1064 RAID�enabled controllers (from raidctl(1M)).
Some of the PERCs (most?) are LSI but I don't know if they are chipsets used by your PoweEdge (I doubt it).
Generally you can break it down like this for x86:
If you are using hardware RAID with Solaris 10 x86 you have to use pre-Solaris (i.e. on the RAID controller) managment or hope that the manufacturer of the device has a Solaris managment agent/interface (good luck).
The only exception to this that I know of is the RAID that comes with V20z, V40z, X4100, X4200.
Otherwise you will want to go with SVM or VxVM and manage RAID within Solaris (software RAID).
SMC etc are only going to show you stuff if SVM is involved and VxVM has its own interface, otherwise the disks are controlled by PERC and just hanging out as far as Solaris is concerned.
Hope this helps.

Solaris 10 colormap hardware support question

Hi -
[Reposting an article that disappeared...]
I am porting an X application from Solaris2.6/Sparc to Solaris 10/x86. The display application requires multiple (hardware) colormaps to correctly display images without "flashing".
Does anyone have a Solaris 10 x86 installation with a PCI (or PMC) graphics card interface that supports more than 1 hardware colormap? The command:
xdpyinfo | grep colormaps
will show you how many maps your hardware supports. I would be grateful to learn of any Solaris 10 x86 PCI (or PMC) graphics hardware that supports at least 2 maps.
Thd following gets a bit more away from a platform question, and into an X question, but:
How does the Xserver determine how many hardware colormaps are available? My X server says that my ATI Radeon 7000 hardware only supports 1 hardware colormap - could it be mistaken/"fibbing" about this capability? Perhaps just 1 colormap is a fallback default and can be changed?

You can use SMC for other purposes but it won't help your with RAID.
Sol 10 1/06 has raidctl which handles LSI1030 and LSI1064 RAID�enabled controllers (from raidctl(1M)).
Some of the PERCs (most?) are LSI but I don't know if they are chipsets used by your PoweEdge (I doubt it).
Generally you can break it down like this for x86:
If you are using hardware RAID with Solaris 10 x86 you have to use pre-Solaris (i.e. on the RAID controller) managment or hope that the manufacturer of the device has a Solaris managment agent/interface (good luck).
The only exception to this that I know of is the RAID that comes with V20z, V40z, X4100, X4200.
Otherwise you will want to go with SVM or VxVM and manage RAID within Solaris (software RAID).
SMC etc are only going to show you stuff if SVM is involved and VxVM has its own interface, otherwise the disks are controlled by PERC and just hanging out as far as Solaris is concerned.
Hope this helps.

Installation of 0.7.1-pre1 troubleshooting

After a fresh 0.7.1-pre1 installation on 2 SATA disks RAID1 (I followed instructions of WIKI RAID/LVM HOWTO) my system boots unexpectably:
Here is a copy of boot failed lines:
1) mount Mounting /dev/md0 on /new_root failed No such file or directory
2) pivot_root No such file or directory
3) umount /initrd No such file or directory
4) /bin/sh Can't open
My comments on boot failure:
I never declare a /new_root, Neither initrd !! I am dead without a shell :-(
I don't wanna leave Arch pacman for a functional Debian installation ...
Have you any suggestion to get my system functional?
By the way WIKI RAID/LVM HOWTO has errata such as:
It doesn't mention that modprobe raid1 and modprobe dm-mod are needed.
mkdir /sys
mount -t sysfs none /sys
always fail.
Usage of
mkdir /mnt/sys
mount -t sysfs none /mnt/sys
don't fail but I am not sure about ...

So far, no responce. OK guys, I understand that Arch 0.7.1-pre is a PRE release so it contains many or a few bugs.
I used my 0.7.1-pre CD but instead of using CD files for installation I used FTP (0.7.0) stable branch and everything is OK.

Arch installation with Raid0 and Windows 7

Hi
I am not a newbie at Arch but I am a newbie at Raid0 i never had Raid0.
So my problem is i want to Install W 7 and Arch on Raid0.
I make the Raid0 in the Bios (Asus P5E Mainboard) and Install the Windows System,
after that i try to boot the Bios CD it ends at grub command line.
I downloaded the Arch Net Install and with this i boot.
But my problem how the install now i try the Raid/LWM howto from the Wiki but i dont know it doesnt
work.
I hope some can me help
And Sorry for my english
CU

loosec wrote:
Follow http://wiki.archlinux.org/index.php?tit … _Fake_RAID carefully and you are on your way.
Software raid will not work in a dualboot setup with Windows 7.
Fake-Raid will work if your chipset is supported by the dmraid driver.
Also a lot of threads about this in the forum so a search for 'Windows RAID dualboot' should be able to help you.
GL HF.
Ok thanx I will try it and report here if it was sucsessfull

Howto use onboard Promise Raid Controller pdc20265 on 694D PRO AR Ver1

Currently I'm running Win2k on my MSI 694D Pro AR Ver 1.0 board with Bios version W6321VMS.310 and the included Fasttrack-Family Win2k Raid-Controller driver for my Promise Raid Controller pdc20265 with lite bios.
Due to software updates I'm now absolutely required to switch to Windows XP Prof. However this is the cause for my inquiry:
I downloaded and installed the latest available Bios version W6321VMS.370 from MSI site.
On installation of XP I tried to include the pdc20265 Fasttrack raid driver from MSI site to get access to my HD's. However WinXP couldn't find any HD's. Remark: XP with SP1 and VIA 4in1443v.exe installed.
So I repeated this procedure with the original drivers Fasttrack family and pdc202065 which were attached on floppy. Unfortunately no success as well.
Then I have put the HD on the Ultra66 channel and installed XP first without raid and ultra 100 support.
Later I re-enabled the on-board promise device in bios and unfortunately WinXP didn't recoginze the device by itself. So I provided the latest pdc20265 driver from MSI site. XP complained that the driver is not digitally signed. After reboot the promise device reported an error under WinXP.
I repeated this procedure with the original drivers Fasttrack family and pdc202065 which were attached on floppy. Unfortunately no success as well.
Why MSI-Site says this pdc20265 driver supports WinXP if there are only the Win2k and WinME,98... drivers included?
Currently I can't use the promise device at all under WinXP. This means even I don't have an Ultra 100 controler available.
Has anyone an idea how to install HD's on WinXP with the corresponding promise raid drivers for my pdc20265 onboard chipset?
I'd really appreciate your help!

Some of the suggestions I don't understand quite well. Please could you explain further:
> remove the other two drives leaving the raid pair
> and cd only
>
> put raid 2nd in boot order
What do you mean with that?
> reboot press the key you need to get in to raid bios
> create the array and make it bootable
array is already created (Note: there is important data on it, can't recreate it! Only Segate 80GB is free and empty)
I don't want to boot from raid.
>
> now boot to cd to install,right at beginning it will say
> press f6 to install mass storage drive you need the
> driver on floppy to install it
I already tried the XP-Install routine to specify additional mass storage drivers. (Note: 1 single 80GB Drive was attached) Which are the suitable ones? As mentioned I tried the following:
1. Attached floppy 'Fasttrack family drivers'
Result: Message: Driver is for Win2k only. Not a single Harddrive shows for installing XP.
2. Attached Floppy (Promise Ultra 100 lite, 256 only)
Result: Driver is for Win2k only. Installation procedure hangs.
3. Driver from MSI-Site for pdc20265. Same as 2.
4. Extracting via4in1 drivers and putting WinXPIDE drivers on floppy:
Result: Installation routine doesn't recoginze drivers on floppy.
> rest should be the same as normal
>
> this should be similar as well
>
> http://www.amdforums.com/showindex.php?s=&threadid=146384
Which is the right driver for WinXP to specify for mass storage device at WinXP installation?

Z87-GD65 raid howto

hello
i am finding difficult to understand MSI documentation.
prior to purchasing the MB, i have done some reading on this product.
and i had understood this MB to provide support for RAID configurations of HDD.
my question:
How do i configure a RAID 5 using 3 disks of 1GB each?
Is there something in the BIOS that i should enable/change to accomplish this task?
many thanks,

Quote from: xmad on 15-February-14, 01:43:04
Is this for a storage volume or OS?
I have the same or very similar problem. MB: Z87-G45. Plan is to install a single SSD as the boot drive and then install a pair of regular hard drives as a mirrored paid (data drive) under RAID 1. I've done this many times before, but not with MSI motherboards.
If I turn on RAID in Bios, then it won't let me select which drives are bootable and Windows 8.1 won't let me install to the SSD. If I turn off RAID, then I can't configure the mirrored pair. On an Intel MB, I usually configured for ACHI, which still supported RAID, but that doesn't seem to be the case here.
Ideas?

Arch linux full raid

I am experimenting with arch and mdadm I was using the following guide:
http://linux-101.org/howto/arch-linux-s … tion-guide
I get into trouble (at least I notice it at that point) with the bootloader. find /boot/grub/stage1 returns Error 15: File not found, so running the commands:
grub> device (hd0) /dev/sda
grub> root (hd0,0)
grub> setup (hd0)
naturally result in the same problem.
Any indication what I am doing wrong? Maybe the tutorial is out of date?

Blµb wrote:I think you're missing that 'device (hd0) /dev/sdX defines hd0 to be /dev/sdX, which is once done for sda and then for sdb.
Yes I was/am missing that. I understand what you are saying and you have a point but I still have something daunting:
find /grub/stage1
(hd0,0)
(hd1,0) <---- what's this?
running the guide grub installs went fine but running:
grub> device (hd1) /dev/sdb
grub> root (hd1,0)
grub> setup (h1)
also works. Why?
I only have two harddisks installed, what is (hd1) as I was under the impression that it was /dev/sdb, which now seems to be incorrect...
Very confusing..
Blµb wrote:I'm curious about the md= entries in this guide though. Is the goal of this to not require mdassemble to be run in an initramfs? Because mdadm usually reads from /etc/mdadm.com in the initramfs to assemble the devices.
But what do I know, mdassemble segfaults for my intel imsm raid... so I'm still sticking to DM-raid though maybe this could help... and that doesn't help me in my case either (says "bad raid superblock magic")
You are referring to the "md=" in grub's menu.lst? I also remember this happening in a later stage. The strange thing is that it seems to work though... If you know a better/other guide/tutorial about this subject I would like to know about it.
Thanks allot for the information!
Last edited by whoop (2012-02-29 20:24:30)

IDE Raid not recognised by Solaris 10 6/06

Hi,
I am new to Solaris and was trying to install Solaris 10 on my old machine which has got Intel Server Board SE7500CW2 with built in Raid (ATA-100) controller. The raid controller is Promise Technology PDC20267 ASIC.
What settings are needed to be done to allow the Solaris to recognise it?
Thanks

solaris supports raid cards based on the LSI1030 and LSI1064 controller.
Also the LSI MegaRAID 320-2x SCSI RAID Controller.
Other raid cards would only be supported if the vendor provided their own raid drivers.
But in general your better off forgetting about hardware raid and using sds software raid.
Unless you go for a quite an expensive card, software raid tends to end up being faster.
But a bit of googling turned up this
According to Sun Big Admin
(http://www.sun.com/bigadmin/hcl/data/sol/components/details/503.html)
, the Mylex Accelaraid 150 is reported to work with Solaris 9 04/04 to Solaris 10 03/05 (read Solaris 9 and 10 X86). The firmware and bios on the card needs to be: BIOS Version 4.10-50; Firmware 4.08-37.
Lots of other cards are listed in the HCL but you have to wade through it to work out which ones are IDE raid cards
https://www.sun.com/bigadmin/hcl/driverlist.html

HowTo install archlinux to a far away server?

HowTo install archlinux to a far away server?
or what about Archbootstrap?
I have a server far away from me with software raid on it.
It is running a different distro and i want to install archlinux on it.
I was thinging to break the sw raid and use something like archbootstrap.
I could install archlinux to one hard disk, fix the network and then
add a new grub entry and reboot. Then i could rebuild the sf raid and configure
my new archlinux server as i want.
I've tried archbootstrap to my PC first and try to install archlinux to a different partition
(same logic to want i need to do). I found some trouble, I even hack a little the script
to fix some initial problems but i cant find a way to run it correctly.
Is there another way? Can someone point me to a direction?
PS: i've already looked up the forum and wiki - couldnt find anything useful (yet).

With pacman-static from the French mirror and small fixes worked perfectly
Unfortunately i couldnt find an official pacman-static on ftp.archlinux.org
I 've tried to create a pacman-static from the source of pacman - but my efforts werent successful
But in the end i was able to do what i really wanted with one way or another.
thanks finferflu for hint

Unable to move existing installation to software RAID-1 setup

I have an existing Arch Linux amd64 installation which I want to move to a RAID-1 setup.
I followed the following Wiki article:
Arch Linux Wiki - Installing with Software RAID or LVM
with necesary changes applied and some supplemental advice from the equivalent Gentoo Wiki article:
Gentoo Linux Wiki - HOWTO Install on Software RAID
mainly for the "--assume-clean" command-line switch to mdadm.
With a Larch live CD I took a tarball backup of each partition.
Then with cfdisk partitioned the disks.
And copied their partition tables to their RAID-1 mirrors:
sfdisk -d /dev/sda | sfdisk /dev/sdb
Now, I cannot boot Arch on the RAID-1 setup.
After initramfs is finished, I get a kernel panic as the "/" partition cannot be mounted.
The mkinitcpio.conf that created my kernel is this:
MODULES="ahci pata_amd ata_generic sata_nv sata_sil"
HOOKS="base udev autodetect pata scsi sata usbinput keymap raid lvm2 filesystems"
My rc.conf is this:
MODULES=(raid1 powernow-k8 fuse forcedeth ac battery button fan thermal loop)
My fstab ("/" and "/boot" lines) is this:
/dev/md0 /boot ext3 noatime 0 1
/dev/md1 / ext3 noatime 0 1
And my menu.lst is this:
timeout 5
default 0
color light-blue/black light-cyan/blue
title Arch Linux
root (hd0,0)
kernel /vmlinuz26 root=/dev/md1 ro swncq=1 md=0,/dev/sda1,/dev/sdb1 md=1,/dev/sda2,/dev/sdb2
initrd /kernel26.img
I even tried another shot by passing all ten RAID-1 arrays (md0 to md9) as kernel parameters, but still, no effect.
Any help would be greatly appreciated.
PS: I have created a correct mdadm.conf file with:
mdadm -D --scan >>/etc/mdadm.conf
Last edited by wantilles (2008-09-08 08:28:20)

My experience with raid suggests that mdadm setups work after boot-up as "software raid". The array is assembled and "ID'd" with mdadm --assemble command.
IMHO In order to utilize mdadm for boot-up, how does the user "assemble" before the elements needed for mdadm --assemble are accessible?
IMHO My understanding of booting with raid involves the use of dmraid, a "software" raid program which can be adapted to boot use. It involves changes to the boot sequence to prevent loss of dmraid params during the boot processes such as hardware detect AFAIK.

ZFS on HW RAID with poor performance. Ideas?

Hi all,
I'm trying to figure out why my RAID performs so poorly using ZFS compared to even UFS. Any thoughts on the following would be helpful.
H/W Config:_
- SunFire v245 w/ 4GB RAM and LSI1064 mirrored 73GB SAS
- QLogic QLE2462
- Fibre Channel 4Gb Hardware RAID w/ 1GB ECC cache
- 16 x 1TB SATA II drives
- Configured 1 volume RAID-6
S/W Config:_
- Solaris 08/07 SPARC - 5.10 Generic_120011-14
- Latest 10_Recommended as of 1/08
- zpool create fileserv /dev/dsk/c3t0d0s6
- zfs set atime=off fileserv
Test Raw:_
To the "RAW" disk or volume I get descent numbers:
# dd if=/dev/zero of=/dev/rdsk/c3t0d0s6 bs=1048576 count=16384
# dd if=/dev/rdsk/c3t0d0s6 of=/dev/null bs=1048576 count=16384
Both c3t0d0 and c3t0d0s6 result in similar numbers:
5 x 16GB writes took 475.50 seconds, yielding an average of *172.28 MB/s*.
5 x 16GB reads took 384.68 seconds, yielding an average of *212.97 MB/s*.
Test ZFS:_
Creating and mounting ZFS to the same volume, I modified my scripts to use dd created files from /dev/null instead:
# dd if=/dev/zero of=./16G bs=16777216 count=4096
Then ran:
# dd if=/dev/zero of=./16G bs=1048576 count=16384
# dd if=./16G of=/dev/null bs=1048576
The result for ZFS on a 14.6TB volume is horrible:
5 x 16GB writes took 1013.28 seconds, yielding an average of *80.84 MB/s*.
5 x 16GB reads took 980.36 seconds, yielding an average of *83.56 MB/s*.
What would cause a delta difference of more than half my capable speed from the unit just by running ZFS? Thinking it might just be a dd issue, I ran iozone using the same parameters as "milek's blog" at http://milek.blogspot.com and got the same crappy results:
# iozone -ReM -b iozone-2G.wks -r 128k -s 2g -t 32 -F /test/*
(snippet:)
Output is in Kbytes/sec
Time Resolution = 0.000001 seconds.
Processor cache size set to 1024 Kbytes.
Processor cache line size set to 32 bytes.
File stride size set to 17 * record size.
Throughput test with 32 processes
Each process writes a 2097152 Kbyte file in 128 Kbyte records
Children see throughput for 32 initial writers = 90584.21 KB/sec
Parent sees throughput for 32 initial writers = 79823.98 KB/sec
Min throughput per process = 2186.76 KB/sec
Max throughput per process = 3225.63 KB/sec
Avg throughput per process = 2830.76 KB/sec
Min xfer = 1427456.00 KB
Children see throughput for 32 rewriters = 88526.23 KB/sec
Parent sees throughput for 32 rewriters = 88380.95 KB/sec
Min throughput per process = 2264.00 KB/sec
Max throughput per process = 3152.58 KB/sec
Avg throughput per process = 2766.44 KB/sec
Min xfer = 1510656.00 KB
I can understand that ZFS wants to have the entire "disk" as in a JBOD, but that's just not a viable option in my Corporate America world. Does presenting a RAID Controller handled LUN Vs. a JBOD presented matrix of drives really make this much of a difference? I'm just at a loss here as to why a unit that is capable of 4Gbit per channel is working as it should via raw, but runs like a single disk in performance as a ZFS filesystem.
I would appreciate some assistance in figuring this one out.
Thanks to all in advance.
--Tom

Robert,
Thanks for the help. Unfortunately, using RAID-Z or Z2 is not an option here as I'd rather rely on my hardware RAID over using software. While doing testing, I set my RAID to pass-thru mode and allowed ZFS to inherit the RAW drives from the RAID Chassis, set up a pool, and did my testing. In all cases, write performance was not much better overall, CPU utilization with compression on was ~30% higher, and my RAM utilization shot up under load. I just don't see that as an option on a heavily hit CVS server where IOPS and CPU/RAM are important for compilations and the like.
Things Hardware RAID gives me that ZFS can't do are:
Ease of use - changing failed drives for example is just different. It's a complicated filesystem once you get into it.
Pre-write buffer performance - This is ZFS's bottleneck afterall.
Fastest I/O - RAID Controllers handle more drives better than ZFS and IOPS are much faster under a H/W RAIDThere's a whole line of reasons why I choose not to use ZFS RAID-Z/Z2. Why else would Sun continue selling both H/W RAID and JBOD? I will check into the Intent Logging though, that's a good idea. I appreciate the link to solarisinternals, I had not thought about using their wiki for this.
Thanks again!
--Tom

Sbo HowTos at a glance

Hi all,
the number of SAP Business One HowTos is growing.
If you need a hint, you might consider checking here:
http://www.itwiki.net/ow.asp?SboHowTo
Itwiki is a non-commercial wiki made from developers for developers.
Ibai has just added another HowTo.
Lutz Morrien

Just wondering...
Is anyone interested in these postings?
I am just trying to pass on information with them, but if they are just annoying, I will stop posting them.
Lutz Morrien

LSI1064 RAID 1 V215 HowTo?

Similar Messages

Maybe you are looking for