Boot partition corrupted


#1

I installed Manjaro on /dev/sdc (I think sdc1 is a special boot partition and dev/sdc2 is everything else) and I set my bios to boot up with that disk. I’ve been running Manjaro this way for many months, perhaps over a year.

I also have Fedora installed on dev/sda (this install predates the Manjaro install). When I want to run it I just set my bios to boot into dev/sda. I use fedora as a backup if Manjaro gets borked.

So Manjaro has its native grub and fedora has its native grub. Both grubs ‘pickup’ the other installed OS but I never used that option when booting from the grub menu.

I’m writing this from my Fedora install because (I think) dev/sdc1 is corrupted. If I set my bios to boot Manjaro no grub shows up. just a black screen with a _ in the upper left area of my screen.

Here is what happened just before this problem. I was watching a movie on smplayer and the movie froze. Smplayer was frozen so a killed it. I reran smplayer and fastforwarded to the same spot it froze and it froze again.

So I had xfce reboot. That’s when I got the black screen. I tried cold booting and warm booting but grub wouldn’t come up. So I set my bios to boot sda and Fedora boots up AND I was able to mount /dev/sdc2 and finish the movie.

I ran Gnome Disks (I’m using Xfce btw) and here is what it says about sdc1:

Can I fix sdc1? Sdc2 seems ok although I haven’t fsck’d yet.


#2

Do this for both partitions.


#3

sdc1:
fsck /dev/sdc1
fsck from util-linux 2.32.1
e2fsck 1.44.3 (10-July-2018)
Error reading block 243826687 (Invalid argument). Ignore error? yes
Force rewrite? no
Superblock has an invalid journal (inode 8).
Clear? no
fsck.ext4: The journal superblock is corrupt while checking journal for home
e2fsck: Cannot proceed with file system check

home: ********** WARNING: Filesystem still has errors **********

sdc2: (from the cli it doesn’t seem to scan the disk but from gnome-disk it does seem to scan the disk and it also says that sdc2 is ok)
fsck /dev/sdc2
fsck from util-linux 2.32.1
e2fsck 1.44.3 (10-July-2018)
/dev/sdc2: clean, 1730194/122068992 files, 35378285/488247296 blocks


#4

Please repair your posted terminal output as “code”. Doesn’t it look ugly?

Unmount any partitions on sdc and run fsck as root (with sudo)

sudo fsck -r /dev/sdc

If it asks to repair (I guess) you should say “Yes” :wink:


#5

fsck -r /dev/sdc2
fsck from util-linux 2.32.1
e2fsck 1.44.3 (10-July-2018)
/dev/sdc2: clean, 1730202/122068992 files, 353867114/488247296 blocks
/dev/sdc2: status 0, rss 4252, real 0.382584, user 0.351140, sys 0.001981
[root@localhost michael]# fsck -r /dev/sdc1
fsck from util-linux 2.32.1
e2fsck 1.44.3 (10-July-2018)
Error reading block 243826687 (Invalid argument). Ignore error? yes
Force rewrite? yes
Superblock has an invalid journal (inode 8).
Clear? yes
*** journal has been deleted ***

The filesystem size (according to the superblock) is 488378368 blocks
The physical size of the device is 131072 blocks
Either the superblock or the partition table is likely to be corrupt!
Abort? yes
Error writing block 243826687 (Invalid argument). Ignore error? yes

home: ***** FILE SYSTEM WAS MODIFIED *****
/dev/sdc1: status 9, rss 4436, real 15.442361, user 0.368542, sys 0.003194

Well sdc2 is all good (which is nice since it’s my Manjaro install). However sdc1 is borked. I vaguely recall Manjaro creating both partitions on installation. sdc1 isn’t very big, 537mb and I think it had to do with uefi bios stuff. Is there a way to recreate it (since the actual install on sdc2 is fine)?


#6

Print output from terminal

sudo parted -l
sudo blkid
findmnt -s
efibootmgr

#7

parted -l
Model: ATA WDC WD10EZEX-00W (scsi)
Disk /dev/sda: 1000GB
Sector size (logical/physical): 512B/4096B
Partition Table: gpt
Disk Flags:

Number Start End Size File system Name Flags
1 1049kB 211MB 210MB fat16 EFI System Partition boot, esp
2 211MB 1285MB 1074MB ext4
3 1285MB 1000GB 999GB lvm

Model: ATA WDC WD20EZRZ-00Z (scsi)
Disk /dev/sdb: 2000GB
Sector size (logical/physical): 512B/4096B
Partition Table: msdos
Disk Flags:

Number Start End Size Type File system Flags
1 1049kB 2000GB 2000GB primary ext4

Model: ATA WDC WD20EZRZ-00Z (scsi)
Disk /dev/sdc: 2000GB
Sector size (logical/physical): 512B/4096B
Partition Table: msdos
Disk Flags:

Number Start End Size Type File system Flags
1 1049kB 538MB 537MB primary ext4 boot
2 538MB 2000GB 2000GB primary ext4

Model: Mass Storage Device (scsi)
Disk /dev/sdd: 16.0GB
Sector size (logical/physical): 512B/512B
Partition Table: msdos
Disk Flags:

Number Start End Size Type File system Flags
1 32.8kB 556MB 555MB primary boot
2 556MB 560MB 4194kB primary esp

blkid
/dev/sda1: SEC_TYPE=“msdos” UUID=“3009-E4A5” TYPE=“vfat” PARTLABEL=“EFI System Partition” PARTUUID=“1425cdf9-a990-42f8-8c9d-085e114f1dbc”
/dev/sda2: UUID=“3ef7ab67-2832-4238-87c1-116622778e54” TYPE=“ext4” PARTUUID=“c910bb40-75eb-4d84-bf9f-7dc87acd29ae”
/dev/sda3: UUID=“Ffi7HB-clxd-KD9b-MGu2-dRPU-ZJBd-gSIT79” TYPE=“LVM2_member” PARTUUID=“f4db5230-b805-42aa-87b8-c25c0fc84032”
/dev/sdb1: UUID=“7f9e068c-64fe-4113-8356-82b223b34af5” TYPE=“ext4” PARTUUID=“fc72b1e8-01”
/dev/sdc1: LABEL=“home” UUID=“afe4e565-12c5-40f0-8b00-ba361eff3755” TYPE=“ext4” PARTUUID=“09353a85-01”
/dev/sdc2: UUID=“901a5188-e255-4f97-abab-6f78911d1bb9” TYPE=“ext4” PARTUUID=“09353a85-02”
/dev/mapper/fedora_localhost–live-root: UUID=“f25fb27e-c34c-4672-bc0d-51dfcab6d42e” TYPE=“ext4”
/dev/mapper/fedora_localhost–live-swap: UUID=“88beb3fb-33ab-460c-bb0a-3c41891074fb” TYPE=“swap”
/dev/sdd1: UUID=“2018-10-09-08-32-57-00” LABEL=“MJRO1711” TYPE=“iso9660”
/dev/sdd2: SEC_TYPE=“msdos” LABEL=“MISO_EFI” UUID=“67CA-F308” TYPE=“vfat”
/dev/mapper/fedora_localhost–live-home: UUID=“10f0078e-fd99-470b-84c2-404bbb54f096” TYPE=“ext4”

findmnt -s
TARGET SOURCE FSTYPE OPTIONS
/ /dev/mapper/fedora_localhost–live-root ext4 defaults
/boot UUID=3ef7ab67-2832-4238-87c1-116622778e54 ext4 defaults
/boot/efi UUID=3009-E4A5 vfat umask=0077,shortname=winnt
/home/michael/Videos UUID=7f9e068c-64fe-4113-8356-82b223b34af5 ext4 defaults,x-gvfs-hide
/mnt/fedora UUID=901a5188-e255-4f97-abab-6f78911d1bb9 ext4 defaults,x-gvfs-hide
/home /dev/mapper/fedora_localhost–live-home ext4 defaults
swap /dev/mapper/fedora_localhost–live-swap swap defaults
/home/michael/Music /mnt/fedora/home/michael/Music none bind,x-gvfs-hide
/home/michael/Downloads /mnt/fedora/home/michael/Downloads none bind,x-gvfs-hide
/home/michael/Documents /mnt/fedora/home/michael/Documents none bind,x-gvfs-hide
/home/michael/Pictures /mnt/fedora/home/michael/Pictures none bind,x-gvfs-hide
/home/michael/Android /mnt/fedora/home/michael/Android none bind,x-gvfs-hide
/home/michael/AndroidStudio /mnt/fedora/home/michael/AndroidStudio none bind,x-gvfs-hide
/home/michael/bin /mnt/fedora/home/michael/bin none bind,x-gvfs-hide
/home/michael/Games /mnt/fedora/home/michael/Games none bind,x-gvfs-hide
/home/michael/Images-OS /mnt/fedora/home/michael/Images-OS none bind,x-gvfs-hide
/home/michael/Programming /mnt/fedora/home/michael/Programming none bind,x-gvfs-hide
/home/michael/tmp /mnt/fedora/home/michael/tmp none bind,x-gvfs-hide
/home/michael/VirtualBox VMs /mnt/fedora/home/michael/VirtualBox VMs none bind,x-gvfs-hide

efibootmgr
BootCurrent: 0001
Timeout: 1 seconds
BootOrder: 0001,0003,0007,0008,0004
Boot0001* Fedora
Boot0003* Hard Drive
Boot0004* CD/DVD Drive
Boot0006 WDC WD10EZEX-00WN4A0
Boot0007* UEFI OS
Boot0008* UEFI: Mass Storage Device

Hope that’s helpful. On findmnt -s you’ll see some out mounts to /mnt/fedora. That’s sdc2, my manjaro install. And I use it to mount my data directories from sdc2 home to my fedora install so can get to them . I’v go to sleep now so I’ll catch you tomorrow (in Thailand at least). I’m wondering if sdc1 is supposed to be like sda1?


#8

Your manjaro is on sdc which is msdos.
You don’'t have a efibootmgr entry for manjaro which is not surprising.

It won’t work that way.


#9

You have mixed MSDOS and UEFI installations. It needs experience and technical awareness to do this.

This is important to know, what partitions and how are they mounted in /etc/fstab of Manjaro installation.
Find Manjaro root partition and get/post /etc/fstab.

You have used Fedora boot to provide info.
For now, it is preferred to use a Manjaro Live ISO booted, to get info.

I don’t know if running fsck on this situation has any risks or is safe…
And, for the record, you did not follow the suggested command for fsck (on partition instead of drive). I don’t know if this has any difference, but it shows that either you know what you are doing, or you are not as careful as you should be, while messing with your data… :worried:


#10

Manjaro fstab:

# /dev/sdc2
UUID=901a5188-e255-4f97-abab-6f78911d1bb9 / ext4 rw,noatime,data=ordered 0 0

# /dev/sdb1
UUID=7f9e068c-64fe-4113-8356-82b223b34af5 /home/michael/Videos ext4 defaults,x-gvfs-hide 0 2
/swapfile none swap defaults,pri=-2 0 0

I did run sudo fsck -r /dev/sdc but I forgot to post it so here it is.

fsck -r /dev/sdc
fsck from util-linux 2.32.1
e2fsck 1.44.3 (10-July-2018)
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/sdc

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 dos partition table in /dev/sdc

Also I know that sdc1 is reported as msdos but I’m not sure that’s correct. sdc1 and sdc2 were created by Manjaro architect when I first installed it.

I’m dl’ing xfce manjaro iso. Tonight I’ll install to my sdcard and do everything from there.


#11

Okay, used a live cd. I think sdc1 was an EFI partition. I tried to restore it as such using a manjaro wiki guide. But t didn’t work. So I just did the bios method were you install grub to the drive /dev/sdc and that worked.

After I did that i found that that Manjaro had a more extensive uefi guide that would’ve been better to follow. But the bios install works fine (for now anyway).


#12

It’s ext4 and labeled as Home. Not an $esp.
M-A does what you choose. It was an MsDos install, with root only and swap-file.
There is no entry for home(sdc1) in fstab, unless you manually removed it.

Take care!


#13

See this post and the links in it.

You’re lucky you’ve

This is not feasible.


#14

So I’ve got a legacy install? Thanks for the link.


#15

Ok, thank you for your help.