Boot Failure with HP HDD

I have an old Vectra VL420 mini tower which I've used to install 3 different operating systems on 5 different IDE Ultra ATA hard drives from different manufacturers.  The drives range in size from 40G to 200G.
I have a second, socket 370, system which I built myself using an ASUS TUV4X motherboard.  I have used this system to install two different operating systems, each on its own drive.
Both systems run without issue, but here's the rub:
1)  I can boot my Vectra with the drives from my home-built system, but...
2)  I cannot boot the home-built system with any one of the Windows (Win 2k Pro and XP home) drives from the Vectra, nor can I slave any one of the Vectra's Windows drives to it.
3)  I have one drive with an old Red Hat OS that will boot either system.
4)  The home-built will not boot if I swap its optical drive with one from the Vectra.
When I try to boot the home-built with the Vectra loaded Windows drives the sequence of events is always the same:
1) Power on...
2) Fans come on and drives start to spin up.  This last for about 2 or 3 seconds before...
3) The system shuts itself off (power off).  It doesn't even stay up long enough for a BIOS screen to appear.
This also happens when I swap the optical drive with the Vectra's.
I get the impression that the motherboard takes one quick look at the hardware, doesn't like what it sees, and shuts down.
I've spent a lot of time with the TUV4X owner's manual trying to see if there was some parameter in the BIOS or some switch/jumper on the motherboard that would solve this issue.  I'm reasonably certain this is a dead end.
I'm beginning to think that there's something peculiar about the way HP formats drives.  Perhaps it even modifies the firmware on them.
Any ideas?
Thanks in advance,
Pat

Hi dragnoak,
I'm talking about the USB cable that came with my Navigon 72 Plus. I bought this GPS navigator 2 years ago, which means that I used the cable 8 times (I update the maps 4 times/year), always on my X220t.
I plugged it into the A520's USB 3 port for the first time last week. You know what happened.
I said that the cable has been "destroyed" because I don't know the right English word, but you should understand what that means: the cable stopped working during the first half hour. After that I tried to connect my GPS to the X220t, but to no avail.
Same thing happened to my "pass-through" e-cigarette (it is equipped with a micro-USB port at the bottom). After a few hours the red LED next to the port turned off and the battery stopped charging. I had to order a new cable.
Neither the GPS nor the e-cigarette were damaged, only the cables. Strange things happen sometimes...
I have no doubt that your USB 3 ports work like a charm. Mine don't, since day 1. My external USB 3 compatible HDD is plugged into a USB 2 port, otherwise I can't save anything onto it (just read). In short, I have two useless USB 3 ports. I am not complaining, just talking about a fact.
@TLC2013,
I apologize for using your topic to report my own issues...
X220t | i7 | 320GB HDD | 8GB RAM | WIN7 PRO
IdeaCenter A520 | i5 | 1 TB HDD | 6GB RAM | WIN8.1

Similar Messages

  • Error in boot-uponly with win98 HDD installed

      Gents:
         Desire to report a bug in arch 0.5 downloaded Oct 18, 2003.
         Utilized arch 0.5 for some time but after installing arch linux, slackwareeline 9.0 and slackware linux 9.1 along with windows 98 in my system I encountered inability to load arch 0.5 until win98 HDD was removed. 
        Initial  setup of the system operated correctly, each linux OS capable of mounting partitions of the other, whether it was arch to slackware or the reverse.  This capability was in addition to accessing vfat on two HDD having fat file systems(one is a USB device the other the secondary slave.  However, upon reboot, an fsck fail occurred asking  for:     " mount -n -o remount, rw/" .  This notation appears in :  man fsck....
         I wish to pursue a bug description since this indicates a cross OS fault with win98 file systems/HDD.
        The boot is selected in bios before initiating same.
         How do I submit a bug?

      Sorry I must be more careful in describing the complex problem.
         I utilize a pciide card to extend hdd capability,
         I change boot-up HDD in bios for four mobo HDD as is standard.
         I cannot boot on pciide card hdd's.
         I have win98 on sec-slave, with no other OS partitioned.
        I have slackware 9.0 attached to pciide slot sec-master with no partitions to other OS's.
         I have slackware 9.1 attached to pri-master when used as the in-use HDD.  It has access to partitions on arch, win98, and slckware 9.0.
         I can install arch in pri-slave when using slackware as OS.
         I can install arch as OS and slackware 9.0 as pri-slave and have access to partitions on all other HDD.
         I also have a USB HDD which is accessible from the OS in all cases.
        The problem in arch 0.5 is that after setting up the accessibilities in Linux and win98 HDD's, at next reboot I could not pass fsck.  This condition persisted until I removed the win98HDD which cleared the problem.
         In win98, the OS does not recognize any Linux HDD's.
         In arch0.5, the presence of win98 HDD prevents  arch 0.5 from booting.
         I read ....."man fsck"... and it refers to drives as  "/dev/hda...etc" and this type of ID does not apply to kernel 2.4.21 which uses /dev/discs/discX/partx and therefore I feel therein lies a bug.  This seems to be true since I am booting kernel 2.4.21 in arch0.5 which ID's hdd's in a mode other than specified in fsck.
        If fsck "sees" the win98HDD through the /dev/hdx search(supposedly a multiple parallel hdd check) it most certainly will fail the arch0.5 boot-up AFAICT.
         Perhaps I have improved your understanding of my problem..I use lilo for booting and have ....append="hde=ide-scsi ide=reverse" to allow for pciide ID after mobo ID and to enable cdrw in pcide slot primary-pri.
         If further info needed, I am ready to try.

  • Boot issue with External HDD since OSX 10.10

    Hi
    Wanted to share my experience and I hope someone can help me here. I have a 2TB USB3.0 LaCie Minimus HDD that worked just fine on OSX 10.9 and even Windows 8.1. However since Yosemite (10.10) every single Mac (MacPro, MacBookPro) that I plug the HDD to will not longer boot-up normally (cold boot) IF the HDD is turned on. Power off the HDD every Mac on 10.10 will boot normally. However reboot and wake-up from sleep work fine.
    To make sure I explained my self correctly.
    Power off your mac on OSX 10.9, have the 2TB USB3.0 LaCie Minimus HDD (powered on) connected to your Mac. then power it on back and no problems.
    Power off your PC with Win 8.1, have the 2TB USB3.0 LaCie Minimus HDD (powered on) connected to your PC. then power it on back and no problems.
    Power off your mac on OSX 10.10, have the 2TB USB3.0 LaCie Minimus HDD (powered on) connected to your Mac. then power it on back and the Mac boot will be stuck until your power off the 2TB USB3.0 LaCie Minimus HDD.
    Also note that Rebbot and wake from sleep work just fine in every situation and OSs. I reseted the PRAM, SMC, and tested the HDD on a Fresh 10.10 install as well as on a 10.10 upgrade and a Old 10.9.X MacBookPro.
    To make sure it was not a partition problem I formatted the drive and removed all partitions (EFI) several times on each OSs... Same result.
    Finally I contacted LaCie and I am waiting for their feedback.
    Message was edited by: Akiba-Seattle

    Here you are!
    PS Thanks for helping. In My case it was disk2
    XXXs-Mac-Pro:~ XXX$ diskutil info -plist disk0
    <?xml version="1.0" encoding="UTF-8"?>
    <!DOCTYPE plist PUBLIC "-//Apple//DTD PLIST 1.0//EN" "http://www.apple.com/DTDs/PropertyList-1.0.dtd">
    <plist version="1.0">
    <dict>
      <key>Bootable</key>
      <false/>
      <key>BusProtocol</key>
      <string>PCI</string>
      <key>CanBeMadeBootable</key>
      <false/>
      <key>CanBeMadeBootableRequiresDestroy</key>
      <false/>
      <key>Content</key>
      <string>GUID_partition_scheme</string>
      <key>DeviceBlockSize</key>
      <integer>512</integer>
      <key>DeviceIdentifier</key>
      <string>disk0</string>
      <key>DeviceNode</key>
      <string>/dev/disk0</string>
      <key>DeviceTreePath</key>
      <string>IODeviceTree:/PCI0@0/RP05@1C,4/SSD0@0/PRT0@0/PMP@0</string>
      <key>Ejectable</key>
      <false/>
      <key>FreeSpace</key>
      <integer>0</integer>
      <key>GlobalPermissionsEnabled</key>
      <false/>
      <key>IOKitSize</key>
      <integer>251000193024</integer>
      <key>Internal</key>
      <true/>
      <key>LowLevelFormatSupported</key>
      <false/>
      <key>MediaName</key>
      <string>APPLE SSD SM0256F Media</string>
      <key>MediaType</key>
      <string>Generic</string>
      <key>MountPoint</key>
      <string></string>
      <key>OS9DriversInstalled</key>
      <false/>
      <key>ParentWholeDisk</key>
      <string>disk0</string>
      <key>RAIDMaster</key>
      <false/>
      <key>RAIDSlice</key>
      <false/>
      <key>SMARTStatus</key>
      <string>Verified</string>
      <key>SolidState</key>
      <true/>
      <key>SupportsGlobalPermissionsDisable</key>
      <false/>
      <key>SystemImage</key>
      <false/>
      <key>TotalSize</key>
      <integer>251000193024</integer>
      <key>VolumeName</key>
      <string></string>
      <key>WholeDisk</key>
      <true/>
      <key>Writable</key>
      <true/>
      <key>WritableMedia</key>
      <true/>
      <key>WritableVolume</key>
      <false/>
    </dict>
    </plist>
    XXXs-Mac-Pro:~ XXX$ diskutil info -plist disk2
    <?xml version="1.0" encoding="UTF-8"?>
    <!DOCTYPE plist PUBLIC "-//Apple//DTD PLIST 1.0//EN" "http://www.apple.com/DTDs/PropertyList-1.0.dtd">
    <plist version="1.0">
    <dict>
      <key>Bootable</key>
      <false/>
      <key>BusProtocol</key>
      <string>USB</string>
      <key>CanBeMadeBootable</key>
      <false/>
      <key>CanBeMadeBootableRequiresDestroy</key>
      <false/>
      <key>Content</key>
      <string>GUID_partition_scheme</string>
      <key>DeviceBlockSize</key>
      <integer>512</integer>
      <key>DeviceIdentifier</key>
      <string>disk2</string>
      <key>DeviceNode</key>
      <string>/dev/disk2</string>
      <key>DeviceTreePath</key>
      <string>IODeviceTree:/PCI0@0/PEG0@1/BR00@0/BR13@1/XHC1@0</string>
      <key>Ejectable</key>
      <true/>
      <key>FreeSpace</key>
      <integer>0</integer>
      <key>GlobalPermissionsEnabled</key>
      <false/>
      <key>IOKitSize</key>
      <integer>2000398934016</integer>
      <key>Internal</key>
      <false/>
      <key>LowLevelFormatSupported</key>
      <false/>
      <key>MediaName</key>
      <string>ST2000DM 001-1ER164 Media</string>
      <key>MediaType</key>
      <string>Generic</string>
      <key>MountPoint</key>
      <string></string>
      <key>OS9DriversInstalled</key>
      <false/>
      <key>ParentWholeDisk</key>
      <string>disk2</string>
      <key>RAIDMaster</key>
      <false/>
      <key>RAIDSlice</key>
      <false/>
      <key>SMARTStatus</key>
      <string>Not Supported</string>
      <key>SupportsGlobalPermissionsDisable</key>
      <false/>
      <key>SystemImage</key>
      <false/>
      <key>TotalSize</key>
      <integer>2000398934016</integer>
      <key>VolumeName</key>
      <string></string>
      <key>WholeDisk</key>
      <true/>
      <key>Writable</key>
      <true/>
      <key>WritableMedia</key>
      <true/>
      <key>WritableVolume</key>
      <false/>
    </dict>
    </plist>
    XXXs-Mac-Pro:~ XXX$ diskutil cs list
    No CoreStorage logical volume groups found
    XXXs-Mac-Pro:~ XXX$
    XXXs-Mac-Pro:~ XXX$ sudo gpt -vv -r show /dev/disk0
    Password:
    gpt show: /dev/disk0: mediasize=251000193024; sectorsize=512; blocks=490234752
    gpt show: /dev/disk0: PMBR at sector 0
    gpt show: /dev/disk0: Pri GPT at sector 1
    gpt show: /dev/disk0: Sec GPT at sector 490234751
          start       size  index  contents
              0          1         PMBR
              1          1         Pri GPT header
              2         32         Pri GPT table
             34          6        
             40     409600      1  GPT part - C12A7328-F81F-11D2-BA4B-00A0C93EC93B
         409640  488555536      2  GPT part - 48465300-0000-11AA-AA11-00306543ECAC
      488965176    1269536      3  GPT part - 426F6F74-0000-11AA-AA11-00306543ECAC
      490234712          7        
      490234719         32         Sec GPT table
      490234751          1         Sec GPT header
    XXXs-Mac-Pro:~ XXX$
    XXXs-Mac-Pro:~ XXX$ sudo gpt -vv -r show /dev/disk2
    gpt show: /dev/disk2: mediasize=2000398934016; sectorsize=512; blocks=3907029168
    gpt show: /dev/disk2: PMBR at sector 0
    gpt show: /dev/disk2: Pri GPT at sector 1
    gpt show: /dev/disk2: Sec GPT at sector 3907029167
           start        size  index  contents
               0           1         PMBR
               1           1         Pri GPT header
               2          32         Pri GPT table
              34           6        
              40      409600      1  GPT part - C12A7328-F81F-11D2-BA4B-00A0C93EC93B
          409640  3906357344      2  GPT part - 48465300-0000-11AA-AA11-00306543ECAC
      3906766984      262151        
      3907029135          32         Sec GPT table
      3907029167           1         Sec GPT header

  • W530 Boot Failure with out any BSOD

    I bought my thinkpad w530 in Oct. 2012. It works perfect until recent month.
    At the beginning, it can't wake up in the sleep mode. If I connect the AC power, it reset the BIOS time.
    And nowadays, when i power off this laptop, it can't boot. And I remove and setup the battery, It restored. But if I first connect the ac power/dock, and remove-setup the battery, the BIOS time is reseted.
    I updated all my drivers. The failure is still here. I wonder if oneday it died forever?
    Thinkpad W530 2lu, 32G DDR 3 Kinston, 500G HDD. K2000m

    Can you try resetting your BIOS settings to defaults?
    It's also possible that your CMOS battery is depleted, in which case you would have to replace it.
    W520: i7-2720QM, Q2000M at 1080/688/1376, 21GB RAM, 500GB + 750GB HDD, FHD screen
    X61T: L7500, 3GB RAM, 500GB HDD, XGA screen, Ultrabase
    Y3P: 5Y70, 8GB RAM, 256GB SSD, QHD+ screen

  • Windows XP system boot failure with \Boot\BCD status 0xc000000f

    I have a ThinkCenter M52 purchased secondhand from my employer. It was originally loaded with Vista but was upgraded to Windows XP before I got it. (The recovery partition on the HDD is still Vista.) For the 15 months since I bought I have had no problems. I had to reboot earlier this week because of a software upgrade and now I get:
    File: \Boot\BCD
    Status 0xc000000f
    An error occurred while attempting to read the boot configuration data
    From Google searches this is a Vista error, somehow the XP configuration has been lost. I have tried using a partition manager, BOOTCFG from an XP install disc, BartPE. I have run out of ideas, how do I fix this?

    Did you check your HDD for errors?Try using Lenovo's hard drive quick test
    http://www-307.ibm.com/pc/support/site.wss/MIGr-70578.html#boot
    Cheers and regards,
    • » νιנαｿѕαяα∂нι ѕαмανє∂αм ™ « •
    ●๋•کáŕádhí'ک díáŕý ツ
    I am a volunteer here. I don't work for Lenovo

  • Msi Z87-GD65 Booting Failure With eSATA Drives

    Hi Folks,
    Before I go down the (probably ill-fated) Customer Service path I thought I'd address the forum here on a little problem I'm having with my Z87-GD65.
    IN essence, if I have a hard drive connected to my eSATA port the PC won't boot.  I'm using an ICYDOCK 4 bay external enclosure (MB561US-4SB if interested).  If the drive itself is on but the HD trays are ejected then it boots.  If any of the drives are secured then it'll hang at a post-BIOS/pre-Windows screen where all I get is a blinking cursor for about 30 seconds and then it disappears to a plain black screen.  If the device is powered off then it boots.
    I've checked the BIOS with one of the HDs running and it doesn't appear within my boot list - in fact, except for one selection in the bios allowing me to disable eSATA there really isn't much I can do there.
    I've upgraded my BIOS to 1.30 from 1.00 and the process seems to move a bit further - now I get the oh-so-pretty ugly Windows logo and that's all.
    When I do actually boot the PC with the ICYDOCK off then I'm able to get into Windows normally, and turn on the ICYDOCK.  After a few seconds all 4 hard drives report in and everything's fine.
    I've been using this ICYDOCK for about  a year and a half, with 2 other motherboards (neither were an MSI) and i7 cores, and neither of them caused me any issues.  I remember that neither of those boards had the port multiplier eSATA capability so I had to buy a controller card with that capability.  I could probably dig that up and see if the problem remains.
    In case you're wondering, if it helps, I built a Msi Z87-GD65/4770 i7 - based PC with 2 internal 2TB Hard Drives, and 16gb RAM.  I already mentioned the ICYDOCK.  I used LiveUpdate to install all the latest drivers & BIOS before uninstalling it.
    I build & repair PCs for a living so I'm pretty familiar with what's going on with the system.  I figure that there must be something happening between the BIOS and Windows "handoff" of the ICYDOCK, but I'm damned if I can figure out just what.

    More information please. PSU, OS being used, etc..
    Live Update is best uninstalled. Flash UEFI/BIOS the safer way;
    https://forum-en.msi.com/index.php?topic=169827.0
    Recommend to download drivers and utilities from the MSI Websites and install manually.
      >> Posting Guide <<

  • No longer able to boot - failure with /boot

    I recently, due to a hard drive change, rebuilt my desktop.  Every now and again, since then, it hasn't booted.  I just logged into root and rebooted; figuring I'd sort it out at some point.
    Only, now it won't boot at all.  When I go through journalctl -xb I get the following errors (the ellipsis, in case it isn't clear, indicate an number of lines with no error in between the error messages):
    Job dev-sda2.device/start timed out.
    Timed out waiting for device dev-sda2.device.
    Dependency failed for /boot.
    Dependency failed for Local File Systems.
    Triggering OnFailure= dependencies of local-fs.target.
    Dependency failed for File System Check on /dev/sda2
    and also, much later in the logs:
    Failed at step EXEC spawning /bin/plymouth: No such file or directory
    My initial assumption would have been that the relevant drive is failing, but I only recently ran a check on the drives (a few days ago and since the rebuild) and all was fine and dandy - but I had already been seeing these errors on a periodic basis.  Only now, as I said, they happen at every boot and I never get as far as login.
    Thanks in advance for any help.

    I ran the extended smartmontools test on the disk today and it returned with no errors.  However, the error log for the disk did contain the following:
    Complete error log:
    SMART Error Log Version: 1
    Warning: ATA error count 21 inconsistent with error log pointer 5
    ATA Error Count: 21 (device log contains only the most recent five errors)
    CR = Command Register [HEX]
    FR = Features Register [HEX]
    SC = Sector Count Register [HEX]
    SN = Sector Number Register [HEX]
    CL = Cylinder Low Register [HEX]
    CH = Cylinder High Register [HEX]
    DH = Device/Head Register [HEX]
    DC = Device Command Register [HEX]
    ER = Error register [HEX]
    ST = Status register [HEX]
    Powered_Up_Time is measured from power on, and printed as
    DDd+hh:mm:SS.sss where DD=days, hh=hours, mm=minutes,
    SS=sec, and sss=millisec. It "wraps" after 49.710 days.
    Error 21 occurred at disk power-on lifetime: 10341 hours (430 days + 21 hours)
    When the command that caused the error occurred, the device was in an unknown state.
    After command completion occurred, registers were:
    ER ST SC SN CL CH DH
    84 51 00 00 00 00 e0 Error: ICRC, ABRT at LBA = 0x00000000 = 0
    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 08 00 00 00 e0 08 01:12:12.224 READ DMA
    27 00 00 00 00 00 e0 08 01:12:12.224 READ NATIVE MAX ADDRESS EXT [OBS-ACS-3]
    ec 00 00 00 00 00 a0 0a 01:12:12.224 IDENTIFY DEVICE
    ef 03 45 00 00 00 a0 0a 01:12:12.224 SET FEATURES [Set transfer mode]
    27 00 00 00 00 00 e0 08 01:12:12.224 READ NATIVE MAX ADDRESS EXT [OBS-ACS-3]
    Error 20 occurred at disk power-on lifetime: 10341 hours (430 days + 21 hours)
    When the command that caused the error occurred, the device was in an unknown state.
    After command completion occurred, registers were:
    ER ST SC SN CL CH DH
    84 51 00 00 00 00 e0 Error: ICRC, ABRT at LBA = 0x00000000 = 0
    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 08 00 00 00 e0 08 01:11:26.048 READ DMA
    27 00 00 00 00 00 e0 08 01:11:26.048 READ NATIVE MAX ADDRESS EXT [OBS-ACS-3]
    ec 00 00 00 00 00 a0 0a 01:11:26.048 IDENTIFY DEVICE
    ef 03 46 00 00 00 a0 0a 01:11:26.048 SET FEATURES [Set transfer mode]
    27 00 00 00 00 00 e0 08 01:11:26.048 READ NATIVE MAX ADDRESS EXT [OBS-ACS-3]
    Error 19 occurred at disk power-on lifetime: 10341 hours (430 days + 21 hours)
    When the command that caused the error occurred, the device was in an unknown state.
    After command completion occurred, registers were:
    ER ST SC SN CL CH DH
    84 51 00 00 00 00 e0 Error: ICRC, ABRT at LBA = 0x00000000 = 0
    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 08 00 00 00 e0 08 01:10:16.816 READ DMA
    27 00 00 00 00 00 e0 08 01:08:51.584 READ NATIVE MAX ADDRESS EXT [OBS-ACS-3]
    ec 00 00 00 00 00 a0 0a 01:08:51.584 IDENTIFY DEVICE
    ef 03 46 00 00 00 a0 0a 01:08:51.584 SET FEATURES [Set transfer mode]
    27 00 00 00 00 00 e0 08 01:08:51.568 READ NATIVE MAX ADDRESS EXT [OBS-ACS-3]
    Error 18 occurred at disk power-on lifetime: 10340 hours (430 days + 20 hours)
    When the command that caused the error occurred, the device was in an unknown state.
    After command completion occurred, registers were:
    ER ST SC SN CL CH DH
    84 51 00 00 00 00 e0 Error: ICRC, ABRT at LBA = 0x00000000 = 0
    Commands leading to the command that caused the error were:
    CR FR SC SN CL CH DH DC Powered_Up_Time Command/Feature_Name
    25 00 01 00 00 00 e0 08 00:04:28.384 READ DMA EXT
    c6 00 10 00 00 00 e0 08 00:04:28.384 SET MULTIPLE MODE
    91 00 3f 00 00 00 a0 08 00:04:28.384 INITIALIZE DEVICE PARAMETERS [OBS-6]
    10 00 00 00 00 00 a0 08 00:04:28.352 RECALIBRATE [OBS-4]
    25 00 01 00 00 00 e0 04 00:04:28.352 READ DMA EXT
    Error 17 occurred at disk power-on lifetime: 10340 hours (430 days + 20 hours)
    When the command that caused the error occurred, the device was in an unknown state.
    After command completion occurred, registers were:
    ER ST SC SN CL CH DH
    84 51 00 00 00 00 e0 Error: ICRC, ABRT at LBA = 0x00000000 = 0
    Commands leading to the command that caused the error were:
    CR FR SC SN CL CH DH DC Powered_Up_Time Command/Feature_Name
    25 00 01 00 00 00 e0 08 00:04:28.288 READ DMA EXT
    c6 00 10 00 00 00 e0 08 00:04:28.288 SET MULTIPLE MODE
    91 00 3f 00 00 00 a0 08 00:04:28.288 INITIALIZE DEVICE PARAMETERS [OBS-6]
    10 00 00 00 00 00 a0 08 00:04:28.272 RECALIBRATE [OBS-4]
    25 00 01 00 00 00 e0 04 00:04:28.272 READ DMA EXT
    Does this mean my disk is dying?  That would be very annoying after just rebuilding from another failed disk!

  • Boot failure with AMD core unlock *solved*

    Before you criticize me for buying a triple core instead of a quad core, I want you to know that my situation seems to only conflict with Arch.
    I have an AMD Athlon II x3.  If I unlock the 4th core, Linux live CDs boot up just fine, Windows XP boots fine, Windows 7 boots fine, and as long as any OS completely boots up it runs flawlessly for hours with constant load.  However, Arch will fail to boot IMMEDIATELY after unlocking cores. IIRC, the Arch setup CD also fails to boot.  I have a small feeling that GRUB has something to do with it, but whenever I attempt to install GRUB2 I'm never able to boot again.
    As another note, I can't seem to get IOMMU to work with Arch.  With Debian based distros it works immediately, but I can't find anything on how to enable it with Arch.  I get this impression that there's a lot of missing Kernel entries in Arch which are causing these CPU problems, and possibly others.
    Last edited by schmidtbag (2011-09-27 16:16:30)

    schmidtbag wrote:
    R00KIE wrote:Not much of an idea then, get /proc/config.gz from the distros that work and the one from arch, compare them and see if you can spot what might be causing the problem. No other ideas here.
    debian doesn't have that file, did you mistake it for something different?
    I know some distros don't have it but I wasn't aware debian is one of them (I use arch everyday and I try to manage a few centos boxes and that's all), that is an option can be enabled/disabled when building the kernel and it can be quite useful when trying to figure out why something doesn't work (such as seeing which drivers were built and which option was selected when there are multiple choices), however I guess it might have security implications since anyone can find out which options were selected when building the running kernel and some combinations may have yet uncovered/unpublished/undisclosed security exploits.

  • Am I able to install Windows 7 in Boot Camp with this HDD partition setup?

    I recently upgraded from Snow Leopard to Lion, and my Boot Camp partition was obliterated beyond recognition. Fortunately I have backups, but I'm having issues re-installing Windows 7. This is what my disk looks like:
    Mac OSX - Current Lion partition
    Untitled - Where Boot Camp / Windows 7 used to live...
    Shared - 1TB of shared data... Media/Documents/etc
    This is the error I get when trying to install Windows 7 with Boot Camp Assistant...
    From what I can tell, this means I won't be able to do it without wiping the Shared partition? Or is there a workaround I can use? I'd really hate to have to move all of it over to an external hard drive, since I don't have one with 750GB of free space handy...
    And would this probably happen again once Mountain Lion comes out? I'll be getting that pretty much on launch, so should I hold off on messing around with this if I'll likely have to do it all again in a few weeks?
    Thanks in advance to anyone who can help!
    - Mark

    Why don't you invest in a 1.5TB drive and case? And add to that a TimeMachine drive (and a small 40GB or even less "Emergency OS X" partition on it... a must - could even have clone of Lion and Lion Recovery on it, AND  TimeMachine partition.
    If you don't have a backup, it almost always will "rain" on the parade.
    If you try booting from Windows 7 DVD and aim it at the parittion, what happens? tried?
    To use BCA yes it is one partition and one way only.
    You could remove " - " the UNTITLED volume and then expand Mac OS volume to fill that area, or plan for and setup Lion Recovery space too.
    http://support.apple.com/kb/HT4718
    People have managed. Usually planning ahead up front for a setup like this.
    CLONE OS X and ~ or install Lion on an external drive and create a Lion Recovery partition.
    http://www.bombich.com/software/ccc.html
    http://macperformanceguide.com/Mac-HowToClone-backup.html
    http://macperformanceguide.com/Mac-HowToClone.html

  • T530 with N-6300 boot failure 1802

    Hi,
    I got a nice T530 with built in 6205 Wireless LAN. As I tried to replace with N-6300 there comes the Hardware boot failure with error 1802 (incompatible PCI device). I just wonder as the N-6300 is in the compatibility list and the third antenna was also already built in. Is there any workaround to get this running?
    regards
    Solved!
    Go to Solution.

    I picked up the N6300 with FRU 60Y3233 from http://www.ebay.ca/itm/1pc-Ultimate-N-6300-633ANHM​W-FRU-60Y3233-Wireless-Card-for-IBM-Thinkpad-Intel​...
    The card works flawlessly out of the box and utilizes all 3 antennae.
    Just in case someone was looking for an answer here.

  • System boot failure after upgrade from linux3.13.8-1 to linux3.14.6-1

    I have tried to update the kernel again from 3.13 to 3.14 again, but no luck.
    My arch system boot failure with black screen, tried [ctrl]+[alt]+[F1-6] and nothing happen, no any recure shell prompt out.
    Then I boot with kernel debug parameters
    systemd.log_level=debug systemd.log_target=kmsg log_buf_len=1M
    althrough the screen was black, when I reboot and chroot into my system,
    I entered the following to find any error messages, please see the link below:
    journalctl -b -0 >> ~/3.13_no_problem.log
    journalctl -b -1 >> ~/3.14-6_nodebug.log
    journalctl -b -2 >> ~/3.14-6_debug.log
    3.13_no_problem.log: http://pastebin.com/EQ2Mucq8
    3.14-6_nodebug.log: http://pastebin.com/18TRZVRp
    3.14-6_debug.log: http://pastebin.com/0QZJBPnf
    In both 3.14 journal messages, I found some similar error message:
    Jun 15 14:37:47 arch-desktop kernel: [drm:atom_op_jump] *ERROR* atombios stuck in loop for more than 5secs aborting
    Jun 15 14:37:47 arch-desktop kernel: [drm:atom_execute_table_locked] *ERROR* atombios stuck executing D218 (len 62, WS 0, PS 0) @ 0xD234
    Jun 15 14:37:55 arch-desktop kernel: [drm:atom_op_jump] *ERROR* atombios stuck in loop for more than 5secs aborting
    Jun 15 14:37:55 arch-desktop kernel: [drm:atom_execute_table_locked] *ERROR* atombios stuck executing D218 (len 62, WS 0, PS 0) @ 0xD234
    Jun 15 14:38:00 arch-desktop kernel: [drm:cypress_dpm_set_power_state] *ERROR* rv770_restrict_performance_levels_before_switch failed
    Jun 15 14:38:01 arch-desktop kernel: [drm:atom_op_jump] *ERROR* atombios stuck in loop for more than 5secs aborting
    Jun 15 14:38:01 arch-desktop kernel: [drm:atom_execute_table_locked] *ERROR* atombios stuck executing D218 (len 62, WS 0, PS 0) @ 0xD234
    Jun 15 14:38:07 arch-desktop kernel: [drm:atom_op_jump] *ERROR* atombios stuck in loop for more than 5secs aborting
    Jun 15 14:38:07 arch-desktop kernel: [drm:atom_execute_table_locked] *ERROR* atombios stuck executing D218 (len 62, WS 0, PS 0) @ 0xD234
    Jun 15 14:38:13 arch-desktop kernel: [drm:atom_op_jump] *ERROR* atombios stuck in loop for more than 5secs aborting
    Jun 15 14:38:13 arch-desktop kernel: [drm:atom_execute_table_locked] *ERROR* atombios stuck executing D218 (len 62, WS 0, PS 0) @ 0xD234
    I searched on internet, I think this is caused by my graphic card(ATI 5750), but I have no idea to solve it
    I don't know my system boot failure due to these error or another things.
    my PC specs:
    motherbroad - gigabyte GA-P55A-UD3 (bios ver - F11)
    cpu -  i5-750
    display - ati 5750
    os - arch 64bit
    Currently, I have downgraded back to 3.13.
    I hope someone can give me some idea,
    Thanks
    Last edited by samtai (2014-06-17 12:17:02)

    As there are errors associated with ntpd, I would temporarily disable the ntpd service and also ipv6.
    If they are not the only problem, at least your logs would be easier to examine for other problems.

  • IMac grey screen with external HDD attached

    I used to have unibody Macbook with externall USB HDD (containing Time Machine and some free space) attached to it.
    Today I have 2011 iMac but now if HDD is connected via USB, computer will stay at gray screen (after DVD drive noises).
    If I disconnect the HDD, it succesfully boots. And ALT key Boot Menu with plugged HDD can be opened no problems too.
    Formatted and partitioned HDD - no change.

    1. Potential solution: Apple wants your forum feedback
    Please see a post in the following thread and reply to it as you wish. Apple has now reportedly requested that we provide evidence in support of our desire to have the "open lid with screen off" option reinstated (eg significance of operating temperature differences, reduction in wifi reception, etc). They may then address our concerns with a Lion update.
    https://discussions.apple.com/thread/3190417?start=60&tstart=0
    2. The madness of magnets
    This is getting very worrying. It's madness that Apple owners feel obliged to experiment with passing magnets over the top of their premium-priced computers and sticking them on here, there and everywhere in the hope of finding short-term workarounds. The sooner this problem is fixed at source (ie within Lion), the better.

  • Mac OS X Boot failure... I cant Repair HDD with OS Disk,Shows Repair Failed. I cant backup my files from HDD. Backup failed. But I need my all datas from HDD. I dont want to format. Cant enter safemode also. anything else..

    Mac OS X Boot failure... I cant Repair HDD with OS Disk,Shows Repair Failed. I cant backup my files from HDD. Backup failed. But I need my all datas from HDD. I dont want to format. Cant enter safemode also. anything else..
    I installed XP @Bootcamp, I cant access my Mac HDD via XP..
    What I do??? Please help me.. please...

    You can try DiskWarrior (about $100).
    If that doesn't work, and if you have no backups at all, you might need to send your hard drive to Drive Savers or a similar service. It will cost a lot of money to get the data back, I'm sorry to say.

  • HELP! How can i restore/recover files from Bootcamp with Boot Failure - Missing operating system error?

    Hi,
    I am having a few problems with bootcamp on my imac. When i tried to move the bootcamp partition on windows 7 into free space, it crashed and turned off. Ever since i have had the error 'Missing operating system' and it fails to boot. I have some very important files on the bootcamp partition. Is it possible to recover these files or even to restore the bootcamp partition to it's original state? I do not have a backup of my bootcamp partition. Another problem i have is that ever since i tried to expand my macintosh HD partition into free space, when i hold alt while booting up (to choose which partition to boot like i normally do), the bootcamp partition has stopped appearing. This means that i cannot even boot the windows 7 bootcamp partition anymore!
    So basically here are my 2 questions:
    How can i restore/recover files from Bootcamp with Boot Failure - Missing operating system error?
    How can i make the Bootcamp partition appear in Startup Disk and when i hold the option key while starting up my computer to allow me to boot windows 7?
    Any solutions are very much apreciated!
    Thanks!
    I know that bootcamp (disk0s4) hasn't been fully deleted since it appears in disk utility (i cant do anything to it though)
    And here is the error i see when i try to launch bootcamp (back when i was actually able to boot up bootcamp to the error screen)

    WinClone 3 is OS X and saves Windows image it makes for restore - that should work but you will have to try and you would need to make a new image unless it also works with a native Windows system restore image. It is now supported and has come a long way.
    http://www.twocanoes.com/
    Paragon Clone OS works and does disk-to-disk clone just like CCC you end up with two bootable drives. But does not work with your setup. It would let you clone and move your Windows install to an SSD or another disk drive though and be bootable.
    During its clone process it checks for errors which is very helpful and lets you know - something CCC and others should adopt more of.
    http://www.paragon-software.com/downloads/demo.html
    I wish for our/my sake you had re-read and rewritten the long 'story' and broken it into a brief list of facts we needed.
    OS X
    Windows
    Backup (though external is much safer) and you want bootable OS X clones as well as TimeMachine
    https://support.apple.com/kb/HT1427
    https://support.apple.com/kb/HT1553
    There are a number of things to do like chkdsk and others as well as Windows DVD to do automatic system repairs and find out why.
    AppleHFS - the abilty to mount and read HFS volumes can be notorious.
    I would rearrange and redo your storage setup and how you use the 4-5 internal hard drive bays.

  • Problems with 1st Boot (media test failure, disk boot failure)

    I have the K7N2G motherboard.
    I hooked up everything in my system and on my first boot I get this error:
    PXE-E61: Media Test Failure, check cable
    PXE-M0F: Exiting NVIDIA Boot Agent
    DISK BOOT FAILURE, INSERT SYSTEM DISK AND PRESS ENTER
    So, I figure I'll start from scratch and just start with the floppy drive, cpu, and ram hooked up and I get the same error.  Here are my specs:
    MSI K7N2G
    Athlon 2400
    Kingston PC3500 RAM
    Volcano 7 Fan/Heatsink
    Seagate Barracuda V SATA 80 GB
    Verbatim CDRW 52/24/52
    Any help or suggestions would be greatly appreciated.

    This happens if:
    - The hard drive is not installed
    - An Operating System is not installed
    - The BIOS cant detect the hard drive, maybe:
      = The wrong jumpers are set on the hard-drive
      = The cable is not polarised and pin 1 is on the wrong pin
    - The hard-drive has not been set-up in the BIOS
    Try something like the above  

Maybe you are looking for

  • Restoring doesn't work correctly.

    I have formatted it and I've changed the path. When I restore it, it still asks me to restore it. I have a black fifth Gen black 30 gig iPod video. Any help would be awesome! I'm getting crazy music withdraws. >_<

  • What cast type are used for?

    In the example attached to this question is a simple VI application that cast, using type cast of LabVIEW, one value to different other type. My understanding of type cast, in C, C++ and to my best knowledge, was an implicit adaptation of a numerical

  • ITunes Visualizer Button is gone in new update

    Hello again, I did the most recent update to iTunes and the visualizer button that used to be in the bottom right hand corner is no longer there. I know I can use the hot keys, but I like to use the button. Does anyone know how I can get that button

  • Error during XML = ABAP conversion, empty tag

    Hi. Im sending data from a Data Base to a proxy using BI. But when I get an empty response from the data base wich gives me an empty XML tag the proxy shows me an error: -PARSE_APPLICATION_DATA Error during XML => ABAP conversion (Response  Message;

  • How do I unlock the blue box?

    There is a blue box around some of my paragraphs and not others. For the ones that have the blue box I cannot drag images into the middle. I have tried help, talked to my co-workers, even cycled thru the inspector comparing text with boxes as text wi