Announcement

Collapse
No announcement yet.

system will not boot

Collapse
This topic is closed.
X
X
 
  • Filter
  • Time
  • Show
Clear All
new posts

    system will not boot

    i am trying to reboot my kubuntu system and when it reachs mounting root file system it errors and says


    booting 'ubunu kernel 2.6.25-27-386'

    root (hda0,0)
    filesystem type is ext2fs, partition type 0x83
    kernel /boot/vmlinuz-2.6.15-27-386 root=/dev/hda1 ro quiet splash
    [linux-bzimage, setup=0x1c00, size=0x157860]
    initrd /boot/initrd.img-2.6.15-27-386
    [linux-initrd @ 0x1e8ea000, 0x675882 bytes]
    savedefault
    boot
    uncompressing linux... ok, booting the kernel.
    [17179570.752000] pci: failed to allocate mem resource #6:10000@fc000000 for 0000:01:00.0
    mount: mounting /devhda1 on /root failed: invalid argument
    mount: mounting /root/dev on/dev/.static/dev failed: no such file or directory
    mount:mounting /sys on /root/sys failed: no such file or directory
    mount: mounting /proc on /root/proc failed: no such file or directory
    target filesystem doesnt have /sbin/init


    busybox v1.01 (debian 1:1.01-4ubuntu3) built in shell (ash)
    enter 'help' for a list of built in commands.

    /bin/sh: can't access tty; job control turned off

    im really new at this and would appreciate any help that could bne given

    #2
    Re: system will not boot

    ouch. doesn't look good does it

    A couple of things you could do.

    Run the MemTest. That should rule out that it's not a memory chip gone wacky at least. I doubt that will really give you anything but worth a shot.


    [17179570.752000] pci: failed to allocate mem resource #6:10000@fc000000 for 0000:01:00.0
    Right there seems to be the main problem, at least to me. Need to find out what device that is that is failing. If you have another computer and you can ssh into the problem box then we can find that out.

    If you have a linux box, you probably have SSH built into it. If you have a Windows box and can access the problem Linux box, you can use PuTTy.

    The command to find the problem device is :

    Code:
    lspci | grep 01:00
    This will tell you what the problem device is. Video Card, NIC, whatever. Switching it out might just do the trick.

    Comment

    Working...
    X