LinuxQuestions.org

LinuxQuestions.org (/questions/)
-   Linux - Newbie (https://www.linuxquestions.org/questions/linux-newbie-8/)
-   -   After installing a solid state drive my computer no longer dual boots. (https://www.linuxquestions.org/questions/linux-newbie-8/after-installing-a-solid-state-drive-my-computer-no-longer-dual-boots-4175586834/)

RCSMG 08-11-2016 02:22 PM

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.

rokytnji 08-11-2016 02:39 PM

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>

http://www.catb.org/~esr/faqs/smart-questions.html

Happy Trails and good luck with it, Rok

PS Welcome to Linux Questions.

RCSMG 08-11-2016 02:48 PM

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.

lazydog 08-11-2016 02:57 PM

Off the cuff did you check to see if it is looking at the UUID of the drive and ensure that that is not what it is looking at during boot?

syg00 08-11-2016 06:59 PM

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.

RCSMG 08-11-2016 08:16 PM

Lazy dog, I don't know how to get to the UUID or where it is.

syq00, thanks for that info. I will post the error tomorrow (Friday).

jefro 08-11-2016 09:20 PM

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.

RCSMG 08-11-2016 11:06 PM

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.

lazydog 08-13-2016 09:33 AM

As you haven't stated what you are using to boot I'm going to assume Grub, How to fix UUID

If this is not the case do a search on the boot loader you are using with UUID

RCSMG 08-13-2016 09:40 AM

Thank you LD I will check that out.

mrmazda 08-14-2016 02:20 AM

Quote:

Originally Posted by RCSMG (Post 5589620)
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.

rokytnji 08-14-2016 11:19 AM

Quote:

Originally Posted by RCSMG (Post 5589620)
Lazy dog, I don't know how to get to the UUID or where it is.

syq00, thanks for that info. I will post the error tomorrow (Friday).

Code:

# blkid
/dev/sda1: UUID="99517a34-0f9f-42d4-af4c-82ae817fb057" TYPE="ext4"
/dev/sda2: UUID="52dc4336-761c-4976-ac02-0851fa022abc" TYPE="ext4"

The blkid command will help you find info for uuid numbers,

RCSMG 08-14-2016 11:41 AM

1 Attachment(s)
Here are two screen shots of the error messages that I get when I try to boot into Ubuntu on my dual boot laptop.

RCSMG 08-14-2016 11:47 AM

1 Attachment(s)
Here is the second screen shot.

AwesomeMachine 08-14-2016 11:47 AM

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

Here's a post on the 'dd' command: http://www.linuxquestions.org/questi...ommand-362506/


All times are GMT -5. The time now is 09:55 PM.