The Community Forums

Interact with an entire community of cPanel & WHM users!
  1. This site uses cookies. By continuing to use this site, you are agreeing to our use of cookies. Learn More.

hda1/dma issue

Discussion in 'General Discussion' started by I Love Jesus, Dec 21, 2004.

  1. I Love Jesus

    I Love Jesus AKA chadi

    Joined:
    Dec 6, 2004
    Messages:
    62
    Likes Received:
    0
    Trophy Points:
    6
    In WHM's server status I get:

    Disk hda1 (/boot) DMA+ 82% (flashing yellow button status)

    Yellow is like a warning sign in the status area so why is it flashing yellow for this boot partition, and how do I fix this?
     
  2. dezignguy

    dezignguy Well-Known Member

    Joined:
    Sep 26, 2004
    Messages:
    534
    Likes Received:
    0
    Trophy Points:
    16
    probably because it's over 80% full...

    You should probably uninstall a few old kernels... keep at least two new ones though, if you should have to revert back for whatever reason.
     
  3. I Love Jesus

    I Love Jesus AKA chadi

    Joined:
    Dec 6, 2004
    Messages:
    62
    Likes Received:
    0
    Trophy Points:
    6
    Could you please be kind enough to explain to me how to remove old kernels? Plus, this server was freshly re-imaged only 2-3 weeks ago. I'm not quite sure how fast new kernels are updated by the server user but I cannot imagine that much, that quick.
     
  4. EdRooney

    EdRooney BANNED

    Joined:
    Oct 21, 2004
    Messages:
    166
    Likes Received:
    0
    Trophy Points:
    0
    ls /boot

    Let us know whats in their.

    Look for kernel images with kernels you don't need anymore and remove those, then edit you grub or lilo conf file accordingly. I recommend keeping at least 2 different kernel versions. Also, I like to make /boot 1gig, harddrive space is cheap, you never know what size the next kernel will be, or a kernel 5 years from now.

    Hope this helps.
     
    #4 EdRooney, Dec 21, 2004
    Last edited: Dec 21, 2004
  5. dgbaker

    dgbaker Well-Known Member
    PartnerNOC

    Joined:
    Sep 20, 2002
    Messages:
    2,578
    Likes Received:
    3
    Trophy Points:
    38
    Location:
    Toronto, Ontario Canada
    cPanel Access Level:
    DataCenter Provider
    Nice answer Abe ;)

    You give someone an answer like that? You're the one constantly asking similar type questions. I suggest you take your own advise sometime.
     
  6. EdRooney

    EdRooney BANNED

    Joined:
    Oct 21, 2004
    Messages:
    166
    Likes Received:
    0
    Trophy Points:
    0
    Is
    ls /boot
    not the place to start?

    How am I suppose to know what he has in there.
     
  7. I Love Jesus

    I Love Jesus AKA chadi

    Joined:
    Dec 6, 2004
    Messages:
    62
    Likes Received:
    0
    Trophy Points:
    6
    Code:
    root@server [~]# ls
    ./               bfd-0.4/              firstboot_log         public_ftp/
    ../              bfd-current.tar.gz.1  .forward              public_html/
    .accesshash      .cpan/                .gconfd/              .rnd
    anaconda-ks.cfg  cpanel3-skel/         Install_DigiChat.bin  .spamassassin/
    apf-0.9.4-7/     cpanel_install.log    install.log           .tcshrc
    .bash_history    .cpcpan/              install.log.syslog    urchin-add.php*
    .bash_logout     .cpmysqlrpm/          mail/                 urchin-remove.php*
    .bash_profile    .cshrc                .my.cnf*              .Xresources
    .bashrc          download.php?did\=54  .pgpass 
    
    Code:
    root@server [~]# ls /boot
    ./                              quota.user*
    ../                             System.map@
    aquota.user*                    System.map-2.4.21-20.0.1.EL
    config-2.4.21-20.0.1.EL         System.map-2.4.21-20.0.1.ELsmp
    config-2.4.21-20.0.1.ELsmp      System.map-2.4.21-20.EL
    config-2.4.21-20.EL             System.map-2.4.21-20.ELsmp
    config-2.4.21-20.ELsmp          System.map-2.4.21-4.EL
    config-2.4.21-4.EL              System.map-2.4.21-4.ELsmp
    config-2.4.21-4.ELsmp           vmlinux-2.4.21-20.0.1.EL*
    grub/                           vmlinux-2.4.21-20.0.1.ELsmp*
    initrd-2.4.21-20.0.1.EL.img     vmlinux-2.4.21-20.EL*
    initrd-2.4.21-20.0.1.ELsmp.img  vmlinux-2.4.21-20.ELsmp*
    initrd-2.4.21-20.EL.img         vmlinux-2.4.21-4.EL*
    initrd-2.4.21-20.ELsmp.img      vmlinux-2.4.21-4.ELsmp*
    initrd-2.4.21-4.EL.img          vmlinuz-2.4.21-20.0.1.EL
    initrd-2.4.21-4.ELsmp.img       vmlinuz-2.4.21-20.0.1.ELsmp
    kernel.h                        vmlinuz-2.4.21-20.EL
    lost+found/                     vmlinuz-2.4.21-20.ELsmp
    message                         vmlinuz-2.4.21-4.EL
    message.ja                      vmlinuz-2.4.21-4.ELsmp
    root@server [~]#
    
     
  8. EdRooney

    EdRooney BANNED

    Joined:
    Oct 21, 2004
    Messages:
    166
    Likes Received:
    0
    Trophy Points:
    0
    80% isnt bad necessarily, I would remove these 2
    System.map-2.4.21-20.EL
    System.map-2.4.21-20.ELsmp
     
  9. casey

    casey Well-Known Member

    Joined:
    Jan 17, 2003
    Messages:
    2,303
    Likes Received:
    0
    Trophy Points:
    36
    Location:
    If there is trouble, it will find me
    You can do:

    rpm -qa | grep kernel

    and then you can see what kernels you have. To delete the ones you don't need, run

    rpm -e name_of_the_kernel

    It will remove all the unnecessary stuff for you.
     
  10. I Love Jesus

    I Love Jesus AKA chadi

    Joined:
    Dec 6, 2004
    Messages:
    62
    Likes Received:
    0
    Trophy Points:
    6
    Forgive me for asking, but how do I know which ones I need and do not need? I've never deleted kernels so I just want to be careful.
     
  11. EdRooney

    EdRooney BANNED

    Joined:
    Oct 21, 2004
    Messages:
    166
    Likes Received:
    0
    Trophy Points:
    0
    If its working ok with the latest version of the kernel, keep that one, start by deleting the oldest, then second oldest, etc until you have enough free space on /boot.
     
  12. dezignguy

    dezignguy Well-Known Member

    Joined:
    Sep 26, 2004
    Messages:
    534
    Likes Received:
    0
    Trophy Points:
    16
    Those are old ones... I'd remove those... there's no reason you'd want to go back to those. Leave the 2.4.21-20 versions as those are the two most recent kernels.

    Clarifying my last post, 80% isn't necessarily bad... since the /boot partition isn't going to be growing as the server is used and cause problems when it hits 100%, like /home. So it's not too much of a worry as long as you remember to remove old kernels more frequently, as you update to new kernels. Since you seem to have a rather small /boot partition. I've got 9 old kernels (some are doubled up with the SMP version) still installed and am barely over 50% usage.
     
  13. chirpy

    chirpy Well-Known Member

    Joined:
    Jun 15, 2002
    Messages:
    13,475
    Likes Received:
    20
    Trophy Points:
    38
    Location:
    Go on, have a guess
    And please, if you are usng a RedHat OS, you really should follow casey's advice and use rpm to remove any package installed on your system, especially old kernels. Not doing so could render your server unbootable thanks to the simplest of typos. Unless you are a competent system admiinistrator you shouldn't touch anything in /boot directly.
     
  14. I Love Jesus

    I Love Jesus AKA chadi

    Joined:
    Dec 6, 2004
    Messages:
    62
    Likes Received:
    0
    Trophy Points:
    6
    root@server [/boot]# rpm -qa | grep kernel
    rpmdb: Program version 4.2 doesn't match environment version
    error: db4 error(22) from dbenv->open: Invalid argument
    error: cannot open Packages index using db3 - Invalid argument (22)
    error: cannot open Packages database in /var/lib/rpm


    ???
     
  15. haze

    haze Well-Known Member

    Joined:
    Dec 21, 2001
    Messages:
    1,550
    Likes Received:
    3
    Trophy Points:
    38
    Try rebuilding the rpm db: rpm -vv --rebuilddb

    uname -a will show you what kernel you are currently running. You can not remove a kernel you are currently live on, keep that in mind.

    Before you remove ANY kernel, ensure you are on the latest, which is now: 2.4.21-27.EL
    Its a good rule of thumb to keep the last 1 - 2 kernels you know have worked, just incase the new kernel buggers up, or has problems in the future you can then revert back to a known working kernel.

    Is this a hyperthreaded or dual processor machine ? If not, get rid of ALL of the SMP kernel's, if so, get rid of ALL of the NON SMP kernels.

    When you are complete, I suggest your audit your lilo.conf or grub.conf ( depending on which is in use on your system ) to ensure they are correct and your newest or current kernel is selected.
     
  16. EdRooney

    EdRooney BANNED

    Joined:
    Oct 21, 2004
    Messages:
    166
    Likes Received:
    0
    Trophy Points:
    0
    He is using Red Hat Enterprise.
     
  17. neonix

    neonix Well-Known Member

    Joined:
    Oct 21, 2004
    Messages:
    124
    Likes Received:
    2
    Trophy Points:
    0
    Hi,

    I received a Drive Warning: /sda1 (/boot) is 83% full message.

    I am on RHEL Dual Xeon.

    Processor InformationProcessor #1 Vendor: GenuineIntel
    Processor #1 Name: Intel(R) Xeon(TM) CPU 2.80GHz
    Processor #1 speed: 2790.839 MHz
    Processor #1 cache size: 512 KB

    Processor #2 Vendor: GenuineIntel
    Processor #2 Name: Intel(R) Xeon(TM) CPU 2.80GHz
    Processor #2 speed: 2790.839 MHz
    Processor #2 cache size: 512 KB

    Processor #3 Vendor: GenuineIntel
    Processor #3 Name: Intel(R) Xeon(TM) CPU 2.80GHz
    Processor #3 speed: 2790.839 MHz
    Processor #3 cache size: 512 KB

    Processor #4 Vendor: GenuineIntel
    Processor #4 Name: Intel(R) Xeon(TM) CPU 2.80GHz
    Processor #4 speed: 2790.839 MHz
    Processor #4 cache size: 512 KB




    root@pac3 [/boot]# uname -r
    2.4.21-37.ELsmp

    root@pac3 [/boot]# rpm -qa | grep kernel
    kernel-2.4.21-27.0.1.EL
    kernel-2.4.21-20.0.1.EL
    kernel-smp-2.4.21-27.0.4.EL
    kernel-smp-2.4.21-32.0.1.EL
    kernel-2.4.21-20.EL
    kernel-smp-2.4.21-4.EL
    kernel-2.4.21-32.0.1.EL
    kernel-smp-2.4.21-37.0.1.EL
    kernel-smp-2.4.21-27.EL
    kernel-2.4.21-27.0.2.EL
    kernel-2.4.21-27.0.4.EL
    kernel-2.4.21-32.EL
    kernel-2.4.21-37.EL
    kernel-smp-2.4.21-40.EL
    kernel-pcmcia-cs-3.1.31-19
    kernel-smp-2.4.21-20.EL
    kernel-2.4.21-27.EL
    kernel-smp-2.4.21-27.0.1.EL
    kernel-smp-2.4.21-20.0.1.EL
    kernel-2.4.21-4.EL
    kernel-smp-2.4.21-27.0.2.EL
    kernel-smp-2.4.21-32.EL
    kernel-smp-2.4.21-37.EL
    kernel-2.4.21-37.0.1.EL
    kernel-2.4.21-40.EL


    Are the below commands correct?

    rpm -e kernel-2.4.21-20.EL
    rpm -e kernel-smp-2.4.21-20.EL
    rpm -e kernel-2.4.21-20.0.1.EL
    rpm -e kernel-smp-2.4.21-20.0.1.EL

    Do I have to manually modify grub.conf...after running these commands...do I have to do anything else after runing these commands...besides praying :)


    Thanks for your advise...
     
  18. Doug E

    Doug E Well-Known Member

    Joined:
    Aug 17, 2005
    Messages:
    58
    Likes Received:
    0
    Trophy Points:
    6
    I've the same problem as some in this thread with the drive space warning.

    I've run rpm -qa | grep kernel and it appears I have a few extra kernels.

    They don't seem to be in order, which would be recommended I keep? I can delete the rest.

    kernel-smp-2.6.9-55.0.9.EL
    kernel-smp-2.6.9-67.0.1.EL
    kernel-smp-2.6.9-67.0.4.EL
    kernel-2.6.9-67.0.7.EL
    kernel-smp-2.6.9-78.0.8.EL
    kernel-smp-2.6.9-78.0.13.EL
    kernel-devel-2.6.9-78.0.17.EL
    kernel-smp-2.6.9-42.0.3.EL
    kernel-2.6.9-67.0.4.EL
    kernel-smp-2.6.9-67.0.15.EL
    kernel-2.6.9-67.0.20.EL
    kernel-smp-2.6.9-67.0.22.EL
    kernel-smp-2.6.9-22.EL
    kernel-smp-2.6.9-22.0.2.EL
    kernel-smp-2.6.9-42.0.2.EL
    kernel-2.6.9-55.0.2.EL
    kernel-smp-2.6.9-55.0.6.EL
    kernel-2.6.9-55.0.9.EL
    kernel-smp-2.6.9-55.0.12.EL
    kernel-2.6.9-67.0.22.EL
    kernel-hugemem-devel-2.6.9-78.0.17.EL
    kernel-smp-2.6.9-78.0.1.EL
    kernel-utils-2.4-14.1.117
    kernel-smp-2.6.9-42.0.8.EL
    kernel-2.6.9-22.0.2.EL
    kernel-smp-2.6.9-55.0.2.EL
    kernel-smp-2.6.9-67.EL
    kernel-2.6.9-67.0.15.EL
    kernel-smp-2.6.9-78.0.5.EL
    kernel-smp-devel-2.6.9-78.0.17.EL
    kernel-smp-2.6.9-42.0.10.EL
    kernel-2.6.9-67.0.1.EL
    kernel-smp-2.6.9-67.0.7.EL
    kernel-smp-2.6.9-67.0.20.EL
    kernel-2.6.9-78.0.1.EL
    kernel-2.6.9-78.0.8.EL
    kernel-2.6.9-78.0.13.EL
    kernel-2.6.9-78.0.17.EL
    kernel-smp-2.6.9-55.EL
    kernel-2.6.9-67.EL
    kernel-2.6.9-78.0.5.EL
    kernel-smp-2.6.9-78.0.17.EL
     
Loading...

Share This Page