Solaris 10 x86 - software RAID boot

What I can write in eeprom : - for boot form 1-st, and if it absent - from 2-nd disk ? (2 disks in soft raid). two bootpath ?
In Solaris 9/sparc for boot with one working HDD in mirror (2 disks in mirrir) I wrote in /etc/system : set md:mirrored_root_flag=1
What I can wrote for this in solaris 10/ x86 ?

Just for the record: The problem is solved.
I went on looking for more info on this message:
Oct 14 00:07:09 schille gda: [ID 107833 kern.notice] Sense Key: ICRC error during UDMAAnd then found an interesting post from 2004 by Juergen Keil:
The "bad block detected" message appears to be an old/obsolete error
message text, somewhere in the Solaris "ata" driver.
The ATA-1 standard (1997?) defined the 0x80 bit in the IDE
controller's error register as "bad block detected". (See page 32 on
<URL:http://www.t13.org/project/d0791r4c-ATA-1.pdf>)
The 0x80 bit seems to be "reserved" (undefined, not used any more)
with ATA-2 and ATA-3.
ATA-4 and newer now defines this bit 0x80 as ICRC "interface CRC error
has occurred during an Ultra DMA data transfer" when using ultra dma
transfers. (see the description of the "READ DMA" or "WRITE DMA"
command in <URL:http://www.t13.org/project/d1153r18-ATA-ATAPI-4.pdf>).
The Solaris ata driver seems to interpret the 0x80 bit according to
the old / obsolete 1997 ATA-1 standard.
So the "bad block detected" message seems to be a hint that some sort
of data corruption is happening on the IDE interface during UDMA data
transfers with the HDD. With UDMA capable disks it apparently does
not mean "the disk drive is dying".
I went to search what could cause a hardware datacorruption on my system and found that my internal removeable disktray was making bad contact.
After replacement everything worked as expected.

Similar Messages

  • 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 x86: How to boot from Veritas mirror disk?

    Hello team,
    We are using trailware Veritas Storage Foundation (VxVM) on Solaris 10 x86 system and need help in booting from alternative boot disk(Mirror disk).
    Steps did :
    1. Mirrored the root disk group using veritas volume manager command *"vxrootmir"*
    2. Updated the bootpath with mirror disk path in /boot/solaris/bootenv.rc
    Updated the EEPROM information:
    # bootadm update-archive -R /a
    3. Edited the grub configuration file, /boot/grub/menu.lst
    Created the following entry similar to primary disk entry to allow the root disk mirror to be booted
    title Oracle Solaris 10 8/11 s10x_u10wos_17b X86 <VxVM: Alternate Boot Disk>
    findroot (rootfs0,0,a)
    kernel /platform/i86pc/multiboot
    module /platform/i86pc/boot_archive
    4. reboot -- -r
    At the time of boot, selected the newly added entry from the grub list and got the following error,
    *"Reboot and select proper boot device or insert boot media in selected device and press a key".*
    I am unable to move further from here, is this because of the veritas trial version we are using ?
    Please help in resolving this issue and also explain the step by step process of booting from alternative boot disk on a x86 machine.
    Let me know if you find anything inappropriate. Looking forward for your replies.
    Thanks in advance.

    Hi--
    I have not seen this message before but a quick google search says that is pretty common and is related to the system
    trying to boot from a different device (not the one you intended). Can you check your BIOS settings and possibly remove
    devices from the boot order setting... Otherwise, I would suggest running installgrub on the disk that you are trying to boot
    from.
    I'm curious why you are trying Veritas. Is there a Veritas feature that you need? You might consider trying ZFS if you haven't
    already. Its very simple to set up and use.
    Thanks, Cindy

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

  • Software raid won't boot after updating to "mdadm" in mkinitcpio.conf

    After a power outage I've discovetred the config I was using (with raid in mkinitcpio.conf) no longer works, it's mdadm now - that's fine.  I've updated that and re-run mkinitcpio successfully, however my system is unable to boot from the root filesystem /dev/md2 like so:
    Waiting for 10 seconds for device /dev/md2 ...
    Root device '/dev/md2' doesn't exist. Attempting to create it.
    ERROR: Unable to determine major/minor number of root device '/dev/md2'.
    You are being dropped to a recovery shell
        Type 'exit' to try and continue booting
    /bin/sh: can't access tty; job control turned off
    [ramfs /]#
    As far as I can see from reading various threads and http://wiki.archlinux.org/index.php/Ins … AID_or_LVM I'm doing the right things now (although I'm not using lvm at all, which makes the installation document a little confusing).
    I think I've included all the appropriate bits of config here that should be working.  I assume I've missed something fundamental - any ideas?
    menu.lst:
    # (0) Arch Linux
    title  Arch Linux  [/boot/vmlinuz26]
    root   (hd0,0)
    kernel /vmlinuz26 root=/dev/md2 ro
    initrd /kernel26.img
    mkinitcpio.conf:
    HOOKS="base udev autodetect pata scsi mdadm sata filesystems"
    fstab:
    /dev/md1 /boot ext3 defaults 0 1
    /dev/md2 / ext3 defaults 0 1
    mdadm.conf
    ARRAY /dev/md1 level=raid1 num-devices=2 metadata=0.90 UUID=7ae70fa6:9f54ba0a:21
    47a9fe:d45dbc0c
    ARRAY /dev/md2 level=raid1 num-devices=2 metadata=0.90 UUID=20560268:8a089af7:e6
    043406:dbdabe38
    Thanks!

    Hi magec, that's quite helfpul - I've certainly got further.
    Before I was doing this to set up the chroot (which is what is suggested in the wiki article about setting up software raid):
    mdadm -A /dev/md1 /dev/sda1 /dev/sdb1
    mdadm -A /dev/md2 /dev/sda2 /dev/sdb2
    mount /dev/md2 /mnt
    mount /dev/md1 /mnt/boot
    mount -o bind /dev /mnt/dev
    mount -t proc none /mnt/proc
    chroot /mnt /bin/bash
    But based on your suggestion it's working better
    mdadm -A /dev/md1 /dev/sda1 /dev/sdb1
    mdadm -A /dev/md2 /dev/sda2 /dev/sdb2
    mount /dev/md2 /mnt
    mount /dev/md1 /mnt/boot
    mount -t proc none /mnt/proc
    mount -t sysfs none /mnt/sys
    mount -n -t ramfs none /mnt/dev
    cp -Rp /dev/* /mnt/dev
    chroot /mnt /bin/bash
    The boot is now getting further, but now I'm getting:
    md: md2 stopped.
    md: bind<sdb2>
    md: bind<sda2>
    raid1: raid set md2 active with 2 out of 2 mirrors
    md2: detected capacity change from 0 to 32218349568
    mdadm: /dev/md2 has been started with 2 drives.
    md2: Waiting 10 seconds for device /dev/md2 ...
    unknown partition table
    mount: mounting /dev/md2 on /new_root failed: No such device
    ERROR: Failed to mount the real root device.
    Bailing out, you are on your own. Good luck.
    /bin/sh: can't access tty; job contol turned off
    [ramfs /]#
    The bit that really confuses me is this:
    [ramfs /]# cat /proc/mdstat
    Personalities : [raid1]
    md2 : active raid1 sda2[0] sdb2[1]
    31463232 blocks [2/2] [UU]
    md1 : active raid1 sda1[0] sdb1[1]
    208704 blocks [2/2] [UU]
    unused devices: <none>
    [ramfs /]# mount /dev/md2 /new_root
    mount: mounting /dev/md2 on /new_root failed: No such file or directory
    [ramfs /]# ls /dev/md2
    /dev/md2
    [ramfs /]#
    So the array is up, the device node is there but it can't be mounted?  Very strange.
    Last edited by chas (2010-05-02 11:24:09)

  • Can I install Snow Leopard and boot from software RAID 1 (mirror)?

    I have a Mac Pro (quad core 2.66 GHz) on order for my office workstation. Yeah, I know new ones are probably coming out early next year but due to budget and upcoming projects I need one now. What I'd like to do is replace the pre-installed 640GB drive with two 1 TB drives and mirror them. The 640GB drive will be redeployed to another machine in the office. Can I boot from the Snow Leopard install DVD, go to Disk Utility, setup a RAID 1 with the two drives, install Snow Leopard to the mirror and then boot off the mirror set?
    I've searched and found offhand comments to the effect that installing to and booting from a software mirror is OK, but I'd like to know for sure that it's OK. Any experience that you have with such a configuration would be nice to hear.

    Yes. But before you do read the following:
    RAID Basics
    For basic definitions and discussion of what a RAID is and the different types of RAIDs see RAIDs. Additional discussions plus advantages and disadvantages of RAIDs and different RAID arrays see:
    RAID Tutorial;
    RAID Array and Server: Hardware and Service Comparison>.
    Hardware or Software RAID?
    RAID Hardware Vs RAID Software - What is your best option?
    RAID is a method of combining multiple disk drives into a single entity in order to improve the overall performance and reliability of your system. The different options for combining the disks are referred to as RAID levels. There are several different levels of RAID available depending on the needs of your system. One of the options available to you is whether you should use a Hardware RAID solution or a Software RAID solution.
    RAID Hardware is always a disk controller to which you can cable up the disk drives. RAID Software is a set of kernel modules coupled together with management utilities that implement RAID in Software and require no additional hardware.
    Pros and cons
    Software RAID is more flexible than Hardware RAID. Software RAID is also considerably less expensive. On the other hand, a Software RAID system requires more CPU cycles and power to run well than a comparable Hardware RAID System. Also, because Software RAID operates on a partition by partition basis where a number of individual disk partitions are grouped together as opposed to Hardware RAID systems which generally group together entire disk drives, Software RAID tends be slightly more complicated to run. This is because it has more available configurations and options. An added benefit to the slightly more expensive Hardware RAID solution is that many Hardware RAID systems incorporate features that are specialized for optimizing the performance of your system.
    For more detailed information on the differences between Software RAID and Hardware RAID you may want to read: Hardware RAID vs. Software RAID: Which Implementation is Best for my Application?

  • Can I install boot camp on a machine with a Software Raid-0?

    I have a machine with a software Raid-0 running Snow Leopard. I'd like to install Boot Camp but I only have 2 SATA hard drives. Windows does not need to run in a RAID on this machine and I'm fine partitioning both drives so that I have a 30GB Windows 7 partition. Both drives are 500GB each.
    Can I partition each drive with -30GB run a software raid and still use bootcamp?
    Please let me know.

    No, and 30GB is too small for Windows 7 64-bit Pro for your Mac.
    Get a 3rd drive. Assuming this is a Mac Pro you have 4 internal drive bays.

  • Reg: Oracle 9i Enterprise Edition software for solaris x86 (32-bit)

    Hi,
    Where can i download the Oracle 9i Enterprise Edition software for solaris x86 (32-bit).
    Thanks in advance.
    Edited by: ora_man_8873786 on May 14, 2011 12:50 AM

    If you have a CSI you can always order the CD at My Oracle Support by submitting a SR.
    Sybrand Bakker
    Senior Oracle DBA

  • Solaris 10 06/06 x86 HP DL585 boot hang aftrer reboot HELP!!!

    Solaris 10 06/06 x86 HP DL585 boot hang aftrer reboot
    when I shutdown server and power on,
    solaris usually start.
    but after "reboot" (or "init 6"), boot hang on
    "SunOS Release 5.10 Version....
    Copyright ...
    Use is subject to license terms"
    HELP!!!

    try getting the Solaris x86 drivers frm HP....
    http://search.hp.com/redirect.html?type=REG&qt=Solaris+x86&url=http%3A//h18007.www1.hp.com/support/files/server/us/download/22412.html%3Fjumpid%3Dreg_R1002_USEN&pos=1
    hope it helps.

  • Server 2003 Software RAID-1 Fail - System won't boot

    Have a Windows 2003 Server with software RAID-1, and the primary drive failed.
    I tried editing the boot.ini of the 2nd drive but all I get is a black screen and blinking cursor.
    The drive had 2 partitions. One of them shows up when we plug the drive into a PC, but the 2nd partition is unrecognized.
    Boot.ini was:
    [boot loader]
    timeout=30
    default=multi(0)disk(0)rdisk(0)partition(1)\WINDOWS
    [operating systems]
    multi(0)disk(0)rdisk(0)partition(1)\WINDOWS=" "
    multi(0)disk(0)rdisk(0)partition(2)\WINDOWS="Windows Server 2003, Standard" /noexecute=optout /fastdetect
    I tried adding this after:
    multi(0)disk(0)rdisk(1)partition(1)\WINDOWS=" "
    multi(0)disk(0)rdisk(1)partition(2)\WINDOWS="Windows Server 2003, Standard" /noexecute=optout /fastdetect
    Any ideas?

    Hi,
    I would like to confirm what is the current situation? Have you resolved the problem?
    If there is anything that we can do for you, please do not hesitate to let us know, and we will be happy to help.
    Best Regards,
    Mandy
    If you have any feedback on our support, please click
    here .
    We
    are trying to better understand customer views on social support experience, so your participation in this
    interview project would be greatly appreciated if you have time.
    Thanks for helping make community forums a great place.

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

  • Cannot get software RAID-1 going on root (/) on Sun V240's

    Hi All,
    I for the life of me cannot get software RAID-1 going on the root file-system. I've followed the instructions in Solaris Volume Manager Admin. Guide and I think I'm doing it right. This is in a Sun V240 with two 137GB drives.
    I basically do the following:
    Disk0 - c1t0d0s0
    Disk1 - c1t0d1s0
    prtvtoc /dev/rdsk/c1t0d0s2 | fmthard -s - /dev/rdsk/c1t1d0s2
    prtvtoc /dev/rdsk/c1t1d0s2 (Double check that disk 1 looks like disk 2)
    metadb -af -c 2 /dev/rdsk/c1t0d0s3 /dev/rdsk/c1t0d0s4
    metadb -af -c 2 /dev/rdsk/c1t1d0s3 /dev/rdsk/c1t1d0s4
    metainit -f d10 1 1 /dev/rdsk/c1t0d0s0
    metainit -f d20 1 1 /dev/rdsk/c1t1d0s0
    metainit d0 -m d10
    metaroot d0
    lockfs -fa
    reboot
    Before I reboot, I do a metastat and it shows the following:
    # metastat
    d0: Mirror
        Submirror 0: d10
          State: Okay        
        Pass: 1
        Read option: roundrobin (default)
        Write option: parallel (default)
        Size: 20494464 blocks (9.8 GB)
    d10: Submirror of d0
        State: Okay        
        Size: 20494464 blocks (9.8 GB)
        Stripe 0:
            Device     Start Block  Dbase        State Reloc Hot Spare
            c1t0d0s0          0     No            Okay   Yes
    d20: Concat/Stripe
        Size: 20494464 blocks (9.8 GB)
        Stripe 0:
            Device     Start Block  Dbase   Reloc
            c1t1d0s0          0     No      YesUpon reboot, I get this:
    Rebooting with command: boot                                         
    Boot device: /pci@1c,600000/scsi@2/disk@0,0:a  File and args:
    SunOS Release 5.10 Version Generic 64-bit
    Copyright 1983-2005 Sun Microsystems, Inc.  All rights reserved.
    Use is subject to license terms.
    Cannot open mirrored root device, error 19
    Cannot remount root on /pseudo/md@0:0,0,blk fstype ufs
    panic[cpu1]/thread=180e000: vfs_mountroot: cannot remount root
    000000000180b960 genunix:vfs_mountroot+2b8 (18aa800, 0, 185e6f8, 3000153dc40, 1859ce8, 4)
      %l0-3: 0000000000000000 0000000000000003 00000000018a40b0 00000000018a40b0
      %l4-7: 000000000185b800 00000000011cb000 00000000018aa800 0000000001834340
    000000000180ba20 genunix:main+88 (1813c98, 1011c00, 1834340, 18a7c00, 0, 1813800)
      %l0-3: 000000000180e000 0000000000000001 000000000180c000 0000000001835200
      %l4-7: 0000000070002000 0000000000000001 000000000181ba54 0000000000000000
    syncing file systems... done
    skipping system dump - no dump device configured
    rebooting...HELP! What am I doing wrong? Thanks!

    You created to many metadatabases..
    I'm not kidding, you did. You created 8 which i suspect trigged a bug which currently exists in Solaris 9 / Solaris 10.
    This bug occours on the following disks: MAT3073N, MAT3147N, MAT3300N and ST373207LC, if you have any of those disks in your system (can be determined with iostat -En) you must use less than 8 replicas.
    Check out bugreport 6244431, if you got a sunsolve login linked to a contract number.
    You could try and boot up the system from a cdrom or similar and add "md_devid_destroy=1;" to the /kernel/drv/md.conf file above the 'Begin MDD database info' line.
    hopefully your system will come up after this, if it does the best workaround is to remove a few replicas, the above line from md.conf and reboot.
    Best regards,
    //Magnus
    Best regards,
    //Magnus

  • Mounting a Solaris x86 CD/DVD from a remote Windows CD/DVD-ROM drive

    Greetings, all.
    Is it possible to mount a remote Windows CD/DVD-ROM drive? I have the Solaris 10x86 Companion Software DVD sitting in a CD/DVD-ROM drive that's installed on a Windows server on my network. It is shared-out (F:) and the two servers can ping each other. I've also confirmed the NFS services/daemons are running on the Solaris x86 machine. I've tried the following variations but, all have failed to produce successful results:
    # mount -F nfs x.x.x.x:/f /mnt
    nfs mount: x.x.x.x: : RPC: Program not registered
    nfs mount: retrying: /mnt
    # mount -F hsfs x.x.x.x:/f /mnt
    mount: No such device
    mount: cannot mount x.x.x.x:/f
    # mount -F hsfs x.x.x.x:/F /mnt
    mount: No such device
    mount: cannot mount x.x.x.x:/F
    [FYI: S10_106_SOFTWARE is the DVD's label as reported by Windows Explorer.]
    # mount -F hsfs x.x.x.x:/S10_106_SOFTWARE /mnt
    mount: No such device
    mount: cannot mount x.x.x.x:/S10_106_SOFTWARE
    # mount -F hsfs x.x.x.x:/s10_106_software /mnt
    mount: No such device
    mount: cannot mount x.x.x.x:/s10_106_software
    # mount -F nfs x.x.x.x:/S10_106_SOFTWARE /mnt
    nfs mount: x.x.x.x: : RPC: Program not registered
    nfs mount: retrying: /mnt
    # mount -F nfs x.x.x.x:/s10_106_software /mnt
    nfs mount: x.x.x.x: : RPC: Program not registered
    nfs mount: retrying: /mnt
    # mount -F hsfs x.x.x.x:/f/s10_106_software /mnt
    mount: No such device
    mount: cannot mount x.x.x.x:/f/s10_106_software
    # mount -F hsfs x.x.x.x:/F/s10_106_software /mnt
    mount: No such device
    mount: cannot mount x.x.x.x:/F/s10_106_software
    # mount -F hsfs x.x.x.x:/f/S10_106_SOFTWARE /mnt
    mount: No such device
    mount: cannot mount x.x.x.x:/f/S10_106_SOFTWARE
    # mount -F hsfs x.x.x.x:/F/S10_106_SOFTWARE /mnt
    mount: No such device
    mount: cannot mount x.x.x.x:/F/S10_106_SOFTWARE
    I've also tried mounting it at bootup by adding the appropriate entry in the /etc/vfstab file but, this does not work as well. I've tried Google'ing for an answer to my issue but, I haven't been able to find anything that applies directly to what I'm reporting. It's usually chatter about mounting from one UNIX server to another. Any advice from the community would be greatly appreciated.

    After three weeks, you deserve a reply. Windoze does
    not natively support NFS.Also deserves a decent answer...
    There are two ways to do this:
    Install Microsoft's free "Windows Services for UNIX," which includes a Windows NFS server; or
    Install the 'sharity' package (google for it); it provides Solaris systems the ability to mount Windows shares

  • I have some questions regarding setting up a software RAID 0 on a Mac Pro

    I have some questions regarding setting up a software RAID 0 on a Mac pro (early 2009).
    These questions might seem stupid to many of you, but, as my last, in fact my one and only, computer before the Mac Pro was a IICX/4/80 running System 7.5, I am a complete novice regarding this particular matter.
    A few days ago I installed a WD3000HLFS VelociRaptor 300GB in bay 1, and moved the original 640GB HD to bay 2. I now have 2 bootable internal drives, and currently I am using the VR300 as my startup disk. Instead of cloning from the original drive, I have reinstalled the Mac OS, and all my applications & software onto the VR300. Everything is backed up onto a WD SE II 2TB external drive, using Time Machine. The original 640GB has an eDrive partition, which was created some time ago using TechTool Pro 5.
    The system will be used primarily for photo editing, digital imaging, and to produce colour prints up to A2 size. Some of the image files, from scanned imports of film negatives & transparencies, will be 40MB or larger. Next year I hope to buy a high resolution full frame digital SLR, which will also generate large files.
    Currently I am using Apple's bundled iPhoto, Aperture 2, Photoshop Elements 8, Silverfast Ai, ColorMunki Photo, EZcolor and other applications/software. I will also be using Photoshop CS5, when it becomes available, and I will probably change over to Lightroom 3, which is currently in Beta, because I have had problems with Aperture, which, until recent upgrades (HD, RAM & graphics card) to my system, would not even load images for print. All I had was a blank preview page, and a constant, frozen "loading" message - the symbol underneath remained static, instead of revolving!
    It is now possible to print images from within Aperture 2, but I am not happy with the colour fidelity, whereas it is possible to produce excellent, natural colour prints using its "minnow" sibling, iPhoto!
    My intention is to buy another 3 VR300s to form a 4 drive Raid 0 array for optimum performance, and to store the original 640GB drive as an emergency bootable back-up. I would have ordered the additional VR300s already, but for the fact that there appears to have been a run on them, and currently they are out of stock at all, but the more expensive, UK resellers.
    I should be most grateful to receive advice regarding the following questions:
    QUESTION 1:
    I have had a look at the RAID setting up facility in Disk Utility and it states: "To create a RAID set, drag disks or partitions into the list below".
    If I install another 3 VR300s, can I drag all 4 of them into the "list below" box, without any risk of losing everything I have already installed on the existing VR300?
    Or would I have to reinstall the OS, applications and software again?
    I mention this, because one of the applications, Personal accountz, has a label on its CD wallet stating that the Licence Key can only be used once, and I have already used it when I installed it on the existing VR300.
    QUESTION 2:
    I understand that the failure of just one drive will result in all the data in a Raid 0 array being lost.
    Does this mean that I would not be able to boot up from the 4 drive array in that scenario?
    Even so, it would be worth the risk to gain the optimum performance provide by Raid 0 over the other RAID setup options, and, in addition to the SE II, I will probably back up all my image files onto a portable drive as an additional precaution.
    QUESTION 3:
    Is it possible to create an eDrive partition, using TechTool Pro 5, on the VR300 in bay !?
    Or would this not be of any use anyway, in the event of a single drive failure?
    QUESTION 4:
    Would there be a significant increase in performance using a 4 x VR300 drive RAID 0 array, compared to only 2 or 3 drives?
    QUESTION 5:
    If I used a 3 x VR300 RAID 0 array, and installed either a cloned VR300 or the original 640GB HD in bay 4, and I left the Startup Disk in System Preferences unlocked, would the system boot up automatically from the 4th. drive in the event of a single drive failure in the 3 drive RAID 0 array which had been selected for startup?
    Apologies if these seem stupid questions, but I am trying to determine the best option without foregoing optimum performance.

    Well said.
    Steps to set up RAID
    Setting up a RAID array in Mac OS X is part of the installation process. This procedure assumes that you have already installed Mac OS 10.1 and the hard drive subsystem (two hard drives and a PCI controller card, for example) that RAID will be implemented on. Follow these steps:
    1. Open Disk Utility (/Applications/Utilities).
    2. When the disks appear in the pane on the left, select the disks you wish to be in the array and drag them to the disk panel.
    3. Choose Stripe or Mirror from the RAID Scheme pop-up menu.
    4. Name the RAID set.
    5. Choose a volume format. The size of the array will be automatically determined based on what you selected.
    6. Click Create.
    Recovering from a hard drive failure on a mirrored array
    1. Open Disk Utility in (/Applications/Utilities).
    2. Click the RAID tab. If an issue has occurred, a dialog box will appear that describes it.
    3. If an issue with the disk is indicated, click Rebuild.
    4. If Rebuild does not work, shut down the computer and replace the damaged hard disk.
    5. Repeat steps 1 and 2.
    6. Drag the icon of the new disk on top of that of the removed disk.
    7. Click Rebuild.
    http://support.apple.com/kb/HT2559
    Drive A + B = VOLUME ONE
    Drive C + D = VOLUME TWO
    What you put on those volumes is of course up to you and easy to do.
    A system really only needs to be backed up "as needed" like before you add or update or install anything.
    /Users can be backed up hourly, daily, weekly schedule
    Media files as needed.
    Things that hurt performance:
    Page outs
    Spotlight - disable this for boot drive and 'scratch'
    SCRATCH: Temporary space; erased between projects and steps.
    http://en.wikipedia.org/wiki/StandardRAIDlevels
    (normally I'd link to Wikipedia but I can't load right now)
    Disk drives are the slowest component, so tackling that has always made sense. Easy way to make a difference. More RAM only if it will be of value and used. Same with more/faster processors, or graphic card.
    To help understand and configure your 2009 Nehalem Mac Pro:
    http://arstechnica.com/apple/reviews/2009/04/266ghz-8-core-mac-pro-review.ars/1
    http://macperformanceguide.com/
    http://www.macgurus.com/guides/storageaccelguide.php
    http://www.macintouch.com/readerreports/harddrives/index.html
    http://macperformanceguide.com/OptimizingPhotoshop-Configuration.html
    http://kb2.adobe.com/cps/404/kb404440.html

  • Oracle 8.1.5 Client/WLS/Solaris x86

    has anyone been able to get Oracle's client 8.1.5 running on Solaris x86 in conjunction with WLS to talk to back-end Oracle? Any help would be greatly appreciated.thanks.

    This will not work. We have not built the native libraries to work with
    Solaris on Intel..
    I suggest trying the platform independent type 4 JDBC driver available for
    free from Oracle. It is supported (as is any JDBC driver) with WebLogic
    Server. To download it:
    Go to http://www.oracle.com and select the "Download" option.
    From the resulting page, use the "Select Utility or Driver" dropdown to
    select Oracle JDBC drivers
    From the resulting page, scroll down a little (since SQLJ stuff appears at
    the top).
    Or, to go directly there:
    http://technet.oracle.com/software/tech/java/sqlj_jdbc/software_index.htm
    Thanks,
    Michael
    Michael Girdley
    BEA Systems Inc
    "Dean Davis" <[email protected]> wrote in message
    news:3a267487$[email protected]..
    has anyone been able to get Oracle's client 8.1.5 running on Solaris x86in conjunction with WLS to talk to back-end Oracle? Any help would be
    greatly appreciated.thanks.

Maybe you are looking for