Raid not mounting, only mounts after restart

When i restart the MP, the 4tb RAID (2x WD Black Cav.) fail to mount, but show in disc utility.
When I restart, the RAID Shows - Is this a sign they are about to die... I bought them in Oct 2011 - around the same time as the inflated HDD prices due to the Tsunami (so perhaps were bothed in the manufacturing process).
Ive also noticed that when a external usb drive is connected when booting up, it will hang on the blue screen.
Is any of this normal?
appears one disc isnt mounting in DU
I have since restarted amd made a backup just Incase
I took a screen grab here - http://forums.macrumors.com/showthread.php?t=1422333

If everything seems fine but the RAID is just "not there" the two big places to look are hardware issues or LUN masking. If your fibre cable connections seem fine and the computer is showing the SCSI devices in System Profiler and the Fibre Channel Utility sees the ports then look to LUN masking. You'll need to run version 1.5 of the RAID admin tool (it was removed in v1.5.1) and make sure LUN masking isn't checked 'on'.
Good luck,
=Tod

Similar Messages

Time Capsule not mounting after Restart

I have only used Time Capsule for 2 days. However, it does not mount after Restart. I have to manually go in to the Time Machine Preferences and choose it again as the backup disk. Is anyone else having this issue, or is that the way it is supposed to work? Please help.

I can see where you're coming from. I have just invested in an iMac with iLife08 , iWork08 and .Mac
I saw getting this Time Capsule as the logical last step in this splurge.
I still have an old Dell desktop WIN 95 vintage which is still chugging along, VERY slowly, its specs having been increased way beyond what its makers ever planned.
I think (hope) this Time Capsule saga is a bit of a blip, superimposed on software (Time Machine) which has not been fully ironed out yet.
As you say, "Works straight out of the box" and "one click and thats it" are statements one took for granted with Apple,but with a big push coming from the suits, perhaps things are shipped too early.
From what I had heard of Apple, I would have expected better.
It was amazing to read the frustrations of Mac veterans in their efforts to get the Time Capsule up and going - and they appeared to know what they were on about.
I have to admit that I wasn't quite sure at first what exactly I was installing, but settled for a wireless external drive on my existing network, which doesn't have any other Apple products.
Even that setup has gremlins.
I am hoping that soon one of the mags will devote a feature on clearing the decks and starting from scratch with DETAILED instructions. I found that the installation bumpf which came with this brick stopped at the point where things got tricky.
Keep the faith!

Acfs not mounted after rebooting..

Hi,
I have create acfs filesystem . but that filesystem is not mounted after rebooting server? how to enable auto mount?
OS version : RHEL 5
Grid Version : 11.2.0.2
ASMCMD> volinfo -G ACFS_U06 ORAHOMEVG
Diskgroup Name: ACFS_U06
Volume Name: ORAHOMEVG
Volume Device: /dev/asm/orahomevg-92
State: ENABLED
Size (MB): 7168
Resize Unit (MB): 256
Redundancy: UNPROT
Stripe Columns: 4
Stripe Width (K): 128
Usage: ACFS
Mountpath: /u06/app/oracle/product/11.2.0.2
Thanks

Register the mount point with acfsutil utility.
oracle@rmdydbitdb1 $ acfsutil registry -h
Usage: acfsutil [-h] registry [-l]                     - Display registry contents
                -l <mountpoint>          - Display a specific mount point
                -l <device>              - Display a specific device
                -m <device>              - Display a specific mount point associated with a device
                -a [-f] [-o <opts>] [-n <nodes>] <device> <mountpoint> - Add a mount point
                -d [<mountpoint> | <device>] - Delete a mount point or a devicehttp://docs.oracle.com/cd/E11882_01/server.112/e18951/asmfs_util010.htm#CACGHBHI
Thanks
Kuljeet Pal Singh

Hard Drive Not Mounting After Being Magically Changed to Read Only

I was using a firewire connected, verbatim 1tb drive as a time machine. Everything had been working fine, but I walked away from my laptop for the morning and came back this afternoon to find my hard drive changed to read only. Time machine wouldn't back up to the hard drive; so, I rebooted.
Since then, I haven't been able to get the hard drive to mount. It won't show up in Drive Utility or on the desktop. I have rebooted the hard drive, unplugged it, turned it on and off.
What should I do? How do I fix this? It has my backups and my music. I'm no amused.

I've had exactly the same trouble this morning.
I'm using a MacBook Pro with my Time Machine on a portable Hard Drive. When doing my regular back up the computer froze. I force restarted the computer and the TM drive came up as 'Read Only'.
So, I rebooted again and the drive is not mounting at all. I can see it connected through System Profiler, however the drive isn't showing up in Disk Utility.
Does anyone have any ideas? Coz I don't seem to be the only one with this issue.

USB drives not mounting after sleep

I've started to experience a frustrating problem whereby any connected USB drive fails to mount after the Mac has been to sleep. Rather alarmingly I get an error message saying "disk not ejected properly"
The set-up I have is two USB drives connected to my early 2011 MacBook Pro via a D-Link mains powered USB hub. I'd planned to have the Mac wake up at 2am for SuperDuper to perform a backup but it's proving impossible as the drive is never available and I have to do a restart before the Mac sees it again.
I've tried a few solutions I've seen online such as installing Jettison (didn't work) and making sure Spotlight isn't indexing the drives (didn't work either).
Can anyone suggest anything else?
THANKS

You can boot OS X from USB2 or FireWire as well as internal drives. There are also two unused SATA ports hidden away inside that OS X can use, but Vista/XP won't see. There is a $24 kit from NewerTech to connect SATA cable, run out PCI slot adapter, and use eSATA shielded cable to a 2-drive enclosure ($67+).
I always boot from an alternate boot drive before ever doing an Mac OS update - repair the drive, do backup, other maintenance. And even sometimes apply the update from there (requires using a standalone downloaded combined update, which is preferred method). Never apply an update w/o a working bootable backup. Something that requires multiple licenses I suspect with XP/Vista.
I have external backup and restore drives for Vista, Mac OS boot drive, 2-drive RAID for Vista, and Vista boot drive.
All of my drives are GUID. Vista is 64-bit, and has some support for EFI (SP1 will bring better support for UEFI).
Disk arbitration has been updated and improved and some products even had to wait for later versions (10.4.8 introduced a number of fixes I understand). I would be more concerned with make of drives and whether they have GUID/GPL or MBR partition tables.

Drive not mounting after boot

I believe this is an epidemic problem in OS X. I have seen this problem on OS X 10.5 to 10.8.2. The fundament issue is that external drives will not mount randomly after the system is powered down and restarted. I have seen the problem with USB 2.0 and Firewire attached drives. I have seen this on many hardware platforms from PowerPC to i7 2.6GHz. I have seen the problem on different enclosures, WD, NextStar, Lacie etc. I have tried numours remedies like resetting the PRAM. The only remedy that works is unpluging the drive and pluging it back in, which if very annoying espicially since this is most prevalent in Time Machine backup drives. The many people who I help with their MACs don't often notice that Time Machine has been failing to backup for weeks since their drive has silently not mounted. Is there a real solution for this out there? It seems to me like a boot timing issue. Where the drive is not recognized by the low level driver, if it becomes powered on at a later time in the boot cycle. I can't really pin it down as it happens often but not often enough for any predictable pattern.

I believe this is an epidemic problem in OS X. I have seen this problem on OS X 10.5 to 10.8.2. The fundament issue is that external drives will not mount randomly after the system is powered down and restarted. I have seen the problem with USB 2.0 and Firewire attached drives. I have seen this on many hardware platforms from PowerPC to i7 2.6GHz. I have seen the problem on different enclosures, WD, NextStar, Lacie etc. I have tried numours remedies like resetting the PRAM. The only remedy that works is unpluging the drive and pluging it back in, which if very annoying espicially since this is most prevalent in Time Machine backup drives. The many people who I help with their MACs don't often notice that Time Machine has been failing to backup for weeks since their drive has silently not mounted. Is there a real solution for this out there? It seems to me like a boot timing issue. Where the drive is not recognized by the low level driver, if it becomes powered on at a later time in the boot cycle. I can't really pin it down as it happens often but not often enough for any predictable pattern.

External drive not mounting after crash

I had the finder lock up on me and I had to force a restart.
At the time an external USB2 drive was plugged in. Since the forced restart the external drive is not mounting. It won't mount via USB2 or Firewire. It is formatted as Mac OS Extended.
Upon booting the computer notifies that it can't be read and asks to initialize, ignore or eject.
The system profiler sees it. Disk Utility sees it but it won't allow the options to verify or repair to be used.
Disk warrior, Drive 10, and Disk Rescue won't allow the drive to be fixed unless its mounted. In fact the drive won't even appear as an option in those programs without mounting.
So what do I have left to try?

After trial and error and moving the drive around to various enclosures I had Disk Utility open up the options to verify and repair.
It wouldn't actually fix it or go through the whole process of fixing it but that was enough to let a boot from the Disk Warrior CD see the drive as an option.
I only recovered about 60% of what was originally on it after DW redid the directory but it was at least something.
One question though what sort of issues could my boot drive's directory have that would effect the external ones? Is the corruption the fault of the internal drive?
I ask because although I've been assured that it will work fine I am running a 160G drive in a machine that only sees the first 128GB as the boot drive. I am not 100% positive that won't have some side effects but everyone around here seems to tell me its all good and that I shouldn't worry about that. Its this belief that makes me use the external drive as my torrent media drive since there is so much more reading and writing being done to it.

External hard drive not mounting on restart

Hi
I have 3 x 4TB RAID0 G-Tech EHDs. One of them only works at all when connected via the USB socket on the 'old-style' plug-in keyboard (USB2) but will not mount at all via the USB3 sockets. (This query is in another post)
Today's 'problem' is that another of the drives (not the above problem one) will not remount on restarting the iMac. (It is left on whilst the iMac is off). By turning off the EHD and on again it remounts normally. Why does one drive mount OK when left on and this one not?

Welcome to the "Mountain Lion Destroys Hard Drive" club.
Join in. There is only a few thousands of us here.

USB 3 external drive volume not mounting on restart

I've bought an external USB 3 full size hard drive enclosure case and put in a 2TB drive. The drive is partitioned into 3 volumes. I've noticed from time to time that the volumes have gotten dismounted some how. If I unplug the USB cable and plug it back in the volumes mount again. After a long time I finally figured it out that what's really happening is that the volumes are not mounting when I do a restart, I just didn't notice it before. Once the volumes are mounted they stay mounted until the next restart. I replaced the enclosure and cable with a different and more expensive brand but that didn't make a difference. No matter what I do the volumes never mount on restart.

I think this might be due to the fact that my iMac as a fusion drive and it boots so fast that the exteranl drive isn't finished starting up when OS X is looking for drives durring it's bootup.

Hard drive will not mount after optical drive upgrade

I recently performed an optical drive install. Had to remove the hard drive bays (I use three hard drives - Luckily, 2 run OSX).
I carefully removed all three drive bays and the empty bay. When I inserted the drives into the computer I had changed the position, swapping one OSX drive with a different one and reversing the drive bays. On restart, the computer started on the drive I had not selected for startup and I received an error message stating the other drive could not mount and it gave three options (Initialize - Ignore and Eject).
I can see the drive in Disk Utility and repair the permissions (it's also located in the System Profile).
I tried a few things I read in the community using various Terminal commands but was unsuccessful.
(Let me point out that I recently switched from a PPC G5 to MacPro and swapped the drives from PPC into MacPro and all has been fine until I removed changed their positions in the bays)
Any suggestions/help would be greatly appreciated.

I would recommend you reformat your drives that you brought over, and if possible put in a Firewie case.
Swapping drives will normally not matter but you should use Startup Disk to reset the default after using Option key the first time.
Putting in an optical device shouldn't require removing the drives to get the cage loose and let you put in a 2nd superdirve.
G5 used APM partition map, Intel Macs use EFI and requie GPT/GUID.
A drive with just data should not matter but that is not fool-proof either.
A drive iwth the system from a G5 though can.
During startup the boot process scans all volumes and looks for systems and mountable volumes.
Pull all the drives except the one with OS X that you were using, and put that in bay #1.
I've moved arrays between bays and that never "broke" the array or had trouble mounting and using (even moving to ODD ports).

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

Partitions not mounting after Archive and Install

I have just installed 10.4 after putting it off for ages. My machine is G4DA with 1.5ghz processor upgrade and a Sonnet ATA133 card for hooking up my 180gb Seagate 7200.7 HD.
I had the HD partitioned into three equal 60gb partitions. One for system, users and apps, one for my video stuff and one for my audio stuff.
The install went fine (Archive and Install option) onto the System partition. However after restarting, only the System partition is mounted. Disk Utility recognises the other two partitions (they have the generic document icon next to them rather than the little HD icon). When I run the repair it tells me there is nothing wrong with either partition.
Disk Warrior also sees the partitions and also repairs them fine without any errors. Even the VISE installer for some of my software installs lists the partitions as available to install on but neither mount.
I have been able to recover the data from the partitions using Data Rescue. Just wanted to know whether there was any way of getting the partitions to mount via the command line or otherwise before I resort to reformatting the drive.

The Terminal.app command diskutil will do that. Launch it and type
man diskutil, hit the return key, and read all about it.

RAID not mounting

After a reboot the RAID won't mount, i can see the RAID on the xserve Disk utility in grey (not mounted) when i click mount the utility doesn`t nothing. How can i mount it? is possible to mount using other utility?? i verified and repaired the raid, no problem found. Tryed to change the fiber cables and switch them.
Plz Help

This may be a little too late, but maybe it will help. I'm not sure why this happens. I reinstalled my server, and I could not access the drives, even though they showed up in disk utility (as a blank file).
Here is what I did to fix it:
1. Open up Disk Utility
2. Make a disk image of the drive you want to mount, save this somewhere accessible (i saved it on another one of my RAID drives)
3. Erase the disk, it should then mount and be accessible
4. Restore the image onto the drive.
Cheers!

Lacie drive not mounting after updating to 10.4.8

Hi,
I have a 160gb Lacie d2 external hd, and after updating my OS to 10.4.8 in October, it will not mount. It's recognized in Disk Utility, but will not mount. I've tried repairing disk permissions from both my current OS and from the installer DVD, but it isn't helping and I keep getting the same message.
When I first updated to 10.4.8 in October, my computer had problems re-starting (it would get stuck at the blue boot-up screen), so I had to turn it off by holding the power button. Ever since then, the lacie drive won't mount.
Is there anything else I can do? I've thought about trying Disk Warrior, but if possible I'd like to save the $100 to buy it!
Any advice? I would really appreciate it.

What I think.
The major changes occurred in the 10.4 original Tiger release. Due to the nature of what I believe the problem is 10.4.7 would just be changing how, where and when the issue(s) become most noticeable to you and not solve it. It will leave you hangin' somewhere else. This I/O API does effect everything. I only wanted to finish a movie with iMovie and set some clips at 00:05 f as I have done forever. Bought a new MacBook Pro specifically for OS X.4 and iMovie and all that was over. iMovie as well as many other Universal apps are IMO mostly non functional except at the OS and QT interface. All other Universal apps and devices cause it to choke and sputter as things pass through this very same I/O API that is causing the external HD issues. As for the PB G4, I was believing the age of the machine to be causing these failures then I had noticed many others developing the same issues on newer G4 machines. Most puzzling was the performance hit on the machines with the proper HW especially larger Core Image supported graphics cards as 10.4 has made this a very relevant piece of HW now. The more I read about the how's and why's of the changes in the architecture of the OS in the Developer Connection the more I realized that many issues that seem so unrelated are indeed caused by the same area and or error in this API. iTunes, Safari, iMovie, iPhoto, -.. CPU's, Fans, HD's, jpegs choking G5's and intels-.. plug n play's that worked yesterday not today, same machines/HW new OS.
Photoshop CS and, an extremely resource greedy, 3D Modeling/database application running in Rosetta works fine. Animating 3D graphics on the fly without so much as a stutter everything calm and quiet. Open Safari and the comp gets too hot to handle the fans are screaming just displaying basic window graphics here at the Apple Discussion boards. Most times this is a text only forum for me as the MPB can't even process the window graphics, often the original posts push-pin graphic is the only one that will display.
AFAICT Rosetta is just an application with no graphic user interface and it is not Universal Binary therefore avoiding this I/O kit as it was designed for the specific configuration of the MacIntel only and works fine. Apple's iLife and iWork apps especially, as well as any SW using this I/O Kit API for Universal Binary apps don't work properly. Anyone with a later G4 and especially a G5 with a good, Core Image supported, graphics card should be feeling like they have a new machine, not saying "hey my stuff isn't working anymore" or slow imports of files or processing.
Personally I would:
Start up from 10.3 install discs, back up my docs to external HD and re-partition the internal HD. At least two, IMO three partitions (do not journal OS partitions) would be the least. Install 10.3.9 on one 10.4+ on the (an)other. Docs on the third. Keep the OS partitions as small as possible while allowing for OS's extra "operating space". 3.9 only requires about 2-5 GB's above required space to install while OS 10.4 seems to need 5-10 GB that is always "free" depending on what you are doing and also allowing for any OS and app. updates that may come before the next OS X release. 3.9 is already maxed so one can assume no new news here.
My G4's HD set up is 6 partitions as it is now mainly a slave hub between my MBP and my "legacy" products PB G3, serial devices, Zip drives, modems, SCSI devices, scanners, printers old apps/file formats. Apps and HW that are still useful but "max out" at a certain OS/comp configuration are installed on that OS's partition, i.e. QT w/MPEG-2, Virtual PC, or Photoshop plugins that were never developed or not worth the investment for OS X or the current release as they are not used often enough etc.
5GB-9.2.2, 10GB-10.2, 15GB- 10.3.9, 20GB-10.4.6, 15 GB Apps. 35GB docs. Nothing gets written to any OS partitions unless absolutely required. All OS's share the apps they can (except 9 apps) and document partition. As far as I understand I should be able to use XGrid to use these other computers processors through the MBP. A "super computer" kind of set up with the G4 at the least, but documentation indicates it should work on any OS X so possibly my G3 as well which stopped at 10.1.
You do not have to duplicate apps and I would install and update all through 3.9 even if you install them in the 10.4 Apps. folder. At most you may need to create a couple of folders in the OS's System Library for Application Support or plug-ins etc. If you fear one OS reading from the other's Library/System files you can unmount the other OS volumes but I have yet to see this happen without intentionally directing the OS to do so.
I would do all my external back ups and device communication (cameras, HD's MIDI's etc) booting in 10.3 only. For me the G4 booted in Target disk mode seems to be the safest way to access an "external HD" via FW with the MBP. I have had zero problems with this method. A two step process for files that don't reside on the G4 but I'd rather be safe than sorry and I have already lost one HD that was completely unrecoverable (a mechanical rebuild lead to the discovery of overwritten files with driver type data and damaged disk surface from arcing). Small files I just access on the external HD's through G4 over the airport network. I have not used Bonjour in depth yet though will most likely incorporate that into everyday use as I was able to quickly transfer a few very large files to a friends MacBook with it. Used this Just after realizing the MBP lacks IRDA and neither of us had any cables with us.
The above type of configuration would give you the ability to move forward with 10.4 and easily work around HW, SW and connectivity issues by booting into 10.3 when needed. This is a great way of trouble shooting OS and app issues. My MBP already has a partition waiting for Leopard. If the OS lacks something or has problems of it's own I can boot back into 10.4 quickly and easily. If all is well with Leopard 10.4 will definitely be removed. The G4 will never see Leopard except over a network.
Sorry to be long winded. Hope this gives you some reasonable ideas. In a nutshell. I believe the problem is that the OS and QT are set to higher, more accurate standards (ISO's MPEG's, SMTP's, IEEE's etc) than in the past and the I/O API is unable to communicate/calculate and transfer the information properly between devices and apps.
BTW when your LaCie appears to have given up the ghost and will not respond at all, before you toss the whole thing remove the HD and put it in a different enclosure. I have dealt with hundreds of these and the Firewire ports on the PC board become too hot and melt off. Repair is not possible and although this is a known issue with LaCie no attempts have been made to correct this and they will not sell you a service part to repair it. Replacement would require removal and replacement of two screws and two plugs. Most HD's I have removed are Western HD's and work fine in a new enclosure.
HTH

External Hard Drive not mounting after...drop

Hi all,
Not really a Time Machine question, but my wife, not realizing an external USB hard drive was connected to my macbook, pick up the laptop and the external drive dropped on it's corner...slight damage. It is a 320Gb hard drive with three partitions....two for storage and one for time machine backup. The two storage drives are mounting find and seem OK, but the time machine partition is not mounting. Disk Utility sees the partition but can't mount or repair it and gives me the error "Invalid sibling link, unable to verify or repair."
Any ideas on what I should do next (other than back up the other two drives)? Should I try erasing the disk and see if it'll mount?
Thanks,
John

Johnk93 wrote:
Disk Utility sees the partition but can't mount or repair it and gives me the error "Invalid sibling link, unable to verify or repair."
If you have +Disk Warrior+ (4.1.1 or 4.2 only), or another heavy-duty disk repair app (that you're certain is compatible with Leopard), it might be able to repair the partition. DW is about $100, so unless you think you may need it for other things in the future, it may not be worth the chance.
Otherwise, if Disk Utility can erase it, it's probably ok. In this case, though, it would be worthwhile clicking +Security Options+ then +Zero Out Disk+ to be sure it can write to the entire partition.
Long term, though, I'd be a bit reluctant to trust my backups to it. (Perhaps a hint to Santa?)
Additionally, I am having trouble ejecting the two working partitions. It seems to eject them becuase they no longer appear on my desktop, but I get the "unable to eject...." error message. Not sure what this means.
See what happens after erasing the TM partition. That may clear it up. If not, try mounting them again.

Seagate Free Agant will not mount on restart

Every time I restart the computer 2 new Seagate Free Agent Drives will not mount, unless I pool the power cord in and out. I am using Firewire 800.
I called The Seagate tech support they said that it Mac problem. I have the old Seagate drives and they work fine. The new Silver color drives don't even have the power button anymore.
Did anyone have the same and is there a solution?
thanks.
Message was edited by: Girshon Rutstein

HEllo
I have the BLACK SEAGATE FREE-AGENTS DRIVES and they are the only two that will not restart when I power up the MAC .... I too have to pull power cords or try plugging them in with USB if they are FIREWIRE. Once MAC sees them they are ok until I restart my computer.
What did you find on GOOGLE.....I tried SEAGATE DIAGNOSTICS for MAC, but it doesn't see the drives even though the DRIVES are active at the moment.
THanks
Art

Raid not mounting, only mounts after restart

Similar Messages

Maybe you are looking for