You are not logged in.
Pages: 1
Full text:
starting version 232
/dev/sda3: clean, 37200/8257356 files, 951377/33030144 blocks
[ 3.156477] 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.
sh: can't access tty; job control turned off
[rootfs ]# exit
ERROR: Failed to mount the real root device.
Bailing out, you are on your own. Good luck.
sh: can't access tty; job control turned off
I've already booted to a live USB, chrooted into the installation and added the crc32 modules to mkinitcpio.conf and re-run mkinitcpio.
Offline
Does the "fallback" initramfs load?
Please also provide complete details of your installation procedure.
Jin, Jîyan, Azadî
Offline
Related? https://bbs.archlinux.org/viewtopic.php?id=210673
Also see: https://wiki.archlinux.org/index.php/Ex … _checksums
I've already booted to a live USB, chrooted into the installation and added the crc32 modules to mkinitcpio.conf and re-run mkinitcpio.
Which modules did you add, exactly?
Last edited by 2ManyDogs (2017-01-31 18:29:30)
Offline
Does the "fallback" initramfs load?
Please also provide complete details of your installation procedure.
Steps taken:
Downloaded latest image and wrote to USB drive with Lili.
Installed per Arch Wiki Installation Guide, including GRUB (old laptop uses BIOS, not UEFI)
Rebooted.
Choosing either normal boot or fallback boot from GRUB yields the same result.
Related? https://bbs.archlinux.org/viewtopic.php?id=210673
Also see: https://wiki.archlinux.org/index.php/Ex … _checksums
Which modules did you add, exactly?
I'll check that out when I get another opportunity to fiddle with the laptop. Currently working.
I added all the modules listed in the solution for that post, plus a couple more I found with further searching. I see one that I hadn't seen before in that blog link, but I can't fiddle with the laptop until my shift is over.
Offline
Got a chance to add the crypto-crc32 module to mkinitcpio.conf. No dice. Tried fallback boot, here's some more info that may help:
[…]
[FAILED] Failed to mount /boot.
(here I ran systemctl status boot.mount as recommended)
[…]
Active: failed (Result: exit-code)
Where: /boot
What: /dev/disk/by-uuid/DC34182B34180B62
Docs: man:fstab(5)
man:systemd-fstab-generator(8)
Process: 226 ExecMount=/usr/bin/mount /dev/disk/by-uuid/DC34182B34180B62 /boot -t ntfs -o rw,nosuid,nodev,relatime,user_id=0,group_id=0,allow_other,blksize=4096 (code=exited, status 32)
I commented out that drive from fstab and now the fallback boot appears to boot properly, but normal boot remains unchanged.
Offline
A separate issue you probably will want to look into is why the partition you are trying to mount is formatted ntfs or the at least the fstab entry for it is for an ntfs partition.
You did regenerate the initrd after changing mkinitcpio.conf?
Offline
A separate issue you probably will want to look into is why the partition you are trying to mount is formatted ntfs or the at least the fstab entry for it is for an ntfs partition.
You did regenerate the initrd after changing mkinitcpio.conf?
It shouldn't have been there. /dev/sda1 is a Windows boot loader partition, I was just checking what it was to be sure (laptop is new to me) and had it mounted to /mnt/boot when I generated fstab.
And yes, I did that as well.
Offline
Possibly-but-not-quite-really-solved: I reinstalled Arch using the same USB stick as before, but I used an EXT3 file system instead of EXT4 and it behaves properly, no need to even add modules to mkinitcpio.conf.
Offline
Pages: 1