Announcement

**Shabakthanai** · Jun 24, 2011, 11:51 PM

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

Originally posted by Teunis

So you mean to say you did complete the installation but when you start up the new installation you get stuck just before logging in?Yes I completed the installation and rebooted. When the Login Screen appeared, the mouse would not move.

When that's the case it's probably a video driver issue, you could try to log in using the recovery mode. The only options in the boot menu were CD, HDD. Neither produced any change. There was no recovery option. I reset to default in the BIOS to see if it was a video card issue. Nothing changed.
When you have a single-boot (Kubuntu is the only operating system on your computer), to get the boot menu to show, you have to hold down the Shift key during bootup. I was unaware of how to do that. I did have an option available to click f8 to enter the boot menu; it produced what I said before. Since I am in a Live CD right now, I will finish answering your questions prior to trying your 'Shift Key' option to see if that changes the boot options.

When you have a dual-boot (Kubuntu is installed next to for example Windows; and you choose at boot time which operating system to boot into), the boot menu should appear without the need to hold down the Shift key. I no longer have any other OS in my computer.

From the boot menu, select recovery mode, which is usually the second boot option. Not available as previously mentioned.

Select one of the options and tell us how far you get.Just before Booting to Live CD this time, I attempted restart of the computer under normal circumstances after leaving the computer shut off for several minutes. No particular reason, I just thought maybe things might change if no electricity passed through it for a while. When I booted up this time, I got this error message and did not know how to deal with it either: Error: no such device d37edb06-1aae-4e9a-8e64-1703ba8e6e41 - Nest Line - Grub rescue> I typed in ls and got several options which looked like DOS options. Unfortunately, I screwed up and did not copy them down, there were many. In any event, I would not have know what to do without help.
The last resort one would be the option to drop to a root shell prompt, the one with networking is obviously preferable. I am too inexperienced on the command line. I would need help with proper code and instruction. I believe this may be my only solution, because every time I have tried to install any other operating system, after installation, I come to the same error message and no way that I know to finish the boot process.

**GreyGeek** · Jun 25, 2011, 05:09 AM

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

Turn your computer off.

While holding down the Shift Key, turn on the computer.

Keep the Shift Key depressed until you see the Grub menu.

When the Grub menu appears, press the Down Arrow and move the focus to the second line of the Grub menu. This line starts the computer in the recovery mode.

After a short period of time another menu will appear. This is the Recovery Mode menu. There should several (5) options available.

Arrow down to the LAST option (root console with network connection).

Press the Tab Key to move the focus from the last option to the "Ok" button.

Press the Enter Key.

This will boot you into a console as root, with your network connection running, assuming you have an Ethernet cable connected to Eth0. (If you had wicd installed and configured for your wireless you could have a wireless connection without the Ethernet cable.)

At this point your are in a "base" condition for testing video issues. If your computer locks up again you can do the steps above to restore this base condition and try a different approach.

The first thing to try is just starting the KDE desktop. Issue
service kdm start
and,hopefully, KDE will start up and your keyboard will work, and continue to work when you reboot. If not, you may have to create a piece of the xorg.conf file. That can be explained later.

**Shabakthanai** · Jun 25, 2011, 11:08 AM

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

Thank you for the wonderful way you described your response.

The screen that appears is black with white print (Like a console screen). It displays the following:

error: no such device: d37edb0b-1aae-4e9a-8e64-1703ba8e6e41
grub rescue>_ (with a blinking cursor)

This may be what you wanted to finally appear, however, I never had the (5) choices that include 'recovery mode'; the error message is the only screen I got when depressing the Shift Key and holding it down then turning on the computer. It no longer stops at a screen with the message, (unfortunate I have to paraphrase), 'unable to write to /run/udev...' It also said that when unable to write to /run/udev it then went to another process, but I can't remember the detail. I didn't realize I was in such trouble at the time. I just rebooted thinking something caused a glitch that would probably be corrected when rebooting. I remember putting notes in a document and saving it, I think in the Documents or Desktop folder, but when I finally had to use the Live CD, I was not permitted to enter those files to get the exact error messages and descriptions. I also remember googling for information relating to the error message and came to a screen where kubuntu developers were discussing this problem. They suggested it was a bug and were unclear what should be done. (I just tried to find that page, however my current description of the problem does not include all the information that got me to that discussion, and I am unable to find it again without my browsing history available.) Sorry if I am too wordy, but I don't know what is important and what is not from this experience. Thank you for your patience.

If I end at the right place when at 'grub rescue', what do I type in to further the process?

**GreyGeek** · Jun 25, 2011, 11:49 AM

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

Since you are no longer dual booting with Windows it appears that your HD has been misconfigured, possible by attempting to do a manual partition of the HD.

Rather than going through a long complicated procedure for trying to recover grub from an error, it would be much simpler if you merely reinstalled Kubuntu from the LiveCD. But, this time, instead of doing a manual partition, if that is what you did, just give Kubuntu the ENTIRE HD and let it sort things out for itself.

**Shabakthanai** · Jun 25, 2011, 05:23 PM

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

Dear GreyGeek,

I don't know how I confused you, but I have not been running a dual-boot nor Windows for 8 years. The original problem occurred when operating Kubuntu Natty 64bit. My operating system is located on my 1TB HDD using your suggested installation procedure would wipe out most of my saved data.

Your most recent reply suggests a Grub problem and reinstall. Since I have been attempting to reinstall unsuccessfully, I believe the problem is as you infer... in the grub, and if the grub remains broken, any new installation attempt will continue in failure until I repair the grub (which is obviously over my head without help).

I don't know if having this is important, but my OS is on a 15gb partition and is separate from all other data. Additionally, I have a 20gb swap partition. I have 8 partitions in total and 1.5TB in 2 HDD's.

The only affected partition is my boot partition, I believe.

Thanks for your patience. Please don't give up on me, if you still feel you can isolate the problem?

**GreyGeek** · Jun 25, 2011, 05:53 PM

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

Ok, re-installation is not an option!

At the grub menu at boot up (hold the "shift" key while booting until you get the Grub menu) select the OS you are trying to boot. But do not press "enter", press "e" instead to edit the menuentry. Delete the line:

search --no-floppy --fs-uuid --set d37edb0b-1aae-4e9a-8e64-1703ba8e6e41

and then press "Ctrl+X". This should boot your OS. If you were not able to boot into you OS, you are experiencing a different problem which we will have to address.

If you are able to boot into Kubuntu and get to the desktop open a Konsole and issue

sudo blkid

and post the contents of that command. Also, the contents of
/etc/default/grub
and
/ect/fstab

**Snowhog** · Jun 25, 2011, 05:57 PM

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

Two things are possible -1) your root partition (15GB) is full (how many kernel versions have you got?), or 2) the UUID of your root partition is/was/has been changed and the reference to it in /boot/grub/grub.conf is wrong. Can you burn a copy of Super Grub2? This should/will allow you to boot into Kubuntu so some forensic review can be performed.

**GreyGeek** · Jun 25, 2011, 06:01 PM

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

Shabakthanai, forget my advice and go with Snowhog's!

**Shabakthanai** · Jun 25, 2011, 08:52 PM

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

Dear Snowhog,

I was unable to make a CD with SuperGrub2. I suppose the Live CD is necessary to complete the project and the blank media and Live CD cannot occupy the same space at the same time.

I notice that SuperGrub2 is an .exe file and the new installation has not yet included the application Wine. Is wine needed to have SuperGrub2 functional? I was able to copy SuperGrub2 to a thumb drive, but there is other information on the drive too. Do I have to lose the other data to have SuperGrub2 functional? Is SuperGrup2 an ISO? I also copied an .odt of other data included on the download page. Do I have to change the boot sequence in the BIOS and will the removable entry respond to a thumb drive?

I believe I have plenty of space on my boot drive. I believe appx. 10gb, however, I don't recall looking closely at it other than to make sure it was not crowded. I usually maintain a plazmoid on the desktop with hard drive space indicated, so I am generally aware when a partition or drive is getting critically filled.

Thanks for current help!

**Snowhog** · Jun 25, 2011, 09:10 PM

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

SuperGrub2 is an .iso and you would burn it to CD to create a LiveCD of SuperGrub2.

**GreyGeek** · Jun 25, 2011, 10:03 PM

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

Shabakthanai, perhaps the advice given in my msg (just before Snowhog's) will be sufficient to get your desktop running and then you can download and burn the SuperGrub2 iso.

It's worth a try, seeing that you are running a LiveCD and can't burn an ISO while it is running.

**Shabakthanai** · Jun 25, 2011, 10:16 PM

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

Thanks, my friend. I have another DVDRW in my computer, but it does not run while I am running the Live CD. I don't know why. Can I mount the second DVDRW in my difficult circumstance? Then the Live CD could run the computer and the other DVDRW could burn the SuperGrub2?

It is getting pretty late here, so I will wait a bit, in case this is a possibility, with help of course. Not knowing where you are and how late you are connected, I will wait a half hour. Then I may try your previous solution. I am pretty alert still.

Your kindness is so much appreciated. I wish able to be a better patient.

I just found a scribbled note that I typed and saved because of the terrible penmanship. It relates to this problem and may open a new avenue of thinking.

They are as follows:

/run/udev error on boot, not writable. Falls to /dev/.udev. And next:

KDEInet could not launch /usr/bin/rekonq

I do not know if the additional information changes any thinking, but one can only hope.

**GreyGeek** · Jun 25, 2011, 10:22 PM

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

If you can attach to CDROM's to your PC, and one of them is set to boot from in the BIOS, you can run the LiveCD on the bootable CDROM, and running Kubuntu LiveCD you can use Kb3 to burn the SuperGrub2 iso to the second CDROM. Just select it as the destination of the burn.

**GreyGeek** · Jun 25, 2011, 10:40 PM

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

Originally posted by Shabakthanai

.....
I don't know if having this is important, but my OS is on a 15gb partition and is separate from all other data. Additionally, I have a 20gb swap partition.
...

Snowhog pointed out that your 15gb partition may be full, but I wanted to say that a swap file rarely needs to be more than twice the size of the RAM in your system. The biggest swap file I ever used was only 4GB, and I found that rarely was more than 500Kb ever used, if any was used at all. Mostly it is used when editing large movie files, or gigantic tiff images.

Announcement

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

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

Comment

Comment

Comment

Comment

Comment

Comment

Comment

Comment

Comment

Comment

Comment

Comment

Comment

Comment