Internal hard drive won't mount after running Tech Tools Pro 5

HELP.
We have an imac 2ghz Intel Core 2 running OS 10.6.8.
I ran Tech Tools Pro 5 to rebuild directory, optimize files, optimize volume. It ran over nightbut seemed to hang up optimizing the volume.
Now the HD doesn't mount.
I've tried a few fixes. Including running disk utility from a CD. The disk utility says the directory is okay but doesn't see the HD to verify or repair permissions.
I've tried zapping the pram and safe boot, neither of which worked.
I've been able to use the computer by booting from an external start up hd.
Oddly, I ran a Time Machine back up prior to running TTP, but for some reason the only back up I see is from 3 months ago.
Not sure why the recent back up didn't happen, but were missing some very important recent docs.
I downloaded a trial version of Stellar Pheonix Mac Data Recovery and it seems to be able to see all of the data on the main HD.
I'm wondering whether or not to spend $100 for full version to attempt to restore content of HD to an external.
If I do this, I assume I'll have to erase the HD and reinstall data from the Stellar Pheonix collection, hoping that it's all intact.
Does anyone have any other suggestions to get the HD mounted????

Hi, never "Optimize" a drive before Repairing it AND having a backup clone to boot from.
I assume I'll have to erase the HD and reinstall data from the Stellar Pheonix collection, hoping that it's all intact.
No, I don't think you want an erase at all, you want a freah external drive to recover to first off.

Similar Messages

Hard drive won't mount after running disk utility repair

I have an iMac with a 320gb hard drive. It will not mount. The small horible wheel started sining so I retared. It could not find the start-up disk. I restared with the CD, after doing this twice the disk was visible in disk untility. I have ran this 3 times and it says the node is incorrect and it cannot be reapired by Disk Untility. It will not mount.
Is there any other way to save the disk so I can get my files off.
Any help is welcomed

You would need the Firewire cable. If you get one then you can use Target Disk Mode - Transferring files between two computers using FireWire to transfer your files to another drive.

Hard Drive Won't Mount After Repair by Second Computer

I have an G4 Cube with OS 10.2 on the internal hard drive (which is full) and OS 10.4 on an external La CIe hard drive (that I use as my main OS). The external hard drive accumulated serious damage that couldn't be repaired by Disk Utility on the internal drive. My copy of DiskWarrior X would not run under OS 10.2 (10.4 was required) and it wouldn't boot from the CD either So I connected the external hard drive to my second computer, an iMAC running OS 10.5. (Unfortunately, I disconnected the external hard drive when the computer was off instead of ejecting the drive by dragging it to the Wastebasket.) The external drive mounted and DiskWarrior easily constructed a new directory, defragmented the files, and eliminated all of the damage on the external hard drive visible to Disk Utility. However, when I reconnected the repaired external hard drive to the G4 Cube, the drive wouldn't mount. Privileges were repaired on both computers with the external drive connected without helping. Being repaired while connected to a higher OS or perhaps simply being connected to a higher OS seems to have left the LaCie external hard drive in a state which couldn't be mounted by an earlier OS.
Following this hypothesis, it booted the G4 Cube from the OS 10.4 Installation CD while the LaCie external hard drive was connected. When I cancelled installation of OS 10.4, I was asked to choose a start-up disk AND OS 10.4 WAS NOW MAGICALLY AVAILABLE ON THE EXTERNAL DRIVE. Simply starting up from a more advanced OS allowed the hard drive to mount.
Shockingly, when I restarted from OS 10.2, the external hard drive was still mounted. Whatever was preventing the drive from mounting was a TRANSIENT STATE, not backwards incompatability.
POSSIBLE LESSON: If a hard drive won't mount on computer A after being connected to computer B, consider booting computer A using the OS on the installation disk from computer B.

If you need to repair a hard drive with OS X installed on it, you must use that same version of OS X to perform the repair. Using another--in this case, newer--OS can cause quite a bit of trouble, as the directories/permissions may be dealt with differently between the OS's.
Seems you've learned this lesson--and luckily you didn't lose anything!
~Lyssa

External drives won't mount after running repair permissions

None of my external drives will mount after running disk permissions. Drives work fine on my mbpro.
None of the external drives show up in disk utilities...
I've try shutting down and unplugging computer. even mini zip drives won't mount.
I'm running 10.4.11
PPC G5 2.3Ghz
Thanks for any help..

Repairing Permission only deals with installer receipts and system components. Not with mounting or accessing hard drives.
Have your run Apple DU First Aid? Disk Warrior? Only use latest version for your OS.
Are you trying to clone your system to external and then repairing permissions? trying to boot from them?
If cloning, make sure the "Ignore Ownership" flag is unchecked before cloning (but do repair permissions on external drives you intend to boot from, such as a Firewire drive).
What type of cases and interface are these?

G5 tower now boots, but one of the internal hard drives won't mount!

For those of you who saw my previous thread, my G5 tower would turn on and play the startup chime, then sit there until the fans ramped up. It seems that the problem was the Belkin PCI card. I removed it, and the machine started up with no problems.
Now, however, one of my internal hard drives (not the primary one) won't mount. Various programs can't even tell it's there. I'm completely lost as to how to solve this problem. My first thought was to try to swap it into an external case to see if it would mount that way. Thoughts?

One, possible two posts should read ground. Test for continuity against the metal case. Another should read 5V+DC. I think the four prong are: ground, ground, illumination then power. The connectors are gold plated and should not corrode, however, they are no match against fine particles of dust. You can carefully unplug both sides of the drive connections and vacuum. Usually, to unplug and re-plug is enough to get it to work again. When there no power coming off the logic board, you can find a Y-splitter and power off the other drive.

My new LaCie hard drive won't mount on my mac book pro

I bought a LaCie P9233 hard drive, I try to connect to my MacBook Pro that runs Mac OSX 10.6.8. I connect and I get a message saying the disk is not readable by my computer. It then gives me the option of "Initialize", "Ignore" or "Eject". Can anyone help?

I believe you hsave to first launch Setup Assistant:
http://manuals.lacie.com/en/manuals/porsche-9233/connection

Internal hard drive/repair: SMART status; Disk Utility, Tech Tool & More

machine: 12" PowerBook 1.5 GHz PowerPC G4 (Aluminium) with 80GB internal HD
internal hard drive (original): Hitachi Travelstar 5K100 series HTS541080G9AT00
hard drive firmware: MB4AA5AJ
ATA version: 6
ATA standard: ATA/ATAPI-6 T13 1410D revision 3a
I have monitored the SMART status etc. of my internal drive with smartmontools for some time. Occasionally, I would see an error or a failed self-test but later testing always succeeded and things did not seem to be problematic.
At the beginning of this week, I started to see a lot of failed self-tests (though some still passed), a rising number of bad ("pending") sectors and reallocation attempts (though no reallocated sectors) and various other errors. The computer seemed to have trouble reading from the disk at times and Carbon Copy Cloner reported two I/O errors when cloning (a later clone succeeded). fsck showed errors although running fsck -fy repeatedly seemed to resolve them.
The Apple hardware tests initially reported an error (2STF/8/3:ATA-100 ata-6-Master) but I hadn't realised I should disconnect peripherals before running it so I did that and repeated the test which found no issues. I ran the extended test a total of three times with no errors.
As I continued to have problems, I booted from my clone and had Disk Utility wipe the drive by writing zeros to it. (I thought trying to get it to write everywhere would either finish the drive off or force it to reallocate the bad blocks. As I understand it, in normal use, the drive won't reallocate the blocks unless it can recover the data in the hopes of reading it at a later time.)
I then continued monitoring the disk using smartmontools. At this point, short self-tests succeed but extended self-tests "disappear". They don't fail, they simply vanish. They begin and smartctl shows the test in progress but then no error or result is logged - it is as if the test was never run. The first time I did this, I got an error saying the SMART attributes could not be read but subsequent tests do not trigger even an error. Short self-tests continue to pass.
There are now (according to SMART) zero bad ("pending") sectors but zero reallocated sectors, which seems odd. The raw read error rate fluctuates (zero one minute, many thousands a while later) although I am not sure it did not do this before.
Disk Utility claims the disk does not support SMART status even though smartctl clearly shows it does. Disk Utility claims the volume is "OK".
I ran Tech Tool Deluxe 3.04 from CD and 3.1.1 from my clone. In both cases, I ran all available tests on the drive. No problems were found.
I am seeing some problems even while booted from my clone - yesterday, the system froze completely and I had to force a shut-down by switching off the power (fsck then found a minor error but repaired it). Just before this happened, I was unable to mount a disk image and was trying to rectify the situation when the system froze. It is possible that the errors fsck corrected were implicated in the freeze, rather than caused by it, since Disk Utility found and repaired similar errors for the other two clones I have (on different partitions of my external drive - yes, I know this is sub-optimal).
Here is some current output from smartmontools:
---output: smartctl -q noserial -a disk0---
smartctl version 5.38 [powerpc-apple-darwin8.11.0] Copyright (C) 2002-8 Bruce Allen
Home page is http://smartmontools.sourceforge.net/
=== START OF INFORMATION SECTION ===
Model Family: Hitachi Travelstar 5K100 series
Device Model: Hitachi HTS541080G9AT00
Firmware Version: MB4AA5AJ
User Capacity: 80,026,361,856 bytes
Device is: In smartctl database [for details use: -P show]
ATA Version is: 6
ATA Standard is: ATA/ATAPI-6 T13 1410D revision 3a
Local Time is: Sat Jul 3 20:28:52 2010 BST
SMART support is: Available - device has SMART capability.
SMART support is: Enabled
=== START OF READ SMART DATA SECTION ===
SMART overall-health self-assessment test result: PASSED
General SMART Values:
Offline data collection status: (0x00) Offline data collection activity
was never started.
Auto Offline Data Collection: Disabled.
Self-test execution status: ( 0) The previous self-test routine completed
without error or no self-test has ever
been run.
Total time to complete Offline
data collection: ( 645) seconds.
Offline data collection
capabilities: (0x5b) SMART execute Offline immediate.
Auto Offline data collection on/off support.
Suspend Offline collection upon new
command.
Offline surface scan supported.
Self-test supported.
No Conveyance Self-test supported.
Selective Self-test supported.
SMART capabilities: (0x0003) Saves SMART data before entering
power-saving mode.
Supports SMART auto save timer.
Error logging capability: (0x01) Error logging supported.
General Purpose Logging supported.
Short self-test routine
recommended polling time: ( 2) minutes.
Extended self-test routine
recommended polling time: ( 55) minutes.
SMART Attributes Data Structure revision number: 16
Vendor Specific SMART Attributes with Thresholds:
ID# ATTRIBUTE_NAME FLAG VALUE WORST THRESH TYPE UPDATED WHEN_FAILED RAW_VALUE
1 RawRead_ErrorRate 0x000b 100 100 062 Pre-fail Always - 0
2 Throughput_Performance 0x0005 100 100 040 Pre-fail Offline - 0
3 SpinUpTime 0x0007 142 142 033 Pre-fail Always - 2
4 StartStopCount 0x0012 097 097 000 Old_age Always - 5793
5 ReallocatedSectorCt 0x0033 100 100 005 Pre-fail Always - 0
7 SeekErrorRate 0x000b 100 100 067 Pre-fail Always - 0
8 SeekTimePerformance 0x0005 100 100 040 Pre-fail Offline - 0
9 PowerOnHours 0x0012 039 039 000 Old_age Always - 26720
10 SpinRetryCount 0x0013 100 100 060 Pre-fail Always - 0
12 PowerCycleCount 0x0032 098 098 000 Old_age Always - 4168
191 G-SenseErrorRate 0x000a 100 100 000 Old_age Always - 0
192 Power-OffRetractCount 0x0032 100 100 000 Old_age Always - 201877487644
193 LoadCycleCount 0x0012 001 001 000 Old_age Always - 2209599
194 Temperature_Celsius 0x0002 141 141 000 Old_age Always - 39 (Lifetime Min/Max 16/46)
196 ReallocatedEventCount 0x0032 100 100 000 Old_age Always - 194
197 CurrentPendingSector 0x0022 100 100 000 Old_age Always - 0
198 Offline_Uncorrectable 0x0008 100 100 000 Old_age Offline - 0
199 UDMACRC_ErrorCount 0x000a 200 200 000 Old_age Always - 0
SMART Error Log Version: 1
ATA Error Count: 2138 (device log contains only the most recent five errors)
CR = Command Register [HEX]
FR = Features Register [HEX]
SC = Sector Count Register [HEX]
SN = Sector Number Register [HEX]
CL = Cylinder Low Register [HEX]
CH = Cylinder High Register [HEX]
DH = Device/Head Register [HEX]
DC = Device Command Register [HEX]
ER = Error register [HEX]
ST = Status register [HEX]
PoweredUpTime is measured from power on, and printed as
DDd+hh:mm:SS.sss where DD=days, hh=hours, mm=minutes,
SS=sec, and sss=millisec. It "wraps" after 49.710 days.
Error 2138 occurred at disk power-on lifetime: 26716 hours (1113 days + 4 hours)
When the command that caused the error occurred, the device was active or idle.
After command completion occurred, registers were:
ER ST SC SN CL CH DH
10 51 00 09 4f c2 a0 Error: IDNF
Commands leading to the command that caused the error were:
CR FR SC SN CL CH DH DC PoweredUpTime Command/Feature_Name
b0 d6 01 09 4f c2 a0 00 08:30:04.500 SMART WRITE LOG
b0 d5 01 09 4f c2 a0 00 08:30:04.300 SMART READ LOG
b0 d1 00 00 4f c2 a0 00 08:30:04.000 SMART READ ATTRIBUTE THRESHOLDS [OBS-4]
b0 d0 00 00 4f c2 a0 00 08:30:04.000 SMART READ DATA
b0 da 00 00 4f c2 a0 00 08:30:04.000 SMART RETURN STATUS
Error 2137 occurred at disk power-on lifetime: 26682 hours (1111 days + 18 hours)
When the command that caused the error occurred, the device was active or idle.
After command completion occurred, registers were:
ER ST SC SN CL CH DH
40 51 28 18 95 98 e4 Error: UNC 40 sectors at LBA = 0x04989518 = 77108504
Commands leading to the command that caused the error were:
CR FR SC SN CL CH DH DC PoweredUpTime Command/Feature_Name
25 00 80 c0 94 98 e0 00 1d+01:30:37.600 READ DMA EXT
25 00 80 c0 94 98 e0 00 1d+01:30:30.600 READ DMA EXT
25 00 80 c0 94 98 e0 00 1d+01:30:22.600 READ DMA EXT
25 00 80 c0 94 98 e0 00 1d+01:30:16.300 READ DMA EXT
25 00 80 40 94 98 e0 00 1d+01:30:14.700 READ DMA EXT
Error 2136 occurred at disk power-on lifetime: 26682 hours (1111 days + 18 hours)
When the command that caused the error occurred, the device was active or idle.
After command completion occurred, registers were:
ER ST SC SN CL CH DH
40 51 21 1f 95 98 e4 Error: UNC 33 sectors at LBA = 0x0498951f = 77108511
Commands leading to the command that caused the error were:
CR FR SC SN CL CH DH DC PoweredUpTime Command/Feature_Name
25 00 80 c0 94 98 e0 00 1d+01:30:30.600 READ DMA EXT
25 00 80 c0 94 98 e0 00 1d+01:30:22.600 READ DMA EXT
25 00 80 c0 94 98 e0 00 1d+01:30:16.300 READ DMA EXT
25 00 80 40 94 98 e0 00 1d+01:30:14.700 READ DMA EXT
25 00 80 c0 93 98 e0 00 1d+01:30:14.100 READ DMA EXT
Error 2135 occurred at disk power-on lifetime: 26682 hours (1111 days + 18 hours)
When the command that caused the error occurred, the device was active or idle.
After command completion occurred, registers were:
ER ST SC SN CL CH DH
40 51 22 1e 95 98 e4 Error: UNC 34 sectors at LBA = 0x0498951e = 77108510
Commands leading to the command that caused the error were:
CR FR SC SN CL CH DH DC PoweredUpTime Command/Feature_Name
25 00 80 c0 94 98 e0 00 1d+01:30:22.600 READ DMA EXT
25 00 80 c0 94 98 e0 00 1d+01:30:16.300 READ DMA EXT
25 00 80 40 94 98 e0 00 1d+01:30:14.700 READ DMA EXT
25 00 80 c0 93 98 e0 00 1d+01:30:14.100 READ DMA EXT
25 00 80 40 93 98 e0 00 1d+01:30:13.500 READ DMA EXT
Error 2134 occurred at disk power-on lifetime: 26682 hours (1111 days + 18 hours)
When the command that caused the error occurred, the device was active or idle.
After command completion occurred, registers were:
ER ST SC SN CL CH DH
40 51 28 18 95 98 e4 Error: UNC 40 sectors at LBA = 0x04989518 = 77108504
Commands leading to the command that caused the error were:
CR FR SC SN CL CH DH DC PoweredUpTime Command/Feature_Name
25 00 80 c0 94 98 e0 00 1d+01:30:16.300 READ DMA EXT
25 00 80 40 94 98 e0 00 1d+01:30:14.700 READ DMA EXT
25 00 80 c0 93 98 e0 00 1d+01:30:14.100 READ DMA EXT
25 00 80 40 93 98 e0 00 1d+01:30:13.500 READ DMA EXT
25 00 80 c0 92 98 e0 00 1d+01:30:12.100 READ DMA EXT
SMART Self-test log structure revision number 1
Num Test_Description Status Remaining LifeTime(hours) LBAof_firsterror
# 1 Short offline Completed without error 00% 26717 -
# 2 Short offline Completed without error 00% 26717 -
# 3 Short offline Completed without error 00% 26717 -
# 4 Short offline Completed without error 00% 26717 -
# 5 Short offline Completed without error 00% 26716 -
# 6 Short offline Completed without error 00% 26715 -
# 7 Short offline Completed without error 00% 26714 -
# 8 Short offline Completed without error 00% 26697 -
# 9 Extended offline Completed: read failure 10% 26692 75071682
#10 Short offline Completed without error 00% 26687 -
#11 Extended offline Completed: read failure 10% 26676 77108511
#12 Short offline Completed: read failure 40% 26663 296917
#13 Short offline Completed without error 00% 26657 -
#14 Short offline Completed: read failure 10% 26646 296918
#15 Short offline Completed: read failure 70% 26645 296905
#16 Short offline Completed: read failure 10% 26644 296910
#17 Short offline Completed: read failure 10% 26644 296910
#18 Short offline Completed: read failure 40% 26643 296916
#19 Short offline Completed: read failure 20% 26643 296909
#20 Extended offline Completed without error 00% 26620 -
#21 Short offline Completed without error 00% 26618 -
Warning! SMART Selective Self-Test Log Structure error: invalid SMART checksum.
SMART Selective self-test log data structure revision number 1
SPAN MIN_LBA MAX_LBA CURRENTTESTSTATUS
1 0 0 Not_testing
2 0 0 Not_testing
3 0 0 Not_testing
4 0 0 Not_testing
5 0 0 Not_testing
Selective self-test flags (0x0):
After scanning selected spans, do NOT read-scan remainder of disk.
If Selective self-test is pending on power-up, resume after 0 minute delay.
---end output---
Self-tests 1-8 were all run after I erased the disk. The others were run before I did so. Not listed are the extended self-tests I've started since erasing which, as I say, have simply disappeared.
The checksum error regarding the log is normal for this disk. At least, I've got that error ever since I started using smartmontools for monitoring so I assume it is normal. (I installed this version of the software in about April 2008 and have used it since.) Also, starting offline testing has never succeeded on this disk (I think I checked into this at the time but can't quite remember - this is not new, anyway).
Questions
how should I interpret all this? (Why does Disk Utility say SMART is not supported while smartctl clearly shows it is at the same time? Why do the extended tests simply vanish? Is the drive definitely dying?) I do not want to replace the disk unless I absolutely have to because I understand that replacing disks in 12" PBs is no small matter and cost is an issue. I do not want to replace the machine unless I have to because cost is an issue and, also, I really like this computer and have no idea what I would want in its place, even if expense were no obstacle.
if it isn't clear whether the drive is dying or not, is there some further strategy I can use to establish this?
if the drive is dying, is a machine of this age worth repairing and, if it is, under what circumstances is it worth doing so? For example, it might be worth doing if you can do the job yourself, but that might be quite impractical for non-expert (not to mention, inexpert) users.
if there is a hardware problem (which I obviously think is very, very probable at this point), is it definitely a dying hard drive? (I've seen people write ominous things about disk controllers etc. which I gather are more serious - or less repairable - than a "mere" dying disk.)
what questions should I be asking you and what are the answers to those questions?!
Many thanks for your patience in reading this far.
- cfr

The 12" PB internals are a bit more complex, for PB's. If you don't want to replace the hard drive yourself or pay someone to install it, you could always get an external firewire hard drive, and use it to boot from and for general usage. Would have to be firewire, since the PB won't book from a USB device. One example of what you could get is a 160GB external hard drive: http://eshop.macsales.com/item/Other%20World%20Computing/MS4U5160GB8/ . All the choices with that case are listed here: http://eshop.macsales.com/shop/firewire/on-the-go
Have you called any Apple Authorized Service Providers to see what they would charge to install a drive for you? Whether you bought it or they supplied it? You can find a local one in the US at http://www.apple.com/buy/locator/service/

"Extra" Internal Hard Drives won't mount - swap, /, and /home work.

Hello All,
*** I'm updating my post finally. Sorry it's so long, I'm not entirely sure what is and isn't relevant.
*** Also I think it's a mix up with RAID causing the issue, as I'll address below, but in case I'm wrong I wanted to include the other information that came to mind before I noticed the RAID issue (because the RAID issue doesn't make a lot of sense to me).
First off, I'm running Arch64 and KDE4 with my system up to date. Also I have Gamin installed and not FAM. I use ReiserFS on all of my partitions and drives.
I have six hard drives in my computer, all of which are SATA drives. One is a WD 150GB Raptor with my swap, /, and /home partitions on it, the other five are for extra storage on what I call my media-server (they mount to /media/media-server/1 ,2 ,and so on). They only have one partition each. Of those five the first (/media/media-server/1) is a WD 1TB drive, the other four are WD 500GB drives of identical model.
All of the Raptor's patitions, swap, /, and /home mount just fine.
On top of that the 1TB drive mounts just fine. But the four 500GB drives will not mount at all. They show up in Dolphin, Disk Utility, KwikDisk, KDiskFree, and Partition Manager. However, their size is not shown and/or marked N/A, except in Partition Manager, where their size is shown. They are not seen by 'df'.
Output from 'df':
df -h
Filesystem Size Used Avail Use% Mounted on
udev 10M 308K 9.7M 4% /dev
/dev/sda2 25G 7.7G 17G 32% /
none 4.0G 0 4.0G 0% /dev/shm
/dev/sda3 112G 90G 22G 81% /home
/dev/sdb1 932G 919G 13G 99% /media/media-server/1
*** As for removable media, it's being a bit odd. When I first wrote this post removable media, specifically USB flash drives and SD media cards mounted fine. A while after that they'd show up in Device Notifier, but wouldn't mount. Just a little while ago they wouldn't show up in Device Notifier and wouldn't mount. Now they show up fine and mount fine again. This is possibly unrelated, I'm not sure.
Depending on what method I try to mount my hard drives I either get an 'only root can mount that' error or else a HAL drive busy or already mounted error, followed by a 'drive is not mounted' error when I use umount to double check.
*** Permissions are working better now , Dolphin isn't giving me the 'only root can mount' errors anymore. Still can't mount the drives though.
All of this output is from when the drives are listed in /etc/fstab:
Konsole output:
mount /dev/sdf1
mount: only root can mount /dev/sdf1 on /media/media-server/5
sudo mount /dev/sdf1
mount: /dev/sdf1 already mounted or /media/media-server/5 busy
umount /dev/sdf1
umount: /dev/sdf1 is not mounted (according to mtab)
sudo umount /dev/sdf1
umount: /dev/sdf1: not mounted
Dolphin output:
An error occurred while accessing 'MediaServer5', the system responded: org.freedesktop.Hal.Device.Volume.PermissionDenied: Device /dev/sdf1 is listed in /etc/fstab. Refusing to mount.
Device Notifier output (pops up when I try to mount the drives in Dolphin):
org.freedesktop.Hal.Device.Volume.PermissionDenied: Device /dev/sdf1 is listed in /etc/fstab. Refusing to mount.
Partition Manager:
The file system on partition /dev/sdf1 could not be mounted.
Details
==========================================================================================
Command: mount -v /dev/sdf1 /media/media-server/5
==========================================================================================
mount: /dev/sdf1 already mounted or /media/media-server/5 busy
mount: you didn't specify a filesystem type for /dev/sdf1
I will try type reiserfs
At boot, when the daemons are starting I get:
mount: /dev/sdc1 already mounted or /media/media-server/2 busy
mount: /dev/sdd1 already mounted or /media/media-server/3 busy
mount: /dev/sde1 already mounted or /media/media-server/4 busy
mount: /dev/sdf1 already mounted or /media/media-server/5 busy
This is from when the drives are not listed in /etc/fstab:
Dolphin output:
An error occurred while accessing 'MediaServer5', the system responded: org.freedesktop.Hal.Device.InterfaceLocked: The enclosing drive for the volume is locked
Device Notifier output (pops up when I try to mount the drives in Dolphin):
An error occurred while accessing 'MediaServer5', the system responded: org.freedesktop.Hal.Device.InterfaceLocked: The enclosing drive for the volume is locked
I have tried listing (with the UUID method and the /dev method) and not listing the drives in /etc/fstab, and I have 'hal' and 'dbus' daemons in /etc/rc.conf (and I've tried using only the hal daemon and not the dbus in /etc/rc.conf). I've also tried not listing 'hal', 'dbus', and 'kdm' and only booting to terminal and then mounting the drives manually, that doesn't work either.
Here is my /etc/fstab (back to using UUID's):
# /etc/fstab: static file system information
# <file system> <dir> <type> <options> <dump> <pass>
none /dev/pts devpts defaults 0 0
none /dev/shm tmpfs defaults 0 0
UUID=699cdd5e-3f4a-4b85-8dcb-5d00c00c94a9 swap swap defaults 0 0
UUID=ce94e7a3-3e07-41e5-90d7-1116e5da3121 / reiserfs defaults 0 0
UUID=a1dce435-df90-4f0d-892c-61ff3ea0c8d1 /home reiserfs defaults 0 0
## Media-Server
# media-server/1
UUID=81998a75-f887-4a35-b3fa-e159190f25a3 /media/media-server/1 reiserfs defaults 0 0
#/dev/sdb1 /media/media-server/1 reiserfs defaults 0 0
# media-server/2
UUID=8cdd114a-b190-44f6-9240-1910a5d048f7 /media/media-server/2 reiserfs defaults 0 0
#/dev/sdc1 /media/media-server/2 reiserfs defaults 0 0
# media-server/3
UUID=59164593-b56d-4c49-8837-277b3c392dfb /media/media-server/3 reiserfs defaults 0 0
#/dev/sdd1 /media/media-server/3 reiserfs defaults 0 0
# media-server/4
UUID=ba6007bd-1e36-431c-85f4-857c83845c86 /media/media-server/4 reiserfs defaults 0 0
#/dev/sde1 /media/media-server/4 reiserfs defaults 0 0
# media-server/5
UUID=6fab5364-1acb-4ba3-9f83-bb171a6d398a /media/media-server/5 reiserfs defaults 0 0
#/dev/sdf1 /media/media-server/5 reiserfs defaults 0 0
## VirtualBox USB
none /proc/bus/usb usbfs auto,busgid=108,busmode=0775,devgid=108,devmode=0664 0 0
Here's the daemons line from /etc/rc.conf:
DAEMONS=(syslog-ng !dbus hal network netfs crond wicd openntpd sshd avahi-daemon avahi-dnsconfd samba alsa mysqld lircd mythbackend !mpd !sensors !sensord !fancontrol cups keytouch kdm)
Also, /etc/mtab because only the first media-server drive is listed in it (the one that does mount):
proc /proc proc rw,relatime 0 0
sys /sys sysfs rw,relatime 0 0
udev /dev devtmpfs rw,nosuid,relatime,size=10240k,nr_inodes=1014438,mode=755 0 0
/dev/sda2 / reiserfs rw,relatime 0 0
fusectl /sys/fs/fuse/connections fusectl rw,relatime 0 0
none /dev/pts devpts rw 0 0
none /dev/shm tmpfs rw 0 0
/dev/sda3 /home reiserfs rw 0 0
/dev/sdb1 /media/media-server/1 reiserfs rw 0 0
none /proc/bus/usb usbfs rw,busgid=108,busmode=0775,devgid=108,devmode=0664 0 0
I attempted to add the other drives to /etc/mtab but they get overwritten upon a reboot. I've drived mounting the drives from konsole and dolphin.
All my drives used to work. At one point I had Chakra installed and had this issue after an update, however after thinking about it the problem may have actually started after the power flashed on and off here. I couldn't fix it so I installed Arch64 and KDE4 (the normal KDE from the Arch repos, not KDEMod) thinking maybe it was a Chakra specific issue. That fixed it at the time. It later happened on my Arch install. I reinstalled Arch again and the issue was gone. However the issue is back. Again I think it was after a power outage/flash but it was also after an update that included a kernel update. Best I can remember each time it's happened has been after a kernel update and power flash. So I can't say for sure which is the cause.
Oddly though if I boot from a live disc (in my case a Chakra Live DVD) I can mount and access all of the drives just fine.
Another oddity, is that in 'Disk Utility' (palimpsest) there is a 1.5TB RAID-5 array listed. The only thing I can figure is that that is what is making the individual drives busy.
Here's a screenshot from Disk Utility of the RAID-5 array:
http://theavataroftime.com/sites/defaul … enshot.png
After talking to a friend I remembered that quite a while back (over a year) we had messed around trying to setup a RAID array and dual boot WindowsXP. However, we never could get it working quite right, not even just in Linux without dual booting. I really can't say what all we did/tried, it's been too long. I realize that's not much help but...
Anyway I'm pretty certain I deleted everything RAID related at the time and turned it off. However I must be mistaken or I guess the array wouldn't be showing up.
I apologize, I really know nothing about RAID or RAID controllers. I do have an onboard RAID controller, but it's not a full fledged hardware RAID controller. It's onboard, but doesn't have it's on proccessor like good hardware RAID would. Or that's the way I understand it. Perhaps 'hybrid' is the proper term?
I checked in BIOS and my onboard RAID controller is off.
I take it that my attempts at setting up a RAID array before are still in the MBR (on that note I use GRUB and have never used LILO)? That's the only place I can think of that any leftover RAID configurations wouldn't have been wiped during reinstalling and reformatting the drives and partitions? I've reformatted my drives completely and changed the size of swap, /, and /home on several occasions since then, as well as formatting the media-server drives to ReiserFS (not sure what FS I was using when trying to setup RAID before. Perhaps FAT32 since I was trying to dual boot).
I clicked the stop array button in Disk utility, and then all the options except start array went away. Then I clicked start, and instead of my four media-server drives being listed at the side of Dolphin there was one 1.4TB drive. I rebooted and now it's back to the 4 500GB media-server drives.
I'm worried about losing a bunch of data, so I'm hesitant to start experimenting. How should I go about getting rid of the remnants of the RAID array safely?
Also here's a screenshot of MediaServer5 from Disk Utility. The other 500GB drives have the same info minus the names and labels of course:
http://theavataroftime.com/sites/defaul … enshot.png
*** I had forgotten about dmesg output. It's quite long so instead of copying it, here's a link to it:
http://theavataroftime.com/sites/defaul … /dmesg.txt
Thanks for advice on the matter.
Last edited by The Avatar of Time (2010-10-07 08:27:06)

Thanks for the reply.
Here is my output from the commands you suggested:
fuser -v -m /media/media-server/2
USER PID ACCESS COMMAND
/media/media-server/2:
root kernel mount /
theavataroftime 2518 fr.e. startkde
theavataroftime 2561 Frce. gpg-agent
theavataroftime 2575 .rce. dbus-launch
theavataroftime 2576 .rce. dbus-daemon
theavataroftime 2584 Fr.e. kdeinit4
theavataroftime 2585 Fr.e. klauncher
theavataroftime 2587 fr.e. kded4
theavataroftime 2592 .r.e. kglobalaccel
theavataroftime 2605 .r.e. kwrapper4
theavataroftime 2613 Fr.e. ksmserver
theavataroftime 2622 .r.e. kwin
theavataroftime 2656 fr.e. knotify4
theavataroftime 2658 fr.e. plasma-desktop
theavataroftime 2662 .rce. kuiserver
theavataroftime 2665 .r.e. akonadi_control
theavataroftime 2667 .r.e. akonadiserver
theavataroftime 2670 Fr.e. mysqld
theavataroftime 2714 .r.e. akonadi_contact
theavataroftime 2715 .r.e. akonadi_contact
theavataroftime 2716 .r.e. akonadi_ical_re
theavataroftime 2717 .r.e. akonadi_ical_re
theavataroftime 2718 .r.e. akonadi_maildir
theavataroftime 2719 .r.e. akonadi_maildis
theavataroftime 2720 .r.e. akonadi_nepomuk
theavataroftime 2721 .r.e. akonadi_vcard_r
theavataroftime 2739 .r.e. nepomukserver
theavataroftime 2741 .r.e. nepomukservices
theavataroftime 2747 .r.e. kaccess
theavataroftime 2759 fr.e. krunner
theavataroftime 2765 Fr.e. virtuoso-t
theavataroftime 2772 Fr.e. kio_http_cache_
theavataroftime 2774 .r.e. kmix
theavataroftime 2782 Fr.e. konsole
theavataroftime 2785 .r.e. kjots
theavataroftime 2790 .r.e. bash
theavataroftime 2807 .r.e. kalarm
theavataroftime 2809 fr.e. kopete
theavataroftime 2812 .r.e. polkit-kde-auth
theavataroftime 2815 .r.e. kwin
theavataroftime 2821 .r.e. dolphin
theavataroftime 2822 Fr.e. firefox
theavataroftime 2834 .r.e. kwalletd
theavataroftime 2839 .r.e. kwalletmanager
theavataroftime 2842 Frce. gconfd-2
theavataroftime 2850 .r.e. python
theavataroftime 2854 .rce. wicd-client
theavataroftime 2858 .r.e. klipper
theavataroftime 2861 .r.e. nepomukservices
theavataroftime 2862 .r.e. nepomukservices
theavataroftime 2865 .r.e. nepomukservices
theavataroftime 2867 .r.e. nepomukservices
theavataroftime 2868 .r.e. nepomukservices
theavataroftime 2869 .r.e. nepomukservices
theavataroftime 2870 .r.e. nepomukservices
theavataroftime 2871 .r.e. korgac
theavataroftime 2883 fr.e. kmozillahelper
theavataroftime 2979 .r.e. amarokapp
theavataroftime 2989 .r.e. plugin-containe
theavataroftime 3010 .r.e. npviewer.bin
theavataroftime 3048 Fr.e. kdeinit
theavataroftime 3051 Fr.e. dcopserver
theavataroftime 3053 Fr.e. klauncher
theavataroftime 3055 fr.e. kded
theavataroftime 3075 .r.e. ruby
theavataroftime 3081 fr.e. kio_file
theavataroftime 15311 .r.e. kio_http
theavataroftime 15312 .r.e. kio_http
theavataroftime 15313 .r.e. kio_http
theavataroftime 15314 .r.e. kio_http
theavataroftime 15315 .r.e. kio_http
theavataroftime 15316 .r.e. kio_http
fuser -v -m /dev/sdb1
USER PID ACCESS COMMAND
/dev/sdb1: root kernel mount /media/media-server/1
I ran 'fsck.reiserfs --check' one /dev/sdf1, which is the /media/media-server/5 hard drive.
Here are the results:
fsck.reiserfs --check /dev/sdf1
reiserfsck 3.6.21 (2009 www.namesys.com)
** If you are using the latest reiserfsprogs and it fails **
** please email bug reports to [email protected], **
** providing as much information as possible -- your **
** hardware, kernel, patches, settings, all reiserfsck **
** messages (including version), the reiserfsck logfile, **
** check the syslog file for any related information. **
** If you would like advice on using this program, support **
** is available for $25 at www.namesys.com/support.html. **
Will read-only check consistency of the filesystem on /dev/sdf1
Will put log info to 'stdout'
Do you want to run this program?[N/Yes] (note need to type Yes if you do):Yes
reiserfsck --check started at Mon Sep 27 19:21:20 2010
Replaying journal: Done.
Reiserfs journal '/dev/sdf1' in blocks [18..8211]: 0 transactions replayed
Checking internal tree.. finished
Comparing bitmaps..finished
Checking Semantic tree:
finished
No corruptions found
There are on the filesystem:
Leaves 77863
Internal nodes 474
Directories 2856
Other files 18718
Data block pointers 77184421 (0 of them are zero)
Safe links 0
reiserfsck finished at Mon Sep 27 19:29:03 2010
Also I just used Partition Manager to check /media/media-server/5 as well.
Check and repair partition '/dev/sdf1' (465.76 GiB, reiser)
Job: Check file system on partition '/dev/sdf1'
Command: fsck.reiserfs --fix-fixable -q -y /dev/sdf1
reiserfsck 3.6.21 (2009 www.namesys.com)
** If you are using the latest reiserfsprogs and it fails **
** please email bug reports to [email protected], **
** providing as much information as possible -- your **
** hardware, kernel, patches, settings, all reiserfsck **
** messages (including version), the reiserfsck logfile, **
** check the syslog file for any related information. **
** If you would like advice on using this program, support **
** is available for $25 at www.namesys.com/support.html. **
Will check consistency of the filesystem on /dev/sdf1
and will fix what can be fixed without --rebuild-tree
Will put log info to 'stdout'
reiserfsck --fix-fixable started at Wed Oct 6 22:29:02 2010
Replaying journal: Replaying journal: Done.
Reiserfs journal '/dev/sdf1' in blocks [18..8211]: 0 transactions replayed
Checking internal tree..
***I'm cutting most of this out, it's insanely long: \|/-\|/-\|finished
Comparing bitmaps..Bad nodes were found, Semantic pass skipped
3 found corruptions can be fixed only when running with --rebuild-tree
reiserfsck finished at Wed Oct 6 22:36:43 2010
block 32772: The level of the node (48287) is not correct, (1) expected
the problem in the internal node occured (32772), whole subtree is skipped
block 262149: The level of the node (28423) is not correct, (1) expected
the problem in the internal node occured (262149), whole subtree is skipped
block 11326: The level of the node (63701) is not correct, (1) expected
the problem in the internal node occured (11326), whole subtree is skipped
vpf-10630: The on-disk and the correct bitmaps differs. Will be fixed later.
Check file system on partition '/dev/sdf1': Error
Check and repair partition '/dev/sdf1' (465.76 GiB, reiser): Error
Thanks for the advice.
Last edited by The Avatar of Time (2010-10-07 05:53:05)

Internal hard drive won't mount

First off, thanks in advance to any who offer help with my frustrating problem.
It would appear that my primary drive has come unmounted and will not remount. Yesterday I went to upgrade Corel Painter. The computer hung up when I launched the installer so I walked away from it for a few hours. Upon returning I found a screen telling me I had to restart. After the first restart I was looking at a Darwin command prompt (I don't know Unix, so this didn't help!). I restarted again and got the grey apple screen and a blue screen for a long time. I finally booted up from the OS X disc.
After unintentionally installing Tiger on my secondary internal drive I ran Disk Utility. My primary drive shows up in the left hand window, but greyed out. When I verify or repair the disk it tells me it passed verification and does not need to be repaired. When I try to mount the disk, it says "the disk cannot be mounted"
Looking at the additional info gives me this:
Name : Hard Drive
Type : Volume
Disk Identifier : disk0s2
Mount Point : Not mounted
File System : Mac OS Extended (Journaled)
Connection Bus : ATA
Partition Type : Apple_HFS
Device Tree : mac-io/ata-4@1f000/@0:2
Writable : Yes
Universal Unique Identifier : 0D681EDE-DA84-3486-AC05-16F7794AC9BA
Capacity : 28.0 GB (30,020,235,264 Bytes)
Owners Enabled : No
Can Turn Owners Off : Yes
Can Be Formatted : Yes
Bootable : Yes
Supports Journaling : Yes
Journaled : No
S.M.A.R.T. Status : Verified
Disk Number : 0
Partition Number : 2
I just don't understand what happened. This is the first trouble I've had since using OS X so I am lost in how to troubleshoot it. Any input would be great. I am a dummy and haven't backed up my drive in over 6 months so I am quite sad over this.
Erin
G4 450 Dual Mac OS X (10.4.7)

Have you tried mounting the partition from the command line? Even if it doesn't work, the command line sometimes gives more informative error messages. As a variation, the hint below describes how mounting a drive as "read-only" may sometimes succeed where a regular "read & write" mount might fail. If successful, it should be possible to pull files off for backup.
http://www.macosxhints.com/article.php?story=20041127045644235
In another approach, if you have an external drive that is big enough to hold the entire unmountable partition (or if your secondary partition has the free space), it might be possible to use "Disk Utility.app" to create a disk image of the whole partition - try selecting the icon for the unmounted partition in the left panel, then click the "New Image" button in the toolbar. After going through various prompts, it should create a disk image called disk0s2.dmg. I have read that it is sometimes possible to mount a disk image of an unmountable disk created using this process (unfortunately, I haven't been able to find a link).

External Firewire hard drive won't mount after 10.4.10 update

I see many posts about USB drives not mounting after 10.4.10 update. Just lending my voice to that issue (my USB drive won't work either) as well as the 10.4.10 update breaking Firewire drives.
Hope a fix is coming. No backups are scaaaary.

How to fix the problem of a missing external Hard Drive (Firewire) after it vanishes from you desktop after installing 10.4.10 update.
I have a iMac PPC (Non intel). Aparently my system upated installed the wrong version of 10.4.10 and thus my external firewire hard drives a 320 GB Westerndigital My Book, and Acomdata 80 GB, and aWestern Digital 160 GB media center all vanished from the desktop.
The instructions below should be credited to several different people. I found various version of these steps in the Discussion. I combines a few of them into this one 10 step fix and it worked for me. I hope it works for you.
1) Shut down you computer
2) Unplug all peripherals (i.e USB and Firewire, I left computer power plug in as well as ethernet and Keyboard+ Mouse) and leave along for 30 Minutes
3) Restart holding down the Command (Apple) + Option + P + R keys for three startup bongs, then release the keys and your computer will start up as usual.
4) Verify and repair disk Permission using Disk Utility. (Several things were repaired here)
5) Instal 10.4.10 Combo PPC
6) Restart Again
7) Again repair Disk permissions (None of mine needed to be repaired fyi this time)
8) Unplug Power cable and Firewire cable from External Hard Drive (leave along for 1 minute)
9) Reconnect power to Firewire External Drive first then the Firewire cable to the drive second, then the firewire cable from the Drive to the computer last.
10) Turn on your Firewire Drive... you will head it spin up and eventually show up on your desktop just like it did before the 10.4.10 update.

External hard drives won't mount after upgrading to Tiger 10.4.9. Help!

Hi, I've just got the latest iMac. Very excited! I did all the software updates, connected my Western Digital extended hard drive so that I could copy some files over onto my new Mac. It was fine at first. Then when I wanted to open up the external hard drive icon on my desktop again and double clicked on it, everything disappeared from the screen for a few seconds, then reappeared but my external hard drive simply opened the window to my personal hard drive on the Mac. The WD links to my computer via Firewire. I then connected my USB external hard drive stick and it was the same story.
I used Disk Utility to test everything and everything was fine.
I then reinstalled Mac OSX 10.4.8 and plugged in my external hard drives. Everything worked perfectly. After copying over documents and a couple of programs, and downloading a few more programs, I ran my software updates again, upgrading the operating system to Tiger 10.4.9. I attached my external hard drive and it was the same problem all over again.
I the read up the online discussions and also chatted to an Apple dealer, and their advice was to download the Intel Combo and reinstall the operating system. I have just done this and my external hard drives will still not mount properly. Their icons appear on screen but double click them and everything disappears.
Please help. This is really frustrating as I have a backlog of work to do and I seem to be wasting hours on this. Not only that, this is a brand new machine which I rightly expect to work straight away.
I look forward to your response. Thank you in advance.

Hi, try to put your HDD in other Mac and look if appear the same, also you can try to repair permission.

My other hard drives won't mount after installation of 10.4.7

i have 3 hard drives in my G4 Quicksilver. when i installed 10.4 on one of them, the other two hd's appear in disk utility but gave invalid b-tree node errors & won't mount?? disk utility reports
"Invalid B-tree node size
Volume check failed.
Error: The underlying task reported failure on exit"
all my important info is on these two hard drives so i can't just clear them and start over. any help would be greatly appreciated.

Welcome to Apple Discussions!
Usually this is indicative of a damaged directory. However, sometimes it is indicative of a dying hard drive,
or damaged peripheral interface.
Since you say all of your critical data is on the drives, I'd purchase Prosoft Data Rescue and another empty Mac formatted drive you can recover the data to and see if that is successful.
If that is not, follow my directory repair FAQ:
http://www.macmaps.com/directoryfaq.html
In the future always make sure you have at least two copies of your data at all times as my backup FAQ explains:
http://www.macmaps.com/backup.html

My Toshiba external hard drive won't mount after OSX Mavericks update. Please help.

Two days ago I updated to Mavericks 10.9.3 and prior to this, my Toshiba 1TB external hard drive worked perfectly well. Since the update, my hard drive will no longer mount. It shows up in Disk Utility but will not let me 'mount', 'verify disk' or 'repair disk' through Disk Utility. My sister has an identical Macbook Pro which she has not updated to Mavericks. I have tested my hard drive on her laptop and it works just fine. Can anyone tell me how to fix this? Do I need to reformat my hard drive (and if so, will that clear everything on my hard drive?) or is there a simple fix?
Thank you for any assistance you can offer!

Reset the NVRAM/PRAM and Reset the SMC, then try again.

Firewire external hard drives won't mount after using Windows Vista

Hi to All,
I installed Windows Vista Business in a SATA hard drive I added to my Mac Pro. Every time I select the HD from the start up disk in my preferences and restart, the next time I start up with Mac OS 10.6.1 all my firewire devices don't mount. I have to shut down my Mac unplug the power cord for a few minutes to get my firewire devices back. Do you know of any workarounds to this issue? Thanks in advance!

Yea, don't use Snow Leopard or don't use Firewire for now.
Nothing to do with Vista Business.

My hard drive won't mount on 2012 mac book pro with retina display

The flash drive in my Sept 2012 mac book pro with retina display is not mounted, won't mount, and can't be repaired in disk repair. I need files created right before it failed last night that were not backed up. Can they be salvaged before a new warrantied drive is put in at my request? Also is this failure a common problem?

I believe you hsave to first launch Setup Assistant:
http://manuals.lacie.com/en/manuals/porsche-9233/connection

Internal hard drive won't mount after running Tech Tools Pro 5

Similar Messages

Maybe you are looking for