FCode ide boot driver - disklabel interface errors

Hello,
I can not find out how to get the 'offset' for the (disk label) load method set to h# 200.
First, I could not get 'load' to work at all except for 'no label' as a parameter, then as I was trying different things, I got 'bad magic number'.
Otherwise, load seems to work, as far as reading disk blocks into memory, and returning a count, etc.
This disk works ok with Solaris 8, has a valid label, and boot block code.
Does load use the numbers after the '@' for parameters? i.e. disk@0,0 ?
I can not find any other documentation on how 'load' works.
Any new information would be a big help!!
Thanks,
Jim Brennan

I think this is an endian thing so I will try 'lbflips' to change the byte ordering in the buffer

Similar Messages

Why do I get a boot drive not found error only when laptop lid has been closed?

I've got a HP Mini 210 P/Number: VX818EA with Windows 7 Starter.
It works fine when turning on after shutdown, but when I've put it to sleep by closing the lid it won't 'wake up', and I get a blank screen. On restarting the computer I get a 'boot drive not found' error, (3F0) which can be resolved by following the steps on this page: http://h10025.www1.hp.com/ewfrf/wc/document?docname=c01443463&tmp_task=solveCategory&lc=en&dlc=en&cc...
I've run disk check etc as suggested on that link, no errors are found, but nothing seems to resolve the problem more than temporarily. Seems odd that this only happens if I close the lid (sleep mode with the lid up is fine, doesn't crash the computer).
Can anyone advise?
Thanks

Hello,
Very strange, can you go to BIOS and reset the setting " By Default " ?. How did you check the disk ?
This is an unusual probleme Hp Mini 210 . And notice me after your reset the bios settings.

Boot drive causes screen errors on other Macs - but not mine...?

Due to a recent accident, my MBP's 160 gig hard drive was damaged and is now unusable. (I was backed up, that's not the issue.) I've since been using a 100 gig, 2.5 inch external drive (which I erased and formatted for use with Intel Macs) as a boot drive but it's close to full, and now that I don't have any major projects at hand, I'd like to send the MBP in for repair. The problem is, when using the external drive to boot other Macs (my Mini at work, my girlfriend's MacBook) the display is all mixed up - some parts are visible, others aren't. I can recognize certain icons from my desktop and Dock, for example - but everything's scattered all over the screen, and any kind of motion - dragging, hiding and showing the dock, opening windows - causes "ghosting" and "trails". There seems to be no way I can use the drive on other computers while I wait for my laptop to be repaired. Why does it only work on my MBP, is it something in the way I formatted it? (GUID partition scheme, SMART status, etc.)
:/

I'm surprised by this just because I booted another Mac from an external drive with a clone of my system for a couple of weeks under similar circumstances and the Macs were not especially similar. G4 PowerBook which came with Tiger pre-installed and the machine-specific disks vs. G3 eMac which had come with Panther. I would have thought that MBP vs. MB would be, if anything, much less problematic than PB vs. eMac. I wonder how common such problems are.
I assume you've played with Display preferences etc.? Presumably, you use an external monitor with the mini. Do you know if drivers are available for that which you might be able to install. (I don't expect this is the problem but you might want to check just in case.)
- cfr

Unico Drive serial interface error

1) I am trying to talk to a Unico drive via a serial port. I receive a -1073807339 error in the Vesa Read in the Drive Send VI. However, the VISA write doesn't seem to be getting to the drive properly as it should effect the speed even though the read doesn't work. I have been able to talk to the drive in HTBasic. I checked that the port settings are correct. I checked the CRC creation. The command is to be sent without any character trailing the CRC character. I turned that off in the VISA open. Any suggestions what else to try?
2) I also found that the VISA duplicate output doesn't work in the VISA open. That block element outputs an empty VESA device addr when "probed". Any idea why that isn't working?
Attachments:
Drive.llb ‏202 KB

RicK,
The error -1073807339 is almost always caused by a timeout. Adding a wait function, running in Highlight execution mode, or running with Ni-Spy will slow the processor and give the instrument time to read and generate a response. For more information, check out our VISA support page at: http://www.ni.com/support/visasupp.htm
Sarah Fenney
Applications Engineer
National Instruments

Boot drive error message

Following a near disaster after installing security update 2005-009 i have 2 problems ( or maybe only 1)
When i do a verify on my boot drive i get the message from disk utility, INCORRECT NUMBER OF THREAD RECORDS, volume needs repair but it cannot fix it.
Any suggestions.
Second after I managed to get my boot drive running again following many kernel panics I now have a folder called damaged files, can I discard this as it seems to mirror my HD

Hi, Paul and Allan, et.al —
Paul — Fwiw, I agree with Allan about your apparent options.
When you launched Disk Utility from your Install Disc as part of running Disk First Aid, did you notice the S.M.A.R.T. status of your HD?
Before saying another word — have you tried to access and save any data that may not have been included in your last backup? Using FireWire Target Disk Mode from another (or borrowed) Mac might be a means to accomplish this...
I'm not familiar with the specific "incorrect number of thread records" error message you received — so everything below should be considered conjectural or based on the perspective of the references cited. Each file and folder (directory) in an HFS+ file system must have a unique thread record. Apple describes the technical details in technical note TN1150: HFS+ Volume Format and the File Manager Reference. On a more layperson's level — paraphrasing and quoting from this source and its linked refs. — on an HFS+ formatted volume, a Catalog file contains records for all the files and directories stored in the volume. File thread records and directory thread records are two of four types of records contained in the catalog file. A file thread record stores just the name of the file and the Catalog Node ID (CNID) of its parent directory; similarly, a directory thread record stores its name and the CNID of its parent directory. The other two records are file records and directory records that "store a variety of metadata — including CNID, size, time-stamps, the first file extents of the data and resource forks, and pointers to the file's first data and resource extent records in the Extent Overflow File."
My point in considering this is that an incorrect number of thread records suggests that the catalog file can't do its job properly in helping you to access your files and directories. As Allan concluded, this sounds like a potentially significant disk directory problem. Although the terminology differs, a MicroMat (makers of TechTool) tech addresses a TechTool "file thread mismatch (-92) error" message in this MacFixIt forum thread. Several users report their experiences. If the Disk Utility "incorrect number" and TechTool "thread mismatch" messages are comparable... the MicroMat tech's comment that "Unfortunately, the file thread mismatch is an uncommon disk directory error, and it is not possible to know whether the ultimate cause is software or hardware" may be relevant.
I hope that you follow Allan's advice — and that DiskWarrior 3.0.3, TechTool Pro 4.0.6, or ProSoft's DriveGenius 1.1.5 is able to repair the problem — or that you're in a position to perform an Erase & Install. Please keep us apprised of your progress, so others may learn from your experience.
Good luck!
Dean

Hard disk error "boot drive not found...."

After screwing around to see how hard it would be to upgrade my hard disk, I started getting the ol' boot device not found error.
So, I went online on another machine and found that I could boot into a menu of boot devices by holding down the OPTION key. It presents me with options to boot from DVD, external drives, network, or lo and behold my MacHD. If I select my MacHD, after a minute it will boot as usual and present me with the
logon screen. I could just let it go and continue to do this, or what can I do to put it back the way it was so I can boot without holding down a key?
My intention is to upgrade to a 2TB drive as I see it's easy enough for me to do myself.

Try SMC and PRAM resets:
http://support.apple.com/kb/HT3964
http://support.apple.com/kb/HT3964
Ciao.

I have a MacBook Pro, Matshita UJ-857E while recording music my drive reported an error: Sense Key=HARDWARE ERROR Sense Code=0x03,0x01 I have no idea what this means, and now my cd burner/player won't work. can someone help me fix this problem?

Please Help me. I am having problems with my MATSHITA UJ-857E DVD-R burner/writer. I burned 4 cd's and then it stopped working.
I can select my songs, and then it asks for a blank disc. It starts preparing to write the disc,then it says,"
The drive reported an error: Sense Key= HARDWARE ERROR Sense Code= 0x09,0x01 TRACKING SERVO FAILURE.
Can anyone give me some advice on how to fix it or what this means because I have no idea what it is talking about or how to begin to fix the problem?

tanyafrombakersfield wrote:
It starts preparing to write the disc,then it says,"
The drive reported an error: Sense Key= HARDWARE ERROR Sense Code= 0x09,0x01 TRACKING SERVO FAILURE.
This is an error reported by the optical drive's firmware. The tracking servo is the servomechanism which guides the laser pickup along the track on the optical disc. The error means that the servo couldn't do its job within the programmed parameters. What it doesn't say is why.
You have to be very precise as to when this error occurs. If it occurs as you wrote, while it "starts preparing to write the disc", and not when it has actually began to burn, then it's likely that the drive has gone bad and needs to be replaced.
There are other possibilities, so you should check them, but they would be more likely if the error occurred after the drive began to write. OrangeMarlin has suggested two options -- try a different brand of CD or DVD, and try cleaning the lens.

ERROR: You're trying to run the product with the legacy launcher oracle.ide.boot.Launcher

Hi,
I have problem while upgrading SQL developer 4.0.0.12 to 4.0.0.13 on my windows 64 bit machine. 4.0.0.12 version is working good, where as 4.0.0.13 is showing below error while starting it.
I did try sqldveloper.exe and its not working, So I started running sqldeveloper.bat to get more information, also added AddJavaLibFile & SetMainClass to sqldevloper.conf but no luck. Could you please help in this regard.
Error Message
C:\Dev Software\sqldeveloper-2\sqldeveloper\bin>java -Xmx640M -Xms128M -Xverify:none -Doracle.ide.util.AddinPolicyUtils.OVERRIDE_FLAG=true -Dsun.java2d.ddoffscreen=false -Dwindows.
shell.font.languages= -XX:MaxPermSize=128M -Dide.AssertTracingDisabled=true -Doracle.ide.util.AddinPolicyUtils.OVERRIDE_FLAG=true -Djava.util.logging.config.file=logging.conf -Dsql
dev.debug=false -Dide.conf=”./sqldeveloper.conf” -Dide.startingcwd=”.” -classpath ../../ide/lib/ide-boot.jar oracle.ide.boot.Launcher
ERROR: You’re trying to run the product with the legacy launcher oracle.ide.boot.Launcher . Check your .conf file and be sure to include:
AddJavaLibFile ../../ide/lib/fcpboot.jar
SetMainClass oracle.ide.osgi.boot.OracleIdeLauncher

Use C:\Dev Software\sqldeveloper\sqldeveloper.exe instead.

I have downloaded OS X Yosemite using recovery from boot but while installing error occuring showing unable to extract essential.pkg so can't install. problem is i have already formatted my drive and dont have any os right now. please help

i have downloaded OS X Yosemite using recovery from boot but while installing error occuring showing unable to extract essential.pkg so can't install. problem is i have already formatted my drive and dont have any os right now. only the downloaded new os x yosemite in the os x base system. please help

Please try again after taking each of the following steps that you haven't already taken.
Step 1
Reset your computer’s PRAM.
Step 2
If your model has user-replaceable memory, and you've upgraded the memory modules, reinstall the original memory and see whether there's any improvement. Be careful not to touch the gold contacts. Clean them with a mild solvent such as rubbing alcohol. Aftermarket memory must exactly match the technical specifications of the machine.
Step 3
Back up all data to at least two different storage devices, if you haven't already done so. One backup is not enough to be safe. The backups can be made with Time Machine or with Disk Utility. Preferably both.
Erase and install OS X. This operation will destroy all data on the startup volume, so you had be better be sure of the backups.
Step 4
Make a "Genius" appointment at an Apple Store, or go to another authorized service provider to have the machine tested.

Neo4 Dual Drive ATA and IDE boot from ATA?

I just set up a Neo4 board using two drives. A seagate 120Gg ATA drive and a Maxtor 200Gb IDE drive. I would like to use the ATA drive as the boot drive but I can only seem to startup from the IDE drive. Is there a trick to get this working?

Quote from: Richard on 28-September-05, 01:07:15
ATA and IDE are the same thing.
Huh. Well. Okay, perhaps I'm not posing the question properly. The seagate drive is plugged into the SATA1 position, while the Maxtor is plugged into IDE1. They use different cables and connectors which is where my confusion started I guess. In the BIOS when I select the seagate drive to boot from it will not boot. But it does off the Maxtor. I have no reason to believe the drive is bad but hwo knows. I guess I just want to make sure I'm not missing some setting to properly boot from the SATA1 position when both drives are attached.

IDE drives not recognized with SATA as boot drive

Greetings All,
I have a new 865PE Neo2-P that has a 120 Gig SATA drive as its main boot drive. It's loaded with WinXP Home. I'm trying to add two IDE hard drives from my previous system to the on-board controller, and it simply refuses to recognize them at all.
I've read the FAQ, the manual, previous posts, etc., and I've tried the different BIOS settings suggested in the forum, and nothing seems to work. The only thing I haven't been able to do as posted was to "set my SATA drive as the boot drive". The boot selections in the BIOS only list floppy, IDE-0, and some boot manager. Not sure if the boot manager was installed by my local PC assembler or not.
The PC shipped with the BIOS settings MSI recommends on page 3-22 and 3-23 for users wanting to use both SATA and IDE devices. That is to say:
Legacy Mode
P-ATA only
SATA Keep Yes
PATA Channel Both
SATA Ports P0-3rd/P1-4th
Changing the BIOS settings only seems to lose the DVD/CD drives, and the system wants to boot off of the IDE's rather than boot from the SATA.
What the ??!! is going on here? Why is it so difficult to get this MB to recognize IDE devices? I've never had this much difficulty before with any MB's, and I'm getting very frustrated.
What should I do next?

OK, I checked my notes. I did try these two BIOS settings without it working:
ATA On CHip Operate Mode: Native
ATA Config: SATA only
PATA Keep Enabled: Yes
PATA Channel Selection: Both
Set SATA as RAID: No(Only available in FIS2R/FISR versions only)
or
ATA On CHip Operate Mode: Native
ATA Config: PATA only
SATA Keep Enabled: Yes
Set SATA as RAID: No(Only available in FIS2R/FISR versions only)
Now, tonight I decided to try a different cable just to eliminate that. What I discovered is that the IDE1 socket is "out of spec". There are no bent pins, but the rightmost three columns of pins are larger than the others, too large for any IDE cable, and consequently it doesn't fit snugly in the socket!! (I tried plugging the MSI supplied cable from the DVD drive into that socket as well and it wouldn't fit.) I never noticed this before as I was pressing the cable in the socket as far as it would go.
I will talk to my local manufacturer to see about getting a replacement board. It's clearly messed up. Thank you MSI for the swell quality control.
Derek

SOLVED: Mounting IDE ZIP Drives, "Special Device hdb4 Does Not Exist"

I thought I would post a follow-up, since I have finally resolved this long standing issue, which has plagued me since my first days with Linux many years ago.
As outlined in my original post below, every time I would attempt to access a Zip disk for the first time since boot, Linux (pretty much all distros I have ever tried, with the exception of SuSE 9.3) would fail to mount the disk and report back that "Special device hdb4 does not exist". Of course the "hdb4" part varies from distro to distro and machine to machine, depending on how your Zip disk is connected and how the distro names its disks, but the basic error has been constant. I have always worked around it by redoing the mount command specifying just the device, not the partition, and while that would always fail, it would force the creation of the device /dev/hdb4, and I could carry on. Annoying but effective.
FINALLY, a long term answer. I got my inspiration from a really snarky post I read in another online forum where someone had posted this very same question (this is a very common problem with no common answer it seems!). The respondant, who completely failed to provide a helpful answer, basically said "listen, the OS is telling you what is wrong - the device hdb4 doesn't exist - so fix it, and all will be just fine". Of course, the respondant didn't even bother to offer a suggestion about HOW to fix it.
However, therein lies the inspiration for the solution. Indeed they are right, /dev/hdb4 *doesn't* exist, so how to fix that? They had a point. I started researching the mysteries of mknod, a program that can create /dev files, and the even deeper mysteries of Linux device numbers, both major and minor.
In the end, I found a wonderfully informative document that described the current standard for the device numbering scheme used by mknod, and Linux in general. The key things of interest are this:
1/ The major number for IDE based drives is 3.
2/ IDE allows for 64 partitions per device, so the minor numbers are 0-63 for device "a", 64-127 for device "b" and so on. You derive the minor number of interest for your particular device by taking the starting value of the minor number range of interest for your device and adding the partition number to it. So, for example, hdb4 would have a minor number of 64 (the start of the minor number range for device "b") plus 4 (the partition number in "hdb4"), yielding a result of 68.
3/ The major number for SCSI based drives, or those that your OS treats as SCSI, is 8.
4/ SCSI allows for 16 partitions per device, so the minor numbers are 0-15 for device "a", 16-31 for device "b" and so on. You derive the minor number of interest for your particular device by taking the starting value of the minor number range of interest for your device and adding the partition number to it. So, for example, sdb4 would have a minor number of 16 (the start of the minor number range for device "b") plus 4 (the partition number in "hdb4"), yielding a result of 20.
In my case, Arch seems to be treating all of my disk based devices as SCSI, perhaps because I do have a real SCSI interfaced Jaz drive in my machine. So, the Zip disk of interest in my machine is sdc4 (my real SCSI jaz is sda, my Arch root is sdb, and the IDE Zip is sdc). Applying the above, for /dev/sdc4:
- The major number is 8.
- The minor number is 32 (start of range for device "c") plus 4 (the partition number) = 36.
Armed with this knowledge, I su'd to root and entered:
# mknod /dev/sdc4 b 8 36
and like magic, there is was, /dev/sdc4. I popped a disk into the drive and my first attempt to access it was greeted with success, not the usual "device does not exist" error! By the way, the "b" in the above command is just part of the mknod syntax, and indicates that I am creating a block device (vs. a character device, or some other type of device - disk drives all seem to be "block" devices for apparent reasons).
SO, determine your major number by device type (it will usually be 3 or 8), compute your minor number by device letter and partition number, and add a mknod command to your system startup (so you don't have to do it manually every time) and you are done! No more annoying "device does not exist" errors.
Now for the kicker. It turns out that this information has been available under my nose all along. I just didn't recognize the code. If you do the following:
# ls -ald /dev/sd*
Linux obligingly provides you with the major number and the start of the minor number range for your device. Since Linux has always detected the Zip *device* (just not the partition) this is really all you need to know. When I issue the above command, I get an output like:
brw-rw---- 1 root disk 8, 32 date time /dev/sdc
Guess what, there they are! "8" is the major number of interest, "32" is the start of the minor number range of interest. If I had just recognized that, and known that all I had to do was add the partition number to the minor number to get the magic number to feed into mknod, things would have been easier.
Sorry for the long post, but like so many things in Linux, the OS doesn't make this easy on the uninitiated. I sincerely hope that this post may help lots of other people to resolve this vexing and longstanding problem.

Solved!
See the lengthy response in this post:
http://bbs.archlinux.org/viewtopic.php?id=36468
I posted the solution separately, with the most informative title I could come up with, so that others Googling this topic on the web may hopefully easily find it.

Can't burn CD's - "Interface error 5"

Hello, I haven't used my old firewire LaCie CD burner (LaCie 1394, blue front with the slide out tray) in a while but recently I needed to put some graphics files on a CD. The sw I'm using is Toast 6. No matter what I tyry to do I get the following message: "Interface Error: 5 The connection is not stable"
I tried different CD brands, no effect.
This is the setup.
Machine Name: Power Mac G4 Cube
Machine Model: PowerMac5,1
CPU Type: PowerPC 60? (1.1)
CPU Speed: 1.3 GHz
L2 Cache (per CPU): 512 KB
L3 Cache (per CPU): 2 MB
Memory: 1.25 GB
Bus Speed: 100 MHz
Boot ROM Version: 4.1.9f1
System Version: Mac OS X 10.4.2 (8C46)
Kernel Version: Darwin 8.2.0
Looking for answers I found an (unanswered) message on a macosx.com forum. I'm reposting it because it provides more info about the same problem:
[quote]
"Burning the disc failed because communication to the disc drive failed. (Error code 0x80020022)" -- Is the error code when I attempt to burn any disc using the Finder or Disk Utility.
"Interface Error: 5 The connection is not stable.
The drive reported an error:
Sense Key = Illegal Request
Sense Code = 0x210x02
BUFFER UNDERRUN" --
Are the errors when I attempt to use Toast Titanium v6.x and v7.x.
I'm using an iMac G5 running 10.4.2. I have two burners, both of which give me the errors and will no longer burn to CD's or DVD's (cheap or expensive media, I've tried many different types). The burners i have are an internal superdrive that came with the mac (MATSHITA DVD-R UJ-825) and an external LaCie Firewire DL drive (_NEC DVD_RW ND-3500AG). Both drives started giving this error at the same time and I can't think of anything that I installed that could effect these. I don't have any speed tools installed.
I have tried all that Apple suggests in the articles http://docs.info.apple.com/article.html?artnum=25750.
I've experienced the same errors twice before, though not both drives at the same time. What fixed it the first time was simply upgrading the firmware on the burner. Second time, there were problems on the hard drive that I was burning from (directory issues if i remember) and running a combination of Tech Tool and Disk Utilitity fixed that.
But this time, I'm at my wits end and can't find anything helpful online. I'm hoping to find an answer before I end up trying a complete system reinstall.
Any info would be greatly appreciated.
[/quote]
Yes, any info ...
TIA
Cube, 2 ibooks Mac OS X (10.4.2)

I'm having the same problem using Toast 7 to burn a Video TS movie I made. I'm using an external Lacie 16X DVD-R DL drive and an iMac G5 2.0, and Mac OS 10.4.3
After several failures with Interface Error 5, I tried copying a DVD movie I made from another DVD. This was created with the same Lacie drive using Mac OS 10.3 and my old iMac FP 15 inch. I got the same failure message.
I then switched my Lacie Drive to the USB port and everything is working fine. I switched it back to FireWire and I get the same error message again.
I can play DVD's on the Lacie with either the USB or FireWire port without any problem, I just can't record using the FireWire port. The FireWire ports on the computer work fine with all my other FireWire devices.
It must be a combination of 10.4.3, Toast 7 and Lacie FireWire. I'm going to recheck Lacie's site to make sure I have all of the updates.
iMac G5 Mac OS X (10.4.2) Mac OS 10.4.3

How can I upgrade my Mac G5's boot drive?

Hi,
I have a PowerMac G5 running 10.5.8... and just bought a new internal 1TB SATA I would like use as my new boot drive.
What's the most simple method to do so?
I have a copy of Data Rescue 3 that has a "clone" feature -- which I tried. It worked, but the new drive's system partition map is reduced to the size of the old (smaller) drive. I used Disk Utility to try to increase the volume scheme up to the new capacity, but it gives me an error saying "MediaKit reports partition (map) to small." and won't increase the size.
Suggestions?
Thanks,
Carl

I have no idea what you've done with Data Rescue, but it isn't a system clone. Here's what you need to do:
A. Prep the new drive:
1. Open Disk Utility in your Utilities folder.
2. After DU loads select your hard drive (this is the entry with the mfgr.'s ID and size) from the left side list. Note the SMART status of the drive in DU's status area. If it does not say "Verified" then the drive is failing or has failed and will need replacing. SMART info will not be reported on external drives. Otherwise, click on the Partition tab in the DU main window.
3. Under the Volume Scheme heading set the number of partitions from the drop down menu to one. Set the format type to Mac OS Extended (Journaled.) Click on the Options button, set the partition scheme to GUID (for Intel Macs) or APM (for PPC Macs) then click on the OK button. Click on the Partition button and wait until the process has completed.
B. Repair the Old Hard Drive and Permissions
Boot from your OS X Installer disc. After the installer loads select your language and click on the Continue button. When the menu bar appears select Disk Utility from the Utilities menu. After DU loads select your hard drive entry (mfgr.'s ID and drive size) from the the left side list. In the DU status area you will see an entry for the S.M.A.R.T. status of the hard drive. If it does not say "Verified" then the hard drive is failing or failed. (SMART status is not reported on external Firewire or USB drives.) If the drive is "Verified" then select your OS X volume from the list on the left (sub-entry below the drive entry,) click on the First Aid tab, then click on the Repair Disk button. If DU reports any errors that have been fixed, then re-run Repair Disk until no errors are reported. If no errors are reported click on the Repair Permissions button. Wait until the operation completes, then quit DU and return to the installer. Now restart normally.
If DU reports errors it cannot fix, then you will need Disk Warrior and/or Tech Tool Pro to repair the drive. If you don't have either of them or if neither of them can fix the drive, then you will need to reformat the drive and reinstall OS X.
C. Clone using Restore Option of Disk Utility
1. Select the destination volume from the left side list.
2. Click on the Restore tab in the DU main window.
3. Select the destination volume from the left side list and drag it to the Destination entry field.
4. Select the source volume from the left side list and drag it to the Source entry field.
5. Double-check you got it right, then click on the Restore button.
Destination means the new hard drive.
Source means the old boot drive.
Last, use Startup Disk preferences to select the new drive as the permanent startup drive, then click on the Restart button.

Converting to SSD Drive for Boot Drive on m7 with Win8

I just bought a new m7-j020dx (product code E4S19UA#ABA) with Windows 8 from Best Buy. Unfortunately, it came with a standard hard disk drive (HDD) and I would like to install a Solid State Drive (SSD). I have an Intel 320 and 530 series drive. But I have not been able to get a bootable drive from this.
The first thing I tried was cloning the factory drive to a new 530 series drive using AOMEI Backupper. I got a write error on the third partition. I thought perhaps the drive was bad so I tried it again with an Intel 320 series SSD drive. Same error.
The next attempt was to clone the drive to another 1 TB drive (connected via USB), shrink the main partition with MiniTool and clone to the 320 series SSD. The cloning went fine. However, with the new SSD installed, the computer will not boot and I get "Error0x0000225", something about a file not found. Turning off "secure boot" in the BIOS setup did not help (I did this after the clone).
So I thought I would make a clean install of Win 8. I generated a recovery disk on a 32GB SanDisk USB drive using Win8's recovery disk generator (as instructed on the HP site). I then ran the recovery program off the USB drive and after a couple of hours of installing driver software and several reboots, I get an HP message stating the installation was not complete. Repeating the install did not help.
I am not sure what the problem is.
Is the USB recovery disk a made from the original HDD bad (one only gets one shot at it)? Do I need to order media from HP on disks? Are there issues with using SSD drives on these computers? Do I not have a BIOS settig correctly (UEFI)? Is there some Intel storage drivers getting in the way?
I think my next step will be to create a disk Image and then put it back to the SSD drive. But I doubt this fixes the issue with booting to it.
Another option might be to do a fresh build using Win8 media and then download and install each driver from the HP website.
Any ideas out there in the land of experts?
This question was solved.
View Solution.

Vachsen
Please install the HDD Back
Update your BIOS
http://h10025.www1.hp.com/ewfrf/wc/softwareDownloadIndex?softwareitem=ob-128144-1&cc=us&dlc=en&lc=en...
Install the new Intel Rapid Start Technology Driver
https://downloadcenter.intel.com/Detail_Desc.aspx?agr=Y&DwnldID=23496&ProdId=2101&lang=eng&OSVersion...
Reboot
Attach the SSD over USB Cable
Update the SSD Firmware
https://downloadcenter.intel.com/Detail_Desc.aspx?DwnldID=18363
Reboot
Use the Intel tool for drive Copy
https://downloadcenter.intel.com/Detail_Desc.aspx?agr=Y&DwnldID=19324
Say thanks by clicking the "Kudos! Star" which is on the left.
Make it easier for other people to find solutions, by marking my answer with "Accept as Solution" if it solves your issue.

FCode ide boot driver - disklabel interface errors

Similar Messages

Maybe you are looking for