UBUNTU upgrade problems - Ubuntu

This is a discussion on UBUNTU upgrade problems - Ubuntu ; I upgraded my UBUNTU system a few months ago and have been living with a problem ever since. I would like to get this fixed if possible, so any help would be appreciated. When the system starts to boot (2.6.24-19-generic) ...

+ Reply to Thread
Results 1 to 14 of 14

Thread: UBUNTU upgrade problems

  1. UBUNTU upgrade problems

    I upgraded my UBUNTU system a few months ago and have been living with a
    problem ever since. I would like to get this fixed if possible, so any
    help would be appreciated.

    When the system starts to boot (2.6.24-19-generic) I get the following
    message, repeated in a loop, using the recover kernel has the same problem).

    (Hopefully I got this correct, I wrote it down and am typing it in, so
    beware of typos)
    (Using xx:xx:xx... because I didn't write down the address)

    The text blow just keeps repeating OVER and OVER again
    "
    Begin: Running /scripts/nfs-premount
    Done.
    nfsmount: need a path
    Begin: Retrying NFS mount
    IP-Config: eth0 hardware address xx:xx:xx:xx:xx:xx mtu 1500 DHCP RARP
    IP-Config: eth0 guessed broadcast address 192.168.0.255
    IP-Config: eth0 Complete (from 192.168.0.1) : address : 192.168.0.103 :
    Net Mask 255.255.255.0
    Gateway: 192.168.0.1 dns: 102.168.0.1 dns1: 0.0.0.0
    Domain : MYNET
    rootserver 192.168.0.1 rootpath:
    filenameL
    nfsmount: need a path
    "

    I was able to boot by going into grum and selecting a different kernel
    "2.6.20-16-generic"

    thanks in advance !
    Joe

  2. Re: UBUNTU upgrade problems

    dada wrote:
    > I upgraded my UBUNTU system a few months ago and have been living with a
    > problem ever since. I would like to get this fixed if possible, so any
    > help would be appreciated.
    >
    > When the system starts to boot (2.6.24-19-generic) I get the following
    > message, repeated in a loop, using the recover kernel has the same
    > problem).
    >
    > (Hopefully I got this correct, I wrote it down and am typing it in, so
    > beware of typos)
    > (Using xx:xx:xx... because I didn't write down the address)
    >
    > The text blow just keeps repeating OVER and OVER again

    *BELOW*
    > "
    > Begin: Running /scripts/nfs-premount
    > Done.
    > nfsmount: need a path
    > Begin: Retrying NFS mount
    > IP-Config: eth0 hardware address xx:xx:xx:xx:xx:xx mtu 1500 DHCP RARP
    > IP-Config: eth0 guessed broadcast address 192.168.0.255
    > IP-Config: eth0 Complete (from 192.168.0.1) : address : 192.168.0.103 :
    > Net Mask 255.255.255.0
    > Gateway: 192.168.0.1 dns: 102.168.0.1 dns1: 0.0.0.0
    > Domain : MYNET
    > rootserver 192.168.0.1 rootpath:
    > filenameL

    filename: (dang fat fingers...)
    > nfsmount: need a path
    > "
    >
    > I was able to boot by going into grum and selecting a different kernel
    > "2.6.20-16-generic"
    >
    > thanks in advance !
    > Joe


  3. Re: UBUNTU upgrade problems

    dada wrote:

    > dada wrote:
    >> I upgraded my UBUNTU system a few months ago and have been living with a
    >> problem ever since. I would like to get this fixed if possible, so any
    >> help would be appreciated.
    >>
    >> When the system starts to boot (2.6.24-19-generic) I get the following
    >> message, repeated in a loop, using the recover kernel has the same
    >> problem).
    >>
    >> (Hopefully I got this correct, I wrote it down and am typing it in, so
    >> beware of typos)
    >> (Using xx:xx:xx... because I didn't write down the address)
    >>
    >> The text blow just keeps repeating OVER and OVER again

    > *BELOW*
    >> "
    >> Begin: Running /scripts/nfs-premount
    >> Done.
    >> nfsmount: need a path
    >> Begin: Retrying NFS mount
    >> IP-Config: eth0 hardware address xx:xx:xx:xx:xx:xx mtu 1500 DHCP RARP
    >> IP-Config: eth0 guessed broadcast address 192.168.0.255
    >> IP-Config: eth0 Complete (from 192.168.0.1) : address : 192.168.0.103 :
    >> Net Mask 255.255.255.0
    >> Gateway: 192.168.0.1 dns: 102.168.0.1 dns1: 0.0.0.0
    >> Domain : MYNET
    >> rootserver 192.168.0.1 rootpath:
    >> filenameL

    > filename: (dang fat fingers...)
    >> nfsmount: need a path
    >> "
    >>
    >> I was able to boot by going into grum and selecting a different kernel
    >> "2.6.20-16-generic"
    >>
    >> thanks in advance !
    >> Joe


    Are you trying to do a NFS mount in your /etc/fstab?

    Cheers.


  4. Re: UBUNTU upgrade problems

    AspireOne_User wrote:
    > dada wrote:
    >
    >> dada wrote:
    >>> I upgraded my UBUNTU system a few months ago and have been living with a
    >>> problem ever since. I would like to get this fixed if possible, so any
    >>> help would be appreciated.
    >>>
    >>> When the system starts to boot (2.6.24-19-generic) I get the following
    >>> message, repeated in a loop, using the recover kernel has the same
    >>> problem).
    >>>
    >>> (Hopefully I got this correct, I wrote it down and am typing it in, so
    >>> beware of typos)
    >>> (Using xx:xx:xx... because I didn't write down the address)
    >>>
    >>> The text blow just keeps repeating OVER and OVER again

    >> *BELOW*
    >>> "
    >>> Begin: Running /scripts/nfs-premount
    >>> Done.
    >>> nfsmount: need a path
    >>> Begin: Retrying NFS mount
    >>> IP-Config: eth0 hardware address xx:xx:xx:xx:xx:xx mtu 1500 DHCP RARP
    >>> IP-Config: eth0 guessed broadcast address 192.168.0.255
    >>> IP-Config: eth0 Complete (from 192.168.0.1) : address : 192.168.0.103 :
    >>> Net Mask 255.255.255.0
    >>> Gateway: 192.168.0.1 dns: 102.168.0.1 dns1: 0.0.0.0
    >>> Domain : MYNET
    >>> rootserver 192.168.0.1 rootpath:
    >>> filenameL

    >> filename: (dang fat fingers...)
    >>> nfsmount: need a path
    >>> "
    >>>
    >>> I was able to boot by going into grum and selecting a different kernel
    >>> "2.6.20-16-generic"
    >>>
    >>> thanks in advance !
    >>> Joe

    >
    > Are you trying to do a NFS mount in your /etc/fstab?
    >

    No there is just "normal" stuff there

    # /etc/fstab: static file system information.
    #
    #
    proc /proc proc defaults 0 0
    # /dev/sda1
    UUID=6bb2f238-2a89-46cf-a7f3-6aa302619135 / ext3
    defaults,errors=remount-ro 0 1
    # /dev/sda5
    UUID=c09a798d-32b1-471f-9df4-eb2da13923d2 none swap sw
    0 0
    /dev/hda /media/cdrom0 udf,iso9660 user,noauto 0 0
    ~

    ~
    > Cheers.
    >

    Thanks ... Any other ideas ?

  5. Re: UBUNTU upgrade problems

    dada wrote:

    > AspireOne_User wrote:
    >> dada wrote:
    >>
    >>> dada wrote:
    >>>> I upgraded my UBUNTU system a few months ago and have been living with
    >>>> a problem ever since. I would like to get this fixed if possible, so
    >>>> any help would be appreciated.
    >>>>
    >>>> When the system starts to boot (2.6.24-19-generic) I get the following
    >>>> message, repeated in a loop, using the recover kernel has the same
    >>>> problem).
    >>>>
    >>>> (Hopefully I got this correct, I wrote it down and am typing it in, so
    >>>> beware of typos)
    >>>> (Using xx:xx:xx... because I didn't write down the address)
    >>>>
    >>>> The text blow just keeps repeating OVER and OVER again
    >>> *BELOW*
    >>>> "
    >>>> Begin: Running /scripts/nfs-premount
    >>>> Done.
    >>>> nfsmount: need a path
    >>>> Begin: Retrying NFS mount
    >>>> IP-Config: eth0 hardware address xx:xx:xx:xx:xx:xx mtu 1500 DHCP RARP
    >>>> IP-Config: eth0 guessed broadcast address 192.168.0.255
    >>>> IP-Config: eth0 Complete (from 192.168.0.1) : address : 192.168.0.103 :
    >>>> Net Mask 255.255.255.0
    >>>> Gateway: 192.168.0.1 dns: 102.168.0.1 dns1: 0.0.0.0
    >>>> Domain : MYNET
    >>>> rootserver 192.168.0.1 rootpath:
    >>>> filenameL
    >>> filename: (dang fat fingers...)
    >>>> nfsmount: need a path
    >>>> "
    >>>>
    >>>> I was able to boot by going into grum and selecting a different kernel
    >>>> "2.6.20-16-generic"
    >>>>
    >>>> thanks in advance !
    >>>> Joe

    >>
    >> Are you trying to do a NFS mount in your /etc/fstab?
    >>

    > No there is just "normal" stuff there
    >
    > # /etc/fstab: static file system information.
    > #
    > #
    > proc /proc proc defaults 0 0
    > # /dev/sda1
    > UUID=6bb2f238-2a89-46cf-a7f3-6aa302619135 / ext3
    > defaults,errors=remount-ro 0 1
    > # /dev/sda5
    > UUID=c09a798d-32b1-471f-9df4-eb2da13923d2 none swap sw
    > 0 0
    > /dev/hda /media/cdrom0 udf,iso9660 user,noauto 0 0
    > ~
    >
    > ~
    >> Cheers.
    >>

    > Thanks ... Any other ideas ?


    Post your /boot/grub/menu.lst

    Cheers.

    --
    The world can't afford the rich.


  6. Re: UBUNTU upgrade problems

    NoStop wrote:
    > dada wrote:
    >
    >> AspireOne_User wrote:
    >>> dada wrote:
    >>>
    >>>> dada wrote:
    >>>>> I upgraded my UBUNTU system a few months ago and have been living with
    >>>>> a problem ever since. I would like to get this fixed if possible, so
    >>>>> any help would be appreciated.
    >>>>>
    >>>>> When the system starts to boot (2.6.24-19-generic) I get the following
    >>>>> message, repeated in a loop, using the recover kernel has the same
    >>>>> problem).
    >>>>>
    >>>>> (Hopefully I got this correct, I wrote it down and am typing it in, so
    >>>>> beware of typos)
    >>>>> (Using xx:xx:xx... because I didn't write down the address)
    >>>>>
    >>>>> The text blow just keeps repeating OVER and OVER again
    >>>> *BELOW*
    >>>>> "
    >>>>> Begin: Running /scripts/nfs-premount
    >>>>> Done.
    >>>>> nfsmount: need a path
    >>>>> Begin: Retrying NFS mount
    >>>>> IP-Config: eth0 hardware address xx:xx:xx:xx:xx:xx mtu 1500 DHCP RARP
    >>>>> IP-Config: eth0 guessed broadcast address 192.168.0.255
    >>>>> IP-Config: eth0 Complete (from 192.168.0.1) : address : 192.168.0.103 :
    >>>>> Net Mask 255.255.255.0
    >>>>> Gateway: 192.168.0.1 dns: 102.168.0.1 dns1: 0.0.0.0
    >>>>> Domain : MYNET
    >>>>> rootserver 192.168.0.1 rootpath:
    >>>>> filenameL
    >>>> filename: (dang fat fingers...)
    >>>>> nfsmount: need a path
    >>>>> "
    >>>>>
    >>>>> I was able to boot by going into grum and selecting a different kernel
    >>>>> "2.6.20-16-generic"
    >>>>>
    >>>>> thanks in advance !
    >>>>> Joe
    >>> Are you trying to do a NFS mount in your /etc/fstab?
    >>>

    >> No there is just "normal" stuff there
    >>
    >> # /etc/fstab: static file system information.
    >> #
    >> #
    >> proc /proc proc defaults 0 0
    >> # /dev/sda1
    >> UUID=6bb2f238-2a89-46cf-a7f3-6aa302619135 / ext3
    >> defaults,errors=remount-ro 0 1
    >> # /dev/sda5
    >> UUID=c09a798d-32b1-471f-9df4-eb2da13923d2 none swap sw
    >> 0 0
    >> /dev/hda /media/cdrom0 udf,iso9660 user,noauto 0 0
    >> ~
    >>
    >> ~
    >>> Cheers.
    >>>

    >> Thanks ... Any other ideas ?

    >
    > Post your /boot/grub/menu.lst
    >
    > Cheers.
    >


    OK, I attached it ... does it help diagnose the problem ?

    Thanks !
    Joe

    # menu.lst - See: grub(8), info grub, update-grub(8)
    # grub-install(8), grub-floppy(8),
    # grub-md5-crypt, /usr/share/doc/grub
    # and /usr/share/doc/grub-doc/.

    ## default num
    # Set the default entry to the entry number NUM. Numbering starts from 0, and
    # the entry number 0 is the default if the command is not used.
    #
    # You can specify 'saved' instead of a number. In this case, the default entry
    # is the entry saved with the command 'savedefault'.
    # WARNING: If you are using dmraid do not change this entry to 'saved' or your
    # array will desync and will not let you boot your system.
    default 0

    ## timeout sec
    # Set a timeout, in SEC seconds, before automatically booting the default entry
    # (normally the first entry defined).
    timeout 3

    ## hiddenmenu
    # Hides the menu by default (press ESC to see the menu)
    hiddenmenu

    # Pretty colours
    #color cyan/blue white/blue

    ## password ['--md5'] passwd
    # If used in the first section of a menu file, disable all interactive editing
    # control (menu entry editor and command-line) and entries protected by the
    # command 'lock'
    # e.g. password topsecret
    # password --md5 $1$gLhU0/$aW78kHK1QfV3P2b2znUoe/
    # password topsecret

    #
    # examples
    #
    # title Windows 95/98/NT/2000
    # root (hd0,0)
    # makeactive
    # chainloader +1
    #
    # title Linux
    # root (hd0,1)
    # kernel /vmlinuz root=/dev/hda2 ro
    #

    #
    # Put static boot stanzas before and/or after AUTOMAGIC KERNEL LIST

    ### BEGIN AUTOMAGIC KERNELS LIST
    ## lines between the AUTOMAGIC KERNELS LIST markers will be modified
    ## by the debian update-grub script except for the default options below

    ## DO NOT UNCOMMENT THEM, Just edit them to your needs

    ## ## Start Default Options ##
    ## default kernel options
    ## default kernel options for automagic boot options
    ## If you want special options for specific kernels use kopt_x_y_z
    ## where x.y.z is kernel version. Minor versions can be omitted.
    ## e.g. kopt=root=/dev/hda1 ro
    ## kopt_2_6_8=root=/dev/hdc1 ro
    ## kopt_2_6_8_2_686=root=/dev/hdc2 ro
    # kopt=root=UUID=6bb2f238-2a89-46cf-a7f3-6aa302619135 ro

    ## Setup crashdump menu entries
    ## e.g. crashdump=1
    # crashdump=0

    ## default grub root device
    ## e.g. groot=(hd0,0)
    # groot=(hd0,0)

    ## should update-grub create alternative automagic boot options
    ## e.g. alternative=true
    ## alternative=false
    # alternative=true

    ## should update-grub lock alternative automagic boot options
    ## e.g. lockalternative=true
    ## lockalternative=false
    # lockalternative=false

    ## additional options to use with the default boot option, but not with the
    ## alternatives
    ## e.g. defoptions=vga=791 resume=/dev/hda5
    # defoptions=quiet splash

    ## should update-grub lock old automagic boot options
    ## e.g. lockold=false
    ## lockold=true
    # lockold=false

    ## Xen hypervisor options to use with the default Xen boot option
    # xenhopt=

    ## Xen Linux kernel options to use with the default Xen boot option
    # xenkopt=console=tty0

    ## altoption boot targets option
    ## multiple altoptions lines are allowed
    ## e.g. altoptions=(extra menu suffix) extra boot options
    ## altoptions=(recovery) single
    # altoptions=(recovery mode) single

    ## controls how many kernels should be put into the menu.lst
    ## only counts the first occurence of a kernel, not the
    ## alternative kernel options
    ## e.g. howmany=all
    ## howmany=7
    # howmany=all

    ## should update-grub create memtest86 boot option
    ## e.g. memtest86=true
    ## memtest86=false
    # memtest86=true

    ## should update-grub adjust the value of the default booted system
    ## can be true or false
    # updatedefaultentry=false

    ## should update-grub add savedefault to the default options
    ## can be true or false
    # savedefault=false

    ## ## End Default Options ##

    title Ubuntu 8.04.1, kernel 2.6.24-19-generic
    root (hd0,0)
    kernel /boot/vmlinuz-2.6.24-19-generic root=UUID=6bb2f238-2a89-46cf-a7f3-6aa302619135 ro quiet splash
    initrd /boot/initrd.img-2.6.24-19-generic
    quiet

    title Ubuntu 8.04.1, kernel 2.6.24-19-generic (recovery mode)
    root (hd0,0)
    kernel /boot/vmlinuz-2.6.24-19-generic root=UUID=6bb2f238-2a89-46cf-a7f3-6aa302619135 ro single
    initrd /boot/initrd.img-2.6.24-19-generic

    title Ubuntu 8.04.1, kernel 2.6.24-16-generic
    root (hd0,0)
    kernel /boot/vmlinuz-2.6.24-16-generic root=UUID=6bb2f238-2a89-46cf-a7f3-6aa302619135 ro quiet splash
    initrd /boot/initrd.img-2.6.24-16-generic
    quiet

    title Ubuntu 8.04.1, kernel 2.6.24-16-generic (recovery mode)
    root (hd0,0)
    kernel /boot/vmlinuz-2.6.24-16-generic root=UUID=6bb2f238-2a89-46cf-a7f3-6aa302619135 ro single
    initrd /boot/initrd.img-2.6.24-16-generic

    title Ubuntu 8.04.1, kernel 2.6.22-14-generic
    root (hd0,0)
    kernel /boot/vmlinuz-2.6.22-14-generic root=UUID=6bb2f238-2a89-46cf-a7f3-6aa302619135 ro quiet splash
    initrd /boot/initrd.img-2.6.22-14-generic
    quiet

    title Ubuntu 8.04.1, kernel 2.6.22-14-generic (recovery mode)
    root (hd0,0)
    kernel /boot/vmlinuz-2.6.22-14-generic root=UUID=6bb2f238-2a89-46cf-a7f3-6aa302619135 ro single
    initrd /boot/initrd.img-2.6.22-14-generic

    title Ubuntu 8.04.1, kernel 2.6.20-16-generic
    root (hd0,0)
    kernel /boot/vmlinuz-2.6.20-16-generic root=UUID=6bb2f238-2a89-46cf-a7f3-6aa302619135 ro quiet splash
    initrd /boot/initrd.img-2.6.20-16-generic
    quiet

    title Ubuntu 8.04.1, kernel 2.6.20-16-generic (recovery mode)
    root (hd0,0)
    kernel /boot/vmlinuz-2.6.20-16-generic root=UUID=6bb2f238-2a89-46cf-a7f3-6aa302619135 ro single
    initrd /boot/initrd.img-2.6.20-16-generic

    title Ubuntu 8.04.1, memtest86+
    root (hd0,0)
    kernel /boot/memtest86+.bin
    quiet

    ### END DEBIAN AUTOMAGIC KERNELS LIST


  7. Re: UBUNTU upgrade problems

    dada wrote:

    > NoStop wrote:
    >> dada wrote:
    >>
    >>> AspireOne_User wrote:
    >>>> dada wrote:
    >>>>
    >>>>> dada wrote:
    >>>>>> I upgraded my UBUNTU system a few months ago and have been living
    >>>>>> with a problem ever since. I would like to get this fixed if
    >>>>>> possible, so any help would be appreciated.
    >>>>>>
    >>>>>> When the system starts to boot (2.6.24-19-generic) I get the
    >>>>>> following message, repeated in a loop, using the recover kernel has
    >>>>>> the same problem).
    >>>>>>
    >>>>>> (Hopefully I got this correct, I wrote it down and am typing it in,
    >>>>>> so beware of typos)
    >>>>>> (Using xx:xx:xx... because I didn't write down the address)
    >>>>>>
    >>>>>> The text blow just keeps repeating OVER and OVER again
    >>>>> *BELOW*
    >>>>>> "
    >>>>>> Begin: Running /scripts/nfs-premount
    >>>>>> Done.
    >>>>>> nfsmount: need a path
    >>>>>> Begin: Retrying NFS mount
    >>>>>> IP-Config: eth0 hardware address xx:xx:xx:xx:xx:xx mtu 1500 DHCP RARP
    >>>>>> IP-Config: eth0 guessed broadcast address 192.168.0.255
    >>>>>> IP-Config: eth0 Complete (from 192.168.0.1) : address : 192.168.0.103
    >>>>>> : Net Mask 255.255.255.0
    >>>>>> Gateway: 192.168.0.1 dns: 102.168.0.1 dns1: 0.0.0.0
    >>>>>> Domain : MYNET
    >>>>>> rootserver 192.168.0.1 rootpath:
    >>>>>> filenameL
    >>>>> filename: (dang fat fingers...)
    >>>>>> nfsmount: need a path
    >>>>>> "
    >>>>>>
    >>>>>> I was able to boot by going into grum and selecting a different
    >>>>>> kernel
    >>>>>> "2.6.20-16-generic"
    >>>>>>
    >>>>>> thanks in advance !
    >>>>>> Joe
    >>>> Are you trying to do a NFS mount in your /etc/fstab?
    >>>>
    >>> No there is just "normal" stuff there
    >>>
    >>> # /etc/fstab: static file system information.
    >>> #
    >>> #
    >>> proc /proc proc defaults 0 0
    >>> # /dev/sda1
    >>> UUID=6bb2f238-2a89-46cf-a7f3-6aa302619135 / ext3
    >>> defaults,errors=remount-ro 0 1
    >>> # /dev/sda5
    >>> UUID=c09a798d-32b1-471f-9df4-eb2da13923d2 none swap sw
    >>> 0 0
    >>> /dev/hda /media/cdrom0 udf,iso9660 user,noauto 0 0
    >>> ~
    >>>
    >>> ~
    >>>> Cheers.
    >>>>
    >>> Thanks ... Any other ideas ?

    >>
    >> Post your /boot/grub/menu.lst
    >>
    >> Cheers.
    >>

    >
    > OK, I attached it ... does it help diagnose the problem ?
    >
    > Thanks !
    > Joe


    I was just wondering if there was a switch being used on the kernel lines
    for the newer kernels that are different from what is being used on the
    kernel that works for you. I see no changes there. Please post the contents
    of:

    /usr/share/initramfs-tools/init

    I'm not sure that I have an answer for you, but that's the script that will
    run to setup things and determine if it should boot from nfs or not.
    Possibly there's a prob (corruption) with it. Why an older kernel should
    boot without probs and not the newer ones is strange, if no one else is
    reporting such problems.

    Cheers

    --
    The world can't afford the rich.


  8. Re: UBUNTU upgrade problems

    dada wrote:

    > NoStop wrote:
    >> dada wrote:
    >>
    >>> AspireOne_User wrote:
    >>>> dada wrote:
    >>>>
    >>>>> dada wrote:
    >>>>>> I upgraded my UBUNTU system a few months ago and have been living
    >>>>>> with a problem ever since. I would like to get this fixed if
    >>>>>> possible, so any help would be appreciated.
    >>>>>>
    >>>>>> When the system starts to boot (2.6.24-19-generic) I get the
    >>>>>> following message, repeated in a loop, using the recover kernel has
    >>>>>> the same problem).
    >>>>>>
    >>>>>> (Hopefully I got this correct, I wrote it down and am typing it in,
    >>>>>> so beware of typos)
    >>>>>> (Using xx:xx:xx... because I didn't write down the address)
    >>>>>>
    >>>>>> The text blow just keeps repeating OVER and OVER again
    >>>>> *BELOW*
    >>>>>> "
    >>>>>> Begin: Running /scripts/nfs-premount
    >>>>>> Done.
    >>>>>> nfsmount: need a path
    >>>>>> Begin: Retrying NFS mount
    >>>>>> IP-Config: eth0 hardware address xx:xx:xx:xx:xx:xx mtu 1500 DHCP RARP
    >>>>>> IP-Config: eth0 guessed broadcast address 192.168.0.255
    >>>>>> IP-Config: eth0 Complete (from 192.168.0.1) : address : 192.168.0.103
    >>>>>> : Net Mask 255.255.255.0
    >>>>>> Gateway: 192.168.0.1 dns: 102.168.0.1 dns1: 0.0.0.0
    >>>>>> Domain : MYNET
    >>>>>> rootserver 192.168.0.1 rootpath:
    >>>>>> filenameL
    >>>>> filename: (dang fat fingers...)
    >>>>>> nfsmount: need a path
    >>>>>> "
    >>>>>>
    >>>>>> I was able to boot by going into grum and selecting a different
    >>>>>> kernel
    >>>>>> "2.6.20-16-generic"
    >>>>>>
    >>>>>> thanks in advance !
    >>>>>> Joe
    >>>> Are you trying to do a NFS mount in your /etc/fstab?
    >>>>
    >>> No there is just "normal" stuff there
    >>>
    >>> # /etc/fstab: static file system information.
    >>> #
    >>> #
    >>> proc /proc proc defaults 0 0
    >>> # /dev/sda1
    >>> UUID=6bb2f238-2a89-46cf-a7f3-6aa302619135 / ext3
    >>> defaults,errors=remount-ro 0 1
    >>> # /dev/sda5
    >>> UUID=c09a798d-32b1-471f-9df4-eb2da13923d2 none swap sw
    >>> 0 0
    >>> /dev/hda /media/cdrom0 udf,iso9660 user,noauto 0 0
    >>> ~
    >>>
    >>> ~
    >>>> Cheers.
    >>>>
    >>> Thanks ... Any other ideas ?

    >>
    >> Post your /boot/grub/menu.lst
    >>
    >> Cheers.
    >>

    >
    > OK, I attached it ... does it help diagnose the problem ?
    >
    > Thanks !
    > Joe


    Also do this and post results:

    cd /boot
    ls -l

    Thanks

    Cheers.

    --
    The world can't afford the rich.


  9. Re: UBUNTU upgrade problems

    dada wrote:

    > AspireOne_User wrote:
    >> dada wrote:
    >>
    >>> dada wrote:
    >>>> I upgraded my UBUNTU system a few months ago and have been living with
    >>>> a problem ever since. I would like to get this fixed if possible, so
    >>>> any help would be appreciated.
    >>>>
    >>>> When the system starts to boot (2.6.24-19-generic) I get the following
    >>>> message, repeated in a loop, using the recover kernel has the same
    >>>> problem).
    >>>>
    >>>> (Hopefully I got this correct, I wrote it down and am typing it in, so
    >>>> beware of typos)
    >>>> (Using xx:xx:xx... because I didn't write down the address)
    >>>>
    >>>> The text blow just keeps repeating OVER and OVER again
    >>> *BELOW*
    >>>> "
    >>>> Begin: Running /scripts/nfs-premount
    >>>> Done.
    >>>> nfsmount: need a path
    >>>> Begin: Retrying NFS mount
    >>>> IP-Config: eth0 hardware address xx:xx:xx:xx:xx:xx mtu 1500 DHCP RARP
    >>>> IP-Config: eth0 guessed broadcast address 192.168.0.255
    >>>> IP-Config: eth0 Complete (from 192.168.0.1) : address : 192.168.0.103 :
    >>>> Net Mask 255.255.255.0
    >>>> Gateway: 192.168.0.1 dns: 102.168.0.1 dns1: 0.0.0.0
    >>>> Domain : MYNET
    >>>> rootserver 192.168.0.1 rootpath:
    >>>> filenameL
    >>> filename: (dang fat fingers...)
    >>>> nfsmount: need a path
    >>>> "
    >>>>
    >>>> I was able to boot by going into grum and selecting a different kernel
    >>>> "2.6.20-16-generic"
    >>>>
    >>>> thanks in advance !
    >>>> Joe

    >>
    >> Are you trying to do a NFS mount in your /etc/fstab?
    >>

    > No there is just "normal" stuff there
    >
    > # /etc/fstab: static file system information.
    > #
    > #
    > proc /proc proc defaults 0 0
    > # /dev/sda1
    > UUID=6bb2f238-2a89-46cf-a7f3-6aa302619135 / ext3
    > defaults,errors=remount-ro 0 1
    > # /dev/sda5
    > UUID=c09a798d-32b1-471f-9df4-eb2da13923d2 none swap sw
    > 0 0
    > /dev/hda /media/cdrom0 udf,iso9660 user,noauto 0 0
    > ~
    >
    > ~
    >> Cheers.
    >>

    > Thanks ... Any other ideas ?


    OK, here's a final thought on how to maybe correct this situation. Get into
    Ubuntu using the kernel that works. Then go into Synaptic and find the
    kernel that isn't working and do a re-install of that kernel.

    Maybe that will fix it and you'll be able to run the latest kernel?

    Cheers.

    --
    The world can't afford the rich.


  10. Re: UBUNTU upgrade problems

    NoStop wrote:
    > dada wrote:
    >
    >> NoStop wrote:
    >>> dada wrote:
    >>>
    >>>> AspireOne_User wrote:
    >>>>> dada wrote:
    >>>>>
    >>>>>> dada wrote:
    >>>>>>> I upgraded my UBUNTU system a few months ago and have been living
    >>>>>>> with a problem ever since. I would like to get this fixed if
    >>>>>>> possible, so any help would be appreciated.
    >>>>>>>
    >>>>>>> When the system starts to boot (2.6.24-19-generic) I get the
    >>>>>>> following message, repeated in a loop, using the recover kernel has
    >>>>>>> the same problem).
    >>>>>>>
    >>>>>>> (Hopefully I got this correct, I wrote it down and am typing it in,
    >>>>>>> so beware of typos)
    >>>>>>> (Using xx:xx:xx... because I didn't write down the address)
    >>>>>>>
    >>>>>>> The text blow just keeps repeating OVER and OVER again
    >>>>>> *BELOW*
    >>>>>>> "
    >>>>>>> Begin: Running /scripts/nfs-premount
    >>>>>>> Done.
    >>>>>>> nfsmount: need a path
    >>>>>>> Begin: Retrying NFS mount
    >>>>>>> IP-Config: eth0 hardware address xx:xx:xx:xx:xx:xx mtu 1500 DHCP RARP
    >>>>>>> IP-Config: eth0 guessed broadcast address 192.168.0.255
    >>>>>>> IP-Config: eth0 Complete (from 192.168.0.1) : address : 192.168.0.103
    >>>>>>> : Net Mask 255.255.255.0
    >>>>>>> Gateway: 192.168.0.1 dns: 102.168.0.1 dns1: 0.0.0.0
    >>>>>>> Domain : MYNET
    >>>>>>> rootserver 192.168.0.1 rootpath:
    >>>>>>> filenameL
    >>>>>> filename: (dang fat fingers...)
    >>>>>>> nfsmount: need a path
    >>>>>>> "
    >>>>>>>
    >>>>>>> I was able to boot by going into grum and selecting a different
    >>>>>>> kernel
    >>>>>>> "2.6.20-16-generic"
    >>>>>>>
    >>>>>>> thanks in advance !
    >>>>>>> Joe
    >>>>> Are you trying to do a NFS mount in your /etc/fstab?
    >>>>>
    >>>> No there is just "normal" stuff there
    >>>>
    >>>> # /etc/fstab: static file system information.
    >>>> #
    >>>> #
    >>>> proc /proc proc defaults 0 0
    >>>> # /dev/sda1
    >>>> UUID=6bb2f238-2a89-46cf-a7f3-6aa302619135 / ext3
    >>>> defaults,errors=remount-ro 0 1
    >>>> # /dev/sda5
    >>>> UUID=c09a798d-32b1-471f-9df4-eb2da13923d2 none swap sw
    >>>> 0 0
    >>>> /dev/hda /media/cdrom0 udf,iso9660 user,noauto 0 0
    >>>> ~
    >>>>
    >>>> ~
    >>>>> Cheers.
    >>>>>
    >>>> Thanks ... Any other ideas ?
    >>> Post your /boot/grub/menu.lst
    >>>
    >>> Cheers.
    >>>

    >> OK, I attached it ... does it help diagnose the problem ?
    >>
    >> Thanks !
    >> Joe

    >
    > Also do this and post results:
    >
    > cd /boot
    > ls -l
    >
    > Thanks
    >
    > Cheers.
    >


    Hope this helps.

    Note : as you can see in the GRUB menu list I have tried to upgrade a
    couple of times, always getting the same results on bootup. The original
    kernel continues to work.

    Thanks for looking at this.

    Joe

    #!/bin/sh

    echo "Loading, please wait..."

    [ -d /dev ] || mkdir -m 0755 /dev
    [ -d /root ] || mkdir --mode=0700 /root
    [ -d /sys ] || mkdir /sys
    [ -d /proc ] || mkdir /proc
    [ -d /tmp ] || mkdir /tmp
    mkdir -p /var/lock
    mount -t sysfs none /sys -onodev,noexec,nosuid
    mount -t proc none /proc -onodev,noexec,nosuid

    # Note that this only becomes /dev on the real filesystem if udev's scripts
    # are used; which they will be, but it's worth pointing out
    mount -t tmpfs -o mode=0755 udev /dev
    [ -e /dev/console ] || mknod /dev/console c 5 1
    [ -e /dev/null ] || mknod /dev/null c 1 3
    > /dev/.initramfs-tools

    mkdir /dev/.initramfs

    # Export the dpkg architecture
    export DPKG_ARCH=
    .. /conf/arch.conf

    # Export it for root hardcoding
    export ROOT=

    # Bring in the main config
    .. /conf/initramfs.conf
    for i in conf/conf.d/*; do
    [ -f ${i} ] && . ${i}
    done
    .. /scripts/functions

    # Parse command line options
    export break=
    export init=/sbin/init
    export quiet=n
    export readonly=y
    export rootmnt=/root
    export debug=
    export cryptopts=${CRYPTOPTS}
    export panic

    for x in $(cat /proc/cmdline); do
    case $x in
    init=*)
    init=${x#init=}
    ;;
    root=*)
    ROOT=${x#root=}
    case $ROOT in
    LABEL=*)
    ROOT="/dev/disk/by-label/${ROOT#LABEL=}"
    ;;
    UUID=*)
    ROOT="/dev/disk/by-uuid/${ROOT#UUID=}"
    ;;
    /dev/nfs)
    BOOT=nfs
    ;;
    esac
    ;;
    rootflags=*)
    ROOTFLAGS="-o ${x#rootflags=}"
    ;;
    rootfstype=*)
    ROOTFSTYPE="${x#rootfstype=}"
    ;;
    rootdelay=*)
    ROOTDELAY="${x#rootdelay=}"
    ;;
    resumedelay=*)
    RESUMEDELAY="${x#resumedelay=}"
    ;;
    loop=*)
    LOOP="${x#loop=}"
    ;;
    loopflags=*)
    LOOPFLAGS="-o ${x#loopflags=}"
    ;;
    loopfstype=*)
    LOOPFSTYPE="${x#loopfstype=}"
    ;;
    cryptopts=*)
    cryptopts="${x#cryptopts=}"
    ;;
    nfsroot=*)
    NFSROOT="${x#nfsroot=}"
    ;;
    netboot=*)
    NETBOOT="${x#netboot=}"
    ;;
    ip=*)
    IPOPTS="${x#ip=}"
    ;;
    boot=*)
    BOOT=${x#boot=}
    ;;
    resume=*)
    RESUME="${x#resume=}"
    ;;
    noresume)
    NORESUME=y
    ;;
    panic=*)
    panic="${x#panic=}"
    ;;
    quiet)
    quiet=y
    ;;
    ro)
    readonly=y
    ;;
    rw)
    readonly=n
    ;;
    debug)
    debug=y
    exec >/tmp/initramfs.debug 2>&1
    set -x
    ;;
    debug=*)
    debug=y
    set -x
    ;;
    break=*)
    break=${x#break=}
    ;;
    break)
    break=premount
    ;;
    esac
    done

    if [ -z "${NORESUME}" ]; then
    export resume=${RESUME}
    fi

    depmod -a
    maybe_break top

    # Don't do log messages here to avoid confusing usplash
    run_scripts /scripts/init-top

    maybe_break modules
    log_begin_msg "Loading essential drivers..."
    load_modules
    log_end_msg

    maybe_break premount
    [ "$quiet" != "y" ] && log_begin_msg "Running /scripts/init-premount"
    run_scripts /scripts/init-premount
    [ "$quiet" != "y" ] && log_end_msg

    maybe_break mount
    log_begin_msg "Mounting root file system..."
    .. /scripts/${BOOT}
    parse_numeric ${ROOT}
    mountroot
    log_end_msg

    maybe_break bottom
    [ "$quiet" != "y" ] && log_begin_msg "Running /scripts/init-bottom"
    run_scripts /scripts/init-bottom
    [ "$quiet" != "y" ] && log_end_msg

    # Move virtual filesystems over to the real filesystem
    mount -n -o move /sys ${rootmnt}/sys
    mount -n -o move /proc ${rootmnt}/proc

    while [ ! -x ${rootmnt}${init} ]; do
    panic "Target filesystem doesn't have ${init}"
    done

    # Confuses /etc/init.d/rc
    if [ -n ${debug} ]; then
    unset debug
    fi

    # Chain to real filesystem
    maybe_break init
    exec run-init ${rootmnt} ${init} "$@" <${rootmnt}/dev/console >${rootmnt}/dev/console 2>&1

    total 77884
    -rw-r--r-- 1 root root 407163 2007-09-23 14:42 abi-2.6.20-16-generic
    -rw-r--r-- 1 root root 417807 2008-02-11 23:30 abi-2.6.22-14-generic
    -rw-r--r-- 1 root root 420164 2008-04-10 11:12 abi-2.6.24-16-generic
    -rw-r--r-- 1 root root 420224 2008-08-20 18:15 abi-2.6.24-19-generic
    -rw-r--r-- 1 root root 75332 2007-09-23 13:16 config-2.6.20-16-generic
    -rw-r--r-- 1 root root 67666 2008-02-11 23:30 config-2.6.22-14-generic
    -rw-r--r-- 1 root root 74079 2008-04-10 11:12 config-2.6.24-16-generic
    -rw-r--r-- 1 root root 74164 2008-08-20 18:15 config-2.6.24-19-generic
    drwxr-xr-x 2 root root 4096 2008-09-13 20:51 grub
    -rw------- 1 root root 1306033 2008-03-02 13:47 initrd.img-
    -rw-r--r-- 1 root root 7507407 2007-11-06 20:49 initrd.img-2.6.20-16-generic
    -rw-r--r-- 1 root root 7507679 2007-09-26 20:02 initrd.img-2.6.20-16-generic.bak
    -rw-r--r-- 1 root root 7981048 2008-03-02 13:31 initrd.img-2.6.22-14-generic
    -rw-r--r-- 1 root root 7981065 2008-02-21 22:01 initrd.img-2.6.22-14-generic.bak
    -rw-r--r-- 1 root root 8364076 2008-05-17 08:52 initrd.img-2.6.24-16-generic
    -rw-r--r-- 1 root root 8364342 2008-05-17 08:49 initrd.img-2.6.24-16-generic.bak
    -rw-r--r-- 1 root root 8404416 2008-09-13 20:55 initrd.img-2.6.24-19-generic
    -rw-r--r-- 1 root root 8404337 2008-09-13 20:51 initrd.img-2.6.24-19-generic.bak
    -rw-r--r-- 1 root root 103204 2007-09-28 07:03 memtest86+.bin
    -rw-r--r-- 1 root root 1033618 2007-09-23 14:43 System.map-2.6.20-16-generic
    -rw-r--r-- 1 root root 1052627 2008-02-11 23:30 System.map-2.6.22-14-generic
    -rw-r--r-- 1 root root 1145670 2008-04-10 11:12 System.map-2.6.24-16-generic
    -rw-r--r-- 1 root root 1152364 2008-08-20 18:15 System.map-2.6.24-19-generic
    -rw-r--r-- 1 root root 1725110 2007-09-23 14:42 vmlinuz-2.6.20-16-generic
    -rw-r--r-- 1 root root 1743752 2008-02-11 23:30 vmlinuz-2.6.22-14-generic
    -rw-r--r-- 1 root root 1887736 2008-04-10 11:12 vmlinuz-2.6.24-16-generic
    -rw-r--r-- 1 root root 1903096 2008-08-20 18:15 vmlinuz-2.6.24-19-generic


  11. Re: UBUNTU upgrade problems

    dada wrote:

    > NoStop wrote:
    >> dada wrote:
    >>
    >>> NoStop wrote:
    >>>> dada wrote:
    >>>>
    >>>>> AspireOne_User wrote:
    >>>>>> dada wrote:
    >>>>>>
    >>>>>>> dada wrote:
    >>>>>>>> I upgraded my UBUNTU system a few months ago and have been living
    >>>>>>>> with a problem ever since. I would like to get this fixed if
    >>>>>>>> possible, so any help would be appreciated.
    >>>>>>>>
    >>>>>>>> When the system starts to boot (2.6.24-19-generic) I get the
    >>>>>>>> following message, repeated in a loop, using the recover kernel has
    >>>>>>>> the same problem).
    >>>>>>>>
    >>>>>>>> (Hopefully I got this correct, I wrote it down and am typing it in,
    >>>>>>>> so beware of typos)
    >>>>>>>> (Using xx:xx:xx... because I didn't write down the address)
    >>>>>>>>
    >>>>>>>> The text blow just keeps repeating OVER and OVER again
    >>>>>>> *BELOW*
    >>>>>>>> "
    >>>>>>>> Begin: Running /scripts/nfs-premount
    >>>>>>>> Done.
    >>>>>>>> nfsmount: need a path
    >>>>>>>> Begin: Retrying NFS mount
    >>>>>>>> IP-Config: eth0 hardware address xx:xx:xx:xx:xx:xx mtu 1500 DHCP
    >>>>>>>> RARP IP-Config: eth0 guessed broadcast address 192.168.0.255
    >>>>>>>> IP-Config: eth0 Complete (from 192.168.0.1) : address :
    >>>>>>>> 192.168.0.103
    >>>>>>>> : Net Mask 255.255.255.0
    >>>>>>>> Gateway: 192.168.0.1 dns: 102.168.0.1 dns1: 0.0.0.0
    >>>>>>>> Domain : MYNET
    >>>>>>>> rootserver 192.168.0.1 rootpath:
    >>>>>>>> filenameL
    >>>>>>> filename: (dang fat fingers...)
    >>>>>>>> nfsmount: need a path
    >>>>>>>> "
    >>>>>>>>
    >>>>>>>> I was able to boot by going into grum and selecting a different
    >>>>>>>> kernel
    >>>>>>>> "2.6.20-16-generic"
    >>>>>>>>
    >>>>>>>> thanks in advance !
    >>>>>>>> Joe
    >>>>>> Are you trying to do a NFS mount in your /etc/fstab?
    >>>>>>
    >>>>> No there is just "normal" stuff there
    >>>>>
    >>>>> # /etc/fstab: static file system information.
    >>>>> #
    >>>>> #
    >>>>> proc /proc proc defaults 0 0
    >>>>> # /dev/sda1
    >>>>> UUID=6bb2f238-2a89-46cf-a7f3-6aa302619135 / ext3
    >>>>> defaults,errors=remount-ro 0 1
    >>>>> # /dev/sda5
    >>>>> UUID=c09a798d-32b1-471f-9df4-eb2da13923d2 none swap sw
    >>>>> 0 0
    >>>>> /dev/hda /media/cdrom0 udf,iso9660 user,noauto 0 0
    >>>>> ~
    >>>>>
    >>>>> ~
    >>>>>> Cheers.
    >>>>>>
    >>>>> Thanks ... Any other ideas ?
    >>>> Post your /boot/grub/menu.lst
    >>>>
    >>>> Cheers.
    >>>>
    >>> OK, I attached it ... does it help diagnose the problem ?
    >>>
    >>> Thanks !
    >>> Joe

    >>
    >> Also do this and post results:
    >>
    >> cd /boot
    >> ls -l
    >>
    >> Thanks
    >>
    >> Cheers.
    >>

    >
    > Hope this helps.
    >
    > Note : as you can see in the GRUB menu list I have tried to upgrade a
    > couple of times, always getting the same results on bootup. The original
    > kernel continues to work.
    >
    > Thanks for looking at this.
    >
    > Joe


    Please post the results of this:

    ls -al /dev/disk/by-uuid

    Cheers.

    --
    The world can't afford the rich.


  12. Re: UBUNTU upgrade problems

    dada wrote:

    > NoStop wrote:
    >> dada wrote:
    >>
    >>> AspireOne_User wrote:
    >>>> dada wrote:
    >>>>
    >>>>> dada wrote:
    >>>>>> I upgraded my UBUNTU system a few months ago and have been living
    >>>>>> with a problem ever since. I would like to get this fixed if
    >>>>>> possible, so any help would be appreciated.
    >>>>>>
    >>>>>> When the system starts to boot (2.6.24-19-generic) I get the
    >>>>>> following message, repeated in a loop, using the recover kernel has
    >>>>>> the same problem).
    >>>>>>
    >>>>>> (Hopefully I got this correct, I wrote it down and am typing it in,
    >>>>>> so beware of typos)
    >>>>>> (Using xx:xx:xx... because I didn't write down the address)
    >>>>>>
    >>>>>> The text blow just keeps repeating OVER and OVER again
    >>>>> *BELOW*
    >>>>>> "
    >>>>>> Begin: Running /scripts/nfs-premount
    >>>>>> Done.
    >>>>>> nfsmount: need a path
    >>>>>> Begin: Retrying NFS mount
    >>>>>> IP-Config: eth0 hardware address xx:xx:xx:xx:xx:xx mtu 1500 DHCP RARP
    >>>>>> IP-Config: eth0 guessed broadcast address 192.168.0.255
    >>>>>> IP-Config: eth0 Complete (from 192.168.0.1) : address : 192.168.0.103
    >>>>>> : Net Mask 255.255.255.0
    >>>>>> Gateway: 192.168.0.1 dns: 102.168.0.1 dns1: 0.0.0.0
    >>>>>> Domain : MYNET
    >>>>>> rootserver 192.168.0.1 rootpath:
    >>>>>> filenameL
    >>>>> filename: (dang fat fingers...)
    >>>>>> nfsmount: need a path
    >>>>>> "
    >>>>>>
    >>>>>> I was able to boot by going into grum and selecting a different
    >>>>>> kernel
    >>>>>> "2.6.20-16-generic"
    >>>>>>
    >>>>>> thanks in advance !
    >>>>>> Joe
    >>>> Are you trying to do a NFS mount in your /etc/fstab?
    >>>>
    >>> No there is just "normal" stuff there
    >>>
    >>> # /etc/fstab: static file system information.
    >>> #
    >>> #
    >>> proc /proc proc defaults 0 0
    >>> # /dev/sda1
    >>> UUID=6bb2f238-2a89-46cf-a7f3-6aa302619135 / ext3
    >>> defaults,errors=remount-ro 0 1
    >>> # /dev/sda5
    >>> UUID=c09a798d-32b1-471f-9df4-eb2da13923d2 none swap sw
    >>> 0 0
    >>> /dev/hda /media/cdrom0 udf,iso9660 user,noauto 0 0
    >>> ~
    >>>
    >>> ~
    >>>> Cheers.
    >>>>
    >>> Thanks ... Any other ideas ?

    >>
    >> Post your /boot/grub/menu.lst
    >>
    >> Cheers.
    >>

    >
    > OK, I attached it ... does it help diagnose the problem ?
    >
    > Thanks !
    > Joe


    Did you try and reinstall the newest kernel through Synaptic like I
    suggested in my last msg? If so and still no got, I'm running out of ideas.
    Maybe some prob with using UUIDs with those new kernels?

    You can try ...

    Comment out this line in /etc/fstab:

    #UUID=6bb2f238-2a89-46cf-a7f3-6aa302619135 / ext3
    defaults,errors=remount-ro 0 1

    Add this line below it:

    /dev/sda1 / ext3 defaults,errors=remount-ro 0 1

    And in /boot/grub/menu.lst change:

    kernel /boot/vmlinuz-2.6.24-19-generic
    root=UUID=6bb2f238-2a89-46cf-a7f3-6aa302619135 ro quiet

    to:

    kernel /boot/vmlinuz-2.6.24-19-generic root=/dev/sda1 ro quiet

    Cheers.


    --
    The world can't afford the rich.


  13. Re: UBUNTU upgrade problems

    NoStop wrote:
    > dada wrote:
    >
    >> NoStop wrote:
    >>> dada wrote:
    >>>
    >>>> NoStop wrote:
    >>>>> dada wrote:
    >>>>>
    >>>>>> AspireOne_User wrote:
    >>>>>>> dada wrote:
    >>>>>>>
    >>>>>>>> dada wrote:
    >>>>>>>>> I upgraded my UBUNTU system a few months ago and have been living
    >>>>>>>>> with a problem ever since. I would like to get this fixed if
    >>>>>>>>> possible, so any help would be appreciated.
    >>>>>>>>>
    >>>>>>>>> When the system starts to boot (2.6.24-19-generic) I get the
    >>>>>>>>> following message, repeated in a loop, using the recover kernel has
    >>>>>>>>> the same problem).
    >>>>>>>>>
    >>>>>>>>> (Hopefully I got this correct, I wrote it down and am typing it in,
    >>>>>>>>> so beware of typos)
    >>>>>>>>> (Using xx:xx:xx... because I didn't write down the address)
    >>>>>>>>>
    >>>>>>>>> The text blow just keeps repeating OVER and OVER again
    >>>>>>>> *BELOW*
    >>>>>>>>> "
    >>>>>>>>> Begin: Running /scripts/nfs-premount
    >>>>>>>>> Done.
    >>>>>>>>> nfsmount: need a path
    >>>>>>>>> Begin: Retrying NFS mount
    >>>>>>>>> IP-Config: eth0 hardware address xx:xx:xx:xx:xx:xx mtu 1500 DHCP
    >>>>>>>>> RARP IP-Config: eth0 guessed broadcast address 192.168.0.255
    >>>>>>>>> IP-Config: eth0 Complete (from 192.168.0.1) : address :
    >>>>>>>>> 192.168.0.103
    >>>>>>>>> : Net Mask 255.255.255.0
    >>>>>>>>> Gateway: 192.168.0.1 dns: 102.168.0.1 dns1: 0.0.0.0
    >>>>>>>>> Domain : MYNET
    >>>>>>>>> rootserver 192.168.0.1 rootpath:
    >>>>>>>>> filenameL
    >>>>>>>> filename: (dang fat fingers...)
    >>>>>>>>> nfsmount: need a path
    >>>>>>>>> "
    >>>>>>>>>
    >>>>>>>>> I was able to boot by going into grum and selecting a different
    >>>>>>>>> kernel
    >>>>>>>>> "2.6.20-16-generic"
    >>>>>>>>>
    >>>>>>>>> thanks in advance !
    >>>>>>>>> Joe
    >>>>>>> Are you trying to do a NFS mount in your /etc/fstab?
    >>>>>>>
    >>>>>> No there is just "normal" stuff there
    >>>>>>
    >>>>>> # /etc/fstab: static file system information.
    >>>>>> #
    >>>>>> #
    >>>>>> proc /proc proc defaults 0 0
    >>>>>> # /dev/sda1
    >>>>>> UUID=6bb2f238-2a89-46cf-a7f3-6aa302619135 / ext3
    >>>>>> defaults,errors=remount-ro 0 1
    >>>>>> # /dev/sda5
    >>>>>> UUID=c09a798d-32b1-471f-9df4-eb2da13923d2 none swap sw
    >>>>>> 0 0
    >>>>>> /dev/hda /media/cdrom0 udf,iso9660 user,noauto 0 0
    >>>>>> ~
    >>>>>>
    >>>>>> ~
    >>>>>>> Cheers.
    >>>>>>>
    >>>>>> Thanks ... Any other ideas ?
    >>>>> Post your /boot/grub/menu.lst
    >>>>>
    >>>>> Cheers.
    >>>>>
    >>>> OK, I attached it ... does it help diagnose the problem ?
    >>>>
    >>>> Thanks !
    >>>> Joe
    >>> Also do this and post results:
    >>>
    >>> cd /boot
    >>> ls -l
    >>>
    >>> Thanks
    >>>
    >>> Cheers.
    >>>

    >> Hope this helps.
    >>
    >> Note : as you can see in the GRUB menu list I have tried to upgrade a
    >> couple of times, always getting the same results on bootup. The original
    >> kernel continues to work.
    >>
    >> Thanks for looking at this.
    >>
    >> Joe

    >
    > Please post the results of this:
    >
    > ls -al /dev/disk/by-uuid
    >



    root@mustang:/home/dada/junk# ls -al /dev/disk/by-uuid
    total 0
    drwxr-xr-x 2 root root 80 2008-09-21 01:32 .
    drwxr-xr-x 5 root root 100 2008-09-21 01:32 ..
    lrwxrwxrwx 1 root root 10 2008-09-21 01:32
    6bb2f238-2a89-46cf-a7f3-6aa302619135 -> ../../sda1
    lrwxrwxrwx 1 root root 10 2008-09-21 01:32
    c09a798d-32b1-471f-9df4-eb2da13923d2 -> ../../sda5

    > Cheers.
    >


  14. Re: UBUNTU upgrade problems

    NoStop wrote:
    > dada wrote:
    >
    >> NoStop wrote:
    >>> dada wrote:
    >>>
    >>>> AspireOne_User wrote:
    >>>>> dada wrote:
    >>>>>
    >>>>>> dada wrote:
    >>>>>>> I upgraded my UBUNTU system a few months ago and have been living
    >>>>>>> with a problem ever since. I would like to get this fixed if
    >>>>>>> possible, so any help would be appreciated.
    >>>>>>>
    >>>>>>> When the system starts to boot (2.6.24-19-generic) I get the
    >>>>>>> following message, repeated in a loop, using the recover kernel has
    >>>>>>> the same problem).
    >>>>>>>
    >>>>>>> (Hopefully I got this correct, I wrote it down and am typing it in,
    >>>>>>> so beware of typos)
    >>>>>>> (Using xx:xx:xx... because I didn't write down the address)
    >>>>>>>
    >>>>>>> The text blow just keeps repeating OVER and OVER again
    >>>>>> *BELOW*
    >>>>>>> "
    >>>>>>> Begin: Running /scripts/nfs-premount
    >>>>>>> Done.
    >>>>>>> nfsmount: need a path
    >>>>>>> Begin: Retrying NFS mount
    >>>>>>> IP-Config: eth0 hardware address xx:xx:xx:xx:xx:xx mtu 1500 DHCP RARP
    >>>>>>> IP-Config: eth0 guessed broadcast address 192.168.0.255
    >>>>>>> IP-Config: eth0 Complete (from 192.168.0.1) : address : 192.168.0.103
    >>>>>>> : Net Mask 255.255.255.0
    >>>>>>> Gateway: 192.168.0.1 dns: 102.168.0.1 dns1: 0.0.0.0
    >>>>>>> Domain : MYNET
    >>>>>>> rootserver 192.168.0.1 rootpath:
    >>>>>>> filenameL
    >>>>>> filename: (dang fat fingers...)
    >>>>>>> nfsmount: need a path
    >>>>>>> "
    >>>>>>>
    >>>>>>> I was able to boot by going into grum and selecting a different
    >>>>>>> kernel
    >>>>>>> "2.6.20-16-generic"
    >>>>>>>
    >>>>>>> thanks in advance !
    >>>>>>> Joe
    >>>>> Are you trying to do a NFS mount in your /etc/fstab?
    >>>>>
    >>>> No there is just "normal" stuff there
    >>>>
    >>>> # /etc/fstab: static file system information.
    >>>> #
    >>>> #
    >>>> proc /proc proc defaults 0 0
    >>>> # /dev/sda1
    >>>> UUID=6bb2f238-2a89-46cf-a7f3-6aa302619135 / ext3
    >>>> defaults,errors=remount-ro 0 1
    >>>> # /dev/sda5
    >>>> UUID=c09a798d-32b1-471f-9df4-eb2da13923d2 none swap sw
    >>>> 0 0
    >>>> /dev/hda /media/cdrom0 udf,iso9660 user,noauto 0 0
    >>>> ~
    >>>>
    >>>> ~
    >>>>> Cheers.
    >>>>>
    >>>> Thanks ... Any other ideas ?
    >>> Post your /boot/grub/menu.lst
    >>>
    >>> Cheers.
    >>>

    >> OK, I attached it ... does it help diagnose the problem ?
    >>
    >> Thanks !
    >> Joe

    >
    > Did you try and reinstall the newest kernel through Synaptic like I
    > suggested in my last msg? If so and still no got, I'm running out of ideas.
    > Maybe some prob with using UUIDs with those new kernels?
    >
    > You can try ...
    >
    > Comment out this line in /etc/fstab:
    >
    > #UUID=6bb2f238-2a89-46cf-a7f3-6aa302619135 / ext3
    > defaults,errors=remount-ro 0 1
    >
    > Add this line below it:
    >
    > /dev/sda1 / ext3 defaults,errors=remount-ro 0 1
    >
    > And in /boot/grub/menu.lst change:
    >
    > kernel /boot/vmlinuz-2.6.24-19-generic
    > root=UUID=6bb2f238-2a89-46cf-a7f3-6aa302619135 ro quiet
    >
    > to:
    >
    > kernel /boot/vmlinuz-2.6.24-19-generic root=/dev/sda1 ro quiet
    >
    > Cheers.
    >
    >


    I'll give that a shot when I am not working so late...

    Thanks Again !
    Joe

+ Reply to Thread