Hello All, I used Rescuezilla to backup a system image of my tower "Linux1" 2 days ago. After finishing, I rebooted the tower and it was unable. Msg was:
"error : file '/boot/grub/i386-pc/extendcmd.mod' not found.
"Entering Rescue Mode......"
Rescue mode >
I went back to rescuezilla and installed back the system image. Same result upon rebooting. Tried fsck but no access allowed to device on /dev/sda
(running ASUS tower 64 bit.) Zorin 17.3
You could try booting from a Zorin-Live-USB-Boot Stick (choose "Try Zorin" here) and then search in the startmenu for "boot repair" and run it.
You can also check if the boot order in your BIOS is set correctly with ubuntu at the first place.
You can run from Live USB gparted or disks and look wheather the partitions are mounted correctly and have the right mount points boot and root.
Do you have any prior images that you can attempt to reboot into?
However, in this case, I'd recommend reaching out to the Rescuezilla developer directly about this issue. If it's causing drives to fail or messing with files that it shouldn't, when it's supposed to be making copies only, this should be raised to their attention.
I have already done from the live Zorin USB and run boot repair - to no avail. I get confused with the partitions status, my weak point.
It may not be Rescuezilla's fault. I ran this tower direct HDMI into a 50 inch TV display, and the desktop overflows the sides, normal problem. I could not see where to exit Resuczilla with my mouse, so when the backup was complete, I powered down the tower totally with the button?
You can run gparted in a USB Live Session of Zorin and post a screenshot of your partitions here if you still need help.
You shouldn't have to do that. On the interface that appears when you are backing up there is a choice of Do nothing or shut down on completion. Have you checked the S.M.A.R.T. status of your backup drive recently?
root@ubuntu:~# sudo nano /etc/default/grub
sudo: nano: command not found
root@ubuntu:~# sudo /etc/default/grub
sudo: /etc/default/grub: command not found
root@ubuntu:~# sudo fsck -f /dev/sda
fsck from util-linux 2.39.3
e2fsck 1.47.0 (5-Feb-2023)
ext2fs_open2: Bad magic number in super-block
fsck.ext2: Superblock invalid, trying backup blocks...
fsck.ext2: Bad magic number in super-block while trying to open /dev/sda
The superblock could not be read or does not describe a valid ext2/ext3/ext4
filesystem. If the device is valid and it really contains an ext2/ext3/ext4
filesystem (and not swap or ufs or something else), then the superblock
is corrupt, and you might try running e2fsck with an alternate superblock:
e2fsck -b 8193
or
e2fsck -b 32768
Found a gpt partition table in /dev/sda
root@ubuntu:~# sudo e2fsck -b 8193 /dev/sda
e2fsck 1.47.0 (5-Feb-2023)
e2fsck: Bad magic number in super-block while trying to open /dev/sda
The superblock could not be read or does not describe a valid ext2/ext3/ext4
filesystem. If the device is valid and it really contains an ext2/ext3/ext4
filesystem (and not swap or ufs or something else), then the superblock
is corrupt, and you might try running e2fsck with an alternate superblock:
e2fsck -b 8193
or
e2fsck -b 32768
Found a gpt partition table in /dev/sda
root@ubuntu:~# e2fsck -b 8193 /dev/sda
e2fsck 1.47.0 (5-Feb-2023)
e2fsck: Bad magic number in super-block while trying to open /dev/sda
The superblock could not be read or does not describe a valid ext2/ext3/ext4
filesystem. If the device is valid and it really contains an ext2/ext3/ext4
filesystem (and not swap or ufs or something else), then the superblock
is corrupt, and you might try running e2fsck with an alternate superblock:
e2fsck -b 8193
or
e2fsck -b 32768
Found a gpt partition table in /dev/sda
root@ubuntu:~#
I will check in BIOS
In gparted you can also see the mount points. Look in gparted if sda2 has a boot flag (/boot) and sda3 a root flag (/).
If you need to use e2fsck it is best done using Kali Linux in live (try) mode.
SMART status in BIOS is OK.
sda2 has a flag = boot, esp
sda3 has no flag.
I did run up the install (Try Zorin) USB drive to try boot repair. It wants me to disable BIOS compatability mode for UEFI BIOS. However, I do not see this feature in the BIOS (ASUS 2012 old tower).
I started "try Zorin" from the USB install drive and went to 'Boot repair'. I did the second option and was given the following URL to write down - summary of current boot status - https://paste.ubuntu.com/P/Xby94yXWKs/
I tried to access the URL and got told it does not exist?
I see that after my install of zorin17 alongside the existing 17.3, that the boot is the culprit. I will research Kali Live.
When you boot from Zorin Live USB Stick can you run gparted, right click on sda3 and choose "manage flags" to set / (root) here? But I am not sure if it will remain after reboot without the stick...
Have you recently changed your BIOS settings or performed a CMOS reset (e.g. by replacing the cmos battery) or loaded the default settings after Zorin was installed, so that your computer was switched from legacy or CSM to uefi or vice versa? This would also prevent booting.
I'll give that a go tomorrow. Is that the whole syntax "/ (root)" or is it just the forward slash?
No, not on that tower.
Please forget my suggestion. It does not work. I am sorry. I could only try it now on my PC. There is no possibility to set a root flag in the live session in gparted.
Thank you for your good intentions anyway.
