2100: Detection error on SSD0 (M.2) -- X1 Carbon 2014

I keep on getting this error on the X1 Carbon, attaching picture.
If it stays on for a long time, 8 hours and more it will show, consistently.
Anyone else had this problem ? found a fix ?
Its brand new and it started showing since day 1

lenovo support 06/22/2014 filed a support request and this is what I was told:
- Replacement : Not possible after 30 days  
- Loaner : Not possible at Lenovo
- Technician on site : No Unless you purchased an onsite warranty
- Business Partners : available but they will charge  
- Replacing SSDD is not recommended its fragile and if the laptop is opened the warranty dies
So the only option
- Shipping back the unit for repair : available they will fix it since its under warranty
This is an expensive laptop that happen to have HW issues. I could have sent it back for repair no problem but my work obligations are keeping me from doing it

Similar Messages

  • T450s: 2100: Detection error on HDD0 (Main HDD)

    Hi,I got T450s with 500GB HDD which I replaced with 500GB SSD Crucial MX200.After installing Windows 8.1 Pro, turning on bitlocker and restarting machine, I saw black screen with white text: 2100: Detection error on HDD0 (Main HDD) usually if I power off laptop and turn it on again, problem gets solved and I can start Windows, but then after restarting computer again the error is usually there again... I've noticed that if I turn off the bitlocker, the problem doesn't appear (at least I wasn't able to encounter it without bitlocker). I saw threads about similar problems with this and other thinkpad models as well as crucial and samsung SSDs, but none was actually reporting that it may be connected with bitlocker functionality... (I can't be 100% sure it is, but so far it looks like it). any idea how I can fix it so that it works also when bitlocker is enabled? Thanks!

    I have exactly the same problem too with a T550 and a 1TB Crucial MX200. Did you ever find a solution? I'm tempted to return the MX200 and try a Samsung 850 EVO instead.

  • 2100: Detection error on HDD0 (Thinkpad Yoga)

    I have a Thinkpad Yoga which today was turned on while I was away (i.e. computer was not in use). When returning back the screen said "2100: Detection error on HDD0 (Main HDD)". Windows must have crashed (probably just another one of those faulty Lenovo drivers) and then the system couldn't boot up.
    Everything seems alright after a hard reboot but I'm afraid my SSD drive has gone bad.
    Link to image
    Found a support document of the error on Thinkpads with Samsung SSD, but mine have a LiteOn. Can anyone help me find out why this happened and if anything is wrong with my SSD?
    Thanks,
    // Måns
    The support document I'm talking about: http://support.lenovo.com/us/en/documents/ht082504
    Moderator note: large image(s) converted to link(s):  About Posting Pictures In The Forums

    Hi guys,
    had the same error and found out, that the cable from Motherboard to HDD controller was not plugged in correctly.
    After plugin correctly the error disappeared.
    Hope to help you.
    BR, David

  • W520: PNY XLR8 240GB SSD with error "2100: Detection Error on HDD0 (Main HDD)"

    When I try to boot my W520, I get a BIOS boot up error : "2100: Detection Error on HDD0 (Main HDD)". I am using PNY XLR8 240GB SSD.
    It worked fine for a month.
    I also have PGP installed and whole disc encrypted.
    I installed an update of Intel Management Engine Firmware and Intel Chipset, both are the latest from lenovo site because I was experiencing expreme slowness from my harddrive. Programs would freeze. Webpages would take forever to load..
    The next time I rebooted, I got the error. If I leave the SSD out for a bit, and put the SSD back in, the disk will work for some time... but on next reboot, it is again detection error..
    TRIM is enabled on my system. I am not sure how the SSD died so quickly.
    I am back to using my HDD but I am not happy. I want a solution... is this a intel chipset issue? Intel IMEI issue? Is  the PNY SSD just a bad model?
    I've googled plenty and dont really see a solution. Sometimes there is a firmware update.. PNY has no firmware updates for my drive.. I don't see anybody else using PNY on their W520, but plenty of people are experiencing Error 2100 with SSD on their W520.. somethings fishy..
    help please! thanks in advance !

    No go, the drive is in there pretty firmly, a tech support to PNY said they are going to replace my drive.
    They came to the same conclusion I did - which is that the drive is toast..
    Drive slow downs and eventually unable to detect points to this.. I was hoping for some firmware update. I am really surprised an SSD died because I thought the whole point of them - no spinning parts - would make them last longer.. but there is some sort of logic board and maybe the flash drive itself went kaput.. who knows. 
    They do have 3 year warranty on my mode and i'm happy to take it. Luckily my old HDD was still around and works.. so thats what i'll be using for the next few weeks while I ship this to them and have them send me a new one.
    I asked about Advanced replacement, which is when they send me a new one before they recieve my current ssd. They said the Advanced replacemenet costs $30, and they would need credit card info to place a charge of the original amount for the drive incase I didnt send in the drive too. So it would cost me $30 plus temporary $100-150 or so... which I opted not to do... So I wait now for a few weeks. I dont know if I'll get another PNY drive in the future. OCZ has faired pretty well for me, I've had 3 of them work on desktops/laptops flawlessly. 

  • 2100: Detection error on HDD0 (Main HDD)

    I have a Lenovo ThinkPad Yoga, with a 256GB SSD and an i5 processor.
    I received it on April 29. After two weeks of normal use, it crashed and gave this error:
    “2100: Detection error on HDD0 (Main HDD)”
    I could not get it to boot. I took it to a computer repair shop and they (Lenovo warrantee) replaced the SSD. It worked for about a week, then crashed again, same error. My tech guy said that it might be a bad board, frying hard drives; but Lenovo insisted on replacing the hard drive again. Ten days later, same crash. I unplugged it and put it on a shelf for the weekend, intending to take it back to the shop. Monday morning I plugged it in and it started up normally.
    It has been working normally for three days, but I am worried about getting the same error and crash. Can you tell me what might be happening, and if there is anything I can do to prevent a recurrence?
    This seems to be a common problem across many machine models, but I haven't found any solutions to it.
    Solved!
    Go to Solution.

    Thanks!
    Funny, my post was dated 7/15/2014.  That article is dated 7/17/2014.  Someone might be listening
    http://support.lenovo.com/en_US/detail.page?DocID=HT082504
    Will test it out, hopefully it works.
    -Sloppy

  • X240 2100: Detection error on HDD0 (Main HDD)

    Hi all,
    I replaced original HDD on SSD 250 GB and formatted built-in Toshiba SSD-disk 20 GB . On 250 GB SSD installed Windows 8. And after turn on notebook I get "2100: Detection error on HDD0 (Main HDD). Press Esc to continue". If press "Esc" then there is boot menu, contain 2 point: ATA HDD2 Toshiba and PCI LAN. But after ALT+CTRL+DEL begins normal loading Windows 8.
    Any ideas why?

    Count me in... 
    Crucial M550 1TB SSD...
    It is fine after reboot, I got this laptop on Wednesday and just doing stability testing since this morning...
    I left home ~1pm with the Lenovo hardware testing software running, and came back ~7pm... not even half day...
    I just finished the same hardware testing, no 2100 yet... will leave it on overnight.
    My client is waiting for this laptop... I can't wait for replacement... either refund or firmware to fix it.
    Why is that so hard to get a decent PC laptop these days?! Even we are willing to pay for the money.
    EDIT:
    x240 config - Upgraded to
    8GB RAM
    Intel 7260 BT ACBGN
    X240 12.5FHD IPS MT WWAN
    X240 Intel i5-4300U

  • T530 2100: Detection error on HDD0 (Main HDD) SSD Mushkin Chronos Deluxe

    Sometimes i get this error when i start my Thinkpad T530 (Cold Boot and also with a reboot). Could Someone give me advise on this all update and firmware updates are installed also on my SSD drive
    Manufactor: Mushkin
    Type: Chronos Deluxe       
    Model : MKNSSDCR480GB-DX
    Firmware : 504ABBF0
    Serial Number : MKN1243A0000135952
    Link to image
    Moderator note: large image(s) converted to link(s):  About Posting Pictures In The Forums

    Hi Michael222,
    Welcome to Lenovo Community!
    As per the query we understood that you are facing an issue with HDD detection on your ThinkPad T530.
    Have you checked updating system BIOS?
    Is the system is having both HDD and SSD?
    Check with reseating the drives.
    Best regards,
    Hemanth Kumar
    Did someone help you today? Press the star on the left to thank them with a Kudo!
    If you find a post helpful and it answers your question, please mark it as an "Accepted Solution"! This will help the rest of the Community with similar issues identify the verified solution and benefit from it.
    Follow @LenovoForums on Twitter!

  • Detection Error 2100 - Lenovo X240 with Crucial M500 SSD

    I have a new Lenovo X240 out of the box.  I immediately upgraded with a Crucial M500 SSD 240mb drive.  The computer is running a fresh install of Windows 7 64-bit. The BIOS on the laptop is the most current.  The firmware on the M500 is the most current.  It seems that every several times I start or reboot the system I receive "DETECTION ERROR 2100".  After powering off the machine and powering it on again the computer will boot to Winddows.
    I have seen numerous posts about this issue between Crucial vs. Lenovo.  I've tried every suggested fix to no avail.  I have tried the configuration using an identical, brand new M500 SSD with the same results.  Am I missing something?
    Thanks in advance for your suggestions,.

    Hi Mrtree,
    Welcome to Lenovo Community Forums!
    I’m sorry to hear that you are facing the issue with SSD drive on ThinkPad X240.
    Regarding the issue we have got the same thread in the forum, but it is different model.
    I suggest you to chect with the below link to follow the further troubleshooting steps.
    Please click here to visit the page, and proceed with the steps provided in that.
    Hope this helps. Do post back if issue persists!
    Best regards,
    Hemanth Kumar
    Did someone help you today? Press the star on the left to thank them with a Kudo!
    If you find a post helpful and it answers your question, please mark it as an "Accepted Solution"! This will help the rest of the Community with similar issues identify the verified solution and benefit from it.
    Follow @LenovoForums on Twitter!

  • Detection Error 2100 - M500 SSD in Lenovo X240 laptop

    I have a new Lenovo X240 out of the box.  I immediately upgraded with a Crucial M500 SSD 240mb drive.  The computer is running a fresh install of Windows 7 64-bit. The BIOS on the laptop is the most current.  The firmware on the M500 is the most current.  It seems that every several times I start or reboot the system I receive "DETECTION ERROR 2100".  After powering off the machine and powering it on again the computer will boot to Winddows. I have seen numerous posts about this issue between Crucial vs. Lenovo.  I've tried every suggested fix to no avail.  I have tried the configuration using an identical, brand new M500 SSD with the same results.  Am I missing something?
    Thanks in advance for your suggestions,.

    Hello mrtree and welcome to the Crucial forum. I spotted your post yesterday and spent some time Googling for info from the Lenovo support forum last night. I found several things you are probably aware of. First, this Detection Error 2100 is not limited to just the X240 series laptops, there are quite a few other models affected in the same way. Second, it is not limited to only Crucial SSDs, there are people with Samsungs, Toshibas, Intels, and even conventional drives that have experienced this same problem at system boot. These two observations indicate to me that problem is probably related to BIOS/firmware/driver issues. Since you have stated that you already installed the latest BIOS(v. 2.23?) and firmware(chipset v. 9.5.22.1760?), that leaves one area: drivers. From what I can see, the latest Intel RST drivers available are version 12.8.10.1005, dated 1/26/2014. Please be aware that there are seperate downloads for 32 and 64 bit systems. There is also a Solid State Drive Firmware Update Utility listed, but I do not recommend using it since Crucial M500s are not listed in the "Read Me" notes. Which brings up the question of SSD firmware, do you have the MU03 or MU05 firmware installed on your Crucial SSDs? Also, just to double check, do you have AHCI mode enabled in your BIOS settings? You'd be surprised at how many people overlook this. I suppose that Lenovo will get around to releasing updated software addressing this issue, as they have for the other brands of SSD drives, it's just a question of when. Edit: Two more things I thought of after my initail post. First, did you order your M500 directly from Crucial? When I ordered the M500 for my Lenovo T400 Thinkpad, I went to the website and used the advisor to find the M500 part number for my machine. I called to order several days later, and when I gave the part number to the customer representative, she immediately replied "that's for a Lenovo T400, correct?". That tells me there is a part number that is specific to the T400 series, and this may also be the case with the X240 series. Ordering from an online retailer or purchasing the M500 from a store may not have given you the correct part. Second, does your machine have Intel's Management Engine firmware installed, and do you have it enabled? Try entering BIOS and disabling it, just to see if this problem persists. I've noticed that on my T400, when I boot from the DVD drive or a USB stick, I see a brief warning message from the Management Engine stating that I'm not using the normal boot device, but then my machine boots regardless. Perhaps it's causing some sort of grief for your machine.

  • Fix for ORA-00060: Deadlock detected errors

    Hello APEX community,
    in the last days we are hitting more and more frequent the ORA-00060: Deadlock detected error in one of our applications. Logged an SR with Oracle Support but so far not too much help, except pointing to some older bugs:
    Bug 6618662: APEX APPEARS TO BE CAUSING DEADLOCK - CASE COLLECTION or Bug 7587013: INSERTING AND DELETING WWV_FLOW_DATA CAUSES DEADLOCK, which do not look at all appealing as the first bug was logged in Nov 2007 and the resolution was delayed from version 3.1, to 4.0 and even to 4.1, while de second was logged in Nov 2008 and not much happened with it.
    I am curious how many other users are hitting the same issue and which workarounds found for the problem. For example yesterday I could see 12 such errors in my log, today already 3.
    Florin

    Hi John,
    here it is: http://www.moyersoen.be/auction/1442/ or http://www.moyersoen.be/pls/apex/f?p=2008:11:0::::P11_AUCTION_ID:1442. Normally the page response time is < 0.20, but from time to time it goes up to more than 20 seconds and at those times I can see also the ORA-00060: Deadlock detected errors.
    Looks like the users are clicking twice refresh for that page. I am trying now to build a testcase that reproduce the issue easily.
    Florin

  • Preflight detected errors - overset text (1)

    Hi
    I have copied / pasted text from a Word document and tried 2 ways to place it in my InDesign CS6 document
    (1) putting copied text into a prepared text box
    (2) using the 'text box' that 'came with' the copied text (enlarged to fit area)
    each time the dreaded 'red box with a + ' sign inside appears on the rt. side of the 'finalised' text
    and 1 error shows at the bottom which is the Preflight detected error - overset text
    I have loads of other text in my document but none copied/pasted
    Writing the text manually into the document is not an option in this case
    Do I have to format it somehow? I would really appreciate a really simple A-Z step answer for this old gal
    cheers  - any help will really stop my hair from greying any further Lou

    Does the text contain special glyphs that require a font with Maori support? Id not then you can edit the styles to change the font (or, on the strong probability that the Word file doen't really use styles, you can use Find Font to replace it). if you do need Maori support, you should install a font that supports it, like Arial Maori, on the computer. ID uses any fonts installed normally for the OS (presuming they are not really badly made) or that are located in the private Adobe or InDesign fonts folders.

  • [svn:bz-trunk] 21394: bug fix for watson 2887837 Not getting duplicate session detected error when same flex client id is used from two different HTTP sessions in CRX .

    Revision: 21394
    Revision: 21394
    Author:   [email protected]
    Date:     2011-06-16 12:34:13 -0700 (Thu, 16 Jun 2011)
    Log Message:
    bug fix for watson 2887837 Not getting duplicate session detected error when same flex client id is used from two different HTTP sessions in CRX.
    get the sessions id before we invalidate the duplicate session.
    Checkintests pass
    Modified Paths:
        blazeds/trunk/modules/core/src/flex/messaging/endpoints/BaseHTTPEndpoint.java

    For our profect I think this issue was caused as follows:
    Believing that remoting was full asynchronous we fired a 2 or 3 remote calls to the server at the same time ( within the same function ) - usually when the users goes to a new section of the app.
    This seemed to trigger the duplicate http session error since according to http://blogs.adobe.com/lin/2011/05/duplication-session-error.html  two remote calls arriving before a session is created will cause 2 sessions to be created.
    Our current solution ( too early to say it works ) is to daisy chain the multiple calls together .
    Also there seemed to be an issue where mobile apps that never quit ( thanks Apple! )  caused the error when activated after a few hours.
    I guess the session expires on the server and the error above occurs on activation.
    So the mobile apps now ping the server with a remote call when activated after sleeping for more than one hour.
    All duplicate http errors are silently caught and reported.
    Fingers crossed we won't get any more!

  • Detect error message on the screen

    How do I detect error message on the windows 2000 screen? I need to detect any error message appearing on the screen
    Thank you,
    Jeff

    You mean any kind of message generated by any kind of program, whether Java or not?

  • [svn:fx-trunk] 21141: Bug: 2780176 - Logging and logging out multiple times in LCDS can cause duplicate session detected errors .

    Revision: 21141
    Revision: 21141
    Author:   [email protected]
    Date:     2011-04-26 06:40:39 -0700 (Tue, 26 Apr 2011)
    Log Message:
    Bug: 2780176 - Logging and logging out multiple times in LCDS can cause duplicate session detected errors.
    QA: Yes
    Doc: No
    Checkintests: Pass
    Details: When a logout was followed by an immediate login, sometimes the server would throw duplicate session detected errors. This was because when logout happened, a fire-and-forget disconnect message was sent to the server that established a new session, and if the subsequent login happened before disconnect ACK returned from the server, that would establish another session and hence the error. The fix is to insert a slight delay between disconnect and ResultEvent dispatching. This way, disconnect has a chance to return before a login is performed.
    Modified Paths:
        flex/sdk/trunk/frameworks/projects/rpc/src/mx/messaging/ChannelSet.as

    You've got an  incompatible Logitech driver and java was incompletely uninstalled.
    You may have a problem with the Wacom driver.
    I don't know if fixing those things will help.
    There also a few window server errors, but I don't know if they are causal.
    If you can note the time of the hangs, that might help narrow it down in the logs.

  • Error 2101 Detection error on HDD2 (mini sata) X220

    running 1.40 biosthink I have WWAN model as there is a SIM slot and there are a red and blue wires ready for the 3G wireless card.all lenovo drivers etc checked to latest versionsInstalled 128GB Kingspan which failed to do anything and caused the whole system to be unbootable. Turns out the ssd was dead as it did not work in working usb enclosure.swapped in 64GB msata minipci from my old eee901 it is the correct size for the lenovo slot - it wasn't for the 901 and I am now getting 2101 Detection Error on hdd2 on boot up.I have tried reseating the card, cleaning the pins, reseating, booting to Hirens, Slacko, Gparted, Fedora and not been able to see it as the error code is pre OS... Anything I can do? - roll back drivers, roll back bios, buy specific brand msata any suggestions welcome :-)

    Ram speed is not the issue I mentioned the speed purely in response to
    comment relating to the bios and ram speed.
    Because i would like to multiboot I would like to get an ssd to run in the
    msata slot, which is currently empty. I bought a 128GB Kingspan ssd that
    did "nothing" in the slot and refused to even let the x220 boot (I tried
    booting from the ultrabase and from the laptop) i tried reseating the ssd a
    number of times but the laptop would not boot with it in the msata slot.
    And the Kingspan ssd did nothing in a working external msata enclosure and
    is being returned.
    I have an old m-factor 64GB ssd from my eee901 (with 2 or 3 mixed format
    partitions on it) and I tried that in the x220 at which point I received
    the 2101: Detection error on hdd2. I tried reseating the ssd to no avail
    and tried cleaning the contacts with rubbing alcohol and reseated it but
    still keep getting the error.
    What I do not know is if the x220 is a wwan model does it need a specific
    brand of msata ssd to work in the slot? E.G. the Intel 80GB + that are
    mentioned in the forums.
    Re Bios: According to the readme file attached to the older bios versions
    that are available from lenovo there were some fixes for the wwan models
    that related to the ssds which is why I asked about rolling back the bios
    in the hope that an earlier bios might work the ssd in the msata slot.
    (Rather as the later bios restricts the speed of the ram...)
    Thanks again for all of your help. I'm new to messing around with the x
    series and don't know all of the quirks etc :-)

Maybe you are looking for

  • ITunes Freezing... 64 Bit

    Ever since I bought my new Gateway 64-bit Windows 7 PC, I have been having numerous issues with iTunes 64-bit. It will install and open fine, but it always freezes. It freezes when I import a CD, sample music from the iTunes store, and occasionally f

  • Scheduling a task 1 year (365 days) out

    I am trying to schedule a task for 365 days out (1 year/52 weeks) and am encountering errors with the automatic scheduling. Work will be performed on the weekends, year-round, from 8:00 AM to 5:00 PM. I have set the "Change Working Time" options to c

  • Maps not accurate

    When I use the Maps icon to show my location, it shows me to 3 city blocks away from my actual location. I have wi-fi and 3G enabled and have a wifi router in the next room. My 3GS is spot on! The iPhone 4 however is quite a ways off. Any ideas?

  • What exactly does itunes mean when it says "apply sort field"

    In iTunes when I select a track [or several tracks] and then Right click i see an option at the bottom of the resulting menu that offers to "apply sort field", when I select this option a sub menu comes up offering several fields for me to choose fro

  • SMC Firmware update NOT compatible with Adobe Version Cue

    After 2 days of SMC Firmware install & reboot problems (and many other folks in this forum), I went to my Apple Store Genius who resolved the issue by turning off Adobe Version Cue at startup. It is now a know problem at Apple.