I have a Lenovo ideapad 330s 15ikb with a 1TB HDD and 16GB Intel Optane memory.
Now I have ordered an SSD from Crucial (MX500) (with SATA to USB cable). I wanted to start cloning with the software provided by Crucial (Acronis True Image), but it turns out that the hard disk is not displayed as an HDD but as a RAID.
This means that exactly nothing happens on restart. The laptop just boots up as if nothing had happened (well, strangely, the USB slots only work when you restart it, but well?). According to Acronis, there seem to be problems cloning RAID to SSD. I just don't understand why it's a RAID at all, I only have one hard drive. Is it due to the Intel Optane memory? And in general, can the RAID state be changed?
I'd be happy for help!
Fortunately, you have an Intel chipset. With the AMD RAID controller you lost, without deleting the hard drive you can't get rid of the RAID config. But that's another topic.
This has absolutely nothing to do with the Optane memory. For some stupid reason, the manufacturer has set the SATA mode in your BIOS to RAID. Which makes no sense if you only operate a single non-RAID hard drive. However, since this should not be initialized at Intel, you can usually simply switch the SATA mode from RAID to AHCI in the BIOS. The hard drive should still be running and booting, and Acronis should still be able to clone normally to your SSD in this status.
Thank you for the fast answer!
So. The Intel RST mode is activated in the BIOS, the hard disk is noted as a non-raid with the controller type AHCI. If I want to switch from RST to AHCI mode, I get the message that this would delete the hard disk data. My confusion is growing
Then I fear that the new Intel chipset will do the same thing as the AMD RAID controller. Non-RAID hard disks must be initialized in RAID before they can be used in RAID mode (RST = Rapid Storage Technology - this is Intel's own standard). Unfortunately, that ensures that. That when the RAID BIOS is deactivated, these hard drives can no longer be used without performing a deletion. Backward step through progress, older Intel RAID controllers could be activated and deactivated as desired, non-RAID hard drives always ran without problems without losing data.
With luck, the message may only refer to RAID arrays and not to the non-RAID hard drive. But since I don't have a PC to test here, I can't guarantee that. Without prior backup (clone image), which you were unlucky with with the Acronis version that was included, I would not experiment.
Which Acronis Trueimage version is included? According to the website, the Home 2010 version and higher is RAID compatible. I have the 2016 version myself, which can clone and back up RAID arrays.
So I have Acronis True Image for Crucial. The 2020 version is too expensive for me with at least 50 euro to use it once. I also have a free program called MiniTool Partition Wizard. There's the interesting problem that it does not recognize the SSD, but only the SATA-to-USB cable with a storage capacity of 0GB. Logically.
I absolutely understand. 50 euro are relatively heavy. Although I have to say that Acronis TrueImage has been the best program I have had when it comes to performing 1: 1 backups of system partitions and disk clones. The detection of USB devices, hard drives etc. Is also very good in rescue mode without an operating system. With other programs you only have to jiggle. What many can't do is mirror 1: 1 cloned backup images to smaller hard drives or to larger ones without leaving any unpartitioned areas. That's why TrueImage is worth its money.
But maybe one or the other free program also works very well. Here is an example that should also support RAID: https://www.ubackup.com/de/klonen/freie-klon-software-fuer-raid-array.html
The software has the same problem as the Partition Wizard: it does not recognize the SSD or is specified with 0KB. Is it maybe the SATA to USB cable? Ordered the Amazon's Choice product.
Does the SSD work normally under Windows? Is it already partitioned there? If not, then the times as a volume and try to clone afterwards. Or the other way around, if a partition with volume already exists, delete it via the disk management before you try cloning.
