Updated Gentoo Linux 2005.0 Filesystem

March 30, 2005 9:16 pm

Brought Gentoo up to date, to 2005.0 profile.

Please let me know if I missed anything.

-Chris

21 Responses

  1. Hi Chris,

    I’m a newbie on Linodes, I’ve tried to boot the 2005.0 profile but it crashes at the beginning.

    I post here the output from the remote console:

    [code]
    md: raid5 personality registered as nr 4
    raid5: measuring checksumming speed
    8regs : 6055.600 MB/sec
    32regs : 1976.800 MB/sec
    raid5: using function: 8regs (6055.600 MB/sec)
    md: multipath personality registered as nr 7
    md: md driver 0.90.0 MAX_MD_DEVS=256, MD_SB_DISKS=27
    md: Autodetecting RAID arrays.
    md: autorun …
    md: … autorun DONE.
    LVM version 1.0.8(17/11/2003)
    Initializing Cryptographic API
    Initializing software serial port version 1
    mconsole (version 2) initialized on /linodes/warp3r/.uml/warp3r/mconsole
    Partition check:
    hda: unknown partition table
    hdb: unknown partition table
    Initializing stdio console driver
    Netdevice 0 (fe:fd:40:3e:be:df) : TUN/TAP backend –
    IPv6 v0.8 for NET4.0
    IPv6 over IPv4 tunneling driver
    NET4: Linux TCP/IP 1.0 for NET4.0
    IP Protocols: ICMP, UDP, TCP, IGMP
    IP: routing cache hash table of 512 buckets, 4Kbytes
    TCP: Hash tables configured (established 8192 bind 16384)
    IPv4 over IPv4 tunneling driver
    GRE over IPv4 tunneling driver
    Linux IP multicast router 0.06 plus PIM-SM
    ip_conntrack version 2.1 (964 buckets, 7712 max) – 288 bytes per conntrack
    ip_tables: (C) 2000-2002 Netfilter core team
    ipt_recent v0.3.1: Stephen Frost <sfrost@snowman.net>. http://snowman.net/projects/ipt_recent/
    arp_tables: (C) 2002 David S. Miller
    NET4: Unix domain sockets 1.0/SMP for Linux NET4.0.
    ip6_tables: (C) 2000-2002 Netfilter core team
    NET4: Ethernet Bridge 008 for NET4.0
    802.1Q VLAN Support v1.8 Ben Greear <greearb@candelatech.com>
    All bugs added by David S. Miller <davem@redhat.com>
    kjournald starting. Commit interval 5 seconds
    EXT3-fs: mounted filesystem with ordered data mode.
    VFS: Mounted root (ext3 filesystem) readonly.
    INIT: version 2.84 booting

    Gentoo Linux; http://www.gentoo.org/
    Copyright 2001-2004 Gentoo Technologies, Inc.; Distributed under the GPL

    * Mounting proc at /proc… [ ok ]
    * Mounting devfs at /dev… [ ok ]
    * Activating (possible) swap… [ ok ]
    * Remounting root filesystem read-only (if necessary)… [ ok ]
    * Checking root filesystem…fsck.ext3: No such file or directory while trying to open /dev/ubda
    /dev/ubda:
    The superblock could not be read or does not describe a correct ext2
    filesystem. If the device is valid and it really contains an ext2
    filesystem (and not swap or ufs or something else), then the superblock
    is corrupt, and you might try running e2fsck with an alternate superblock:
    e2fsck -b 8193 <device>

    * Filesystem couldn’t be fixed :(
    [ !! ]

    Give root password for maintenance
    [/code]

    Since it’s the first time i set up the linode, I don’t know if i missed something 🙂 can you check it?

    thanks & cheers!

    warp3r

  2. Ok, give me a few minutes and I’ll have that fixed.

    -Chris

  3. Wow! That’s what we call a fast reply 🙂

    many thanx, I’ll wait for the fix

    byte

  4. Fixed. Please delete that image and re-deploy 🙂

    Gentoo ignores its own startup kernel arguments (noudev nodevfs). Go figure.

    -Chris

  5. I supposed it was something related to udev/devfs as I saw the line:
    [code]* Mounting devfs at /dev… [ ok ] [/code]

    But I’m not used to UML so i didn’t knew if it was generating the prob.

    Many thanks chris!

  6. [quote:5901b44f33=”warp3r”]Many thanks chris![/quote]
    Don’t thank me yet. Another fix in a few minutes…

    -Chris

  7. Redeploy once more — you should be set. Had to fix the remote console that time.

    -Chris

  8. Ok … 😛 Just in case i’ll shut down the linode and start redeploying tomorrow morning 🙂

    its 1 AM in spain and tomorrow i’ve to wake up early…
    see you!

  9. I was also trying out 2005.0 and here’s as far as the boot process got:

    [quote]VFS: Cannot open root device “ubda” or 62:00
    Please append a correct “root=” boot option
    Kernel panic: VFS: Unable to mount root fs on 62:00
    <6>SysRq : Show Regs

    EIP: 0073:[<802ab891>] CPU: 0 Not tainted ESP: 007b:b7ffefa0 EFLAGS: 00000296
    Not tainted
    EAX: 00000000 EBX: 00007514 ECX: 00000013 EDX: 00007514
    ESI: 00000000 EDI: 00000000 EBP: 00000000 DS: 007b ES: 007b
    Call Trace: [<80312ce7>] [<8031a484>] [<800125cf>] [<801a9f8e>] [<80312215>]
    [<80195875>] [<8001f15e>] [<80312215>] [<80014bc7>] [<80014c3d>] [<800028c9>]
    [<8031fda4>] [<80010184>] [<8000382d>] [<80312215>] [<800106ed>] [<80312215>]
    [<8001070d>] [<80010192>] [<802ab53d>] [<802ab4f1>] [<80010184>] [<80190441>]
    [<80010184>] [<8019041c>] [<80010184>] [<80199ac5>] [<80010184>] [<80199561>]
    [<802ab638>] [<802ab891>] [/quote]

  10. [quote:ea8e8ebb83=”yoshi”]I was also trying out 2005.0 and here’s as far as the boot process got:
    [/quote]
    Did you delete and re-deploy the fixed template image? If not, which host are you on?

    Thanks,
    -Chris

  11. I just did a complete redeploy and changed the profile to use the latest 2.6 kernel and all is well.

    Thanks for your support.

  12. I think I missed something,

    I redeployed twice and I have another issue now.
    When it boots it does not do it completely, it freezes at the end and says:

    [code] * Starting sshd… [ ok ]
    * Starting local… [ ok ]

    INIT: Id "c0" respawning too fast: disabled for 5 minutes
    INIT: no more processes left in this runlevel
    [/code]

    Then I can’t log in via ssh directly to the linode, neither using host20 LISH, as I don’t have any user prompt.

    I use the 2005.0 Image and the latest 2.6.10 kernel available on configuration profile, did I forget to do something?

    cheers
    warp3r[/quote]

  13. ok, forget it, it works…

    sorry for any inconvenience
    warp3r

  14. [quote:99fcb5aa48=”warp3r”]I think I missed something,

    I redeployed twice and I have another issue now.
    When it boots it does not do it completely, it freezes at the end and says:

    [code] * Starting sshd… [ ok ]
    * Starting local… [ ok ]

    INIT: Id "c0" respawning too fast: disabled for 5 minutes
    INIT: no more processes left in this runlevel
    [/code]

    Then I can’t log in via ssh directly to the linode, neither using host20 LISH, as I don’t have any user prompt.

    I use the 2005.0 Image and the latest 2.6.10 kernel available on configuration profile, did I forget to do something?

    cheers
    warp3r[/quote][/quote]

    I’m doing the same thing as you with the 2005.0 image and latest 2.6 kernel and I’m also seeing the respawning too fast messages in my console.

    I’m unsure if I should worry about the message tho. Should I? 🙂

  15. [quote:06904e5c63=”yoshi”]I’m doing the same thing as you with the 2005.0 image and latest 2.6 kernel and I’m also seeing the respawning too fast messages in my console.

    I’m unsure if I should worry about the message tho. Should I? :)[/quote]
    If you guys deployed the distro before last evening when I fixed it, you have two options:

    1. Redeploy the image. It should not have this problem.
    2. Edit /etc/inittab, change “tty0” to “vc/0”. Add “vc/0” to /etc/securetty. Then run “init q” as root.

    -Chris

  16. Perfect now 🙂

    sorry for the delay, didn’t checked the forum ’til today

    thx for your support

  17. [quote:42f799a78f=”caker”]
    If you guys deployed the distro before last evening when I fixed it, you have two options:

    1. Redeploy the image. It should not have this problem.
    2. Edit /etc/inittab, change “tty0” to “vc/0”. Add “vc/0” to /etc/securetty. Then run “init q” as root.

    -Chris[/quote]

    I just deployed a new 2005 image and i’m unable to boot it, it gets stalled here with that same problem

    * Mounting network filesystems… [ ok ]
    * Starting sshd… [ ok ]
    * Starting local… [ ok ]
    INIT: Id “c0” respawning too fast: disabled for 5 minutes
    INIT: no more processes left in this runlevel

    thanks

  18. I am using the “older” Gentoo install, and keep my setup uptodate with fairly regular emerges, so all my packages are new versions.

    I think my kernel is linux-2.4.26.

    Would upgrading to this image make any sense to me? I know that it has a more recent kernel, but are there other advantages or disadvantages?

    Would I have to totally backup my current setup offline, install the image, and restore my programs and data, or would my currently compiled programs have trouble running?

  19. Kernels can be selected independently of the distro/version – edit your configuration profile(s) in the Linode Platform Manager.

    If you tell emerge to update your current system you will be invited to upgrade your Gentoo profile if necessary – that is as good as a new install.

    Do not restore programs from your current system to a new install – you will may end up linking against the wrong library versions and chaos and madness will follow.

  20. [quote:3a20ebee69=”Clapper”]I am using the “older” Gentoo install, and keep my setup uptodate with fairly regular emerges, so all my packages are new versions.

    I think my kernel is linux-2.4.26.

    Would upgrading to this image make any sense to me? I know that it has a more recent kernel, but are there other advantages or disadvantages?

    Would I have to totally backup my current setup offline, install the image, and restore my programs and data, or would my currently compiled programs have trouble running?[/quote]

    Just change your profile. There’s a doc on gentoo’s site about how to upgrade your profile.

  21. Just to say that the “INIT: Id “c0″ respawning too fast: disabled for 5 minutes” thing is still there. I’ve changed this and works:

    2. Edit /etc/inittab, change “tty0” to “vc/0”. Add “vc/0” to /etc/securetty. Then run “init q” as root.

Leave a Reply