HPE GreenLake Administration
- Community Home
- >
- Servers and Operating Systems
- >
- Operating Systems
- >
- Operating System - Linux
- >
- Re: /boot
Operating System - Linux
1827809
Members
1983
Online
109969
Solutions
Forums
Categories
Company
Local Language
back
Forums
Discussions
Forums
- Data Protection and Retention
- Entry Storage Systems
- Legacy
- Midrange and Enterprise Storage
- Storage Networking
- HPE Nimble Storage
Discussions
Forums
Discussions
Discussions
Discussions
Forums
Discussions
back
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
- BladeSystem Infrastructure and Application Solutions
- Appliance Servers
- Alpha Servers
- BackOffice Products
- Internet Products
- HPE 9000 and HPE e3000 Servers
- Networking
- Netservers
- Secure OS Software for Linux
- Server Management (Insight Manager 7)
- Windows Server 2003
- Operating System - Tru64 Unix
- ProLiant Deployment and Provisioning
- Linux-Based Community / Regional
- Microsoft System Center Integration
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Blogs
Information
Community
Resources
Community Language
Language
Forums
Blogs
Go to solution
Topic Options
- Subscribe to RSS Feed
- Mark Topic as New
- Mark Topic as Read
- Float this Topic for Current User
- Bookmark
- Subscribe
- Printer Friendly Page
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
06-22-2005 09:39 PM
06-22-2005 09:39 PM
Hi everyone
During a number of builds, I overlooked the creation of a seperate filesystem for /boot. I know that this isn't a necessity but would like to rectify it.
If I look at my partition table I can see the boot partition
/dev/sda1 * 1 13 103981+ 83 Linux
In a normal situation I would consider tarring the contents of the dir, creating a new FS, with a new mount point, extracting the contents of the directory into the filesystem, remove the old files and rename the new mount point to the required etc
Any ideas what would be the best thing to do. I haven't really got anywhere to test this at the moment
Thanks in advance
Steve
During a number of builds, I overlooked the creation of a seperate filesystem for /boot. I know that this isn't a necessity but would like to rectify it.
If I look at my partition table I can see the boot partition
/dev/sda1 * 1 13 103981+ 83 Linux
In a normal situation I would consider tarring the contents of the dir, creating a new FS, with a new mount point, extracting the contents of the directory into the filesystem, remove the old files and rename the new mount point to the required etc
Any ideas what would be the best thing to do. I haven't really got anywhere to test this at the moment
Thanks in advance
Steve
take your time and think things through
Solved! Go to Solution.
3 REPLIES 3
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
06-22-2005 09:53 PM
06-22-2005 09:53 PM
Solution
Generally the reason for a '/boot' filesystem is to have the boot-files (kernel) in the first 1024 cylenders of a hard-disk.
On newer systems, the need for this has gone away, as system BIOS' have the ability to access more of a disk during those early stages of boot-up (were the controller drivers aren't available).
If you really want to put one in place, it'd be best to try to get that sort of thing in place.
To do this, you'd need to re-partition the harddrive, and if possible, create a partition at the very beginning of the disk. So you'll need a tool to move the contents of the disk around ('parted' can do this I believe) to free up that space.
Once that's done, you create your filesystem in the free'd up space at the start of the disk. You make sure you 'e2label' the filesystem as '/boot'. Create the entry for the filesystem in '/etc/fstab', and then mount the filesystem somewhere temporary.
Copy the content to the temporary mount point, then 'mv /boot /boot.old;mkdir /boot', and re-mount the new filesystem to '/boot'.
Here you'll need to re-install the bootloader ('grub-install', or 'lilo'), hopefully without any errors.
Moment of truth time.. Make sure you have a rescue disk (one of the RH CD's) handy, then reboot.
On newer systems, the need for this has gone away, as system BIOS' have the ability to access more of a disk during those early stages of boot-up (were the controller drivers aren't available).
If you really want to put one in place, it'd be best to try to get that sort of thing in place.
To do this, you'd need to re-partition the harddrive, and if possible, create a partition at the very beginning of the disk. So you'll need a tool to move the contents of the disk around ('parted' can do this I believe) to free up that space.
Once that's done, you create your filesystem in the free'd up space at the start of the disk. You make sure you 'e2label' the filesystem as '/boot'. Create the entry for the filesystem in '/etc/fstab', and then mount the filesystem somewhere temporary.
Copy the content to the temporary mount point, then 'mv /boot /boot.old;mkdir /boot', and re-mount the new filesystem to '/boot'.
Here you'll need to re-install the bootloader ('grub-install', or 'lilo'), hopefully without any errors.
Moment of truth time.. Make sure you have a rescue disk (one of the RH CD's) handy, then reboot.
One long-haired git at your service...
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
06-22-2005 10:54 PM
06-22-2005 10:54 PM
Re: /boot
if you are already having a small partition to have boot files then it is very easy.
* just format the partition as ext3 or whatever the file system you want.
* mount this partition in some temporary mount point.
* copy the contents of /boot files to this mount point
* remove contents of /boot directory, make sure the directory exists
* add the following entry in /etc/fstab
/dev/
* update grub.conf/lilo.conf file to reflect the partition where the boot files resides. field to update is root
reboot your system and it should come up.
if you dont have free partition then you have to follow stuart's suggestion.
Hope this helps,
Gopi
Never Never Never Giveup
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
06-28-2005 10:41 PM
06-28-2005 10:41 PM
Re: /boot
Hi Guys
Thanks for the responses, will be working on this over the next couple of days
will post the outcome
Regards
Steve
Thanks for the responses, will be working on this over the next couple of days
will post the outcome
Regards
Steve
take your time and think things through
The opinions expressed above are the personal opinions of the authors, not of Hewlett Packard Enterprise. By using this site, you accept the Terms of Use and Rules of Participation.
Company
Support
Events and news
Customer resources
© Copyright 2025 Hewlett Packard Enterprise Development LP