Grub returns File not found when booting on a new disk with Debian Jessie
Clash Royale CLAN TAG#URR8PPP
I installed Debian Jessie on a new hard disk, and wanted to boot from this new disk. At the end of Debian setup, I choosed setup Grub also. But when booting, Grub falls into rescue mode with a File not found error. I tried several guides I found around to try to have it up again, with no success.
Here is my configuration (I booted on a live Knoppix distro)
knoppix@Microknoppix:~$ lsblk -f
NAME FSTYPE LABEL MOUNTPOINT
sda
└─sda1 ext4
sdb
├─sdb1 ext4
├─sdb2
└─sdb5 swap
sdc
└─sdc1 ntfs Stock
sdd
├─sdd1 ext4 Debian
├─sdd2
└─sdd5 swap
sdh
└─sdh1 ntfs My Passport
sr0 iso9660 KNOPPIX /mnt-system
sr1 udf WD SmartWare
zram0 swap [SWAP]
cloop0 iso9660 KNOPPIX_FS /KNOPPIX
blkid
/dev/cloop0: LABEL="KNOPPIX_FS" TYPE="iso9660"
/dev/zram0: UUID="770d53d4-32d4-4810-988a-ffb80edecc8f" TYPE="swap"
/dev/sda1: UUID="2a0bdecf-9074-40de-8d23-bcaf01af17bb" TYPE="ext4"
/dev/sdb1: UUID="a4eaeb3b-27d1-4285-a364-fcdfa601fb82" TYPE="ext4"
/dev/sdb5: UUID="76381585-358a-46a1-bc16-feb51b08fe90" TYPE="swap"
/dev/sdc1: LABEL="Stock" UUID="A2904C19904BF1F9" TYPE="ntfs"
/dev/sdd1: LABEL="Debian" UUID="c45c0acc-f414-4c3e-a4ba-b3c1a33c3cbd" TYPE="ext4"
/dev/sdd5: UUID="2f0c8892-f4a8-4312-bc19-1e8d72f23e6c" TYPE="swap"
/dev/sr0: LABEL="KNOPPIX" TYPE="iso9660"
/dev/sdh1: LABEL="My Passport" UUID="325220A852207331" TYPE="ntfs"
/dev/sr1: LABEL="WD SmartWare" TYPE="udf"
parted
(parted) print all
Model: ATA Maxtor 7V250F0 (scsi)
Disk /dev/sda: 251GB
Sector size (logical/physical): 512B/512B
Partition Table: msdos
Disk Flags:
Number Start End Size Type File system Flags
1 1049kB 251GB 251GB primary ext4 boot
Model: ATA Maxtor 7V300F0 (scsi)
Disk /dev/sdb: 300GB
Sector size (logical/physical): 512B/512B
Partition Table: msdos
Disk Flags:
Number Start End Size Type File system Flags
1 1049kB 284GB 284GB primary ext4
2 284GB 300GB 16.1GB extended
5 284GB 300GB 16.1GB logical linux-swap(v1)
...
The grub.cfg file contains thism which looks correct
### BEGIN /etc/grub.d/10_linux ###
function gfxmode
set gfxpayload="$1"
set linux_gfx_mode=
export linux_gfx_mode
menuentry 'Debian GNU/Linux' --class debian --class gnu-linux --class gnu --class os $menuentry_id_option 'gnulinux-simple-2a0bdecf-9074-40de-8d23-bcaf01af17bb'
load_video
insmod gzio
if [ x$grub_platform = xxen ]; then insmod xzio; insmod lzopio; fi
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 2a0bdecf-9074-40de-8d23-bcaf01af17bb
else
search --no-floppy --fs-uuid --set=root 2a0bdecf-9074-40de-8d23-bcaf01af17bb
fi
echo 'Loading Linux 3.16.0-4-amd64 ...'
linux /boot/vmlinuz-3.16.0-4-amd64 root=UUID=2a0bdecf-9074-40de-8d23-bcaf01af17bb ro quiet
echo 'Loading initial ramdisk ...'
initrd /boot/initrd.img-3.16.0-4-amd64
Note that the .mod files are in a seperate directory /boot/grub/i386-pc Is it usual?
Thank you for helping me understand what is wrong and how to solve this?
grub2
add a comment |
I installed Debian Jessie on a new hard disk, and wanted to boot from this new disk. At the end of Debian setup, I choosed setup Grub also. But when booting, Grub falls into rescue mode with a File not found error. I tried several guides I found around to try to have it up again, with no success.
Here is my configuration (I booted on a live Knoppix distro)
knoppix@Microknoppix:~$ lsblk -f
NAME FSTYPE LABEL MOUNTPOINT
sda
└─sda1 ext4
sdb
├─sdb1 ext4
├─sdb2
└─sdb5 swap
sdc
└─sdc1 ntfs Stock
sdd
├─sdd1 ext4 Debian
├─sdd2
└─sdd5 swap
sdh
└─sdh1 ntfs My Passport
sr0 iso9660 KNOPPIX /mnt-system
sr1 udf WD SmartWare
zram0 swap [SWAP]
cloop0 iso9660 KNOPPIX_FS /KNOPPIX
blkid
/dev/cloop0: LABEL="KNOPPIX_FS" TYPE="iso9660"
/dev/zram0: UUID="770d53d4-32d4-4810-988a-ffb80edecc8f" TYPE="swap"
/dev/sda1: UUID="2a0bdecf-9074-40de-8d23-bcaf01af17bb" TYPE="ext4"
/dev/sdb1: UUID="a4eaeb3b-27d1-4285-a364-fcdfa601fb82" TYPE="ext4"
/dev/sdb5: UUID="76381585-358a-46a1-bc16-feb51b08fe90" TYPE="swap"
/dev/sdc1: LABEL="Stock" UUID="A2904C19904BF1F9" TYPE="ntfs"
/dev/sdd1: LABEL="Debian" UUID="c45c0acc-f414-4c3e-a4ba-b3c1a33c3cbd" TYPE="ext4"
/dev/sdd5: UUID="2f0c8892-f4a8-4312-bc19-1e8d72f23e6c" TYPE="swap"
/dev/sr0: LABEL="KNOPPIX" TYPE="iso9660"
/dev/sdh1: LABEL="My Passport" UUID="325220A852207331" TYPE="ntfs"
/dev/sr1: LABEL="WD SmartWare" TYPE="udf"
parted
(parted) print all
Model: ATA Maxtor 7V250F0 (scsi)
Disk /dev/sda: 251GB
Sector size (logical/physical): 512B/512B
Partition Table: msdos
Disk Flags:
Number Start End Size Type File system Flags
1 1049kB 251GB 251GB primary ext4 boot
Model: ATA Maxtor 7V300F0 (scsi)
Disk /dev/sdb: 300GB
Sector size (logical/physical): 512B/512B
Partition Table: msdos
Disk Flags:
Number Start End Size Type File system Flags
1 1049kB 284GB 284GB primary ext4
2 284GB 300GB 16.1GB extended
5 284GB 300GB 16.1GB logical linux-swap(v1)
...
The grub.cfg file contains thism which looks correct
### BEGIN /etc/grub.d/10_linux ###
function gfxmode
set gfxpayload="$1"
set linux_gfx_mode=
export linux_gfx_mode
menuentry 'Debian GNU/Linux' --class debian --class gnu-linux --class gnu --class os $menuentry_id_option 'gnulinux-simple-2a0bdecf-9074-40de-8d23-bcaf01af17bb'
load_video
insmod gzio
if [ x$grub_platform = xxen ]; then insmod xzio; insmod lzopio; fi
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 2a0bdecf-9074-40de-8d23-bcaf01af17bb
else
search --no-floppy --fs-uuid --set=root 2a0bdecf-9074-40de-8d23-bcaf01af17bb
fi
echo 'Loading Linux 3.16.0-4-amd64 ...'
linux /boot/vmlinuz-3.16.0-4-amd64 root=UUID=2a0bdecf-9074-40de-8d23-bcaf01af17bb ro quiet
echo 'Loading initial ramdisk ...'
initrd /boot/initrd.img-3.16.0-4-amd64
Note that the .mod files are in a seperate directory /boot/grub/i386-pc Is it usual?
Thank you for helping me understand what is wrong and how to solve this?
grub2
add a comment |
I installed Debian Jessie on a new hard disk, and wanted to boot from this new disk. At the end of Debian setup, I choosed setup Grub also. But when booting, Grub falls into rescue mode with a File not found error. I tried several guides I found around to try to have it up again, with no success.
Here is my configuration (I booted on a live Knoppix distro)
knoppix@Microknoppix:~$ lsblk -f
NAME FSTYPE LABEL MOUNTPOINT
sda
└─sda1 ext4
sdb
├─sdb1 ext4
├─sdb2
└─sdb5 swap
sdc
└─sdc1 ntfs Stock
sdd
├─sdd1 ext4 Debian
├─sdd2
└─sdd5 swap
sdh
└─sdh1 ntfs My Passport
sr0 iso9660 KNOPPIX /mnt-system
sr1 udf WD SmartWare
zram0 swap [SWAP]
cloop0 iso9660 KNOPPIX_FS /KNOPPIX
blkid
/dev/cloop0: LABEL="KNOPPIX_FS" TYPE="iso9660"
/dev/zram0: UUID="770d53d4-32d4-4810-988a-ffb80edecc8f" TYPE="swap"
/dev/sda1: UUID="2a0bdecf-9074-40de-8d23-bcaf01af17bb" TYPE="ext4"
/dev/sdb1: UUID="a4eaeb3b-27d1-4285-a364-fcdfa601fb82" TYPE="ext4"
/dev/sdb5: UUID="76381585-358a-46a1-bc16-feb51b08fe90" TYPE="swap"
/dev/sdc1: LABEL="Stock" UUID="A2904C19904BF1F9" TYPE="ntfs"
/dev/sdd1: LABEL="Debian" UUID="c45c0acc-f414-4c3e-a4ba-b3c1a33c3cbd" TYPE="ext4"
/dev/sdd5: UUID="2f0c8892-f4a8-4312-bc19-1e8d72f23e6c" TYPE="swap"
/dev/sr0: LABEL="KNOPPIX" TYPE="iso9660"
/dev/sdh1: LABEL="My Passport" UUID="325220A852207331" TYPE="ntfs"
/dev/sr1: LABEL="WD SmartWare" TYPE="udf"
parted
(parted) print all
Model: ATA Maxtor 7V250F0 (scsi)
Disk /dev/sda: 251GB
Sector size (logical/physical): 512B/512B
Partition Table: msdos
Disk Flags:
Number Start End Size Type File system Flags
1 1049kB 251GB 251GB primary ext4 boot
Model: ATA Maxtor 7V300F0 (scsi)
Disk /dev/sdb: 300GB
Sector size (logical/physical): 512B/512B
Partition Table: msdos
Disk Flags:
Number Start End Size Type File system Flags
1 1049kB 284GB 284GB primary ext4
2 284GB 300GB 16.1GB extended
5 284GB 300GB 16.1GB logical linux-swap(v1)
...
The grub.cfg file contains thism which looks correct
### BEGIN /etc/grub.d/10_linux ###
function gfxmode
set gfxpayload="$1"
set linux_gfx_mode=
export linux_gfx_mode
menuentry 'Debian GNU/Linux' --class debian --class gnu-linux --class gnu --class os $menuentry_id_option 'gnulinux-simple-2a0bdecf-9074-40de-8d23-bcaf01af17bb'
load_video
insmod gzio
if [ x$grub_platform = xxen ]; then insmod xzio; insmod lzopio; fi
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 2a0bdecf-9074-40de-8d23-bcaf01af17bb
else
search --no-floppy --fs-uuid --set=root 2a0bdecf-9074-40de-8d23-bcaf01af17bb
fi
echo 'Loading Linux 3.16.0-4-amd64 ...'
linux /boot/vmlinuz-3.16.0-4-amd64 root=UUID=2a0bdecf-9074-40de-8d23-bcaf01af17bb ro quiet
echo 'Loading initial ramdisk ...'
initrd /boot/initrd.img-3.16.0-4-amd64
Note that the .mod files are in a seperate directory /boot/grub/i386-pc Is it usual?
Thank you for helping me understand what is wrong and how to solve this?
grub2
I installed Debian Jessie on a new hard disk, and wanted to boot from this new disk. At the end of Debian setup, I choosed setup Grub also. But when booting, Grub falls into rescue mode with a File not found error. I tried several guides I found around to try to have it up again, with no success.
Here is my configuration (I booted on a live Knoppix distro)
knoppix@Microknoppix:~$ lsblk -f
NAME FSTYPE LABEL MOUNTPOINT
sda
└─sda1 ext4
sdb
├─sdb1 ext4
├─sdb2
└─sdb5 swap
sdc
└─sdc1 ntfs Stock
sdd
├─sdd1 ext4 Debian
├─sdd2
└─sdd5 swap
sdh
└─sdh1 ntfs My Passport
sr0 iso9660 KNOPPIX /mnt-system
sr1 udf WD SmartWare
zram0 swap [SWAP]
cloop0 iso9660 KNOPPIX_FS /KNOPPIX
blkid
/dev/cloop0: LABEL="KNOPPIX_FS" TYPE="iso9660"
/dev/zram0: UUID="770d53d4-32d4-4810-988a-ffb80edecc8f" TYPE="swap"
/dev/sda1: UUID="2a0bdecf-9074-40de-8d23-bcaf01af17bb" TYPE="ext4"
/dev/sdb1: UUID="a4eaeb3b-27d1-4285-a364-fcdfa601fb82" TYPE="ext4"
/dev/sdb5: UUID="76381585-358a-46a1-bc16-feb51b08fe90" TYPE="swap"
/dev/sdc1: LABEL="Stock" UUID="A2904C19904BF1F9" TYPE="ntfs"
/dev/sdd1: LABEL="Debian" UUID="c45c0acc-f414-4c3e-a4ba-b3c1a33c3cbd" TYPE="ext4"
/dev/sdd5: UUID="2f0c8892-f4a8-4312-bc19-1e8d72f23e6c" TYPE="swap"
/dev/sr0: LABEL="KNOPPIX" TYPE="iso9660"
/dev/sdh1: LABEL="My Passport" UUID="325220A852207331" TYPE="ntfs"
/dev/sr1: LABEL="WD SmartWare" TYPE="udf"
parted
(parted) print all
Model: ATA Maxtor 7V250F0 (scsi)
Disk /dev/sda: 251GB
Sector size (logical/physical): 512B/512B
Partition Table: msdos
Disk Flags:
Number Start End Size Type File system Flags
1 1049kB 251GB 251GB primary ext4 boot
Model: ATA Maxtor 7V300F0 (scsi)
Disk /dev/sdb: 300GB
Sector size (logical/physical): 512B/512B
Partition Table: msdos
Disk Flags:
Number Start End Size Type File system Flags
1 1049kB 284GB 284GB primary ext4
2 284GB 300GB 16.1GB extended
5 284GB 300GB 16.1GB logical linux-swap(v1)
...
The grub.cfg file contains thism which looks correct
### BEGIN /etc/grub.d/10_linux ###
function gfxmode
set gfxpayload="$1"
set linux_gfx_mode=
export linux_gfx_mode
menuentry 'Debian GNU/Linux' --class debian --class gnu-linux --class gnu --class os $menuentry_id_option 'gnulinux-simple-2a0bdecf-9074-40de-8d23-bcaf01af17bb'
load_video
insmod gzio
if [ x$grub_platform = xxen ]; then insmod xzio; insmod lzopio; fi
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 2a0bdecf-9074-40de-8d23-bcaf01af17bb
else
search --no-floppy --fs-uuid --set=root 2a0bdecf-9074-40de-8d23-bcaf01af17bb
fi
echo 'Loading Linux 3.16.0-4-amd64 ...'
linux /boot/vmlinuz-3.16.0-4-amd64 root=UUID=2a0bdecf-9074-40de-8d23-bcaf01af17bb ro quiet
echo 'Loading initial ramdisk ...'
initrd /boot/initrd.img-3.16.0-4-amd64
Note that the .mod files are in a seperate directory /boot/grub/i386-pc Is it usual?
Thank you for helping me understand what is wrong and how to solve this?
grub2
grub2
asked Apr 21 '15 at 22:33
user1185081user1185081
15919
15919
add a comment |
add a comment |
1 Answer
1
active
oldest
votes
The line set root='hd0,msdos1'
in your grub configuration tells grub that the root of your filesystem you want to work with is in the first partition of the first disk, which is the same as /dev/sda1.
Your parted output shows that /dev/sda1 has its bootable flag set, but a different partition, /dev/sdd1, is the one labeled "Debian" and I'm assuming your root filesystem lives there. If that's true you will need to edit your grub.cfg so grub is working with the right disk.
I would recommend making a backup of your grub.cfg and then changing the set root='hd0,msdos1'
line to set root='hd3,msdos1'
and repeating that change anywhere you see hd0 mentioned. Then use parted to set the bootable flag for /dev/sdd1 and try to boot Debian. Best of luck!
Actually, Debian is a former install. hd0 is the disk referenced in fstab, where is /dev/sda1. Switching to hd3 returns the same error!
– user1185081
Apr 22 '15 at 21:08
Huh, I don't know what's wrong then. Everything about your configuration looks identical to the one I use, and same for the location of the .mod files. Is your grub folder where you expect it to be?
– ivor-c
Apr 22 '15 at 21:20
Yes, they are targeting the actual files in boot/ ... I ll try again from grub rescue ...
– user1185081
Apr 22 '15 at 21:25
If all your files are where they belong and still can't be found your best bet may be toupdate-grub
... Good luck
– ivor-c
Apr 22 '15 at 21:30
Well, digging with Grub rescue shows one thing: /dev/sda is pointing to hd3. The Grub I start with may not be the one I am trying to configure! I shall start from BIOS boot order to make sure of which disk I am booting on ...
– user1185081
Apr 23 '15 at 7:17
add a comment |
Your Answer
StackExchange.ready(function()
var channelOptions =
tags: "".split(" "),
id: "106"
;
initTagRenderer("".split(" "), "".split(" "), channelOptions);
StackExchange.using("externalEditor", function()
// Have to fire editor after snippets, if snippets enabled
if (StackExchange.settings.snippets.snippetsEnabled)
StackExchange.using("snippets", function()
createEditor();
);
else
createEditor();
);
function createEditor()
StackExchange.prepareEditor(
heartbeatType: 'answer',
autoActivateHeartbeat: false,
convertImagesToLinks: false,
noModals: true,
showLowRepImageUploadWarning: true,
reputationToPostImages: null,
bindNavPrevention: true,
postfix: "",
imageUploader:
brandingHtml: "Powered by u003ca class="icon-imgur-white" href="https://imgur.com/"u003eu003c/au003e",
contentPolicyHtml: "User contributions licensed under u003ca href="https://creativecommons.org/licenses/by-sa/3.0/"u003ecc by-sa 3.0 with attribution requiredu003c/au003e u003ca href="https://stackoverflow.com/legal/content-policy"u003e(content policy)u003c/au003e",
allowUrls: true
,
onDemand: true,
discardSelector: ".discard-answer"
,immediatelyShowMarkdownHelp:true
);
);
Sign up or log in
StackExchange.ready(function ()
StackExchange.helpers.onClickDraftSave('#login-link');
);
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
StackExchange.ready(
function ()
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2funix.stackexchange.com%2fquestions%2f197750%2fgrub-returns-file-not-found-when-booting-on-a-new-disk-with-debian-jessie%23new-answer', 'question_page');
);
Post as a guest
Required, but never shown
1 Answer
1
active
oldest
votes
1 Answer
1
active
oldest
votes
active
oldest
votes
active
oldest
votes
The line set root='hd0,msdos1'
in your grub configuration tells grub that the root of your filesystem you want to work with is in the first partition of the first disk, which is the same as /dev/sda1.
Your parted output shows that /dev/sda1 has its bootable flag set, but a different partition, /dev/sdd1, is the one labeled "Debian" and I'm assuming your root filesystem lives there. If that's true you will need to edit your grub.cfg so grub is working with the right disk.
I would recommend making a backup of your grub.cfg and then changing the set root='hd0,msdos1'
line to set root='hd3,msdos1'
and repeating that change anywhere you see hd0 mentioned. Then use parted to set the bootable flag for /dev/sdd1 and try to boot Debian. Best of luck!
Actually, Debian is a former install. hd0 is the disk referenced in fstab, where is /dev/sda1. Switching to hd3 returns the same error!
– user1185081
Apr 22 '15 at 21:08
Huh, I don't know what's wrong then. Everything about your configuration looks identical to the one I use, and same for the location of the .mod files. Is your grub folder where you expect it to be?
– ivor-c
Apr 22 '15 at 21:20
Yes, they are targeting the actual files in boot/ ... I ll try again from grub rescue ...
– user1185081
Apr 22 '15 at 21:25
If all your files are where they belong and still can't be found your best bet may be toupdate-grub
... Good luck
– ivor-c
Apr 22 '15 at 21:30
Well, digging with Grub rescue shows one thing: /dev/sda is pointing to hd3. The Grub I start with may not be the one I am trying to configure! I shall start from BIOS boot order to make sure of which disk I am booting on ...
– user1185081
Apr 23 '15 at 7:17
add a comment |
The line set root='hd0,msdos1'
in your grub configuration tells grub that the root of your filesystem you want to work with is in the first partition of the first disk, which is the same as /dev/sda1.
Your parted output shows that /dev/sda1 has its bootable flag set, but a different partition, /dev/sdd1, is the one labeled "Debian" and I'm assuming your root filesystem lives there. If that's true you will need to edit your grub.cfg so grub is working with the right disk.
I would recommend making a backup of your grub.cfg and then changing the set root='hd0,msdos1'
line to set root='hd3,msdos1'
and repeating that change anywhere you see hd0 mentioned. Then use parted to set the bootable flag for /dev/sdd1 and try to boot Debian. Best of luck!
Actually, Debian is a former install. hd0 is the disk referenced in fstab, where is /dev/sda1. Switching to hd3 returns the same error!
– user1185081
Apr 22 '15 at 21:08
Huh, I don't know what's wrong then. Everything about your configuration looks identical to the one I use, and same for the location of the .mod files. Is your grub folder where you expect it to be?
– ivor-c
Apr 22 '15 at 21:20
Yes, they are targeting the actual files in boot/ ... I ll try again from grub rescue ...
– user1185081
Apr 22 '15 at 21:25
If all your files are where they belong and still can't be found your best bet may be toupdate-grub
... Good luck
– ivor-c
Apr 22 '15 at 21:30
Well, digging with Grub rescue shows one thing: /dev/sda is pointing to hd3. The Grub I start with may not be the one I am trying to configure! I shall start from BIOS boot order to make sure of which disk I am booting on ...
– user1185081
Apr 23 '15 at 7:17
add a comment |
The line set root='hd0,msdos1'
in your grub configuration tells grub that the root of your filesystem you want to work with is in the first partition of the first disk, which is the same as /dev/sda1.
Your parted output shows that /dev/sda1 has its bootable flag set, but a different partition, /dev/sdd1, is the one labeled "Debian" and I'm assuming your root filesystem lives there. If that's true you will need to edit your grub.cfg so grub is working with the right disk.
I would recommend making a backup of your grub.cfg and then changing the set root='hd0,msdos1'
line to set root='hd3,msdos1'
and repeating that change anywhere you see hd0 mentioned. Then use parted to set the bootable flag for /dev/sdd1 and try to boot Debian. Best of luck!
The line set root='hd0,msdos1'
in your grub configuration tells grub that the root of your filesystem you want to work with is in the first partition of the first disk, which is the same as /dev/sda1.
Your parted output shows that /dev/sda1 has its bootable flag set, but a different partition, /dev/sdd1, is the one labeled "Debian" and I'm assuming your root filesystem lives there. If that's true you will need to edit your grub.cfg so grub is working with the right disk.
I would recommend making a backup of your grub.cfg and then changing the set root='hd0,msdos1'
line to set root='hd3,msdos1'
and repeating that change anywhere you see hd0 mentioned. Then use parted to set the bootable flag for /dev/sdd1 and try to boot Debian. Best of luck!
answered Apr 22 '15 at 0:53
ivor-civor-c
313
313
Actually, Debian is a former install. hd0 is the disk referenced in fstab, where is /dev/sda1. Switching to hd3 returns the same error!
– user1185081
Apr 22 '15 at 21:08
Huh, I don't know what's wrong then. Everything about your configuration looks identical to the one I use, and same for the location of the .mod files. Is your grub folder where you expect it to be?
– ivor-c
Apr 22 '15 at 21:20
Yes, they are targeting the actual files in boot/ ... I ll try again from grub rescue ...
– user1185081
Apr 22 '15 at 21:25
If all your files are where they belong and still can't be found your best bet may be toupdate-grub
... Good luck
– ivor-c
Apr 22 '15 at 21:30
Well, digging with Grub rescue shows one thing: /dev/sda is pointing to hd3. The Grub I start with may not be the one I am trying to configure! I shall start from BIOS boot order to make sure of which disk I am booting on ...
– user1185081
Apr 23 '15 at 7:17
add a comment |
Actually, Debian is a former install. hd0 is the disk referenced in fstab, where is /dev/sda1. Switching to hd3 returns the same error!
– user1185081
Apr 22 '15 at 21:08
Huh, I don't know what's wrong then. Everything about your configuration looks identical to the one I use, and same for the location of the .mod files. Is your grub folder where you expect it to be?
– ivor-c
Apr 22 '15 at 21:20
Yes, they are targeting the actual files in boot/ ... I ll try again from grub rescue ...
– user1185081
Apr 22 '15 at 21:25
If all your files are where they belong and still can't be found your best bet may be toupdate-grub
... Good luck
– ivor-c
Apr 22 '15 at 21:30
Well, digging with Grub rescue shows one thing: /dev/sda is pointing to hd3. The Grub I start with may not be the one I am trying to configure! I shall start from BIOS boot order to make sure of which disk I am booting on ...
– user1185081
Apr 23 '15 at 7:17
Actually, Debian is a former install. hd0 is the disk referenced in fstab, where is /dev/sda1. Switching to hd3 returns the same error!
– user1185081
Apr 22 '15 at 21:08
Actually, Debian is a former install. hd0 is the disk referenced in fstab, where is /dev/sda1. Switching to hd3 returns the same error!
– user1185081
Apr 22 '15 at 21:08
Huh, I don't know what's wrong then. Everything about your configuration looks identical to the one I use, and same for the location of the .mod files. Is your grub folder where you expect it to be?
– ivor-c
Apr 22 '15 at 21:20
Huh, I don't know what's wrong then. Everything about your configuration looks identical to the one I use, and same for the location of the .mod files. Is your grub folder where you expect it to be?
– ivor-c
Apr 22 '15 at 21:20
Yes, they are targeting the actual files in boot/ ... I ll try again from grub rescue ...
– user1185081
Apr 22 '15 at 21:25
Yes, they are targeting the actual files in boot/ ... I ll try again from grub rescue ...
– user1185081
Apr 22 '15 at 21:25
If all your files are where they belong and still can't be found your best bet may be to
update-grub
... Good luck– ivor-c
Apr 22 '15 at 21:30
If all your files are where they belong and still can't be found your best bet may be to
update-grub
... Good luck– ivor-c
Apr 22 '15 at 21:30
Well, digging with Grub rescue shows one thing: /dev/sda is pointing to hd3. The Grub I start with may not be the one I am trying to configure! I shall start from BIOS boot order to make sure of which disk I am booting on ...
– user1185081
Apr 23 '15 at 7:17
Well, digging with Grub rescue shows one thing: /dev/sda is pointing to hd3. The Grub I start with may not be the one I am trying to configure! I shall start from BIOS boot order to make sure of which disk I am booting on ...
– user1185081
Apr 23 '15 at 7:17
add a comment |
Thanks for contributing an answer to Unix & Linux Stack Exchange!
- Please be sure to answer the question. Provide details and share your research!
But avoid …
- Asking for help, clarification, or responding to other answers.
- Making statements based on opinion; back them up with references or personal experience.
To learn more, see our tips on writing great answers.
Sign up or log in
StackExchange.ready(function ()
StackExchange.helpers.onClickDraftSave('#login-link');
);
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
StackExchange.ready(
function ()
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2funix.stackexchange.com%2fquestions%2f197750%2fgrub-returns-file-not-found-when-booting-on-a-new-disk-with-debian-jessie%23new-answer', 'question_page');
);
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function ()
StackExchange.helpers.onClickDraftSave('#login-link');
);
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function ()
StackExchange.helpers.onClickDraftSave('#login-link');
);
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function ()
StackExchange.helpers.onClickDraftSave('#login-link');
);
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown