Problem mounting a RAID disk

First of all, sorry if this isn't the category, first i though that it was OSX 10.6, but right now, i think it may be a hardwrare problem, not sure, ok the story is this:
I had 2 HD of 500GB in a RAID-1 configuration (mirror...), the machine that i was using for this resulted damaged and isn't working right now, we had to take the disk to extract the info, we though that it was going to be easy, cause we set everything from Ubuntu, and OSx is UNIX based, besides i have the Disk Utilities and the RAID Tools, WRONG!
The disk appears with a yellow icon, the description 500GB Hitachi HD in black letters, is right now connected as USB to my iMac, it appears to don't have the S.M.A.R.T. supported.
Below it's name appears disk1s2,disk1s5, disk1s6, disk1s7, disk1s8, disk1s9 and disk1s10 with the same yellow icon but with grey letters, every time i tried to hit the Mount button it doesn't do anything, partition Linux (i suppose linux RAID partition), so i can't see anything from my data.
When i go to Terminal i go to the dev directory and type mount disk1s2, and says:
mount: disk1s2: unknown special file or file system.
Is there a way to see the data from this disk? When i use the RAID utility in iMac, it doesn't work, it tells me that the RAID utility is not compatible with this PC, when i asked for a RAID compatibility i found that the iMac could see RAID information, but i can't do a thing with this RAID, i'm skipping some obvious steps, or doing (not doing) something?
I really appreciate if someone can spare some info with me, i usually works on Ubuntu, but changed to iMac, and, well i'm kinda of n00b on this one.
Thanks

osx does not support ext3/4 or riserfs filesystem, and as your harddisk comes from a linux system, i guess it's ext3 or 4.
you must install macfuse with ext3 module and you should be able to read (and maybe write?) the harddisk. it's not an hardware problem
or boot a linux distro inside a virtual machine and attach the harddisk to it and it should go.
try macfuse first keep in touch

Similar Messages

  • Problems mounting usb Maxtor disk Help PLZ

    Usb maxtor disk that already has 2 OSX partitions does not want to mount in 10.4.9 updated mac mini.
    Disk utils in 10.4.9 is smoking some weed and does not / or want to do anything with the usb Maxtor.
    Tried on windows with Macdrive 7.0.4 trail and nothing mounting as well.
    Success on windows with Macdrive 6.1.5 trail and it mounted.
    Any idea what is going on here as it used to mount perfectly in osx sometime ago but not sure if it was in 10.4.8 or earlier.
    Help would be appreciated

    Indeed, I too have externals, both USB and FW attached to Macs running 10.4.9 and have no similar problems. I think the signs are that 10.4.9 is fine and that the issue in this instance is with your Mac or drive. Understanding that should help focus attention where it needs to be in order to resolve the problems you are experiencing.
    First things first - if you are using a hub, shut the Mac and drive down, disconnect the hub and connect the drive directly to the Mac. Then power up the Mac, and once booted, power up the drive. Open Disk Utility (in Applications>Utilities on your mini), select the external drive (the entry giving the make/model/size) and select 'repair disk'. Next, select the first partition on the drive in Disk Utility, and repeat the repair disk. Lastly, select the second partition on the drive, and again, repair disk. If you get an error with any of these repairs which then reports a repair cannot be effected, the drive has damage - likely data rather than physical - which will either require a utility such as DiskWarrior or Tech Tools Pro to attempt to resolve, or a reformat after you have backed up your data. Problems of that sort can often result from drives that are powered down or disconnected while writing or updating.
    If Disk Utility reports no errors after undertaking all three repairs, or the system continues to be unable to read the drive correctly, the problem is with the MacOS install on your system. In that instance, first try to repair permissions on your internal hard drive (also using disk utility). An SMC reset may also help.

  • Anybody having problems mounting G-Raid 4TB eSATA after Lion install?

    I have a G-Technology 4TB G-Raid connected to my Mac Pro via eSATA which has been working fine until I updated to Lion.  Now it doesn't even mount on startup.  Anybody else having this issue?

    I tried re-intalling the silicone image 3124 & 3132... which I had originally installed in 2009 (was that Leopard?)
    no luck! I could give you some details, but still the eSATA drives are not showing up.  Incidentally, they are not RAIDed together, they are just four individual drives in a collective case.
    Does anyone know specifically what drivers will work with eSATA in a LION (10.7) system?  It's gotta be one driver, right? It's not a different driver for every manufacturer, is it? I hope not!
    W

  • How to mount RAID disk with target mode

    Hi,
    On my Mac Pro I have 2x2TB HHD which I use as RAID 1.
    For maintenance I need now to access the HHD content from my macbook via FIreWIre target mode. On the macbook however I see the two HHD unmounted as two independent units, not as RAID 1.
    How can I safely mount my RAID 1 disk?

    I don't think you'll need another computer or eight hours of downtime. You didn't mention the size of your internal drive but I'd assume the 300gb external will hold it all. I'll also assume the external is a firewire drive, if it's not none of this will work.
    This is what I would do:
    1. Download Carbon Copy Cloner or SuperDuper to clone your remaining raid slice to the external 300gb drive, and make sure to check the "make bootable" box.
    2. In System Preferences set your startup disk to the external.
    3. Restart from the external.
    4. Run disk Utility to reformat your internal drive. At this point you're going to need to decide wether or not to set it up as a raid again. I don't think I would.
    5. Use Carbon Copy Cloner or SuperDuper to clone the external back onto your internal drive.
    6. System Prefs again to reset the startup drive to your internal.
    7. Restart and you should be good to go, and you've got your first backup done on your external.
    8. Devise and impliment a backup strategy. Do you need daily/weekly/monthly backups? You'll have to decide how much you can afford to lose if your main drive goes belly up. There are several programs that are easy to set up a backup schedule on, the above mentioned CCC and SuperDuper and a little app called Deja Vu which runs as a system preference pane, is very easy to set up and if I remember is free.
    Now, I say all of this not knowing what you do with your external drive to begin with. I am guessing that the raid was set up as a mirror to be a backup if the drive had problems....which is exactly where you are. Personally I would just format it as one drive and backup to the external. If the internal does actually fail you'll still have all your stuff and can run from the external until you replace the internal.
    Make sense? I know I rambled a bit but it's really easy.
    Dual 2.0, 4 GB, 2x160 GB , SuperDrive, 9800 SE, 20 Aluminum - 15 1.5 PB,   Mac OS X (10.4.5)  

  • Mirrored RAID not mounting/not showing as RAID (Disk Utility)

    I have 2 Lacie Firewire Disks set up as a mirrored RAID (created by Disk Utility). I've been using this setup for about a year with no issues. But today I tried mounting the RAID and I got this msg twice (one for each drive)...
    "Disk Insertion - The disk you inserted was not readable by this computer."
    It then asks if I want to Initialize, Ignore or Eject. If I leave this msg up for a bit it eventually just goes away. But the disks never load.
    I opened up Disk Utilities to check and see if the drives were listed and they are, but the RAID is NOT listed. All of the first aid options are greyed out. I tried to mount each disk but they will not mount, I assume because the RAID info has been lost?
    Is there a way for me restore the RAID or at least get my info off of the drives? They contain a large photo library that cannot be replaced.
    Powerbook G4 Aluminium 1.33gthz   Mac OS X (10.4.7)  

    I never technically fixed the RAID. I used the program Data Rescue mentioned above to look at the drives and pull my data off of them. What I found was one of the drives was in perfect order, and the other drive had stopped recording data MONTHS ago. Basically the RAID became un-paired and stopped working correctly, and only one of the drives was saving the data. It freaked me out at first because the drive I decided to recover first was the one that was missing data. But I then looked at the 2nd drive and it had all my data on it, and I was able to recover it.
    Anyway, Data Rescue worked perfectly. Now I just have the drives running independently. But I am staying away from the apple software RAIDs for now, as I did some reading and they seem to not be so trustworthy.
    Also, Data Rescue takes quite a bit of time to pull all your data off, especially when you have a couple hundred gigs of data. Hopefully this helps.
    Sam

  • Backups failing with error 19: the backup disk could not be resolved, or there was a problem mounting it

    Hello all,
    Doubt this issue relates to a recent and ugly issue but sharing anyways (resolved thanks to a user here: LaPastenague)
    Time Capsule won't backup if Modem (Motorola SB6121) attached
    This was on Feb 10th resolved. Few days later I upgraded to Yosemite.  Backups were working fine since.  
    Yesterday I happen to notice my last backup was 5 days ago.  I looked in the console logs and saw:
    2/25/15 3:55:06.127 PM com.apple.backupd[2777]: Attempting to mount network destination URL: afp://Paul;AUTH=SRP@Time%20Capsule._afpovertcp._tcp.local./Data
    2/25/15 3:55:17.778 PM com.apple.backupd[2777]: NAConnectToServerSync failed with error: 2 (No such file or directory) for url: afp://Paul;AUTH=SRP@Time%20Capsule._afpovertcp._tcp.local./Data
    2/25/15 3:55:17.792 PM com.apple.backupd[2777]: Backup failed with error 19: The backup disk could not be resolved, or there was a problem mounting it.
    2/25/15 3:57:18.808 PM com.apple.prefs.backup.remoteservice[2021]: Attempt to use XPC with a MachService that has HideUntilCheckIn set. This will result in unpredictable behavior: com.apple.backupd.status.xpc
    I called Apple.  Their front line was clueless. He suggested resetting the TC (latest "tower" model btw") which then a backup kicked off YEAH
    But the next hour it failed
    Called Apple again, this time to Sr Advisor.  He suggested factory reset of the TC and set up again.  Also first backup worked then rest failed
    Third call to Apple useless also.  He was asking questions I didn't feel relevant.  He also was asking me to reset the TC which I told him was done 2 hours prior. He asked me to reboot which I could NOT at that time.
    I begged him to collect data to submit to engineering, which will take days to get a reply.
    So I thought I would throw this out to the community....
    TC Is NEW (replaced from last issue).  Mac is 8 months old (iMac 27"), Os is Yosemite,  TC also new (latest model)
    Thanks...

    Yosemite is problematic on two fronts.. Networking and Time Machine.. so the combo of doing both with a Time Capsule is like bugs on bugs.
    Here is my standard list.. but your problem maybe difficult to resolve.. and my suggestion is simple.. until Apple get their act together and fix TM.. buy Carbon Copy Cloner and use that for your backup. It is solid and reliable.. even better if you use USB drive plugged into the computer and do a bootable clone.. because then you have a backup that is able to be tested for full functionality 2min after the end of the backup.
    This also starts from a factory reset.. but the reason for it is to change the configuration which is much more easily handled with factory reset to begin.. the instructions are there.. because this is my standard reply.. this is not uncommon!!
    Factory reset universal
    Power off the TC.. ie pull the power cord or power off at the wall.. wait 10sec.. hold in the reset button.. be gentle.. power on again still holding in reset.. and keep holding it in for another 10sec. You may need some help as it is hard to both hold in reset and apply power. It will show success by rapidly blinking the front led. Release the reset.. and wait a couple of min for the TC to reset and come back with factory settings. If the front LED doesn’t blink rapidly you missed it and simply try again. The reset is fairly fragile in these.. press it so you feel it just click and no more.. I have seen people bend the lever or even break it. I use a toothpick as tool.
    N.B. None of your files on the hard disk of the TC are deleted.. this simply clears out the router settings of the TC.
    Setup the TC again.
    ie Start from a factory reset. No files are lost on the hard disk doing this.
    Then redo the setup from the computer with Yosemite.
    1. Use very short names.. NOT APPLE RECOMMENDED names. No spaces and pure alphanumerics.
    eg TCgen5 and TCwifi for basestation and wireless respectively.
    Even better if the issue is more wireless use TC24ghz and TC5ghz with fixed channels as this also seems to help stop the nonsense. But this can be tried in the second round.
    2. Use all passwords that also comply but can be a bit longer. ie 8-20 characters mixed case and numbers.. no non-alphanumerics.
    3. Ensure the TC always takes the same IP address.. you will need to do this on the main router using dhcp reservation.. or a bit more complex setup using static IP in the TC. But this is important.. having IP drift all over the place when Yosemite cannot remember its own name for 5 min after a reboot makes for poor networking. If the TC is main router it will not be an issue.
    4. Check your share name on the computer is not changing.. make sure it also complies with the above.. short no spaces and pure alphanumeric.. but this change will mess up your TM backup.. so be prepared to do a new full backup. Sorry.. keep this one for second round if you want to avoid a new backup.
    5. Mount the TC disk in the computer manually.
    In Finder, Go, Connect to server from the top menu,
    Type in SMB://192.168.0.254 (or whatever the TC ip is which you have now made static. As a router by default it is 10.0.1.1 and I encourage people to stick with that unless you know what you are doing).
    You can use name.. SMB://TCgen5.local where you replace TCgen5 with your TC name.. local is the default domain of the TC and doesn't change.
    However names are not so easy as IP address.. nor as reliable. At least not in Yosemite they aren't. The domain can also be an issue if you are not plugged or wireless directly to the TC.
    6. Make sure IPv6 is set to link-local only in the computer. For example wireless open the network preferences, wireless and advanced / TCP/IP.. and fix the IPv6. to link-local only.
    There is a lot more jiggery pokery you can try but the above is a good start.. if you find it still unreliable.. don't be surprised.
    You might need to do some more work on the Mac itself. eg Reset the PRAM.. has helped some people. Clean install of the OS is also helpful if you upgrade installed.
    Tell us how you go.
    Someone posted a solution.. See this thread.
    Macbook can't find Time Capsule anymore
    Start from the bottom and work up.. What I list here is good network practice changes but I have avoided Yosemites bug heaven.
    This user has had success and a few others as well.
    RáNdÓm GéÉzÁ
    Yosemite has serious DNS bug in the networking application.. here is the lets say more arcane method of fixing it by doing a network transplant from mavericks.
    http://arstechnica.com/apple/2015/01/why-dns-in-os-x-10-10-is-broken-and-what-yo u-can-do-to-fix-it/

  • Utility need to saftly mount / repair raid volume over fibre optic

    Hi,
    was wondering if there's any ideas for the following scenario:
    Mac Pro / OS 10.5.x which usually mounts a RAID volume over fibre optic link. The thing is the RAID volume is corrupt, and when any Mac tries to mount it (after being informed that it's damaged, and givent the option to format / ignore...) it crashes.
    Another problem is the only way to access the volume is to mount it on a Mac first because they're the only machines with fiber channel cards.
    The questions are - is there any way to access the volume without crashing the mac?
    Once the volume is accessible, what's the best tool for repairing rAID volumes these days?
    Any thoughts appreciated ( i know this is all a bit vague, just looking for general info, opinions). Many thanks in advance.
    c

    Hello,
    First of all thanks for the reply. The only problem is that I've already tried what you suggested. When I press the option key on the keyboard with the installation cd inserted I see what I am supposed to, the CD, Windows Vista and Macintosh HD. When I select Macintosh HD it does that same thing, goes to the "restart your computer" screen.
    If I try to change the startup disk from the OS X Installation disk the only two volumes that show up are "Windows Vista on Untitled" and the "OS X Installation" disk, no Macintosh HD to even choose. I believe the reason for this is because Macintosh HD but as I have already said, it just can't be mounted.
    I think the reason that Macintosh HD shows up when I press Option at startup is because Apple has hard-coded it in so that it's always there, no matter if you can actually access it or not depending on whether or not it's mounted.
    Right now the best thing for me is to find out how to mount Macintosh HD, if it has to be done manually through Terminal I'll do it, I just need the syntax but something tells me if it doesn't work through GUI it probably won't work through command prompt.
    Anyway, thanks for the reply. Let's hope we get something.

  • RAID disk not seen from WInPE boot

    Dear all,
    We have a system with 3ware raid controler card configure as RAID1.
    We are trying to build a standard Windows server 2008 image that can be installed in any System, by providing a system dependant unattend.xml file.
    As a test first I have generate an unattend.xml file using WAIK. Then I have generate a WinPe boot disk.
    When generating the WinPE boot disk, I have follow this procedure in order to add to WinPE boot my Raid controler driver:
    http://www.windows-noob.com/forums/index.php?/topic/2349-guide-adding-drivers-to-a-custom-winpe-30/
    The problem I have when booting from WinPe and listing volumes from DISKPART is that I cannot see my Disk mounted as RAID 1.
    Any idea what can be wrong ?
    regards
    serge
    Your knowledge is enhanced by that of others.

    Hi Serge,
    Can you please post how did you resolve the issue? I am having similar issue here & I am unable to see the Disk Drives in WinPE 3.0. I have 2 3TB Hard Disk Drives connected & it needs Intel RAID drivers to load to see the drives in DISKPART "List
    Disk" command. I used drvload.exe & it shows success but actually it didn't load the drivers & I am unable to see the drives.
    But interestingly I am able to load the RAID drivers manually in Windows 7 Setup screen.
    Please help me to load the drivers in WinPE.
    Thanks,
    Sourav D Gupta
    Born to Learn

  • Problems with Xserve RAID

    I have been having problems with Xserve RAID, which happened in a close time span, but may not be related. The Xserve RAID is set up with 7 disks with RAID 5, totaling to 1.3TB in storage capacity.
    First, the first disk failed and the RAID system was degraded. Since I got a very similar 250GB harddisk (but without "Apple Firmware") I tried putting it as a replacement. It was recognized but it became a hot spare disk, even though I did not set the system to use hot spare.
    Later Mac OS X reported that the Xserve RAID's 1.3TB volume was unmounted. I check with Disk Utility, and it reported a lot of errors. I ended up with about 70GB of files in lost+found, and I confirmed that many files were missing. Disk Utility could not really fixed it.
    I put back the failed disk, and Xserve RAID successfully rebuilt the array. I did "Background Array Conditioning" to perform surface scan and mapping of bad blocks. It completed without error. I then did "Verify Parity Data", and it completed but with error, as follows:
    Event:
    Disk 5 Reported An Error. COMMAND:0x37 ERROR:0x64 STATUS:0x81 LBA:0x119E6880
    Description:
    The drive reported ATA error. This is a failure in the communication from the RAID Controller to the drive.
    Any idea what is happening with this Xserve RAID? Bad disk? Bad controller? Or what? Any help is appreciated.
    Thanks,
    Xserve RAID Dual G5 2.0GHz   Mac OS X (10.3.9)  

    After reading here and there on the net (including this forum), yes I realized that the "Apple Firmware" thing may be significant after all. But since I set the Xserve RAID to use RAID 5, a failure of one disk should not affect data integrity. And surface scan was successful, implyingthat all disks are now free from defects. So why did it lost 70GB worth of data? I experienced disk hardware failure often with Windows system but never experienced losing data while the hardware seems to be fine. Without knowing why this happened, I feel scared to put data on Xserve RAID, and this is ironic since this 1.7TB Xserve RAID is meant for storing data safely...

  • Video FX: video effects and editing drive (incl. RAID disk arrays)

    Having had an issue with rendering iMovie effects and read through a few posted thread, I ran an experiment that pinpoints an incompatibility between iMovie and large size (800GB) RAID array volumes. Hence the following questions:
    Is iMovie designed to support large sire RAID disk arrays ?
    Could anybody test a non-RAID array large size (say 500GB or better 1000GB) volume to check if it is size or RAID dependent ?
    When can we expect a fix ?
    For more details, please read on.
    Reading through the other threads talking about the Quartz composer effects, it sounds like the Apple programmers have a lot of work ahead to deliver a more robust 6.0.2 version.
    I wanted to record the noticed incompatibility of working with a project outside the System & Application drive and applying Quartz composer effects.
    Most keen videographers are using either a good large size external drive, a RAID array or a separate partition to store their video footage and editing work. So the noticed incompatibility needs to be looked into.
    Interestingly, I read of other users having the same problem but Karl Petersen also mentionned that he didn't have the problem ...
    So, what's wrong ? If the problem would be consistent, it would be easy to have Apple on their toes to fix it, but if not ...
    So I ran a small experiment. I took the same iMovie project and copied it to my different disks and volumes (at least the ones where I had enough space) and tested 3 types of effects:
    -1- the non-Quartz Composer 'fast/slow/reverse' effect, which caused me trouble already in iMovie '05;
    -2- the Quartz Composer 'sepia tone' effect, which I was using without problem in the previous version;
    -3- the non-Quartz Composer 'aged film' effect, which I was using without problem in the previous version;
    My disk and volume configuration is the following:
    -> First internal 500GB Serial ATA Disk split into 3 partitions:
    a) 30GB System & Applications Drive (Start-up Disk);
    b) 20GB Pictures Drive;
    c) 415.6GB Partition as Slice 1 of my Apple RAID array;
    -> Second internal 500GB Serial ATA Disk split into 4 partitions:
    d) 15GB Virtual PC System & Applications Drive;
    e) 15GB MAC & PC Documents Drive;
    f) 20GB Musics Drive;
    g) 415.6GB Partition as Slice 2 of my Apple RAID array;
    -> Internal 831.3GB Apple RAID Array - striped RAID set made of 2 slices (volumes c and g above);
    -> External 120GB FireWire Disk in one volume.
    All volumes are formated using Mac OS Extended (Journaled) format.
    The result is consistent and points towards an incompatibility of iMovie with either very large size volume or RAID array. Indeed, all tested effects preview fine on all tested volumes, however, they can be applied seemlessly on all tested volumes apart for my large size RAID array.
    When the project is on the RAID array, hitting the apply button results in the following:
    For the non-Quartz Composer 'fast/slow/reverse' effect and the Quartz Composer 'sepia tone' effect, rendering starts but then stops a fraction of a second later (as if it was unable to write the rendered file to disk). Resulting image in the video viewer is shifted diagonally to leave a black corner on the bottom-left.
    For the non-Quartz Composer 'aged film' effect, rendering starts and proceeds but the resulting image in the video viewer is again shifted diagonally to leave a black corner on the bottom-left. Note that resizing the iMovie window corrects this viewer issue.
    Conclusion:
    Is iMovie designed to support large sire RAID disk arrays ?
    Could anybody test a non-RAID array large size (say 500GB or better 1000GB) volume to check if it is size or RAID dependent ?
    When can we expect a fix ?
    Regards,
    Alex

    I had the same problem rendering a movie with iMovie 6 when the file is placed on a second internal disk.
    Clicking the 'Ignore ownership on this volume' tick box is a solution but I find it too blunt. My Mac is configured as a multiuser system and I bought the second internal disk to use it for my /Users directory. I thus don't want the different users to be able to create files in each others directories.
    When unclicking the 'Ignore ownership on this volume' tick box again I'm surprised to find that rendering still works fine for all users with the desired file integrity.
    I would have preferred to set up all the permissions using unix commands instead of all this magic. Can anyone explain the proper way to configure the correct permissions using the Terminal?
    Power Mac G5 DP 1.8GHz   Mac OS X (10.4.5)  

  • How to mount Aiport Extreme Disk - Leopard

    Just got a miniStack v2. Added a 500gb PATA. Formated the disk while hooked up to my macbookpro. Then moved it to my Airport Extreme via USB. My MBP sees the drive when I open my Mac Harddrive under the shared tab>central station>minStack 500GB.
    What do I do now to mount the drive and start using it as backup, etc?
    Is there something that I need to enable somewhere like "mount all airport disk?" or something in the airport utility?

    I got my air disk to mount. A little bit of legwork on my part and found the drive thru looking on my drive and shared folder. Definitely different than tiger.
    Here is my new problem. I moved some folders and files from my leopard mbp, but when I mount the same air disk on a mac mini g4 running tiger I can not see any of the folders (besides "shared") or any of their contents. Even the "shared" folder show nothing but empty.
    The only thing I did on the leopard machine was customize some of the folder icon styles, gave them more slick looking icons.

  • Display status of raid disk

    I have create a raid set with two disks.
    I have disconnect 1 of them but the system didn't show no warning for this fact.
    If I look into disk utility then I see that raid is degraded, but no warning in find.
    This may be a problem because if a disk is in failure and the system don't warn it, then you use the raid set like it is ok.
    But you work only with one disk and you can have problem if also the second disk goes in failure.
    Do you know if there is a way to have a warning if raid set is degraded?
    Thanks.

    So you have a mirror, and they are on (FW, eSATA, soemthing else?) and each has its own interface cable, right?
    And the RAID was created with Apple Disk Utility, maybe Leopard rather than new Snow Leopard (there are usually changes to partition tables and features, and rebuilding is often a good idea - ONCE you know you want to. You may even want to wait until next OS update too.
    If you want better warnings and features, buy SoftRAID, and faster mirror read performance.
    Rebuild degraded mirror
    http://www.macfixit.com/article.php?story=20090623123621959

  • Auto-Mounting Network Shares/Disk Images

    Hi,
    I'd like to share how I solved my problem with auto-mounting a network disk image/folder share to be used as a custom library/location for Aperture 3.xx. I can now either reference the master photos from the network or have it copy to this disk image volume on the network, although it might be better to have it copy to the disk image volume, so one can move it around as a file later. I researched hard over these forums and internet resources and discovered what I thought was the best way to accomplish this. Initially, I found right away that Aperture doesn't allow you to create a library over your network drive or a home server such as mine, unless it is partitioned/formatted to Mac OS. This wasn't acceptable for me as I also run Windows 7 PCs that need to utilize the network folder shares, as well.
    I don't understand why I don't have this problem using iPhoto 2011, and do with Aperture 3.0, which is a far more expensive application. Anyhow, I read a little about NFS, but didn't know how to implement this or if it required the Mac Server and/or a non-built in application, it probably isn't compatible with windows. So, I found that by creating a .DMG disk image file, as a partitioned/formatted Mac OS file in Disk Utility, and saving it to the network folder of my choosing, did the trick.
    Steps I used to accomplish this:
    -Go to Disk Utility and create "New Image"
    -Select format w/ MacOSX Extended(journaled) and choose "single partition/GUID" type (or whatever you want)
    -Enter a custom size of your disk image (ex in 1GB or 1TB). Click "Create"
    * I created this locally 1st and then I copied it over the network, to the network folder/subfolder on my HP Mediasmart Home Server EX495. I found that creating it over the network took too long and would crash Disk Utility.
    -After it's copied to your desired location over the network folder, open Automator.
    -choose "Application" workflow, double-click to add "Get Specified servers". Enter location of your server (ex smb://hpserver/)
    -Then add "Connect to Servers",
    -Then add "Get specified Finder Items". Click Add, and locate your disk image file over the network. (this will automatically add the location path. For ex. smb:/hpserver/photos/aperture_library.dmg)
    -Then add "Mount Disk Image".
    -Then test workflow by clicking on "Run" button on top right of window. If your
    Finder->Preferences->General settings on your Mac is set to show "Connected Servers" on your desktop, your disk image will appear on you desktop.
    -Finally, save this Application workflow as an application by clicking File menu->Save As. Save this to your documents folder area.
    -To have your Mac auto-mount your disk image automatically when you login:
    ->go to System Preferences->Accounts->your "Admin account name"->Login Items
    ->click "+" sign and navigate to the Documents folder, to where the Automator application you saved
    ->click Add. Once done, it will appear on the Login Items area. You can choose to hide it, if you want by clicking the checkbox.
    -Now Restart your Mac, and now your disk image should auto-mount.
    Hope this helps, as it helped me solve the issue. Too bad one must have to program this and it is not native on MacOSX.

    Too many steps. Do this:
    1. Go to Disk Utility and create a disk image with the following properties:
    Format: Mac OS Extended (Journaled)
    Partitions: Hard Disk
    Image Format: Sparse bundle disk image
    2. Copy the image you just created to the share on the network where it should reside.
    3. Open System Preferences, and click on the Accounts icon
    4. Select *your account* and click on the Login Items tab
    5. Drag the icon for the disk image from the network share into the Login Items list
    If a login item is something on a network share, it will reconnect to the share it's located on automatically first.
    If a login item is a disk image, the disk image will be opened and mounted.
    It's important that the image is a journaled one because if it isn't, being disconnected from it while writing would be potentially disastrous.
    It's important that the image is a sparsebundle for two reasons: sparsebundles only take up as much space as they need (e.g., a 1Tb sparsebundle with 100M of data takes up about 100M of space), and they also break the disk down into smaller files. If the underlying filesystem on your network share is FAT32, then no file can go over 4Gb. If you use a sparsebundle, of course, there's no practical limit to how large the disk image can get. Also, it can speed up certain types of backup procedures.
    I suggest using partition type "Hard Disk" instead of "1 partition GUID" because, as a disk image, there's no sense in having a partition table or making it bootable (because you can't boot from the image).

  • Could not mount Volume "Lacie Disk" HELP!

    I have had a Lacie disk plugged into my Airport Extreme and have used it for wireless transfers and backups just fine since April...
    I have an alias of the Lacie on my Desktop and clicking this has allowed the drive to mount.
    Today, for some unknown reason I get MOUNT FAILED, could not mount volume "Lacie Disk".
    Can someone please help trouble shoot? I have tried restarting the computer and restarting the drive and Airport Extreme. I don't know what hapened.
    Help is greatly appreciated...!!
    Bill

    Hen,
    Just thought I'd drop by for an unsolicited essay on this kind of problem. In my experience, computer don't have luck (and they're low on the food chain relative to vacuum cleaners).
    However, always suspect an Apple enhancement if you've just upgraded & fixed permissions. Upgrades change things, but they also patch vulnerabilities that were there: be paranoid. They also add bulk (usually), and a resource-started computer can react in strange ways.
    So, did you check your previous network settings for accuracy first?-for, dare I say it here, some 'trojan horses' change these. (I always treat a new problem first as a security problem.) If not, you should check them in a week and assure yourself they're what you typed in.
    My LaCie drive, though a DVD burner, just quit after the last 10.4.11 upgrade (or iTunes or Quicktime upgrade). On my other Mac, upgrading Quicktime & iTunes caused downloaded virtual disc images to fail to mount, with no error message in any log. The second I traced to a new Apple intolerance for home-made typefaces, three of which I removed from the 'computer collection' (where they shouldn't have been anyway). The first problem is proving more elusive. I fear a conflict with a so-called 'third-party' device driver.
    The professionals' second maxim (after 'take the defaults') is, 'when trouble strikes, reboot'. (This is for the 5-minute corporate repair; they dump to logs & perform essential postmortems after hours.) Your solution is a variety of the second. (As is the deleting of preference files when trouble strikes.) Even if this fix is permanent, check your network settings now, to see whether they've been changed.
    Bruce

  • RAID ALERT: RAID disk 0: WARNING -SETFEATURES SET TRANSFER

    Hi All,
    I'm receiving this alert onmy Ironport C160. What and How I should do?
    Thanks in advance.
    ~~~~~~~~~~~~~~~~
    A RAID-event has occurred:
    RAID disk 0: WARNING - SETFEATURES SET TRANSFER MODE taskqueue timeout
    - completing request directly RAID disk 0: WARNING
    - SETFEATURES SET TRANSFER MODE taskqueue timeout
    - completing request directly RAID disk 0: WARNING
    - SETFEATURES ENABLE RCACHE taskqueue timeout
    - completing request directly RAID disk 0: WARNING
    - SETFEATURES DISABLE WCACHE taskqueue timeout
    - completing request directly RAID disk 0: WARNING
    - SET_MULTI taskqueue timeout - completing request directly RAID disk 0: TIMEOUT
    - WRITE_DMA retrying (1 retry left) LBA=46304703
    Version: 7.0.1-010
    Serial Number: 0025643D44EA-98LHJL1
    Timestamp: 29 Mar 2012 11:13:27 +0800
    To learn more about alerts, please visit our Knowledge Base.  In many cases, you can find further information about this specific alert.  Please click the Knowledge Base link after logging into our Support Portal at:
    https://supportportal.ironport.com/irppcnctr/srvcd?u=http://secure-support.soma.ironport.com/products/&sid=900002
    If you desire further information, please contact your support provider.
    To open a support request for this issue, access the IronPort C160 and issue the "supportrequest" command. The command sends an email with diagnostic information directly to your IronPort support provider to facilitate a rapid diagnosis of the problem.
    Thank you.

    Call TAC, they'll have you open a secure. support tunnel from your WSA, and they can dig into what's happening.
    There isn't much you can actually do to the raid set.
    You should also backup your configuration off of the box. Make sure to save it with the passwords unmasked, so if they have to send a replacement, you'll have something to restore.

Maybe you are looking for