I have deleted accidentally all disks partitions in the laptop, and now I cannot start ubuntu neither start installation from usb. After turning on laptop I get
error: no such partition.
Entering rescue mode...
grub rescue>
typing ls I get
(hd0)(hd1)
I don't need to recover any data I would like to install new OS
I updated the system from 18.04 to 20.04 via the terminal. When the computer restarts, the black screen appears with the above written mention.
What should I do to fix the problem (without obviously losing the files and programs on the disk)?
Thanks for your help
I upgraded Ubuntu from 19.04 to 19.10. The upgrade went without errors but after restart grub throws an error on startup and goes into rescu mode
error: symbol 'grub_file_filters' not found.
Entering rescue mode...
grub rescue>
It's a physical machine not a virtualbox, and I have windows and linux in dual boot.
I managed to find what partition is my linux on with ls, but don't really know what to do next.
insmod normal fails with the same error
So I'm running Ubuntu 18.04 on a btrfs root. I recently rebooted because I got a notification about "restart required" after an update. The last few times I restarted this server, I had an issue where the kernel wouldn't load and I ended up in grub, and loaded the last kernel manually. This time (I had definitely run update-grub since last time) I'm in grub rescue and the usual commands don't work, so I looked at a tutorial, but when I get to insmod normal, I get the error "Compression type 0x3 not supported", and then normal yields command not found. I'm writing this post because apparently nobody has ever seen this error* and I can't figure out what it means or how to fix it. My system works fine with kernel 4.15.0-23 but not at all with 4.15.0-24, which somehow got reinstalled after I removed it.
*A web search for the error message in quotes comes up empty
I know there are a few questions in this already (error: file '/grub/i386-pc/normal.mod' not found, error: file '/boot/grub/i386-pc/normal.mod' not found, https://askubuntu.com/questions/519463/boot-grub-i386-pc-normal-mod-not-found-in-grub-rescue) but non of those solves my problem.
I upgraded a DELL PowerEdge 830 from 12.04 LTS to 14.04LTS and found myself staring at the "grub rescue" prompt. (Funny thing is that non of the commands that should work, like 'boot', are recognized by the grub trying to talk to me...)
I used the BootRepair, which was a nice utility. Unfortunately it didn't help. Still "grub rescue".
Here's the link to its log if someone would be kind enough to have a look at it.
I also tried this and this, which are mostly the same. So obviously there is something differently wrong with my setup.
At the grub rescue prompt I did "ls" to ensure I had the partitions I wanted. I can see the 3 expected partions on the first drive, /dev/sda1 being marked as boot and ext3. Here's a session with grub rescue:
grub rescue> ls
(hd0) (hd0,msdos5) (hd0,msdos1) (hd1) (hd1, msdos)
grub rescue> ls (hd0)
(hd0): Filesystem is unknown.
grub rescue> ls (hd0,1)
(hd0,1): Filesystem is fat
grub rescue> ls (hd0,5)
(hd0,5): Filesystem is fat.
grub rescue> set
cmdpath=(hd0)
prefix=(hd0,msdos1)/boot/grub
root=hd0,msdos1
grub rescue> normal
unknown command ‘normal’
grub rescue> insmod normal
error: file ‘/boot/grub/i386-pc/normal.mod’ not found
grub rescue> ls (hd0,1)/boot
error: file '/boot' not found.
Seems like grub thinks hd0,msdos1 is a FAT partition, right? fdisk (from a LiveCD) says its an ext3. That's causing "normal.mod not found", I suppose, since the kernel on a Linux system does not have FAT-support, which it shouldn't need...
This is our "production" server so I'd appreciate any quick replies so I can get it back running before Monday, thanks.
UPDATE: I did find a number of file system markings using wipefs (no, it doesn't wipe the filesystem...), but removing all but one (ext3) still did not fix my issue.
Biting the bullet, and many nightly hours later I had a fresh install and most of the data restored piece by piece from backup.
So, no solution.