Unable to find UUID after pacstrap [SOLVED]

barefly · 2017-06-30 01:40:34

I was in the process of attempting to install Arch on another drive on my pc, testing out how it would work so I can could migrate files later, and ran through the steps of generating an fstab and chrooting in to begin configuring the new drive. When I attempted to restart into the new install grub gave me an error stating it couldn't find the UUID of the drive and was dropping into an emergency shell. I was unable to use my keyboard in emergency shell and hopped into my arch usb. After chrooting into my old installation of arch I was going to attempt to update grub to fix the problem, but ran lsblk and fdisk prior. I received the following errors.

lsblk
lsblk:failed to access sysfs directory: /sys/dev/block: No such file or directory

fdisk:
cannot open /proc/partitions: No such file or directory

After chrooting into the new installation and running lsblk and fdisk I am not getting the same errors, it shows the drive and partition information. How can I revert this back so I can load back into my old installation?

EDIT: I checked the fstab on my old drive and it doesn't look like it was modified.

Last edited by barefly (2017-07-03 02:41:09)

Trilby · 2017-06-30 01:43:56

Did you use arch-chroot command from arch-install-scripts or just the regular chroot command?

barefly · 2017-06-30 01:45:25

I used chroot.

EDIT: I'm thinking of formatting the drive I was testing on and installing arch again on the old drive, since all my files are still fine.

Last edited by barefly (2017-06-30 01:55:00)

Scimmia · 2017-06-30 01:54:53

https://wiki.archlinux.org/index.php/Ch … ing_chroot

barefly · 2017-06-30 02:01:23

Scimmia wrote:

https://wiki.archlinux.org/index.php/Ch … ing_chroot

In the context of doing this from a liveusb, how do I go about doing this? Do I mount both drives and reference them from their mount points? Do I need to be chrooted into the new drive since that would have been the the proc, sys, and dev info migrated to? Or can I mount both these within liveusb and run the commands from there?

EDIT: This may not work as intended because even when chrooted into the new install and I run

mount -t proc proc/

I get...
mount: can't find proc in /etc/fstab

Last edited by barefly (2017-06-30 02:11:05)

Scimmia · 2017-06-30 02:09:08

You're making this too complicated You either need to use arch-chroot, which mounts the pseudo-filesystems for you, or you need to do it manually like the wiki says. Notice that proc, sys, and dev aren't real filesystems, but in-memory access to kernel or system functions.

barefly · 2017-06-30 02:19:41

Scimmia wrote:

You're making this too complicated You either need to use arch-chroot, which mounts the pseudo-filesystems for you, or you need to do it manually like the wiki says. Notice that proc, sys, and dev aren't real filesystems, but in-memory access to kernel or system functions.

I ran the commands for chroot in the wiki and after restart it dropped me back into emergency shell.

EDIT: God I'm an idiot. Ran mkinitcpio -p linux and I'm back up. Thanks for your patience folks.

Last edited by barefly (2017-06-30 02:49:20)

ewaller · 2017-06-30 03:19:15

Remember to mark your thread as solved.

Arch Linux

#1 2017-06-30 01:40:34

Unable to find UUID after pacstrap [SOLVED]

#2 2017-06-30 01:43:56

Re: Unable to find UUID after pacstrap [SOLVED]

#3 2017-06-30 01:45:25

Re: Unable to find UUID after pacstrap [SOLVED]

#4 2017-06-30 01:54:53

Re: Unable to find UUID after pacstrap [SOLVED]

#5 2017-06-30 02:01:23

Re: Unable to find UUID after pacstrap [SOLVED]

#6 2017-06-30 02:09:08

Re: Unable to find UUID after pacstrap [SOLVED]

#7 2017-06-30 02:19:41

Re: Unable to find UUID after pacstrap [SOLVED]

#8 2017-06-30 03:19:15

Re: Unable to find UUID after pacstrap [SOLVED]

Board footer