These forums have been archived and are now read-only.

The new forums are live and can be found at https://forums.eveonline.com/

Out of Pod Experience

 
  • Topic is locked indefinitely.
 

ThinkPad E530 and the case of the vanished SSD.

Author
Solstice Project
Sebiestor Tribe
Minmatar Republic
#1 - 2013-04-08 11:56:42 UTC
I had so much fun writing this post on the Lenovo Forums,
i thought i'd share it here. Also, by chance, somebody MIGHT be able to help. :)

- - - - - - - - - -

Greetings !

I am a proud (well, yes ...) owner of the E530 A3G-Model sporting a 16GB SSD.
Yes, the one with the pulsy, noisy fan. ^_^


The Story:

Last week i thought i'd need a change and try something new. As i'm not really a noob on
computers, i thought i'd set up Win7 x64 SP1 on the SSD. That's ... not that easy,
considering the size, so i've spent the weekend removing irrelevant components ...
... like Natural Language, Speech Support, Language Packs ...
... from the Win7 x64 SP1 Installation Disks.


It took me two days to get it to work, with several testing sessions using VirtualBox,
but then i got it right. I haven't removed any drivers, services or anything actually essential
which could break the system. (I promise!)

So ... after a long session in VirtualBox and installing this system on a small partition on my HDD
to verify it REALLY works, i went going on to install it on the SSD.


Please note that RapidBoot is turned off in the BIOS and i have removed ExpressCache,
which i had previously installed manually, but wasn't actually caching anything anymore,
for reasons i don't understand. Maybe i have turned it off weeks ago, i don't know.

So, i have set up a 3GB FAT32 partition at the beginning of the SSD for the pagefile. It's a habit.
It's a good idea to do this on HDDs, so i kept doing it. Longevity of the SSD was no issue for me,
as if it breaks ... well, then it breaks ... but then it would break in honor, having served me well.

The rest of the SSD got partitioned NTFS, for Win7 x64 SP1, which installed *successfully*.
The installation process went *flawlessly* and it also ran *flawlessly*.

So ... i've started installing drivers from my HDD, which are all in this nice SWTOOLS folder,
onto the SSD. Easy cheesy, clicked through the symbols in my Device Manager and let it
run through the folder, to update the drivers.

The first odd thing i've noticed was that, after establishing an internet connection,
the ThinkPad PM Driver got named into Lenovo PM Driver. Okay, well, so be it, i thought.

All drivers actually installed smoothly. No issues. Nothing. Reboots worked. All good.

Then ... i've started Windows Update. I have done this in the VirtualBox so i knew there were
quite a lot updates to be downloaded (around 280MByte) ... but it didn't get very far.



Here it starts:


The green bar, which indicates searching, kept pulsing. The visible windows were all stuck,
but the mouse still could be moved. I thought ... okay ... that's odd ... but left it for a few minutes.
As nothing changed for 10min, i've reset the system. That may not have been a smart thing to do,
but as not even the Task Manager came up, it was the *only choice i had*.


Now ... i can't recall if the 2101 Error displayed at this time already, but i can recall having tried to
boot into the OS on the SSD again and it took ages. Ages. After 5min watching the pulsing
Windows ButterFly, i thought "Okay, that's odd" and reset the system.


(Actually, after i have written the whole post, i'm not sure anymore if i actually tried
booting onto the SSD now, or if the error came up already. I'm sorry for this lack of memory,
it was past 0100am.)


In hindsight, i know i should have waited longer, but that may not actually
have changed anything. Now i'll never know.


So ... after this reboot ... Lenovo Boot Splash Screen ... BEEP ... msata 2101 blabla HDD2 not found etc.
F***! Okay ... no worry ... let's see. Booted into the HDD OS ... the pulsing butterfly again ...
... waiting ... waiting ... waiting ... waiting ... okay i'll have a smoke ... 5min later ... the login sound.

I know this kind of waiting. It's the waiting that happens when a driver delays everything,
for reasons only the driver knows, unwilling to share it with the user.


So ... finally, the HDD OS booted up. I'm glad. I log in ... and wait. BlackScreen. Wait. Wait.
Desktop comes up. System is heavily unresponsive.

I'm starting the Task Manager. Waiting. It starts.
Show all processes.
"System" is at 25%, indicating it's hogging a CPU core ... for unknown reasons.


I open up the Device Manager.
One Exclamation Mark on Yellow Background:

Lenovo PM Driver.


I run the Windows Please-Help-Me-And-Find-Out-What's-Going-On-Program.

It suggests updating the driver ... so i tried updating the driver via Windows Update ... and it did.


Now ... i have *no* idea where that issue comes from and updating the driver did not help at all.
Right now, the exclamation mark again is present, so i simply *deactivated* it in the Device Manager,
but haven't rebooted yet. The PC is still running and i doubt it'll have a serious impact. I already deleted
it from the Device Manager once, just to see it get reinstalled.


So ... this is the whole story, in right order. Complete.


Windows Update, for some odd reason, broke something. I doubt the reboots are part of this,
but there may be a first time for anything.


Solstice Project
Sebiestor Tribe
Minmatar Republic
#2 - 2013-04-08 11:57:07 UTC  |  Edited by: Solstice Project
In the now:

I have googled this extensively, within limited options regarding search terms. I have removed the SSD
and plugged it in again, but it changed nothing. I am researching on how to find the one driver which
causes the boot delay (which only happens when the SSD is plugged in, btw), which - i hope - gives
me more options ... but as of yet, i'm still researching. I might try bootvis, because i know it does stuff like that.

So ... after telling you my story (hope you had a nice read and you're at work, wasting your time ^_^),
if there is ANYBODY OUT THERE who knows **bleep** is going on, I'd REALLY appreciate ANY advise !
Except: unplug the SSD and forget it. That's not an option. ^_^


Thank you for your time, i hope you like detailed posts about malfunctions happening. :)


Oh and i forgot to mention that the 2101 error doesn't even show up anymore.


(why does it say i exceed the character limit, although i still have around 100 left -.-)
Copine Callmeknau
Dirty Vagrants
Intergalactic Space Hobos
#3 - 2013-04-09 10:24:18 UTC
What's the problem exactly, the SSD not being detected, or the computer taking a long time to boot?

If it's SSD detection issue, try plugging the SSD into another computer to check if it's working normally.
Also try plugging another drive into your laptop to see if the laptop is detecting other drives correctly.

There should be a rather awesome pic here

Reiisha
#4 - 2013-04-09 10:30:23 UTC  |  Edited by: Reiisha
If you're trying to run the thing off the SSD, it might be a space issue. You need to keep 20-30% of the SSD free, otherwise it starts slowing down a LOT. After an SSD is about 70% full, the performance gradually degrades depending on free space.

I never heard it being this bad though.

Also, look at the windows error log. Maybe there's something in there. Type in "eventvwr" in the start menu and hit enter to bring it up.

Also, to make it clear, you are talking about something running on the SSD in Virtualbox?

If you do things right, people won't be sure you've done anything at all...

Alice Saki
Nocturnal Romance
Cynosural Field Theory.
#5 - 2013-04-09 10:31:35 UTC
I understood Like 5 words \o/ Lol

FREEZE! Drop the LIKES AND WALK AWAY! - Currenly rebuilding gaming machine, I will Return.

Solstice Project
Sebiestor Tribe
Minmatar Republic
#6 - 2013-04-09 11:07:24 UTC  |  Edited by: Solstice Project
Copine Callmeknau wrote:
What's the problem exactly, the SSD not being detected, or the computer taking a long time to boot?

If it's SSD detection issue, try plugging the SSD into another computer to check if it's working normally.
Also try plugging another drive into your laptop to see if the laptop is detecting other drives correctly.
The mSata-interface doesn't recognize the SSD. It's a common error among ThinkPads,
except not on my particular line.

Yesterday, after rebooting from hibernation into the HDD OS,
the SSD got detected (according to windows),
but with zero space on it. Then, after a reboot, it vanished again.

I don't have any other mSata-slot anywhere to test it. Except, MAYBE, in my other notebook,
but then there's something connected to it already. I have never checked.
I really believe the card is still alive.


Reiisha wrote:
If you're trying to run the thing off the SSD, it might be a space issue. You need to keep 20-30% of the SSD free, otherwise it starts slowing down a LOT. After an SSD is about 70% full, the performance gradually degrades depending on free space.

I never heard it being this bad though.

Also, look at the windows error log. Maybe there's something in there. Type in "eventvwr" in the start menu and hit enter to bring it up.

Also, to make it clear, you are talking about something running on the SSD in Virtualbox?
Wow, it seems my post was much more confusing than i thought. :(

It's def. no space-issue. More of a hardware/bios-failure, but nobody knows for certain .. not even Lenovo.

The installed Win7 x64 SP1 took less than seven gigabyte on a twelve gigabyte SSD ... that would give enough room,
especially considering that i would run mostly portable apps or install them somewhere else.

Funny that you mention the eventvwr. I've heard about it today for the first time. I have unplugged the SSD already
and i'm kind of unsure if i should plug it in again. I've bought an Kingston SSDNow V300, because F*** YEAH
and i'm quite happy with this. xD

The whole error is a mystery to everybody. Lenovo ... actually, the notebooks are really awesome ...
... except that the fans make weird, pulsy noises (well, tbh, that changed with the kingston for the time being) ...
... and the weird hardware failures ... and the fact that factory built notebooks don't utilize the mSata SSD at all ...

Oh and ... no, the SSD was tested in reality, not in VirtualBox. I've used VirtualBox only to test the slimmed
windows installations i've made.

Wow, i've bought some crap ... but i like it. xD
Copine Callmeknau
Dirty Vagrants
Intergalactic Space Hobos
#7 - 2013-04-09 13:02:56 UTC
Solstice Project wrote:
Copine Callmeknau wrote:
What's the problem exactly, the SSD not being detected, or the computer taking a long time to boot?

If it's SSD detection issue, try plugging the SSD into another computer to check if it's working normally.
Also try plugging another drive into your laptop to see if the laptop is detecting other drives correctly.
The mSata-interface doesn't recognize the SSD. It's a common error among ThinkPads,
except not on my particular line.

Yesterday, after rebooting from hibernation into the HDD OS,
the SSD got detected (according to windows),
but with zero space on it. Then, after a reboot, it vanished again.

I don't have any other mSata-slot anywhere to test it. Except, MAYBE, in my other notebook,
but then there's something connected to it already. I have never checked.
I really believe the card is still alive.

It's def. no space-issue. More of a hardware/bios-failure, but nobody knows for certain .. not even Lenovo.

Wow, i've bought some crap ... but i like it. xD

Oh mSata, yuck.
That's gonna make it quite tricky to find where the fault is.

You really need to find another mSata capable computer to test the drive on, or another mSata drive to test the laptop with. From the information you've given us it would be impossible to tell whether the SSD or the laptop's mSata interface is faulty.

From what you've described though, it sounds as if the SSD has become corrupted during an unexpected power loss and needs reformatting. Can you detect the drive through device manager or disk manager?

It's also a possibility that you have had a BIOS failure, but I think that is less likely.

There should be a rather awesome pic here

Solstice Project
Sebiestor Tribe
Minmatar Republic
#8 - 2013-04-09 16:44:18 UTC
Copine Callmeknau wrote:
Oh mSata, yuck.
That's gonna make it quite tricky to find where the fault is.

You really need to find another mSata capable computer to test the drive on, or another mSata drive to test the laptop with. From the information you've given us it would be impossible to tell whether the SSD or the laptop's mSata interface is faulty.

From what you've described though, it sounds as if the SSD has become corrupted during an unexpected power loss and needs reformatting. Can you detect the drive through device manager or disk manager?

It's also a possibility that you have had a BIOS failure, but I think that is less likely.
I'm sure the card is okay, but there are no ways for me to test it.

Lenovo is already known for 2101 Errors (HDD2 on mSata not found).

For some lines of their notebooks, the whole issue gets fixed by un- and replugging them in.
I've tried that, of course ... didn't help.

The drive detectable anymore .. well, almost. I've written above that, after coming out of hibernation
on the HDD OS, for some odd reason, the SDD got recognized. Then, after a reboot, it was gone again.

:Lenovo: ... there's nothing more to say. I've unplugged it, it lies right next to me and if i ever manage
to find somebody with mSata (never), i'll give it a test. ^_^

All i wanted to do anyway is make a Win7 x64 SP1 that fits, works and leaves enough room.
Success. Then it died. I blame Windows Update and some driver that acted strangely,
which i will now simply *not* update. There's worse. ^_^

Oh and i've learned new things too ... this Event Viewer is quite handy. ^_^