GX630 boot from esata expresscard adapter

Hi,
i have GX630 with non functional sata ports (sata working for 5min and after that not).
Now i booting from USB, but this is little slowly.
I read many topics about booting ssd card from expresscard slot, and it works, but its much expensive for me.
Can i boot from esata expresscard adapter (adapter supports booting)?
Can bios in GX630 recognize this sata adapter?
Thanks for reply

Hi and welcome to Discussions,
the EFI and SMC updates are specific for each Mac model.
Therefor trying to apply an EFI update made for the newer MBP to an older one would either not work (because the Installer checks the model) or, if it installs, surely crash your MBP.
Don't try it !!
Since the newer MBPs uses a different (newer) Intel-chipset on the logic board, it is most likely that the ability to boot from eSATA Express Card is not implemented on the chipset that is in your 'older' MBP.
Sorry
Stefan

Similar Messages

  • Lion 10.7 - Proper driver for Dynex eSATA Expresscard adapter?

    I just upgraded to OS X Lion today, and I'm having trouble talking to my external drive with my eSATA expresscard adapter. (see link below)
    http://reviews.bestbuy.com/3545/8682393/dynex-2-port-esata-ii-expresscard-adapte r-reviews/reviews.htm
    The adapter is detected as a "Mass Storage Controller," but I can't get any connectivity with my external drive. Has anyone had success with this/any expresscard adapter? Back to good ol' USB 2.0 for the time being I guess...
    Thanks in advance!

    I can confirm that this driver (SLI 3132 ver. 1.2.5.0) is working for my Dynex 2 port e-SATA II ExpressCard Adapter.
    (Link to Mac specific driver page)
    I haven't done any super heavy lifting with it yet, but so far so good.
    Will report back if I see any issues over the next couple days of use.

  • Is it possible to boot from esata T510?

    wondering if anyone tried it - pressing f12 see the drive and boot...

    CorkyG wrote:
    This is interesting. My eSATA drive is an external Vantec case that can be connected eSATA or USB. So - I connected it via USB and I could then boot from it. That is somewhat freaky!
    exactly - that's what I too found : usb-yes but esata-no
    it doesn't make any sense ! why shouldn't be able to boot from esata ?

  • Is it possible to boot from eSATA?

    Hello!
    Is it possible to boot from the eSATA port with an external hard disk?
    At XP or Vista?
    Thanks!
    dup

    Thanks for your answer but I don't undestand :"If you could boot from eSATA, you could copy or erase the data on the HDD. So I think this would be not so good ;)
    I explain I have for example an external box eSATA with a HDD and XP or Vista installed on it.
    My question is: If I plugged it on the P300 via the port eSATA can I boot form it in doing for example to choice the boot "F8"?
    Yes or no?
    I test it with few desktop computes: It works with eSATA (but not with USB) and no risk to destroy or erase files! So is it idem with a laptop?
    Best regards

  • Boot from eSATA

    I just received my HP Proobook 4720s. When I ordered it I didn't realize that I had to take the thing apart to swap out HD's. With my old notebook I would have both a "work" and a "home" HD, and would swap them out depending on my use, usually a couple of times a day. That will not work with the 4720s.
    1. Is it possible to boot from esata? I don't see that as a boot option in the bios.
    2. Is it possible to use a USB 3.0 express card and boot from that?

    You can contact them using chat in the USA, but the quality and knowledge of the help you get varies widely.
    USA
    http://welcome.hp.com/country/us/en/contact_us.html
    Everywhere else
    http://welcome.hp.com/country/us/en/wwcontact_us.html

  • GD80: Boot from eSata? (and slow booting)

    I recently built a set of workstations for our office with p55 GD80 motherboards.  To do some testing, I wanted to do a clean Ubuntu OS install onto an external drive using eSata.
    Here's the issue:
    - The motherboard detects the eSata drive during the boot sequence, but it may do so very slowly or even hang (code 0075).  This has been observed on two separate machines.
    - The F11 boot menu does not list the eSata drive as a choice to boot from.  Disconnecting the internal drive and removing all other bootable media to try to force it to use the eSata fails with the standard "no boot media" message.
    - The drive in questions boots and operates fine when I hook it up to internal SATA (or in my case, via the SATA to eSATA breakout pannel)
    Questions:
    1: Is the ability to boot from eSata supposed to be a working feature?  These are the first machines where I've had it.
    2: Are these issues something that might be fixed by a BIOS update?  (I will update here later with my current bios version when I get into work again, but the motherboards were all purchased from Newegg at the same time in September.)
    3: If not, is this a known issue?
    Thanks in advance.

    You could easily prepare and USB Flash Drive for a safe DOS-based BIOS Flash on any Windows based system and then use then boot from that flash drive on the target board in order to update the BIOS.  These are some pretty straight-forward instructions:
    https://forum-en.msi.com/index.php?topic=142371.msg1062484#msg1062484
    ... and of course, the BIOS File will have a different name for your board and so will the actual flash command.

  • Booting from ESATA drive on Qosmio F50-10Z

    Hi,
    is it possible to boot from an external drive using the ESATA port?
    I have BIOS 1.60 installed but I don't see an option for ESATA?
    What about a USB drive? Laptop is a Qosmio F50-10Z
    Thanks

    I think its not possible to boot from eSATA. The BIOS must provide such functionality.
    I never tried this but I think this is not possible.
    As far as I know it must be possible to boot from an USB device.
    The BIOS does support this so try it.

  • My MBP won't boot from my Expresscard SSD after I took it out during sleep!

    Before this happened I booted my Macbook Pro from an Expresscard SSD. Oddly enough you can take it out while the computer is sleeping. This time though I took it out and inserted it in another computer to transfer files. I put it back in and woke the computer, and I started getting weird messages (ex. Evernote didn't work because it couldn't read its database,) and other things. Now it simply hangs on the Apple logo during startup.
    Does anyone that knows what exactly happens to a drive during sleep, and while being read by another computer? What I can do to avoid reinstalling OSX on the drive?

    +Oddly enough you can take it out while the computer is sleeping.+
    What makes you think that? From your description, it's obvious that you corrupted the contents of the drive. You can try "Repair Disk" in Disk Utility, but most likely you'll have to reinstall. I wouldn't trust any of the data on it now.

  • DV6 2160EL Boot from eSATA hard drive

    Hi all,
    anyone know if is it possibile to boot from an eSATA HD on a DV6 2160EL?
    I tried to set it up in the bios boot order but it doesnt recognize it.
    It is recognized in windows and work well.
    Is there a BIOS patch or update to solve the problem?
    Thanks
    Giò

    Did you hold down the option key when you turn on your computer, until a selection thing comes up?
    Do this, and then select the external hard drive
    Hope this works!

  • Booting from an ExpressCard SATA card

    I would like to know, out of any of the ExpressCard SATA cards available, do any of them support booting from an attached external drive? I want to be able to install Mac OS X and run it off of the attached drive. Thanks.

    Any Firewire drive can be used to boot an Intel Mac (as well as any USB 2.0 drive.)
    If you are concerned about speed but want to use a notebook drive, then you are pretty well off using FW400 or FW800 because the drives themselves are not fast enough to see any appreciable speed difference whether you use SATA on the ExpressCard/34 slot or Firewire. Just because the PCI/e bus is faster doesnt' accomplish a thing if the drives are maxed out on a FW400 port. Current notebook drives whether SATA or PATA are not fast enough to saturate a FW800 bus and rarely are faster than a FW400 bus.
    I'm not sure why you feel there is indefinite information about bootable external drives and cloning software. The available information is quite definitive and specific. You seem to have a lot of information but don't quite understand it.
    Intel Macs can boot from external Firewire or USB 2.0 drives. All Intel Macs require their hard drives be partitioned using the GUID partition scheme. You cannot boot an Intel Mac from a drive using the APM partition scheme. You cannot boot an Intel Mac using a PPC version of OS X and you cannot boot a PPC Mac using an Intel version of OS X. There are no problems with drives not spinning up quickly enough (I have no idea where you picked up that piece of misinformation.) Although the Oxford chipsets are the most popular in use with external drives, Macs can boot from external drives using other chipsets such as the Initio chipset.

  • PB won't boot from one specific battery

    Does anyone know why a fully charged battery would not have enough juice to boot a Powerbook? I have a third party battery (Hi Capacity 4400 mAh) that will run fine once I boot from an ac adapter but I can't boot from this battery. I've tried it in different Powerbooks and I got the same result.
    It used to boot fine.

    Notes from System Profiler:
    Battery Information:
    Battery Installed: Yes
    First low level warning: No
    Full Charge Capacity (mAh): 3925
    Remaining Capacity (mAh): 1247
    Amperage (mA): -2051
    Voltage (mV): 10983
    Cycle Count: 196
    Coconut battery has the same data.

  • Multiple booting - through esata port, usb, firewire

    i'm testing usb, esata, firewire ports for multiple booting and if anyone has also experimented just let me know p.s i remember there was another topic last year about it

    I have tried to boot from eSATA, and I discovered a trick.  In the BIOS, you have to switch the SATA mode from AHCI to IDE (aka legacy, compatibility, or just off).
    I have a Y450 with a built-in eSATA port and an Intel ICH9 SATA controller.  I  bought an external powered enclosure that has an eSATA connector.  The BIOS would not recognize the external drive, and so wouldn't list it in the boot order.  It would recognize and boot from it via the USB connection however.  Also, even though not recognized by the BIOS when connected via eSATA, once Windows 7 booted up, it found and used the drive just fine.  I was able to partition and format it in Windows 7 over the eSATA connection.  I was also able to boot Linux from CD-ROM, and then it also was able to see the eSATA drive (and install Linux).  I just wasn't able to boot from it.
    I experimented with settings in the BIOS, and found that if I set the SATA mode to IDE, then the BIOS did recognize the eSATA drive, list it in the boot order, and could boot from it.  I've had no problems booting and running Linux on the eSATA drive this way, and performance measurements are close to the manufacturer's specs for average read throughput.  What I lose without ACHI is native command queueing (which could provide a performance in random read cases), and hot plugging.  Oh well.
    The big pain is that I have to switch back to ACHI in order to boot Windows 7 on the internal drive.  Otherwise I get the blue screen of death, due to Windows expecting SATA devices, not IDE.
    I think Lenovo could fix the BIOS if it wanted to.  I wish it would...
    Greg Holmberg

  • Almost got WinXP booting from Expresscard SSD

    Here is a story of how I almost got this to work. Seeing if the user community has any advice/suggestions. Here we go:
    1) Bought a 48GB Express34 SSD card hoping to install and boot XP on it. The expresscard34 is on the Serial-SATA bus so had my fingers crossed.
    2) In OSX ran the BCA, partitioned 48GB, and installed WinXP on the my internal HD: Success
    3) Booted into WinXP, updated to SP3/etc, restart: Success
    4) In OSX I used WinClone to Clone my bootcamp partition: Success
    5) In OSX inserted my expresscard SSD and formatted it using to the GUID Partition Table: Success
    6) In OSX I used WinClone to restore the bootcamp partition to the SSD: Success
    7) Deleted the bootcamp partition on my internal HD. Now I have OSX->HDD and WinXP->SSD: Success
    8) Shut down computer. Make sure SSD is inserted. Turn computer on while holding the option key. Boot Camp sees MacintoshHD and BootcampSSD!: Success
    9) Choose BootcampSSD...wait for it..."No bootable device found - please insert disk and hit any key": FAIL :/
    Side note: I tried this again, but skipped step 7. It worked. I was able to boot from either MacintoshHD, BootCampPartitionHDD, or BootCampSSD, but that defeats the purpose...
    I suppose this has to do with the fact that WinXP not only likes to be the only OS on a HD, but also perhaps the driver between the expresscard34 and SATA bus is not available on bootup. Its a shame because BC sees the SSD as bootable, but WinXP chokes. Of course it is a 10 yr old OS so its almost to be expected.
    Perhaps this would be possible using Win7?

    Thanks for replying. I gave changing the bootconfiguration an other try. although I had done it already.Results: If I use only "legacy" the bios passes both my ssd-drive and my hdd-drive and goes to network-boot (without result of course). If I choose Efi first, and put the windowsbootmanager on SSD on top, he skips it an goes to bootmanager on the HDD.The question still is: How to adapt the windows bootmanager on the ssd to make that it boots the windowspartition on the SSD ??

  • T400s Linux/Windows dual boot with Linux from Esata Flash Drive

    This project is about a dual boot Windows/Linux system without using the normal dual boot changes in the bootloader of the windows hard drive. When I started this I found bits and pieces of information on the web but no complete description so I wrote this post.
    I have done a dual boot system on my previous Thinkpad where I had partitioned the hard drive between Linux and windows. For this project I wanted to leave the windows hard drive absolutely intact and unaltered, and boot Linux from a flash drive in the esata port on the back of the T400s. Obviously this uses the F12 boot list function key to boot from the flash. The advantage of this is that Windows is totally unaltered and when I need Linux, I plug in the esata flash drive, hit F12 during the boot cycle and select booting from the esata flash drive. The reason for Esata rather than USB is simply speed. I have a nice fast Linux installation.
    I used the OCZ esata flash drive but suspect any of the alternatives will work. It did not need the accessory usb cable because the Thinkpad powered the esata flash directly.
    To boot from the esata drive I had to make the following changes in the bios
        I left the esata flash plugged in as I went into the bios
        Bios>config>Serial ATA and changed the Sata controller mode option to compatibility
        Restart and back into the Bios
        Bios>startup>boot - in my case the esata flash drive showed up as ATA HDD2 and was excluded from the boot order so I had to un-exclude it and move it to the point in the boot order that I wanted.
    Next I downloaded a linux installation iso and put it on a CD - in my case opensuse. Then booted from the CD
    From now on this instructions are specific to opensuse and yast but can be generalized to whatever Linux is being used.
    In my case yast came up with a good set of suggestions for automatically partitioning the flash drive but then crashed during the partitioning itself. So I rebooted and specified the partitions manually.
        A fat32 partition left as a partition which both windows and Linux could see (in my case about 20% of the drive) (/dev/sdb1)
        An extended partition with the remainder of the drive (/dev/sdb2) which contains the following logical partitions
        A linux Swap partition of 2GB (/dev/sdb5)
        A linux /home partition –the remainder of the drive (/dev/sdb6)
        A linux /root partition of 8GB (/dev/sdb7)
    Yast automatically suggested mount points of C,D,E for the windows partitions. Unfortunately because of the way the Thinkpad hard drive was laid out Yast had C assigned the ThinkPad Service partition and D assigned to the SW_Preload (or main windows partition). However there was an edit function that allows for the reversal of those mount points so that the windows C drive is mounted in Linux as Windows/C thereby avoiding confusion. I had already backed up and removed the Thinkpad factory install data so I did not have to deal with that. Yast suggested Windows/E for the mount point of the FAT32 partition on the flash drive, which I accepted.
    The yast install configurator made all this manual selection easy, and after the manual configuration the partitioning worked perfectly.
    Next step was Linux user configuration which went fine
    Next was booting.
    In the section management tab
        delete the windows 1 and 2 options (since we are not dual booting directly)
    In the boot loader installation tab
        uncheck boot from mbr ( this stops the install from installing Grub and dual boot on the windows c drive
        check boot from root partition (this installs grub and all associated files in the Linux root partition (/dev/sdb6)
    I believe that the correct procedure at this point is to click Boot Loader installation details which will bring up the Grub device map. In the device map there will be a line for the fixed hard drive (aka the windows drive) and a line for the esata flash drive. When the installer started up these were in hard drive and esata drive order. However when we boot directly from the flash the esata drive will be grub drive hd0 and the fixed hard drive will be grub hd1. The device map order needs to be changed to reflect this ie the esata drive should be first not second.
    I did not do this and ended up initially doing Grub command line editing to boot and later manually editing the grub files using information I had previously learned the hard way and through google.
    At this point let the installer go ahead and install Linux. After doing this it should come back and tell you to reboot. Do not do it yet because we need to install the MBR into the flash drive.
    I suspect that there is a way of doing this in Yast running from the Live CD but it was not obvious to me so I used the manual method that I have used before.
    Open a root terminal
    Mount /dev/sdb6 to /mnt/sdb6 (my linux root)
    Touch /mnt/sdb6/boot/grub/flag
    The purpose of this is when we go looking later at the grub command prompt we need an easy to find unique file
    Start grub and do the following
    #grub
                grub> find /boot/grub/flag
                    (hd1,5)    -- the result of the find in my example
                grub> root (hd1,5)   -- using the result of the find in my example
                grub> setup (hd1)   -- install mbr -- my example parameters - if you get this wrong you will trash some other drive!!!
                      hopefully grub announces success
                grub> quit
    Reboot and select the flash drive. In my case I still had the grub devicemap wrong and had to edit the grub commands during boot to tell grub how to find the correct partition and then edit them again after booting
    Typical linux install issues that we all always seem to have and can be solved with a little (or a lot of) google research.
    As I said at the beginning I now have an untouched windows installation and a nice fast Linux installation. I hope that this will be of some use to someone.

    Hi chrissh
    i tried this exact procedure... on the exact same notebook (T400s). However, as soon as I set the 
        Bios>config>Serial ATA to "compatibility", I cannot use my default Windows installation! I immediately get the "blue screen of death".
    I doubt I did anything differently since this is the first step of your procedure and my laptop is brand new!
    any idea? 

  • Qosmio G30: Booting from external ESATA HDD

    Dear All,
    I'm trying to boot from an external HDD connected with a express/34 card that has an BOOT feature. It works like a charm on a other manufacturers notebook because the express/34 card is recognized without problems. I can choose the external sata HDD as bootdevice.
    My Qosmio G30 BIOS (V3.5) seems not having this option. Any suggestions? Thank you for feedback!
    express/34 esata card: http://www.cooldrives.com/2saexcadues.html (ROM BIOS supports Boot Features)
    Regards,
    Nboss

    Hi
    Such boot options depending from the BIOS.
    The BIOS which is installed on the G30 does not provide such option. So unfortunately, but there is nothing to do!
    Best regards

Maybe you are looking for