problems with fdisk

rfernandez · 03-28-2010, 12:41 PM

@tommylovell

It's because in the past I had a similar problem, and that was the fix for it. I might be wrong as well.

But, one thing is for sure: more than one option is better for the OP.

_Linux_Learner · 03-28-2010, 01:09 PM

Quote:

Originally Posted by tommylovell

hmmm. rfernandez, I'm not sure that is correct. But it certainly wouldn't hurt making your suggested change to the root statement, as I could be wrong. Actually, I'm often wrong.

If that doesn't help, I'd suggest changing it back to (hd0, 5).

'root (hd0,5)' has gotten grub to the Linux kernel and the initial ramdisk.
I think the statement "Than it throws me to a busy box shell with initramfs prompt.." demonstrates that.

I suspect the problem has to do with mounting the root file system and that we're we're past grub problems. Everything in the bootinfoscript output looks good to me.

_Linux_Learner, what were the messages that preceeded "/dev/disk/by-uuid/<uuid of the root partition> does not exist"?

If you do an 'ls -l /dev/disk/by-uuid' at the initramfs prompt, what do you get? Does it show any other disks? Or do you get an error?

Before the initramfs prompt I get the following errors...

Code:

/init: line 194: depmod: not found
/scripts/init-top/usplash: line55: modprobe: not found
/scripts/init-premount/udev:line 24: /sbin/udevd: not found

on running the command...

Code:

s -l /dev/disk/by-uuid

I get no such file or directory found error

Regards
_Linux_Learner

tommylovell · 03-28-2010, 08:56 PM

Here is what I think is going on.

As I said earlier, I think your /boot partition is on /dev/sda6; 'grub' is going there using the 'root (hd0,5)' statement; loading the kernel; the initrd is loaded; the 'init' shell script is then executed. So far, so good.

Then the confusion sets in. On my Ubuntu Netbook Remix (9.10) system, the ramdisk /sbin contains 'depmod', 'modprobe' and 'udevd'. (That's the /sbin in the ramdisk - not the root filesystem's /sbin.) So it's perplexing why those three executables can't be found.

I don't know how the PATH for 'init' is set, but it doesn't seem to be set properly.

Did you have to recreate the grub.conf (menu.lst) file when you repaired the system? I'm not familiar with Ubuntu 9.04, but it seems a little odd that your kernel does not have a version number (i.e. 2.6.28) imbedded in it that matches your initrd. Is it possible they are mismatched?

_Linux_Learner · 03-29-2010, 02:53 AM

Quote:

Originally Posted by tommylovell

Here is what I think is going on.

As I said earlier, I think your /boot partition is on /dev/sda6; 'grub' is going there using the 'root (hd0,5)' statement; loading the kernel; the initrd is loaded; the 'init' shell script is then executed. So far, so good.

Then the confusion sets in. On my Ubuntu Netbook Remix (9.10) system, the ramdisk /sbin contains 'depmod', 'modprobe' and 'udevd'. (That's the /sbin in the ramdisk - not the root filesystem's /sbin.) So it's perplexing why those three executables can't be found.

I don't know how the PATH for 'init' is set, but it doesn't seem to be set properly.

Did you have to recreate the grub.conf (menu.lst) file when you repaired the system? I'm not familiar with Ubuntu 9.04, but it seems a little odd that your kernel does not have a version number (i.e. 2.6.28) imbedded in it that matches your initrd. Is it possible they are mismatched?

Hi thanks for explanation of errors. I created a new initrd image from live cd by mounting /sbin to my file system. And it works now.

The only problem now is on starting it shows an error something like....

Code:

No force chipset ...

After flashing this error it boots well and start working..

How can I remove this now ???

Regards
_Linux_Learner

tommylovell · 03-29-2010, 10:42 AM

Great. I think you are in the home stretch, but you need someone that is Ubuntu literate, and I am not.

But you can try this. Find the newest kernel and initrd files in /boot; create a new Linux entry in grub.conf / menu.lst that points to those files; reboot and select that new entry to boot off of. (If that doesn't work, you still have your old Linux entry to fall back on.)

I suspect that the kernel and initrd that you are running off of probably has fewer features config'd into the kernel. If you go with the normal kernel for your system, I'm hoping that message will go away.

If you don't have a suitable kernel/initrd pair that work, you will probably need to use apt-get (or one of those other Debian based maintenance tools) to force an update or reinstall of the latest kernel and its corresponding initrd; then update your grub.conf / menu.lst file to point to them if that's not done automatically.

If this doesn't work, I think you can open a new post (without incurring any wrath for multiposting), and ask how you can refresh the current kernel and initrd in Ubuntu.

Good luck.