You are not logged in.

#1 2018-04-26 20:03:46

diederick76
Member
Registered: 2010-02-14
Posts: 157

Waiting for 30 seconds for device /dev/disk/by-label/ARCH_... [SOLVED]

Hi,

Since I own a 4T hard drive I thought I'd convert my BIOS/MBR system to GPT/UEFI. I reinstalled windows 10 in that manner, and then proceeded to reinstall Arch on the second hard drive, but I can't seem to boot the installation media. It drops me into a rootfs interactive prompt after these messages:

:: running early hook [udev]
starting version 238
:: running early hook [archiso_pxe_nbd]
:: running hook [udev]
:: Triggering events...
[    3.628477] nouveau 0000:01:00.0: bus: MMIO write of 80000036 FAULT at 10eb14
 [ IBUS ]
:: running hook [memdisk]
:: running hook [archiso]
:: running hook [archiso_loop_mnt]
:: running hook [archiso_pxe_common]
:: running hook [archiso_pxe_nbd]
:: running hook [archiso_pxe_http]
:: running hook [archiso_pxe_nfs]
:: Mounting '/dev/disk/by-label/ARCH_201804' to '/run/archiso/bootmnt'
Waiting 30 seconds for device /dev/disk/by-label/ARCH_201804 ...
[   10.325119] usb 1-2: device descriptor read/64, error -110
[   26.197119] usb 1-2: device descriptor read/64, error -110
[   26.555118] usb 1-2: device descriptor read/64, error -71
[   26.801119] usb 1-2: device descriptor read/64, error -71
[   27.759116] usb 1-2: device not accepting address 5, error -71
[   28.303116] usb 1-2: device not accepting address 6, error -71
[   28.691118] usb 1-2: device descriptor read/64, error -62
[   28.940120] usb 1-2: device descriptor read/64, error -62
[   29.324118] usb 1-2: device descriptor read/64, error -62
[   29.572118] usb 1-2: device descriptor read/64, error -62
[   30.543118] usb 1-2: device not accepting address 5, error -62
[   31.095116] usb 1-2: device not accepting address 6, error -62
[   31.095163] usb usb1-port2: unable to enumerate USB device
ERROR: '/dev/disk/by-label/ARCH_201804' device did not show up after 30 seconds...
   Falling back to interactive prompt
   You can try to fix the problem manually, log out when you are finished
sh: can't access tty: job control turned off
[rootfs ]#

I have tried two USB keys, one of which just succesfully put Windows 10 on the first hard disk, I tried three different USB ports on the machine, I have created the usb key on my BIOS/MBR laptop as well as a GPT-machine and I have tried the april and the march 2018 version of the installation media.

I have also found and tried the suggestions of much older threads on this site as well as https://superuser.com/questions/519784/ … nux#611574.

The directory /dev/disks/by-label/ only contains a single entry:

Linux -> ../../sda1

Which is the existing BIOS arch. When I try to chroot into that, I get:

bash: cannot set terminal process group (-1): Inappropriate ioctl for device
bash: no job control in this shell

Is there a way I can use this installation to install it on a GPT disk?

Thanks for any help!

Last edited by diederick76 (2018-04-27 12:39:25)

Offline

#2 2018-04-26 20:46:38

Slithery
Administrator
From: Norfolk, UK
Registered: 2013-12-01
Posts: 5,776

Re: Waiting for 30 seconds for device /dev/disk/by-label/ARCH_... [SOLVED]

How did you create the installation USB?


No, it didn't "fix" anything. It just shifted the brokeness one space to the right. - jasonwryan
Closing -- for deletion; Banning -- for muppetry. - jasonwryan

aur - dotfiles

Offline

#3 2018-04-26 20:55:14

diederick76
Member
Registered: 2010-02-14
Posts: 157

Re: Waiting for 30 seconds for device /dev/disk/by-label/ARCH_... [SOLVED]

Slithery wrote:

How did you create the installation USB?

# sudo dd bs=4M if=archlinux-2018.03.01-x86_64.iso of=/dev/sdb status=progress oflag=sync

Offline

#4 2018-04-27 05:50:19

diederick76
Member
Registered: 2010-02-14
Posts: 157

Re: Waiting for 30 seconds for device /dev/disk/by-label/ARCH_... [SOLVED]

I took the hard drive from the other GPT machine and hooked it up to the machine I want to install Arch on. It has the same problem. After it boots it waits for 10 seconds for /dev/sda1 to come online, but it doesn't. But now I can't do any looking around, because it doesn't seem to respond to my keyboard.

Offline

#5 2018-04-27 06:02:40

x33a
Forum Fellow
Registered: 2009-08-15
Posts: 4,587

Re: Waiting for 30 seconds for device /dev/disk/by-label/ARCH_... [SOLVED]

@diederick76, please fix the image that you posted.

https://wiki.archlinux.org/index.php/Co … s_and_code

Offline

#6 2018-04-27 06:29:29

diederick76
Member
Registered: 2010-02-14
Posts: 157

Re: Waiting for 30 seconds for device /dev/disk/by-label/ARCH_... [SOLVED]

x33a wrote:

@diederick76, please fix the image that you posted.

https://wiki.archlinux.org/index.php/Co … s_and_code

Done. Sorry about that.

Offline

#7 2018-04-27 11:53:03

Lone_Wolf
Member
From: Netherlands, Europe
Registered: 2005-10-04
Posts: 11,866

Re: Waiting for 30 seconds for device /dev/disk/by-label/ARCH_... [SOLVED]

[   10.325119] usb 1-2: device descriptor read/64, error -110
[   26.197119] usb 1-2: device descriptor read/64, error -110
[   26.555118] usb 1-2: device descriptor read/64, error -71
[   26.801119] usb 1-2: device descriptor read/64, error -71
[   27.759116] usb 1-2: device not accepting address 5, error -71
[   28.303116] usb 1-2: device not accepting address 6, error -71
[   28.691118] usb 1-2: device descriptor read/64, error -62
[   28.940120] usb 1-2: device descriptor read/64, error -62
[   29.324118] usb 1-2: device descriptor read/64, error -62
[   29.572118] usb 1-2: device descriptor read/64, error -62
[   30.543118] usb 1-2: device not accepting address 5, error -62
[   31.095116] usb 1-2: device not accepting address 6, error -62
[   31.095163] usb usb1-port2: unable to enumerate USB device

Some EFI implementations change how USB ports are made visible to OSes dependant on a setting.

I do remember one case where setting USB support to "legacy mode" resulted in archlinux not being able to use the usb3 ports after early boot.
On that system setting USB support to windows 7 mode made it possible to continue.

Maybe you have a similar issue, check usb related settings in the EFI firmware.
What is brand and model of your motherboard ?


Disliking systemd intensely, but not satisfied with alternatives so focusing on taming systemd.


(A works at time B)  && (time C > time B ) ≠  (A works at time C)

Offline

#8 2018-04-27 12:02:28

diederick76
Member
Registered: 2010-02-14
Posts: 157

Re: Waiting for 30 seconds for device /dev/disk/by-label/ARCH_... [SOLVED]

The motherboard is a MSI 970 Gaming G Series. The usb options  are:

  • USB Controller (enabled)

  • XHCI Hand-off (enabled)

  • EHCI Hand-off (enabled)

  • Legacy USB support (auto, now disabled)

  • USB 3.0 Controller (enabled)

I disabled the legacy USB support but that didn't make a difference. Do you know what the options might do?

I also read somewhere that turning off XHCI on the kernel boot line might help. Is there a way to do that?

Offline

#9 2018-04-27 12:23:56

Lone_Wolf
Member
From: Netherlands, Europe
Registered: 2005-10-04
Posts: 11,866

Re: Waiting for 30 seconds for device /dev/disk/by-label/ARCH_... [SOLVED]

There may be a simpler solution.
Is this your motherboard  https://www.msi.com/Motherboard/970A-GA … cification ?

If so, you should have plenty of usb2 ports. Try booting with the arch iso in one of those ports.


Disliking systemd intensely, but not satisfied with alternatives so focusing on taming systemd.


(A works at time B)  && (time C > time B ) ≠  (A works at time C)

Offline

#10 2018-04-27 12:38:07

diederick76
Member
Registered: 2010-02-14
Posts: 157

Re: Waiting for 30 seconds for device /dev/disk/by-label/ARCH_... [SOLVED]

I honestly thought I already tried that before I asked this on this forum. Probably not with this USB key though. It appears to work. big_smile

Offline

Board footer

Powered by FluxBB