Internal HD won't mount

My wife says she wasn't doing anything when the imac froze and then she restarted it via power button. But then start up got stuck at the grey screen with the wheel. I booted up from a SuperDuper image and opened disk util to see if i had to repair anything and would not recognize the HD. It wouldn't show up while holding option during start up, so I manually mounted it via terminal. I had it erased, repaired and holding D at start up it says everything is fine. However, even though the HD shows up at holding option now, installer hangs at the last minute. The last line of the installer log reads:
mac installer error updatedyld_sharedcache failed: read failure copying dylib errno=5 for System/Library/Frameworks/ApplicationServices.framework/Versions/A/Frameworks/H IServices.framework/Versions/A/HIServices while copying /System/Library/Frameworks/ApplicationServices.framework/Versions/A/Frameworks/ HIServices.framework/Versions/A/HIServices to shared cache.
everything above that is no receipt for...
This is a 2007 imac that installed leopard on when it came out and had been perfect until yesterday.
Help would be awesome...I think the HD might be corrupted

took it to the apple store, the exact words were, it sounds like monster truck is running around in there (hard drive)...haha

Similar Messages

  • Original internal HDD won't mount.

    I recently had my iMac HDD upgraded from 500gig to 2TB and now I'd like to grab some old files off my original HDD. To do this I bought myself a Dynamode SATA USB docking station and ran migration assistant. MOST of the files copied across but some (my movies, a bunch of applications & some work files) didn't.
    Unfortunately now it seems my machine won't mount the drive again. Is there some clever way I can force it to mount or check why it's not?

    Hey Ben. A couple of obvious things to try. Restart and the try to connect. Also, when the drive is connected, open Disk Utility to see if it recognizes the drive and you may be able to mount it from there.
    I've used a similar device from OWC and I found that sometimes you need to plug and unplug a few times before it's seen.
    Hope it helps.

  • Internal HDD Won't Mount

    I have an Aluminum 2007 20" iMac. Running Yosemite 10.10.2 and all Apple apps upgraded to latest versions. I have installed a Kingston 120GB SSD in the optical bay, which is the boot drive. I have replaced the original internal HDD (250GB) with a Western Digital 1TB, which I use for file storage (music/docs/pics, etc). I added the SSD and replaced the internal HDD about 12 months ago and everything worked like a charm. Yesterday (Feb 19), when I booted up the computer, the internal HDD was missing from the desktop and did not show up in System Profile as a SATA drive, nor a an option for a Start-up drive. Not a calamity, because I have an external HDD as a Time Machine backup, so all files are available for recovery.
    I restarted using a USB Bootable drive, and the missing HDD shows up as an available drive for restore/restart. So I can restart off the (previously missing) internal HHD, and everything is normal that way (the SSD also mounts normally as a second drive). I ran Disk Utility and OnyX on the internal drive when it was the boot drive, and there is no indication of a problem. I also restored the internal HDD from Time Machine using the last back-up before it disappeared. When I restart again from the SSD, the internal HDD is gone again.
    Any ideas?

    I ended up re-installing Yosemite 10.10.2 on both drives, and things are (so far) back to normal. I'll be back again if I have this problem recur.

  • 1TB WD Caviar Black SATA internal drive won't mount on desktop or Disk Util

    I just installed this brand new drive in bay B of my G5 tower...it doesn't appear on the desktop, and not in Disk Utility. Can a 1 TB SATA3 drive be functional in a G5? The owner's manual only mentions a maximum 250GB (or 500GB drive, don't recall) ; maybe that was the biggest available in 2004/05?

    Thanks, all. I found a link to WDC drive jumper settings (http://wdc.custhelp.com/cgi-bin/wdc.cfg/php/enduser/stdadp.php?p_faqid=1337&p_created=1112379341&p_sid=eST7ItDi&p_accessibility=0&p_red irect=&p_lva=&p_sp=cF9zcmNoPTEmcF9zb3J0X2J5PSZwX2dyaWRzb3J0PSZwX3Jvd19jbnQ9NDg3J nBfcHJvZHM9MCZwX2NhdHM9MCZwX3B2PSZwX2N2PSZwX3NlYXJjaF90eXBlPWFuc3dlcnMuc2VhcmNoX 2ZubCZwX3BhZ2U9MSZwX3NlYXJjaF90ZXh0PWp1bXBlciBzZXR0aW5ncyBzYXRh&p_li=&ptopview=1), and jumpered pins 5 and 6 to limit transfer speeds to 150 MB/s. On restart, the OS prompted me to initialize, which I did, and voila, the drive is mounted.
    Question: it appears the jumper setting is to convert a SATA2 dirve to SATA1. Is there any reason to try (or jumper setting that would enable) converting my SATA 3 drive to a SATA2 configuration?

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

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

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

  • Hard Drive In 2nd Internal Bay Sometimes won't mount

    I recently installed a second internal drive in my computer. My main problem is sometimes the drive won't mount. If I turn off the computer for a while it will finally mount but that's not good enough. One day it may not mount at all. What I want to know is; does anybody else have this problem and if so, how did you fix it?
    Or better yet, is there a command I can use in Terminal to mount the drive?
    G5 Dual 2.5 GHz; 4.5 Gig Ram; Logic Pro 7.1.1   Mac OS X (10.4.5)   2nd internal 160 gig hard drive installed

    Barry, make sure all of your connections are seated properly. I had this same problem with a SP 1.8 PowerMac, and the problem was that the cable was not seated well which disrupts the signals from getting to the drive. This caused the drive to mount sometimes, and not mount others. Check connections at the drive and motherboard.
    Jeff Weinberg

  • G4733DA w/ 4 internal HD's sometimes won't mount/boot to alternate HD-Why?

    I own a G4 733 DA w/ 4 internal HD's which sometimes won't mount/boot to an alternate HD on an internal Sonnet PCI controller card (position 1 only).
    I can also boot to either of the 2 HD's on the sonnet pci controller card (even though neither shows up on system profiler in OS X.4.10). One of which is a Seagate 7200rpm, 400GB which I am currently booted to right now (it's in slot 2 of the sonnet pci card and works fine) However, at times the HD on slot 1 refuses to mount on the desktop. When I remove the same hard drive it mounts fine on an ext. FW enclosure.
    Is it possible that slot one on this sonnet pci card is starting to go out? And how do I know for certain since neither of the HD's on this Sonnet pci controller card show up on system profiler? Is this normal? Shouldn't every hard drives show up in Apple's system profiler? Even the ones on the pci controller card? Should I just try a separate HD on the same slot and see what happens? I have all of the drives cloned to a much larger ext. FW HD so I'm not really worried about loss of data since I have all drives backed up to ext. FW HD's.

    Neither of the HD's on this Sonnet pci controller card show up on system profiler. Is this normal?
    Yes, it is normal. Earlier versions (before Panther) of System Profiler would show the drives connected to a Sonnet PCI controller, but current versions just show the controller itself. Disk Utility should show the drives.
    Each port on the Sonnet card can have up to two drives, one Master, one Slave. The Master should be at the end of the cable. If a Western Digital drive is alone on a cable, it should be set to Single. Drives on the Sonnet card that are set to Slave are not bootable.
    Try swapping cables at the Sonnet card. If the same drive has problems, then it is the drive or cable. Try swapping just the cables.

  • External disc won't mount in Leopard, but will in Snow Leopard

    I have a 5-yr-old G5 networked to a new iMac. I have had a 1-TB external HD attached via Firewire 400 to the G5 for about a year. Yesterday it didn't show up on the G5 desktop. I went to this forum, searched under "disc won't mount", got some ideas, ran DiskWarrior and Disk Utility...but nothing worked. They all said the disc was fine, directories rebuilt, etc., but it wouldn't mount. This AM it occurred to me that I had the correct cable, so I tried plugging it into the iMac instead. It worked. The data is safe, the disc shows up, everything seems to be OK, but it won't mount to the G5. Why would that happen, and how can I mount it to the G5? And how likely is the disc to remain accessible?

    May I hop onto your thread as I have a similar problem.
    I have a 5 year old G5 PMac with 10.5 onto which I have daisy chained two UltraMax 1TB firewire 800 drives. For the last 5 years I have been able, even with out sharing enabled, to connect to the G5 from a G4 Graphite with 10.4, a G4 Powerbook with 10.5 and now a MbP with 10.6.
    After completing the login dialogue in the past from any other mac it would give me a list of the G5, it's Hard disk, user directories and the two Firewire Drives. On selecting them the drive would mount onto the desktop as a network drive. This went well until monday when it became temperamental in the morning and after a few restarts and one successful mount it has not shown up since. If I come to the G5 via the Go > Connect to Server I get a dialogue "Could Not connect to the server because the name or password are incorrect". If I try to connect via the network icon in the side window of the finder window I get a network dialogue log in, I get a list of folders and drives but then when selecting the FH drive get an error message which relates to the alias to the G5 Server requiring deleting or fixing.
    Originally it just connected without any messing but now unless i make the firewire drive a shared drive the process on the other macs cannot see the firewire drive. NOTE - After having made the internal boot HD of the G5 shared, I can now see and mount this drive from the other macs but not the external drive.
    This is causing me to pull my hair out, I have run disk utility, powered down unconnected and reconnected everything .The HD's appear to be working ok from the G5.
    I urgently need to connect the FW drive to my G4 to do some work but it also needs to be connected to the G5, has anyone got a clue why I cant get G4 (or any other mac) to mount G5's external FW drive

  • Fantom external hard drive won't mount

    I am using an imac G3 with OS 10.3.9. Until yesterday my Fantom external hard drive mounted. I dismounted it and turned it off. I went to turn it back on later and it won't mount. I selected initialize from the dialogue box that says it won't mount and when disk utility comes up it show the two icons for the internal hard drive and just one for the external so I can't do anything with it. Thanks for your help.
    imac Mac OS X (10.3.9)
    imac Mac OS X (10.3.9)
    imac   Mac OS X (10.3.9)  

    Thought you could use this info about getting FireWire to work!
    First, you should always Repair Permissions in Disk Utility before and after any update; I would do that now. If you installed your update with FireWire plugged in, your Mac may not recognize it anymore.
    Try resetting your FireWire ports by disconnecting all FW devices, shut down your Mac and unplug it from AC power (wall socket) for 30 minutes. plug it back in and try FW.
    If that did'nt work, download the combo update from this site (yours may be corrupt), not Software Update, disconnect all firewire + USB devices except keyboard + mouse, Repair Permissions, re-install update, Repair Permissions again + try. Yours is the 10.3.9 Combo update. Others reading, download the Combo that applies to your system.
    If that still did'nt get it Zap the PRAM. While restarting Mac hold down the following key combo Command-Option-P-R. Keep holding those keys down till you hear the second start-up chime, then release.
    For those of you with Macs that are not PowerBooks or iBooks, a bad internal battery can cause FireWire to not be recognized, so make sure it's good!
    Good Luck!
    Cheers!
    DALE
    p.s. Hi to you too Sherry! Keep up the good work!

  • External hard drive won't mount any more

    I do a daily backup of the data on my internal HD to an external HD via FireWire. For some reason, the backup froze tonight - 10 minutes went by with no change in the progress. The only way I could get out of it was to quit everything, Force quit the ones that wouldn't respond, then reboot.
    The internal HD is fine, but the external HD that I back up to won't mount now. I ran Disk Utility, and it sees the drive, but the Finder doesn't. In Disk Utility, if I click on "Verify Disk," I get this message:
    Verifying volume “FireWire Disk”
    Checking HFS Plus volume.
    Checking Extents Overflow file.
    Checking Catalog file.
    The volume FireWire Disk needs to be repaired.
    Volume check failed.
    Error: The underlying task reported failure on exit (-9972)
    1 volume checked
    0 HFS volumes verified
    1 volume failed verification
    Does this mean I have lost everything on the external disk? What do I need to do to get that disk running and mounted again? There were other files on the external disk, besides the backup. There were some large video files that I will have to capture from tape again if they cannot be recovered.
    Thank you for your help!

    Cornelius,
    Thank you for your reply. I was able to get out of the situation through luck. I read on another forum a post by someone in a similar situation, and they said that the drive would mount on a different Mac. So I tried plugging in the drive to my old iMac, and sure enough it mounted, although when Disk Utility was run, the same error message was given.
    Fortunately I was able to copy the files I need from the drive to the iMac's internal drive. The copy worked even though there was obviously a problem with the external drive. Then I erased the external drive using Disk Utility, and copied the files back onto it.
    So I'm back where I started, and I didn't lose any files that I really need. But it was pretty scary for a while - I thought I would have to re-do a lot of work. Fortunately I don't, but I realize how valuable it is to have a second backup in case the first one fails. I am now going to duplicate everything onto the iMac's drive until the project is finished and I can archive it all. I still don't know how the disk got so messed up, and I'm surprised that a disk can get corrupted so easily.

  • Internal hard drives not mounting on startup

    Problem: I recently did a clean install of Mac OS X 10.8 Mountain Lion on my Early 2008 Mac Pro. Since then, one or more of my four internal hard drives will not mount at startup, and it's seemingly random which ones will or won't mount; it differs from one startup to the next. Obviously, the boot drive starts up, but the remaining three drives are hit-or-miss.
    Troubleshooting So Far: I can open Disk Utility and mount the disk(s) manually, and when I click Verify Disk, the hardware checks out okay. After my most recent startup, I brought up the System Log in Terminal (sudo syslog -B) and found this entry for one disk ("Media 1") that did not mount:
    Apr 25 10:40:09 new-host-2.home fseventsd[48] <Critical>: event logs in /Volumes/Media 1/.fseventsd out of sync with volume.  destroying old logs. (454 0 68038)
    Apr 25 10:40:09 new-host-2.home revisiond[33] <Warning>: Had metainfo
    Apr 25 10:40:09 new-host-2.home revisiond[33] <Warning>: UUIDs match!
    Apr 25 10:40:09 new-host-2.home fseventsd[48] <Critical>: log dir: /Volumes/Media 1/.fseventsd getting new uuid: 1D55396E-183E-42AA-B788-FEFFF8694C10
    Apr 25 10:40:09 new-host-2.home fseventsd[48] <Critical>: Events arrived for /Volumes/Media 1 after an unmount request! Re-initializing.
    Apr 25 10:40:09 new-host-2.home fseventsd[48] <Critical>: creating a dls for /Volumes/Media 1 but it already has one...
    Apr 25 10:40:09 new-host-2.home SecurityAgent[147] <Notice>: User info context values set for dangreene
    Apr 25 10:40:09 new-host-2.home fseventsd[48] <Error>: disk logger: failed to open output file /Volumes/Media 1/.fseventsd/0000000000000c6d (No such file or directory). mount point /Volumes/Media 1/.fseventsd
    There were no entries for the disks that mounted correctly. Can anyone make sense of this for me? The system jargon is a little beyond me.
    Thanks for your help!

    Is "Media 1" the name of the volume, or is it just "Media"?

  • USB disk won't mount on startup (have tried everything)

    Hi!
    I'm having big problems getting my USB disk to mount on startup.:(
    It used to work perfectly by having 'mount /dev/sdc1 /media/disk' in rc.local (and umount in local.shutdown) but recently it started saying that 'filesystem type must be defined' (or something like that). So I changed the line to 'mount -t ext3 /dev/sdc1 /media/disk' but now I get a message that '/dev/sdc1 does not exist'.
    So I decided to get this fixed in fstab once and for all.
    I checked the designations of the disks with 'fdisk -l' and noticed that the USB disk would alternate between /dev/sdc, /dev/sde and /dev/sdd quite random on every reboot. In other words I couldn't mount it in fstab by using one of those paths cause I'd get the same problem with '/dev/sdc or -e or -d does not exist'. I figured the sollution must be to mount the disk by using UUID. I checked the uuid's and got the following (as you can see the USB disk is on this reboot registered as '/dev/sde'):
    bash-3.2$ ls -l /dev/disk/by-uuid/
    total 0
    lrwxrwxrwx 1 root root 10 2009-02-07 11:56 6cf5e803-429a-44c3-bcf9-0f007df623f3 -> ../../sda1
    lrwxrwxrwx 1 root root 10 2009-02-07 11:56 8ef6be20-ee30-4a00-8946-56a4d94a7245 -> ../../sda3
    lrwxrwxrwx 1 root root 10 2009-02-07 11:56 947b3b86-8501-4011-9da2-4de45eb4ed60 -> ../../sda2
    lrwxrwxrwx 1 root root 10 2009-02-07 11:56 94911fb3-def7-4440-b6a5-5e09f91b19f6 -> ../../sde1
    lrwxrwxrwx 1 root root 10 2009-02-07 11:56 acd197d3-f63e-48f9-88de-41eff1b3b425 -> ../../sda4
    lrwxrwxrwx 1 root root 10 2009-02-07 11:56 b6745703-bde6-44ef-865d-d09501ecc8ab -> ../../sdb1
    I other words the UUID of the disk should be '94911fb3-def7-4440-b6a5-5e09f91b19f6' so I added that to the fstab file, but I still get the same error that the disk doesn't exist. How is this possible? Isn't the UUID supposed to be the same no matter what? When the disk is clearly labeled with this UUID every time I check it why can't it be used in fstab??
    Here's my fstab (I've commented out the lines that I've been trying out):
    # /etc/fstab: static file system information
    # <file system> <dir> <type> <options> <dump> <pass>
    none /dev/pts devpts defaults 0 0
    none /dev/shm tmpfs defaults 0 0
    /dev/cdrom /mnt/cdrom iso9660 ro,user,noauto,unhide 0 0
    /dev/dvd /mnt/dvd udf ro,user,noauto,unhide 0 0
    /dev/sda1 /boot ext2 defaults 0 1
    /dev/sda2 / ext3 defaults 0 1
    /dev/sda3 /var reiserfs defaults 0 1
    /dev/sda4 /home ext3 defaults 0 1
    /dev/sdb1 /extra ext3 defaults 0 1
    #/dev/sdc1 /media/disk defaults 0 0
    #UUID=94911fb3-def7-4440-b6a5-5e09f91b19f6 /media/disk defaults 0 0
    What am I doing wrong here? I've also tried to use different options like 'rw,auto,exec' but it won't work.

    It seems I'm able to mount the disk from the terminal by doing '# sudo mount UUID=94911fb3-def7-4440-b6a5-5e09f91b19f6 /media/disk'.
    But this only works when I do it manually. Adding 'mount UUID=94911fb3-def7-4440-b6a5-5e09f91b19f6 /media/disk' to rc.local only gives the error that filesystem must be defined and when it's defined I get the error that device is not found.
    How can it work manually, but not in fstab or rc.local?
    Here's my dmesg:
    BIOS EBDA/lowmem at: 0009f800/0009f400
    Linux version 2.6.28-ARCH (root@T-POWA-LX) (gcc version 4.3.3 (GCC) ) #1 SMP PREEMPT Mon Feb 2 22:22:59 UTC 2009
    KERNEL supported cpus:
    Intel GenuineIntel
    AMD AuthenticAMD
    NSC Geode by NSC
    Cyrix CyrixInstead
    Centaur CentaurHauls
    Transmeta GenuineTMx86
    Transmeta TransmetaCPU
    UMC UMC UMC UMC
    BIOS-provided physical RAM map:
    BIOS-e820: 0000000000000000 - 000000000009f400 (usable)
    BIOS-e820: 000000000009f400 - 00000000000a0000 (reserved)
    BIOS-e820: 00000000000f0000 - 0000000000100000 (reserved)
    BIOS-e820: 0000000000100000 - 000000007fef0000 (usable)
    BIOS-e820: 000000007fef0000 - 000000007fef3000 (ACPI NVS)
    BIOS-e820: 000000007fef3000 - 000000007ff00000 (ACPI data)
    BIOS-e820: 00000000e0000000 - 00000000f0000000 (reserved)
    BIOS-e820: 00000000fec00000 - 0000000100000000 (reserved)
    DMI 2.4 present.
    Phoenix BIOS detected: BIOS may corrupt low RAM, working it around.
    last_pfn = 0x7fef0 max_arch_pfn = 0x100000
    x86 PAT enabled: cpu 0, old 0x7040600070406, new 0x7010600070106
    Scanning 0 areas for low memory corruption
    modified physical RAM map:
    modified: 0000000000000000 - 0000000000010000 (reserved)
    modified: 0000000000010000 - 000000000009f400 (usable)
    modified: 000000000009f400 - 00000000000a0000 (reserved)
    modified: 00000000000f0000 - 0000000000100000 (reserved)
    modified: 0000000000100000 - 000000007fef0000 (usable)
    modified: 000000007fef0000 - 000000007fef3000 (ACPI NVS)
    modified: 000000007fef3000 - 000000007ff00000 (ACPI data)
    modified: 00000000e0000000 - 00000000f0000000 (reserved)
    modified: 00000000fec00000 - 0000000100000000 (reserved)
    kernel direct mapping tables up to 377fe000 @ 10000-16000
    RAMDISK: 7fe0e000 - 7fedf2e4
    Allocated new RAMDISK: 0055f000 - 006302e4
    Move RAMDISK from 000000007fe0e000 - 000000007fedf2e3 to 0055f000 - 006302e3
    ACPI: RSDP 000F8600, 0014 (r0 HP-CPC)
    ACPI: RSDT 7FEF3040, 0038 (r1 HP-CPC AWRDACPI 42302E31 AWRD 0)
    ACPI: FACP 7FEF30C0, 0084 (r2 HP-CPC AWRDACPI 42302E31 AWRD 0)
    ACPI: DSDT 7FEF31C0, 3C55 (r1 HP-CPC AWRDACPI 1000 MSFT 100000E)
    ACPI: FACS 7FEF0000, 0040
    ACPI: SSDT 7FEF6F40, 01CA (r1 HP-CPC POWERNOW 1 LTP 1)
    ACPI: SRAT 7FEF7180, 00A0 (r1 HP-CPC HAMMER 1 AMD 1)
    ACPI: MCFG 7FEF7280, 003C (r1 HP-CPC AWRDACPI 42302E31 AWRD 0)
    ACPI: APIC 7FEF6E80, 0068 (r1 HP-CPC AWRDACPI 42302E31 AWRD 0)
    ACPI: Local APIC address 0xfee00000
    1158MB HIGHMEM available.
    887MB LOWMEM available.
    mapped low ram: 0 - 377fe000
    low ram: 00000000 - 377fe000
    bootmap 00012000 - 00018f00
    (9 early reservations) ==> bootmem [0000000000 - 00377fe000]
    #0 [0000000000 - 0000001000] BIOS data page ==> [0000000000 - 0000001000]
    #1 [0000001000 - 0000002000] EX TRAMPOLINE ==> [0000001000 - 0000002000]
    #2 [0000006000 - 0000007000] TRAMPOLINE ==> [0000006000 - 0000007000]
    #3 [0000100000 - 000055b520] TEXT DATA BSS ==> [0000100000 - 000055b520]
    #4 [000055c000 - 000055f000] INIT_PG_TABLE ==> [000055c000 - 000055f000]
    #5 [000009f400 - 0000100000] BIOS reserved ==> [000009f400 - 0000100000]
    #6 [0000010000 - 0000012000] PGTABLE ==> [0000010000 - 0000012000]
    #7 [000055f000 - 00006302e4] NEW RAMDISK ==> [000055f000 - 00006302e4]
    #8 [0000012000 - 0000019000] BOOTMAP ==> [0000012000 - 0000019000]
    found SMP MP-table at [c00f46e0] 000f46e0
    Zone PFN ranges:
    DMA 0x00000010 -> 0x00001000
    Normal 0x00001000 -> 0x000377fe
    HighMem 0x000377fe -> 0x0007fef0
    Movable zone start PFN for each node
    early_node_map[2] active PFN ranges
    0: 0x00000010 -> 0x0000009f
    0: 0x00000100 -> 0x0007fef0
    On node 0 totalpages: 523903
    free_area_init_node: node 0, pgdat c0406600, node_mem_map c1000200
    DMA zone: 32 pages used for memmap
    DMA zone: 0 pages reserved
    DMA zone: 3951 pages, LIFO batch:0
    Normal zone: 1744 pages used for memmap
    Normal zone: 221486 pages, LIFO batch:31
    HighMem zone: 2318 pages used for memmap
    HighMem zone: 294372 pages, LIFO batch:31
    Movable zone: 0 pages used for memmap
    SB4X0 revision 0x11
    Ignoring ACPI timer override.
    If you got timer trouble try acpi_use_timer_override
    ACPI: PM-Timer IO Port: 0x4008
    ACPI: Local APIC address 0xfee00000
    ACPI: LAPIC (acpi_id[0x00] lapic_id[0x00] enabled)
    ACPI: LAPIC (acpi_id[0x01] lapic_id[0x01] enabled)
    ACPI: LAPIC_NMI (acpi_id[0x00] high edge lint[0x1])
    ACPI: LAPIC_NMI (acpi_id[0x01] high edge lint[0x1])
    ACPI: IOAPIC (id[0x02] address[0xfec00000] gsi_base[0])
    IOAPIC[0]: apic_id 2, version 33, address 0xfec00000, GSI 0-23
    ACPI: INT_SRC_OVR (bus 0 bus_irq 0 global_irq 2 dfl dfl)
    ACPI: BIOS IRQ0 pin2 override ignored.
    ACPI: INT_SRC_OVR (bus 0 bus_irq 9 global_irq 21 low level)
    Enabling APIC mode: Flat. Using 1 I/O APICs
    Using ACPI (MADT) for SMP configuration information
    SMP: Allowing 2 CPUs, 0 hotplug CPUs
    PM: Registered nosave memory: 000000000009f000 - 00000000000a0000
    PM: Registered nosave memory: 00000000000a0000 - 00000000000f0000
    PM: Registered nosave memory: 00000000000f0000 - 0000000000100000
    Allocating PCI resources starting at 80000000 (gap: 7ff00000:60100000)
    PERCPU: Allocating 36864 bytes of per cpu data
    NR_CPUS: 16, nr_cpu_ids: 2, nr_node_ids 1
    Built 1 zonelists in Zone order, mobility grouping on. Total pages: 519809
    Kernel command line: root=/dev/sda2 ro quiet
    Enabling fast FPU save and restore... done.
    Enabling unmasked SIMD FPU exception support... done.
    Initializing CPU#0
    PID hash table entries: 4096 (order: 12, 16384 bytes)
    Fast TSC calibration using PIT
    Detected 2188.552 MHz processor.
    Console: colour VGA+ 80x25
    console [tty0] enabled
    Dentry cache hash table entries: 131072 (order: 7, 524288 bytes)
    Inode-cache hash table entries: 65536 (order: 6, 262144 bytes)
    Scanning for low memory corruption every 60 seconds
    Memory: 2072040k/2096064k available (2227k kernel code, 22632k reserved, 1026k data, 332k init, 1186760k highmem)
    virtual kernel memory layout:
    fixmap : 0xffee8000 - 0xfffff000 (1116 kB)
    pkmap : 0xff800000 - 0xffc00000 (4096 kB)
    vmalloc : 0xf7ffe000 - 0xff7fe000 ( 120 MB)
    lowmem : 0xc0000000 - 0xf77fe000 ( 887 MB)
    .init : 0xc0433000 - 0xc0486000 ( 332 kB)
    .data : 0xc032cfd9 - 0xc042db5c (1026 kB)
    .text : 0xc0100000 - 0xc032cfd9 (2227 kB)
    Checking if this processor honours the WP bit even in supervisor mode...Ok.
    SLUB: Genslabs=12, HWalign=64, Order=0-3, MinObjects=0, CPUs=2, Nodes=1
    Calibrating delay loop (skipped), value calculated using timer frequency.. 4378.48 BogoMIPS (lpj=7295173)
    Security Framework initialized
    Mount-cache hash table entries: 512
    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: 0
    Intel machine check architecture supported.
    Intel machine check reporting enabled on CPU#0.
    Checking 'hlt' instruction... OK.
    ACPI: Core revision 20080926
    ACPI: Checking initramfs for custom DSDT
    ..TIMER: vector=0x30 apic1=0 pin1=0 apic2=-1 pin2=-1
    CPU0: AMD Athlon(tm) 64 X2 Dual Core Processor 4200+ stepping 01
    Booting processor 1 APIC 0x1 ip 0x6000
    Initializing CPU#1
    Calibrating delay using timer specific routine.. 4379.66 BogoMIPS (lpj=7295468)
    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
    Intel machine check architecture supported.
    Intel machine check reporting enabled on CPU#1.
    x86 PAT enabled: cpu 1, old 0x7040600070406, new 0x7010600070106
    CPU1: AMD Athlon(tm) 64 X2 Dual Core Processor 4200+ stepping 01
    Brought up 2 CPUs
    Total of 2 processors activated (8757.15 BogoMIPS).
    net_namespace: 768 bytes
    Booting paravirtualized kernel on bare hardware
    NET: Registered protocol family 16
    ACPI: bus type pci registered
    PCI: MCFG configuration 0: base e0000000 segment 0 buses 0 - 255
    PCI: MCFG area at e0000000 reserved in E820
    PCI: Using MMCONFIG for extended config space
    PCI: Using configuration type 1 for base access
    ACPI: EC: Look up EC in DSDT
    ACPI: Interpreter enabled
    ACPI: (supports S0 S1 S3 S4 S5)
    ACPI: Using IOAPIC for interrupt routing
    ACPI: No dock devices found.
    ACPI: PCI Root Bridge [PCI0] (0000:00)
    pci 0000:00:00.0: reg 18 io port: [0x4100-0x411f]
    pci 0000:00:00.0: reg 1c 64bit mmio: [0xe0000000-0xffffffff]
    pci 0000:00:02.0: PME# supported from D0 D3hot D3cold
    pci 0000:00:02.0: PME# disabled
    pci 0000:00:12.0: reg 10 io port: [0xfe00-0xfe07]
    pci 0000:00:12.0: reg 14 io port: [0xfd00-0xfd03]
    pci 0000:00:12.0: reg 18 io port: [0xfc00-0xfc07]
    pci 0000:00:12.0: reg 1c io port: [0xfb00-0xfb03]
    pci 0000:00:12.0: reg 20 io port: [0xfa00-0xfa0f]
    pci 0000:00:12.0: reg 24 32bit mmio: [0xfe02f000-0xfe02f1ff]
    pci 0000:00:12.0: reg 30 32bit mmio: [0x000000-0x07ffff]
    pci 0000:00:12.0: supports D1 D2
    pci 0000:00:13.0: reg 10 32bit mmio: [0xfe02e000-0xfe02efff]
    pci 0000:00:13.1: reg 10 32bit mmio: [0xfe02d000-0xfe02dfff]
    pci 0000:00:13.2: reg 10 32bit mmio: [0xfe02c000-0xfe02cfff]
    pci 0000:00:13.2: supports D1 D2
    pci 0000:00:13.2: PME# supported from D0 D1 D2 D3hot
    pci 0000:00:13.2: PME# disabled
    pci 0000:00:14.0: reg 10 io port: [0x500-0x50f]
    pci 0000:00:14.0: reg 14 32bit mmio: [0xfe02b000-0xfe02b3ff]
    HPET not enabled in BIOS. You might try hpet=force boot option
    pci 0000:00:14.1: reg 10 io port: [0x00-0x07]
    pci 0000:00:14.1: reg 14 io port: [0x00-0x03]
    pci 0000:00:14.1: reg 18 io port: [0x00-0x07]
    pci 0000:00:14.1: reg 1c io port: [0x00-0x03]
    pci 0000:00:14.1: reg 20 io port: [0xf800-0xf80f]
    pci 0000:01:00.0: reg 10 32bit mmio: [0xfa000000-0xfaffffff]
    pci 0000:01:00.0: reg 14 64bit mmio: [0xd0000000-0xdfffffff]
    pci 0000:01:00.0: reg 1c 64bit mmio: [0xfb000000-0xfbffffff]
    pci 0000:01:00.0: reg 24 io port: [0xef00-0xef7f]
    pci 0000:01:00.0: reg 30 32bit mmio: [0x000000-0x01ffff]
    pci 0000:00:02.0: bridge io port: [0xe000-0xefff]
    pci 0000:00:02.0: bridge 32bit mmio: [0xfa000000-0xfcffffff]
    pci 0000:00:02.0: bridge 64bit mmio pref: [0xd0000000-0xdfffffff]
    pci 0000:02:01.0: reg 10 io port: [0xdf00-0xdfff]
    pci 0000:02:01.0: supports D1 D2
    pci 0000:02:03.0: reg 10 io port: [0xde00-0xdeff]
    pci 0000:02:03.0: reg 14 32bit mmio: [0xfdeff000-0xfdeff0ff]
    pci 0000:02:03.0: reg 30 32bit mmio: [0x000000-0x00ffff]
    pci 0000:02:03.0: supports D1 D2
    pci 0000:02:03.0: PME# supported from D1 D2 D3hot D3cold
    pci 0000:02:03.0: PME# disabled
    pci 0000:02:04.0: reg 10 32bit mmio: [0xfdefe000-0xfdefe7ff]
    pci 0000:02:04.0: reg 14 io port: [0xdd00-0xdd7f]
    pci 0000:02:04.0: supports D2
    pci 0000:02:04.0: PME# supported from D2 D3hot D3cold
    pci 0000:02:04.0: PME# disabled
    pci 0000:00:14.4: transparent bridge
    pci 0000:00:14.4: bridge io port: [0xd000-0xdfff]
    pci 0000:00:14.4: bridge 32bit mmio: [0xfde00000-0xfdefffff]
    pci 0000:00:14.4: bridge 32bit mmio pref: [0xfdd00000-0xfddfffff]
    bus 00 -> node 0
    ACPI: PCI Interrupt Routing Table [\_SB_.PCI0._PRT]
    ACPI: PCI Interrupt Routing Table [\_SB_.PCI0.P2P_._PRT]
    ACPI: PCI Interrupt Link [LNKA] (IRQs 3 4 5 6 7 10 11) *0, disabled.
    ACPI: PCI Interrupt Link [LNKB] (IRQs 3 4 5 6 7 10 11) *0, disabled.
    ACPI: PCI Interrupt Link [LNKC] (IRQs 3 4 5 6 7 10 11) *0, disabled.
    ACPI: PCI Interrupt Link [LNKD] (IRQs 3 4 5 6 7 10 11) *0, disabled.
    ACPI: PCI Interrupt Link [LNKE] (IRQs 3 4 5 6 7 *10 11)
    ACPI: PCI Interrupt Link [LNKF] (IRQs *3 4 5 6 7 10 11)
    ACPI: PCI Interrupt Link [LNK0] (IRQs 3 4 5 6 7 10 *11)
    ACPI: PCI Interrupt Link [LNK1] (IRQs 3 4 5 6 7 10 11) *0, disabled.
    PCI: Using ACPI for IRQ routing
    pci 0000:00:00.0: BAR 3: can't allocate resource
    NetLabel: Initializing
    NetLabel: domain hash size = 128
    NetLabel: protocols = UNLABELED CIPSOv4
    NetLabel: unlabeled traffic allowed by default
    pnp: PnP ACPI init
    ACPI: bus type pnp registered
    pnp 00:09: mem resource (0xf0000-0xf3fff) overlaps 0000:00:00.0 BAR 3 (0x0-0x1fffffff), disabling
    pnp 00:09: mem resource (0xf4000-0xf7fff) overlaps 0000:00:00.0 BAR 3 (0x0-0x1fffffff), disabling
    pnp 00:09: mem resource (0xf8000-0xfbfff) overlaps 0000:00:00.0 BAR 3 (0x0-0x1fffffff), disabling
    pnp 00:09: mem resource (0xfc000-0xfffff) overlaps 0000:00:00.0 BAR 3 (0x0-0x1fffffff), disabling
    pnp 00:09: mem resource (0x0-0x9ffff) overlaps 0000:00:00.0 BAR 3 (0x0-0x1fffffff), disabling
    pnp 00:09: mem resource (0x100000-0x7feeffff) overlaps 0000:00:00.0 BAR 3 (0x0-0x1fffffff), disabling
    pnp: PnP ACPI: found 10 devices
    ACPI: ACPI bus type pnp unregistered
    system 00:01: ioport range 0x228-0x22f has been reserved
    system 00:01: ioport range 0x40b-0x40b has been reserved
    system 00:01: ioport range 0x4d6-0x4d6 has been reserved
    system 00:01: ioport range 0xc00-0xc01 has been reserved
    system 00:01: ioport range 0xc14-0xc14 has been reserved
    system 00:01: ioport range 0xc50-0xc52 has been reserved
    system 00:01: ioport range 0xc6c-0xc6d has been reserved
    system 00:01: ioport range 0xc6f-0xc6f has been reserved
    system 00:01: ioport range 0xcd4-0xcdf has been reserved
    system 00:01: ioport range 0x4000-0x40fe has been reserved
    system 00:01: ioport range 0x4210-0x4217 has been reserved
    system 00:06: ioport range 0x4d0-0x4d1 has been reserved
    system 00:06: ioport range 0x800-0x87f has been reserved
    system 00:08: iomem range 0xe0000000-0xefffffff has been reserved
    system 00:09: iomem range 0x7ff00000-0x7fffffff has been reserved
    system 00:09: iomem range 0x7fef0000-0x7fefffff could not be reserved
    system 00:09: iomem range 0xffff0000-0xffffffff has been reserved
    system 00:09: iomem range 0xfec00000-0xfec00fff has been reserved
    system 00:09: iomem range 0xfee00000-0xfee00fff has been reserved
    system 00:09: iomem range 0xfff80000-0xfffeffff has been reserved
    pci 0000:00:02.0: PCI bridge, secondary bus 0000:01
    pci 0000:00:02.0: IO window: 0xe000-0xefff
    pci 0000:00:02.0: MEM window: 0xfa000000-0xfcffffff
    pci 0000:00:02.0: PREFETCH window: 0x000000d0000000-0x000000dfffffff
    pci 0000:00:14.4: PCI bridge, secondary bus 0000:02
    pci 0000:00:14.4: IO window: 0xd000-0xdfff
    pci 0000:00:14.4: MEM window: 0xfde00000-0xfdefffff
    pci 0000:00:14.4: PREFETCH window: 0x000000fdd00000-0x000000fddfffff
    pci 0000:00:02.0: setting latency timer to 64
    bus: 00 index 0 io port: [0x00-0xffff]
    bus: 00 index 1 mmio: [0x000000-0xffffffff]
    bus: 01 index 0 io port: [0xe000-0xefff]
    bus: 01 index 1 mmio: [0xfa000000-0xfcffffff]
    bus: 01 index 2 mmio: [0xd0000000-0xdfffffff]
    bus: 01 index 3 mmio: [0x0-0x0]
    bus: 02 index 0 io port: [0xd000-0xdfff]
    bus: 02 index 1 mmio: [0xfde00000-0xfdefffff]
    bus: 02 index 2 mmio: [0xfdd00000-0xfddfffff]
    bus: 02 index 3 io port: [0x00-0xffff]
    bus: 02 index 4 mmio: [0x000000-0xffffffff]
    NET: Registered protocol family 2
    Switched to high resolution mode on CPU 0
    Switched to high resolution mode on CPU 1
    IP route cache hash table entries: 32768 (order: 5, 131072 bytes)
    TCP established hash table entries: 131072 (order: 8, 1048576 bytes)
    TCP bind hash table entries: 65536 (order: 7, 524288 bytes)
    TCP: Hash tables configured (established 131072 bind 65536)
    TCP reno registered
    NET: Registered protocol family 1
    Unpacking initramfs... done
    Freeing initrd memory: 836k freed
    apm: BIOS version 1.2 Flags 0x07 (Driver version 1.16ac)
    apm: disabled - APM is not SMP safe.
    highmem bounce pool size: 64 pages
    VFS: Disk quotas dquot_6.5.1
    Dquot-cache hash table entries: 1024 (order 0, 4096 bytes)
    msgmni has been set to 1732
    alg: No test for stdrng (krng)
    Block layer SCSI generic (bsg) driver version 0.4 loaded (major 254)
    io scheduler noop registered
    io scheduler anticipatory registered
    io scheduler deadline registered
    io scheduler cfq registered (default)
    pci 0000:00:00.0: MSI quirk detected; MSI disabled
    pci 0000:01:00.0: Boot video device
    pcieport-driver 0000:00:02.0: setting latency timer to 64
    pcieport-driver 0000:00:02.0: found MSI capability
    pci_express 0000:00:02.0:pcie00: allocate port service
    pci_express 0000:00:02.0:pcie01: allocate port service
    pci_express 0000:00:02.0:pcie03: allocate port service
    aer 0000:00:02.0:pcie01: AER service couldn't init device: no _OSC support
    isapnp: Scanning for PnP cards...
    isapnp: No Plug & Play device found
    Serial: 8250/16550 driver4 ports, IRQ sharing disabled
    input: Macintosh mouse button emulation as /class/input/input0
    PNP: No PS/2 controller found. Probing ports directly.
    serio: i8042 KBD port at 0x60,0x64 irq 1
    serio: i8042 AUX port at 0x60,0x64 irq 12
    mice: PS/2 mouse device common for all mice
    cpuidle: using governor ladder
    cpuidle: using governor menu
    TCP cubic registered
    NET: Registered protocol family 17
    Using IPI No-Shortcut mode
    registered taskstats version 1
    Freeing unused kernel memory: 332k freed
    SCSI subsystem initialized
    libata version 3.00 loaded.
    pata_acpi 0000:00:12.0: PCI INT A -> GSI 22 (level, low) -> IRQ 22
    pata_acpi 0000:00:14.1: PCI INT A -> GSI 16 (level, low) -> IRQ 16
    scsi0 : pata_atiixp
    scsi1 : pata_atiixp
    ata1: PATA max UDMA/100 cmd 0x1f0 ctl 0x3f6 bmdma 0xf800 irq 14
    ata2: PATA max UDMA/100 cmd 0x170 ctl 0x376 bmdma 0xf808 irq 15
    ata2.00: ATAPI: HP DVD Writer 740b, ED24, max UDMA/33
    ata2.00: configured for UDMA/33
    scsi 1:0:0:0: CD-ROM HP DVD Writer 740b ED24 PQ: 0 ANSI: 5
    sata_sil 0000:00:12.0: version 2.3
    scsi2 : sata_sil
    scsi3 : sata_sil
    ata3: SATA max UDMA/100 mmio m512@0xfe02f000 tf 0xfe02f080 irq 22
    ata4: SATA max UDMA/100 mmio m512@0xfe02f000 tf 0xfe02f0c0 irq 22
    ata3: SATA link up 1.5 Gbps (SStatus 113 SControl 300)
    ata3.00: ATA-8: SAMSUNG HD501LJ, CR100-10, max UDMA7
    ata3.00: 976773168 sectors, multi 16: LBA48 NCQ (depth 0/32)
    ata3.00: configured for UDMA/100
    ata4: SATA link up 1.5 Gbps (SStatus 113 SControl 300)
    ata4.00: ATA-7: WDC WD2500JS-60MHB1, 10.02E01, max UDMA/100
    ata4.00: 488397168 sectors, multi 16: LBA48
    ata4.00: configured for UDMA/100
    scsi 2:0:0:0: Direct-Access ATA SAMSUNG HD501LJ CR10 PQ: 0 ANSI: 5
    scsi 3:0:0:0: Direct-Access ATA WDC WD2500JS-60M 10.0 PQ: 0 ANSI: 5
    usbcore: registered new interface driver usbfs
    usbcore: registered new interface driver hub
    usbcore: registered new device driver usb
    ehci_hcd: USB 2.0 'Enhanced' Host Controller (EHCI) Driver
    ehci_hcd 0000:00:13.2: PCI INT A -> GSI 19 (level, low) -> IRQ 19
    ehci_hcd 0000:00:13.2: EHCI Host Controller
    ehci_hcd 0000:00:13.2: new USB bus registered, assigned bus number 1
    ehci_hcd 0000:00:13.2: irq 19, io mem 0xfe02c000
    Driver 'sd' needs updating - please use bus_type methods
    sd 2:0:0:0: [sda] 976773168 512-byte hardware sectors: (500 GB/465 GiB)
    sd 2:0:0:0: [sda] Write Protect is off
    sd 2:0:0:0: [sda] Mode Sense: 00 3a 00 00
    sd 2:0:0:0: [sda] Write cache: enabled, read cache: enabled, doesn't support DPO or FUA
    sd 2:0:0:0: [sda] 976773168 512-byte hardware sectors: (500 GB/465 GiB)
    sd 2:0:0:0: [sda] Write Protect is off
    sd 2:0:0:0: [sda] Mode Sense: 00 3a 00 00
    sd 2:0:0:0: [sda] Write cache: enabled, read cache: enabled, doesn't support DPO or FUA
    sda:<6>ehci_hcd 0000:00:13.2: 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: 8 ports detected
    ohci_hcd: USB 1.1 'Open' Host Controller (OHCI) Driver
    ohci_hcd 0000:00:13.0: PCI INT A -> GSI 19 (level, low) -> IRQ 19
    ohci_hcd 0000:00:13.0: OHCI Host Controller
    ohci_hcd 0000:00:13.0: new USB bus registered, assigned bus number 2
    ohci_hcd 0000:00:13.0: irq 19, io mem 0xfe02e000
    usb usb2: configuration #1 chosen from 1 choice
    hub 2-0:1.0: USB hub found
    hub 2-0:1.0: 4 ports detected
    ohci_hcd 0000:00:13.1: PCI INT A -> GSI 19 (level, low) -> IRQ 19
    ohci_hcd 0000:00:13.1: OHCI Host Controller
    ohci_hcd 0000:00:13.1: new USB bus registered, assigned bus number 3
    ohci_hcd 0000:00:13.1: irq 19, io mem 0xfe02d000
    sda1 sda2 sda3 sda4
    sd 2:0:0:0: [sda] Attached SCSI disk
    sd 3:0:0:0: [sdb] 488397168 512-byte hardware sectors: (250 GB/232 GiB)
    sd 3:0:0:0: [sdb] Write Protect is off
    sd 3:0:0:0: [sdb] Mode Sense: 00 3a 00 00
    sd 3:0:0:0: [sdb] Write cache: enabled, read cache: enabled, doesn't support DPO or FUA
    sd 3:0:0:0: [sdb] 488397168 512-byte hardware sectors: (250 GB/232 GiB)
    sd 3:0:0:0: [sdb] Write Protect is off
    sd 3:0:0:0: [sdb] Mode Sense: 00 3a 00 00
    sd 3:0:0:0: [sdb] Write cache: enabled, read cache: enabled, doesn't support DPO or FUA
    sdb: sdb1
    sd 3:0:0:0: [sdb] Attached SCSI disk
    usb usb3: configuration #1 chosen from 1 choice
    hub 3-0:1.0: USB hub found
    hub 3-0:1.0: 4 ports detected
    EXT3-fs: mounted filesystem with ordered data mode.
    kjournald starting. Commit interval 5 seconds
    usb 1-7: new high speed USB device using ehci_hcd and address 5
    usb 1-7: configuration #1 chosen from 1 choice
    rtc_cmos 00:03: RTC can wake from S4
    rtc_cmos 00:03: rtc core: registered rtc_cmos as rtc0
    rtc0: alarms up to one month, 242 bytes nvram
    usb 2-2: new low speed USB device using ohci_hcd and address 2
    usb 2-2: configuration #1 chosen from 1 choice
    8139too Fast Ethernet driver 0.9.28
    8139too 0000:02:03.0: PCI INT A -> GSI 20 (level, low) -> IRQ 20
    eth0: RealTek RTL8139 at 0xf8182000, 00:13:d3:88:fb:ec, IRQ 20
    eth0: Identified 8139 chip type 'RTL-8100B/8139D'
    lirc_dev: IR Remote Control driver registered, major 61
    lirc_mceusb2: Philips eHome USB IR Transceiver and Microsoft MCE 2005 Remote Control driver for LIRC $Revision: 1.44 $
    lirc_mceusb2: Daniel Melander <[email protected]>, Martin Blatter <[email protected]>
    usbcore: registered new interface driver lirc_mceusb2
    usb 3-1: new full speed USB device using ohci_hcd and address 2
    C-Media PCI 0000:02:01.0: PCI INT A -> GSI 21 (level, low) -> IRQ 21
    usb 3-1: configuration #1 chosen from 1 choice
    input: Power Button (FF) as /class/input/input1
    usb 3-1: reset full speed USB device using ohci_hcd and address 2
    ACPI: Power Button (FF) [PWRF]
    input: Power Button (CM) as /class/input/input2
    ACPI: Power Button (CM) [PWRB]
    processor ACPI_CPU:00: registered as cooling_device0
    ACPI: Processor [CPU0] (supports 8 throttling states)
    processor ACPI_CPU:01: registered as cooling_device1
    ACPI: Processor [CPU1] (supports 8 throttling states)
    lirc_dev: lirc_register_plugin: sample_rate: 0
    lirc_mceusb2[2]: Philips eHome Infrared Transceiver on usb3:2
    usb 3-2: new low speed USB device using ohci_hcd and address 3
    usb 3-2: configuration #1 chosen from 1 choice
    usb 3-4: new full speed USB device using ohci_hcd and address 4
    usb 3-4: configuration #1 chosen from 1 choice
    Linux agpgart interface v0.103
    usbcore: registered new interface driver hiddev
    scsi 1:0:0:0: Attached scsi generic sg0 type 5
    sd 2:0:0:0: Attached scsi generic sg1 type 0
    sd 3:0:0:0: Attached scsi generic sg2 type 0
    input: Logitech HID compliant keyboard as /class/input/input3
    generic-usb 0003:046D:C30E.0001: input,hidraw0: USB HID v1.10 Keyboard [Logitech HID compliant keyboard] on usb-0000:00:13.0-2/input0
    parport_pc 00:07: reported by Plug and Play ACPI
    parport0: PC-style at 0x378, irq 7 [PCSPP,EPP]
    input: Logitech HID compliant keyboard as /class/input/input4
    generic-usb 0003:046D:C30E.0002: input,hidraw1: USB HID v1.10 Device [Logitech HID compliant keyboard] on usb-0000:00:13.0-2/input1
    input: Microsoft Microsoft 5-Button Mouse with IntelliEye(TM) as /class/input/input5
    generic-usb 0003:045E:0047.0003: input,hidraw2: USB HID v1.10 Mouse [Microsoft Microsoft 5-Button Mouse with IntelliEye(TM)] on usb-0000:00:13.1-2/input0
    usbcore: registered new interface driver usbhid
    usbhid: v2.6:USB HID core driver
    nvidia: module license 'NVIDIA' taints kernel.
    piix4_smbus 0000:00:14.0: SMBus Host Controller at 0x500, revision 0
    Driver 'sr' needs updating - please use bus_type methods
    sr0: scsi3-mmc drive: 40x/40x writer cd/rw xa/form2 cdda tray
    Uniform CD-ROM driver Revision: 3.20
    sr 1:0:0:0: Attached scsi CD-ROM sr0
    input: PC Speaker as /class/input/input6
    Initializing USB Mass Storage driver...
    scsi4 : SCSI emulation for USB Mass Storage devices
    usb-storage: device found at 5
    usb-storage: waiting for device to settle before scanning
    scsi5 : SCSI emulation for USB Mass Storage devices
    usbcore: registered new interface driver usb-storage
    USB Mass Storage support registered.
    usb-storage: device found at 4
    usb-storage: waiting for device to settle before scanning
    ohci1394 0000:02:04.0: PCI INT A -> GSI 21 (level, low) -> IRQ 21
    ohci1394: fw-host0: OHCI-1394 1.1 (PCI): IRQ=[21] MMIO=[fdefe000-fdefe7ff] Max Packet=[2048] IR/IT contexts=[4/8]
    Error: Driver 'pcspkr' is already registered, aborting...
    lp0: using parport0 (interrupt-driven).
    ppdev: user-space parallel port driver
    nvidia 0000:01:00.0: PCI INT A -> GSI 18 (level, low) -> IRQ 18
    nvidia 0000:01:00.0: setting latency timer to 64
    NVRM: loading NVIDIA UNIX x86 Kernel Module 180.22 Tue Jan 6 09:29:08 PST 2009
    EXT3 FS on sda2, internal journal
    ReiserFS: sda3: found reiserfs format "3.6" with standard journal
    ReiserFS: sda3: using ordered data mode
    ReiserFS: sda3: journal params: device sda3, size 8192, journal first block 18, max trans len 1024, max batch 900, max commit age 30, max trans age 30
    ReiserFS: sda3: checking transaction log (sda3)
    ReiserFS: sda3: Using r5 hash to sort names
    kjournald starting. Commit interval 5 seconds
    EXT3 FS on sda4, internal journal
    EXT3-fs: mounted filesystem with ordered data mode.
    kjournald starting. Commit interval 5 seconds
    EXT3 FS on sdb1, internal journal
    EXT3-fs: mounted filesystem with ordered data mode.
    ieee1394: Host added: ID:BUS[0-00:1023] GUID[0010dc0000bc42b8]
    eth0: link up, 100Mbps, full-duplex, lpa 0x45E1
    scsi 5:0:0:0: Direct-Access Generic USB SD Reader 1.00 PQ: 0 ANSI: 0
    sd 5:0:0:0: [sdc] Attached SCSI removable disk
    sd 5:0:0:0: Attached scsi generic sg3 type 0
    scsi 5:0:0:1: Direct-Access Generic USB CF Reader 1.01 PQ: 0 ANSI: 0
    scsi 4:0:0:0: Direct-Access ST316002 3A 8.01 PQ: 0 ANSI: 0
    sd 5:0:0:1: [sdd] Attached SCSI removable disk
    sd 5:0:0:1: Attached scsi generic sg4 type 0
    scsi 5:0:0:2: Direct-Access Generic USB SM Reader 1.02 PQ: 0 ANSI: 0
    sd 4:0:0:0: [sde] 312581808 512-byte hardware sectors: (160 GB/149 GiB)
    sd 4:0:0:0: [sde] Write Protect is off
    sd 4:0:0:0: [sde] Mode Sense: 03 00 00 00
    sd 4:0:0:0: [sde] Assuming drive cache: write through
    sd 4:0:0:0: [sde] 312581808 512-byte hardware sectors: (160 GB/149 GiB)
    sd 4:0:0:0: [sde] Write Protect is off
    sd 4:0:0:0: [sde] Mode Sense: 03 00 00 00
    sd 4:0:0:0: [sde] Assuming drive cache: write through
    sde: sde1
    sd 4:0:0:0: [sde] Attached SCSI disk
    sd 4:0:0:0: Attached scsi generic sg5 type 0
    usb-storage: device scan complete
    sd 5:0:0:2: [sdf] Attached SCSI removable disk
    sd 5:0:0:2: Attached scsi generic sg6 type 0
    scsi 5:0:0:3: Direct-Access Generic USB MS Reader 1.03 PQ: 0 ANSI: 0
    sd 5:0:0:3: [sdg] Attached SCSI removable disk
    sd 5:0:0:3: Attached scsi generic sg7 type 0
    usb-storage: device scan complete
    NET: Registered protocol family 10
    lo: Disabled Privacy Extensions
    eth0: no IPv6 routers present
    kjournald starting. Commit interval 5 seconds
    EXT3 FS on sde1, internal journal
    EXT3-fs: mounted filesystem with ordered data mode.
    TCP(wget:15427): Application bug, race in MSG_PEEK.
    TCP(wget:18681): Application bug, race in MSG_PEEK.
    TCP(wget:4122): Application bug, race in MSG_PEEK.
    TCP(wget:4275): Application bug, race in MSG_PEEK.
    TCP(wget:19451): Application bug, race in MSG_PEEK.

  • Hard Drive Won't Mount After Repair by Second Computer

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

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

  • WD External drive won't mount

    Hello everyone! I haven't been here in a while because I just haven't had any Mac issues. Now I do.
    I have a 1 TB WD external HD that won't mount. I connect it via firewire to an Old G4 Sawtooth running OS 10.5.8. My mac sees the drive, it just won't mount. I've also tried to mount it via USB, but again, my system sees the drive, but won't mount it. I inadvertantly disconnected the firewire cable, which I didn't realize for several hours. I reattached the cable, tried to mount it, and nothing. I ran disc repairs, and Disc Utility actually told me the drive was successfully repaired. Again I tried to remount it, but nothing. I repaired permissions, and this didn't work. I've tried different cables, and this doesn't work.
    I don't have another Mac to connect it to, so I don't know if this would work. Here's where things get a little wierd, but interesting. I connected it to my PC laptop, and it mounted. Now, this is a drive that was formatted Mac OS Extended (Journaled) on my G4, so I have to use Mac Drive so my PC will recognize and mount The Drive. So My PC sees The Drive as Mac OS Extended, and mounts it. All files are in tact, and the drive runs normally. This is a music drive and it plays normally on my PC. Meanwhile, if I try connecting it back on My Mac, the name of The Drive randomly changes from 931.5 GB WD to 931.5 GB WD My Media Book. I believe My Media Book is the factory name of The Drive before OS formatting. The Volume name remains the same on my G4 each time I've tried to mount it.
    I do have another identical drive that mounts from all the bus ports on my G4. Any ideas here? Can I get my Drive to begin mounting on my G4 again? Any and all answers are appreciated.

    Terminal List. disk4 is the malfunctioning drive.
    Last login: Mon Feb 25 19:25:12 on ttys000
    raymond-medinas-power-mac-g4-agp-graphics:~ raymondmedina$ diskutil list
    /dev/disk0
       #:                       TYPE NAME                    SIZE       IDENTIFIER
       0:     Apple_partition_scheme                        *111.8 Gi   disk0
       1:        Apple_partition_map                         31.5 Ki    disk0s1
       2:             Apple_Driver43                         28.0 Ki    disk0s2
       3:             Apple_Driver43                         28.0 Ki    disk0s3
       4:           Apple_Driver_ATA                         28.0 Ki    disk0s4
       5:           Apple_Driver_ATA                         28.0 Ki    disk0s5
       6:             Apple_FWDriver                         256.0 Ki   disk0s6
       7:         Apple_Driver_IOKit                         256.0 Ki   disk0s7
       8:              Apple_Patches                         256.0 Ki   disk0s8
       9:                  Apple_HFS Mac Leopard II          91.8 Gi    disk0s10
      10:                  Apple_HFS Mac Tiger               19.7 Gi    disk0s12
    /dev/disk1
       #:                       TYPE NAME                    SIZE       IDENTIFIER
       0:     Apple_partition_scheme                        *186.3 Gi   disk1
       1:        Apple_partition_map                         31.5 Ki    disk1s1
       2:             Apple_Driver43                         28.0 Ki    disk1s2
       3:             Apple_Driver43                         28.0 Ki    disk1s3
       4:           Apple_Driver_ATA                         28.0 Ki    disk1s4
       5:           Apple_Driver_ATA                         28.0 Ki    disk1s5
       6:             Apple_FWDriver                         256.0 Ki   disk1s6
       7:         Apple_Driver_IOKit                         256.0 Ki   disk1s7
       8:              Apple_Patches                         256.0 Ki   disk1s8
       9:                  Apple_HFS Mac Leopard I           186.2 Gi   disk1s10
    /dev/disk2
       #:                       TYPE NAME                    SIZE       IDENTIFIER
       0:     Apple_partition_scheme                        *465.8 Gi   disk2
       1:        Apple_partition_map                         31.5 Ki    disk2s1
       2:             Apple_Driver43                         28.0 Ki    disk2s2
       3:             Apple_Driver43                         28.0 Ki    disk2s3
       4:           Apple_Driver_ATA                         28.0 Ki    disk2s4
       5:           Apple_Driver_ATA                         28.0 Ki    disk2s5
       6:             Apple_FWDriver                         256.0 Ki   disk2s6
       7:         Apple_Driver_IOKit                         256.0 Ki   disk2s7
       8:              Apple_Patches                         256.0 Ki   disk2s8
       9:                  Apple_HFS 500 GB HD               465.6 Gi   disk2s10
    /dev/disk3
       #:                       TYPE NAME                    SIZE       IDENTIFIER
       0:     Apple_partition_scheme                        *931.5 Gi   disk3
       1:        Apple_partition_map                         31.5 Ki    disk3s1
       2:             Apple_Driver43                         28.0 Ki    disk3s2
       3:             Apple_Driver43                         28.0 Ki    disk3s3
       4:           Apple_Driver_ATA                         28.0 Ki    disk3s4
       5:           Apple_Driver_ATA                         28.0 Ki    disk3s5
       6:             Apple_FWDriver                         256.0 Ki   disk3s6
       7:         Apple_Driver_IOKit                         256.0 Ki   disk3s7
       8:              Apple_Patches                         256.0 Ki   disk3s8
       9:                  Apple_HFS 1 TB Music Drive II     931.4 Gi   disk3s10
    /dev/disk4
       #:                       TYPE NAME                    SIZE       IDENTIFIER
       0:     Apple_partition_scheme                        *931.5 Gi   disk4
       1:        Apple_partition_map                         31.5 Ki    disk4s1
       2:             Apple_Driver43                         28.0 Ki    disk4s2
       3:             Apple_Driver43                         28.0 Ki    disk4s3
       4:           Apple_Driver_ATA                         28.0 Ki    disk4s4
       5:           Apple_Driver_ATA                         28.0 Ki    disk4s5
       6:             Apple_FWDriver                         256.0 Ki   disk4s6
       7:         Apple_Driver_IOKit                         256.0 Ki   disk4s7
       8:              Apple_Patches                         256.0 Ki   disk4s8
       9:                  Apple_HFS 1TB Music Drive         931.4 Gi   disk4s10
    raymond-medinas-power-mac-g4-agp-graphics:~ raymondmedina$
    Terminal info on disk4s10.
    Last login: Mon Feb 25 22:22:41 on ttys000
    raymond-medinas-power-mac-g4-agp-graphics:~ raymondmedina$ diskutil info disk4s10
       Device Identifier:        disk4s10
       Device Node:              /dev/disk4s10
       Part Of Whole:            disk4
       Device / Media Name:      Apple_HFS_Untitled_1
       Volume Name:              1TB Music Drive
       Mount Point:             
       File System:              Journaled HFS+
       Owners:                   Disabled
       Partition Type:           Apple_HFS
       Bootable:                 Is bootable
       Media Type:               Generic
       Protocol:                 FireWire
       SMART Status:             Not Supported
       Volume UUID:              61A8EAFF-E1C9-3605-AF92-5A210E3C781A
       Total Size:               931.4 Gi (1000069726208 B) (1953261184 512-byte blocks)
       Free Space:               0.0 B (0 B) (0 512-byte blocks)
       Read Only:                No
       Ejectable:                Yes
       Whole:                    No
       Internal:                 No
    Disk Utility Info on 1TB Music Drive.
    Name :
    1TB Music Drive
    Type :
    Volume
    Disk Identifier :
    disk4s10
    Mount Point :
    Not mounted
    File System :
    Mac OS Extended (Journaled)
    Connection Bus :
    FireWire
    Device Tree :
    IODeviceTree:fwx/node@90a9c5c29aa50b/sbp-2@c000
    Writable :
    Yes
    Universal Unique Identifier :
    61A8EAFF-E1C9-3605-AF92-5A210E3C781A
    Capacity :
    931.4 GB (1,000,069,726,208 Bytes)
    Owners Enabled :
    No
    Can Turn Owners Off :
    Yes
    Can Be Formatted :
    Yes
    Bootable :
    Yes
    Supports Journaling :
    Yes
    Journaled :
    No
    Disk Number :
    4
    Partition Number :
    10
    I've read that WD uses crappy chipsets in their external drives. I'm wondering if the chipset is suspect here? Just not sure. I did discover that I can clone the drive from my PC as an exact Mac OS Extended (Journaled) drive, and my Mac doesn't even know the difference. I've also read that I can initialize the drive, and reinsert the drivers, and the drive should function normally. Interesting, huh? Well, let me know what you come up with BDAqua. And again, many, many thanks.

  • External HD won't mount, lots of errors

    I bought a 250GB Maxtor internal harddrive and installed it inside a no-name external enclosure. It's connected through USB2. When I connect it, I get a pop-up that says "disk not recognized" with options to initialize, ignore, or eject. I went into Disk Utility and partitioned the disk...still won't mount. I then reinstalled the 10.4.3 combo updater...still no luck. When I try to repair the disk through Disk Utilities it says:
    "Verify and Repair disk “disk1s3”
    Volume check failed.
    Error: The underlying task reported failure on exit
    1 HFS volume checked
    1 volume could not be repaired because of an error
    What can I do to get this hard drive to mount and work?

    Put it into a FireWire enclosure. USB is basically useless; normally unbootable. You can get a decent FW/USB combo enclosure for under $50. I like this one (I have two): http://www.pcmicrostore.com/PartDetail.aspx?q=p:10500933 ($38 US + S&H).
    Note: I have no financial interest with this seller or product.

Maybe you are looking for