Xserve not recognising LaCie RAID

I have a very strange issue with a LaCie 4Big Quadra RAID.
The device used to be attached to our Xserve (10.6.8 server) as part of a mirrored Raid of two hardware RAIDs, and had been function fime for some months. Recently I added some more RAM to the Xserve as CrashPlan, which we use for running backups was creating huge swapfiles and filling the startup disc. So, to add the RAM all attached drives were ejected, all users disconnected and RAM installed. Drives were reconnected and users carried on working as if nothing had happened.
A couple of days later I spotted on Disk Utility thet the RAID was degraded - the LaCie was 'missing' from the mirrored RAID. No sign of it on Disk Utility.
Strangely when connected by Firewire to my MBP (10.9.2) it mounted and the information stored on it was visible. Reconnected it to the Xserve - still now sign of it. Connected it to an iMac which is also running 10.6.8 server and it mounted quite happily there.
In discussion with LaCie technical support I wiped the RAID, reformatted as RAID 0, then back to RAID 5 all while connected to my MBP and then initialised it. Have tried all formats and partition maps, but it is still not recognised by the Xserve. We actually have two Xserves and it is not recognised by the newer one either. The only reference one can see is in System Profiler where it shows up as an Unknown Device in the FireWire Device Tree.
I have also tried connecting by USB as well as FW 800.
Does anyone have any idea what is going on and how I can get the drive to be recognised again by an Xserve?
Thanks for any assistance.
Huw

adam taylor1 wrote:
As the data is backed up, I am not worried about having to re-format the entire Raid. When (and if) I do - what is the best way to configure the set-up for video work and retain the Raid 5?
That is a loaded question It all depends on a nearly infinite number of details. What type of video are you shooting in? DV, HD compresses or uncompressed, etc. How is the storage used in your workflow? Ingest, editing, play out. How many people are connected to it and how do they connect? Is this direct connect? Is it a reshare over AFP? Are only project files kept there and all ingest/cutting is done on the workstation? And those are just the tip of the iceberg.
Here are some basic suggestions. RAID 5 is the best format for relative safety of your data. However, the nature of the XRaid design is that you end up with two independent volumes. So say you have 14 500 GB drives. This is 7 TB of raw storage. Doing a Raid 5 on each side, no spare, will yield 3 TB (about 2.7 TB formated). On top of those formats, the unit can be software raided into a raid 50 (two raid 5s striped) or 51 (two raid 5s mirrored). These are tenuous as you've discovered. The later is wasteful as you throw 7 TB of raw storage at a volume that yield 2.7 TB of usable space. In high availability/redundancy situations this makes sense. But the amount of data that needs that level of protection is probably pretty small. The other option, which is what I guess happened to you, is taking the two raid 5s and striping them together. The only benefit here is that you get what appears to be a single volume spanned across the two controllers. There is a perceived speed benefit here and since you mentioned video workflow, that may explain the decision. However, unless you are doing ingest, this formating likely makes no sense.
Hope this helps

Similar Messages

MBP does not recognise Lacie external Hard drive

hi,
I have a couple of 4-5 year old lacie 500 gig ext hard drives which now do not show up when plugged into the mac Book pro 2.8 intel duo core. I have used them only a couple of months ago no problems.
thank you

Older hard drive partitioning schemes will not show up on newer Mac OS systems. One file will show up stating "where did all my files go" or the equivalent. Of course the drive must be mounted first and sometimes a third party utility like disk warrior or drive genius must be used. To start up from any new external hard drive in system 10 or above the GUID partition scheme must be employed. If you will never boot from your external drives you can format as Mac Os extended (journaled) without checking the GUID box. Hope this helps as well.

XP Setup not recognising RAID

Hi
Having just decided to rebuild my system, I have now found that my RAID is not being recognised in Windows XP setup. This has all been working for me previously without a problem. I am using the same drivers I have always used, either on a floppy drive, or with an nlite build. The RAID itself is showing as HEALTHY, BOOTABLE=N/A and everything seems to be working correctly. When Windows XP setup loads it identifies two seperate 75Gb drives, as opposed to the 150GB Stripe that I would expect. I have reset the BIOS, and recreated the RAID several times.
I know it was tricky getting this all to work the first time I did it, but I can't work out if there is something I have forgotten to do. Should the RAID be bootable, or is this not important? I'm pretty sure the XP setup process is ok, but I can't figure out what else it could be. Any advice would be appreciated. Thank you.
Steve

Hi Bas
Sorry about that, it's partly cos I'm mostly doing this from work, and I can't remember. and partly because I know if I let myself I would write you pages and pages and bore you to tears. Also I know that this worked previously and the only thing I have really changed since the last time I did this is my Graphics Card. I now have a 4850HD ATI (gone from 1950x and with 1Gb instead of 512Mb) My Hard Drives are 2x WD800JDs (http://wdc.custhelp.com/cgi-bin/wdc.cfg/php/enduser/std_adp.php?p_faqid=1228) . The PSU is a 400 Watt Winpower ATX-400. I also run a couple of small fans inside. There was a DVD Burner and a CD BURNER, but I just run the DVD at the moment.
TBH go_for I am not sure about the BIOS versions, I would have flashed it when I got the machine, but the new one would be the latest. But the problem started before I changed it over...
Here I will try and give you the full story....
It started when Firefox got really slow, at first I thought internet speed, but download was fine. Tried removing all the add-ins, reinstalling clean. I even used IE for a while. Eventually I got a Windows lack-of-anti-virus warning even though AVG was working fine. I had also been having issues with CMOS settings, I had thought this was the battery and replaced it but it came back later.
I figured it was a virus and decided to rebuild. I used an nLite build that I had created a while ago. The rebuild went skew. I don't remember why, I ended up stripping down and removing bits. Including taking out the graphics card to remove dust, somehow I managed to damage it, the second 1950x I have fried, either cards are much more sensitive these days, or these are particularly so. Managed to get a powercolor 4850HD 1Gb for £80 from Maplin, which I was quite pleased about at short notice. I was in a hurry to get back to Dragon Age. Rebuilt the machine, no problems, except something happened right at the end, I wasn't here to see what, Windows booted no problem, but it hadn't set up my start menu programs. I lived with it for about a week or so. Then I turned it on, and there were problems with Windows and I think BIOS messages. I tried to rebuild again, discovered that the Windows setup no longer recognised the RAID. I also got errors about BIOS when I tried to boot ubuntu and WinPE (but these turned out to be normal) so I wondered if my BIOS was faulty or corrupted. I ordered a new one from eBay, thought this would fix everything. But when I put it in the same issues came back.
I know that when I first got the RAID disks it took ages to work out what was wrong. But I did figure it out in the end, after I searched around for a bit, but that was a long time ago, and I don't remember what I did. I know that the BOOTABLE option was an issue but I can't remember if I resolved it, or if it turned out to be irrelevant. I also remember loads of hassle with the RAID drivers on XP, as I don't normally have a floppy drive in my machine, I have to cannibalise from elsewhere when I rebuild. When I grabbed it this time, it still had the same disk inside from the last rebuild, so I know that is ok. That was why I was so keen to get an nLite version going, I'd like to be able to rebuild silently at whim, without spending half the day under the desk with a torch. I keep all my data on a NAS and I prefer to just wipe Windows rather than diagnose issues. If it works I can be fully configured in less than half a day. Obviously if it doesn't work... well here I am.
I thought there was just something obvious in the configuration that I am doing wrong. I expected to come here, then feel really embarrassed when you point out something I really should have noticed, that's what usually happens, especially after I have written a 10,000 word essay only to get a two-word response. I was confident you guys were right about wiping the hard drive. When it showed up as a new ID number I thought everything was going to be ok.
I mounted an old hard drive to build XP on to then wipe the disks, but that is also on it's last legs, and I've had to give up on that (I seem to break everything at the moment). Otherwise I would wipe them again. I'm trying to work out how I can get something else to mount for the moment I would still like to try accessing the drives from XP as a RAID, maybe if I can format them as a single drive I can then install to that. I have also read that Windows 7 has solved this issue for other people, but I as I keep saying, I know this should work, it has done in the past.
I'm thinking I should try the old BIOS again, if I didn't mess it up getting it out, I'll try that tomorrow, but as it didn't work before I am not hopeful. I have also stripped the box back to basics, removed 1 of the memory sticks, disconnected spare fans, to try and lower the power consumption. I also swapped the SATA cables over, just in case. I have just cleared the CMOS again, I'm gonna give it one more try with just the basics. I have not yet tried new XP setup drivers, as I have no way to get them onto a floppy easily, however this is something else I am working on.
One other detail that might be worth mentioning, I run the machine on a KVM with my little ITX Media Box, which I'm typing on now. This used to be PS/2, but I have recently put in USB, a pain in the ass as it tends to auto-switch, especially in the middle of the Windows Setup. I have to move the keyboard directly onto my main box to access BIOS and the XP setup. Not really relevant, but I want you to feel my pain . It's very frustrating typing desperately only to realise you are on the wrong box.
I have Googled this over and over, gone through all the manuals I can find, and tried every option I can think of. I have a few more ideas to try, but nothing I am really confident will have any effect. Thank the stars I have this little machine, or I would be having serious withdrawal by now, that is why I am loathe to start poking around in here to try things (that and the build is ubuntu). I think it is nearing the point where I might have to.
See I told you I might go on . I much appreciate your help guys, I hope the above helps explain where I am. Please don't give up on me yet.
Steve

PM8M2-V RAID array not recognised by WinXP Pro

Greetings,
i'm just setting up a PM8M2-V system with 2 x WD 80GB JD SATA drives. In the RAID BIOS i have configured the drives to be RAID 0 (striped) for performance and made them bootable. From a IDE DVD rom, i'm running a WinXP Pro (corp ed - no pre-installed service packs) install but the OS will not detect any drives in the system.
I have downloaded the VIA_RAID_OM74.zip file from MSI VIA PIDE-SATA RAID Drivers and Utility for creating the RAID drivers and tried to create a floppy disk with the WinXP drivers on it using the embedded (and slightly cryptic) VIA MakeDisk.txt instructions.
Containined on the floppy disk are the following files/folders:
a:\TXTSETUP.OEM
a:\PIDE\WinXP\viapdisk.cat
a:\PIDE\WinXP\viapdisk.sys
a:\PIDE\WinXP\viapide.inf
a:\RAID\WinXP\viamraid.cat
a:\RAID\WinXP\viamraid.inf
a:\RAID\WinXP\viamraid.sys
*plus the other MS operating system files in the similar directory structure*
Problem - WinXP Pro does not recognise this created floppy disk as a hardware support disk and will NOT let the OS recognise the SATA RAID array as a drive.
Complete system specs
MSI PM8M2-V VIA P4800 + 8237R (RAID)
Intel P3 3ghz HT LGA775 CPU
2 x 512 DDR-RAM PC3200
2 x WD 80GB JD SATA drives configured in a RAID 0 Striped set and bootable
1 x IDE DVD D/L Burner (Master drive on IDE Secondary Channel)
ATI Radeon 9250 128m AGP Card
Web Excel 56K software modem

Did you boot with WinXP CD 1st and then hit F6 to install the RAID controller drivers?

System Profile not recognising known good 80GB ADM

I currently have 2 Xserve slot loading, running Mac OS Server 10.3.9. Drive bay 1 and 2 contain 2 mirrored drives. When I place the spare drive module in bay 3 it is not recognised in system profiler and will not mount. It has been working before for backups is this a known issue that may have been caused by an update ? I am currently running frimware version 5.1.7f1.
Xserve G5 slot loading Mac OS X (10.3.9)

First of all, unless you have 10.4 running and have your mirror set to auto-rebuild, your raid should now be degraded.
It is easy to repair anyway, but you should check the status with disk utility or diskutil command line.
I am assuming that unrecognized means that the drive doesn't even show up in disk utility? or does it say that the drive isn't recognized in the finder (with a message to format)?
The latter may be fixed with the usual tools like disk warrior or even the repair funtion in Disk Utility. If the drive is completely invisible, it may be something as simple as a loose connector inside the drive module (power or sata). Have not seen that though.
If you have Applecare, just try to get it exchanged...

All firewire devices not recognised after upgrading to Leopard 10.5.4

Hello, yesterday I finally got around to upgrading one of my home computers (old Emac G4 powerpc from 2005) to Leopard. I have been using Leopard on my work computer (G5 also from 2005) with no problems for a year now (this Leopard update was installed professionally when. I work with a lot of files on external hd's, mostly Lacies, one Maxtor and yesterday got new G-Drive 1TB. Since the upgrade the Emac will not recognise any of the external hds when connected by Firewire. It will recognise them if I use the USB. However I'm sending too much media traffic (film editing) to just use usb all the time. I need my firewire connections!
This is clearly a Leopard issue, there are no problems with the drives or the firewire connections or the cables, they all work fine on the work computer and my other home computer (powerbook laptop G4) and as I said the upgraded emac will recognise them from usb. And since it's three different kinds of drives that all work on other computers but all stopped working on the single Leopard upgrade it's not a Lacie, Maxtor or G-drive problem.
I've seen a lot of threads on this and other support forums about firewire problems but some are a slightly different problem and many are quite old so I wonder if anyone has any recent experience/advice for me?
Many threads complain that Apple was not recognising the problem, maybe there is also some progress there?
thanks in advance for any help!

It's still possible that there is now a hardware issue, and if so it might respond to resetting the FireWire bus. This can often be done by just unplugging the power cord for a few minutes.
From
*What to do if your computer won't recognize a FireWire or USB device*
http://support.apple.com/kb/HT1317?viewlocale=en_US
# Shut down the computer.
# Disconnect all devices and all other cables, except the keyboard and mouse cable(s).
# Disconnect the computer from the power outlet and wait for 3 to 5 minutes.
# Plug the computer back in and turn it on.
# Reconnect the device(s) (one at a time if there is more than one) and test. Test with each port if you have more than one.
--------------------------

External hard drive not recognised in start up options

Hi! I'm struggling to get to grips with creating a bootable external drive - any advice would be very welcome!
I've recently bought a LaCie Triple Interface 300GB external drive to use for backup storage and to use as a back up bootable drive should disaster strike. It's connected to my Mac via the FireWire 800 port.
I've backed up my documents and cloned system folders and apps using Intego Backup, but the drive is not recognised in the start up options of the system preferences, nor does it appear as a bootable drive when I option-restart.
Do I need to format and partition the drive before it will be recognised as a bootable drive? (I haven't done so) Or have I just cloned the wrong thing?! I'm not entirely sure what I need to clone to be able to boot and back up from it. Should I clone the entire HD?
Or does it sound like something else entirely?
Can anyone help??
1.8 GHz PowerPC G5 6.5MB RAM Mac OS X (10.2.x)

I'm not familar with Intego Backup. Get Carbon Copy Cloner and use it to clone your entire drive, user files and all.Be sure to check the "make bootable" box before you start the process. Could be that Intego isn't capable of making a drive bootable.

Macbook not recognising receiver

Hi folks,
I'm using a MiniDisplay to HDMI cable, to try to connect my MBP to my Denon Home Theatre Receiver.
I'm connecting the cable to the Thunderbolt connection on the MBP, and Blu-ray input on the HT receiver.
The Mac is not recognising the receiver as a display, nor an audio output.
When I use the same cord to connect the MBP to HDMI input on my plasma TV, it works fine. So that eliminates the cord as being the problem.
Any ideas?

I'm having the same problem. LaCie has been no help saying that they will give me a discount if I want to buy a new one.
The drive just doesn't appear in the Finder and the drive doesn't spin up like usual.

Latest Initrd not recognising USB storage devices?

Just installed 2.6.30 with all the necessary files. Everything seemed fine, except for one thing: my external USB hard drive is no longer recognised on boot. Here is my fstab and my mkinitcpio.conf.
# /etc/fstab: static file system information
# <file system> <dir> <type> <options> <dump> <pass>
none /dev/pts devpts defaults 0 0
none /dev/shm tmpfs rw,noexec,nosuid 0 0
#/dev/cdrom /media/cd auto ro,user,noauto,unhide 0 0
#/dev/dvd /media/dvd auto ro,user,noauto,unhide 0 0
#/dev/fd0 /media/fl auto user,noauto 0 0
UUID=139cf76d-425a-4c40-a5b1-bbbf22533d9a /boot ext4 defaults 0 1
UUID=4eddd177-23f6-49ab-a8ad-d3e1303133e0 / ext4 defaults 0 1
UUID=ED83-B8D4 /media/flash vfat rw,user,noauto 0 0
#UUID=ac46c6ae-d9eb-47d4-809b-19a2484b3133 /iomega ext4 rw,noexec,nosuid 0 1
UUID=ac46c6ae-d9eb-47d4-809b-19a2484b3133 /media/iomega ext4 rw,user,noauto 0 0
UUID=da9e741f-3525-47c6-8c7f-edf1ded00e7a swap swap defaults 0 0
As you can see from this, I originally had my external usb drive mounted on /iomega @ boot. However, since that no longer works, I have changed it to /media/iomega and let HAL mount it automatically when I fire up GNOME (the same way I have my flash drive set up). I used the original line with 2.6.29 with no problems.
The strange thing is, the device is there, because, when it fails, I go into single user mode, remount / read-write and then run mount -a and the device appears with no errors. If I change the line so it doesn't do an fsck on boot, it doesn't mount the device, but I do get an error saying the device is not there. I can then mount it manually at the command prompt.
The device is shown in /etc/blkid.tab and in /dev/disk/by-uuid.
# vim:set ft=sh
# MODULES
# The following modules are loaded before any boot hooks are
# run. Advanced users may wish to specify all system modules
# in this array. For instance:
# MODULES="piix ide_disk reiserfs"
MODULES=""
# BINARIES
# This setting includes, into the CPIO image, and additional
# binaries a given user may wish. This is run first, so may
# be used to override the actual binaries used in a given hook.
# (Existing files are NOT overwritten is already added)
# BINARIES are dependancy parsed, so you may safely ignore libraries
BINARIES=""
# FILES
# This setting is similar to BINARIES above, however, files are added
# as-is and are not parsed in anyway. This is useful for config files.
# Some users may wish to include modprobe.conf for custom module options,
# like so:
# FILES="/etc/modprobe.conf"
FILES=""
# HOOKS
# This is the most important setting in this file. The HOOKS control the
# modules and scripts added to the image, and what happens at boot time.
# Order is important, and it is recommended that you do not change the
# order in which HOOKS are added. Run 'mkinitcpio -H <hook name>' for
# help on a given hook.
# 'base' is _required_ unless you know precisely what you are doing.
# 'udev' is _required_ in order to automatically load modules
# 'modload' may be used in place of 'udev', but is not recommended
# 'filesystems' is _required_ unless you specify your fs modules in MODULES
# Examples:
# This setup specifies all modules in the MODULES setting above.
# No raid, lvm2, or encrypted root is needed.
# HOOKS="base"
# This setup will autodetect all modules for your system and should
# work as a sane default
# HOOKS="base udev autodetect pata scsi sata filesystems"
# This is identical to the above, except the old ide subsystem is
# used for IDE devices instead of the new pata subsystem.
# HOOKS="base udev autodetect ide scsi sata filesystems"
# This setup will generate a 'full' image which supports most systems.
# No autodetection is done.
# HOOKS="base udev pata scsi sata usb filesystems"
# This setup assembles an pata raid array with an encrypted root FS.
# Note: See 'mkinitcpio -H raid' for more information on raid devices.
# HOOKS="base udev pata raid encrypt filesystems"
# This setup loads an lvm2 volume group on a usb device.
# HOOKS="base udev usb lvm2 filesystems"
HOOKS="base udev autodetect pata scsi sata usb keymap filesystems"
# COMPRESSION
# Use this to compress the initramfs image. With kernels earlier than
# 2.6.30, only gzip is supported, which is also the default. Newer kernels
# support gzip, bzip2 and lzma.
#COMPRESSION="gzip"
#COMPRESSION="bzip2"
#COMPRESSION="lzma"
This is essentially the same as I had it in 2.6.29. I did initially use LZMA, since that gives slightly faster compression & decompression, but changed it back in case it was a timing issue (and rebuilt initrd). No joy. I also tried usbdelay=10 on boot, but again no difference.
This isn't exactly a "show-stopper", since the device functions normally otherwise and everything else is fine, but it is annoying. I would much rather have this device available automatically on boot, so that it gets checked when the max mount count comes up.

This was the bug update I received today:
FS#15282 - [mkinitcpio] Latest initrd not recognising usb storage devices?
User who did this - Thomas Bächler (brain0)
You can never rely on external hard drives to show up "in time".
The difference was that adding the "usb" hook to mkinitcpio used to add a 6 second delay on boot by default, this doesn't happen anymore. I think external drives simply don't belong in fstab, because there's too many possible race conditions. If you insist, you can try to force the usb storage driver to scan for devices sooner after detection, see the delay_use parameter to the usb-storage module.
You're going to have to modify the delay_use parameter to get it to work. Be prepared for race conditions, though. I didn't bother myself as it wasn't a show stopper for me, so I've advised that it can be closed as a non-bug.
ETA: usbdelay=10 doesn't work as that flag is apparently no longer recognised for some reason.
ETTA: I've always used UUID in the fstab because udev can remap devices on boot (I've had fstab not recognising devices because of this).
In case some people don't know, to see what the uuid for a device is, use the following:
sudo tune2fs -l <device-name>
Last edited by jamesbannon (2009-06-28 18:30:23)

First time starting up iMac, USB keyboard not recognised

i have tried to set-up my imac, however the keyboard is not recognised and says that i have to turn on my bluetooth keyboard when i have a USB keyboard and it will not go on to the next step.

Hi manocchio1994,
Thanks for contacting the Apple Support Communities. I understand your keyboard is not recognized when connecting if for the first time and I know how frustrating that can be. There is a fantastic article available for USB keyboard troubleshooting I would recommend.
None of the keys on my keyboard work
http://support.apple.com/kb/TS1996
Troubleshooting your Apple USB Keyboard Step-by-Step
If your keyboard keys still aren't working after trying the steps in USB Basic Troubleshooting, try these steps, in order, until you've come to a resolution.
▪ Unplug all devices from your computer, including your mouse and keyboard, as well as your printer, scanner, cameras, iPod, external hard drives, and hubs. (Warning: Some devices, like iPods, may require you to perform steps before it is safe to unplug them.) If you have a hub, don't forget to unplug it as well.
▪ Plug your keyboard and mouse back into your computer firmly and securely. Take special care to make sure that the connector is completely in the port. (USB plugs fit into ports one way only, and won't plug in if you try to plug them in upside-down.)
▪ If that still doesn't work, try plugging your keyboard in to the other USB ports. Be sure to try them all. Check to see if the keyboard's Caps Lock light turns on when you press it, and try typing in one of your applications, such as TextEdit.
▪ If your keyboard works in one of your USB ports but not all, your computer may need service to resolve an issue with its USB port or ports.
If your keyboard doesn't work in any of your computer's USB ports, it appears that your keyboard isn't functioning properly and needs to be replaced. You can order this part online. Order a replacement keyboard.
If needed, I suggest resetting the System Management Controller as well. Those steps can be found in the following section of this article.
Resetting the SMC for Mac Pro, Intel-based iMac, Intel-based Mac mini, or Intel-based Xserve
Intel-based Macs: Resetting the System Management Controller (SMC)
http://support.apple.com/kb/ht3964
Thanks for reaching out,
-Joe

I have downloaded snow leopard and it is not recognising that i have, i need to in order to update to mavericks, I have downloaded snow leopard and it is not recognising that i have, i need to in order to update to mavericks

Basically, I bought snow leopard and just installed it but its not recognising the fact that I've installed it. I've tried twice and it has restarted both times, but it hasn't done anything, and I need that to update to Mavericks, which I really need to do. Please help!

Then you've installed Snow Leopard.
It needs to be 10.6.8 so download and install Mac OS X 10.6.8 Update Combo v1.1. Then try installing Mavericks.
Upgrading to Mavericks
You can upgrade to Mavericks from Lion or directly from Snow Leopard. Mavericks can be downloaded from the Mac App Store for FREE.
A. Upgrading to Mavericks
To upgrade to Mavericks you must have Snow Leopard 10.6.8 or Lion installed. Download Mavericks from the App Store. Sign in using your Apple ID. Mavericks is free. The file is quite large, over 5 GBs, so allow some time to download. It would be preferable to use Ethernet because it is nearly four times faster than wireless.
    Macs that can be upgraded to OS X Mavericks
         1. iMac (Mid 2007 or newer) - Model Identifier 7,1 or later
         2. MacBook (Late 2008 Aluminum, or Early 2009 or newer) - Model Identifier 5,1 or later
         3. MacBook Pro (Mid/Late 2007 or newer) - Model Identifier 3,1 or later
         4. MacBook Air (Late 2008 or newer) - Model Identifier 2,1 or later
         5. Mac mini (Early 2009 or newer) - Model Identifier 3,1 or later
         6. Mac Pro (Early 2008 or newer) - Model Identifier 3,1 or later
         7. Xserve (Early 2009) - Model Identifier 3,1 or later
To find the model identifier open System Profiler in the Utilities folder. It's displayed in the panel on the right.
     Are my applications compatible?
         See App Compatibility Table - RoaringApps.

Ms-6741 + SATA HDDs not recognised by xp setup

Hi all, i have been ripping my hair out for 24 hours about this machine.
It is a TINY PC with a MS-6741 mainboard. It previously had 2 SATA HDDs installed, both 200GB. 1 had XP installed on it and the other just data. The OS disk failed, many many bad sectors and errors. I bought a new SATA HDD (WD2500AAJS) and thought i would be able to install xp from either the tiny restore disk, or a standard windows xp disk. But I can't!
First problem (although not the worst) is that the BIOS does not recognise the 250 GB new disk, not one bit. Checked the sata cable, checked the power, checked the disk in another machine; all fine. So after some swearing I decided to copy the data off the data disk and use a disk the BIOS was recognising.
The mobo recognises it fine, but when i get to the xp setup to select disks and partitions it says 'no disk available'.
I did some reading and many people suggest that the XP setup disk doesn't have drivers to make SATA work, they suggest downloading the raid/sata driver from the mobo manufacturer website and pressing F6 at the start of setup, copying the drivers to a floppy and letting xp setup find the drivers and use them. I tried that, i tried both the drivers listed for raid on the MSI support page for this mobo, i tried getting the drivers for the VIA VT8237 SATA controller, they didn't work.
I have tried upgrading the bios, flashing it from a win 98 boot disk, following the instructions on this page http://www.msicomputer.com/support/BIOS_NON_FAT.asp This as far as i can see didn't work, it launched the flash utility fine, said 'deleting' and then 'programming' and said both had completed successfully. I restarted, went into the bios and the bios version hadn't changed. The only difference when i turned it on was that it said 'CMOS settings wrong'.
I am at my wits end, i have no idea what else to try. I read somewhere that TINY used to make their own version of BIOS which only allowed certain HDDs, maybe they stop you flashing the bios, certainly there is no setting in the existing bios saying, 'protect bios' or 'don't allow bios flashing'.
I would greatly appreciate any help.
Many Thanks
James

http://global.msi.com.tw/index.php?func=downloaddetail&type=driver&maincat_no=1&prod_no=575
There you have all drivers for your board.
You probably have to make a driver floppy and load it during install with F6

K9N2 Diamond - bios does not recognise Intel SSD 520 series

Hi,
I have a K9N2 Diamond motherboard and BIOS v2.7. I recently bought an Intel SSD 520 Series and when I connect it, the BIOS does not recognise the HDD at all. When I try to install Windows 7, the HDD is shown at the list, but it says that I can not install Windows at the HDD.
I have tried to connect the HDD at SATA port 5 and 6 and set the RAID mode to ACHI and also at ports 1 and 2 and set the RAID mode to IDE. Nothing works.
Any ideas?
Regards,
George

.and does the problem appears using the HDD which was equipped in this notebook?
If the BSOD would not appear using the HDD, then a problem is realalted to the inserted SSD drive.
In many cases firmware updates are released for SSD drives and in some cases this might be a solution.

Windows Vista - iTunes not recognising iPod!

iTunes is not recognising my iPod and the iPod Setup Assistant isn't showing automatically. Can anyone help. I have a new laptop with Window Vista is this operating system the problem? Can help would be appreciated. I can import music into iTunes OK and purchase music from iTunes itself I just can't get iTunes to recognise my iPod!

> Step 3:Download and install the latest chipset drivers from the laptop manufacturers website.
>*So here I am with the issue still not resolved. How do i Download and install the latest chipset drivers >in order to have Toshiba Satellite L300 & Microsoft Vista recognise my ipod?
Install an hardware diagnostic tool like Everest home Edit or similar.
This tool would provide all hardware details about your notebook.
It would list all devices and chipset name too.
I think its Intel chipset so you could find the driver on the Intel page
Greets

Ipod not recognised by Windows, USB device not recognised

Hi hope someone can help
I have recently received my ipod back from Applecare who have sent the ipod back in ' working order ' but it will no longer be recognised by my windows. It says USB device not recognised and i cant find, nor will it install drivers that i located on the ipod updater etc.
I have tried several methods on this forum but none seem to work.
The letter from mycare says the iPod is formatted for a computer operating Mac OS X. Although i stated wi use Windows. But the leter states this can be changed bu installing the updater, but this wont make a diff as comp still wont regonise the device after i have followed there instructions. Any advice?
Thanks

I'm not really up on the complexities of the Windows OS but try this tip I picked up a while back, hopefully it might help.
"USB Device not Recognized in Windows".
1. On the Start menu, click Control Panel.
2. Double-click the System icon.
3. Click the Hardware tab.
4. Click Device Manager.
5. Scroll down the list of devices to the Universal Serial Bus controllers
6. Click the plus icon next to the Universal Serial Bus controllers.
7. Double-click one of the indented USB Root Hub entries.
8. Click the Power Management tab.
9. Deselect the "Allow the computer to turn off this device to save power" option.
10. Click the OK button at the bottom of the window.
11. Restart the computer.

Xserve not recognising LaCie RAID

Similar Messages

Maybe you are looking for