Changing hard drive number in Grub


Recommended Posts

I have an SSD and a normal HDD in my system

SSD was in the laptop and HDD was in a caddy in the optical bay

when SSD was in everything worked fine

when i then add the HDD in the optical bay i get a boot loop when trying to load grub like the laptop is trying to boot from the optical bay first, this is disabled in bios

If i switch the SSD into the optical bay and HDD into laptop it all works fine

Below is my grub2.cfg

I have tried chaning all the hd0 to hd1 but this makes no difference

here is my grub2.cfg


#
# DO NOT EDIT THIS FILE
#
# It is automatically generated by grub2-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 [ x"${feature_menuentry_id}" = xy ]; then
menuentry_id_option="--id"
else
menuentry_id_option=""
fi
export menuentry_id_option
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
}
function load_video {
if [ x$feature_all_video_module = xy ]; then
insmod all_video
else
insmod efi_gop
insmod efi_uga
insmod ieee1275_fb
insmod vbe
insmod vga
insmod video_bochs
insmod video_cirrus
fi
}
if [ x$feature_default_font_path = xy ] ; then
font=unicode
else
insmod part_msdos
insmod ext2
set root='hd0,msdos2'
if [ x$feature_platform_search_hint = xy ]; then
search --no-floppy --fs-uuid --set=root --hint-bios=hd0,msdos2 --hint-efi=hd0,msdos2 --hint-baremetal=ahci0,msdos2 --hint='hd0,msdos2' e5b30aa2-a4b6-41a3-9e0a-6688252d36ee
else
search --no-floppy --fs-uuid --set=root e5b30aa2-a4b6-41a3-9e0a-6688252d36ee
fi
font="/usr/share/grub/unicode.pf2"
fi
if loadfont $font ; then
set gfxmode=auto
load_video
insmod gfxterm
set locale_dir=$prefix/locale
set lang=en_GB
insmod gettext
fi
terminal_output gfxterm
insmod part_msdos
insmod ext2
set root='hd0,msdos1'
if [ x$feature_platform_search_hint = xy ]; then
search --no-floppy --fs-uuid --set=root --hint-bios=hd0,msdos1 --hint-efi=hd0,msdos1 --hint-baremetal=ahci0,msdos1 --hint='hd0,msdos1' 8351a5aa-4bfd-4c45-872c-2ae6dc431e37
else
search --no-floppy --fs-uuid --set=root 8351a5aa-4bfd-4c45-872c-2ae6dc431e37
fi
insmod gfxmenu
loadfont ($root)/grub2/themes/system/DejaVuSans-10.pf2
loadfont ($root)/grub2/themes/system/DejaVuSans-12.pf2
loadfont ($root)/grub2/themes/system/DejaVuSans-Bold-14.pf2
loadfont ($root)/grub2/fonts/unicode.pf2
insmod png
set theme=($root)/grub2/themes/system/theme.txt
export theme
set timeout=5
### END /etc/grub.d/00_header ###
### BEGIN /etc/grub.d/10_linux ###
menuentry 'Fedora (3.7.5-201.fc18.x86_64)' --class fedora --class gnu-linux --class gnu --class os $menuentry_id_option 'gnulinux-simple-e5b30aa2-a4b6-41a3-9e0a-6688252d36ee' {
load_video
set gfxpayload=keep
insmod gzio
insmod part_msdos
insmod ext2
set root='hd0,msdos1'
if [ x$feature_platform_search_hint = xy ]; then
search --no-floppy --fs-uuid --set=root --hint-bios=hd0,msdos1 --hint-efi=hd0,msdos1 --hint-baremetal=ahci0,msdos1 --hint='hd0,msdos1' 8351a5aa-4bfd-4c45-872c-2ae6dc431e37
else
search --no-floppy --fs-uuid --set=root 8351a5aa-4bfd-4c45-872c-2ae6dc431e37
fi
echo 'Loading Fedora (3.7.5-201.fc18.x86_64)'
linux /vmlinuz-3.7.5-201.fc18.x86_64 root=UUID=e5b30aa2-a4b6-41a3-9e0a-6688252d36ee ro rd.md=0 rd.lvm=0 rd.dm=0 rd.luks=0 vconsole.keymap=uk rhgb quiet LANG=en_GB.UTF-8
echo 'Loading initial ramdisk ...'
initrd /initramfs-3.7.5-201.fc18.x86_64.img
}
menuentry 'Fedora (3.7.4-204.fc18.x86_64)' --class fedora --class gnu-linux --class gnu --class os $menuentry_id_option 'gnulinux-simple-e5b30aa2-a4b6-41a3-9e0a-6688252d36ee' {
load_video
set gfxpayload=keep
insmod gzio
insmod part_msdos
insmod ext2
set root='hd0,msdos1'
if [ x$feature_platform_search_hint = xy ]; then
search --no-floppy --fs-uuid --set=root --hint-bios=hd0,msdos1 --hint-efi=hd0,msdos1 --hint-baremetal=ahci0,msdos1 --hint='hd0,msdos1' 8351a5aa-4bfd-4c45-872c-2ae6dc431e37
else
search --no-floppy --fs-uuid --set=root 8351a5aa-4bfd-4c45-872c-2ae6dc431e37
fi
echo 'Loading Fedora (3.7.4-204.fc18.x86_64)'
linux /vmlinuz-3.7.4-204.fc18.x86_64 root=UUID=e5b30aa2-a4b6-41a3-9e0a-6688252d36ee ro rd.md=0 rd.lvm=0 rd.dm=0 rd.luks=0 vconsole.keymap=uk rhgb quiet LANG=en_GB.UTF-8
echo 'Loading initial ramdisk ...'
initrd /initramfs-3.7.4-204.fc18.x86_64.img
}
menuentry 'Fedora' --class fedora --class gnu-linux --class gnu --class os $menuentry_id_option 'gnulinux-simple-e5b30aa2-a4b6-41a3-9e0a-6688252d36ee' {
load_video
set gfxpayload=keep
insmod gzio
insmod part_msdos
insmod ext2
set root='hd0,msdos1'
if [ x$feature_platform_search_hint = xy ]; then
search --no-floppy --fs-uuid --set=root --hint-bios=hd0,msdos1 --hint-efi=hd0,msdos1 --hint-baremetal=ahci0,msdos1 --hint='hd0,msdos1' 8351a5aa-4bfd-4c45-872c-2ae6dc431e37
else
search --no-floppy --fs-uuid --set=root 8351a5aa-4bfd-4c45-872c-2ae6dc431e37
fi
echo 'Loading Linux 3.6.10-4.fc18.x86_64 ...'
linux /vmlinuz-3.6.10-4.fc18.x86_64 root=UUID=e5b30aa2-a4b6-41a3-9e0a-6688252d36ee ro rd.md=0 rd.lvm=0 rd.dm=0 rd.luks=0 vconsole.keymap=uk rhgb quiet
echo 'Loading initial ramdisk ...'
initrd /initramfs-3.6.10-4.fc18.x86_64.img
}
submenu 'Advanced options for Fedora' $menuentry_id_option 'gnulinux-advanced-e5b30aa2-a4b6-41a3-9e0a-6688252d36ee' {
menuentry 'Fedora, with Linux 3.6.10-4.fc18.x86_64' --class fedora --class gnu-linux --class gnu --class os $menuentry_id_option 'gnulinux-3.6.10-4.fc18.x86_64-advanced-e5b30aa2-a4b6-41a3-9e0a-6688252d36ee' {
load_video
set gfxpayload=keep
insmod gzio
insmod part_msdos
insmod ext2
set root='hd0,msdos1'
if [ x$feature_platform_search_hint = xy ]; then
search --no-floppy --fs-uuid --set=root --hint-bios=hd0,msdos1 --hint-efi=hd0,msdos1 --hint-baremetal=ahci0,msdos1 --hint='hd0,msdos1' 8351a5aa-4bfd-4c45-872c-2ae6dc431e37
else
search --no-floppy --fs-uuid --set=root 8351a5aa-4bfd-4c45-872c-2ae6dc431e37
fi
echo 'Loading Linux 3.6.10-4.fc18.x86_64 ...'
linux /vmlinuz-3.6.10-4.fc18.x86_64 root=UUID=e5b30aa2-a4b6-41a3-9e0a-6688252d36ee ro rd.md=0 rd.lvm=0 rd.dm=0 rd.luks=0 vconsole.keymap=uk rhgb quiet
echo 'Loading initial ramdisk ...'
initrd /initramfs-3.6.10-4.fc18.x86_64.img
}
}
### END /etc/grub.d/10_linux ###
### BEGIN /etc/grub.d/20_linux_xen ###
### END /etc/grub.d/20_linux_xen ###
### BEGIN /etc/grub.d/20_ppc_terminfo ###
### END /etc/grub.d/20_ppc_terminfo ###
### BEGIN /etc/grub.d/30_os-prober ###
### 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 ${config_directory}/custom.cfg ]; then
source ${config_directory}/custom.cfg
elif [ -z "${config_directory}" -a -f $prefix/custom.cfg ]; then
source $prefix/custom.cfg;
fi
### END /etc/grub.d/41_custom ###
[/CODE]

and here is my fstab

[CODE]
#
# /etc/fstab
# Created by anaconda on Sat Jan 26 19:50:30 2013
#
# Accessible filesystems, by reference, are maintained under '/dev/disk'
# See man pages fstab(5), findfs(8), mount(8) and/or blkid(8) for more info
#
UUID=e5b30aa2-a4b6-41a3-9e0a-6688252d36ee / ext4 defaults,discard,noatime,nodiratime 1 1
UUID=8351a5aa-4bfd-4c45-872c-2ae6dc431e37 /boot ext4 defaults,discard,noatime,nodiratime 1 2
UUID=5757507b-3c10-4495-89f9-a2b1eeaccaea /home ext4 defaults,discard,noatime,nodiratime 1 2
UUID=1794135c-6075-4f17-b3bb-2b6635fd6380 swap swap defaults,discard,noatime,nodiratime 0 0
none /tmp tmpfs defaults 0 0
/dev/sda1 /home/haggis/Storage ext4 defaults 0 0
[/CODE]

any ideas?

Link to comment
https://www.neowin.net/forum/topic/1135552-changing-hard-drive-number-in-grub/
Share on other sites

I might be being a complete idiots here

if i switch the drives around does SDA become SDB and vice versa?

Edit: that should not make any difference really should it?

Repitition?? u mean the different kernel entries?

and MSODS not sure when i did grub install it added it in there i have never touched it as grub is not something i am used to

Hi Haggis,

Sorry for the short replies I was stuck replying on my Andriod phone.

Repitition?? u mean the different kernel entries?

Exactly, why do you have all the initramfs's from different versions? You would only run into compatibility issues trying to boot from an older img. It is not urgent by any means just - extra data stored for no reason.

and MSODS not sure when i did grub install it added it in there i have never touched it as grub is not something i am used to

It is odd that both are set for root level. -- Why? I have always built my own and I am not sure what the advantage would be in your scenario.

This topic is now closed to further replies.
  • Recently Browsing   0 members

    • No registered users viewing this page.
  • Posts

    • Rufus alternative Ventoy now supports Windows 11's mandatory update, fixes major boot bug by Sayan Sen While Microsoft has its own official Media Creation Tool used for making bootable USB media, there are some popular third-party utilities as well which offer additional options like bypassing system requirements, Microsoft Account creation, and more. One of these is Ventoy, and the software has received its latest update today. In fact, the app actually got a slew of updates over the last couple of days, three version releases in total, to be specific. The first release, version 1.1.13, was pulled as there was some unspecified error in the update, and as such, the corrected version 1.1.14 was pushed out. Following that on very short notice, 1.1.15 was published as well. For those unfamiliar, Ventoy is an open-source utility that lets users create a bootable USB drive once and then simply copy ISO, WIM, IMG, VHD, or EFI files onto it without repeatedly formatting the drive. It supports both legacy BIOS and UEFI boot modes, Secure Boot, and a wide range of operating systems, making it one of the most versatile tools in the category. The biggest change in version 1.1.14 is an updated Secure Boot shim file aimed at resolving the UEFI CA 2023 issue, which is basically a compatibility problem that has affected Secure Boot environments on some systems. If you recall, we reported about severe boot issues on HP devices following the release of updated Secure Boot 2023 keys. For anyone who may not be aware, back in early 2024, Microsoft announced that it was updating Secure Boot keys as they were going to become 15 years old in 2026, which is also when they are set to expire. As such, the new 2023 certificates have been rolling out with the newest Windows 11 updates. Updated boot manager and Secure Boot certificates are crucial for protection against malware like bootkits. These are mandatory updates. Alongside that, the VentoyPlugson graphical plugin configurator was updated in sync with the release. The update also introduces a new VTOY_SECURE_BOOT_POLICY option within the Global Control plugin, giving users more flexibility in managing Secure Boot behavior. Ventoy has also received a fix for a startup issue when Secure Boot was disabled. Microsoft does officially allow users to boot systems without Secure Boot as long as the PC is Secure Boot capable. The full changelog is given below: Update secure boot shim file to solve the UEFI CA 2023 issue. The new release use a new CA, so you need to enroll the new key for the first boot time. VentoyPlugson update synchronously. Global control plugin add a VTOY_SECURE_BOOT_POLICY option. Fix the boot issue when Secure Boot is disabled in the UEFI firmware. You can download the latest version of the app here on Ventoy's official GitHub repo or from Neowin software stories.
    • Windows 11 is fine, no issues on any of the machines I've run it on since release. The stricter security requirements are a good thing, sometimes the baseline needs to change and people will winge, but it is what it is. Happened with the move from 9x to NT - broke compatability Happened with XP SP2 when security started to become a serious consideration Certainly happend with Vista that brought in UAC, the concept of not running as admin (something that has been the norm in Linux/Unix from pretty much the start) and a completely new driver stack. Windows 11 will probably get looked back at as the point where even consumer and SMB IT was dragged kicking and screaming into a somewhat secure by default configuration.
    • Bluestacks has been emulating Android on Windows for fifteen years. It's janky and riddled with ads though, so WSA looked like it was going to be a huge improvement over the emulator experience. Too bad Microsoft dropped the ball on that.
    • Classic. China would be nothing without Western, Japanese, and South Korean technology.
    • The world is larger then your small viewpoint. Plenty of scientists care about this, especially those involved in space.
  • Recent Achievements

    • Rookie
      krychek57 went up a rank
      Rookie
    • Grand Master
      Jaybonaut went up a rank
      Grand Master
    • One Year In
      Philsl earned a badge
      One Year In
    • Dedicated
      Scoobystu earned a badge
      Dedicated
    • First Post
      Tom Schmidt earned a badge
      First Post
  • Popular Contributors

    1. 1
      +primortal
      441
    2. 2
      +Edouard
      172
    3. 3
      PsYcHoKiLLa
      134
    4. 4
      Michael Scrip
      78
    5. 5
      Xenon
      77
  • Tell a friend

    Love Neowin? Tell a friend!