[SOLVED] Put my dual boot hard drive in a different older laptop and now only Linux boots.
Linux - SoftwareThis forum is for Software issues.
Having a problem installing a new program? Want to know which application is best for the job? Post your question in this forum.
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.
Put my dual boot hard drive in a different older laptop and now only Linux boots.
Okay so I had a newer HP pavilion and I had Kali Linux dual booted with Windows 8.1, well I sold the HP and put a different hard drive in it and put my dual booted hard drive into my ASUS X54C. Now when I start up my computer my Linux loads and Grub pops up however it doesn't show my Windows on it. It does however show my windows recovery but when I select it a screen pops up and says that a recent hardware change has made it unable to boot properly. So does anyone have any ideas? I was thinking maybe I needed a BIOS update since this is an older laptop that came with windows 7 installed. I am very new to Linux but not to computers in general, I have never messed with dual booted hard drives however so I am a bit lost.
You probably want to run grub-mkconfig to see if Kali can detect Windows. If that fails, (creds to yancek), you can try running this bootinfoscript available from the link below and post the output file from the to show us what's going on:
Generating grub.cfg ...
#
# DO NOT EDIT THIS FILE
#
# It is automatically generated by grub-mkconfig using templates
# from /etc/grub.d and settings from /etc/default/grub
#
### BEGIN /etc/grub.d/00_header ###
if [ -s $prefix/grubenv ]; then
load_env
fi
set default="0"
if [ "${prev_saved_entry}" ]; then
set saved_entry="${prev_saved_entry}"
save_env saved_entry
set prev_saved_entry=
save_env prev_saved_entry
set boot_once=true
fi
function savedefault {
if [ -z "${boot_once}" ]; then
saved_entry="${chosen}"
save_env saved_entry
fi
}
insmod part_gpt
insmod ext2
set root='(hd0,gpt7)'
search --no-floppy --fs-uuid --set=root 61110269-32be-4b52-8193-e6d3a616bcca
if loadfont /usr/share/grub/unicode.pf2 ; then
set gfxmode=640x480
load_video
insmod gfxterm
insmod part_gpt
insmod ext2
set root='(hd0,gpt7)'
search --no-floppy --fs-uuid --set=root 61110269-32be-4b52-8193-e6d3a616bcca
set locale_dir=($root)/boot/grub/locale
set lang=en_US
insmod gettext
fi
terminal_output gfxterm
set timeout=5
### END /etc/grub.d/00_header ###
### BEGIN /etc/grub.d/05_debian_theme ###
insmod part_gpt
insmod ext2
set root='(hd0,gpt7)'
search --no-floppy --fs-uuid --set=root 61110269-32be-4b52-8193-e6d3a616bcca
Found background image: /usr/share/images/desktop-base/desktop-grub.png
insmod png
if background_image /usr/share/images/desktop-base/kali-grub.png; then
set color_normal=white/black
set color_highlight=black/white
else
set menu_color_normal=cyan/blue
set menu_color_highlight=white/blue
fi
### END /etc/grub.d/05_debian_theme ###
### BEGIN /etc/grub.d/10_linux ###
Found linux image: /boot/vmlinuz-3.18.0-kali3-amd64
Found initrd image: /boot/initrd.img-3.18.0-kali3-amd64
menuentry 'Kali GNU/Linux, with Linux 3.18.0-kali3-amd64' --class kali --class gnu-linux --class gnu --class os {
load_video
insmod gzio
insmod part_gpt
insmod ext2
set root='(hd0,gpt7)'
search --no-floppy --fs-uuid --set=root 61110269-32be-4b52-8193-e6d3a616bcca
echo 'Loading Linux 3.18.0-kali3-amd64 ...'
linux /boot/vmlinuz-3.18.0-kali3-amd64 root=UUID=61110269-32be-4b52-8193-e6d3a616bcca ro initrd=/install/gtk/initrd.gz quiet
echo 'Loading initial ramdisk ...'
initrd /boot/initrd.img-3.18.0-kali3-amd64
}
menuentry 'Kali GNU/Linux, with Linux 3.18.0-kali3-amd64 (recovery mode)' --class kali --class gnu-linux --class gnu --class os {
load_video
insmod gzio
insmod part_gpt
insmod ext2
set root='(hd0,gpt7)'
search --no-floppy --fs-uuid --set=root 61110269-32be-4b52-8193-e6d3a616bcca
echo 'Loading Linux 3.18.0-kali3-amd64 ...'
linux /boot/vmlinuz-3.18.0-kali3-amd64 root=UUID=61110269-32be-4b52-8193-e6d3a616bcca ro single initrd=/install/gtk/initrd.gz
echo 'Loading initial ramdisk ...'
initrd /boot/initrd.img-3.18.0-kali3-amd64
}
### END /etc/grub.d/10_linux ###
### BEGIN /etc/grub.d/20_linux_xen ###
### END /etc/grub.d/20_linux_xen ###
### BEGIN /etc/grub.d/30_os-prober ###
No volume groups found
Found Windows Recovery Environment (loader) on /dev/sda5
menuentry "Windows Recovery Environment (loader) (on /dev/sda5)" --class windows --class os {
insmod part_gpt
insmod ntfs
set root='(hd0,gpt5)'
search --no-floppy --fs-uuid --set=root DEB0BFC8B0BFA585
drivemap -s (hd0) ${root}
chainloader +1
}
### END /etc/grub.d/30_os-prober ###
### BEGIN /etc/grub.d/40_custom ###
# This file provides an easy way to add custom menu entries. Simply type the
# menu entries you want to add after this comment. Be careful not to change
# the 'exec tail' line above.
### END /etc/grub.d/40_custom ###
### BEGIN /etc/grub.d/41_custom ###
if [ -f $prefix/custom.cfg ]; then
source $prefix/custom.cfg;
fi
### END /etc/grub.d/41_custom ###
done
It seems it cant detect it, Im downloading the program now and I will post the results as soon as it is done.
Starting with Windows 7 MS implemented an anti-pirating feature whereby a major hardware change requires re-authorization. If you can get it re-authorized it might be difficult getting it running due to it being an HP OEM version.
============================= Boot Info Summary: ===============================
=> Grub2 (v1.99) is installed in the MBR of /dev/sda and looks at sector
1183421488 of the same hard drive for core.img. core.img is at this
location and looks for (,gpt7)/boot/grub on this drive.
xz: (stdin): Compressed data is corrupt
No volume groups found
This is what the bootinfoscprit brought up. grub-mkconfig brought up this...
Quote:
Generating grub.cfg ...
#
# DO NOT EDIT THIS FILE
#
# It is automatically generated by grub-mkconfig using templates
# from /etc/grub.d and settings from /etc/default/grub
#
### BEGIN /etc/grub.d/00_header ###
if [ -s $prefix/grubenv ]; then
load_env
fi
set default="0"
if [ "${prev_saved_entry}" ]; then
set saved_entry="${prev_saved_entry}"
save_env saved_entry
set prev_saved_entry=
save_env prev_saved_entry
set boot_once=true
fi
function savedefault {
if [ -z "${boot_once}" ]; then
saved_entry="${chosen}"
save_env saved_entry
fi
}
insmod part_gpt
insmod ext2
set root='(hd0,gpt7)'
search --no-floppy --fs-uuid --set=root 61110269-32be-4b52-8193-e6d3a616bcca
if loadfont /usr/share/grub/unicode.pf2 ; then
set gfxmode=640x480
load_video
insmod gfxterm
insmod part_gpt
insmod ext2
set root='(hd0,gpt7)'
search --no-floppy --fs-uuid --set=root 61110269-32be-4b52-8193-e6d3a616bcca
set locale_dir=($root)/boot/grub/locale
set lang=en_US
insmod gettext
fi
terminal_output gfxterm
set timeout=5
### END /etc/grub.d/00_header ###
### BEGIN /etc/grub.d/05_debian_theme ###
insmod part_gpt
insmod ext2
set root='(hd0,gpt7)'
search --no-floppy --fs-uuid --set=root 61110269-32be-4b52-8193-e6d3a616bcca
Found background image: /usr/share/images/desktop-base/desktop-grub.png
insmod png
if background_image /usr/share/images/desktop-base/kali-grub.png; then
set color_normal=white/black
set color_highlight=black/white
else
set menu_color_normal=cyan/blue
set menu_color_highlight=white/blue
fi
### END /etc/grub.d/05_debian_theme ###
### BEGIN /etc/grub.d/10_linux ###
Found linux image: /boot/vmlinuz-3.18.0-kali3-amd64
Found initrd image: /boot/initrd.img-3.18.0-kali3-amd64
menuentry 'Kali GNU/Linux, with Linux 3.18.0-kali3-amd64' --class kali --class gnu-linux --class gnu --class os {
load_video
insmod gzio
insmod part_gpt
insmod ext2
set root='(hd0,gpt7)'
search --no-floppy --fs-uuid --set=root 61110269-32be-4b52-8193-e6d3a616bcca
echo 'Loading Linux 3.18.0-kali3-amd64 ...'
linux /boot/vmlinuz-3.18.0-kali3-amd64 root=UUID=61110269-32be-4b52-8193-e6d3a616bcca ro initrd=/install/gtk/initrd.gz quiet
echo 'Loading initial ramdisk ...'
initrd /boot/initrd.img-3.18.0-kali3-amd64
}
menuentry 'Kali GNU/Linux, with Linux 3.18.0-kali3-amd64 (recovery mode)' --class kali --class gnu-linux --class gnu --class os {
load_video
insmod gzio
insmod part_gpt
insmod ext2
set root='(hd0,gpt7)'
search --no-floppy --fs-uuid --set=root 61110269-32be-4b52-8193-e6d3a616bcca
echo 'Loading Linux 3.18.0-kali3-amd64 ...'
linux /boot/vmlinuz-3.18.0-kali3-amd64 root=UUID=61110269-32be-4b52-8193-e6d3a616bcca ro single initrd=/install/gtk/initrd.gz
echo 'Loading initial ramdisk ...'
initrd /boot/initrd.img-3.18.0-kali3-amd64
}
### END /etc/grub.d/10_linux ###
### BEGIN /etc/grub.d/20_linux_xen ###
### END /etc/grub.d/20_linux_xen ###
### BEGIN /etc/grub.d/30_os-prober ###
No volume groups found
Found Windows Recovery Environment (loader) on /dev/sda5
menuentry "Windows Recovery Environment (loader) (on /dev/sda5)" --class windows --class os {
insmod part_gpt
insmod ntfs
set root='(hd0,gpt5)'
search --no-floppy --fs-uuid --set=root DEB0BFC8B0BFA585
drivemap -s (hd0) ${root}
chainloader +1
}
### END /etc/grub.d/30_os-prober ###
### BEGIN /etc/grub.d/40_custom ###
# This file provides an easy way to add custom menu entries. Simply type the
# menu entries you want to add after this comment. Be careful not to change
# the 'exec tail' line above.
### END /etc/grub.d/40_custom ###
### BEGIN /etc/grub.d/41_custom ###
if [ -f $prefix/custom.cfg ]; then
source $prefix/custom.cfg;
fi
### END /etc/grub.d/41_custom ###
done
I'm thinking that Windows 8.1 just isn't compatable with my computer. I'm thinking about just formatting the windows partition and installing Windows 7 if nothing else works. I already have a backup of my important files so losing my windows 8.1 won't concern me. If not for a lot of games I play only working on windows I would just get rid of it all together and strictly use Linux.
Ahh yes Windows and its fun non-transferrable EULAS - plus Win8 probably is set up to work with UEFI. Better of switching Windows to 7, and perhaps upgrade that to 10 (it's pretty nice, as far as Windows goes)
Yeah I'm still waiting on my email from microsoft about the windows 10 i reserved. im just going to install windows 7 then update to 10..Okay well thanks everyone for the help. This was my first thread here and I couldn't be happier that I got all the responses that I did. I'm going to go ahead and mark this solved.
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.