06-22-2016 03:43 AM
I have replaced CD-ROM by HDD Caddy with SSD (Samsung 850 EVO 250GB) in my Lenovo ThinkPad L440 (20ASS3GT0) as a second storage device (not one with the OS). When I'm trying to start the system, I'm getting a message "Configuration changes - restart the system." and the system reboots again and again. What is more, I can't access the BIOS any more - pressing F1 does not work. Updating to the newest version of BIOS (1.85) does not help. After removing HDD Caddy everything works fine. I have tried some of the configurations below:
Removed the battery, pressed the power button for 10-15 sec. and rebooted with AC Adapter connected - still got message "Configuration changes - restart the system."
The problem is, that I need two storage devices - one for the OS and second one (using HDD caddy) for another data. Could anyone help me to solve that issue?
06-22-2016 05:57 AM
Personal website: ThinkScopes
06-22-2016 06:13 AM - edited 06-22-2016 06:17 AM
Nope. But I am using TrueCrypt to encrypt the whole HDD (the one connected throught standard SATA port). Should I decrypt the whole system drive before connecting the additional storage device ?
07-10-2016 09:13 PM
I have the same issue on my Thinkpad-L540. It was working fine until, about 2 weeks ago, I updated the BIOS/UEFI Firmware to Version 1.86 (released 6/23/2016).
When I updated the BIOS/UEFI firmware and rebooted the system, I got an error saying "Configuration changes - restart the system."
It didn't boot until I removed the caddy with the second hard drive. However, I moved my User folder over to the second hard drive (I'm running Windows 10), so my system isn't working properly. [As a workaround, I've been hotplugging the caddy before logging into Windows, but this does not seem like a great idea].
I'm not exactly sure which version of the BIOS/UEFI I had, but I remember that it was from 2014. I tried downgrading to 1.81, but that didn't make a difference.
Did you recently update your BIOS/UEFI firmware?
07-11-2016 09:12 AM
Do you remember what version you were running before the update? If you revert to that version, does it start working again?
I plan on downgrading to earlier versions when I have the chance to see if that solves the problem. (As mentioned earlier, downgrading to 1.81 didn't solve the problem, so I'll try to go further back)