Lenovo b50-70 UEFI and partitions errors

I just spent a pretty unlikely thing in my lenovo laptop.
It is this: http://www.pccomponentes.com/lenovo_...0gb_15_6_.html
It turns out that I wanted to install windows 8.1 again, because I need to sort things calling and other web programming. He was only Manjaro and doing quite well.
I went to put windows 8.1 and did not get it for UEFI, as I say, I install via legacy and ready, I need it now.
By having windows, updated BIOS 2.01 to 2.02 and was apparently well.
I installed Windows 8.1 and is very fast and well, a partition of 45gb and a 25gb data, both NTFS.
I tried to install Linux and says I have 120gb of free space (my entire SSD, 120gb samsung evo 84).
I was torn because several distros of linux tell me the same. Now what do to do a dual boot.
The facilities have been from pendrive with:
http://www.microsoftstore.com/store/...usbdvd_dwnTool
For Windows 8.1
http://unetbootin.sourceforge.net/
For different linux
They say several installers linux, there is a problem with the partition table, which is fixed by windows (of course).
The secure boot is disabled. And the UEFI BIOS in legacy + UEFI mode with priority.

Vladpaul,
Welcome to the Forums  
As per the query we understood that you are facing issue with BIOS update in your Lenovo B50-70 laptop.
We are checking with our team regarding the BIOS update, we will update once we have an information about the same.
Best regards,         
Ashwin. S

Similar Messages

  • Dual boot, UEFI and partitioning

    Got a new computer which I put my old disks in. After a while I got them to
    boot properly but I'm going to take the time to go from my current MBR setup to
    GPT.
    The idea
    I have three disks, 480GB SSD, 640GB HDD and 2TB HDD. The idea is to use the
    SSD for root and /home and then let the data on the 2TB be as it is (for now).
    I will go all LVM on the SSD and 640 HDD (except for a part which will be for
    windows 8). When I invest in a new disk (2TB) I will make the current 2TB LVM
    as well as that new one so that moving "partitions" (LVM volumes) easier
    if/when needed.
    Questions
    Will I still be needing something like syslinux/grub with UEFI? For the windows
    part, will that require some sort of EFI partition and should I create that or
    just leave 200GB + 500MB space at the beginning of the 640GB disk (and LVM on
    200.5GB-END)?
    If a bootloader is needed, can I put that on my SSD and still boot windows from
    the HDD in an easy fashion?
    Will there be any problems with having one disk still as MBR (I don't have the
    space needed for backing up those 2TB currently)?

    xintron wrote:Will I still be needing something like syslinux/grub with UEFI?
    Booting an OS always requires a boot loader. The details of what boot loaders are available varies from one platform and OS to another, but a boot loader is a necessity. My Web page, Managing EFI Boot Loaders for Linux, describes the options for booting Linux on an EFI-based computer. SYSLINUX and GRUB are both options, but there are others, too. My personal preference is to use the EFI stub loader with rEFInd, but as I'm rEFInd's maintainer, I'm not exactly unbiased.
    For the windows part, will that require some sort of EFI partition and should I create that or just leave 200GB + 500MB space at the beginning of the 640GB disk (and LVM on 200.5GB-END)?
    EFI systems require an EFI System Partition (ESP) to boot any OS. (An exception is EFI-based Macs, but they're just weird all around.) I recommend a size of 550MiB for the ESP. Many Arch Linux users like to mount the ESP at /boot, since that simplifies kernel management with certain boot configurations.
    If a bootloader is needed, can I put that on my SSD and still boot windows from the HDD in an easy fashion?
    Yes, at least in some sense. Boot loaders normally reside on the ESP, which is normally shared between OSes, although there are exceptions to both of these rules. The Windows C: partition is separate from the ESP. In theory, the two can reside on different disks, although in practice I'm not sure how the Windows installers and other tools would cope with that type of configuration. In theory, you can also have multiple ESPs (on the same or on different disks), although the Windows installer flakes out when there are multiple ESPs on a single disk. I'm not sure how the Windows installer copes with a system with multiple ESPs, each on its own disk.
    Note that putting the boot loader on the SSD is something of a waste, since the boot loader is normally accessed only during the boot process, so there's relatively little speed gain from putting it on an SSD vs. on a regular hard disk.
    Will there be any problems with having one disk still as MBR (I don't have the space needed for backing up those 2TB currently)?
    You can mix MBR and GPT; however, on an EFI-based computer, Windows must boot from a GPT disk. (In a conventional setup, this means that C: must be a partition on a GPT disk.) Some EFIs also require that the ESP be on a GPT disk, although I'm not sure how common this requirement is.
    It's possible to convert MBR to GPT without data loss by using gdisk, so you can easily convert your 2TB disk to GPT without doing a backup. This operation is actually safer than it might seem, since the MBR and GPT data structures are quite simple, so there's little that can go wrong compared to, say, resizing a partition. That said, there's still some risk, so if you're not booting Windows from the disk, you might want to just leave it as MBR. Also, some MBR-to-GPT conversions will require shrinking a partition, so you'd need to do that in GParted or some other tool before doing the conversion. Of course, you should always keep backups of important data.

  • MDT Config UEFI Specific disk and partition?

    Installing Win8.1 with MDT2013 on UEFI enabled machines everything seems to be ok.. Until... Injecting drivers. The deployment cannot proceed because of destination disk. Sounds obvious because Uefi makes multiple partitions unlike non-uefi that can be installed
    on the first partition.
    I've created an extra step to the "Format and partition disk" and named it "Format and Partition Disk - UEFI". In this step I've set an option "Task sequence variable IsUEFI equals True". So when it is "True" the step
    will format the drive in GPT (as is required for UEFI boot). This seems to work good. I see in the installation the step "Format and Partition Disk - UEFI" when it's a uefi machine, and the original step if it is a non uefi machine. Obviously the
    original step will have also an option "Task sequence variable IsUEFI equals False".
    The problem comes when we get to the step "Install Operating System". Here I made the same change like I did above. (added extra step with extra option:
    The original step "Install Operating System" will have install location: "Specific disk and partition"
    Disk 0 Partition 1.
    The added step will have install location "Specific disk and partition"
    Disk 0 Partition 3. (Because UEFI has multiple partitions)
    For some reason the deployment will accept the step "Format and Partition Disk - UEFI" but in the install step it will take the "Install Operating System - Legacy" (so it will try to install to disk 0 partition 1 as I see in BCD log).
    Is there any reason that the same condition  works at the format step and not at the install step?
    We choose the option install to "Specific disk and partition" because of problem when have the location set at "logical drive letter stored in a variable" (problem described:
    link)

    Solution in my case was going for the "logical drive letter stored in a variable" instead of "Specific disk and partition".
    Note when applying this: must keep using "OSDisk" variable or it will throw errors (problem described in
    this link)
    So I deleted the "UEFI" steps, and renamed the "Install Operating System - Legacy" to before. Removed the query for the IsUEFI variable. MDT will automatic install to MBR or GPT based on device.

  • Trying to install windows 7 and getting error message windows must be installed to a partition formatted as NTFS

    Trying to install windows 7 and getting error message Windows must be installed to a partition formatted as NTFS

    Welcome to Apple Support Communities
    Boot Camp Assistant creates a Windows partition in FAT32 to make the Windows XP installation easier.
    The problem is that Windows Vista, 7 and 8 require a NTFS partition, so the Windows installer gives this error. The only thing you have to do is to choose the BOOTCAMP partition in the installer and go to “Drive options (advanced)” > Format. Finally, install it

  • Error message on opening lenovo pc experience-support and downloads

    i have a lenovo thinkpad w540 and when i open lenovo pc experience - support and downloads , a error message windows pops up. the snapshot of the error message is enclosed for reference.
    CONSTRUCTION & PROJECT MANAGEMENT SPECIALIST

    hi,
    thanks for the reply. however, avoiding is not the solution.if there is a bug, it should be fixed by lenovo, elsr there is no need to install snaged softwares.
    anyhow, once you know the workaround, please share it with me.
    regards
    CONSTRUCTION & PROJECT MANAGEMENT SPECIALIST

  • Grub, UEFI, and encrypted partitions

    I followed the tutorials on the Wiki regarding setting up luks encryption over LVM which worked fine. Part of this process involved getting grub to decrypt the root partition, which also worked. However, I later went and followed instructions for getting UEFI boot to work; I created a separate /boot partition, used grub-install, etc. I'm now in a weird state, though: grub is still using (and unlocking) the root partition and using whatever is in its /boot directory when it really should be using the /boot partition. I've managed to confuse myself enough through all this that I'm not sure what config files and commands I need to mess with to get grub to load the initramfs from the actual boot partition while not also screwing up the root partition that should be unlocked/mounted by systemd.
    My common sense tells me that the latter has nothing to do with the former but it took me long enough to figure out the hack of copying everything in the boot partition to root's /boot just to get the thing booting again after a kernel update that I'd rather just ask here

    tcdavis wrote:I'm now in a weird state, though: grub is still using (and unlocking) the root partition and using whatever is in its /boot directory when it really should be using the /boot partition.
    UEFI and a dedicated /boot partition are separate things, and they are not dependent on one another. The problem is most likely coincidental.
    Make sure your "root=" and "cryptdevice=" kernel parameters are correct. Edit /etc/default/grub, and use the UUID of the LUKS container on the new /boot partition, replacing the old UUID of the root filesystem. This should be the UUID of the LUKS container itself, not the filesystem contained within it. Use `cryptsetup luksUUID /dev/sda2` substituting sda2 with your /boot partition. This only applies to the kernel and is not directly related to GRUB, so it's just a precautionary measure.
    Make sure /boot is mounted, and regenerate grub.cfg:
    mount /boot
    grub-mkconfig -o /boot/grub/grub.cfg
    Delete the contents of /boot on the root partition to prevent confusion:
    umount /boot
    rm -r /boot
    mkdir /boot
    mount /boot
    Also make sure your /boot partition is being mounted (via crypttab and a keyfile) automatically at boot, or you will run into problems later on.
    Strike0 wrote:If you, in your first attempt, installed grub to the MBR and your bios is set to dual legacy/uefi, the grub bios may take precedence now. You should boot the machine/install ISO in pure efi mode before executing the grub install for uefi and best wipe the grub bios which probably installed itself to sectors before the first partition.
    I don't know enough about the GRUB internals to say whether or not the UUID of the /boot partition is embedded in GRUB's UEFI stub, but in theory the following commands should overwrite both the BIOS boot loader and UEFI.
    mount /boot
    grub-install --target=i386-pc --recheck
    grub-install --target=x86_64-efi --efi-directory=/boot/efi --bootloader-id=grub_uefi --recheck
    This way GRUB should use the correct /boot no matter if it is booting in BIOS or UEFI mode.
    If these instructions don't solve your problem, please specify what stage of the boot process is failing, and what you saw prior to the boot failure (e.g. did you get a GRUB rescue shell? Did you see the GRUB menu? Did GRUB indicate an incorrect UUID?)

  • Lenovo S10 start-up problem and possible error code

    Good day,
    Two days ago I purchased our second S10 system.  I liked the system previously purchased for my son and decied to pick one up for myself.  I purchased a Lenovo DVD-ROM drive and a 2GB Kingston memory DIMM, pn KVR667D2SO/2GR.  Everything worked fine out of the box and during the first 24 hours of ownership I did the following, in the following order, without incident.  During these installs the DVD-ROM was attached to and powered by the right USB port
    Installed PKunzip
    Installed Microsoft Office 2003
    Installed Microsoft Visio 2003
    Installed Microsoft Project 2003
    Installed all available Microsoft service packs and urgent updates related to these products as well as for XP
    Uninstalled Avisys v6.0 and the current update to v6.0H
    Installed Thayer Guide to Birds of North America v3.9 and the current update to v3.9.5
    Installed Garmin MapSource North America v6 and upgrade to v8
    Attached a Seagate GreeAgent Go 500GB USB hard disk via the left USB port.
    Installed the Kingston 2GB DIMM
    Besides rebooting during the required prompting during these software installs and update installs, I rebooted and shutdown the laptop numerous times without incident.  Internet and intranet access was through the wireless ethernet port.  The first night of ownership I left the laptop powered up and it went in sleep-mode as expected.  Everything has worked flawlessly and as expected.  I used the laptop throughout the day for internet access, trying the RJ45 port for network access to test its functionality.
    The second night it was powered off and left unplugged from its power cord.  I carried the device in my cushioned briefcase to and from my car and my destination, never removing it from my bag.  Went I got back home last night the laptop would not power up.  I have tried removing/re-inserting the battery, powering the device without and without the AC cord plugged in.  I have tried reseating the internal hard disk.  I have even replaced the 2GB RAM DIMM with th eoriginal 512MB DIMM that came installed with the laptop.  Nothing is connected to either USB port and nothing is connected to the RJ45 port when I try to power up the laptop.
    I am getting the same error result each time I try to power up without the AC cord - the right-most front panel light remains on and blue while the center front panel light flashes six (6) times as orange.  When the AC power cord is connected the center front panel light remains on and orange.  When I press the startup button the right-most front panel light remains on and blue but the laptop does not start.
    Can anyone tell me what various front panel errors conditions can be expected, and what problem(s) they might represent?  I purchased this laptop from Circuit City the day before they formally announced their plans for liquidation.  I would expect that the store will give me a hard time if I try to return or exchange the laptop.  Also, with all the time and energy I've already invested in this particular laptop, I'd hate to have to go through this installation all over again.
    Thanks in advance,
    David

    A couple of things to try: 
    Try using the one-touch recovery button to see if your machine boots...or...press F2 repeatedly for a few seconds after pressing the power button to see if you can enter the BIOS setup.
    Remove the 512MB DIMM and try to boot with the onboard memory only.
     Press the space bar repeatedly after pressing the power button - hibernation problem.
    Message Edited by PeZzy on 01-18-2009 11:28 AM

  • Windows 7 auf dem Lenovo B50-30

    Guten Tag. Nachdem ich mir kürzlich ein Yoga Pro 3 gekauft habe und mich mit Windows 8.1 so gar nicht anfreunden kann, habe ich mir noch dieses große "Sparbrötchen" Lenovo B50-30 gekauft. Das wird ebenfalls mit Windows 8.1 ausgeliefert, aber ich hatte gesehen, daß es dafür Windows 7-Treiber gibt. Sicher nicht grundlos. Tatsächlich konnte ich Windows 7 Home Premium 64bit mittlerweile installieren, und es läuft recht rund. Aber ein paar Geräte werden mir im Gerätemanager noch als "Unbekannt" angezeigt. Da das B50-30 derzeit recht günstig angeboten wird, hoffe ich, daß vielleicht noch andere mit diesen Problemen zu kämpfen haben. Wo gibt es die restlichen Treiber, die ich noch benötige?

    Die Fehlermeldung hatte ich nicht. Ich bin allerdings so vorgegangen, wie in den Artikeln, die ich mir aus dem Netz kopiert habe. Und wenn gar nichts hilft: Festplatte ausbauen (geht total easy), in ein externes Gehäuse packen, an einen anderen PC anschliessen und von dort aus Partitionen löschen. Aber erstmal folgendes machen: Re: B50-30 problem with install windows 7Options‎10-03-2014 03:38 AM1. In BIOS select exit menu2. Load DEFAULT SETTINGS3. Find OS optimized defaults, make sure OTHER OS is selected!4. Select Boot option menu5.Make sure BOOT FROM LEGACY is enabled6. REORDER BOOT DEVICES INSTALLING WINDOWS 7 IIF YO CANNOT INSTALL WINDOWS (Windows cannot be installed to this disk. The selected disk is of GPT partition style). FOLLOW THIS TUTORIAL https://www.youtube.com/watch?v=DQf9YqbD8WI   The solution is this.... I bet you are Getting the ACPI Error like this... Link to image Step 1: Shut down your Laptop. Step 2: Find the small NOVO button on Left side of your Laptop near the Power cord Point. Press the button. The System loads Boot Options.. Step 3: Click on the BIOs Setup Option. A Blue screen menu appears use arrow keys to navigate to Exit option and select                OS optimized Defaults to Win  7 ( The Default is Windows 8 64 Bit) Step 4: If you are about to Install a Fresh Copy of Windows 7 Then Goto Configuration Tab and Change                USB Mode to USB 2.0 (Original may be USB 3.0)               In case you are already Running Windows 7 and the Problem was caused by Updating Your BIOS then                Then rest the Bios by using the option given in the Status Bar. Step 5:  Goto Exit and Select Exit Saving Changes. Select Yes The problem should be gone.. and if It doesnt... Be Patient. Open BIOS Settings again and tweak around... Boot Mode or Boot Priority etc. * Please refre to this Document -http://download.lenovo.com/consumer/hnt/lenovo_g40_30_g50_30_bsod_solution.pdf Hier: https://forums.lenovo.com/t5/Lenovo-B-and-G-Series-Notebooks/Windows-7-install-on-Lenovo-B50-30/td-p/1654059  To Install Windows 7:
    1 Run BIOS by pressing Novo button
    2.Go to Exit menu
    3. Make sure that OS Optimized Defaults is set to "Other OS". If not - select it
    4. Select Load Default setting above OS Optimized Defaults and confirm loading.
    5. Set Boot Mode to "Legasy Support" in Boot menu. Boot Priority could be set to "Legacy First" as well.
    6. Go to Exit and Exit Saving Changes
    7. Press Fn+F12 during Lenovo Logo to select boot source, then select your ODD (or USB) with Windows 7 Instalation disc.
    8. Press any key to start Windows 7 Instalation wizard.
    Now you can install Windows 7 including setting up new HDD partition(s) inside Windows 7 standard installation Wizard,

  • SSD with caddy on Lenovo B50-70 Laptop not recognized by Windows 8.1

    Hi all.
    I just bought a B50-70 laptop and I thought I upgrade it with a SSD. I bought a caddy and a 120GB Kingston Hyper X Fury and I installed it in the DVD-ROM slot after removing the DVD drive. The problem is that Windows 8.1 does not properly detect this drive. Under Disk Management in Administrative Tools, the drive shows up with a down red arrow and when I try to create a MBR on it, an error message pops up with an I/O error. I have the latest BIOS firmware from Lenovo.
    A Windows 8.1 installation disk does not recognize this drive as a valid on to install the OS on. The SSD works fine in another PC and it is properly detected by the B50-70 BIOS. My question is: does the B50-70 actually support a SSD via a caddy instead of the DVD-ROM? What can I do for this drive to work?
    Please help!

    TudorS wrote:
    Thanks for the hint. However, opening up the case to reach the HDD will void the warranty for the notebook.
    Really? How's that? Do you have any sticker (paper or plastic) anywhere or covering some of the parts that you would have to disassemble in order to reach for and change the HDD? Unless you have one of those, I don't see how it could void your warranty. 
    Didn't you face the same problem when changing the DVD-RAM drive with the caddy?
    I'm more interested to know if there's a specific issue with this laptop and caddys before I start thinking about waiving the warranty and tinkering with it. I found a similar issue on a dutch forum: http://gathering.tweakers.net/forum/list_messages/1600861  which might indicate a recurring problem.
    I don't know about caddies that much, but isn't there a SATA to ATAPI kind of connector for it? I mean, did the DVD-RAM drive have a SATA connector just as a HDD has? Or is there a small controller over there, in your caddy, which converts from SATA to ATAPI.That might be a problem, in my opinion, however, I did not study this potential incompatibility issue with the adaptor, but it might be suspect. 

  • Surface Pro 2 freezes briefly - storachi and disk error

    Hello tech net
    I am running a surface pro 2 with windows 8.1 (updates current as of 3 days ago), 4 GB RAM, 64GB HD.  For the last several months the device will freeze up for about 5-10 secs multiple times per hour, and then resolve on it's own.  During that
    time task manager shows the disk is at 100% and event viewer will display 2 Warnings: an storachi (129) and a disk (153) error.  This is in addition to a service control error (7000) that happens multiple times per second but doesn't seem to
    affect performance.  These freezes happen when plugged in, on battery, SDXC card installed or not, wi-fi or not, and no particular program running. It even happens when I'm not using the device if I go back thru event viewer.  The 100% on disk is
    not associated with any increase in process or app activity.  Most of the time there are a couple 0.1MB/s demands like outlook, explorer or service host running but nothing that looks unusual when it spikes and freezes.
    I am not a tech person and my online search for help has yielded a wide variety of solutions to this problem that didn't seem to be reliable fixes and sounded a little beyond my usual capabilities.  Anyone know if this is fixable or do I need to send
    the device back?
    Thanks!

    Not much information here to go on. Can you supply the bdd.log file. Copy to a public share like OneDrive, and share the link.
    Typically any problems with format and partition have to do with the storage driver. Are you using the latest ADK from Microsoft? As Surface Pro 2 only supports Windows 8.x, you should *only* be using uEFI mode and GPT.
    THe default MDT Task Sequence will do the right thing, *however*, if you change the settings in the "FOrmat and Partition Disk" step, you are then responsible for the settings from then on.
    Keith Garner - Principal Consultant [owner] -
    http://DeploymentLive.com

  • Windows 7 install on Lenovo B50-30

    Hello Everyone,
    I suggested to a school that they invest in some Lenovo B50-30s as they were cheap and cheerful and would do what they needed.
    I checked the Lenovo driver site and saw that there were windows 7 64bit drivers available, so presumed I would be able to downgrade them to fit their domain setup.
    I have tried every different bios configuration, even taken the HDD out and installed win 7 64bit and checked it booted in another system and it was fine, put it back in the Lenovo and it just gets to the point where the Win 7 dots appear as they create the windows boot picture, then it blue screens and says the bios in this system is not fully acpi compatible.....which is what it says when trying to reload from every kind of media known to man.
    Is there a genius out there who can save me many more pain staking hours of grief and tell me what to do please, the bios in this system is so basic its unreal, you can choose boot device priority and achi/ide/compatability modes etc, but thats about it.....what happened to ram voltage settings etc that I used to enjoy messing about with.
    If anyone can figure this, I will buy you a pint!! I'm hoping in the words of Barney Stinson....."Challenge accepted!!"
    Thank you in advance.
    Andy

    Hello,
    Sorry for my english, i'm french.
    I have the same problem.
    I use a CD of windows 8 to delete all system partition.
    After ther is no soucy to install windows 7
    I hope it can help you
    Regards
    Manu

  • Problema al iniciar Lenovo B50-30 Checking media...

    Hola!
    Hace tiempo que tengo este Lenovo B50-30 (80ES) que me venía con Windows 8. Lo pasé a Windows 7 de 32bits, lo cual tuve que volver a cambiarlo por el de 64 bits esta mañana. El error viene cuando después de pasarlo al formato de 64 bits que era el indicado, al terminar el formateo todo normal, el fallo comenzó cuando empecé a instalar los Controladores, al intentar instalar "BIOS Update Utility exe" (O al menos pienso que este pudo ser el último que intenté instalar antes del fallo) La cuestión es que la aplicación me pedía que no utilizara la batería para ejecutarla y que conectase el cargador. Hecho esto, comenzó a instalarse hasta que me apareció una pantalla negra con unas letras en rojo, tras cargarse por completo, lo siguiente que apareció fué:
    El logo de Lenovo y después una pantalla negra que dice"Checking Media..." Tras esto, una ventana azul que dice:
    "Default Boot Device Missing or Boot Failed.
    Insert recovery media and hit any key
    then select "boot manager" to choose a new boot device or to boot recovery media"
    Seguido de la opción [OK], al presionar me lleva a un página de fondo blanco que pone "BOOT MANAGER" debajo; Boot option Menu y solo a poder elegir una opción: "EFI PXE NETWORK", pulso Select y: de nuevo "Checking media..." Solo que ahora en una ventanita azul dice:
    "EFI network 0 for IPv4 (F0-76-1C-19-33-D5) boot failed, Y después este mensaje se repite si sigo presionando [OK]
    Llegué a deducir por lo de IPv4 que necesitaría conexión a internet, por lo que cunecté el cable al ordenador y esto solo cambió la respuesta del cuadro, supongo que dando otro fallo, pero ninguna otra opción que no sean las que ya he dicho.
    La cuestión segun he leido parece fácil de solucionar, pero mi verdadero problema recae en que no puedo acceder a la BIOS de ninguna de las maneras. Mi portatil no tiene ese botón para acceder a la BIOS, supongo que hay que hacerlo mediante F12, aunque los he probado todos, y al salir el Logotipo de Lenovo intento acceder a la BIOS y no me deja. 
    No sabría deciros si instalé el controlador de la Bios, si era el controlador propio de la Bios el que me ha dado este fallo, no sé. No estan todos los Drivers instalados, ya que este era de los 3 primero que me descargué por orden de la página y me salió el fallo este que no me deja acceder a Windows. 
    La verdad es que estoy un poco desquiciado con este error, asique agradecería muchiiisimo una ayudita. Y aunque no se supiera solución, otra duda es que si podría Re-formatearlo para solucionar el problema. La cuestión es esa, que no puedo Acceder a la BIOS y no se siquiera si lo podré formatear.
    Gracias de antemano por dedicarme unos minutillos
    ¡Resuelto!
    Ir a solución.

    Para el caso 2 en el que que modificas la BIOS a legacy el disco duro aparece para el orden de arranque, con esta configuración Windows no carga normalmente verdad? mismo mensaje mostrador desde un inicio, recomendable en la pestaña exit verificar que en las preferencias de sistema operativo, este para Windows 7 en el caso de no estar este parámetro colocar en otros.
    Si con esto persiste el mensaje problema, intenta arrancar el instalador de Windows 7 y verificar si el disco duro, para intentar verificar si es que el problema es debido a error en el arranque de Windows o de plano no tienes ningún sistema en disco que arrancar.
    Un saludo.
    @Antony_Vamu
    Comunidad en Español  English Community  Deutsche Community  РусскоязычноеСообщество
    Mis Lenovo: Y560p,Z580,Z500 touch,S920,T400,G50-70 ,Soy voluntario no trabajo para Lenovo, las opiniones expresadas por mi no representan a Lenovo, no se responde a preguntas de manera privada debes crear un nuevo tema, números del centro de llamada Lenovo Aquí , reglas de participación del foro Aquí , si encontraste solución a tu problema marcarlo aceptándolo como solucionado!!!!!

  • Time Machine won't back up. Starts of REALLY SLOW, and the errors out.

    I've been having a hard time getting time machine to back up. To start off I'll give you my specs and what I have done.
    iMac
    OS 10.6.6
    2.4 GHz Intel Core 2 Duo
    4 GB 667 DDR@ SDRAM
    320 GB HD
    All software updates are current. I am trying to back up to an external Western Digital 1 GB drive connected by USB2. I have formatted the external drive, and set a single partition on that drive from the Disc Utility. I have run disk repair on both the external and local hard drive. I have run disk repair permission on the local drive. I have restarted, after every time. I have done everything listed above multiple times, and have done them all in kinda different orders each time.
    My thought is that the issue may not be with the hard drives, but maybe a file its trying to back up. When it starts out for the first time, it tells me that it needs to back up over 100 GB of data. It gets about halfway done, and then errors out. When I try to start it again, it tells me that it needs to backup around 50 GB of data. And this time, its REALLY slow. Like bytes slow, not Mega bytes, or even kilobytes. Bytes. 36 bites backed up, 120 bytes backed up. 2 Kilobytes backed up. SLOW SLOW SLOW.
    Then it picks up, and usually gets up to 120 MB, and then gives me this error message "The Backup was not performed because an error occurred while copying files to the backup disk. - The problem may be temporary. Try again later to back up. If the problem persists, use Disk Utility to repair your backup disk."
    Its a pretty generic message, and gives me no help in trying to figure out what the problem is. I've been trying again for almost 3 days now, and nothing is working. Is there an error log file that I can go find that would help me a little more?

    woody24 wrote:
    "The Backup was not performed because an error occurred while copying files to the backup disk. - The problem may be temporary. Try again later to back up. If the problem persists, use Disk Utility to repair your backup disk."
    See #C3 in [Time Machine - Troubleshooting|http://web.me.com/pondini/Time_Machine/Troubleshooting.html] (or use the link in *User Tips* at the top of this forum).
    Its a pretty generic message, and gives me no help in trying to figure out what the problem is. I've been trying again for almost 3 days now, and nothing is working. Is there an error log file that I can go find that would help me a little more?
    Tell Apple about the inadequacy of that message: http://www.apple.com/feedback/timemachine.html

  • Stumped On How To Fix HFS+Partition Error!! Help!

    WEll hello and i am having so much trouble with my mac software. My current setup is as follows.
    -Windows XP Home Edition Installed As Base OS
    -80GB Hard Drive Partitioned
    -65GB Windows NTFS Partition
    -15GB Mac Partition
    -Intel Celeron Processor
    -Multiboot Software Set Up As Well
    Here's my problem. I made all the partitions correctly and installed the Mac software onto my pc with already had Windows XP installed on it. The install went smoothly and the disk was mounted and formatted correctly. But after the install of the Mac OS I restart my pc and boot into Mac. Immediatly a message comes up saying HFS+ Partition Error. I have tried tons of things to fix it but everywhere I go it tells you have to fix erros related to intalling Windows onto a Mac. But luckily my Windows Xp still boots up fine. Someone out please help me!!
    Great appreciation if ya do
    Toshiba Satellite Laptop   Mac OS X (10.3.2)   Windows Based PC, Intel Celeron Processor

    Hi Steel Raptor;
    What you are trying to do is illegal. Asking for help here is not a good thing since this forum is an Apple sponsored site.
    Allan

  • Task Sequence Windows Server 2012 format and partition issue when using MDT2012

    Hi all,
    Currently I'm working on a task sequence to deploy a Windows Server 2012 image. We've integrated MDT2012 Update 1 in SCCM2012 SP1 and created a default 'Server Task Sequence'. This task sequence deploys the install.wim to a server which has multiple disks
    attached.
    We've configured multiple format and partition disk steps to create the following partition layout:
    Disk 0: 499MB BDEDrive (do not assign drive letter) + 40GB OSDisk
    Disk 1: 40GB Programs
    Disk 2: 40GB Data
    Disk 3: 25GB User
    When the task sequence is finished I've noticed the drive letters assigned to the disk are not correct. In some cases the BDEdrive gets drive letter D assigned, sometimes drive letters are assigned starting with E, thus skipping drive
    letter D. 
    The smsts.log files show an error when it's re-assigning drive letters after booting into Windows. Looks like an error in the DiskPartScript.txt.
    <![LOG[==============================[ OSDSetupHook.exe ]==============================]LOG]!><time="16:59:40.889-120" date="05-10-2013" component="OSDSetupHook" context="" type="1" thread="776"
    file="osdsetuphook.cpp:186">
    <![LOG[Executing task sequence]LOG]!><time="16:59:40.905-120" date="05-10-2013" component="OSDSetupHook" context="" type="1" thread="776" file="osdsetuphook.cpp:279">
    <![LOG[Loading the Task Sequencing Environment from "C:\_SMSTaskSequence\TSEnv.dat".]LOG]!><time="16:59:40.920-120" date="05-10-2013" component="OSDSetupHook" context="" type="1" thread="776"
    file="basesetuphook.cpp:366">
    <![LOG[Environment scope successfully created: Global\{51A016B6-F0DE-4752-B97C-54E6F386A912}]LOG]!><time="16:59:40.936-120" date="05-10-2013" component="OSDSetupHook" context="" type="1" thread="776"
    file="environmentscope.cpp:659">
    <![LOG[Environment scope successfully created: Global\{BA3A3900-CA6D-4ac1-8C28-5073AFC22B03}]LOG]!><time="16:59:40.936-120" date="05-10-2013" component="OSDSetupHook" context="" type="1" thread="776"
    file="environmentscope.cpp:659">
    <![LOG[Debug shell is enabled]LOG]!><time="16:59:43.806-120" date="05-10-2013" component="OSDSetupHook" context="" type="1" thread="776" file="basesetuphook.cpp:1440">
    <![LOG[Successfully enabled debug command shell support.]LOG]!><time="16:59:43.884-120" date="05-10-2013" component="OSDSetupHook" context="" type="1" thread="776" file="debugwindow.cpp:156">
    <![LOG[Configuring local administrator account]LOG]!><time="16:59:43.884-120" date="05-10-2013" component="OSDSetupHook" context="" type="1" thread="776" file="basesetuphook.cpp:1462">
    <![LOG[Re-assign all drive letters...]LOG]!><time="16:59:43.884-120" date="05-10-2013" component="OSDSetupHook" context="" type="1" thread="776" file="diskutils.cpp:1941">
    <![LOG[Executing command line: "C:\WINDOWS\system32\diskpart.exe" /s "C:\WINDOWS\TEMP\DiskPartScript.txt"]LOG]!><time="16:59:43.900-120" date="05-10-2013" component="OSDSetupHook" context=""
    type="1" thread="776" file="commandline.cpp:827">
    <![LOG[Process completed with exit code 2147942487]LOG]!><time="16:59:50.249-120" date="05-10-2013" component="OSDSetupHook" context="" type="1" thread="776" file="commandline.cpp:1123">
    <![LOG[Diskpart.exe STDOUT:
    Microsoft DiskPart version 6.1.7601
    Copyright (C) 1999-2008 Microsoft Corporation.
    On computer: SRV03
    Volume 1 is the selected volume.
    DiskPart successfully removed the drive letter or mount point.
    The volume you selected is not valid or does not exist.
    There is no volume selected.
    ]LOG]!><time="16:59:50.249-120" date="05-10-2013" component="OSDSetupHook" context="" type="3" thread="776" file="diskutils.cpp:1807">
    When I take a look at the generated diskpart_script.log file the volume D gets selected twice, which fails the second time because of the first remove drive letter command.
    This is the output in the diskpart_script.log file:
    select volume D
    remove letter=D
    select volume D
    remove letter=D
    select volume E
    remove letter=E
    select volume F
    remove letter=F
    select volume H
    remove letter=H
    select disk 0
    select partition 1
    assign
    select disk 1
    select partition 1
    assign
    select disk 2
    select partition 1
    assign
    select disk 3
    select partition 1
    assign
    It seems this error is caused by the first 'Format and Partition Disk' step before the 'Use Toolkit Package' step which is part of the default Server Task sequence. When I disable this Format and Partition step and create the partition manually
    all looks ok showing no errors in the smsts.log file.
    I've solved this by replacing the first 'Format and Partition Disk' step by an Powershell command which formats and partitions the disk. 
    Anyone seen this behavior?

    I have a similar problem when I install windows on some clients. Have you found any explanation for the behavior?

Maybe you are looking for