Error running 'grub-mkconfig -o /boot/grub/grub.cfg'

taranteeno · 2016-09-19 18:29:53

Hi everyone. I'm new to arch Linux and I need your help to get this problem solved.
I actually installed arch the first time following a tutorial. After one week I decided to install it on my own, mainly beacause grub wasn't finding Windows 10.
This is the situation:

1 - HDD with Windows 10 installed (1 TB)
2 - HDD with arch installed (74.5 GB)

Since Windows 10 boots in UEFI mode, I decided to install arch with a UEFI bootloader (in this case grub).
The HDD with Arch is organized like that;

/dev/sda (70 GB)
--> /dev/sda1 (40 GB, /home)
--> /dev/sda2 (34.5 GB, /)

I created a GPT partition table, since I need to boot in UEFI mode.
After installing the base pack of arch with 'pacstrap /mnt base' (with the Windows EFI partition mounted to /boot), I ran 'mkinitpcio -p linux' and started configure grub.

Running 'grub-mkconfig -o /boot/grub/grub.cfg', the shell shows me this message:

Generating grub configuration file ...
Found linux image: /boot/vmlinuz-linux
Found initrd image(s) in /boot : initramfs-linux.img
Found fallback initrd image(s) in /boot: initramfs-linux-fallback.img
  WARNING: Failed to connect to lvmetad. Falling back to device scanning.
[   170.522182] squashfs: SQUASHFS error: can't find a SQUASHFS superblock on sdb3
[   170.522977] EXT4-fs (sdb3): VFS: Can't find ext4 filesystem
[   170.523773] EXT4-fs (sdb3): VFS: Can't find ext4 filesystem
[   170.524548] EXT4-fs (sdb3): VFS: Can't find ext4 filesystem
[   170.525414] FAT-fs (sdb3): bogus number of reserved sectors
[   170.526230] ntfs: (device sdb3): read_ntfs_boot_sector(): Primary boot sector is invalid.
[   170.526237] ntfs: (device sdb3): read_ntfs_boot_sector(): Mount option errors=recover not used. Aborting without trying to recover.
[   170.526251] ntfs: (device sdb3): read_fill_super(): Not an NTFS volume.
done

Also 'os-prober' shows the same message. It seems that there's something wrong with /dev/sdb3 partition and I really don't know why.
What's lvmetad? Is it involved with LVM? If yes, why?

Thanks in advance.
Excuse me for my very bad english (i'm trying to do my best).

Regards,
Roberto.

newbie1962 · 2016-09-19 19:29:11

sdb3 make a disk check, fsck and posting errors.

taranteeno · 2016-09-19 20:13:23

fsck:

fsck from util-linux 2.28.2
e2fsck 1.43.3 (04-Sep-2016)
/dev/sda2 is mounted.
e2fsck: Cannot continue, aborting.

fsck /dev/sdb3:

fsck from util-linux 2.28.2
fsck.ext2: Bad magic number in super-block while trying to open /dev/sdb3
/dev/sdb3:
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 of ufs or something else), then the superblock is corrupt, and you might try running e2fsck with an alternate superblock:
    e2fsck -b 8193 <device>
or
    e2fsck -b 32768 <device>

fsck seems to be searching for a linux filesystem, but I don't know how much this could be useful since we are analyizing Windows partitions.
Anyway /dev/sdb3 is the only partition that shows a error message with fsck /dev/sdb(n)

fdisk -l:

Disk /dev/sdb: 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: BB500393-712B-40F0-899F-9352A99E31C3

Device       Start        End    Sectors  Size Type
/dev/sdb1     2048     923647     921600  450M Windows recovery environment
/dev/sdb2   923648    1128447     204800  100M EFI System
/dev/sdb3  1128448    1161215      32768   16M Microsoft reserved
/dev/sdb4  1161216 1953523711 1952362496  931G Microsoft basic data


Disk /dev/sda: 74.5 GiB, 80026361856 bytes, 156301488 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: gpt
Disk identifier: 799D0C94-1548-4CE9-B911-FE347CE1161B

Device        Start       End  Sectors  Size Type
/dev/sda1      2048  83888127 83886080   40G Linux filesystem
/dev/sda2  83888128 156301454 72413327 34.5G Linux filesystem




Disk /dev/sdc: 14.4 GiB, 15502147584 bytes, 30277632 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: 0x2338a73e

Device     Boot Start     End Sectors  Size Id Type
/dev/sdc1  *        0 1482751 1482752  724M  0 Empty
/dev/sdc2         172   82091   81920   40M ef EFI (FAT-12/16/32)


Disk /dev/sde: 29.3 GiB, 31439454208 bytes, 61405184 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/sde1  *     2048 61405183 61403136 29.3G  c W95 FAT32 (LBA)

newbie1962 · 2016-09-20 08:24:21

take control from windows on the partition that has problems, I would like to understand your partitioning, arch is installed on H.D. external?
If arch is external disk advice use system-boot look in the wiki solution.
edit
for te use system-boot,do you remove grub

Last edited by newbie1962 (2016-09-20 08:28:48)

arch23 · 2016-09-20 11:32:53

Hi there
I'm new to Arch linux too and had the same problem with grub, I couldn't make it work no matter what
So I posted in the forums and was advised to not use grub at all
Just use rEFInd and boot Arch as a EFISTUB, and it worked really well for me.

Head_on_a_Stick · 2016-09-20 18:28:09

taranteeno wrote:

After installing the base pack of arch with 'pacstrap /mnt base' (with the Windows EFI partition mounted to /boot)

You have mounted /boot in the live system to the EFI system partition.

You should have used:

# mount /dev/sda2 /mnt
# mkdir /mnt/{boot,home}
# mount /dev/sda1 /mnt/home
# mount /dev/sdb2 /mnt/boot
# pacstrap /mnt base

Arch Linux

#1 2016-09-19 18:29:53

Error running 'grub-mkconfig -o /boot/grub/grub.cfg'

#2 2016-09-19 19:29:11

Re: Error running 'grub-mkconfig -o /boot/grub/grub.cfg'

#3 2016-09-19 20:13:23

Re: Error running 'grub-mkconfig -o /boot/grub/grub.cfg'

#4 2016-09-20 08:24:21

Re: Error running 'grub-mkconfig -o /boot/grub/grub.cfg'

#5 2016-09-20 11:32:53

Re: Error running 'grub-mkconfig -o /boot/grub/grub.cfg'

#6 2016-09-20 18:28:09

Re: Error running 'grub-mkconfig -o /boot/grub/grub.cfg'

Board footer