[Solved] Wierd boot order when external drives are connected

anark10n · 2013-03-24 20:43:00

So, I've got two external drives, an ntfs drive and ext4 drive. After a recent upgrade, I get this error message when starting up the computer with them connected.
Bootloader: syslinux.

For the ntfs drive:

::performing fsck on '/dev/sda1'
fsck: fsck.ntfs: not found
fsck: error 2 while executing fsck.ntfs for /dev/sda1
ERROR: fsck failed on '/dev/sda1'
::mounting '/dev/sda1' on real boot
mount: unknown filesytem type 'ntfs'

For the ext4 drive (Megadrive is the name of the hard drive):

::performing fsck on '/dev/sda1'
Megadrive: clean, 230913/188148544 files, 193365856/732566385 blocks
ERROR: Root device mounted successfully, but /sbin/init does not exist. Bailing out, you are your own. Good luck.

With both of them connected, it gives the same message as for when the ext4 external is connected. When they are both disconnected, it finds the proper drive that I recorded in syslinux.cfg file.
What could be causing this? If someone could point me in the direction of how to troubleshoot this, that would be a great help?

Last edited by anark10n (2013-03-24 22:42:11)

jasonwryan · 2013-03-24 20:51:24

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

anark10n · 2013-03-24 22:43:13

Ok, I fixed it using UUIDs, but is there anyway of figuring out why it suddenly started acting strangely?

jasonwryan · 2013-03-24 22:57:20

Look through pacman's log to see what was upgraded...

Arch Linux

#1 2013-03-24 20:43:00

[Solved] Wierd boot order when external drives are connected

#2 2013-03-24 20:51:24

Re: [Solved] Wierd boot order when external drives are connected

#3 2013-03-24 22:43:13

Re: [Solved] Wierd boot order when external drives are connected

#4 2013-03-24 22:57:20

Re: [Solved] Wierd boot order when external drives are connected

Board footer