[SOLVED] Almost succesfully EFI install. Error: unable det.... root..

Alber · 2012-07-12 19:22:41

Hello

I almost did a EFI install of Arch.
I've followed the wiki. But as you boot with bios, efibootmgr didn't work. So, as solution, and it's not in the wiki I put the grubx64.efi as bootx64.efi in /boot/efi/EFI/BOOT/. This is where EFI search the file bootx64.efi to launch, if a bootloader wasn't fixed before.

It works. I achieve at grub's menu, and launch Arch. But from there I get the next:

ERROR: unable to determine major/minor number of root device "UUID=......."
::::::
::::::
ERROR: UUID=..... no such file o directory
ERROR unable to determine the file system type of

I've tryed do a mkinitcipio without autodetect HOOK. But the same.

I think it is GRUB2, but for me, five days with EFI (at least), three install tryes, too much for me. I can't do more search.

(it's a usb and use HOOK usb too)
Thankyou by your time.

Last edited by Alber (2012-07-17 11:59:32)

89c51 · 2012-07-13 09:06:46

could you post your fstab and your grub configuration?

DSpider · 2012-07-13 09:13:30

Does the "Fallback" entry work?

And have you tried googling "ERROR: unable to determine major/minor" ? Because it returns several Arch topics that were marked as solved.

Alber · 2012-07-13 10:55:46

Hello.

I read several post. The solution was either delete the "autodetect" HOOK, or Grub2 config. But I tried to understand this file, and it looks like fine to me. But I have no experience in that so it could be wrong.

Fallback entry no works.

My fstab:

# <file system>                                       <dir>	<type>	<options>	<dump>	<pass>
tmpfs                                                  /tmp	tmpfs	  nodev,nosuid	0	0
UUID=dc65138c-aa2c-45aa-ba83-71be6b9a51d6              /          ext4    defaults 0 1
UUID=087141f8-e460-448f-91fe-45ad290454c9              /var       ext4    defaults 0 2
UUID=7D8C-C20F                                         /boot/efi  vfat    defaults 0 2
UUID=7e6bdfb0-9bc2-426b-99cf-3942510c3273              /home      ext4    defaults 0 2
UUID=8350f0a8-3374-4c18-86b8-0b23b69b8654              /boot      ext4    defaults 0 2

gdisk output:

GPT fdisk (gdisk) version 0.8.5

Partition table scan:
  MBR: protective
  BSD: not present
  APM: not present
  GPT: present

Found valid GPT with protective MBR; using GPT.

Command (? for help): Disk /dev/sdb: 31275008 sectors, 14.9 GiB
Logical sector size: 512 bytes
Disk identifier (GUID): 72D56917-9541-4E03-B6E6-CFFCC5449557
Partition table holds up to 128 entries
First usable sector is 34, last usable sector is 31274974
Partitions will be aligned on 2048-sector boundaries
Total free space is 169917 sectors (83.0 MiB)

Number  Start (sector)    End (sector)  Size       Code  Name
   1            2048          616447   300.0 MiB   EF00  Dummy_efi
   2          616448         1026047   200.0 MiB   8300  Dummy_boot
   3         1026048        17803263   8.0 GiB     8300  Dummy_root
   4        17803264        26191871   4.0 GiB     8300  Dummy_var
   5        26191872        31107071   2.3 GiB     8300  Dummy_home

/boot/grub/grub.cfg

### BEGIN /etc/grub.d/00_header ###
insmod part_gpt
insmod part_msdos
if [ -s $prefix/grubenv ]; then
  load_env
fi
set default="0"

if [ x"${feature_menuentry_id}" = xy ]; then
  menuentry_id_option="--id"
else
  menuentry_id_option=""
fi

export menuentry_id_option

if [ "${prev_saved_entry}" ]; then
  set saved_entry="${prev_saved_entry}"
  save_env saved_entry
  set prev_saved_entry=
  save_env prev_saved_entry
  set boot_once=true
fi

function savedefault {
  if [ -z "${boot_once}" ]; then
    saved_entry="${chosen}"
    save_env saved_entry
  fi
}

function load_video {
  if [ x$feature_all_video_module = xy ]; then
    insmod all_video
  else
    insmod efi_gop
    insmod efi_uga
    insmod ieee1275_fb
    insmod vbe
    insmod vga
    insmod video_bochs
    insmod video_cirrus
  fi
}

if [ x$feature_default_font_path = xy ] ; then
   font=unicode
else
insmod part_gpt
insmod ext2
set root='hd1,gpt3'
if [ x$feature_platform_search_hint = xy ]; then
  search --no-floppy --fs-uuid --set=root --hint-bios=hd1,gpt3 --hint-efi=hd1,gpt3 --hint-baremetal=ahci1,gpt3  dc65138c-aa2c-45aa-ba83-71be6b9a51d6
else
  search --no-floppy --fs-uuid --set=root dc65138c-aa2c-45aa-ba83-71be6b9a51d6
fi
    font="/usr/share/grub/unicode.pf2"
fi

if loadfont $font ; then
  set gfxmode=auto
  load_video
  insmod gfxterm
  set locale_dir=$prefix/locale
  set lang=en_US
  insmod gettext
fi
terminal_input console
terminal_output gfxterm
set timeout=5
### END /etc/grub.d/00_header ###

### BEGIN /etc/grub.d/10_linux ###
menuentry 'Arch Linux GNU/Linux, with Linux core repo kernel' --class arch --class gnu-linux --class gnu --class os $menuentry_id_option 'gnulinux-core repo kernel-true-dc65138c-aa2c-45aa-ba83-71be6b9a51d6' {
	load_video
	set gfxpayload=keep
	insmod gzio
	insmod part_gpt
	insmod ext2
	set root='hd1,gpt2'
	if [ x$feature_platform_search_hint = xy ]; then
	  search --no-floppy --fs-uuid --set=root --hint-bios=hd1,gpt2 --hint-efi=hd1,gpt2 --hint-baremetal=ahci1,gpt2  8350f0a8-3374-4c18-86b8-0b23b69b8654
	else
	  search --no-floppy --fs-uuid --set=root 8350f0a8-3374-4c18-86b8-0b23b69b8654
	fi
	echo	'Loading Linux core repo kernel ...'
	linux	/vmlinuz-linux root=UUID=dc65138c-aa2c-45aa-ba83-71be6b9a51d6 ro  quiet add_efi_memmap
	echo	'Loading initial ramdisk ...'
	initrd	/initramfs-linux.img
}
menuentry 'Arch Linux GNU/Linux, with Linux core repo kernel (Fallback initramfs)' --class arch --class gnu-linux --class gnu --class os $menuentry_id_option 'gnulinux-core repo kernel-fallback-dc65138c-aa2c-45aa-ba83-71be6b9a51d6' {
	load_video
	set gfxpayload=keep
	insmod gzio
	insmod part_gpt
	insmod ext2
	set root='hd1,gpt2'
	if [ x$feature_platform_search_hint = xy ]; then
	  search --no-floppy --fs-uuid --set=root --hint-bios=hd1,gpt2 --hint-efi=hd1,gpt2 --hint-baremetal=ahci1,gpt2  8350f0a8-3374-4c18-86b8-0b23b69b8654
	else
	  search --no-floppy --fs-uuid --set=root 8350f0a8-3374-4c18-86b8-0b23b69b8654
	fi
	echo	'Loading Linux core repo kernel ...'
	linux	/vmlinuz-linux root=UUID=dc65138c-aa2c-45aa-ba83-71be6b9a51d6 ro  quiet add_efi_memmap
	echo	'Loading initial ramdisk ...'
	initrd	/initramfs-linux-fallback.img
}

### END /etc/grub.d/10_linux ###

### BEGIN /etc/grub.d/20_linux_xen ###
### END /etc/grub.d/20_linux_xen ###

### BEGIN /etc/grub.d/20_memtest86+ ###
### END /etc/grub.d/20_memtest86+ ###

### BEGIN /etc/grub.d/30_os-prober ###
### END /etc/grub.d/30_os-prober ###

### BEGIN /etc/grub.d/40_custom ###
# This file provides an easy way to add custom menu entries.  Simply type the
# menu entries you want to add after this comment.  Be careful not to change
# the 'exec tail' line above.
### END /etc/grub.d/40_custom ###

### BEGIN /etc/grub.d/41_custom ###
if [ -f  ${config_directory}/custom.cfg ]; then
  source ${config_directory}/custom.cfg
elif [ -z "${config_directory}" -a -f  $prefix/custom.cfg ]; then
  source $prefix/custom.cfg;
fi
### END /etc/grub.d/41_custom ###

I'll go to try to change grub.conf:
It could be that firmware was getting another disk. So I'll change hd1 to hd2 or hd0.

I have to read grub2 wiki to asure where root must be pointing.

Added: Maybe ext2 must be ext4?.
NO, it wasn't

Last edited by Alber (2012-07-13 11:36:46)

89c51 · 2012-07-13 11:56:38

Not sure it will help but i see in some configurations that instead of /vmlinuz-linux they use /boot/vmlinuz-linux

Alber · 2012-07-13 12:18:09

When I changed to ext4 I could read the next messages

error: file '/grub/x86_64-efi/ext4.mod' not found
loading Linux core repo kernel.
loading initial ramdisk...

##Clear screen##

ERROR: unable to determine major/minor number of root device "UUID=......."
same that before

ext2.mod exits. But I can see the next.
loading Linux core repo kernel.
loading initial ramdisk...
before I can't see tha message because it run faster. Perhaps it help.

I'll look at /boot/vmlinuz-linux. Thank you.

Last edited by Alber (2012-07-13 12:19:09)

Alber · 2012-07-13 13:00:52

I've added rootfstype=ext4, but no luck.

89c51 · 2012-07-13 13:44:51

is ext4 in your mkinitcpio modules?

DSpider · 2012-07-13 13:51:50

ERROR: unable to determine major/minor number of root device "UUID=......."
same that before

Which UUID? Is it dc65138c-aa2c-45aa-ba83-71be6b9a51d6 ?

From a LiveCD post the output of:

$ blkid

And have you tried the linux-lts kernel yet? Chroot into your system from a LiveCD, install the linux-lts package and re-generate GRUB2's cfg. Don't try to edit the grub.cfg file. It's a mess to understand...

Alber · 2012-07-13 14:35:54

I've tested /boot/vmlinuz-linux and combinations but no improvement.

Befor I didn't see but theris a new message bit when added rootfstype=ext4 .

mounting UUID=dc65138c-aa2c-45aa-ba83-71be6b9a51d6 on /new_root failed. no such file or directory.

I'll test about ext4 in mkinitcpio.cfg modules.

Sorry I forgot write the UUID and it was important. It is / partition.

ERROR: unable to determine major/minor number of root device "UUID=dc65138c-aa2c-45aa-ba83-71be6b9a51d6"
::::::
::::::
mounting UUID=dc65138c-aa2c-45aa-ba83-71be6b9a51d6 on /new_rootfailed. no such file or directory

I must say that it is a SD on a memory reader where I'm trying intall Arch, (I have a working Arch in another SD but BIOS. Always problem with sda or sdb or sdc... in menu.lst; by all this I was changing hd0, hd1, hd2 in grub.cfg). blkid output from no same computer:

/dev/sdd1: UUID="7D8C-C20F" TYPE="vfat" 
/dev/sdd2: UUID="8350f0a8-3374-4c18-86b8-0b23b69b8654" TYPE="ext4" 
/dev/sdd3: UUID="dc65138c-aa2c-45aa-ba83-71be6b9a51d6" TYPE="ext4" 
/dev/sdd4: UUID="087141f8-e460-448f-91fe-45ad290454c9" TYPE="ext4" 
/dev/sdd5: UUID="7e6bdfb0-9bc2-426b-99cf-3942510c3273" TYPE="ext4"

I'll tri blkid in target computer but live-usb can change device too.

I'm going to try inux-lts.

Last edited by Alber (2012-07-13 14:40:35)

DSpider · 2012-07-13 14:53:27

You forgot to mention that you installed Arch on a USB stick (SD card, memory stick, whatever).

In that case, you will need the "usb" hook in /etc/mkinitcpio.conf:

https://wiki.archlinux.org/index.php/Mkinitcpio#HOOKS

Adds USB modules to the image. Use this if your root device is on a USB mass storage device or if your USB mass storage device needs to be accessed otherwise (checked, mounted, etc.) at boot time.

And don't forget to re-generate your initramfs (from a chroot) each time you modify /etc/mkinitcpio.conf:

# mkinitcpio -p [your kernel preset; e.g. linux]

Alber · 2012-07-13 15:41:00

About usb HOOK. I mentioned that in the first post. Almost the last line. But it is apreciated the recall on that issue.
I have another SD working with arch but using BIOS, and Grub, and with usb HOOK, I remember very well it was my first stumble with Arch.
By the way, Fedora 17 with EFI works.

No succes with linux-lts, too.

I think that will use GRUB-legacy. I give up by now. I'll try again in near future.
Thankyou by yours help. It's very apreciated.

Last edited by Alber (2012-07-13 15:47:45)

cfr · 2012-07-14 23:06:12

error: file '/grub/x86_64-efi/ext4.mod' not found

You have not installed grub2 to disk. See the wiki for instructions on modprobing efivars and using grub-install. You need to boot in EFI mode to install grub to disk. Otherwise it won't work. That's why the file isn't found under /boot/grub/...

I've followed the wiki. But as you boot with bios, efibootmgr didn't work. So, as solution, and it's not in the wiki I put the grubx64.efi as bootx64.efi in /boot/efi/EFI/BOOT/. This is where EFI search the file bootx64.efi to launch, if a bootloader wasn't fixed before.

The wiki explains how to work around this. You haven't followed that part of the wiki so it isn't going to work.

Get something which will boot in EFI mode e.g. a copy of Archboot, Ubuntu, whatever, set your computer to boot in EFI mode (if applicable), boot and then follow the instructions to chroot and install grub2.

You need to follow the wiki precisely and to carefully check that you are following those parts which apply to your setup.

Last edited by cfr (2012-07-14 23:06:33)

Alber · 2012-07-15 12:09:07

error: file '/grub/x86_64-efi/ext4.mod' not found

This error comes when I changed ext2 to ext4 in grub.cfg. But when come back to original, no error is showed.
I get grub menu first, and I can choose kernel. So I think it is ok.

About boot in EFI and all about. I think that the problem was there. But I'll explain because I did that:
The steps are to tell EFI that boot from the bootloader that is said. You can pass over all this, because, if EFI doesn't know nothing about what bootloder must launch, it launchs bootloader founded in /EFI/BOOT/bootx64.efi.
All this was readed out of archwiki. But I think it works beacuse I get GRUB2. No garantee.

Thank you by the way, I'll go try again, this time following all the wiki, with less partitions too. But no now, in a week or two.

Sorry, to all people, I can't explain my self better in English.

Last edited by Alber (2012-07-15 12:09:53)

mynis01 · 2012-07-15 17:32:14

I got errors like that when I had ahci enabled in the motherboard but not in the kernel image. Did you edit /etc/mkinitcpio.conf and rebuild the image?

Last edited by mynis01 (2012-07-15 17:32:28)

Alber · 2012-07-16 08:09:16

Just now, I've made a fast test disabling ahci in mother board, but no succes, same error. Maybe I made to much changes to my system so I would must start again from zero.
First, I'll rebuild the image with achi module and I'll do a new try.

Alber · 2012-07-16 11:19:15

I've made a new fresh installation with ahci module and it give the same error (only this error).

ERROR: unable to determine major/minor number of root device "UUID=dc65138c-aa2c-45aa-ba83-71be6b9a51d6"

Then, it only can be:
grub.cfg because I always have had problems. The BIO/EFI change the devices.
To follow the wiki in this part: "Create GRUB2 entry in the Firmware Boot Manager"
Or anything else.

Last edited by Alber (2012-07-16 11:20:09)

Alber · 2012-07-17 11:38:21

WORKING, WORKING, WORKING.

It was grub2 configuration.
With this, (as ancient configuration) works.

menuentry 'Arch' {
    set root=(hd0,2)
    linux /vmlinux-linux root=/dev/sdb3 ro
    initrd /initramfs-llinux.img
}

(manual copy, could be errors).

Still a grub error, I'll search:

ERROR: not an assigment

Thank you by your help.

Last edited by Alber (2012-07-17 11:41:08)

Arch Linux

#1 2012-07-12 19:22:41

[SOLVED] Almost succesfully EFI install. Error: unable det.... root..

#2 2012-07-13 09:06:46

Re: [SOLVED] Almost succesfully EFI install. Error: unable det.... root..

#3 2012-07-13 09:13:30

Re: [SOLVED] Almost succesfully EFI install. Error: unable det.... root..

#4 2012-07-13 10:55:46

Re: [SOLVED] Almost succesfully EFI install. Error: unable det.... root..

#5 2012-07-13 11:56:38

Re: [SOLVED] Almost succesfully EFI install. Error: unable det.... root..

#6 2012-07-13 12:18:09

Re: [SOLVED] Almost succesfully EFI install. Error: unable det.... root..

#7 2012-07-13 13:00:52

Re: [SOLVED] Almost succesfully EFI install. Error: unable det.... root..

#8 2012-07-13 13:44:51

Re: [SOLVED] Almost succesfully EFI install. Error: unable det.... root..

#9 2012-07-13 13:51:50

Re: [SOLVED] Almost succesfully EFI install. Error: unable det.... root..

#10 2012-07-13 14:35:54

Re: [SOLVED] Almost succesfully EFI install. Error: unable det.... root..

#11 2012-07-13 14:53:27

Re: [SOLVED] Almost succesfully EFI install. Error: unable det.... root..

#12 2012-07-13 15:41:00

Re: [SOLVED] Almost succesfully EFI install. Error: unable det.... root..

#13 2012-07-14 23:06:12

Re: [SOLVED] Almost succesfully EFI install. Error: unable det.... root..

#14 2012-07-15 12:09:07

Re: [SOLVED] Almost succesfully EFI install. Error: unable det.... root..

#15 2012-07-15 17:32:14

Re: [SOLVED] Almost succesfully EFI install. Error: unable det.... root..

#16 2012-07-16 08:09:16

Re: [SOLVED] Almost succesfully EFI install. Error: unable det.... root..

#17 2012-07-16 11:19:15

Re: [SOLVED] Almost succesfully EFI install. Error: unable det.... root..

#18 2012-07-17 11:38:21

Re: [SOLVED] Almost succesfully EFI install. Error: unable det.... root..

Board footer