GRUB boots into rescue mode, unknown filesystem

If none of the more specific forums is the right place to ask

GRUB boots into rescue mode, unknown filesystem

Postby getsetgo » 2017-10-26 22:35

Hello! Long story short, GRUB keeps booting into rescue mode and saying "unknown filesystem." This began happening after I tried to switch from the KDE edition of Manjaro to the xfce edition. So I tried installing Debian and Xubuntu instead, but with the same result for both. I've been doing manual partitioning during installations since I have a separate /home folder. I currently have a separate boot partition as well, as I believe someone suggested it when I came to the IRC for help a month or so ago.

Tried https://askubuntu.com/questions/142300/ ... rub-rescue but once I get to "insmod normal" I get "error: no such partition." Tried https://wiki.manjaro.org/index.php/Rest ... Bootloader but it doesn't recognize the EFI partition as being EFI.

Here's my inxi info (ran the command from Manjaro live media):

System: Host: manjaro Kernel: 4.9.50-1-MANJARO x86_64 bits: 64 gcc: 7.2.0
Desktop: N/A Distro: Manjaro Linux
Machine: Device: portable System: Dell product: Inspiron 7547 serial: N/A
Mobo: Dell model: 0AM670 v: A00 serial: N/A
UEFI: Dell v: A03 date: 10/27/2014
Battery BAT0: charge: 7.3 Wh 100.0% condition: 7.3/44.5 Wh (16%)
model: SIMPLO Dell status: Full
CPU: Dual core Intel Core i7-4510U (-HT-MCP-)
arch: Haswell rev.1 cache: 4096 KB
flags: (lm nx sse sse2 sse3 sse4_1 sse4_2 ssse3 vmx) bmips: 10379
clock speeds: max: 3100 MHz 1: 2302 MHz 2: 1999 MHz 3: 1999 MHz
4: 2076 MHz
Graphics: Card: Intel Haswell-ULT Integrated Graphics Controller
bus-ID: 00:02.0
Display Server: N/A drivers: intel (unloaded: modesetting)
tty size: 80x24
Audio: Card-1 Intel 8 Series HD Audio Controller
driver: snd_hda_intel bus-ID: 00:1b.0
Card-2 Intel Haswell-ULT HD Audio Controller
driver: snd_hda_intel bus-ID: 00:03.0
Sound: Advanced Linux Sound Architecture v: k4.9.50-1-MANJARO
Network: Card: Intel Wireless 3160 driver: iwlwifi bus-ID: 07:00.0
IF: wlp7s0 state: up mac: d0:7e:35:4b:ed:53
Drives: HDD Total Size: 1008.3GB (53.6% used)
ID-1: /dev/sda model: TOSHIBA_MQ02ABF1 size: 1000.2GB
ID-2: USB /dev/sdb model: innostor size: 8.1GB
Partition: ID-1: / size: 5.8G used: 100M (2%) fs: overlay dev: N/A
Sensors: System Temperatures: cpu: 53.0C mobo: 27.8C
Fan Speeds (in rpm): cpu: N/A
Info: Processes: 203 Uptime: 39 min Memory: 2186.0/7893.2MB
Init: systemd Gcc sys: 7.2.0
Client: Shell (bash 4.4.121) inxi: 2.3.38
getsetgo
 
Posts: 2
Joined: 2017-10-26 22:03

Re: GRUB boots into rescue mode, unknown filesystem

Postby GarryRicketson » 2017-10-26 23:58

How does this relate to Debian ? Are you trying to install Debian, or what?
Manjaro :
System: Host: manjaro Kernel: 4.9.50-1-MANJARO x86_64 bits: 64 gcc: 7.2.0
Desktop: N/A Distro: Manjaro Linux

Or Xubuntu:
installing Debian and Xubuntu instead

Yes you do mention you also tried to install Debian. I think to start with you need to
make up your mind, and concentrate on 1 OS, get it installed so you have something that
boots.
"What we expect you have already Done"

Before doing anything, read the Debian documentation:
Debian Documentation
How to ask the smart way
Debian Foro Español
======================
For the Birds
User avatar
GarryRicketson
 
Posts: 4371
Joined: 2015-01-20 22:16
Location: Durango, Mexico

Re: GRUB boots into rescue mode, unknown filesystem

Postby p.H » 2017-10-27 04:40

I suspect that the GRUB core image being loaded at boot is still the old one from the original system.

Please boot on the disk and provide the output of the follwing commands at the GRUB rescue prompt :
Code: Select all
set
ls


Boot with any Linux live system and provide the output of the following commands :
Code: Select all
fdisk -l # or parted -l
blkid
p.H
 
Posts: 161
Joined: 2017-09-17 07:12

Re: GRUB boots into rescue mode, unknown filesystem

Postby getsetgo » 2017-10-29 18:16

p.H wrote:I suspect that the GRUB core image being loaded at boot is still the old one from the original system.

Please boot on the disk and provide the output of the follwing commands at the GRUB rescue prompt :
Code: Select all
set
ls


Boot with any Linux live system and provide the output of the following commands :
Code: Select all
fdisk -l # or parted -l
blkid


grub rescue> set
cmdpath=(hd0)
prefix=(hd0,msdos1)/boot/grub
root=hd0,msdos1
grub rescue> ls
(hd0) (hd0,msdos4) (hd0,msdos3) (hd0,msdos2) (hd0,msdos1)

--

fdisk -l

Disk /dev/loop0: 58.7 MiB, 61579264 bytes, 120272 sectors
Units: sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 512 bytes / 512 bytes


Disk /dev/loop1: 239 MiB, 250634240 bytes, 489520 sectors
Units: sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 512 bytes / 512 bytes


Disk /dev/loop2: 874.1 MiB, 916529152 bytes, 1790096 sectors
Units: sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 512 bytes / 512 bytes


Disk /dev/loop3: 399.4 MiB, 418775040 bytes, 817920 sectors
Units: sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 512 bytes / 512 bytes


Disk /dev/sda: 931.5 GiB, 1000204886016 bytes, 1953525168 sectors
Units: sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 4096 bytes
I/O size (minimum/optimal): 4096 bytes / 4096 bytes
Disklabel type: dos
Disk identifier: 0xb2d79d4b

Device Boot Start End Sectors Size Id Type
/dev/sda1 * 2048 1050623 1048576 512M ef EFI (FAT-12/16/32)
/dev/sda2 1935065127 1953520064 18454938 8.8G 82 Linux swap / Solaris
/dev/sda3 62918656 1935065087 1872146432 892.7G 83 Linux
/dev/sda4 1050624 62918655 61868032 29.5G 83 Linux

Partition 2 does not start on physical sector boundary.
Partition table entries are not in disk order.


Disk /dev/sdb: 7.5 GiB, 8053063680 bytes, 15728640 sectors
Units: sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 512 bytes / 512 bytes
Disklabel type: dos
Disk identifier: 0x00000000

Device Boot Start End Sectors Size Id Type
/dev/sdb1 * 64 3332227 3332164 1.6G cd unknown
/dev/sdb2 3332228 3340419 8192 4M ef EFI (FAT-12/16/32)
getsetgo
 
Posts: 2
Joined: 2017-10-26 22:03

Re: GRUB boots into rescue mode, unknown filesystem

Postby p.H » 2017-10-29 18:56

The output of blkid is missing.
I guess that the root partition is sda4 and /home is sda3.
Try this at the grub rescue prompt :
Code: Select all
set prefix=(hd0,msdos4)/boot/grub
set root=hd0,msdos4
ls /
insmod normal
normal

The "ls" command is just to check that partition 4 can be read and contains the root filesystem with /bin, /boot...
p.H
 
Posts: 161
Joined: 2017-09-17 07:12

Re: GRUB boots into rescue mode, unknown filesystem

Postby varbo » 2017-10-30 13:00

I have quite similar broblem: In my Asus laptop is win7, I need that for my Garmin devices.
Everything worked fine with Debian Jessie. Now I installed Stretch and I cannot boot (there is not
grub screen anymore) in Debian. If I set bios to boot to debian there comes rescue prompt.

I tried to update:

root@sua:/home/hala# sudo update-grub
Searching for GRUB installation directory ... found: /boot/grub
Searching for default file ... found: /boot/grub/default
Testing for an existing GRUB menu.lst file ... found: /boot/grub/menu.lst
Searching for splash image ... none found, skipping ...
Found kernel: /boot/vmlinuz-4.9.0-4-amd64
Found kernel: /boot/vmlinuz-4.9.0-3-amd64
Updating /boot/grub/menu.lst ... done

root@sua:/home/hala# sudo grub-install /dev/sda
Searching for GRUB installation directory ... found: /boot/grub
The file /boot/grub/stage1 not read correctly.
root@sua:/home/hala#

Here is fdisk -l:

root@sua:/home/hala# sudo fdisk -l
Disk /dev/sda: 931,5 GiB, 1000204886016 bytes, 1953525168 sectors
Units: sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 4096 bytes
I/O size (minimum/optimal): 4096 bytes / 4096 bytes
Disklabel type: gpt
Disk identifier: 4F3B93A2-57E5-4A50-8778-F287C9A07B9C

Device Start End Sectors Size Type
/dev/sda1 2048 206847 204800 100M EFI System
/dev/sda2 206848 468991 262144 128M Microsoft reserved
/dev/sda3 468992 307202047 306733056 146,3G Microsoft basic data
/dev/sda4 307202048 307204095 2048 1M BIOS boot
/dev/sda5 307204096 1941176319 1633972224 779,1G Linux filesystem
/dev/sda6 1941176320 1953523711 12347392 5,9G Linux swap

and blkid:

root@sua:/home/hala# sudo blkid
/dev/sda1: UUID="7089-5415" TYPE="vfat" PARTLABEL="EFI system partition" PARTUUID="40a4fb2d-8d9c-4d51-8191-a0cf0e78eb7d"
/dev/sda2: PARTLABEL="Microsoft reserved partition" PARTUUID="ac3ba2e2-463b-4405-b93d-065aa6fd942e"
/dev/sda3: UUID="2060967260964F02" TYPE="ntfs" PARTLABEL="Basic data partition" PARTUUID="60e98bcd-67b9-45dc-8fc5-81687a2be82b"
/dev/sda4: PARTUUID="698d9a51-24e2-418e-b6d2-f1f35b81a4c7"
/dev/sda5: UUID="f0b9e04b-9c75-4c58-a18a-b97124da73c7" TYPE="ext4" PARTUUID="bfb6c8c2-c938-4164-b4d4-429b06449947"
/dev/sda6: UUID="4d40bffb-2428-49b4-bcad-576e39a741e8" TYPE="swap" PARTUUID="eb686a14-abcc-417a-a950-964397cd493f"

Can somebody help me?
varbo
 
Posts: 10
Joined: 2014-10-31 06:23

Re: GRUB boots into rescue mode, unknown filesystem

Postby p.H » 2017-10-30 13:44

varbo wrote:Testing for an existing GRUB menu.lst file ... found: /boot/grub/menu.lst

varbo wrote:The file /boot/grub/stage1 not read correctly.

These messages indicate that GRUB 1 aka legacy (package grub-legacy) is installed instead of GRUB 2 (package grub-pc for BIOS or grub-efi for UEFI).
The Debian installed does not install GRUB legacy by default but GRUB 2, so at some point you chose to replace GRUB 2 with GRUB legacy. Mind to explain why ?

The partition table is GPT and has an EFI system partition, so Windows is installed to boot in EFI mode.
Was Debian installed to boot in EFI mode too ? Check for directory names containing "efi" in /boot and /boot/grub.
varbo wrote:If I set bios to boot to debian

What do you mean ?
p.H
 
Posts: 161
Joined: 2017-09-17 07:12

Re: GRUB boots into rescue mode, unknown filesystem

Postby varbo » 2017-10-30 14:33

Check for directory names containing "efi" in /boot and /boot/grub.


hala@sua:/boot$ ls
config-4.9.0-3-amd64 initrd.img-4.9.0-3-amd64 vmlinuz-4.9.0-3-amd64
config-4.9.0-4-amd64 initrd.img-4.9.0-4-amd64 vmlinuz-4.9.0-4-amd64
efi System.map-4.9.0-3-amd64
grub System.map-4.9.0-4-amd64
hala@sua:/boot$ cd efi
hala@sua:/boot/efi$ ls
boot-repair EFI
hala@sua:/boot/efi$ cd EFI
hala@sua:/boot/efi/EFI$ ls
Boot debian Microsoft
hala@sua:/boot/efi/EFI$ cd Boot
hala@sua:/boot/efi/EFI/Boot$ ls
bootx64.efi
hala@sua:/boot/efi/EFI/Boot$ cd ..
hala@sua:/boot/efi/EFI$ cd debian
hala@sua:/boot/efi/EFI/debian$ ls
grubx64.efi
hala@sua:/boot/efi/EFI/debian$ cd ..
hala@sua:/boot/efi/EFI$ cd Microsoft
hala@sua:/boot/efi/EFI/Microsoft$ ls
Boot
hala@sua:/boot/efi/EFI/Microsoft$ cd Boot
hala@sua:/boot/efi/EFI/Microsoft/Boot$ ls
BCD bootmgfw.efi da-DK es-ES hu-HU memtest.efi pt-BR tr-TR
BCD.LOG bootmgr.efi de-DE fi-FI it-IT nb-NO pt-PT zh-CN
BCD.LOG1 BOOTSTAT.DAT el-GR Fonts ja-JP nl-NL ru-RU zh-HK
BCD.LOG2 cs-CZ en-US fr-FR ko-KR pl-PL sv-SE zh-TW
hala@sua:/boot/efi/EFI/Microsoft/Boot$ cd ..
hala@sua:/boot/efi/EFI/Microsoft$ cd ..
hala@sua:/boot/efi/EFI$ cd ..
hala@sua:/boot/efi$ cd ..
hala@sua:/boot$ cd grub
hala@sua:/boot/grub$ ls
default fonts jfs_stage1_5 minix_stage1_5 unicode.pf2
device.map grub.cfg locale reiserfs_stage1_5 xfs_stage1_5
e2fs_stage1_5 grubenv menu.lst stage1
fat_stage1_5 i386-pc menu.lst~ stage2
hala@sua:/boot/grub$
p.H wrote:[
varbo wrote:If I set bios to boot to debian

What do you mean ?

Sorry my bad english. Bios has boot choices: [debian (PO: ST100L...]
[Windows boot manage...]
[UEFI: KingstonDataT..]

When I set system to boot first choise (debian) it starts to grub-rescue mode.
When I set system to boot second choice windows starts
Third choice is usb stick where is grub rescue program
varbo
 
Posts: 10
Joined: 2014-10-31 06:23

Re: GRUB boots into rescue mode, unknown filesystem

Postby p.H » 2017-10-30 14:58

I see. This is really weird. /boot/efi exists and the EFI system partition is mounted on it, as expected after an installation in EFI mode. The EFI partition contains a GRUB EFI 64-bit core image installed by Debian (from this or a previous installation). However there is no trace of the installation of GRUB EFI in /boot/grub, there should be an x86_64-efi directory containing all the files needed by the core image. There are only the files installed by GRUB 1 (grub-legacy) and the directory i386-pc installed by GRUB 2 BIOS (grub-pc).

So when you select "debian" in the boot menu, this loads the GRUB core image from the EFI partition, but it cannot find the required files in /boot/grub and spawns the rescue prompt.
Installing grub-efi-amd64 should fix things.
p.H
 
Posts: 161
Joined: 2017-09-17 07:12

Re: GRUB boots into rescue mode, unknown filesystem

Postby varbo » 2017-10-30 15:11

p.H wrote:Installing grub-efi-amd64 should fix things.


Thank you very much. Now everything is working fine.
varbo
 
Posts: 10
Joined: 2014-10-31 06:23


Return to General Questions

Who is online

Users browsing this forum: No registered users and 6 guests

fashionable