Disk I/O thoughts?

I recently specced a server that would host an essentially read-only database used for web searches (so query response time is critical, and there's no transactional activity at all). The entire contents of this database are re-creatable in about 2 hours, via a bit of Oracle Text re-indexing and running a table population procedure that pulls data over a database link (and the linked database is properly archived and backed up etc), so it will be running in noarchivelog mode. However, because an outage would still be a bit inconvenient, it will run on mirrored disks. Currently, the tables and indexes in question use a 12GB cache, but I can tell we need a bit more than this -and an extra 1GB or so per month on top of that, because of data growth rates.
So, I specced a 24GB RAM server, expandable over time to 96GB. Lots of growth there. But because Oracle Text always seems to hit disk a little bit no matter how much RAM is available, I decided to spec 2 solid state hard drives in a mirrored configuration. Each disk is 120GB (sufficient for a long time to come) and has a 260MB/sec read and write speed, individually. The mirrored pair should therefore be able to achieve 260MB/sec, at least.
Unfortunately, the supplier now states that no 2.5" SSDDs will work reliably in the server (something to do with the interfaces not fitting properly). He's proposing instead that we fit the server with 4 Western Digital 10000rpm velociraptor disks, in a RAID 1+0 configuration. Each disk, individually, has a quoted throughput of 120MB/sec, so a two-disk strip 0 should (I suppose) achieve 240MB/sec, not far short of the single SSDD's throughput. The other two disks are there to mirror them, of course. (I know the difference between RAID1+0 and RAID0+1... that's not what I'm asking about here).
Which configuration would you go for? A RAID1 of a 260MB/sec SSDD? Or a RAID0 (essentially, although with a mirror backup) of two 120MB/sec traditional HDDs, assuming the hardware costs were broadly comparable in each case. (Actually, since response time is absolutely critical, I have been told that hardware costs are not a limiting factor in this purchase, so that really doesn't come into it at all).
Obviously, if the supplier says the SSDDs don't work properly, though, I don't exactly have a choice here. But I don't want to agree to get the velociraptors if they're going to be very much also-rans in the performance stakes. I'd appreciate any thoughts on which of the two storage solutions seems more attractive to you, which would provide fastest response times to web-site searches, and so on. I cannot vary the two specs by much, though: it's really only one or the other, with minor tweaking to the config possible if it seems desirable.
If it makes any difference, we'd be using OEL5.4, Oracle 11gR2, 64-bit.
I realise it's an open-ended question. Any thoughts appreciated, however.

No, it's a burst of read I/O that always happens whenever a CONTAINS query is submitted. It's ineradicable, too -doesn't depend on the amount of buffer cache in the slightest. Hence, I want lots of RAM to deal with the major part of handling those queries ASAP. But I want the fastest possible, though cheap and basic, physical disk platform so that the little bit of residual I/O is not a major problem.
I do understand that maximising I/O is not just about the technology used, but that's all this question is related to. I have a purchase decision to make: 2 SSDDs or 4 fast HDDs. That's the only degree of freedom in question right now. (In other words, buying 8 HDDs or 4 SSDDs is not an option: disk numbers are fixed in either case, Neither is 'using a faster I/O bus': this is a commodity (cheap!) server, and that's not something that is changeable at this time. Money is about the same either way, so that's not the constraint here... it is simply a question of whether the performance of the one would be comparable to the performance of the other, theoretically.
And yes, I understand (and did say, in fact) that if the vendor is ruling out the SSDD option for interface issues, then I don't have a lot of choice (well, I have the choice of cancelling the order, I suppose!). The question really is at that point, however, is a server with 4 HDDs (2 in a stripe) going to do disk I/O comparably to what I would have got (theoretically) with the 2 SSDDs (one mirrored)? If so, it's a viable alternative. If performance is going to be orders of magnitude worse until I get up to 8 or 16 or more spindles, however, then cancelling the order looks an attractive alternative.
I always seem to upset people here when I ask them to focus on the specific question I've asked, rather than to open it up to all sorts of other issues (such as faster bus I/O, disk partitions, and so on). I really don't intend to do so, and I hope I'm not doing so on this occasion with you, either. I suppose what I'm asking, putting it bluntly, is: will 4 HDDs in a RAID1+0 give me about the same sort of I/O throughput as 2 SSDDs in a RAID1 configuration, ideally and theoretically speaking? That's really the only thing I'm asking about. If it will, theoretically, then I'll buy the 4 HDDs. If not, I won't: it comes down to that for me, basically.
I do appreciate you taking the time to answer, though!

Similar Messages

  • HT1198 I shared disk space and my iPhoto library as described in this article. When creating the disk image, I thought I had set aside enough space to allow for growth (50G). I'm running out of space. What's the best way to increase the disk image size?

    I shared disk space and my iPhoto library as described in this article. When creating the disk image, I thought I had set aside enough space to allow for growth (50G). I'm running out of space. What's the best way to increase the disk image size?

    Done. Thank you, Allan.
    The sparse image article you sent a link to needs a little updating (or there's some variability in prompts (no password was required) with my OS and/or Disk Utility version), but it worked.
    Phew! It would have been much more time consuming to use Time Machine to recover all my photos after repartitioning the drive. 

  • I'm running Lion on a Late 2008 MacBook Air.  With no other applications running, I can no longer Check for Software Updates.  It gets abut half way through the checking process and then freezes.  The MBA passes Disk Utility. Thoughts?

    I'm running Lion on a Late 2008 MacBook Air. 
    With no other applications running, I can no longer Check for Software Updates.  It gets about half way through the checking process and then freezes. 
    The MBA passes Disk Utility. Thoughts?
    Thanks
    Jim Taylor

    How long do you leave it?
    Mine can sometimes sit for quite a while (maybe 10 minutes??) before it finally finishes.
    You could look at the relevant logs via Console (Utilities folder) to see if Software Update is complaining about anything.
    charlie

  • Unable to open windows using boot camp.  Get message "The bless tool was unable to set the current boot disk."  Any thoughts, Thank you.

    Unable to open windows using boot camp.  Get message "The bless tool was unable to set the current boot disk."   I am using an Imac , Lion operating system, and Windows 7.  It worked a few days ago.  Any thoughts, Thank you.

    Note that nowhere in the Boot Camp instructions does it tell you to use Disk Utility to format the Windows partition. The Boot Camp Assistant program creates the partition & sets the +partition scheme info+ of the disk as appropriate for the Windows installer but the Windows installer itself is responsible for formatting the new partition with the appropriate +file system scheme+ (NTFS for Windows 7).
    If you follow the instructions in the Boot Camp Installation & Setup Guide to the letter you should have no problems installing Windows.

  • Can I Use Time Machine To Back Up a FAT32 Disk Containing Image Files?

    New iMac User Here.  I just bought a brand new but mid-2010 27" i7 iMac.  Although I've used recent MacBooks when traveling I've got no experience with Time Machine or other similar third party back up software.
    I moved to the iMac from a desktop PC running Windows XP Pro SP3.  I use the computer(s) mainly for photo image storage and processing.  My workflow is based upon Adobe Lightroom (now v3.4.1) and I plan to stick with it.  In the PC I had three internal hard drives, 2 of which were dedicated to image files.  They were formatted as Windows NTFS.  In preparation for the switch I formatted an external drive as FAT32 and copied all the image files to it.  Now with the iMac I have Lightroom installed on its internal hard drive but keep the image files on the external hard drive and access them as needed.  So far, so good.
    The problem arose when I tried to set up Time Machine to back up both the internal hard drive and the external external drive.  It will back up the former but not the latter.  It tells me it does not interact with FAT32 disks.
    Any thoughts, explanations and/or solutions for establishing a simple, single back up routine for both internal and external drives will be most appreciated.

    Thanks very much for the quick response.  You confirm my intial suspicion, but your suggestion relies on my memory to accomplish on a regular basis (not the best of solutions) and further would be an extended disk run every night because it would not just be backing up new additions but the whole large disk, right?

  • Images (w/correct meta data) are in catalog and on disk, but LR 5.7 considers them new on Import

    For reasons explained below, I want to try to re-import all my images into LR and hope that none/few are in fact considered new and are imported.  Yet, for some folders, LR is apparently unable to detect that my source images are already in the catalog, and are on disk, and that the source file meta data matches what LR knows about the images.  When I click an image in LR and Show in Finder, I do see the imported image on disk.  I can edit the image in the Develop module.  So, it seems good, but all is not well.   Sorry for the long post here, but I wanted to provide as much info as I could, as I am really seeking your help, which I'd very much appreciate.
    Here are some screen shots that illustrate the problem:
    Finder contents of the original images
    LR folder hierarchy
    an image as seen in LR
    Finder content of external LR copy of images
    import showing 10 "new" photos
    The original images ... (I'm not sure why the file date is April 2001 but the actual image date is January 2011; I may have just used the wrong date on the folder name?)
    The LR folder hierarchy ...
    An image as seen in LR ...
    The external folder containing the images in the LR library
    But on import of the original source folder, LR sees 10 "new" photos ...
    I tried "Synchronize Folder ..." on this particular folder, and it simply hangs half-way through as seen in the screen shot below.   IS THIS AN LR BUG?   This is really odd, since "Synchronize Folder ..." on the top-level folder completes quickly.
    I have a spreadsheet of of the EXIF data for the original files and those created by LR.  (I extracted this info using the excellent and free pyExifToolGui graphical frontend for the command line tool ExifTool by Phil Harvey.)   Almost all of the Exif data is the same, but LR has added some additional info to the files after import, including (of course) keywords.  However, I would not have expected the differences I found to enter into the duplicate detection scheme.  (I didn't see a way to attach the spreadsheet to this posting as it's not an "image".)
    I'm running LR 5.7 on a 27" iMac with Yosemite 10.10.2, having used LR since LR2.  I have all my original images (.JPEGs and RAWs of various flavors) on my internal drive on the Mac.   To me this is like saving all my memory cards and never re-using them.   Fortunately, these files are backed up several ways.   I import these images (copying RAWs as DNG) into LR with a renaming scheme that includes the import number, original file creation date and original file name.   There should be one LR folder for each original source file folder, with the identical folder name (usually a place and date).  I store the LR catalog and imported images on an external drive.  Amazingly and unfortunately my external drive failed as did it's twin, same make/size drive that I used as a backup with Carbon Copy Cloner.   I used Data Rescue 4 to recover to a new disk what I thought was almost all of the files on the external drive.
    So, I thought all would be well, but, when I tried "Synchronize Folder" using the top-level folder of my catalog, the dialog box appeared saying there were over 1000 "New" photos that had not been imported.  This made be suspicious that I had failed to recover everything.   But actually things are much worse than I thought..   I have these counts of images:
    80,0061 files in 217 folders for my original source files (some of these may be (temporary?) copies that I actually don't want to import into LR)
    51,780 files in 187 folders on my external drive containing the LR photo library
    49,254 images in the top-level folder in the LR catalog (why different from the external file count?)
    35,332 images found during import of the top-level folder containing original images
    22,560 images found as "new" by LR during import
    1,074 "new" images reported by Synchronize Folder ... on the top-level folder in the catalog; different from import count
    Clearly things are badly out of sync.   I'd like to be sure I have all my images in LR, but none duplicated.   Thus, I want to try to import the entire library and have LR tell me which photos are new.  I have over 200 folders in LR.  I am now proceeding to try importing each folder, one at a time, to try to reconcile the differences and import the truly missing images.  This will be painful.  And it may not be enough to fully resolve the above discrepancies.
    Does anyone have any ideas or suggestions?  I'd really appreciate your help!
    Ken

    Thanks for being on the case, dj!   As you'll see below, YOU WERE RIGHT!      But I am confused.
        1. Does the same problem exist if you try to import (not synchronize) from that folder? In other words, does import improperly think these are not duplic
    YES.  Import improperly thinks they are NOT duplicates, but they are in fact the same image (but apparently not the EXACT SAME bytes on disk!)
        2. According to the documentation, a photo is considered a duplicate "if it has the same, original filename; the same Exif capture date and time; and the same file size."
    This is my understanding too.
        3. Can you manually confirm that, for an example photo, that by examining the photo in Lightroom and the photo you are trying to synchronize/import, that these three items are identical?
    NO, I CAN'T!  The ORIGINAL file name (in the source folder) is the SAME as it was when I first imported that folder.  That name is used as part of the renaming process using a custom template. However, the file SIZES are different.    Here is the Finder Get Info for both files.  Initially, they appeared to be the same SIZE, 253KB, looking at the summary. But, if you look at the exact byte count, however, the file sizes are DIFFERENT: 252,632 for the original file and 2252,883 for the already-imported file:
    This difference alone is enough to indicate why LR does not consider the file a duplicate.
    Furthermore, there IS one small difference in the EXIF data regarding dates ... the DateTimeOriginal:
                                                                                                     CreateDate              DateTimeDigitized                    DateTimeOriginal              FileModifyDate                              ModifyDate
    ORIGINAL name: P5110178.JPG                                     2001:05:11 15:27:18    2001:05:11 15:27:18-07:00        2001:01:17 11:29:00        2011:01:17 11:29:00-07:00       2005:04:24 14:41:05  
    After LR rename:  KRJ_0002_010511_P5110178.JPG    2001:05:11 15:27:18    2001:05:11 15:27:18-07:00        2001:05:11 15:27:18        2011:01:17 11:29:02-07:00       2005:04:24 14:41:05
    So ... now I see TWO reasons why LR doesn't consider these duplicates.   Though the file NAME is the same (as original), the file sizes ARE slightly different.  The EXIF "DateTimeOriginal" is DIFFERENT.   Therefore, LR considers them NOT duplicates.
         4a. With regards to the screen captures of your images and operating system folder, I do not see that the filename is the same; I see the file names are different. Is that because you renamed the photos in Lightroom (either during import or afterwards)?
    I renamed the file on import using a custom template ...
            4b. Can you show a screen capture of this image that shows the original file name in the Lightroom metadata panel (it appears when the dropdown is set to EXIF and IPTC)?
    SO ....
    The METADATA shown by LR does NOT include the ORIGINAL file name (but I think I have seen it displayed for other files?).  The File SIZE in the LR metadata panel (246.96 KB) is different from what Finder reports (254 KB).  There are three "date" fields in the LR metadata, and five that I've extracted from the EXIF data.   I'm not sure which EXIF date corresponds to the "Data Time" shown in the LR metadata.
    I don't understand how these differences arose.   I did not touch the original file outside LR.   LR is the only program that touches the file it has copied to my external drive during import.  (though it was RECOVERED from a failed disk by Data Rescue 4),
    NOW ...
    I understand WHY LR considers the files different (but not how they came to be so).  The question now is WHAT DO I DO ABOUT IT?   Is there any tool I can use to adjust the original (or imported) file's SIZE and EXIF data to match the file LR has?  Any way to override or change how LR does duplicate detection?
    Thanks so very much, dj.   Any ideas on how to get LR to ignore these (minor) differences would be hugely helpful.

  • Recovering data from RAID 0 working disks on a laptop.

    As a former Windows user, I setup a two disks RAID 0 years ago where I put stuff I don't remember. Now I sold my old PC, the RAID controller card broke down, but I retained my working disks because I'd like to recover data stored in there.
    Is there any way you guys know to recover data files from those 2 disks? I thought of treating them as external drives (I've got a MBP, so this is the only one expansion option), make images of them, mounting them and then copy the data in my MBP.
    Thanks!

    I would say the Windows PC would be your best bet but the odds of recovering anything at all is still extreme poor even there.
    The way RAID 0 works is a bit like dealing cards. When you start a new hand in a card game the dealer deal a card to each player in turn. In the case of RAID 0 the computer is the dealer and the disks are the players.
    So what you are attempting to do is undeal the hand. Now while that may sound trival, it is in fact not. Hence on of the reason that everyone says RAID Arrays should always be backed up.
    Allan

  • Leopard Retail Disk No Longer Recognized By Laptop After Installation

    Today, I upgraded my MacBook Pro to Leopard OS X 10.5 using a retail disk. After successfully completing that installation, I kept the disk in the machine in order to try to move forward with a Boot Camp installation. However, the laptop stopped being able to recognize the disk at all. It whirrs three times, trying to read the disk, then it ejects the disk and won't mount. This occurs regardless of whether I am on the Mac side or the Windows side of my newly partitioned machine.
    The disk will, however, load on my other Mac (a G5 tower), which is still running 10.4.11, as an installation disk. But every time I try to load it on the laptop, it does its little whirring thing and then refuses to see the disk.
    Any thoughts on why the machine would be able to see it prior to the installation but not after? This is a particularly thorny issue for me because I am in the middle of a Boot Camp installation as well, and REALLY need to get ahold of those Boot Camp drivers for Windows so conveniently located solely on the Leopard disk (by the way, if those drivers are available to download somewhere -- I could burn a CD using my other machine -- I would muchly appreciate someone posting a link).
    Thank you!

    Hi, try booting in safe mode to see if the disk will install. If so, while your there repair your disk with firs aid, it will be in the menu when the languages show up. You can safely delete most languages knowing only a reinstall will get them back, printer drives as well, I only chose mine. It save much space. If I get a new printer I only have to install the drive.
    To start up into Safe Mode (to "Safe Boot"), do this:
    Be sure the computer is shut down.
    Press the power button.
    Immediately after you hear the startup tone, press and hold the Shift key.
    Tip: The Shift key should be held as soon as possible after the startup tone but not before.
    Release the Shift key when you see the gray Apple and progress indicator (looks like a spinning gear).
    Try this and post back with results. I can offer more potential solutions.
    Ray

  • Hard Disk - Mac OS Boot Volume failure

    Hello everyone,
    My Mac does not boot.
    I started having odd problems of clicking on a document and the mac refusing to open its application (tried with PDF, DOCX, even JPG).
    When I rebooted I was  greeted with a a normal grey screen with apple logo and immediately received a  terminal system message:
    The message read:
    panic(cpu 0 caller 0xffffff8010bcb7d4): "Process 1 exec of /sbin/launched failed, errno 8"@/SourceCache xnu xnu-2422.1.72/bsd/kern/kern_exec.c:3836
    Debugger called: <panic>
    Backtrace (CPU 0), Frame : Return Adrress
    etc. (please see above image)
    After quickly listing these messages it rebooted. Again same thing.
    Now this is odd since to my knowledge nothing particular happened that could justify this behaviour - regular apps being used, mac at the desk, no pwer failluers or surges... I even got a brand new disk I installed back in October last year.
    I rebooted with option pressed and got the three volumes I expected: Mac OS X, Bootcamp and HD Recovery
    Retried Mac OS X (you never know ;-) and nothing changed, same panic screen.
    I then rebooted on HD Recovery and run repair on Disk Utility. The S.M.A.R.T status is "Verified" and so I tried to Repair the volume. Can't remember exactly the message but basically something in the lines of "The disk cannot be repaired, backup your data and format it".
    The disk change prevented me of having a proper backup (last one done before changing disks - and as you probably will know when changing disks Timemachine does not recognize and proposes reset the backup it has from previous disk).
    So I thing I will get the disk out and connect it externally to another mac and backup and format it to later restore.
    But wait, how about Bootcamp? I rebooted, pressed option and chose Bootcamp as startup disk and... amazingly it works without a problem (besides seeing Windows 7 on a mac which is still a troublesome image to me  ;-) So not all is lost!
    So my question: any ideas if I may repair the disk from the apparently fully functional Windows? I started backing up the more recent and important files, but already had troubles with file long names and naming rules (so I will definitely have to backup it later on a Mac OS X environment as external disk).
    Any thoughts will be most welcome.
    Regards,
    -- João
    About my Mac:
    Macbook Pro
    15-inch, Mid 2010
    Processor: 2.66 GHz Intel Core i7
    Memory: 8 Gb 1067 MHz DDR3
    Graphic cards: Intel HD Graphics 288 Mb & nVIDIA GeForce GT 330 M
    Serial: W80282VYAGZ
    Software: OS X 10.9.2 (13C64) Mavericks

    You were right BobRz! :-)
    On second thought and still thinking that the drive could be a more likely culprit I decided to take the Mac back to the store where I had bought and installed it so I could profit from the warranty.
    They run a quick test (could not figure out which sequence keys but it was something built-in into the OS or Firmware) and they told me the disk was probably not at fault and that I should leave my Mac (chills!) for a more thorough testing.
    Although I already had saved all data files not covered by my existing TImemachine backup, I negotiated with them they would do the eventual full backup just in case testing pointed the finger to the disk and left it to - hopefully  - come back next day with everything sorted out.
    The following day they phoned me and when I presented myself at the counter I had my mac wating for me (I think I saw it smile - I certainly was) alongside with a faulty disk cable which has been replaced! So there you have it, you were 100% on target! :-)
    All in all I had a 100€ repair and cable to pay for.
    So all is well that ends well!
    Thank you very much for your insight Bob.
    Best regards,
    -- joão
    ps already bought a 1Tb and did a Timemachine full backup! ;-)

  • HT3275 The back up is too large for the back up disk

    I've been using an external hard drive (not a time capsule)  through time machine since April of last year.  It's been great backing up all of my info.  BUT all of the sudden a message appears saying:  Time Machine could not complete the back up:  This backup is too large for the backup disk.  I thought, when time machine ran out of room it was suppose to erase the oldest backup to replace it with the current one, but that appears not to be happening.  Also, where as I once had all of my backups on the disk, I now only have one from about a month ago and Time Machine will not replace it with the backup I need to make currently.  I tried to create space on the disk by "Deleting all backups from this time machine" and by dragging the items from the finder window to trash-  Neither of these things worked to erase the old back up and/or create space on my external drive for the backup I wish to make currently... does anyone have any answers or advice????

    chaseandlacey wrote:
    Where I am confused is that... prior to this month.  I've backed up my Macbook repeatedly on this same external hard drive since last April.  Until recently I knotied that TM kept several old backups from different dates (as per the design).  Then when I started having trouble recently, I realized there is now only one previous backup.  DId my backups become larger to the point that instead of several there is now only room for one at a time?
    Check what's shown for Estimated size of full backup under the exclusions box in TM Prefs > Options.
    Most likely, something very large was added or changed, and had to be backed-up. 
    It's also possible that your backups were failing for the last month, leaving many partial backups (TM cleans them up, but only after one completes successfully).
    A clue may be lurking in your logs.  Use the widget in #A1 of Time Machine - Troubleshooting to display the backup messages from your logs.  Look back as far as it will let you (probably only a couple of days) and see what's there.  Most of the messages are fairly clear, so you might be able to figure out what happened.  If in doubt, copy and post all the messages from a representative backup here.

  • Help-Erasing a Boot Camp Partition Caused 32 GB of Disk Space to Vanish

    Hi
    I'm a new mac user I'd I have been really happy so far, expect for this problem:
    -I created a 32 gb partition with boot camp.
    -I tried installing windows xp without knowing I had to format the system to NTFS during the install
    The installation didnt work, and I erased the bootcamp partition.
    -When I tried to create a new boot camp partition, it said my Mac HD size hard drive is 227 gb, ie the *32 gb allocated to the partition had vanished*. In addition, I could not recreate a partition because of an error message.
    -I ran the snow leopard CD's disk utility and thought that I had fixed the problem.
    -However in boot camp, the mac drive is still only 227 gb (missing 32 gb). I can create partitions now, and deleting these partitions does cause any additional loss of disk space.
    -I tried erasing empty disk space with no luck.
    Does anyone know how to recover space lost by Boot Camp?
    Thanks

    qcpharaoh wrote:
    -When I tried to create a new boot camp partition, it said my Mac HD size hard drive is 227 gb, ie the *32 gb allocated to the partition had vanished*. In addition, I could not recreate a partition because of an error message.
    -I ran the snow leopard CD's disk utility and thought that I had fixed the problem.
    -However in boot camp, the mac drive is still only 227 gb (missing 32 gb). I can create partitions now, and deleting these partitions does cause any additional loss of disk space.
    Let me ask a simple question. What size HD do you have in your Mac? You say you see 227 GB and that 32GB is "missing". If I add those two numbers up I com up with 259 GB. I suspect that your "missing" space is due to the inconsistencies in which Snow Leopard now reports 1 GB. In some places it reports 1 GB as a hard disk manufacturer (1 GB = 1,000,000,000 bytes). In other places it reports 1 GB as a binary number (1 GB = 2^^30 [IIRC] = 1,073,741,824 Bytes). Since I do not know of any drive manufacturer that sells a 259 GB drive, I suspect that this is just due to the differing definitions of 1 GB.

  • How do I free up disk space on my MacBook Air

    Hi,
    I have a MacBook Air with a 128GB disk. I recently noticed that I seemed to be using up 74% of the disk capacity so thought I would try and remove some old video files from iTunes. When deleting the files I was prompted to remove the files from the file system which I did. I then empted the trash. But that seems to have very little impact on the disk space used. Considering I must have deleted about 20-30GB of files I would have expected the disk usage to come down a fair bit (I have a 128GB SSD).
    Any idea how I can get my disk usage back down?
    Thanks
    Andy

    Have a look at these Links...
    Where did my Disk Space go?
    what-to-do-when-your-hard-drive-is-full.html
    And Here  >  The Storage Display

  • Re-Recording DVD+RW disks?

    I have a LaCie d2 DVD±RW drive and was planning to use DVD+RW disks to (hopefully) re-record iPhoto library backups, ITunes backups, etc. I wanted to use the same disks every month, instead of using DVD+R or DVD-R disks and throwing them out.
    Well, after the first record on by DVD+RW disk, I went in the next time to use the same disk and got "cannot record to disk". It thought it was write-locked and could not be reused. The Finder also sees the DVD+RW disk as read-only.
    I must be doing something wrong.
    Plus one other odd thing. System Profiler shows the LaCie drive as:
    Manufacturer: LaCie Group SA
    Model: > LaCie d2 DVD-RW Firewire
    Drive Type: CD-RW/DVD-RW
    Could I be missing some kind of driver update perhaps?
    Thanks for any suggestions.
    -- Dave

    No, Disk Utility does not present the option to erase it. The Erase button is grey out.
    On the LaCie site, there is this driver. I can burn the DVD+RW - but only once. Perhaps I need to install this too?
    LaCie DiscRecording Support 1.25 for Mac OS X 10.3.2 or later
    Posted: March 29, 2007
    Mac (Download) [475 KB]
    The LaCie DiscRecording installer will add the latest LaCie drive support to burning applications that use the DiscRecording framework. This includes but is not limited to, the Finder, iTunes, iPhoto, Backup, Disk Utility and DVD Studio Pro.

  • Hard Disk or Power Problem

    I have a Powerbook that I have had for many years now. Recently it hasn't been booting up. I hit the start button and it chimes like it usually does but the screen and hard disk don't do anything. Sometimes it does boot up but it doesn't start easily. When it does boot sometime freezes when I go through the login and when loading the desktop but once the desktop is loaded it works fine until it goes to sleep. I just bought a new battery for it this summer. I have been reading though the Discussions and I figure my computer is either having power problems when starting up or I need a new hard disk. Any thoughts?

    You will find step by step directions at iFixit. Note that your computer does not have the EMI finger referred to in the directions. Also, be especially careful with the tiny screws in the sides on the computer. You don't want to strip the heads or it will be very difficult to get them out. Here are few tips you may find helpful:
    • Print out the ifixit directions as well as the screw guide ahead of time.
    • Be sure you have the right tools. You don't want to damage the screw heads or you may never get them out. And the Torx screw driver is critical. For a spudge I use the handle of an old toothbrush (choose one made of hard plastic), cut off the brush and beveled the handle end like a flat blade screw driver). For some spudge jobs a credit card will do the trick.
    • Click on the pages of each step which involved removing screws to enlarge, then print out the pages. Poke holes in the paper where the screws were removed, poke the screws in the holes and stack the pages in order in which there were removed. Reassembling is a lot easier. No cups to tip over and spill. No guessing. Each screw is exactly in the right place. You can use an ice cube tray, egg carton, dixie cups etc. I previously used small medicine cups one for the screws in each step. I nested them so that the last ones out and the first to go back in are on top. (Some users report cutting up the screw guide and placing the applicable section in each container.)
    • Be very careful pulling out leads. Hold the lead as close to the plug as possible and wiggle (the plug ) to loosen its grip. Don’t hold the wires and pull as that can damage the cable, or worse, in some instances pull the wires out of the plug. Indeed, some users have pulled the socket off the logic board! Use needle nose pliers or tweezers if you can access the plug, or nudge the plug with a small instrument to help loosen its grip.
    • Use force gently in removing parts. Separating upper and lower case takes some doing. Use a plastic tool (spudge) so as not to leave marks.
    • Refer to the screw guide when reassembling computer. Putting longer screws in the wrong place can perforate the circuit board.
    So will I be able to put the OS and everything on by the installation discs?
    Yes you will. Indeed you may be able to clone the contents of your current HDD to the new HDD by placing the drive in a firewire enclosure and formatting and cloning the new drive before installing it in the computer. If you have data you need to backup and have a sound installation on your current HDD this might be an option to consider.
    When you get your new HDD it will need to be formatted before you can install the OS on it. If you need directions for formatting and installation, I can post step by step directions here for you. Let me know.
    Good luck.
    cornelius

  • IBook CD-RW Drive Disk Question

    I recently bought a iBook 500MHz with the CD-RW drive and OSX 10.3.9. At first, I could load and read any CD and never had need to write to one - until now. All of a sudden, I was having trouble getting it to load and read disks. I followed all the suggestions from other threads for a fix and now it will recognize a CD-R or CD-RW disk, but it won't write to a 700 Mb CD-R disk.
    I have tried 3 brands of CD's without success. The system recognizes the CD, but won't write to it with Apple's system or with Roxio Toast. By chance, I had a 650 Mb
    CD-RW disk and both OSX and Toast are able to read and write to it??
    Do you think it is possible that the drive is old enough (outdated firmware) that it can't write to a 700 Mb disk? I don't have a 650 Mb CD-R lying around to try it out, and nobody seems to sell them anymore. I do have several 650 Mb CD-RW disks available. Will OSX read a CD-RW as a bootable disk. Any thoughts?
    iBook G3 500   Mac OS X (10.3.9)  
    iBook G3 500   Mac OS X (10.3.9)  

    Well, after messing around with this thing for upteen hours and getting no where, I took the iBook to an apple shop and they diagnosed a damaged CD-RW drive. It would still read disks, but not perform R/RW.
    I was fortunate to pick up a used Toshiba SD-R2002 CD-RW/DVD-ROM Laptop Drive on eBay pretty cheap. I used the PBFixit guide to take the laptop apart and replace the CD drive. It took me about 3 hours to do the operation. Fortunately, the new (old) drive works fine - R/RW. Since the iBook didn't originally come with a DVD player, I had to manually install iDVD. DVD movies play very well on this 500 MHz system.
    The only problem I had was that the iBook CD drive snap connectors on the face plate didn't match up with the new drive caddy. I had to break them off and reglue them in different positions to line up and also grind off some other protrusions. Once the glue dried, it snapped right into place and alignment (boy, was I lucky, and very happy that my 3 additional hours of work paid off). I really didn't want to spend an extra $30 or so for a new face plate but I figured I had nothing to loose here.
    Bottom line...your CD-R/RW drive is probably also broken. Good luck.
    iBook G3 500   Mac OS X (10.3.9)  

Maybe you are looking for