Filename problem with RAID

All,
We have a problem with our Xserve RAID with regards to the way files are named. For example we have a file called "081bSelecting_SkyArea#18.tif" which will not copy to our RAID. If i was to copy this to our Xserve it would be fine, but as soon as it goes down the Fire Channel it says we have the incorrect permissions. As soon as i rename the file it works fine.
I under stand from the link below that there has been issues like this in the past with 10.2, but i am unable to find anything with regards to 10.3 server which is what we are using.
http://docs.info.apple.com/article.html?artnum=107144
Many thanks for your time.
Darren Senadhira

Not sure. That bug you're referring to has to do with file sharing (e.g. AFP or SMB), it doesn't say anything about direct-connected fibre channel.
Wish I had a server with RAID attached to tinker with this right now, but alas I don't at the moment. Any chance you can avoid using the #xx at the end of the file names?

Similar Messages

Anyone else having problem with RAID and iTunes syncing photos in Vista?

Hello,
For whatever reason iTunes can not load some of the photos from C drive. It can do it from D drive, though VERY slow. Both C and D are NTFS system, but C is a RAID 0 drive (implemented by hardware on motherboard, Intel 82801G controller). I just wander if this is something related to iTunes not working correctly with RAID drivers, or is it something else? I should say that ALL other programs and games working fine on this drive.
Thanks for the replies.

The problem is with Windows Vista using the NTFS file system, check out this post for the official solution. This has worked perfectly for me everytime I've tried it:
http://i.nconspicuo.us/2007/10/28/syncing-photos-to-iphone-with-windows-vista-us ing-itunes-sync-pictures-solution/

License problems with RAID systems

We are running a Labview vision 8.0 application on a XP SP2 system with RAID controller. The purpose is to be able to quickly recover from any harddisk problems. Do I have to reactivate the licenses when I swap the harddisks?

Hi,
As your RAID controller is just an external harddrive, the vision license is essentially running on the same machine so the same license can be used on different controllers.
There's no need to deactivate for each controller, as long as the license is being used on one system I don't believe you would be violating the licensing agreement.
Sarah
Applications Engineer | National Instruments | UK & Ireland

Interesting problem with RAID, Windows 2008 server, and Ubuntu

sooooo, i got the system working and linux loved it. just adored it.
however, Windows did not. Windwos 2008 server hard locks from time to time. i fianlly figured out that it had to do with the RAID 0 i was running, that didn't really succeed.
However, when i rebuilt the RAID and everything on it, it refuses to recognize the disk, sayign that windwos cannot determine if this drive has a valid system volume on it.
Ubuntu 9.04 server, however, just took it and made it work great.
I enabled the PCI Bus SATA to be Master in the BIOS, and then Windows Server 2008 said that it could not determine if the drive was bootable. Then i went back and redid the raid, and it did the original error.
I inserted a windows xp disk, destroyed the RAID, and then installed the software on a NEW disk. While it installed fine, it gave me an IRQL_not_less_than_or_equal error. It boots in safe mode, but no where else. I tried installing the NVRAID and MCP55 drivers in safemode and what not, but still, it refused to cooperate. I went back to ubuntu, this time the desktop/workstation versions, and i am doing an alternate install with RAID...much to my disappointment becuase now i will have to use VirtualBox to isntall windows...and if that fails, i'll be really pissed.
My settings are as follows:
SATA Controller 0-5 enabled
NVRAID- enabled
PCI BUS SATA- Option ROM Enabled, Master Enabled, and 0040h latency
MAC LAN- same as above
MAC LAN1- has master disabled, but the other stuff is the same
Serial port A is on AUTO, B is disabled, and floppy is disabled.
Option Rom is PFA relocation.
Also, my AEC A6880 is giving me a ROM expansion error, even though, in both OSes it can be seen....usualy. I just want to fix it
lastly, my LSI PCI-E scsi adapter is not being seen at ALL.
thanks guys.

Quote
Also, my AEC A6880 is giving me a ROM expansion error, even though, in both OSes it can be seen....usualy. I just want to fix it
lastly, my LSI PCI-E scsi adapter is not being seen at ALL.
Turn off onboard raid ctrl 1st. There are conflicting.
Quote
I enabled the PCI Bus SATA to be Master in the BIOS, and then Windows Server 2008 said that it could not determine if the drive was bootable.
Known issue, partition mess:
http://www.google.bg/search?hl=bg&ei=W-l3Sq_4NMbdsgbHnKmmBQ&sa=X&oi=spell&resnum=0&ct=result&cd=1&q=windows+cannot+determine+if+this+drive+has+a+valid+system+volume+on+it.&spell=1
Quote
I inserted a windows xp disk, destroyed the RAID, and then installed the software on a NEW disk. While it installed fine, it gave me an IRQL_not_less_than_or_equal error. It boots in safe mode, but no where else. I tried installing the NVRAID and MCP55 drivers in safemode and what not, but still, it refused to cooperate.
What's the BSOD error? Are you using XP installation disk with included SP3?

Disk Priority Problem with Raid

I have MSI K8N Diamond (Bios version: 1.9)
Here's my problem:
I've got total 4 hard disks. Those are plugged to sata ports
(not to silicon ones, 2 silicon ports are free) also i got no hdd on ide, just a dvd burner
I've planned to create a raid0 array from my WD drives 36x2 with Nvidia raid:
RAID0
1. WD Raptor SATA 36GB
2. WD Raptor SATA 36GB
NONRAID SATA
3. Seagate SATA 300GB
4. Seagate SATA 300GB
Here are the steps that i followed:
1. Enabled nvraid from bios, (just enabled the 2 drives which i'm gonna strip)
2. Set hard disk priority to
1>NVRAID
2>SEAGATE
3>SEAGATE
3. Created raid0 and hooked my both WD drives (f10)
Everything is fine, windows starts to install. Problem just begins after this.
After windows licence agreement (f8) where u choose the disk to install windows, setup tries to install windows on E:
C: Seagate
D: Seagate
E: My NVRAID Stripe => why the hell is it E???
But I set my hdd priority in bios and set the NVRAID first priority as i mentioned earlier.
Why is this priority setting been ignored?
The only workaround i found is removing the Seagate drives physically, then install windows on nvraid as C:
why the hell i must remove my drives everytime i install windows, is there a proper way?
P.S. Same thing happened with silicon raid, so i think this is not a nvraid issue

Halloween,
You may very well be correct, I use an add-in High Point RAID Controller in most of my systems, as you can see in my signature and have one problem from the very start.
When I have the High Point RAID Controller Plugged in, it does not matter which PCI-Express slot I use and the motherboards secondary RAID Controller is Enabled in BIOS the system while not boot. This happens with my K8N Neo4 Platinum and my Diamond Plus motherboards. They have made changes to the BIOS on the Diamond Plus, but the K8N Neo4 Platinum motherboards are still that way and I can not use the Silicon Image RAID Controller on those MB’s yet and its been over four months now. You my have uncover another bug in the BIOS, on these same lines.
You really should get the problem on record with them. Have you used their new nZone trouble reporting system yet. It a lot easier to use than the e-mail help request system. Here is the link to the web site
http://support.msi.com.tw/techSptlogin.php and they have been fixing problem through this system. I have gotten two BIOS fixes so far and they keep list of your request on hand with there current status so you just check every day and answer what questions they have or download and test a fix, which some times and some times do not work. Your respond to the fix or questions and the normally respond within one three days one-way or another. I like it because I can give them a blast on any request I have not heard from them on in a reasonable length of time and a complete transcript of the your messages to and from them is right there for you to refer to if you need it.
Roger
When submitting a problem, include a complete list of your system components; include part numbers, all Power Supply Voltages, and their output ratings. It is almost impossible to estimate what your problem is without knowing something about it.

Problems with raid 0

i have 3 sata's on ports 1, 2 and 3 and i create the array fine,
all sata options in bios are enabled,
when i install xp it loads really slow and i install both drivers off the floppy and then it starts loading the install files really slowly then it hangs at "starting windows"
im using bios 1.4 and the drivers that came with the mobo, i tried using the ones out of the latest nvidia 5.10 package but they wont all fit on a floppy
any ideas?

That sounds like a raid0 problem. No doubt about that. If I were you I would wait for someone like syar2003 to chime in here and help you out. I'll try and give my suggestions but I don't know how much help they'll be.
If you know for a fact that you gain disk performance with three drives in a raid0 array then I would disregard everything I'm about to say: I've never heard of a raid0 array with three drives. I didn't know you could have a raid0 array with three drives. Obviously, this does not mean that you can't do it, it just means I didn't know you could. I've heard of mirrored arrays with two active drives and one inactive backup because I set my machine up like that. Try putting the two drives on ports 3/4. Forget about the third drive, I don't think it's help. Disable the controller and raid all together on ports 1/2 (in other words, just disable ports 1/2 wherever possible). Then update nVRaid for your new two drive array and try again. This should fix your problems.

Problem with raid set on xserve

Hi to all!
I hope you can help me with a big problem that I have with a Xserve of the work.
Yesterday afternoon I come to the work and my partners mentioned to me that the web pages were not going. I tried to connect with ARD but he was not answering. I had to move to the building where the server is racked and when I connected a monitor a it was showing me a folder icon with an interrogation icon.
Since this had happened to me in my Mac of the office once, I initiated from the installation DVD to see if I could repair permissions and/or the discs with the Disk Utility. For my surprise (and terror) does not show any volume or disk except the DVD.
I got into the RAID Utility in the menu and there I could see the discs but the RAID Sets does not appear... We had mounted since we install the machine a raid 5 with 3 discs and 2 volumes on this raid set.
Then, from the Terminal, doing "diskutil list" it's show no volume on any disk.
I suppose that something has happened with the volumes and the raid cannot be mounted...
Is there any way to mount the volumes again? Something similar to the "fixmbr" that I believe that there are in others OS to restore the volumes tables...
Is there any way to mount again the RAID without losing the information from the discs?
Do you know that can be happening?
PS: It is a Xserve of the last ones, with Mac OS X 10.6.8. I have already tried to reset the PRAM and it keeps on doing the same.

The Server Monitr does say anything. It doesnt pick up any server. I tried to add the XServe in the Server Monitor, but it keeps waiting for a reply after I have put in the username, password and IP address.
It is an XServe with a Mirror software RAID on the 2 x Internal Hard Drives within the XServe
I am not using the SAN software
There have been reports of fault latchs on the Apple Drive Bay Modules. Do you think this could be causing the units to dismount?

KT3 Ultra2 (problems with raid).

I have 4 80gb hard drives set up on my pc, and am trying to set them up as plain jbod drives, but the fastbuild utility that creates the arrays wont allow me to do anything besides a 1+0 stripe. Ive looked around for information on the controller itself (mbfasttrak133 lite), and really cant find anything useful on it at all. The 1+0 stripe seems to result in 4 80gb hard drives, but ive heard that if one drive fails in this setup, ill lose the info on 2 drives.
My specs:
Windows 2k Pro SP4
4 Seagate 7200 rpm 80gb (ST380021A) drives (2 hard drives on ide1, and 2 hard drives on raid1)
AMD Athlon XP 2100+ (1.753ghz)
1024 MB DDRAM
GeforceFX 5600 256MB

That could be a problem then, my board just came with the standard kt3 ultra2 manual, and a few cool extras (some kind of cut out), but no manual on raid, and nothing in the kt3 manual about raid beyond a basic description.

Problems with RAID and a Flash USB Drive

I'm attempting to install on a RAID 1 array using just one usb flash drive. Yes, just one. I'm trying out the idea's in this thread: http://bbs.archlinux.org/viewtopic.php?id=64281
Partitioning scheme:
sdb1 -> boot partition
sdb2 -> swap
sdb3 -> raid 1 array -> root
I set the partitiions to type 0xfd (linux raid autodetect) in fdisk (probably not necessary) and created the array with:
mdadm -C /dev/md0 -n 2 -l -b internal missing -W --write-behind /dev/sdb3
I then installed like normal, specifying that I needed usb and raid hooks in mkinitcpio.conf
I added "md=0,/dev/sdb3" as a kernel option in grub's menu.lst, specifying that the md driver should assemble /dev/md0 (my root partition) out of /dev/sdb3 before trying to mount it.
This process was succesful using a partition on my hard drive.
However, using a usb drive causes a kernel panic during boot when trying to mount /dev/md0.
Looking at the messages reveals that before my usb drive was detected, md attempted to create the array, unsuccessfully, as /dev/sdb didn't exist yet. "md: unkown device name /dev/sdb3" or something to that effect.
In mkinitcpio.conf, the usb hook comes before the raid hook, so this shouldn't be happening, should it?

I think rootdelay will not work in that special case, rootdelay makes the system to wait after all the hooks are executed, and you need to wait before executing the raid hook.
I don't know if there is an easy way for that, but one solution is to modify the raid hook to wait for /dev/sdb3 to be created :
- edit /lib/initcpio/hooks/raid, add this before the /bin/mdassemble command :
until [ -e /dev/sdb3 ] ;
do
sleep 1 ;
done
- rebuild your boot images with mkinitcpio (you'll need to chroot to your system)
that should work
PS: someone correct me if I'm wrong, but from what I know, the usb hook does not create your /dev/sdb (if you edit the usb hook, you'll see that it only set rootdelay if it is not yet set). it is the udev daemon, which is launched in the background by the udev hook, and the udev daemon is quite long to create USB device nodes.

Firmware update problem with raid mirrored drives and solution

Note this - the firmware update will not install from a software mirrored boot drive. It will install just fine from a non-mirrored clone. So, make a clone, set it as your boot drive from system preferences, and all is good.

Well this is a pain, this is what I figured I would have to do but c'mon apple, I am sure people are not going want to hassle with making a clone, finding or buying a single drive to install the OS to, boot that drive, install the firmware patch, reboot, make sure it took, tear down the system, swap the soft-RAID set of drives back in etc. etc. etc.
This is another reason why Apple need to take note from the PC world, I know they like to "Think Different" when it comes to things like this but they really need to give access to and write a driver for the supported on-chip hardware RAID controller located in the Motherboards Southbridge chip of THIS motherboard, just like all other woodcrest Xeon based systems running the same intel motherboard chipset!
I am sure this post will get me a long list of flames from the Apple fanboys explaining how what Apple is doing is really better, or telling me that if I want hardware RAID 5 to just go and buy $6000 xServe RAID setup.
Well I better quit typing so I can tear apart my system, find a hard drive to install OSX on.....See you guys in a few hours

990xa-gd55 win7 install problem with raid

I have 990xa-gd55 just got it today as my other board had a problem seeing 3 HDD.
I have the bios set up in raid mode, I have my raid array set up. But when I install windows it copies the files and extracts them then, bsod's on restart and can continue install.
I have a 128 Samsung ssd that I want it installed on and it is not part of the raid I have 2 1 TB drives that make up the array. I hope i'm just forgetting something easy any help is appreciated.

Well, I'd make sure you have the boot options manually set to which array you have your OS on. Hit F10 as the machine boots and check out your options there. It should give you an option somewhere to select which RAID array to boot off of, although I can't remember if it's in BIOS or the Nvidia boot agent at the moment.

Filename problems with packages

problem.
We created Incopy packages from a file example.indd
We then for various reasons changed the name of the file to newexample.indd
Now we are having problems bringing the incopy files back into the file.
I can see why we we might be having problems, but the obvious solutions (changing the names to match) do not seem to be working.
any recommendations?

> Have we put rotten apples in our barrel?
LOL ... no, you should be fine. The Package workflow automates exactly what you did manually. It's just not a good idea to rename any files part of an InCopy workflow, as Bob says. It's a little fragile that way. If you do rename files, then you need to tread carefully and fix/update things manually.
You should make a feature request for InDesign that the "Locate original file" for returned InCopy workflow packages should accept renamed INDD files as well as moved ones.
AM

Problem with RAID drive purchased from Apple.

A RAID drive I purchased from Apple is not functioning- something about the battery. Can anyone explain this to me?
Thank you in advance!

Tom,
Some more information would help. Make, model, etc. Also, what exactly is the message? Is it an Alert? What does the console say?

Raid0 problem with K8N NEO4 F1

I have had some strange problems recently after running with complete stability for a couple of months.
1. On booting up in the morning Windows XP Pro has failed to load. Only a MBR repair or image backup worked.
2. Problems with Raid on boot occurred with 1. No array warning and only one disk showing up after deleting array.
I have :-
1. Run Memtest from Dos with no errors.
2. Run WDDIAG on both disks with no errors
3. Checked temperatures. All less than 45
4. Checked power voltages etc - all good
5. Re-flashed the bios from DOS.
6. First thing I did was turn off overclocking btw.
I have changed to RAID1 mirrored drives and things have been absolutely stable for a week. I even have the impression that the system is running faster!I have all the latest drivers installed. My feeling is that this is a bios or chip related problem though there are stories of XP fouling up the MBR when at the 137GB limit, I don't think these apply.
Any comments would be appreciated.
Thanks

Meditek,
First would like to go over your CD boot problem, because this totally a BIOS problem and Windows and its drivers not in the picture. Therefore, I would like to make sure the BIOS running correctly and stably, before we get look at startup or running of Windows has problem. BIOS Has problem Windows is going to have problems.
The drive boot sequence; If you have a drive boot sequence of (1) Floppy Drive (2) CD Drive (3) Hard Drive and you have no disks in the floppy or CD drive the BIOS should not hang on the Floppy or CD Drive if the is not disk in them or should I give any type of air message.
What I am getting from reading between the lines in your messages is that whenever you need to boot from a drive you are manually placing list in the boot priority less. Please inform me, if I am wrong?
I would like you to set your boot priority list like the one I listed above, that (1) Floppy Drive (2) CD Drive (3) Hard Drive. If the is any other devices list place them after the Hard Drive. Then go to your list of hard drive and insure the drive/Array with Window in stalled on it is first on the list, this tell the BIOS and Windows It is the Windows Boot device.
Next, the CMOS Backup Battery, 2.89V is on the edge of being weak and we need to Totally Eliminate it as a problem. I just took batteries of old motherboard that have been setting on the self for three to five years that read to same or higher. So, get a new replacement battery the measures 2.950 or better. Your current battery if you were having not problem I would you could still use it, but have a new on hand.
A new battery will measure over 3 volts.
Now, like take a look at the BIOS MOS reset procedure you are using. I myself and others I have been in communications with have been having problems with procedure listed the Manual not completely clearing the CMOS Memory. Leaving trash in some of the BIOS parameters, some of which are not even list so you do not your have completed a good total clearing of the BIOS and this alone can lead to some real weird problem that are imposable to trace to a cause. Another MSI Form member gave me this procedure. This procedure insures the there is no power let in the system to defeat your attempt to clear the clear the BIOS parameters.
(1)   Unplug the AC Plug cord from the computer.
(2)   Remove the Battery. If your like me and has always struggled with get the little battery out when buried behind and under cables in between I/O cards. Get a small pair of needle nose priers and press the two metal tabs together that make up the retaining clip. Now this first time you do this it will surprise you, because if there is nothing it its way the spring contact behind it will pop it out with enough force to send it flying. If you power supply is mounted in the bottom of your case, put paper over the grill, because if the battery goes in there you are in for at lest 12 pack day.
(3)   With power, unplugged and the battery remove press the BIOS clear button and the Power switch and holed them for twenty to thirty seconds.
(4)   Then, let the system set for as long as you have patience, at lest thirty minutes.
(5)   Again, press the BIOS clear button and the Power switch and holed them for twenty to thirty seconds.
(6)   Reinstall the battery and plug the power back in.
(7)   Boot the system to the BIOS to BIOS Default Values, Save and Exit.
(8)   Reboot to BIOS Setup Routine and Set all Bios parameters to the normal system operating parameters, save and exit.
Note: Do not setup your system for any over-clocking, but check you memory default setting to insure the BIOS is setting them correctly. Mine sets the default memory voltage to below the manufactures spec.
(9)   Reboot the system to the BIOS setup routine, YES again, rechecks that all of you normal system operating parameters save and exit.
(10)    Check and insure there are no disks in the Floppy or the CD, if there are remove them.
(11)    Now when the system reboots it should not hang on the floppy or CD and the should be no error messages unless Windows itself has problem startup.
Now, when you have all that done, reply and let me know how you system is operating.
And that all for today, my communication center between my right and left brain is about a tenth the of normal and this has been working it on over load for about of about two hours, so time for med’s and a nap.
Roger
When submitting a problem, include a complete list of your system components; include part numbers, all Power Supply Voltages, and their output ratings. It is almost impossible to estimate what your problem is without knowing something about it.

KA 790 GX M, have problem with RAID5

Pls help me, i have 3'd time problem with RAID. First two time's i simply reinstall vista. Now, i can't.
Maybe was something with my datacable on 1 of 3 HD's in SATA RAID5 ,
i change this cable & power cables on disks (maybe were broken).
So, now all 3-re HDD works well. They shows when i set up RAID option to IDE.
So all three HDD's then shows in BIAS post.
When i try to set up RAID to RAID, array loads ... but RAID bios shows one of this Three disks as standalone disk, not connected to RAID!
I.e. it is inside the array, but is not initialised. I can'd describe this in few words :( Maybe i need make screenshoot if anybody can't help me.
What i need... i need HELP!
have 1.0 Tb of information on this raid array, so i can't simply reboot & reinstall all.
Maybe there is simple way to correct state of this array disk? I.e. like it is changed to new one?
Now initialise this disk?
Pls help me.

Hello!
Please list your computer things: processor, memory, and PSU for example.
I'm not very good at RAID. Have you possibly changed SATA port? 1-5 should work well together.

Filename problem with RAID

Similar Messages

Maybe you are looking for