You are not logged in.
Pages: 1
Hello, I have a HP Folio 9470m notebook and am using uefi to boot to a GPT partition mSATA harddrive. I am attempting to add an additional SSD to the system for VM's and seem to have an issue booting once the additional drive is inserted into the machine. This is a blank unformatted brand new SSD.
I run into this error on boot:
::running early hook [udev]
starting version 219
::running hook [udev]
::triggering uevents...
Waiting 10 seconds for device /dev/sda2 ...
ERROR: device ' /dev/sda2' not found. Skipping fsck.
ERROR:: unable to find root device '/dev/sda2'.
You are being dropped to a recovery shell
Type 'exit' to try and continue booting
I am an IT professional and can google with the best of them, but I am not able to accurately state the problem. What is going on here? My original HD is /dev/sda 1,2,3 when the OS is booted. Why is udev looking to /dev/sda2 to boot ?
One solution I have found is "by-uuid" does this mean that I need to change the way the uefi is looking at disks?
Here is my fstab, is it not already using uuid?
#
# /etc/fstab: static file system information
#
# <file system> <dir> <type> <options> <dump> <pass>
# /dev/sda2
UUID=cca98213-f0cc-4bef-80f8-10cb95e776c5 / ext4 rw,relatime,data=ordered 0 1
# /dev/sda1
UUID=8779-89C8 /boot vfat rw,relatime,fmask=0022,dmask=0022,codepage=437,iocharset=iso8859-1,shortname=mixed,errors=remount-ro 0 2
# /dev/sda3
UUID=66198f9e-9d04-4c1d-b1c2-d2144dd9eb79 /home ext4 rw,relatime,data=ordered 0 2
Additionally I am not sure what boot method I am using with uefi, I know its not grub. Can anyone point me in the right direction here? I think I am missing something as I do not know where the uefi information is kept, or understand the boot process 1000%
***EDIT I have found I am using gummiboot
TIA
Kenny
Last edited by kpalmer78 (2015-05-12 23:51:25)
Offline
I am an IT professional
Impressive.
Why is udev looking to /dev/sda2 to boot ?
Almost certainly because you have
root=/dev/sda2in your kernel commandline.
Edit: see https://wiki.archlinux.org/index.php/Gu … ot_entries
Last edited by Raynman (2015-05-12 23:57:35)
Offline
Thanks for busting my balls on my first few posts and properly welcoming me. That's why I love the internet.. I was merely stating I worked in IT so that folks would know I not a complete newb.
So is /dev/sda2 changing with the addition of the new drive? I am assuming the new drive is being mounted as /dev/sda, and it has no partitions, causing the error.
Thanks for the link. reading up on it now.
Kenny
Offline
Good link I understand now. changing:
title Arch Linux
linux /vmlinuz-linux
initrd /initramfs-linux.img
options root=/dev/sda2
to :
title Arch Linux
linux /vmlinuz-linux
initrd /initramfs-linux.img
options root=PARTUUID=341aa5a6-fe34-4898-a661-c8f6b02911f3 rw
crossing fingers and rebooting...;)
***Worked Great. as specified in the link, you need to modify the file:
/boot/loader/entries/arch.conf to always look at at the PARTUUID, as the /dev/sdxY mapping can change on boot.
Thanks for the help.
Kenny
Last edited by kpalmer78 (2015-05-13 00:39:55)
Offline
Pages: 1