<html>
<head>
<style><!--
.hmmessage P
{
margin:0px;
padding:0px
}
body.hmmessage
{
font-size: 10pt;
font-family:Tahoma
}
--></style></head>
<body class='hmmessage'><div dir='ltr'>
Hello,<br>I charged up by notetaker (battery was dead yesterday) and wrote down what my sighted-assistance read off for the last few messages in the boot process.<br><br><br>decompress linux ... parsing ELF ... done.<br>booting the kernel.<br>Running hook udev<br>Triggering uevents ... done.<br>ERROR: device "/dev/sda4" not found. Skipping fsck.<br>ERROR: unable to fid root device "/dev/sda4."<br>You are being dropped to a recovery shell.<br>Type "exit" to try and continue booting.<br>SH: can not access tty; job control turned off.<br>[rootfs] /#<br><br><br>I'm not sure if this changes the recommendation on fsck. I'm not fammiliar with the command, but I'll do some rreading up on it to get an idea what to expect.<br><br>My machine is partitianed such that<br>sda1 and sda2 belong to windows (came that way).<br>I added sda4 which holds the root ("/") of my system.<br>sda5 I set aside for /home<br>sda6 is my swap<br>sda3 I think is the logical partitian that allows for sda 5 and sda6.<br><br><br>>I'm not familiar with archlinux, but your symptoms are those that happen<br>>if there's an error in the linux filesystem that couldn't be automatically<br>>corrected. When that happens, you're dropped into a rudimentary system<br>>with a command-line shell prompt so that you can manually fix that error.<br>>The "fs" in the prompt supports this idea.<br>><br>>The "failed to load tty" I've never seen in this context, but it could be<br>>related to being unable to bring up speech synthesis.<br>><br>>If you are unable to fix the error, you won't be able to get any further.<br>><br>>What you would need to do now is to first verify that you indeed do<br>>have a filesystem error, and which drive(s)/partition(s) is/are affected.<br>>Preceding the "root/fs" prompt should be messages that might help<br>>pinpoint the error source.<br>><br>>If this is in fact the cause of your situation, then you'd have to<br>>issue an "fsck" (file-system check) command, and try to answer the<br>>fix-up questions it poses.<br>><br>>I know this merely parses the problem without offering a solution to you.<br>> </div></body>
</html>