[SOLVED] Issue Booting in to System

morphjk · 2011-10-06 04:46:31

For some reason every second or third boot I am getting the following error:

Root device '/dev/sda5' doesn't exist. Attempting to creat it.

ERROR: Unable to determine major/minor number of root device '/dev/sda5'

You are being dropped to a recovery shell

Type 'exit' to try and continue booting

sh: can't access tty: job control turned off

I've checked all the sata cables and there is nothing wrong with them (checked these because I have seen issues be caused due to sata cables not being connected properly).

I am still relatively new to Linux so not sure how to fix this. When the machine is up everything works fine.

Any help greatly appreciated.

EDIT: Replaced motherboard which has resolved the issue.

Last edited by morphjk (2011-11-21 05:08:04)

jasonwryan · 2011-10-06 04:52:53

Check this out: https://wiki.archlinux.org/index.php/UUID#by-uuid

klerik · 2011-10-06 06:37:53

morphjk can U try re-upgrade the kernel (from chroot in live-usb)? I have same issue like U and when i upgrading the kernel (pacman -U linux-3.0.6-1...) i have many error messages with missing modules.

morphjk · 2011-10-11 01:55:55

jasonwryan wrote:

Check this out: https://wiki.archlinux.org/index.php/UUID#by-uuid

A query that I have is if it's a result of the disks coming up in the wrong order, and say it comes up with sda as sdb and vice versa. When grub goes looking for "/dev/by-uuid/blah blah", then isn't it going to have the same issue? i.e. Those files won't be there if the disk is swapped?

Last edited by morphjk (2011-10-11 01:56:10)

falconindy · 2011-10-11 02:16:31

morphjk wrote:

jasonwryan wrote:
Check this out: https://wiki.archlinux.org/index.php/UUID#by-uuid
A query that I have is if it's a result of the disks coming up in the wrong order, and say it comes up with sda as sdb and vice versa. When grub goes looking for "/dev/by-uuid/blah blah", then isn't it going to have the same issue? i.e. Those files won't be there if the disk is swapped?

UUID symlinks are created by udev (via blkid) at the time of device discovery (on every boot). mkinitcpio allows shorter versions of this, similar to /etc/fstab though, e.g.

"root=UUID=ea1c4959-406c-45d0-a144-912f4e86b207" or "root=LABEL=mysweetroot"

instead of the more verbose

/dev/disk/by-uuid/ea1c4959-406c-45d0-a144-912f4e86b207

Note that these shortcuts do not rely on udev, and use blkid directly to low level probe block devices.

Last edited by falconindy (2011-10-11 02:17:22)

Arch Linux

#1 2011-10-06 04:46:31

[SOLVED] Issue Booting in to System

#2 2011-10-06 04:52:53

Re: [SOLVED] Issue Booting in to System

#3 2011-10-06 06:37:53

Re: [SOLVED] Issue Booting in to System

#4 2011-10-11 01:55:55

Re: [SOLVED] Issue Booting in to System

#5 2011-10-11 02:16:31

Re: [SOLVED] Issue Booting in to System

Board footer