Although most of this information is self-explanatory, of interest is the S. Self-Monitoring Analysis and Reporting Technology status. A disk that supports S. Figure 3. To get more information about a disk or partition, select it in the list and then click the Info icon in the Disk Utility toolbar. Choose the disk or partition that you want to work with and then click the tab to move to the appropriate pane. We'll start with the First Aid. The button bar changes depending on the object you've selected. If you choose a disk, for example, you see all the control areas.
The First Aid pane, shown in Figure 3. In addition to basic disk repair, the First Aid tools can also fix any file permissions that may accidentally have been changed while using your computer. To check or verify a disk, select the disk and partition from the volume list at the left of the window. Next, click the appropriate action button:.
You can only repair volumes other than your boot disk. If you're having trouble installing applications or deleting files, you may have a permissions problem. Permissions can only be repaired on your current boot disk. As files become fragmented, the locations of the fragments are stored here. If errors cannot be repaired, Disk Utility warns you that it is incapable of fixing your system. If the repair does not work, Apple's suggested course of action is to back up the drive, erase it, and then restore your files. I'd recommend trying another disk repair tool before resorting to such desperate measures.
You can batch-repair multiple volumes by selecting several disks from the volume list.
Hard Disk Erasing for Macs
Volumes are repaired from the command line by using the fsck tool in single-user mode, as discussed in Chapter 32, "System Maintenance. Apple also offers a command-line utility for mounting, unmounting, ejecting, and renaming disks: disktool. The next pane, Erase, does exactly what you would think it should: It erases drives and partitions. This is essentially a quick-and-dirty partitioning and initialization tool; it creates a single empty partition on the selected device and erases anything that was previously there.
Enabling Journaling does add a minor speed hit to the drive but helps protect your machine from data corruption if the system crashes or is otherwise interrupted. If you want to securely erase the volume, click the Options button to force Disk Utility to zero all data on the drive and write random data over the drive eight times. Finally, click Erase to remove all existing information from the device and install the selected filesystem.
To create a more complex drive layout, use the Partition pane. Shown in Figure 3. The Volume Scheme section of the Partition pane contains a visual representation of the partitions on the system. Each box is a partition. The highlighted box is the active partition. You can change a partition's size by dragging the dividers between the partitions up and down to shrink or grow the available space. As you drag the bar, the size field on the right portion of the pane changes to show the current settings. In addition to working with the visual view of the partition, you can use the various pop-up menus, fields, and buttons to set other parameters:.
Do a factory reset to MAC OS X Mavericks - CodeProject
You can continue to work with other partitions but not one that is locked. We've also personally lost FireWire drives since installing Panther see below. Taken as a whole, it would seem to be a stunning coincidence if all of these reports were completely unrelated. Whichever may be the case, because of these suspicions, we continue to recommend caution when using FireWire drives with Panther, regardless of the connection speed vs. Is the drive permanently damaged? Although the drives affected by this bug are "unrecognizable" afterwards, the problem is not with the actual drive's hardware; rather, it is with the drive's directory.
After reformatting the drive, it should work fine. See below about recovering data before reformatting. What is technically happening to the drive? Right now, no one is saying. So much so that drive utilities are generally unable to repair it. We continue to investigate this issue, and hope to have more information soon.
Is my data recoverable? Although readers have reported varying degrees of success in recovering data from affected drives, some have been completely out of luck. Those that have been successful have used techniques such as connecting the drives to Macs running Jaguar or OS 9, or installing drives internally instead of connecting them via FireWire. Others report some success with Prosoft's Data Rescue X; on our own drive that was lost see below , we were able to use Prosoft's Data Rescue X to recover some files, but not all.
Some users even report that after being unable to recover data on the damaged drive using Data Rescue X, they used Disk Utility to erase the drive -- NOT using any special options, such as zeroing data -- after which Data Rescue X was successful at retrieving at least some data.
Video of the Day
Since "erasing" a drive in Disk Utility doesn't really erase it, but instead just deletes the drive directory and creates a new one, the data should be mostly untouched. However , we recommend against this procedure except as a last resort. We asked John Christopher, a Data Recovery Engineer at DriveSavers -- the company has worked with a few drives damaged by this problem -- about the possibility of data recovery using commercial utilities.
His reply:. However the dangerous part comes when these tools are used incorrectly. Any disk utility that can perform a fix-it routine may damage whatever directory remnants are on the drive and could complicate further recovery attempts. The safest path to take is to attempt to recover the data to a secondary hard drive. This is of course the big question. We've heard from both sides -- Apple and drive manufacturers -- and many readers have chimed in with their own opinions, as well.
Apple claims that the problem is due to the firmware on affected drives -- Apple invented FireWire, so they should know the official specifications, right? So perhaps Panther requires "more compliant" FireWire devices. This isn't an unreasonable idea, as we've seen a similar issue crop up with Panther and RAM. At the same time, some drive manufacturers claim that the issue is clearly with Panther. After all, Apple has proven that they can provide an operating system that works fine with all of these drives -- they did it with earlier versions of Mac OS X, and even with many of the Panther betas.
Shouldn't Apple simply "fix" Panther so that it works with all drives? The truth may be that both sides are partly at fault, but until we get more facts, we aren't going to "blame" either side. What matters is that a significant number of users have been adversely affected, and who is to blame is clearly less important to these users than who is going to help them. For those users who have drives made by vendors who have provided firmware fixes, this discussion is somewhat academic? However, what about users who have drives from other manufacturers?
What about users who "built" their own FireWire drives using a bare drive and a third-party FireWire enclosure? Apple may or may not be correct in asserting that the problem is with the drives and not with OS X -- we don't really know -- but it doesn't seem realistic to expect every hard drive vendor, and the makers of generic enclosures, to provide firmware updates for those drives and enclosures, meaning that a lot of users are going to be left wondering if it's ever safe to use their FireWire drives again. For these reasons, we continue to hope that Apple provides an update to Panther that "fixes" this problem, regardless of who is actually at fault.
If it turns out the problem really was with the drives, and not with Panther, then Apple looks even better for taking care of their users. Such issues appear to be unrelated to the current Panther problem, but they do make us wonder if FireWire support in OS X isn't quite as mature as we had always assumed.
The drive was connected to the G5's FireWire port. Panther's Disk Utility could not repair the drive. We connected the drive to a Mac running OS X We even removed the drive from its FireWire case and installed it internally in a Mac running Jaguar and OS 9; neither OS could access the drive's contents. We connected the drive to the G5, and it mounted and functioned properly. We ran Disk Utility and Disk Warrior on it, and it appeared to be healthy. Finally, we used Panther's Disk Utility to erase the drive to make sure we could rule out drive problems if something happened.
After erasing, the drive again worked fine, as we were able to unmount it, disconnect it, reconnect and mount it, and copy and delete data from it. We then restarted the G5 with the drive connected. After the restart, the drive no longer functioned; OS X gave the same "unrecognizable" error, with the options to Initialize, Ignore, or Eject, as the previous "lost" drive.
Perhaps this isn't the same exact issue as the one Apple has publicly acknowledged; however, even if that's the case, this clearly wasn't "expected" behavior. MacFixIt reader Jochen writes:. Under Mac OS 9. Under Mac OS X Since the ATA-6 functionality requires new drivers, it stands to reason that with installation of Panther, some part of the specific FireWire driver - or some link to the firmware - was affected.
Some readers have reported that they are once again able to address more than GB of disk size by installing the recently released firmware updates from LaCie and WiebeTech. Speed boost from LaCie firmware update The firmware update from LaCie may do more than prevent problems with drive corruption and data loss. We are beginning to receive reports that the update improves performance even on systems that weren't affected by any problems during the Panther update.
MacFixIt reader Dominic Dunlop writes:. Anyway, after some mucking about resolving an extensions conflict with the LaCie-supplied version of SilverLining I never did work out what the culprit was -- ah, the joys of Mac OS Classic , the upgrade went through exactly as described in the Readme document, and everything is still fine.
Although currently only Mac OS X It's actually possible to enable Case-sensitive HFS in Panther client via Terminal, but it requires you to completely erase your drive, which is a more effective deterrent than existed for journaling. For those tempted to do so, we suggest that you avoid that temptation, at least until Apple and third-party vendors officially support it. Read on for the reasons why. In other words, they do not recognize differences in case when it comes to filenames and filepaths.
However, many Unix file systems, such as UFS, are case-sensitive. To these file systems, these two files -- Text. TXT -- have different names, and can co-exist in the same directory. Under a case-sensitive file system, the only way files are considered to have the same name is if every single character in the names match, including the case. However, implementing a case-sensitive file system in OS X has some significant hurdles, the most compelling being that many current Mac OS applications that work with files will need to be updated to provide case-sensitivity themselves.
This especially the case for backup and disk repair utilities. For example, using the two example files above, most backup applications will assume that they are the same file, and only back one up. Dantz has already posted a warning to this effect in a Retrospect support document, stating, "Retrospect 5. If 'file' and 'FILE' exist in the same directory, only one will be backed up. In other words, Case-sensitive HFS is not yet for the masses. We're sure there will be a curious type or forty who will be determined to figure out how to enable it on the standard OS X client.
If such a procedure becomes available, we urge you to remember the old saying: just because you can doesn't mean you should. Problems with installation: Stuck on Disc 2; bad discs; disconnecting devices. It appears that some Mac OS X Quitting installation after the first CD will leave out some components like extra language support.
Greg Davidson writes:. The installation failed somewhere during the language packs on Install CD 2 didn't see exactly where since I was trying to get my daughter ready for bed. I acknowledged the error and it dropped out of the installer. I rebooted manually and it booted fine into Mac OS X I've tested the programs and rebooted several times without problem. I assume that the failed installation only resulted in my PowerBook not having some foreign language files, which I can live without. Other readers have reported that installation fails during the transition from disc 1 and disc 2.
Les Dodson writes "During the installation of Panther, it will proceed normally through the installation of Disk One, and reboot. After you get through to the continuation screen, one of two things has happened: The install quits unexpectedly or; The installer keep requesting Disc 2, when it's already present in the drive. As a workaround for this problem, you can force the installer to quit when it keeps requesting disc 2 , bringing you to the Finder where you can mount and install the second disc data manually. In many cases, all or most of these devices can be re-introduced after Mac OS X In addition to disconnecting external devices and removing non-native RAM, some readers have reported success eliminating problems by turning off any applications that are triggered at startup, including some menu and interface enhancements.
This results in alerts advising that the hard disk is full? This is a crazy situation with what is supposed to be an advanced operating system requiring regular restarts. In our experience, Panther itself requires more memory than Jaguar did, and MB of RAM is simply not enough for good performance, despite Apple's "minimum system requirements" of MB. If you have less than MB of RAM, you'll probably see significantly more virtual memory swap files -- and therefore less free drive space -- than you would have seen under Jaguar.
In fact, it wasn't until we upgraded our own computers to MB or more that we saw noticeable performance improvements. To be fair, we work with a large number of applications, some of them RAM-hungry, open at the same time. On the Couldn't retrieve the folder from the trash. A reboot resulting in a screen full of kernel panic warnings and other text, ending with 'panic: we are hanging here. However, most users would not know how to do this. If so, one could argue that Apple went too far in trying to make OS X "more convenient" when it comes to deleting files.
But we didn't consider that a good thing, either. Panther problems? Drop us an email at Late-breakers macfixit. Data loss? I've found that repairing permissions after the install and rebooting again is the best option after the install. Wonderful, Slipy works great! I made a master DVD with the Seemed to boot fine in my old G4 Tower but I didn't go further with it.
It did cheese up in G4 iBook but I've had that happen in the past with burned Panthers and sometimes a different disc will work. Thanks for the shortcut! What about the reverse? Off topic question. I'm a mac newbie. Can I use a regular hard drive? Any size limitations? Lost your password? Powered by the Parse. It worked!! Read the rest of the hint for the how-to Let's name it "Panther. Don't mount the image file yet. Now head to the Terminal. Now, the partition inside the image hasn't been resized yet. For that, type: hdiutil resize -size 1. How much smaller should it be compared to the image file?
I don't know, but hdiutil will give you an error if you try to grow the partition beyond the space available in the image file. Mount Panther. Now you have a disk with 1. The Finder will give you a warning about items with the same name: select Replace. It seems Disc 1 has placeholders for all the installable packages. Repeat step 4 with disc 3. Unmount the disc and burn to a DVD. I did this and was able to install Panther from the DVD. Now, you can grow the image file and partition beyond two gigs to fill the entire DVD and copy additional installers.
I guess this hint will really be helpful to people maintaining a lab full of Macs. The following comments are owned by whoever posted them. This site is not responsible for what they say. Modify the list of packages on the DVD? Authored by: davidro on Dec 27, '03 PM. Authored by: zgafford on Dec 27, '03 PM. Authored by: timkingman on Dec 29, '03 PM. To complete some things the above poster didn't explicitly state, be sure to update OSInstallCache. Authored by: knowmad on Dec 31, '03 PM. Authored by: 1equals0 on Jan 02, '04 PM.
- Mac OS X - Troubleshooting Startup Problems.
- could not open a connection to your authentication agent. mac!
- Do a factory reset to MAC OS X 10.9 Mavericks;
- halo trial mac free download;
- midiman midisport 1x1 driver mac.
- fleetwood mac beautiful child midi.
Authored by: macpoupou on Jan 03, '04 AM. Authored by: Sophic on Feb 27, '04 AM. Doesn't work for me Authored by: jubelc on Dec 28, '03 AM. Operation not permitted 1 [ Reply to This ]. Authored by: Bev on Dec 28, '03 AM. Lowering the case of -partitionOnly worked for me Are you logged in as root? Authored by: archiboy on Dec 28, '03 PM. Link [ Reply to This ]. Can this be modified to include updated version of Thanks [ Reply to This ]. I am guessing it's because I have upgrade disks [ Reply to This ]. Won't Startup! Authored by: dihakz on Dec 29, '03 PM.
Darren [ Reply to This ]. Authored by: archiboy on Dec 30, '03 AM. Authored by: shemp on Dec 30, '03 AM.
There is an easier way to do this. Panther's Disk Util has the neat, ever-useful "Restore" function. Its just awesome. Make sure it is writable. For those resizing images Then it only takes as much space as necessary. Carbon Copy Cloner is pretty much free, although I recommend donating since it's so useful and reliable If a man says something in the forest and no woman is around to hear him, is he still wrong?
Thanks, Brian [ Reply to This ]. Can anyone Give step by step instructions on adding packages to the install, It seems very confusing when i read other posts Thanks Beto [ Reply to This ]. On: hack These instructions assume you are currently using We don't need Disc 2. That has the extra bundled software which we're not concerned with anyway. Name it whatever you want. I chose test. Click save, grab some coffee and wait until it finishes.
Once we have our image, go ahead and mount it. The more astute of you have noticed at this point that there doesn't seem to be any folder containing the install packages like previous OS X install Discs. That crafty Apple hid them on you. The "go" menu is your friend.
In the finder click the go menu and select "go to folder". Feel free to copy and paste. Open this file in your favorite text editor. I recommend BBedit. Delete it and save the file. Unmount the image by hitting the eject symbol next to it in the sidebar or by dragging to the trash. Launch Disk Utility. Your image should still be in it's sidebar. Click on the image and then click on the burn symbol.
You obviously need a DVD burner for this. I followed step by step the explanation, but the DVD burned is not valid. Txs [ Reply to This ]. Authored by: jiclark on Nov 25, '04 AM. Good luck, John-o [ Reply to This ]. Search Advanced. From our Sponsor