After installing a solid state drive my computer no longer dual boots.
Linux - NewbieThis Linux forum is for members that are new to Linux.
Just starting out and have a question?
If it is not in the man pages or the how-to's this is the place!
Notices
Welcome to LinuxQuestions.org, a friendly and active Linux Community.
You are currently viewing LQ as a guest. By joining our community you will have the ability to post topics, receive our newsletter, use the advanced search, subscribe to threads and access many other special features. Registration is quick, simple and absolutely free. Join our community today!
Note that registered members see fewer ads, and ContentLink is completely disabled once you log in.
If you have any problems with the registration process or your account login, please contact us. If you need to reset your password, click here.
Having a problem logging in? Please visit this page to clear all LQ-related cookies.
Get a virtual cloud desktop with the Linux distro that you want in less than five minutes with Shells! With over 10 pre-installed distros to choose from, the worry-free installation life is here! Whether you are a digital nomad or just looking for flexibility, Shells can put your Linux machine on the device that you want to use.
Exclusive for LQ members, get up to 45% off per month. Click here for more info.
After installing a solid state drive my computer no longer dual boots.
I cloned my dual boot spinning drive and then replaced it with a SSD. After I copied the cloned drive to the SSD I was unable to boot into Ubuntu. When I try it says something is missing, but the screen changes before I can write down the information. I installed the old drive in the computer and it still dual boots. Is there a way I can get the SSD to dual boot to Windows or Linux? I tried reinstalling Ubuntu but the Windows OS is not recognized. In fact setup window says Ubuntu does not detect any operating systems on this drive. And I have Win 7 currently installed.
No mention of clone steps used/citation-links, or laptop make and model makes it hard to help you.
Members need more detail like so <just a template/example>
I used Acronis 2016 to clone the original drive. The laptop is a Toshiba Qosmio X505 Q8102. The. Ssd is a SanDisk Ultra 2 960 gig drive. Hopefully this is enough information. If not please let me know. Thanks in advance.
M$osft make it as difficult as possible to move Windoze - does Acronis have a MBR recovery option ?. If not, you'll need a Win7 install/recovery disk (USB) to recovery the MBR boot record. Then at least you'll be able to see if Win7 will boot.
Good luck with that.
For Ubuntu installer not recognising Win7, that has been reported as a problem for a while (Mint too). I thought the latest download images had been fixed, but I've never had the issue myself. Manual (expert ?) partitioning might avoid it.
Re the boot message, as soon as the message appears, hit <Ctrl>+q (both together). Be quick. Take a photo or write the message down so we can help maybe.
I have been a fan of Acronis for a long time. Kind of shocked it failed. However we (I) are not sure of many things right now. Doing the install again may have masked what was originally wrong.
Can I assume it is the full version of Acronis or is it like a WD clone deal?
Did you clone it using a usb enclosure?
If you have the full acronis you can usually copy it to a file then back to this location.
A general rule for clones is that you make things generic. That is you remove naming like UUID or even faulty grub entries to make them generic before the clone or you'll have to correct them later.
You can try this clone again and then use a live media maybe to investigate.
It is entirely possible that your bios is not the only HAL monitored by windows and the number of devices changed exceeds the OEM limit. Usually it will show that problem on screen.
I don't understand some of what you were saying. This was my fist time dealing with Acronis, which is a full install. I have another Qosmio computer that I had the same problem with. But I figured something out and got it to dual boot. This was in the early part of the year, and I decided I wouldn't do it with this computer. About a month ago I decided I want this one to be a dual boot, but I don't remember what I did. I know I didn't redo the clone, and I didn't wipe the partition. Somehow I repaired or replaced the grub loader...I think. It was something relatively simple though.
I don't know how to get to the UUID or where it is.
UUIDs can be a huge impediment to successful cloning. Each disk partition has a UUID. Each filesystem has a UUID. Other objects have UUIDs too. The main obstacles WRT cloning have to do with the mounting of Linux filesystems. If the cloning process is strict, then neither the original nor the clone can be used without risk of corruption, if they can be used at all, for booting from an installation that lives on original or clone, unless only one or the other is connected at boot time. That's because /etc/fstab, used for mounting filesystems, including swap, by default in Ubuntu depends on filesystem UUIDs being unique, which they are not after making a true clone. Success post-clone requires creating new UUID(s) to eliminate duplication, and adjusting /etc/fstab to match every UUID change made. Alternatively, /etc/fstab can be changed to mount using a method other than by UUID, such as by LABEL or device name, but non-unique UUIDs can still be big trouble.
Not having both original and clone connected when booting post-clone avoids the UUID problem only until you forget and for whatever reason try to use the other while booted from one, such as attempting to convert the old into a backup device without remembering to boot something else to do it. So, eliminating the duplication should be the first process to follow the completion of cloning.
To discover the UUID of a partition there are multiple methods, among them the blkid and tune2fs commands. To change a UUID depends on the filesystem type. e.g. for type EXT4, tune2fs can be used.
Distribution: Debian testing/sid; OpenSuSE; Fedora; Mint
Posts: 5,524
Rep:
There are certain things that are unique to an installation and therefore won't work on a cloned drive substituted for /dev/sda. UUIDs are one. The machine should still boot to the grub menu. Then you can press the 'e' key for 'edit'. In the 'kernel' line of the grub entry, where there is a root=SOME_UUID, substitute a partition for the UUID, i.e. /dev/sda1. Hit CTRL x to continue. You might have to try different partitions if you don't know which is the 'root' partition.
There are two 'root=' in the grub entry. Don't change them both unless the UUIDs are the same. The first root= is for the 'boot' partition if there is a separate one.
You might also consider using 'dd' to clone the drive, as it is a bitstream duplicator. It duplicates bit for bit, exactly. If you use the 'sync' option with 'dd' it is more difficult for MS Windows to detect it has been moved to a different drive. In any event, Windows must be moved to the same partition number on the target drive, i.e. if windows is on /dev/sda1, then it must be cloned to /dev/sdb1.
If you get it booted up, or even from busybox, try
Code:
$ ls -al /dev/disk/by-uuid
and find the correct UUIDs for your partitions. Edit /etc/fstab and /etc/grub/default accordingly
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.