Linux - NewbieThis Linux forum is for members that are new to Linux.
Just starting out and have a question?
If it is not in the man pages or the how-to's this is the place!
Notices
Welcome to LinuxQuestions.org, a friendly and active Linux Community.
You are currently viewing LQ as a guest. By joining our community you will have the ability to post topics, receive our newsletter, use the advanced search, subscribe to threads and access many other special features. Registration is quick, simple and absolutely free. Join our community today!
Note that registered members see fewer ads, and ContentLink is completely disabled once you log in.
If you have any problems with the registration process or your account login, please contact us. If you need to reset your password, click here.
Having a problem logging in? Please visit this page to clear all LQ-related cookies.
Get a virtual cloud desktop with the Linux distro that you want in less than five minutes with Shells! With over 10 pre-installed distros to choose from, the worry-free installation life is here! Whether you are a digital nomad or just looking for flexibility, Shells can put your Linux machine on the device that you want to use.
Exclusive for LQ members, get up to 45% off per month. Click here for more info.
this is my first ever linux system and up until this, ive been really happy with it. i figured out the repositories and the terminal, but now ive gotten to a point that im totally stuck.
when i try to turn on my computer, the load screen comes up and the orange bar doesnt fill at all for about a minute and half or 2. it just sits there. but then the peach screen flashes on for a moment and then im brought to what looks like a command screen. something like safe mode for windows? its all black with white writing and it says-
" udevd[1461]: parse_config_file: cant open '/etc/udev/udef.conf' as config file: invalid argument
udevdtrigger[1463]: parse_config_file: cant open '/etc/udev/udef.conf' as config file: invalid argument
BusyBox v1.1.3 (Debian 1:1.1.3-5ubuntu12) Built-in shell (ash)
enter 'help' for a built in list of commands. "
i tried putting in help but i dont know what any of the commands mean, and none of them say boot, load, log in or anything that looks like it could get my computer past this screen. any help at all would be very, VERY greatly appreciated.
I'm using version 8.04.1. right before i did that i did a system update and had fixed a bug i had with packager thru the terminal. a friend of mine who has ubuntu also walked me thru what commands she had put into terminal.i cant find where i wrote down the whole thing but i know it started out "sudo...."
i cant find where i wrote down the whole thing but i know it started out "sudo...."
You might be able to find it with:
history | grep sudo
I'm not sure if that will help. It depends on whether or not you are actually logged in as user.
Another way to see it is to look at
/home/<your-user-name>/.bash_history and find the last commands that begin with sudo. You should be able to look at that even if you are in some single user mode.
i put that line into the command prompt and it said it wasnt found. next to where i type it says (initramfs)
after putting that command into it it says-
(initramfs) /etc/udev/udef.conf
/bin/sh: /etc/udev/udef.conv: not found
(initramfs)
Try rebooting and when you see the orange bar, Do Ctrl-Alt-F1 or Ctrl-Alt-F2. I think one of those will give you text showing what is happening. If you can catch the last few lines and the line where it stops, it might give some clues.
after i press cntrl-alt-f1 the text im getting says:
usplash: setting mode 1024x786 failed
usplash: using mode 800x600
checking root= bootarg cat/proc/cmdline
or missing modules, devices: cat /proc/modules ls /dev
ALERT! /dev/disk/by-uuid/ceab9ccf-1327-43b3-b20f-33932bc0999d does not exist. dropping to a shell!
BusyBox v1.1.3 (Debian 1:1.1.3-5ubuntu12) Built-in shell (ash)
enter 'help' for a built in list of commands.
im loosing my mind here, i really appreciate the help.
It looks like maybe the uuid got changed. That can happen if you install Linux on another partition or maybe for some other reason.
You could edit both the grub menu.lst and /etc/fstab or maybe it would be easier to boot using grub command line and then run 'update-grub' and 'grub-install /dev/sda' where /dev/sda is changed to what your actual drive is.
after i press cntrl-alt-f1 the text im getting says:
usplash: setting mode 1024x786 failed
usplash: using mode 800x600
checking root= bootarg cat/proc/cmdline
or missing modules, devices: cat /proc/modules ls /dev
ALERT! /dev/disk/by-uuid/ceab9ccf-1327-43b3-b20f-33932bc0999d does not exist. dropping to a shell!
BusyBox v1.1.3 (Debian 1:1.1.3-5ubuntu12) Built-in shell (ash)
enter 'help' for a built in list of commands.
im loosing my mind here, i really appreciate the help.
Hi, and welcome to our forum!
At this stage, there is little you can do from Busybox to repair the damage...
If you haven't do any work of your own yet (e.g have written some documents) with your ubuntu system, I suggest you put in your CD your Installation disk, and reinstall ubuntu. Of course if you know about partitions and file-systems, you may choose to not format the partition where your /home directory resides (and keeping the same filesystem as before)... This way you wont lose any work ...
vasmakk may be right. However, before going that far, at least try this:
Reboot, and when you see "Grub loading...", press ESC, then select Recovery Mode. After a few lines of text, you'll see a menu. Select "xfix", then "Normal Boot".
I've recovered from a lot of screw-ups that way.
Cheers
Last edited by DragonSlayer48DX; 06-13-2009 at 03:47 PM.
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.