Arch Linux
You are not logged in.
#1 2016-01-10 04:26:13
[Solved] cannot boot, ERROR: device «» not found, skipping fsck; re.
Please help! I screwed up my work computer and I need it back online! I looked through EVERY post on this, +wiki, here and elsewhere. Didn’t work. You are my only hope.
I just need to be able to boot in. Fixing the pacman dependency issue or GRUB, or finding out what caused the initial crash, would be an added bonus.
Timeline:
(1) Yesterday my Lenovo Ideapad Yoga 211 running vanilla Arch kernel randomly crashed. I didn’t get to see the error message if there was any.
(2) Reboot failed because of a running issue with pacman kernel update breaking dependencies. I usually just boot from a USB iso, mount everything, arch-chroot, and update kernel.
(3) This time I was tired of having to do that every time I turn on the computer, so I decided to install GRUB (saw a forum post somewhere that rEFInd was causing it? not sure.)
(4) GRUB install had no errors, but won’t even show up. Just jumps straight to boot, which drops me straight into a recovery shell.
(5) rEFInd works, but still dropped into recovery or kernel panic unless mounting USB iso. Per some forum post, copied efis from /boot/ to /boot/EFI and /boot/EFI/arch
rEFInd:
(1) /boot/EFI/vmlinuz —> tries to mount /dev/mapper/arch_airootfs, kernel panic
(2) /boot/EFI/systemd/systemd-bootx64.efi —> tries to mount ‘ ‘, drops to recovery rootfs. Similar error: https://bbs.archlinux.org/viewtopic.php?id=142052
(3) /boot/EFI/arch/vmlinuz —> tries to mount ubuntu_os (. ) with correct partUUID and label. mounts successfully, but since ubuntu_os is blank, it drops to recovery rootfs. No idea where it got this value from.
(4) /boot/vmlinuz —> tries to mount arch_os with correct UUID and label, «waiting 10 seconds», kernel panic. Similar error: https://bbs.archlinux.org/viewtopic.php?id=184554
Tried several times:
genfstab -U /mnt > /mnt/etc/fstab
mkinitcpio -p linux
pacman -S linux systemd
sda1 is /boot, sda2 is /, sda3 is /home. sda4 and 5 are blank. sdb is the pen drive iso.
Arch Linux
You are not logged in.
#1 2013-07-23 11:50:25
[SOLVED] ERROR: device ‘UUID=88a. 7c’ not found. Skipping fsck.
Hi,
I hope this is the right section of the forum.
When I boot my Arch desktop everything is norrmal until it displays this error message:
I can’t use a keyboard at this stage, I don’t know why.
From what I have read about other people who have had this problem is that they had a sudden loss of power before it happened. The few that I could find didn’t have solutions. I am almost certain that I shut my computer down, however during the night there was a power cut.
Thank you in advance for any help that you can offer 
Last edited by nontlikeuname (2014-12-30 19:46:20)
#2 2013-07-23 12:05:42
Re: [SOLVED] ERROR: device ‘UUID=88a. 7c’ not found. Skipping fsck.
I suspect you’ll need to boot into a live medium to do maintainance.
Once there, get copies of your bootloader config (what bootloader is it?) and your fstab, to start.
«UNIX is simple and coherent. » — Dennis Ritchie, «GNU’s Not UNIX» — Richard Stallman
#3 2013-07-23 12:07:30
Re: [SOLVED] ERROR: device ‘UUID=88a. 7c’ not found. Skipping fsck.
It looks as though you’ve either managed to create a initrd with no modules in it, or you’ve not generated an initrd for the current kernel. You could try the fallback initrd, but I imagine that will have the same problem.
Do you have a LiveCD/USB that you can use to chroot into the installation and re-run the mkinitcpio script?
Sakura:-
Mobo: MSI X299 TOMAHAWK ARCTIC // Processor: Intel Core i7-7820X 3.6GHz // GFX: nVidia GeForce GTX 970 // RAM: 32GB (4x 8GB) Corsair DDR4 (@ 3000MHz) // Storage: 1x 3TB HDD, 5x 1TB HDD, 2x 120GB SSD, 1x 275GB M2 SSD
Making lemonade from lemons since 2015.
#4 2013-07-23 12:10:20
Re: [SOLVED] ERROR: device ‘UUID=88a. 7c’ not found. Skipping fsck.
I am using grub. I will try booting into a live usb and see if i can get bootloader config files and fstab as well as running mkinitcpio. Thanks
#5 2013-07-23 14:58:06
Re: [SOLVED] ERROR: device ‘UUID=88a. 7c’ not found. Skipping fsck.
I have run mkinitcpio and recieved no errors. I’m not exactly sure what it is meant to do or what it did do.
These are my grub config and fstab files.
#6 2013-07-23 15:28:23
Re: [SOLVED] ERROR: device ‘UUID=88a. 7c’ not found. Skipping fsck.
Sorry, I assumed you knew about mkinitcpio. If you just call the script by itself, it just does a trial run. You should pass it the preset name that you want to use (usually named after the kernel). You seem to be using the default Arch kernel, so try running:
It should create two new initial ramdisks for you for that kernel, an optimised one with the modules that your system needs to boot, and a fallback one, with all the modules for your kernel. If there are any errors, post them here.
Sakura:-
Mobo: MSI X299 TOMAHAWK ARCTIC // Processor: Intel Core i7-7820X 3.6GHz // GFX: nVidia GeForce GTX 970 // RAM: 32GB (4x 8GB) Corsair DDR4 (@ 3000MHz) // Storage: 1x 3TB HDD, 5x 1TB HDD, 2x 120GB SSD, 1x 275GB M2 SSD
Making lemonade from lemons since 2015.
#7 2013-07-23 15:42:08
Re: [SOLVED] ERROR: device ‘UUID=88a. 7c’ not found. Skipping fsck.
Thank you for explaining, I ran:
I didn’t get any errors as such but I got 2 warnings.
It did manage to create initramfs-linux.img and initramfs-linux-fallback.img though which fixed the problem.
Thanks very much for your help.
Last edited by nontlikeuname (2013-07-23 15:43:49)
#8 2013-07-23 15:56:44
Re: [SOLVED] ERROR: device ‘UUID=88a. 7c’ not found. Skipping fsck.
Those warnings can be ignored. As far as I know, they’re only relevant to embedded systems.
If you check /var/log/pacman.log, it may shed some light on why the problem occurred in the first place. Possibly an update got interrupted, or you just did the usr/bin move without holding back the bash package, and subsequently «/bin/bash» wasn’t present when the script was called. If this was the case, you may have other packages that also failed to run their associated install scripts.
Glad you got it sorted.
Sakura:-
Mobo: MSI X299 TOMAHAWK ARCTIC // Processor: Intel Core i7-7820X 3.6GHz // GFX: nVidia GeForce GTX 970 // RAM: 32GB (4x 8GB) Corsair DDR4 (@ 3000MHz) // Storage: 1x 3TB HDD, 5x 1TB HDD, 2x 120GB SSD, 1x 275GB M2 SSD
Making lemonade from lemons since 2015.
#9 2013-08-04 04:29:40
Re: [SOLVED] ERROR: device ‘UUID=88a. 7c’ not found. Skipping fsck.
I’m having the same issue, but when I try to chroot from a live USB it complains about not being able to run /bin/zsh but I chsh to /bin/sh (and still get that error). So I ran mkinitcpio directly via chroot but then it complains that /proc isn’t mounted, which is true in the chroot’d environment.
Any idea? I really need to get my laptop working again. Thanks,
Headed for the second star to the right and straight on ’til morning.
Перестала загружаться система после переноса дисков в новый системник.
диск с данным uuid существует, там находится ос линукс
был по новой сгенерирован mkinitcpio и переустановлен загрузчик, но это проблему не решило.
Вторая система типа виндовс загружается нормально.
В чем может быть проблема?
Мне кажется, мало просто «переустановить загрузчик», надо ещё и сгенерировать (или вручную) корректный grub.cfg
Если Вы всё это уже сделали-проверили, то так бы и написали, чтоб зря не гадать.
coffeewater, устройство свое имя не поменяло.
Еще при генерации конфига grub, появляется такая вот ошибка:
тынц.
https://bbs.archlinux.org/viewtopic.php?id=159484 — это первое по списку и не факт, что Ваш случай. Судя по богатому списку результатов гуглопоиска, ошибка не экзотическая.
https://bbs.archlinux.org/viewtopic.php?id=158231
Насчёт остального — не знаю. Нужно больше информации: все конфиги, причастные к этому — сюда.
Так же, сами проверьте grub.cfg (мало ли чего он там нагенерировал. ) и что, кстати, в /etc/grub.d -?
И ещё, вывод этих двух команд:
UUID соответствует не устройству, а разделу, и он не мог измениться при перестановке диска в другую машину.
UUID также не зависит от порядка устройств, он специально для того и придуман.
Раздел может быть не виден ядру из-за отсутствия в initramfs модуля с драйвером контроллера ATA новой машины.
В этом случае надо загрузиться с fallback-строки в меню груба.
Если такого нет – открыть на редактирование (клавиша «e«), исправить initramfs-linux.img на initramfs-linux-fallback.img , и нажать F10
А уже после загрузки выполнить под рутом чтобы пересобрать initramfs.
Natrio
Ничего не надо «генерировать», и бесполезно переустанавливать загрузчик.
UUID соответствует не устройству, а разделу, и он не мог измениться при перестановке диска в другую машину.
UUID также не зависит от порядка устройств, он специально для того и придуман.
Раздел может быть не виден ядру из-за отсутствия в initramfs модуля с драйвером контроллера ATA новой машины.
В этом случае надо загрузиться с fallback-строки в меню груба.
Если такого нет – открыть на редактирование (клавиша «e«), исправить initramfs-linux.img на initramfs-linux-fallback.img , и нажать F10
А уже после загрузки выполнить под рутом чтобы пересобрать initramfs.
trisch
был по новой сгенерирован mkinitcpio и переустановлен загрузчик, но это проблему не решило.