You are not logged in.

#1 2017-02-15 07:11:46

Andrew.B
Member
From: Moscow, Russia
Registered: 2010-12-07
Posts: 23

[solved] can't boot installed arch

I just installed arch on my new PC
After I select boot entry in systemd-boot it writes:

:: running early hook [udev]
starting version 232
:: running hook [udev]
:: truggering events
ERROR: device '' not found. Skipping fsck
ERROR: unable to find root device ''
You are being dropped t t a recovery shell
     Type 'exit' to try and continue booting
sh: can't access tty: job control turned off

/etc/fstab is:

# 
# /etc/fstab: static file system information
#
# <file system>	<dir>	<type>	<options>	<dump>	<pass>
# /dev/sda3 UUID=3218c9e1-4787-491d-baac-a7fcd932149f
LABEL=root          	/         	ext4      	rw,relatime,data=ordered	0 1

# /dev/sda2 UUID=EAB2-BE8D
LABEL=ESP           	/boot     	vfat      	rw,relatime,fmask=0022,dmask=0022,codepage=437,iocharset=iso8859-1,shortname=mixed,errors=remount-ro	0 2

# /dev/sda4 UUID=6739d352-c556-4d2c-b18e-65a81cb92a81
LABEL=home          	/home     	ext4      	rw,relatime,data=ordered	0 2

Boot entry /boot/loader/entries/arch.conf is:

title  Arch Linux
linux  /vmlinuz-linux
initrd /intel-ucode.img
initrd /initramfs-linux.img
opions root=LABEL=root nomodeset

Last edited by Andrew.B (2017-02-15 12:22:27)

Offline

#2 2017-02-15 08:17:08

V1del
Forum Moderator
Registered: 2012-10-16
Posts: 21,427

Re: [solved] can't boot installed arch

Well are your partitions labeled? What's the output of

lsblk -f
blkid

? why don't you simply use the UUIDs which are apparently already available yet not being used for identification?

Offline

#3 2017-02-15 08:32:35

Andrew.B
Member
From: Moscow, Russia
Registered: 2010-12-07
Posts: 23

Re: [solved] can't boot installed arch

I prefer to use labels because I think they are more readable.

lsblk -f:

NAME   FSTYPE LABEL UUID MOUNTPOINT
loop0                    
sda                      
|-sda1                   
|-sda2                   /boot
|-sda3                   /
`-sda4                   
sdb                      
|-sdb1                   
`-sdb2                   
sdc                      
`-sdc1                   /mnt

blkid:

/dev/sda1: LABEL="swap" UUID="82ab4624-7ed5-4dd8-8c2b-f742d6598219" TYPE="swap" PARTUUID="109129de-fb10-4ab6-a436-0026960e4886"
/dev/sda2: LABEL="ESP" UUID="EAB2-BE8D" TYPE="vfat" PARTUUID="a468d114-6f3a-440f-991c-f3fcb889fd58"
/dev/sda3: LABEL="root" UUID="3218c9e1-4787-491d-baac-a7fcd932149f" TYPE="ext4" PARTUUID="47ceb46d-43e5-45d1-a12c-75c4ffdfd8ae"
/dev/sda4: LABEL="home" UUID="6739d352-c556-4d2c-b18e-65a81cb92a81" TYPE="ext4" PARTUUID="a34bf377-3d44-4f7d-a6a1-1882901c2786"
/dev/sdb1: UUID="2017-02-01-17-08-09-00" LABEL="ARCH_201702" TYPE="iso9660" PTUUID="79ef3b99" PTTYPE="dos" PARTUUID="79ef3b99-01"
/dev/sdb2: SEC_TYPE="msdos" LABEL="ARCHISO_EFI" UUID="5B13-1CA8" TYPE="vfat" PARTUUID="79ef3b99-02"
/dev/loop0: TYPE="squashfs"
/dev/sdc1: LABEL="KINGSTON" UUID="9159-262F" TYPE="vfat" PARTUUID="65fba8d7-01"

Offline

#4 2017-02-15 08:36:07

HiImTye
Member
From: Halifax, NS, Canada
Registered: 2012-05-09
Posts: 1,072

Re: [solved] can't boot installed arch

Andrew.B wrote:

I prefer to use labels because I think they are more readable.

you can literally name your folder tree anything you want (aside from system folders, though you could use links). you could even have a /C: if you prefer, but you should use your UUIDs in your fstab to ensure that no errors occur. you can always include the label in the comment line above, where your UUIDs are for some reason

Last edited by HiImTye (2017-02-15 08:36:36)

Offline

#5 2017-02-15 09:02:52

seth
Member
Registered: 2012-09-03
Posts: 49,992

Re: [solved] can't boot installed arch

The lsblk output should make you weary and using the label isn't a good idea at all, because they don't have to be unique. Personal preferences aside: the uuid is the sane choice.

Offline

#6 2017-02-15 09:27:42

Andrew.B
Member
From: Moscow, Russia
Registered: 2010-12-07
Posts: 23

Re: [solved] can't boot installed arch

I've changed the boot entry, now it consists of:

title  Arch Linux
linux  /vmlinuz-linux
initrd /intel-ucode.img
initrd /initramfs-linux.img
opions root=PARTUUID=47ceb46d-43e5-45d1-a12c-75c4ffdfd8ae nomodeset

and /etc/fstab now is:

# /dev/sda3 LABEL=root
UUID=3218c9e1-4787-491d-baac-a7fcd932149f	/         	ext4      	rw,relatime,data=ordered	0 1

# /dev/sda2 LABEL=ESP
UUID=EAB2-BE8D      	/boot     	vfat      	rw,relatime,fmask=0022,dmask=0022,codepage=437,iocharset=iso8859-1,shortname=mixed,errors=remount-ro	0 2

# /dev/sda4 LABEL=home
UUID=6739d352-c556-4d2c-b18e-65a81cb92a81	/home     	ext4      	rw,relatime,data=ordered	0 2

but I still have the same error on booting.

Offline

#7 2017-02-15 11:12:29

Andrew.B
Member
From: Moscow, Russia
Registered: 2010-12-07
Posts: 23

Re: [solved] can't boot installed arch

Damn... It was a silly typo in  boot entry, the last line was opions instead of options. I fixed it but stoll have an error:

:: running eaely hook [udev]
Starting version 232
:: running hook [udev]
:: performing fsck on '/dev/sda3'
root: clean, 39676/1921360 files, 438496/7680000 blocks
:: mounting '/dev/sda3' on real root
[    2.345011] EXT4-fs(sda3): Cannot load  crc32c driver.
mount: mount(2) failed: /new_root: No such file or directory
You are now being dropped into an emergency shell.

Offline

#8 2017-02-15 14:52:35

seth
Member
Registered: 2012-09-03
Posts: 49,992

Offline

#9 2017-02-16 06:20:00

Andrew.B
Member
From: Moscow, Russia
Registered: 2010-12-07
Posts: 23

Re: [solved] can't boot installed arch

Thanks, I found it already and it helped me.

Offline

Board footer

Powered by FluxBB