Sponsored Content
Full Discussion: How to Extend Boot Partition
Operating Systems Linux Red Hat How to Extend Boot Partition Post 302463802 by mark54g on Monday 18th of October 2010 01:04:04 PM
Old 10-18-2010
Perhaps a better question would be how big is /boot and WHY is it full? Normally, 60MB is sufficient for most things. How large is it and why is it full? Do you have many custom kernels? Perhaps you can pare them down.
 

8 More Discussions You Might Find Interesting

1. UNIX for Dummies Questions & Answers

How to remove a unix boot partition ?

Hi group member, I'm as new as a newbie can get on Unix, so bear with me . I just got a task of installing NT on a box that had some sort of unix on it. Once I reboot, i always get a Grub> screen and I dont' know how to get rid of it. Just relying on the nt install parition don't seem to be able... (1 Reply)
Discussion started by: kwanm63
1 Replies

2. Red Hat

required resize /boot partition in linux

Hi, In my linux box I have installed /boot partition with 100MB. I have done compile for a newer kernel. The both kernels are required to me. Finally /boot partition has using 100%. I need to resize the /boot. Any body give the solution how to do resize the /boot partition without dusturbing the... (2 Replies)
Discussion started by: parsrigum
2 Replies

3. SuSE

Extend root partition on SuSE enterprise Server 11.1

Hello Folks, Greetings, I am in need of extending the / partition for one of my SuSE linux Enterprise Server 11.1 which is running on VMware. I will be able to extend the virtual lun from the vshphere console but not sure how to extend the root partition from the OS end. I am not sure if I... (1 Reply)
Discussion started by: PSP
1 Replies

4. Red Hat

Is it possible to extend a extended partition raw space in harddisk thru rhel 6

hi all, As going thru LVM concepts in rhel 6, got hit with a question about "how to use the raw partition of an harddisk which extended volume is taken a bit" please find the attached diagram... is it possible to use this raw space with previously created extended partition without data... (13 Replies)
Discussion started by: redhatlbug
13 Replies

5. Ubuntu

Clone one partition and boot from USB

I have small problem: my hard drive has 500GB storage and it is divided into partitions /dev/sda1 - 20 GB (boot) /dev/sda2 - rest I want to clone only one partition /dev/sda1 and write all data on my USB stick /dev/sdb What's more I want to make my USB bootable and I don't know at all how can... (3 Replies)
Discussion started by: menda
3 Replies

6. Linux

Creating /boot partition for LVM VG

Hi, I have a server booted into sysresccd (mini-linux OS) with 1 40 GB disk attached I am trying to create a volume group and restore another server into the new one However, when I try to create a partition for /boot it seems that my VG in LVM is not recognized anymore These are the... (2 Replies)
Discussion started by: galuzan
2 Replies

7. Solaris

Extend a soft partition

Hi, I need to extend a soft partition from 20G to 100G. New disk is already added as a meta device. This soft partition is already assigned to a guest LDOM. Can someone let me know the steps to increase soft partition so guest LDOM can recognize the new space. Thanks (1 Reply)
Discussion started by: Gho
1 Replies

8. UNIX for Beginners Questions & Answers

How to boot partition from Grub Minimal_BASH?

Hi, someone knows how can I boot my OS or cdrom from a Grub Minimal_Bash? :confused: sorry, I´m a dummy I explain, when I start loading the OS, I get errors, and ends up in the grub bash. This is the minimal_bash and I have no idea of ​​any command. It tells me "unknow partition". The problem is... (0 Replies)
Discussion started by: veravera
0 Replies
GRUBBY(8)						      System Manager's Manual							 GRUBBY(8)

NAME
grubby - command line tool for configuring grub, lilo, and elilo SYNOPSIS
grubby [--add-kernel=kernel-path] [--args=args] [--bad-image-okay] [--boot-filesystem=bootfs] [--bootloader-probe] [--config-file path] [--copy-default] [--default-kernel] [--grub] [--info=kernel-path] [--initrd=initrd-path] [--lilo] [--make-default] [-o path] [--remove-kernel=kernel-path] [--set-default=kernel-path] [--title=entry-title] DESCRIPTION
grubby is a command line tool for updating and displaying information about the configuration files for the grub, lilo, elilo (ia64), and yaboot (powerpc) boot loaders. It is primarily designed to be used from scripts which install new kernels and need to find information about the current boot environment. On Intel x86 platforms, grub is the default bootloader and the configuration file is in /boot/grub/grub.conf. On Intel ia64 platforms, elilo mode is used and the default location for the configuration file is /boot/grub/grub.conf. On PowerPC platforms, yaboot parsing is used and the configuration file should be in /etc/yaboot.conf. There are a number of ways to specify the kernel used for --info, --remove-kernel, and --update-kernel. Specificying DEFAULT or ALL selects the default entry and all of the entries, respectively. If a comma separated list of numbers is given, the boot entries indexed by those numbers are selected. Finally, the title of a boot entry may be specified by using TITLE=title as the argument; all entries with that title are used. OPTIONS
--add-kernel=kernel-path Add a new boot entry for the kernel located at kernel-path. --args=kernel-args When a new kernel is added, this specifies the command line arguments which should be passed to the kernel by default (note they are merged with the arguments from the template if --copy-default is used). When --update-kernel is used, this specifies new arguments to add to the argument list. Multiple, space separated arguments may be used. If an argument already exists the new value replaces the old values. The root= kernel argument gets special handling if the configuration file has special handling for specifying the root filesystem (like lilo.conf does). --bad-image-okay When grubby is looking for a entry to use for something (such as a template or a default boot entry) it uses sanity checks, such as ensuring that the kernel exists in the filesystem, to make sure entries that obviously won't work aren't selected. This option over- rides that behavior, and is designed primarily for testing. --boot-filesystem=bootfs The grub boot loader expects file paths listed in it's configuration path to be relative to the top of the filesystem they are on, rather then relative to the current root filesystem. By default grubby searches the list of currently mounted filesystems to deter- mine this. If this option is given grubby acts as if the specified filesystem was the filesystem containing the kernel (this option is designed primarily for testing). --bootloader-probe grubby tries to determine if grub or lilo is currently installed. When one of those bootloaders is found the name of that bootloader is displayed on stdout. Both could be installed (on different devices), and grubby will print out the names of both bootloaders, one per line. The probe for grub requires a commented out boot directive grub.conf identical to the standard directive in the lilo configuration file. If this is not present grubby will assume grub is not installed (note that anaconda places this directive in grub.conf files it creates). This option is only available on ia32 platforms. --config-file=path Use path as the configuration file rather then the default. --copy-default grubby will copy as much information (such as kernel arguments and root device) as possible from the current default kernel. The kernel path and initrd path will never be copied. --default-kernel Display the full path to the current default kernel and exit. --elilo Use an elilo style configuration file. --grub Use a grub style configuration file instead of lilo style. This is the default on ia32 platforms. --info=kernel-path Display information on all boot entries which match kernel-path. I --initrd=initrd-path Use initrd-path as the path to an initial ram disk for a new kernel being added. --lilo Use a lilo style configuration file. --make-default Make the new kernel entry being added the default entry. --remove-args=kernel-args The arguments specified by kernel-args are removed from the kernels specified by --update-kernel. The root argument gets special handling for configuration files that support separate root filesystem configuration. --remove-kernel=kernel-path Removes all boot entries which match kernel-path. This may be used along with --add-kernel, in which case the new kernel being added will never be removed. --set-default=kernel-path The first entry which boots the specified kernel is made the default boot entry. --title=entry-title When a new kernel entry is added entry-title is used as the title (lilo label) for the entry. If entry-title is longer then maximum length allowed by the bootloader (15 for lilo, unlimited for grub and elilo) the title is shortened to a (unique) entry. --update-kernel=kernel-path The entries for kernels matching kernel-path are updated. Currently the only items that can be updated is the kernel argument list, which is modified via the --args and --remove-args options. --version Display the version of grubby being run and then exit immediately. --yaboot Use an yaboot style configuration file. BUGS
The command line syntax is more then a little baroque. This probably won't be fixed as grubby is only intended to be called from shell scripts which can get it right. SEE ALSO
grub(8), lilo(8), yaboot(8), mkinitrd(8) AUTHOR
Erik Troan <ewt@redhat.com> 4th Berkeley Distribution Thu Jun 21 2002 GRUBBY(8)
All times are GMT -4. The time now is 02:51 AM.
Unix & Linux Forums Content Copyright 1993-2022. All Rights Reserved.
Privacy Policy