RESOLVED Unable to write to /run/udev/ THANKS ALL

[Snowhog]

Re: Unable to write to /run/udev/ Emergency for me.

At this point, reboot with the Grub2 LiveCD and see if it will boot your Kubuntu for you. Reinstall is far down on the list of things to go through.

[Shabakthanai]

Re: Unable to write to /run/udev/ Emergency for me.

Stopped at the Login screen again, with inactive mouse and keyboard.

Two choices for boot, I chose first option.

[Snowhog]

Re: Unable to write to /run/udev/ Emergency for me.

When you say 'Login screen', do you mean the KDM Login screen? The screen you would type in your user name and password?

[Shabakthanai]

Re: Unable to write to /run/udev/ Emergency for me.

When you say 'Login screen', do you mean the KDM Login screen? The screen you would type in your user name and password?

Yes, in fact the one with the beautiful wallpaper with bubbles. That is where it has always stopped, too, if that makes a difference by knowing.

[Snowhog]

Re: Unable to write to /run/udev/ Emergency for me.

We are getting closer.

Reboot with the Grub2 LiveCD. Read the information at the bottom of the screen as to editing options. I believe you press the Tab key. This allows you to edit the kernel line options. You want to edit the line that has quiet splash. Use your arrow keys to move to these two and delete them (if they are present). At the end of this line add: vga=791 and then press Enter to continue to boot. I'm suspecting a video card issue now.

[Snowhog]

Re: Unable to write to /run/udev/ Emergency for me.

Got to step away for a little bit. I'll check back later.

[Shabakthanai]

Re: Unable to write to /run/udev/ Emergency for me.

I had difficulty following the instruction. SuperGrub2 opened with the following choices:

Detect any OS
Detect any grub.cfg
Detect any grub2 installation (even if MBR is overridden)
Detect any loop bootable isos (in /boot-isos or /boot/boot/isos)
Enable grub's LVM support
Enable grub's RAID support
Enable grub's PATA support (to work around bugs/limitations)
Enable grub's USB support *experimenetal
Enable grub's Serial terminal
List devices & partitions

Use the up and down keys to select which entry is highlighted. Press Enter to boot the selected OS, 'e' to edit the commands before booting or 'c' for a command-line.

Here is where I probably screwed up. I highlighted the first entry, pressed e then pressed enter. Got a negative result. Next I highlighted detect any grub.cfg, the line that was produced did not appear the one I needed, so I pressed e and the next line did not seem right either. Then I highlighted the next entry 'Detect any Grub2 installation and e for the lines presented. One of these attempts produced the normal SuperGrub2 screen, so this time I selected the single user entry and then e and enter. I got 18.500010 USB 3-2 : device descripter read/64, error -110. So much was happening that I let things run until a blue screen came up with an edit line that had 'cups cron (the third entry I cannot read my note) with a blinking underscore for edit entry. It appeared that the existing option was ok, so I did not enter any additional information and pressed enter. I was trying to get out of my predicament with as little damage as possible, then a window appeared with the following choices:

resume
clean
dpkg
fsck
grub update boot loader
net root (net shell with networking)

dpkg seemed an appropriate entry that might help any problem I may have made so I selected it. It ran downloading and installing 350+MB of data before it finished. I received an option to boot normally and chose it. It almost opened my system. The wallpaper that I chose for my past installation for the Login Screen flashed on the screen and returned to the boot option. I tried it several times to see if it might catch, but it did not. I shut down the computer before doing anything more that I had no business doing and decided to return for help. It is obvious to me that the OS is probably installed. There was a point where I could have entered a root shell, however I would not have know how to take advantage of it without help. I did not try to update the boot loader, because I thought I probably damaged it. I know I have disappointed you, however, I have had difficulty understanding and following instruction from experts and have tried things that appeared logical, with some success during my learning process. It is just, I did not recognize any entry that I thought would provide a line to edit from I suppose the kernel. And faced with that dilemma, I tried several choices using the 'e' before enter key to see if I could find something with quiet splash to edit out. Then one thing led to another until it was damage control, trying to get out of the complicated fix I was in. Have I screwed up all your work?

I feel the fool I am.

[Snowhog]

Re: Unable to write to /run/udev/ Emergency for me.

Don't feel bad. Trying to assist 'long distance' and with a time difference as well, is well, not easy for anyone.

At this point, especially with the downloads/installs that got performed, I don't know what state your OS is actually in. I'm truely sympathetic to your situation. It may be time to consider doing a clean install (once again) with some coaching as to how to do it the way the 'experts' do it. If you are game, I'll do my best to provide you with easy to follow steps. Let me know.

[Shabakthanai]

Re: Unable to write to /run/udev/ Emergency for me.

I am very sorry. At the beginning, I thought I was doing the right thing, then something I did not expect happened and I panicked. Trying to recover was a maze. Each time I looked for a way out, something somewhat logical offered itself, but when trying that option I just got deeper into the problem. I believe when the option dpkg was offered is when the big changes took place. I though at that time that maybe that could correct what I had been doing wrong. I wish I knew how to make a small mistake.

If I were you, I would be angry with me; I hope you can forgive me.

[Snowhog]

Re: Unable to write to /run/udev/ Emergency for me.

If I were you, I would be angry with me; I hope you can forgive me.

Angry? Why? Nothing to forgive. I'm not upset. Just let me know if you want to 'bite the bullet' and go for another clean installation. As said, I'll do my best to provide you with easy to follow instructions on what to do, and when to do it.

[Shabakthanai]

Re: Unable to write to /run/udev/ Emergency for me.

You are an amazingly terrific person. I suspect you recognize the username 'dibl'. Years ago he came to my home and helped me though a similarly complex problem. At least complex to me. In any event, a couple of days ago he offered to come and install a new system. I declined because I am really learning much with this repair and wanted to see it through. He wrote and offered again to come tomorrow, and I accepted. I am suspicious I will have to get a new HDD, however, your suggestion of my problem being a video problem seems more probable to me.

For years I was unable to understand the instructions provided by those who would help me. As a result, I, suppose with false pride, got kind of used to re-installing when big problems arose rather than try to repair them. It seemed I was unable to understand the simplest of instruction. Kind of like what happened yesterday, when I screwed up.

I really consider myself quite professional when installing an OS, because I have successfully done it so many times. I am probably wrong about that too. After reading your last post, and because I am confident in the installation process, I attempted installing Kubuntu Natty again. This time it was different than the last time. During the installation of the OS, after formatting and enabling and entering the appropriate file systems, and mounting and naming the partitions again, the installation was aborted. The explanation was that the CD was dirty or defective or the drive was bad. I took the reference to the drive to be the HDD.

Nevertheless, prior to installation, I tested the LiveCD for errors and was told that there were no errors. I also cleaned the surface of the CD and checked it's appearance as good, so unless some electronic glitch had affected the CD, I am pretty sure it is still perfect.

During my debacle, I had those brief moments when the system was trying to finish boot, where my custom preferred 'Login Screen' showed the former wallpaper, different from the LiveCD Login Wallpaper. Additionally the rather long dpkg that took place seemed to be modifying the installed OS that would not open, so logic, excuse me my logic, suggested that the HDD must still be OK

I am of a mind that if I could remove the quiet splash and enter the vga=791, success might be achieved. I so wish I could have understood your post relating to those changes using SuperGrub2.

I would like you and GreyGeek to know how much I appreciate your working through the process regardless of the outcome or who assists in the last step. I only chose dibl's offer so I could physically experience how I may improve my installation skills. Also, I thought perhaps he might try your idea with SuperGrub2 relating to the video question. I am anxious to understand that process. In fact, when my system works again, I am going to spend the necessary time to learn and understand the function of and repair of a broken grub.

How kind you are in your response after all the time you both spent helping me learn the steps to resolving this type of problem, only to have me destroy those efforts and all that concern and time by my foolishness at the end. Thanks from the bottom of my heart.

[Snowhog]

Re: Unable to write to /run/udev/ Emergency for me.

dibl is a good person. I'm sure he can get you squared away quickly. Being 'on site' is a big advantage as you are certainly aware.

As to my steps for SuperGrub (editing), please ignore that. I was mistaken (happens). Editing the boot kernel can be done from a real Grub menu, not from SuperGrub. Sorry to have misled you on that.

Do post back on the efforts by dibl, as again, I'm sure that he will be able to get you going - unless you truely do have a HDD that is going bad on you.

Your kind remarks are well received. I hope that you don't feel bad having gone on this journey with us. We are here to provide what aid and assistance we can, within the scope of our skills, knowledge, and abilities.

Be well.

[GreyGeek]

Re: Unable to write to /run/udev/ Emergency for me.

Indeed, and remember, no one has "forsaken you".

[Shabakthanai]

Re: Unable to write to /run/udev/ Emergency for me.

Thanks brother.

[Shabakthanai]

Re: RESOLVED Unable to write to /run/udev/ THANKS ALL

Dibl did his normal thing and got me going again. Strangely though, about 15 minutes before he arrived, I, using SuperGrub2, got the system working again, however, when trying to boot again it went back to its samo problems. Additionally the system opened in Root, a bit scary.

Dibl reinstalled; it took several tries, he made modifications I don't understand completely, but in the end victory. I am very happy, however there are still things that he does not understand about my system. For instance, on a formatted fresh install, when the system opened, my chosen Login Screen Walpaper was retained from my previous install, as well as, my desktop wallpaper. All the plasmoids that were still in place and working and several configurations were carried forward. He was unable to understand why and thinks it may be caused my my motherboard, which has Internet, Skype, and Chat in the motherboard to use even prior to installing any OS.

There were a few other unusual things, but at the moment they don't come to mind. Just wanted to give an update on the repair for those who are following. Cheers all!