G3 Hard Drive boots up only partially

I've just reinstalled my 6G hard drive in my blueberry after using my 6 month old 60G hard drive from it to back up my new iMac G5. The reinstalled hard drive boot sequence is: blank gray, then white then gray with a small question mark for one second then then the little squared face icon (OS 9 or 10.2 as I recall) for a second, soon replaced by the Apple and a few seconds later joined by the little "circling circle" and finally the Apple is permanently replaced by a circle with diagonal slash with the other little circle still circling. This sequence doesn't change although I've tried the iMac Software Restore, Software Reinstall, and OS 10.2 Install, with and without holding the C down while rebooting, and have zapped the PRAM and done all again. I welcome all suggestions. I'm confident the hard drive is physically installed properly. Thanks!

Dale, thanks much, but none of the methods worked. The reinstalled hard drive has 10.3 on it, installed by a Mac dealer who didn't give me the discs; I only have 10.2 (and 7.5) discs, which I suspect won't work to reinstall since 10.3 is on the hard drive . Do I have any recourse other than trying to retrieve a 10.3 startup disc?

Similar Messages

  • If you format in Guid for Intel Macs, Apple partition for PPC Macs for Boot drives, then why do my PPC Hard drives Boot in my 2007 Mac Pro, what gives?

      I recently purchased a 2007 Mac Pro for a song, swapped the CPU's for octo chipsets and proceeded to wait for new Hdd's in the mail. I was told the Hard drives in my old G5 would not be bootable unless they're in Guid format. Disc Utility confirmed to use the specific maps as well and yet all of my 2006 PPC Power Mac G5 Hard drives boot in my MP without a hitch, although a few none universal apps do not work. So what am I missing, does it really matter which Apple partion map to choose from or is this a fluke?...

    all of my 2006 PPC Power Mac G5 Hard drives boot in my MP without a hitch
    Yes, and what version of Mac OS  are they booting?
    >> They will boot the OS that is on them, but not a later one.

  • How do I use AirPort Extreme to be able print from my MacBook Pro AND a PC. If I connect printer into AirPort, I can only print on laptop. If printer is connected to PC hard drive, I can only print on desk top. How do I configure this to make both print?

    How do I use AirPort Extreme to be able print from my MacBook Pro AND a PC. If I connect printer into AirPort, I can only print on laptop. If printer is connected to PC hard drive, I can only print on desk top. How do I configure this to make both print?

    If you have not already done so, your chances will really improve if you....
    1) Connect the printer to the USB port on the AirPort Extreme
    2) Download and install Bonjour Print Services for Windows on the PC

  • My external hard drive is read only

    Hey guys,
    I'm just transferring stuff from a windows pc and i had all my music on my external hard drive. Well i set my default iTunes folder back to my external on my new mac but my hard drive is read only so it won't let me download anything after i buy it. How can i change it from read only?
    Thanks

    If the external drive is formatted NTFS, OSX can read but not write to it.
    MacFUSE is supposed to add NTFS write support to OSX
    <http://julipedia.blogspot.com/2007/03/ntfs-readwrite-support-for-mac-os-x.html> , but it may be safer to copy the data from the drive, the re-format it to Mac Extended (or FAT32 if you still want to use in on Windows). Re-formatting will erase the disk, so save the data first.

  • External Hard Drive Becomes Read Only

    I have a LaCie Hard Drive that Time Machine has been backing up to for about 4 days now. All of a sudden, the external hard drive is read only. When I go into Get Info for the hard drive, I can't even change the read/write permissions - it's all grayed out. This is the second time it's happened. The first time was on a Western Digital MyBook. TM fried that drive. At least this drive hasn't disappeared like the last time.
    I've now changed the Time Machine backup to my second hard drive on my Mac Pro (which is screaming along, as opposed to the FW800 [!!] backup on my La Cie, whose file transfers are slo-o-o-w).
    The idea behind backing up onto the external was so that if I ever needed to leave during a fire or earthquake, I could bring this with me and not worry if my computer was destroyed. Insurance would replace the computer, and I could replace my system.
    If it weren't formatted properly, it wouldn't have been backing up for the last few days.
    Can anyone help?
    Message was edited by: Theresa Mesa

    Thank you to everyone who has posted about this issue -- it just happened to me AGAIN this morning (this is my 3rd time), after I installed the 10.5.2 update. The first two times were right after I hooked up my external Iomega 500GB drive to use with Time Machine and I thought it was something I was doing. Then it seemed to work fine for a couple months so I thought the problem was over. Guess not! It is frustrating because I just lost about 2 months worth of backups. So finally I searched Apple's discussion forums and saw that I am not alone. However, no one was really posting a solution other than to say "reformat the drive".
    So I did a Google search about this topic and encountered the following article. I have just gone through the steps he outlines and although I won't know for awhile if it works, I figure at this point it can't hurt to try. I hope this proves useful to others as well. (One note -- in his article, he says to skip the Erase tab and go right to the Partition tab. If you don't see the Partition tab, first erase your corrupt Time Machine backup disk and then follow his steps.)
    http://gizmodo.com/gadgets/apple/leopard-disk-utility-format-issue-screws-with-t ime-machine-but-theres-an-easy-fix-316573.php
    Cheers ~
    Message was edited by: sneebish

  • Photos in my from my iPhone have same numbering as photos from my dig camera.  They all go into iPhoto fine but when I backup to my ext hard drive it will only save one with the name IMG 1002 and I have two separate images both with that name.  Help?

    Photos in my from my iPhone have the same numbering as photos from my digital camera.  They all go into iPhoto fine but when I backup to my ext hard drive it will only save one with the name IMG 1002 and I have two separate images both with that name.  How do I get them all to save on my ext hard drive and hope do I prevent this numbering overlap in the future?  I'm really hoping I don't have to go through and manually rename every single picture.  Thanks.

    How are you backing up the photos?  The best way is to backup the library itself as that will preserve your organizational efforts as well as all metadata like keywords, titles, faces, places, books, etc.
    You can use a backup application that does incremental backups.  Thus only the first backup is a full one and subsequent backups just copy those files that are new or changed. I use Synk Pro.  The lower cost version, Synk, will do the same job.  Other similar apps can be found at MacUpdate.com.  
    OR: upload your camera to a folder on the Desktop. There you can rename the files to something that is more informative than just the file name.  I use the date (international format) along with a brief desc: 2007-1-20-adian1stbday-001.jpg.  File renaming apps can also be found at MacUpdate.com.  Also you can give the folder an informatve name which will become the Event name when you import the folder of photos into iPhoto.
    OT

  • Elements 5.0 will not download photos onto our hard drive into folders, only individually.    *

    Elements 5.0 will not download photos onto our hard drive into folders, only individually. We have recently changed to Win 7.

    Sorry – I was having trouble using the forum and accidentally doubled up.  Thanks for your suggestion.  We will give it a go.

  • Need help reformatting my hard drive for mac only

    Help please
    Need help reformatting my hard drive for mac only with my toshishba hard drive

    What Mac is this please, with what version of OS X?

  • I had to install a new hard drive because my old hard drives boot files became corrupted, and i want to get all of my music files off the old hard drive and regain all my play counts/ratings/playlists

    Greetings everyone
    as the title says, ive had to install a new hard drive  and i want to transfer my old itunes library onto the new drive, maintaining all playlists/play counts/ratings etc, album artwork if possible. The old hard drive is installed as a slave drive and is completely acessible, but due to the boot files being corrupted i cannot use it as the main drive and therefore operate my old itunes. Also, my ipod no longer contains my music library as itunes synced without my permission and wiped it.
    The only thing i have tried is copying all of my old music files from the old drive by selecting 'add folder to library' and then the old drive, then replacing the new itunes library.itl file with the one from my old itunes. This restores all my playlists and playcounts but when i try to play any of the songs it says that the files could not be found, and i dont fancy locating  8500 music files individually!
    Thankyou for taking the time to read my post, any help will be greatly appreciated.

    Ah, my reply was based on the assumption that you had a default installation of iTunes.
    i.e you had all your music in the iTunes media folder inside your iTunes folder.
    If your iTunes folder is so small compared to the amount of music you have, you must have a different arrangement.
    This complicates you situation considerably.
    iTunes can cope with moving around as long as all the music is in the iTunes media folder, not not if it isn't.
    Your first step should be to get iTunes working on the old drive. This will involve editing the xml library file so that the drive letter is correct and then rebuilding the library from the xml file.
    Then you will need to consolidate your library which moves everything into the iTunes media fodler. After that you will be able to use my first suggestion.
    Step 1
    Find the iTunes folder on the old drive and copy the two library files somewhere else so you can find them again. That's iTunes Library.itl and iTunes Library.xml.
    Now open the copy of iTunes Library.xml with WordPad.
    Look for lines starting:
    Location
    These contain the paths to tracks.
    You will need to use a find/replace to change the drive letter so that it is correct.
    Make sure that you include enough in the "find" so that you only change the right thing.
    Maybe /c:/ and replace with /d:/ or whatever.
    After that, tell iTunes to use the library on the old drive with a shift key start.
    Hold down the shift key and start iTunes, keep holding the shift key until you are prompted to choose a library. Navigate to the iTunes folder on the old drive and choose iTunes Library.itl.
    Then use the method in the following article to rebuild your library;
    http://support.apple.com/kb/HT1451
    Unfortunately the date added will be today for all tracks.
    If iTunes works correctly after this, consolidate your library
    File>>Library>>Organize>>consolidate
    This copies all tracks into to iTunes media folder and could create a problem if you do not have disk space so don't do it if you are unsure about free disk space.
    Check that iTunes works OK and then use the first method.
    Message was edited by: polydorus

  • [Solved] Laptop Suspend puts Hard Drive into Read-Only

    My problem is that s2ram brings back X (and the virtual console, if I'm on one), but never the hard drive.
    s2ram -f -a 1 suspends just like s2ram -f. -a 2 and 3 just make a high pitched sound.
    I tried both http://wiki.archlinux.org/index.php/Suspend_to_RAM and http://wiki.archlinux.org/index.php/Pm-utils methods.
    I updated my BIOS drivers but that didn't help
    s2disk works perfectly.
    This is a COMPAQ Presario CQ60-215DX
    Here is my log of the trouble during resume:
    ata4: SATA link up 3.0 Gbps (SStatus 123 SControl 300)
    ata3: SATA link up 1.5 Gbps (SStatus 113 SControl 300)
    sd 3:0:0:0: [sda] Starting disk
    ata4.00: qc timeout (cmd 0xec)
    ata4.00: failed to IDENTIFY (I/O error, err_mask=0x4)
    ata4.00: revalidation failed (errno=-5)
    ata3.00: qc timeout (cmd 0xa1)
    ata3.00: failed to IDENTIFY (I/O error, err_mask=0x4)
    ata3.00: revalidation failed (errno=-5)
    ata3: SATA link up 1.5 Gbps (SStatus 113 SControl 300)
    ata4: SATA link up 3.0 Gbps (SStatus 123 SControl 300)
    ata3.00: qc timeout (cmd 0xa1)
    ata3.00: failed to IDENTIFY (I/O error, err_mask=0x4)
    ata3.00: revalidation failed (errno=-5)
    ata3: limiting SATA link speed to 1.5 Gbps
    ata4.00: qc timeout (cmd 0xec)
    ata4.00: failed to IDENTIFY (I/O error, err_mask=0x4)
    ata4.00: revalidation failed (errno=-5)
    ata4: limiting SATA link speed to 1.5 Gbps
    ata3: SATA link up 1.5 Gbps (SStatus 113 SControl 310)
    ata4: SATA link up <unknown> (SStatus 103 SControl 310)
    And my full log:
    Linux version 2.6.30-ARCH (root@T-POWA-LX) (gcc version 4.4.1 (GCC) ) #1 SMP PREEMPT Fri Jul 31 07:30:28 CEST 2009
    Command line: root=/dev/disk/by-uuid/9ae7dfa5-74b2-41e2-89bc-b344bbf47109 ro
    KERNEL supported cpus:
    Intel GenuineIntel
    AMD AuthenticAMD
    Centaur CentaurHauls
    libata version 3.00 loaded.
    pata_amd 0000:00:06.0: version 0.4.1
    pata_amd 0000:00:06.0: setting latency timer to 64
    scsi0 : pata_amd
    scsi1 : pata_amd
    ata1: PATA max UDMA/133 cmd 0x1f0 ctl 0x3f6 bmdma 0x30c0 irq 14
    ata2: PATA max UDMA/133 cmd 0x170 ctl 0x376 bmdma 0x30c8 irq 15
    ahci 0000:00:09.0: version 3.0
    ACPI: PCI Interrupt Link [LSI0] enabled at IRQ 22
    ahci 0000:00:09.0: PCI INT A -> Link[LSI0] -> GSI 22 (level, low) -> IRQ 22
    ahci 0000:00:09.0: irq 25 for MSI/MSI-X
    ahci 0000:00:09.0: AHCI 0001.0200 32 slots 2 ports 3 Gbps 0x3 impl IDE mode
    ahci 0000:00:09.0: flags: 64bit ncq sntf led clo pmp pio slum part
    ahci 0000:00:09.0: setting latency timer to 64
    scsi2 : ahci
    scsi3 : ahci
    ata3: SATA max UDMA/133 abar m8192@0xc0004000 port 0xc0004100 irq 25
    ata4: SATA max UDMA/133 abar m8192@0xc0004000 port 0xc0004180 irq 25
    ata2: port disabled. ignoring.
    Clocksource tsc unstable (delta = 4397486409693 ns)
    ata3: SATA link up 1.5 Gbps (SStatus 113 SControl 300)
    ata4: SATA link up 3.0 Gbps (SStatus 123 SControl 300)
    ata4.00: ATA-8: TOSHIBA MK2555GSX, FG002C, max UDMA/100
    ata4.00: 488397168 sectors, multi 16: LBA48 NCQ (depth 31/32)
    ata4.00: configured for UDMA/100
    ata3.00: ATAPI: Optiarc DVD RW AD-7580S, FH03, max UDMA/100
    ata3.00: configured for UDMA/100
    scsi 2:0:0:0: CD-ROM Optiarc DVD RW AD-7580S FH03 PQ: 0 ANSI: 5
    scsi 3:0:0:0: Direct-Access ATA TOSHIBA MK2555GS FG00 PQ: 0 ANSI: 5
    Driver 'sr' needs updating - please use bus_type methods
    sr0: scsi3-mmc drive: 24x/24x writer dvd-ram cd/rw xa/form2 cdda tray
    Uniform CD-ROM driver Revision: 3.20
    sr 2:0:0:0: Attached scsi CD-ROM sr0
    Driver 'sd' needs updating - please use bus_type methods
    sd 3:0:0:0: [sda] 488397168 512-byte hardware sectors: (250 GB/232 GiB)
    sd 3:0:0:0: [sda] Write Protect is off
    sd 3:0:0:0: [sda] Mode Sense: 00 3a 00 00
    sd 3:0:0:0: [sda] Write cache: enabled, read cache: enabled, doesn't support DPO or FUA
    sda: sda1 sda2 sda3 < sda5 > sda4
    sd 3:0:0:0: [sda] Attached SCSI disk
    EXT4-fs: INFO: recovery required on readonly filesystem.
    EXT4-fs: write access will be enabled during recovery.
    EXT4-fs: barriers enabled
    kjournald2 starting: pid 569, dev sda2:8, commit interval 5 seconds
    EXT4-fs: delayed allocation enabled
    EXT4-fs: file extents enabled
    EXT4-fs: mballoc enabled
    EXT4-fs: sda2: orphan cleanup on readonly fs
    ext4_orphan_cleanup: deleting unreferenced inode 148384
    ext4_orphan_cleanup: deleting unreferenced inode 147907
    ext4_orphan_cleanup: deleting unreferenced inode 147903
    EXT4-fs: sda2: 3 orphan inodes deleted
    EXT4-fs: recovery complete.
    EXT4-fs: mounted filesystem sda2 with ordered data mode
    rtc_cmos 00:06: RTC can wake from S4
    rtc_cmos 00:06: rtc core: registered rtc_cmos as rtc0
    rtc0: alarms up to one year, y3k, 114 bytes nvram, hpet irqs
    udev: starting version 141
    pci_hotplug: PCI Hot Plug PCI Core version: 0.5
    shpchp: Standard Hot Plug PCI Controller Driver version: 0.4
    usbcore: registered new interface driver usbfs
    usbcore: registered new interface driver hub
    ACPI: AC Adapter [ADP1] (on-line)
    forcedeth: Reverse Engineered nForce ethernet driver. Version 0.64.
    ACPI: PCI Interrupt Link [LMAC] enabled at IRQ 21
    forcedeth 0000:00:0a.0: PCI INT A -> Link[LMAC] -> GSI 21 (level, low) -> IRQ 21
    forcedeth 0000:00:0a.0: setting latency timer to 64
    sr 2:0:0:0: Attached scsi generic sg0 type 5
    sd 3:0:0:0: Attached scsi generic sg1 type 0
    usbcore: registered new device driver usb
    ehci_hcd: USB 2.0 'Enhanced' Host Controller (EHCI) Driver
    ohci_hcd: USB 1.1 'Open' Host Controller (OHCI) Driver
    cfg80211: Calling CRDA to update world regulatory domain
    input: Power Button as /devices/LNXSYSTM:00/LNXPWRBN:00/input/input2
    ACPI: Power Button [PWRF]
    input: Lid Switch as /devices/LNXSYSTM:00/device:00/PNP0C0D:00/input/input3
    ACPI: Lid Switch [LID0]
    input: Sleep Button as /devices/LNXSYSTM:00/device:00/PNP0C0E:00/input/input4
    ACPI: Sleep Button [SLPB]
    input: Power Button as /devices/LNXSYSTM:00/device:00/PNP0C0C:00/input/input5
    ACPI: Power Button [PWRB]
    processor ACPI_CPU:00: registered as cooling_device0
    processor ACPI_CPU:01: registered as cooling_device1
    forcedeth 0000:00:0a.0: ifname eth0, PHY OUI 0x732 @ 1, addr 00:1f:16:74:cb:72
    forcedeth 0000:00:0a.0: highdma csum pwrctl mgmt lnktim msi desc-v3
    ACPI: PCI Interrupt Link [LUS2] enabled at IRQ 17
    ehci_hcd 0000:00:02.1: PCI INT B -> Link[LUS2] -> GSI 17 (level, low) -> IRQ 17
    ehci_hcd 0000:00:02.1: setting latency timer to 64
    ehci_hcd 0000:00:02.1: EHCI Host Controller
    ehci_hcd 0000:00:02.1: new USB bus registered, assigned bus number 1
    ehci_hcd 0000:00:02.1: debug port 1
    ehci_hcd 0000:00:02.1: cache line size of 64 is not supported
    ehci_hcd 0000:00:02.1: irq 17, io mem 0xc0007000
    ACPI: WMI: Mapper loaded
    ehci_hcd 0000:00:02.1: USB 2.0 started, EHCI 1.00
    usb usb1: configuration #1 chosen from 1 choice
    hub 1-0:1.0: USB hub found
    hub 1-0:1.0: 3 ports detected
    i2c-adapter i2c-0: nForce2 SMBus adapter at 0x3040
    i2c-adapter i2c-1: nForce2 SMBus adapter at 0x3000
    ACPI: PCI Interrupt Link [LUS0] enabled at IRQ 17
    ohci_hcd 0000:00:02.0: PCI INT A -> Link[LUS0] -> GSI 17 (level, low) -> IRQ 17
    ohci_hcd 0000:00:02.0: setting latency timer to 64
    ohci_hcd 0000:00:02.0: OHCI Host Controller
    ohci_hcd 0000:00:02.0: new USB bus registered, assigned bus number 2
    ohci_hcd 0000:00:02.0: irq 17, io mem 0xc0006000
    usb usb2: configuration #1 chosen from 1 choice
    hub 2-0:1.0: USB hub found
    hub 2-0:1.0: 3 ports detected
    ACPI: PCI Interrupt Link [Z011] enabled at IRQ 16
    ehci_hcd 0000:00:04.1: PCI INT B -> Link[Z011] -> GSI 16 (level, low) -> IRQ 16
    ehci_hcd 0000:00:04.1: setting latency timer to 64
    ehci_hcd 0000:00:04.1: EHCI Host Controller
    ehci_hcd 0000:00:04.1: new USB bus registered, assigned bus number 3
    ehci_hcd 0000:00:04.1: debug port 1
    ehci_hcd 0000:00:04.1: cache line size of 64 is not supported
    ehci_hcd 0000:00:04.1: irq 16, io mem 0xc0007400
    ehci_hcd 0000:00:04.1: USB 2.0 started, EHCI 1.00
    usb usb3: configuration #1 chosen from 1 choice
    hub 3-0:1.0: USB hub found
    hub 3-0:1.0: 4 ports detected
    ACPI: PCI Interrupt Link [Z010] enabled at IRQ 16
    ohci_hcd 0000:00:04.0: PCI INT A -> Link[Z010] -> GSI 16 (level, low) -> IRQ 16
    ohci_hcd 0000:00:04.0: setting latency timer to 64
    ohci_hcd 0000:00:04.0: OHCI Host Controller
    ohci_hcd 0000:00:04.0: new USB bus registered, assigned bus number 4
    ohci_hcd 0000:00:04.0: irq 16, io mem 0xc0008000
    usb usb4: configuration #1 chosen from 1 choice
    hub 4-0:1.0: USB hub found
    hub 4-0:1.0: 4 ports detected
    thermal LNXTHERM:01: registered as thermal_zone0
    ACPI: Thermal Zone [TZS0] (68 C)
    ACPI: Battery Slot [BAT0] (battery present)
    thermal LNXTHERM:02: registered as thermal_zone1
    ACPI: Thermal Zone [TZS1] (68 C)
    usb 1-1: new high speed USB device using ehci_hcd and address 2
    nvidia: module license 'NVIDIA' taints kernel.
    Disabling lock debugging due to kernel taint
    usb 1-1: configuration #1 chosen from 1 choice
    Synaptics Touchpad, model: 1, fw: 7.0, id: 0x1a0b1, caps: 0xd04711/0xa00000
    acpi device:13: registered as cooling_device2
    input: Video Bus as /devices/LNXSYSTM:00/device:00/PNP0A08:00/device:10/device:11/input/input6
    ACPI: Video Device [VGA] (multi-head: yes rom: no post: no)
    usb 3-4: new high speed USB device using ehci_hcd and address 2
    input: SynPS/2 Synaptics TouchPad as /devices/platform/i8042/serio2/input/input7
    ath5k 0000:07:00.0: PCI INT A -> Link[Z012] -> GSI 23 (level, low) -> IRQ 23
    ath5k 0000:07:00.0: setting latency timer to 64
    ath5k 0000:07:00.0: registered as 'phy0'
    usb 3-4: configuration #1 chosen from 1 choice
    ACPI: PCI Interrupt Link [LGPU] enabled at IRQ 20
    nvidia 0000:02:00.0: PCI INT A -> Link[LGPU] -> GSI 20 (level, low) -> IRQ 20
    nvidia 0000:02:00.0: setting latency timer to 64
    NVRM: loading NVIDIA UNIX x86_64 Kernel Module 185.18.31 Tue Jul 28 17:52:27 PDT 2009
    EXT4 FS on sda2, internal journal on sda2:8
    Adding 3148700k swap on /dev/sda5. Priority:-1 extents:1 across:3148700k
    scsi 4:0:0:0: Direct-Access Generic- Multi-Card 1.00 PQ: 0 ANSI: 0 CCS
    sd 4:0:0:0: Attached scsi generic sg2 type 0
    usb-storage: device scan complete
    sd 4:0:0:0: [sdb] Attached SCSI removable disk
    scsi 5:0:0:0: Direct-Access USB Driver 0.00 PQ: 0 ANSI: 0 CCS
    sd 5:0:0:0: Attached scsi generic sg3 type 0
    usb-storage: device scan complete
    sd 5:0:0:0: [sdc] 7827456 512-byte hardware sectors: (4.00 GB/3.73 GiB)
    sd 5:0:0:0: [sdc] Write Protect is off
    sd 5:0:0:0: [sdc] Mode Sense: 23 00 00 00
    sd 5:0:0:0: [sdc] Assuming drive cache: write through
    sd 5:0:0:0: [sdc] Assuming drive cache: write through
    sdc:
    sd 5:0:0:0: [sdc] Attached SCSI removable disk
    forcedeth 0000:00:0a.0: irq 26 for MSI/MSI-X
    eth0: no link during initialization.
    NET: Registered protocol family 10
    lo: Disabled Privacy Extensions
    ADDRCONF(NETDEV_UP): eth0: link is not ready
    PM: Syncing filesystems ... done.
    Freezing user space processes ... (elapsed 0.00 seconds) done.
    Freezing remaining freezable tasks ... (elapsed 0.00 seconds) done.
    Suspending console(s) (use no_console_suspend to debug)
    sd 3:0:0:0: [sda] Synchronizing SCSI cache
    sd 3:0:0:0: [sda] Stopping disk
    ath5k 0000:07:00.0: PCI INT A disabled
    forcedeth 0000:00:0a.0: wake-up capability disabled by ACPI
    forcedeth 0000:00:0a.0: PME# disabled
    forcedeth 0000:00:0a.0: PCI INT A disabled
    HDA Intel 0000:00:07.0: PCI INT A disabled
    ata2: port disabled. ignoring.
    ehci_hcd 0000:00:04.1: PCI INT B disabled
    ehci_hcd 0000:00:04.1: PME# disabled
    ohci_hcd 0000:00:04.0: PCI INT A disabled
    ohci_hcd 0000:00:04.0: PME# disabled
    ehci_hcd 0000:00:02.1: PCI INT B disabled
    ehci_hcd 0000:00:02.1: PME# disabled
    ohci_hcd 0000:00:02.0: PCI INT A disabled
    ohci_hcd 0000:00:02.0: PME# disabled
    ACPI: Preparing to enter system sleep state S3
    Disabling non-boot CPUs ...
    CPU 1 is now offline
    SMP alternatives: switching to UP code
    CPU0 attaching NULL sched-domain.
    CPU1 attaching NULL sched-domain.
    CPU0 attaching NULL sched-domain.
    CPU1 is down
    Extended CMOS year: 2000
    x86 PAT enabled: cpu 0, old 0x7040600070406, new 0x7010600070106
    Back to C!
    Extended CMOS year: 2000
    Enabling non-boot CPUs ...
    SMP alternatives: switching to SMP code
    Booting processor 1 APIC 0x1 ip 0x6000
    Initializing CPU#1
    Calibrating delay using timer specific routine.. 4001.76 BogoMIPS (lpj=6666816)
    CPU: L1 I Cache: 64K (64 bytes/line), D cache 64K (64 bytes/line)
    CPU: L2 Cache: 512K (64 bytes/line)
    CPU: Physical Processor ID: 0
    CPU: Processor Core ID: 1
    x86 PAT enabled: cpu 1, old 0x7040600070406, new 0x7010600070106
    CPU1: AMD Athlon Dual-Core QL-62 stepping 01
    CPU0 attaching NULL sched-domain.
    Switched to high resolution mode on CPU 1
    CPU0 attaching sched-domain:
    domain 0: span 0-1 level MC
    groups: 0 1
    CPU1 attaching sched-domain:
    domain 0: span 0-1 level MC
    groups: 1 0
    CPU1 is up
    ACPI: Waking up from system sleep state S3
    ohci_hcd 0000:00:02.0: restoring config space at offset 0x1 (was 0xb00007, writing 0xb00003)
    ehci_hcd 0000:00:02.1: restoring config space at offset 0x1 (was 0xb00006, writing 0xb00002)
    ohci_hcd 0000:00:04.0: restoring config space at offset 0x1 (was 0xb00007, writing 0xb00003)
    ehci_hcd 0000:00:04.1: restoring config space at offset 0x1 (was 0xb00006, writing 0xb00002)
    pata_amd 0000:00:06.0: restoring config space at offset 0x1 (was 0xb00005, writing 0xb80005)
    HDA Intel 0000:00:07.0: restoring config space at offset 0xf (was 0x5020100, writing 0x502010a)
    HDA Intel 0000:00:07.0: restoring config space at offset 0x4 (was 0x0, writing 0xc0000000)
    HDA Intel 0000:00:07.0: restoring config space at offset 0x1 (was 0xb00000, writing 0xb00002)
    ahci 0000:00:09.0: restoring config space at offset 0x1 (was 0xb00007, writing 0xb00407)
    pcieport-driver 0000:00:14.0: restoring config space at offset 0x7 (was 0x1f1, writing 0x200001f1)
    pcieport-driver 0000:00:14.0: restoring config space at offset 0x1 (was 0x100107, writing 0x1005
    nvidia 0000:02:00.0: restoring config space at offset 0xf (was 0x100, writing 0x10a)
    nvidia 0000:02:00.0: restoring config space at offset 0x9 (was 0x1, writing 0x4001)
    nvidia 0000:02:00.0: restoring config space at offset 0x7 (was 0xc, writing 0xc400000c)
    nvidia 0000:02:00.0: restoring config space at offset 0x5 (was 0xc, writing 0xd000000c)
    ath5k 0000:07:00.0: restoring config space at offset 0x3 (was 0x0, writing 0x10)
    nForce2_smbus 0000:00:01.1: PME# disabled
    ohci_hcd 0000:00:02.0: PME# disabled
    ohci_hcd 0000:00:02.0: PCI INT A -> Link[LUS0] -> GSI 17 (level, low) -> IRQ 17
    ohci_hcd 0000:00:02.0: setting latency timer to 64
    ohci_hcd 0000:00:02.0: PME# disabled
    ehci_hcd 0000:00:02.1: PME# disabled
    ehci_hcd 0000:00:02.1: PCI INT B -> Link[LUS2] -> GSI 17 (level, low) -> IRQ 17
    ehci_hcd 0000:00:02.1: setting latency timer to 64
    ehci_hcd 0000:00:02.1: PME# disabled
    usb usb1: root hub lost power or was reset
    ehci_hcd 0000:00:02.1: debug port 1
    ehci_hcd 0000:00:02.1: cache line size of 64 is not supported
    ohci_hcd 0000:00:04.0: PME# disabled
    ohci_hcd 0000:00:04.0: PCI INT A -> Link[Z010] -> GSI 16 (level, low) -> IRQ 16
    ohci_hcd 0000:00:04.0: setting latency timer to 64
    ohci_hcd 0000:00:04.0: PME# disabled
    ehci_hcd 0000:00:04.1: PME# disabled
    ehci_hcd 0000:00:04.1: PCI INT B -> Link[Z011] -> GSI 16 (level, low) -> IRQ 16
    ehci_hcd 0000:00:04.1: setting latency timer to 64
    ehci_hcd 0000:00:04.1: PME# disabled
    usb usb3: root hub lost power or was reset
    ehci_hcd 0000:00:04.1: debug port 1
    ehci_hcd 0000:00:04.1: cache line size of 64 is not supported
    pata_amd 0000:00:06.0: restoring config space at offset 0x1 (was 0xb00005, writing 0xb80005)
    pata_amd 0000:00:06.0: setting latency timer to 64
    ata2: port disabled. ignoring.
    HDA Intel 0000:00:07.0: PCI INT A -> Link[LAZA] -> GSI 19 (level, low) -> IRQ 19
    HDA Intel 0000:00:07.0: setting latency timer to 64
    pci 0000:00:08.0: setting latency timer to 64
    ahci 0000:00:09.0: setting latency timer to 64
    forcedeth 0000:00:0a.0: wake-up capability disabled by ACPI
    forcedeth 0000:00:0a.0: PME# disabled
    ata4: SATA link up 3.0 Gbps (SStatus 123 SControl 300)
    ata3: SATA link up 1.5 Gbps (SStatus 113 SControl 300)
    forcedeth 0000:00:0a.0: irq 26 for MSI/MSI-X
    eth0: no link during initialization.
    pci 0000:00:0b.0: setting latency timer to 64
    ath5k 0000:07:00.0: PCI INT A -> Link[Z012] -> GSI 23 (level, low) -> IRQ 23
    sd 3:0:0:0: [sda] Starting disk
    ata4.00: qc timeout (cmd 0xec)
    ata4.00: failed to IDENTIFY (I/O error, err_mask=0x4)
    ata4.00: revalidation failed (errno=-5)
    ata3.00: qc timeout (cmd 0xa1)
    ata3.00: failed to IDENTIFY (I/O error, err_mask=0x4)
    ata3.00: revalidation failed (errno=-5)
    ata3: SATA link up 1.5 Gbps (SStatus 113 SControl 300)
    ata4: SATA link up 3.0 Gbps (SStatus 123 SControl 300)
    ata3.00: qc timeout (cmd 0xa1)
    ata3.00: failed to IDENTIFY (I/O error, err_mask=0x4)
    ata3.00: revalidation failed (errno=-5)
    ata3: limiting SATA link speed to 1.5 Gbps
    ata4.00: qc timeout (cmd 0xec)
    ata4.00: failed to IDENTIFY (I/O error, err_mask=0x4)
    ata4.00: revalidation failed (errno=-5)
    ata4: limiting SATA link speed to 1.5 Gbps
    ata3: SATA link up 1.5 Gbps (SStatus 113 SControl 310)
    ata4: SATA link up <unknown> (SStatus 103 SControl 310)
    ata4.00: qc timeout (cmd 0xec)
    ata4.00: failed to IDENTIFY (I/O error, err_mask=0x4)
    ata4.00: revalidation failed (errno=-5)
    ata4.00: disabled
    ata3.00: qc timeout (cmd 0xa1)
    ata3.00: failed to IDENTIFY (I/O error, err_mask=0x4)
    ata3.00: revalidation failed (errno=-5)
    ata3.00: disabled
    sd 3:0:0:0: [sda] START_STOP FAILED
    sd 3:0:0:0: [sda] Result: hostbyte=0x04 driverbyte=0x00
    sd 3:0:0:0: [sda] Unhandled error code
    sd 3:0:0:0: [sda] Result: hostbyte=0x04 driverbyte=0x00
    end_request: I/O error, dev sda, sector 134590273
    Buffer I/O error on device sda2, logical block 1094141
    lost page write due to I/O error on sda2
    sd 3:0:0:0: [sda] Unhandled error code
    sd 3:0:0:0: [sda] Result: hostbyte=0x04 driverbyte=0x00
    end_request: I/O error, dev sda, sector 135807281
    Buffer I/O error on device sda2, logical block 1246267
    lost page write due to I/O error on sda2
    sd 3:0:0:0: [sda] Unhandled error code
    sd 3:0:0:0: [sda] Result: hostbyte=0x04 driverbyte=0x00
    end_request: I/O error, dev sda, sector 135815833
    Buffer I/O error on device sda2, logical block 1247336
    lost page write due to I/O error on sda2
    JBD2: Detected IO errors while flushing file data on sda2:8
    sd 3:0:0:0: [sda] Unhandled error code
    sd 3:0:0:0: [sda] Result: hostbyte=0x04 driverbyte=0x00
    end_request: I/O error, dev sda, sector 155463993
    Aborting journal on device sda2:8.
    sd 3:0:0:0: [sda] Unhandled error code
    sd 3:0:0:0: [sda] Result: hostbyte=0x04 driverbyte=0x00
    end_request: I/O error, dev sda, sector 155459417
    Buffer I/O error on device sda2, logical block 3702784
    lost page write due to I/O error on sda2
    JBD2: I/O error detected when updating journal superblock for sda2:8.
    PM: Device 3:0:0:0 failed to resume: error 262144
    usb 1-1: reset high speed USB device using ehci_hcd and address 2
    usb 3-4: reset high speed USB device using ehci_hcd and address 2
    Restarting tasks ... <2>ext4_abort called.
    EXT4-fs error (device sda2): ext4_journal_start_sb: Detected aborted journal
    Remounting filesystem read-only
    ext4_da_writepages: jbd2_start: 1024 pages, ino 131086; err -30
    Pid: 20, comm: pdflush Tainted: P 2.6.30-ARCH #1
    Call Trace:
    [<ffffffffa00d738d>] ? ext4_da_writepages+0x47d/0x4b0 [ext4]
    [<ffffffff8026c6a4>] ? bit_waitqueue+0x24/0xe0
    [<ffffffff802c8332>] ? do_writepages+0x32/0x60
    [<ffffffff80321b7a>] ? __writeback_single_inode+0xba/0x490
    [<ffffffff802406e6>] ? dequeue_task_fair+0x56/0x1d0
    [<ffffffff8020a95c>] ? __switch_to+0xdc/0x3b0
    [<ffffffff803223b3>] ? generic_sync_sb_inodes+0x193/0x530
    [<ffffffff803229c5>] ? writeback_inodes+0x65/0x120
    [<ffffffff802c85a6>] ? wb_kupdate+0xc6/0x160
    [<ffffffff802c995b>] ? pdflush+0x16b/0x2a0
    [<ffffffff802c84e0>] ? wb_kupdate+0x0/0x160
    [<ffffffff802c97f0>] ? pdflush+0x0/0x2a0
    [<ffffffff802c97f0>] ? pdflush+0x0/0x2a0
    [<ffffffff8026c204>] ? kthread+0x64/0xc0
    [<ffffffff8024af20>] ? schedule_tail+0x30/0x80
    [<ffffffff8020d4fa>] ? child_rip+0xa/0x20
    [<ffffffff8026c1a0>] ? kthread+0x0/0xc0
    [<ffffffff8020d4f0>] ? child_rip+0x0/0x20
    sd 3:0:0:0: [sda] Unhandled error code
    sd 3:0:0:0: [sda] Result: hostbyte=0x04 driverbyte=0x00
    end_request: I/O error, dev sda, sector 126637417
    sd 3:0:0:0: [sda] Unhandled error code
    sd 3:0:0:0: [sda] Result: hostbyte=0x04 driverbyte=0x00
    end_request: I/O error, dev sda, sector 126637417
    sd 3:0:0:0: [sda] Unhandled error code
    sd 3:0:0:0: [sda] Result: hostbyte=0x04 driverbyte=0x00
    end_request: I/O error, dev sda, sector 126637417
    sd 3:0:0:0: [sda] Unhandled error code
    sd 3:0:0:0: [sda] Result: hostbyte=0x04 driverbyte=0x00
    end_request: I/O error, dev sda, sector 126637417
    sd 3:0:0:0: [sda] Unhandled error code
    sd 3:0:0:0: [sda] Result: hostbyte=0x04 driverbyte=0x00
    end_request: I/O error, dev sda, sector 126637417
    done.
    sd 3:0:0:0: [sda] Unhandled error code
    sd 3:0:0:0: [sda] Result: hostbyte=0x04 driverbyte=0x00
    end_request: I/O error, dev sda, sector 130097993
    EXT4-fs error (device sda2): ext4_find_entry: reading directory #139292 offset 0
    sd 3:0:0:0: [sda] Unhandled error code
    sd 3:0:0:0: [sda] Result: hostbyte=0x04 driverbyte=0x00
    end_request: I/O error, dev sda, sector 126637417
    sd 3:0:0:0: [sda] Unhandled error code
    sd 3:0:0:0: [sda] Result: hostbyte=0x04 driverbyte=0x00
    end_request: I/O error, dev sda, sector 126004889
    EXT4-fs error (device sda2): ext4_find_entry: reading directory #98457 offset 0
    sd 3:0:0:0: [sda] Unhandled error code
    sd 3:0:0:0: [sda] Result: hostbyte=0x04 driverbyte=0x00
    end_request: I/O error, dev sda, sector 126004889
    EXT4-fs error (device sda2): ext4_find_entry: reading directory #98457 offset 0
    ANY help would be much appreciated.
    Last edited by Cappy (2009-08-10 08:19:09)

    Nevermind .. *sigh* ... pci=msi on the kernel fixed it .. going to go cut myself now ...

  • [SOLVED] Strange Hard Drive Errors - Read Only Filesystem?

    Solution: Discard old laptop, buy new laptop
    I have an Acer Aspire 5103WLMi. For about 2 months now, Arch has been running smoothly. Until 2 weeks ago.
    It all started when I tried to install and configure autofs on Arch x86_64. On the next reboot, all manner of errors were printed to the screen, to the effect that the internal hard drive was only being mounted read-only, rendering the system unusable. I tried to find a solution, but there were no references to read-only anywhere; fstab, grub etc. None that I could find.
    I tried reinstalling. However, x86_64 Arch refused to boot properly first time due to the exact same error; and I *know* that I'm configuring everything correctly. I managed (somehow) to coerce i686 Arch to install, and things "work".
    Seemingly out of the blue, during normal operation, all running applications will stop, and spit out error after error to the effect of "Cannot Write to Read Only Filesystem!". Sakura won't load (Input/Output error, apparently), and the only way to shut down the laptop is a hard reset (I can't log in as root or use sudo because it wants to write to the filesystem first, which it obviously can't.
    Now, I'm going to be giving the insides of this laptop a good cleanout this weekend, and I'm in the process of backing up all of my data, but I was wondering if anyone else has come across a similar form of misbehaviour; or (with a bit of luck) some potential solutions?
    This is very peculiar, because there seems to be no reason why the laptop suddenly loses write permissions to the hard drive. Cheers.
    Edit: I think I should point out that my /boot partition is Ext2, and / and /home are Ext3
    Last edited by aphirst (2013-03-27 14:51:38)

    Smartctl gives me the impression it's my Hard Drive:
    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 Raw_Read_Error_Rate 0x000b 100 100 050 Pre-fail Always - 0
    2 Throughput_Performance 0x0005 100 100 050 Pre-fail Offline - 0
    3 Spin_Up_Time 0x0027 100 100 001 Pre-fail Always - 1711
    4 Start_Stop_Count 0x0032 100 100 000 Old_age Always - 6194
    5 Reallocated_Sector_Ct 0x0033 100 100 050 Pre-fail Always - 0
    7 Seek_Error_Rate 0x000b 100 100 050 Pre-fail Always - 0
    8 Seek_Time_Performance 0x0005 100 100 050 Pre-fail Offline - 0
    9 Power_On_Hours 0x0032 092 092 000 Old_age Always - 3291
    10 Spin_Retry_Count 0x0033 223 100 030 Pre-fail Always - 0
    12 Power_Cycle_Count 0x0032 100 100 000 Old_age Always - 1218
    192 Power-Off_Retract_Count 0x0032 100 100 000 Old_age Always - 294
    193 Load_Cycle_Count 0x0032 088 088 000 Old_age Always - 123904
    194 Temperature_Celsius 0x0022 100 100 000 Old_age Always - 34 (Lifetime Min/Max 15/62)
    196 Reallocated_Event_Count 0x0032 100 100 000 Old_age Always - 0
    197 Current_Pending_Sector 0x0032 100 100 000 Old_age Always - 0
    198 Offline_Uncorrectable 0x0030 100 100 000 Old_age Offline - 0
    199 UDMA_CRC_Error_Count 0x0032 200 200 000 Old_age Always - 17
    220 Disk_Shift 0x0002 100 100 000 Old_age Always - 118
    222 Loaded_Hours 0x0032 094 094 000 Old_age Always - 2425
    223 Load_Retry_Count 0x0032 100 100 000 Old_age Always - 0
    224 Load_Friction 0x0022 100 100 000 Old_age Always - 0
    226 Load-in_Time 0x0026 100 100 000 Old_age Always - 444
    240 Head_Flying_Hours 0x0001 100 100 001 Pre-fail Offline - 0
    Everything being either Old_age or Pre-fail is not encouraging. Additionally, in the output is what I believe to be records of what caused my strange read-only behaviour:
    Error 19 occurred at disk power-on lifetime: 3287 hours (136 days + 23 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
    84 51 01 11 18 6a e1 Error: ICRC, ABRT 1 sectors at LBA = 0x016a1811 = 23730193
    Commands leading to the command that caused the error were:
    CR FR SC SN CL CH DH DC Powered_Up_Time Command/Feature_Name
    c8 00 48 c4 17 6a e1 00 04:43:08.023 READ DMA
    c8 00 48 14 e3 69 e1 00 04:43:08.022 READ DMA
    c8 00 a0 5c e2 69 e1 00 04:43:08.010 READ DMA
    c8 00 08 9c e5 69 e1 00 04:43:08.010 READ DMA
    c8 00 20 5c e5 69 e1 00 04:43:08.009 READ DMA
    Could this truly be referring to my problem, since the 'logs' show that the *exact same* error occurred many times.
    Not that this tells me how to fix it...
    Well, if anyone knows if there is a solution, I'd love to know. If the only solution is to ditch the Hard Drive, fair enough. Either way: I'm backing up all of my important data ASAP.
    Cheers.
    Oh, and kclive18, after I noticed that I couldn't get onto my Drive, I reinstalled arch, leaving no trace of /etc/autofs/auto.media.
    Additionally, somehow I have now been able to install Arch x86_64, but the problems still occur...

  • FireWire I External Hard Drive Boot Up Problem

    I have a 400 Mhz Blue & White G3 running OS X 10.4.8 or Classic 9.2. I also have an IOMEGA 400 Gig Hard Drive capable of connecting with FireWire I & II and USB and an IOMEGA 120 Gig Hard Drive capable of connecting via FireWire I. Of course, the G3 only has FireWire I capability. I also have a PowerBook G4 running OS X 10.4.8.
    The 400 Gig HD boots under all three methods of connection.
    The IOMEGA 400 Gig hard drive will connect via all three methods on the PowerBook G4, but will only boot on the G3 under USB in OS X, i.e., it won't boot on the G3 using FireWire I in OS X.
    However it will boot on the G3 using FireWire I under System 9.2 (Classic).
    NOTE: The 120 Gig HD will boot to the G3 under OS X using FireWire I. And other of my peripherals also work on the G3 under OS X using FireWire I.
    Bottom Line: What can I do to have the G3 recognize the 400 Gig HD when running under OSX?
    Blue & White 400 Mhz G3   Mac OS X (10.4.8)  

    One other thing you mentioned it is seen in Classic but not on OS X. I am not sure if you are aware of this but your drive comes FAT32 formatted. Below is a link to tell you a little more about as to why mac os x can't support a FAT32 partition over 128GB.
    http://docs.info.apple.com/article.html?artnum=107483
    Here are a few steps to resolving your issue.
    STEP ONE - Confirm that the drive is being seen by the system
    Click the Apple icon and select About This Mac.
    Click More Info.
    Select the Drives and Volumes tab.
    If the Iomega Hard Disk drive is not listed under the USB/FireWire arrow, proceed to STEP THREE.
    If the Iomega Hard Disk drive is listed, continue with the next step.
    STEP TWO - Format the Iomega Hard Disk drive to Mac HFS format
    The Iomega Hard Disk drive is factory formatted to FAT32 for maximum compatibility. If you have not reformatted the disk or the disk is formatted to FAT32:
    The disk may mount very slowly in OS X if the disk is FAT32 formatted.
    Mac OS X will not mount any DOS (FAT32) partition larger than 128GB. For more information, please check the Apple® Web site at http://docs.info.apple.com/article.html?artnum=107483
    Warning: Erasing your Iomega Hard Disk drive will erase all of the information stored on the disk. If possible, back up your data before erasing the hard drive. Mac formatted disks are not cross compatible with other operating systems, such as Windows®, without the purchase of additional third-party software.
    Double-click the Mac hard drive icon.
    Double-click the Applications folder.
    Double-click the Utilities folder.
    Double-click the Disk Utilities icon.
    Highlight the Iomega drive in the left window.
    Click the Erase tab.
    Select Mac OS Extended.
    Click the Erase button and then click Erase from the confirmation window.
    If the Iomega Hard Disk drive now mounts, you are ready to use the drive.
    If the Iomega Hard Disk drive does not mount, continue with the next step.
    STEP THREE - Are the Mac OS X drivers detecting the drive properly?
    The Iomega Hard Drive may not mount if you are using Mac OS X versions under 10.1.3. If you are not using Mac OS X 10.1.3 or higher, please visit the Apple® Web site at http://www.apple.com/macosx/ for information on getting the latest version.

  • Is there a size limit for hard drive boot partition?

    I have been using Drive Genius to adjust the size of my boot partition larger. But it doesn't seem to allow for much increase, even though I deleted the second partition and tried to apply the disk space to DH1: (boot - there is a single partition on the hard drive now.)
    It recognizes only 59.53gb and the drive is I think around 130gb. Anything beyond 59.53 is unusable since I deleted that second partition though I could probably get it back with a second partition.
    Is this a Tiger issue or a Mac issue? It resized it bigger somewhat, so it seems to be something about the particular size. I want a really big space for my applications and so on.
    Thanks. Didn't know where to post this question.

    You don't want to make a disc image. You want to clone to an external drive:
    How to Clone Using Restore Option of Disk Utility
    1. Open Disk Utility from the Utilities folder.
    2. Select the backup or destination volume from the left side list.
    3. Click on the Erase tab in the DU main window. Set the format type to Mac OS Extended (journaled, if available) and click on the Erase button. This step can be skipped if the destination has already been freshly erased.
    4. Click on the Restore tab in the DU main window.
    5. Select the backup or destination volume from the left side list and drag it to the Destination entry field.
    6. Select the startup or source volume from the left side list and drag it to the Source entry field.
    7. Double-check you got it right, then click on the Restore button.
    Once you finish the clone open Startup Disk and set the clone as your startup volume, then click on the Restart button. You should now boot from the clone. You can then repartition the internal hard drive the way you want, then clone the external drive to the internal one.

  • I mac g5 hard drive booting issues

    My problem is this, i just tried to upgrade from tiger to snow lep, the installer got stuck so i siwthced it off and concealed defeat and went to do a full format job, once i deleted all the files i formatted to guid so the hard drive would be bootable right? i then installed snow lep all seemed well  but now the hard drive wont appear in the boot menu although it appears in disk utilities on the snow lep install disk

    If you are really running a PPC G5, you cannot install Snow Leopard, it only works on intel machines. And you need to partition a PPC as APC, not GUID.  opefully you have a full backup to resore your drive from.

  • Swapped hard drive boot problem

    Swapped hard drives between 6530b and 6535b, neither boots. What did I miss? (Toshiba MK3255GSX and Hitachi HTS543223L9A300)

    Disk Utility - Erase (drive, not volume) and make sure it is now GPT/GUID and not old Apple Partition Table format.
    Even though it is data only, there can and are some problems (the older it was last formatted the more so perhaps).
    Just pull the data off if needed. Handy to have a FW drive case for SATA laying around.
    Migrating OS and apps from G5 to Intel is full of potential pitfalls.
    Depending on the drive age, size, performance, I'd probably go for a WD Caviar 640GB $75 to transfer files onto, and then wipe the Maxtor and use it for an emergency backup drive off which you can run Disk Warrior and such.

Maybe you are looking for