Booting from GRUB starts ok, but during the process it states: “Gave up waiting for root file system device.â€
Clash Royale CLAN TAG#URR8PPP
up vote
1
down vote
favorite
Thanks to a helpful member here, I got out of GRUB RESCUE environment and now I am able to start a boot from GRUB. I have a dual boot Debian 9 (controls the boot process) and W10 being the other possible boot. After performing a simple overclock setup over the BIOS (MSI X399 motherboard), the computer is unable to boot "fully" if I can say it like that, as it seems it gets stuck finding the root file system (see screenshot#2) Before the BIOS overclock, the sytem was booting happily with no root file system issues.
In the three screenshots you see:
(1) the GRUB commands I applied to start the boot
(2) the lines that followed on the screen as the machine is trying to boot. You can see that the boot gives up finding the "root file system", which I had setup at GRUB witht the command: "linux /boot.... ...root=/dev/sda6"
(3) the folders I have and zooming into /dev/ where obviously the "sda6" is not found.
Question please: is my original GRUB command "linux /boot/vmlinuz-4.9.0-6-amd64 root=/dev/sda6" wrong or is there something else not letting the boot go through?
Thank you very much for your insights.
debian dual-boot grub
asked Jun 21 at 8:58
Julio
111
add a comment |Â
up vote
1
down vote
favorite
Thanks to a helpful member here, I got out of GRUB RESCUE environment and now I am able to start a boot from GRUB. I have a dual boot Debian 9 (controls the boot process) and W10 being the other possible boot. After performing a simple overclock setup over the BIOS (MSI X399 motherboard), the computer is unable to boot "fully" if I can say it like that, as it seems it gets stuck finding the root file system (see screenshot#2) Before the BIOS overclock, the sytem was booting happily with no root file system issues.
In the three screenshots you see:
(1) the GRUB commands I applied to start the boot
(2) the lines that followed on the screen as the machine is trying to boot. You can see that the boot gives up finding the "root file system", which I had setup at GRUB witht the command: "linux /boot.... ...root=/dev/sda6"
(3) the folders I have and zooming into /dev/ where obviously the "sda6" is not found.
Question please: is my original GRUB command "linux /boot/vmlinuz-4.9.0-6-amd64 root=/dev/sda6" wrong or is there something else not letting the boot go through?
Thank you very much for your insights.
debian dual-boot grub
asked Jun 21 at 8:58
Julio
111
I think your initrd doesn't contain the driver for your hard drive controller. Boot with rescue cd, chroot to rootfs, edit/etc/initramfs-tools/initramfs.confandMODULES=all; then regenerate initrd withupdate-initramfs.
– Ipor Sircer
Jun 21 at 9:08
Thanks for this lead. I will definitely look into making a rescue CD (USB)
– Julio
Jun 21 at 22:46
add a comment |Â
up vote
1
down vote
favorite
up vote
1
down vote
favorite
Thanks to a helpful member here, I got out of GRUB RESCUE environment and now I am able to start a boot from GRUB. I have a dual boot Debian 9 (controls the boot process) and W10 being the other possible boot. After performing a simple overclock setup over the BIOS (MSI X399 motherboard), the computer is unable to boot "fully" if I can say it like that, as it seems it gets stuck finding the root file system (see screenshot#2) Before the BIOS overclock, the sytem was booting happily with no root file system issues.
In the three screenshots you see:
(1) the GRUB commands I applied to start the boot
(2) the lines that followed on the screen as the machine is trying to boot. You can see that the boot gives up finding the "root file system", which I had setup at GRUB witht the command: "linux /boot.... ...root=/dev/sda6"
(3) the folders I have and zooming into /dev/ where obviously the "sda6" is not found.
Question please: is my original GRUB command "linux /boot/vmlinuz-4.9.0-6-amd64 root=/dev/sda6" wrong or is there something else not letting the boot go through?
Thank you very much for your insights.
debian dual-boot grub
asked Jun 21 at 8:58
Julio
111
Thanks to a helpful member here, I got out of GRUB RESCUE environment and now I am able to start a boot from GRUB. I have a dual boot Debian 9 (controls the boot process) and W10 being the other possible boot. After performing a simple overclock setup over the BIOS (MSI X399 motherboard), the computer is unable to boot "fully" if I can say it like that, as it seems it gets stuck finding the root file system (see screenshot#2) Before the BIOS overclock, the sytem was booting happily with no root file system issues.
In the three screenshots you see:
(1) the GRUB commands I applied to start the boot
(2) the lines that followed on the screen as the machine is trying to boot. You can see that the boot gives up finding the "root file system", which I had setup at GRUB witht the command: "linux /boot.... ...root=/dev/sda6"
(3) the folders I have and zooming into /dev/ where obviously the "sda6" is not found.
Question please: is my original GRUB command "linux /boot/vmlinuz-4.9.0-6-amd64 root=/dev/sda6" wrong or is there something else not letting the boot go through?
Thank you very much for your insights.
debian dual-boot grub
asked Jun 21 at 8:58
Julio
111
asked Jun 21 at 8:58
Julio
111
asked Jun 21 at 8:58
Julio
111
asked Jun 21 at 8:58
Julio
111
111
I think your initrd doesn't contain the driver for your hard drive controller. Boot with rescue cd, chroot to rootfs, edit/etc/initramfs-tools/initramfs.confandMODULES=all; then regenerate initrd withupdate-initramfs.
– Ipor Sircer
Jun 21 at 9:08
Thanks for this lead. I will definitely look into making a rescue CD (USB)
– Julio
Jun 21 at 22:46
add a comment |Â
I think your initrd doesn't contain the driver for your hard drive controller. Boot with rescue cd, chroot to rootfs, edit/etc/initramfs-tools/initramfs.confandMODULES=all; then regenerate initrd withupdate-initramfs.
– Ipor Sircer
Jun 21 at 9:08
Thanks for this lead. I will definitely look into making a rescue CD (USB)
– Julio
Jun 21 at 22:46
I think your initrd doesn't contain the driver for your hard drive controller. Boot with rescue cd, chroot to rootfs, edit
/etc/initramfs-tools/initramfs.conf and MODULES=all; then regenerate initrd with update-initramfs.– Ipor Sircer
Jun 21 at 9:08
I think your initrd doesn't contain the driver for your hard drive controller. Boot with rescue cd, chroot to rootfs, edit
/etc/initramfs-tools/initramfs.conf and MODULES=all; then regenerate initrd with update-initramfs.– Ipor Sircer
Jun 21 at 9:08
Thanks for this lead. I will definitely look into making a rescue CD (USB)
– Julio
Jun 21 at 22:46
Thanks for this lead. I will definitely look into making a rescue CD (USB)
– Julio
Jun 21 at 22:46
add a comment |Â
active
oldest
votes
active
oldest
votes
active
oldest
votes
active
oldest
votes
active
oldest
votes
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
StackExchange.ready(
function ()
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2funix.stackexchange.com%2fquestions%2f451047%2fbooting-from-grub-starts-ok-but-during-the-process-it-states-gave-up-waiting%23new-answer', 'question_page');
);
Post as a guest
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
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
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
I think your initrd doesn't contain the driver for your hard drive controller. Boot with rescue cd, chroot to rootfs, edit
/etc/initramfs-tools/initramfs.confandMODULES=all; then regenerate initrd withupdate-initramfs.– Ipor Sircer
Jun 21 at 9:08
Thanks for this lead. I will definitely look into making a rescue CD (USB)
– Julio
Jun 21 at 22:46