Booting After Moving Hard Drive To Another Computer
Linux - Laptop and NetbookHaving a problem installing or configuring Linux on your laptop? Need help running Linux on your netbook? This forum is for you. This forum is for any topics relating to Linux and either traditional laptops or netbooks (such as the Asus EEE PC, Everex CloudBook or MSI Wind).
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.
Booting After Moving Hard Drive To Another Computer
Hello All,
I am trying to solve an issue with my Kali Linux system. I had to remove my hard drive from one netbook to another, they are very similar in models and hardware should be the same to my knowledge. My system is now getting a hung on boot. Grub seems to be loading the image but it just hangs with a flashing "-".
I think this may be a driver problem? Can anyone recommend who to resolve this? I cannot bot but I can get into grub interface and I could boot from an old Xubunto live USB. Any suggestions would be appreciated.
That's not much information to go on. Do you have a Live CD/flash drive of any Linux system? If you do, go to the 'bootinfoscript' site (jsut google it) and download and run the script and post the output, a results.txt file. Instructions are in a link in the Description box on their page.
Did the old notebook have only the one drive? Same for the new notebook? Do you see a Grub boot menu at all?
That's not much information to go on. Do you have a Live CD/flash drive of any Linux system? If you do, go to the 'bootinfoscript' site (jsut google it) and download and run the script and post the output, a results.txt file. Instructions are in a link in the Description box on their page.
Did the old notebook have only the one drive? Same for the new notebook? Do you see a Grub boot menu at all?
Yes I see grub and I can get in to the grub command line. I see my partitions and the image etc. I think it hangs because of maybe drivers or something. Both netbooks had a bay for only 1 drive. I have a live USB flash drive as mentioned. Ill try the bootinfoscript
You should use labels or UUIDs in the grub.cfg and /etc/fstab config files. The /dev/ names can be unpredictable on some hardware. The symptoms seem to suggest this is what's happening. That should be the only thing that you need to change to be able to boot it, as long as there's no chipset quirks. As in 32bit vs. 64bit or non-pae kernel needs.
If you moved hdd from 1 machine to anotherI would say it's a case of not having the correct graphics driver.
You can boot to recovery mode via "Advanced Options" at grub menu to see what graphics you have.
Well all of this advice seem really helpful. So far I have entered grub command prompt. I tried to run update-grub but had no success. It say is is an unknown command. I also looked at the grub config file but it says I should not edit this file and there are scripts to do this with.
Is there an better approach to get grub to update and recognize the drive for booting.
I actually think it is a video driver issue is possible. What is the safest way to boot up using generic video driver at boot.
Just an reminder, I only have access to grub command prompt. I do have a USB stick that I can use to boot into a live session.
I am finding various information on the web but I am not sure the safest way as I do not want to loose the install totally.
If you moved hdd from 1 machine to anotherI would say it's a case of not having the correct graphics driver.
You can boot to recovery mode via "Advanced Options" at grub menu to see what graphics you have.
What exactly an I looking for? I went in to grub and edit mode and I can only see load_video. Should I disable this?
Boot the live system. Mount the device. Get the details on the partion(s) with blkid. Change the (mount point)/boot/grub/grub.cfg and change the (mount point)/etc/fstab on the mounted media. Although depending on the version of grub, changing the /etc/fstab and running update-grub could work (if chroot-ed to the install). But it's simpler to just change both config files on the mounted system than it is to chroot and run things on said media.
You can use "e" in grub to enter edit mode to change the boot items. But if the /etc/fstab is in the way that's not much good. You're looking for the line in grub.cfg that reads something like:
linux /boot/vmlinuz root=/dev/sda1
to change it to something like
linux /boot/vmlinuz root=UUID=ffffffff-ffff-ffff-ffff-ffffffffffff
Where the UUID is what matches the data from blkid. Roughly the same syntax for LABEL=xxx... You're basically swapping the /dev/... for UUID=... or LABEL=... in grub.cfg and fstab.
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.