Error 2100 Hard Drive Initialization Error (4)
Posted: Mon Feb 14, 2011 7:28 am
Hi everyone, I just had 2 instances of getting this message in the past 48 hours.
Instance 1: When trying to wake from Hibernate, after the password screen.
Primary drive is an Intel 160Gb SSD, about 8 months old.
Ultrabay is a Hitachi 320Gb HDD, about 2 years old.
Pressing Esc did nothing. I had to hard power off then on. Everything worked as per normal.
I checked the SSD with the Intel SSD Toolkit (Run Fast Diagnostic Scan) - no errors.
Instance 2: Again when trying to wake from Hibernate.
This time, the Ultrabay is empty.
Pressing Esc did nothing. Had to hard power off-on.
Everything worked ok thereafter.
I am backing up everything before going to Hibernation now.
I could not find any posts on here with the type (4) designation.
How likely is it that both the SSD and HDD controller chips are dying at the same time?
The fingerprint reader's been a bit sluggish lately. About half the time I resorted to keying in the password manually. Could that be a sign that something else is wrong with the system?
I am running the Full diagnostic on the SSD now.
All input greatly appreciated.
Instance 1: When trying to wake from Hibernate, after the password screen.
Primary drive is an Intel 160Gb SSD, about 8 months old.
Ultrabay is a Hitachi 320Gb HDD, about 2 years old.
Pressing Esc did nothing. I had to hard power off then on. Everything worked as per normal.
I checked the SSD with the Intel SSD Toolkit (Run Fast Diagnostic Scan) - no errors.
Instance 2: Again when trying to wake from Hibernate.
This time, the Ultrabay is empty.
Pressing Esc did nothing. Had to hard power off-on.
Everything worked ok thereafter.
I am backing up everything before going to Hibernation now.
I could not find any posts on here with the type (4) designation.
How likely is it that both the SSD and HDD controller chips are dying at the same time?
The fingerprint reader's been a bit sluggish lately. About half the time I resorted to keying in the password manually. Could that be a sign that something else is wrong with the system?
I am running the Full diagnostic on the SSD now.
All input greatly appreciated.