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

[GreyGeek]

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]

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

.....
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.

[Shabakthanai]

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

Dear GreyGeek,

I tried your suggestion. Nonetheless, when I boot holding the shift key down, it finally opens with the same error as before:

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

It appears I will have to try to figure some way to get a CD of SuperGrub2. Amazing, if I had a working system, I could download, make a CD and install the file in less time than it takes to boot the computer. Maybe I can get help at church tomorrow. Thanks for your continued effort, my friend.

[GreyGeek]

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

The left shift key works for me. Perhaps holding the ESC key would open Grub.

IF you have two CDROMS or a CDROM and a USB port you can always
1) Boot the LiveCD and use the "try" mode. When you get a desktop download SuperGrub2.iso and then use K3b to burn SuperGrub2.iso to the OTHER CDROM.

or,

2) Boot the LiveCD in the "try" mode. Use "System --> Disk Creator" to create a bootable LiveUSB. Boot from the LiveUSB. Download the SuperGrub2.iso and use K3b to burn it to your primary CDROM.

[Shabakthanai]

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

Dear SnowHog,

I wish I could look like the GreyGeek; he looks so content. I am so depressed.

A friend brought a copy of SuperGrub2 that I picked up at the church. I immediately booted the CD and got about a dozen or more options to try, the first being to search for an OS.

It could not find an Operating System. I tried each of the other options with a repeating NO for each of them. So I installed Kubuntu Natty 64bit again. But before installing Natty, I had the CD checked for errors. The result was that there were NO errors. I installed the OS then came time to restart the system to set the installation. When the system shut down, I got a fail on the following: 'Starting restore sound card(s') mixer state(s). I removed the Installation CD and clicked enter.

There was an error near the beginning of the boot that changed too fast for me to read, 'udevd (113) /run/udev error on boot, not writable. Falls to /dev/.udev. I believe that is correct, however, it passed too fast for me to read or make the appropriate note. The computer continued to boot to the Login Screen. The cursor was immovable and the keyboard did not respond.

Apparently I am unable to get an installed system set, so that I can repair the grub. Do I have to purchase another computer to get an OS to install? Thanks in advance for any further help you may be willing to provide.

[Snowhog]

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

Not sure that I can offer any advise that may be of any help. That SuperGrub2 could not find a Linux OS on the drive is not good news. You say that you reinstalled Kubuntu Natty 64-bit again. Did that in fact go well - no errors? I'm assuming the answer is 'yes.'

When you reboot, do you get a Grub Menu screen? If you do not, then as the PC is booting, hold the Shift key down for the Grub Menu to appear. When the Grub Menu appears, press the 'e' key to edit the current menu entry. Use your down arrow key to move the cursor to the line that begins with linux /boot/vmlinuz and then use your right-arrow key to move all the way to the end of the line and just past the words 'quiet splash'. Then use your backspace key to remove those two words.

Look at the bottom of the screen for the keys to press to then continue to boot (Ctrl+x I think, but it will tell you). Then note the last message on the screen if you are not presented with the KDM Logon screen.

[Shabakthanai]

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

The left shift key works for me. Perhaps holding the ESC key would open Grub.

Thanks so much for hanging in there. I just tried starting the computer holding the left shift key down through the complete boot process and got the same disappointing results. I then tried booting with the ESC key held down in like manner without success.

IF you have two CDROMS or a CDROM and a USB port you can always
1) Boot the LiveCD and use the "try" mode. When you get a desktop download SuperGrub2.iso and then use K3b to burn SuperGrub2.iso to the OTHER CDROM.

A friend provided the SuperGrub2 Live CD, and I tried that too. Apparently I am unable to restart and set a new installation. After the install, I restart and during the shutdown procedure the process stops to instruct removal of the LiveCD, shutting the CDROM drive door, and hitting Enter. It was at this point that I noticed a 'fail' entry as follows:Starting restore sound card(s') mixer state(s). I do not know the ramifications of that but thought I should mention it. Restart process continued. I got a brief blue screen, then an error message that happens so fast before continuation of the boot process that I am not sure I have an accurate error message, however, I think it is as follows: udevd [113] runtime error on boot, not writable. Falls to /dev/.udev. The screen rapidly continues to the Login Screen. Neither the mouse nor the keyboard function at this point. I am pretty sure that although I completed the installation, it does not get set in the system because of the udev error.

I have yet to have any problem due to sound issues, so the fail doesn't make any sense to me. And although I tested the Live CD to make sure it was error free, and found it error free, I seem to be unable to get a system to install.

In other posts on this issue I mentioned the number of 64bit and 32bit attempts of alternate OS's with the same results. What else can I try? Any ideas?

or,

2) Boot the LiveCD in the "try" mode. Use "System --> Disk Creator" to create a bootable LiveUSB. Boot from the LiveUSB. Download the SuperGrub2.iso and use K3b to burn it to your primary CDROM.

If I understand this statement correctly, you are trying to help me to get the LiveCD for the application SuperGrub2. Since I have that CD now, I won't respond more.

[Shabakthanai]

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

Not sure that I can offer any advise that may be of any help. That SuperGrub2 could not find a Linux OS on the drive is not good news. You say that you reinstalled Kubuntu Natty 64-bit again. Did that in fact go well - no errors? I'm assuming the answer is 'yes.'

When you reboot, do you get a Grub Menu screen? No, If you do not, then as the PC is booting, hold the Shift key down for the Grub Menu to appear. I have done this several times, but a Grub Menu never appears that I can edit. When the Grub Menu appears, press the 'e' key to edit the current menu entry. Use your down arrow key to move the cursor to the line that begins with linux /boot/vmlinuz and then use your right-arrow key to move all the way to the end of the line and just past the words 'quiet splash'. Then use your backspace key to remove those two words.

Look at the bottom of the screen for the keys to press to then continue to boot (Ctrl+x I think, but it will tell you). Then note the last message on the screen if you are not presented with the KDM Logon screen.

Not only not knowledgeable enough, I am baffled that I can get the Live CD to function in the 'Try' mode and not be able to install an OS and get it set into the system. My 15gb root partition is formatted each time I attempt to install an Operating System. Do previous Grub installations remain after the format is finished? I am not sure, however, I don't remember but 2 kernels in my computer. When SnowHog suggested the partition may be full, was he referring to previous Grub or Kernels remaining after an installation of an OS? If the answer is 'yes' can they be removed and allow me to start over fresh with current Grub and Kernel? Can I take some space from my swap partition and add it to the boot partition without negatively affecting the remaining storage partitions on my machine? I could take 5gb from swap and allocate it to the boot partition if that might help, and is doable.

In the past, I have done some foolish things that caused me to have to re-install my OS, but this time, I am completely surprised by what is happening. My RAM memory has been checked for errors and is perfect, installing a new operating system is something I have done numerous time times, and although I am pretty old and inclined to be more forgetful, I do not have surprises when installing manually. I have to, because of how I set up my partitions. They are set up so that I do not lose any data due to an unresolvable Operating System crash. I have to lose the HDD to experience loss.

Is my problem so unusual that I have to purchase another computer? That would be very hard for me at this time.

[Snowhog]

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

May I inquire as to how old the HDD is that you are trying to install to?

When installing, Kubuntu will force a format of the identified root partition, and I have to assume that if there were physical issues with the drive surface, the formatting procedure would throw errors. But your posts indicate that all goes well with the installation, or am I not reading you correctly? As to the LiveCD running fine, that is to be expected - the HDD is not being used.

[GreyGeek]

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

......
There was an error near the beginning of the boot that changed too fast for me to read, 'udevd (113) /run/udev error on boot, not writable. Falls to /dev/.udev.
...

That was just an information message telling you that the OS is going to use /dev/.udev instead of /run/udev. My install of Oneiric gave me that one as well and it runs perfectly.

Apparently I am unable to get an installed system set, so that I can repair the grub. Do I have to purchase another computer to get an OS to install? Thanks in advance for any further help you may be willing to provide.

Snowhog's on to this one. My suspicions are that your HDD has problems.

When you hold the Shift key down to enable the Grub menu to display so that you can run a different option on that menu, there are two reason (that I know of) as to why the Shift key does not work.
1) If the grub menu is set to a delay of zero seconds it won't wait .
2) which doesn't apply to you but here it is any way: you have created a user account for another user (the grandkids, for example, so they don't mess up your account) and you set their account to be an automatic, passwordless login. Grub is set to zero second delay in that circumstance as well.

[Snowhog]

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

GreyGeek@
I don't think either of your scenarious applies, as it 'seems' that Grub isn't being installed at all, if that is the only thing that is going on. This is based on the OP's post that SuperGrub2 reported not finding any (Linux) OS on the HDD.

[Shabakthanai]

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

What should I do, then? And, since I am the weakest link here, and although I am trying to come up to speed with Grub, I still don't have a handle on it. I am studying a tutorial on the subject when there is time lapse between helps from you guys. I am using so much of your and GreyGreek's precious time, I am willing to purchase another HDD, if that will assure success. Still, I keep thinking there is something of value here for others as well as us by solving the problem, rather than shortcutting and buying a drive. Your time is more precious than a $50 TB HDD, however, the solution to my problem my prove more valuable to others. I yield to your judgment, with extreme gratitude for all your help, either way.

[Snowhog]

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

Our time, as well as all the other members here in KFN, is your's for the asking. How much time any of us may provide will of course vary. As to me, I live here.

How old is your HDD? Have you had, or been having, any issues with it prior to this issue? If you have the funds to purchase a replacement HDD, and you don't mind doing so, that of course is up to you. I make no promises that that alone will resolve your current problem.

Should have asked earlier, and maybe you already have provided, but what are the specifications of your PC? Make/model; CPU make (Intel, AMD) - it is 64-bit, yes?; number of HDDs; number of optical drives.

[GreyGeek]

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

GreyGeek@
I don't think either of your scenarious applies, as it 'seems' that Grub isn't being installed at all, if that is the only thing that is going on. This is based on the OP's post that SuperGrub2 reported not finding any (Linux) OS on the HDD.

I could be wrong, but it seems to me that grub has to be there, or there wouldn't be a grub error ending with a grub prompt:

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

To me, what appears to be missing is the correct uuid for the kernel. I'd wager that if he ran a LiveCD he could mount the 15 GB HDD partition containing Kubuntu and browse it, look into/dev/disk/by-uuid/ and see what the correct uuid is, he could then edit /boot/grub/grub.cfg and change the first line that looks like:

linux /boot/vmlinuz-2.6.35-25-generic root=UUID=e069a71d-0e03-408e-9356-48c358172bd4 ro quiet splash hpet=disable quiet splash

but replace the big hex number with what is showing in the HHD's /dev/disk/by-uuid directory.
No?

[Snowhog]

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

I could be wrong, but it seems to me that grub has to be there, or there wouldn't be a grub error ending with a grub prompt:

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

Okay, I'll give you that. But with a clean (re)installation, the root partition gets formatted, and the user doesn't specify the UUID, the installer/Grub picks that up during the installation of Grub. So how can Grub be going to the 'wrong' location? Grub is specified to either be installed in the MBR (default) or a specified partition, if set up ( /boot or /root). If installed to the MBR, then Grub should boot without error. If installed to a partition, then again, booting should be without error. This assumes that Grub is actually getting installed fully and correctly.