As the title says, I'd like to reinstall fedora 15 with the netinstall image because it's about 100mb (kernel and initrd) instead of the install dvds. My problem is that those files located in http://download.fedora.redhat.com/pub/fedora/linux/releases/15/Fedora/x86_64... have long been outdated. As you can see the kernel is only 3.7mb and the initrd almost 94mb. How to rebuild them from the latest kernel-2.6.40.4-6.fc15?
--joshua
On 09/28/2011 02:57 AM, Joshua C. wrote:
As the title says, I'd like to reinstall fedora 15 with the netinstall image because it's about 100mb (kernel and initrd) instead of the install dvds. My problem is that those files located in http://download.fedora.redhat.com/pub/fedora/linux/releases/15/Fedora/x86_64... have long been outdated. As you can see the kernel is only 3.7mb and the initrd almost 94mb. How to rebuild them from the latest kernel-2.6.40.4-6.fc15?
--joshua
1. yum install dracut-network
2. use dracut (like mkinitrd) # dracut initrd.img `uname -r`
That's it.
Yoy can PXE boot that, or roll it up into a bootable iso, which is what netboot is.
But why not just use the existing iso? easier
Good Luck!
2011/9/28 Phil Meyer pmeyer@themeyerfarm.com:
On 09/28/2011 02:57 AM, Joshua C. wrote:
As the title says, I'd like to reinstall fedora 15 with the netinstall image because it's about 100mb (kernel and initrd) instead of the install dvds. My problem is that those files located in http://download.fedora.redhat.com/pub/fedora/linux/releases/15/Fedora/x86_64... have long been outdated. As you can see the kernel is only 3.7mb and the initrd almost 94mb. How to rebuild them from the latest kernel-2.6.40.4-6.fc15?
--joshua
yum install dracut-network
use dracut (like mkinitrd) # dracut initrd.img `uname -r`
That's it.
Yoy can PXE boot that, or roll it up into a bootable iso, which is what netboot is.
But why not just use the existing iso? easier
Good Luck!
users mailing list users@lists.fedoraproject.org To unsubscribe or change subscription options: https://admin.fedoraproject.org/mailman/listinfo/users Guidelines: http://fedoraproject.org/wiki/Mailing_list_guidelines
I want to reinstall fedora on a intel fake-raid1 which is practically a software raid. In order to save all the config headaches I want to use a f16-livecd and rebuild the netinstall image with the kernel for f15 (kernel-2.6.40.4-6.fc15) and just boot from it. So from your example '# dracut initrd.img `uname -r' I think `uname -r` will return the running f16 kernel, not the one I want to use. Do I need the kernel-devel-package for this?
Bash will expand $(inane -r) for you - you can pass it any kernel you have headers installed for.
I wanted to jump in to suggest you reconsider motherboard driven fakeraid. The mainboard becomes a single point of failure, and replacing it or migrating the array can be problematic, especially with different chipset revisions or BIOS versions.
I recommend you set up a mdadm array. Drivers are in the kernel, documentation is profuse, and management is fairly simple once you get the hang of it. The graphical installer can even do it for you. Use the array for /home and possibly /etc and /var, and keep your root filesystem separate from your important data.
Hope this helps,
Pete On Sep 28, 2011 10:24 AM, "Joshua C." joshuacov@googlemail.com wrote:
2011/9/28 Phil Meyer pmeyer@themeyerfarm.com:
On 09/28/2011 02:57 AM, Joshua C. wrote:
As the title says, I'd like to reinstall fedora 15 with the netinstall image because it's about 100mb (kernel and initrd) instead of the install dvds. My problem is that those files located in
http://download.fedora.redhat.com/pub/fedora/linux/releases/15/Fedora/x86_64...
have long been outdated. As you can see the kernel is only 3.7mb and the initrd almost 94mb. How to rebuild them from the latest kernel-2.6.40.4-6.fc15?
--joshua
yum install dracut-network
use dracut (like mkinitrd) # dracut initrd.img `uname -r`
That's it.
Yoy can PXE boot that, or roll it up into a bootable iso, which is what netboot is.
But why not just use the existing iso? easier
Good Luck!
users mailing list users@lists.fedoraproject.org To unsubscribe or change subscription options: https://admin.fedoraproject.org/mailman/listinfo/users Guidelines: http://fedoraproject.org/wiki/Mailing_list_guidelines
I want to reinstall fedora on a intel fake-raid1 which is practically a software raid. In order to save all the config headaches I want to use a f16-livecd and rebuild the netinstall image with the kernel for f15 (kernel-2.6.40.4-6.fc15) and just boot from it. So from your example '# dracut initrd.img `uname -r' I think `uname -r` will return the running f16 kernel, not the one I want to use. Do I need the kernel-devel-package for this? -- users mailing list users@lists.fedoraproject.org To unsubscribe or change subscription options: https://admin.fedoraproject.org/mailman/listinfo/users Guidelines: http://fedoraproject.org/wiki/Mailing_list_guidelines
2011/9/28 Pete Travis me@petetravis.com:
Bash will expand $(inane -r) for you - you can pass it any kernel you have headers installed for.
I wanted to jump in to suggest you reconsider motherboard driven fakeraid. The mainboard becomes a single point of failure, and replacing it or migrating the array can be problematic, especially with different chipset revisions or BIOS versions.
I recommend you set up a mdadm array. Drivers are in the kernel, documentation is profuse, and management is fairly simple once you get the hang of it. The graphical installer can even do it for you. Use the array for /home and possibly /etc and /var, and keep your root filesystem separate from your important data.
Hope this helps,
Pete
That's the whole idea behind it. It's on a intel-p67 chipset with the build-in intel-raid1. I tend to use an mdadm array but I'm not sure which will be simpler to set and manage afterwards. I have to say I've not worked with arrays before this.
On Wed, Sep 28, 2011 at 11:41:22 -0600, Pete Travis me@petetravis.com wrote:
Bash will expand $(inane -r) for you - you can pass it any kernel you have headers installed for.
I wanted to jump in to suggest you reconsider motherboard driven fakeraid. The mainboard becomes a single point of failure, and replacing it or migrating the array can be problematic, especially with different chipset revisions or BIOS versions.
I recommend you set up a mdadm array. Drivers are in the kernel, documentation is profuse, and management is fairly simple once you get the hang of it. The graphical installer can even do it for you. Use the array for /home and possibly /etc and /var, and keep your root filesystem separate from your important data.
There is a downside to using mdadm over fake raid and that is that you can hit a bottleneck with the PCI bus as the data needs to be sent to each disk drive that needs a copy of the data (or parity info) instead of just once to the controller. Typically this will be twice as much data.
That said, I use mdadm. I have done such things as drop one side of my raid 1 mirrors, repartition that drive, set up new mirrors with encrypted file systems, and copy over file system data, repartion the other disk, add those partitions to the new mirrors.
On Wed, Sep 28, 2011 at 21:25:56 +0200, "Joshua C." joshuacov@googlemail.com wrote:
That's the whole idea behind it. It's on a intel-p67 chipset with the build-in intel-raid1. I tend to use an mdadm array but I'm not sure which will be simpler to set and manage afterwards. I have to say I've not worked with arrays before this.
mdadm is pretty simple to use.
On 09/28/2011 01:03 PM, Bruno Wolff III wrote:
On Wed, Sep 28, 2011 at 11:41:22 -0600, Pete Travisme@petetravis.com wrote:
Bash will expand $(inane -r) for you - you can pass it any kernel you have headers installed for.
I wanted to jump in to suggest you reconsider motherboard driven fakeraid. The mainboard becomes a single point of failure, and replacing it or migrating the array can be problematic, especially with different chipset revisions or BIOS versions.
I recommend you set up a mdadm array. Drivers are in the kernel, documentation is profuse, and management is fairly simple once you get the hang of it. The graphical installer can even do it for you. Use the array for /home and possibly /etc and /var, and keep your root filesystem separate from your important data.
There is a downside to using mdadm over fake raid and that is that you can hit a bottleneck with the PCI bus as the data needs to be sent to each disk drive that needs a copy of the data (or parity info) instead of just once to the controller. Typically this will be twice as much data.
That said, I use mdadm. I have done such things as drop one side of my raid 1 mirrors, repartition that drive, set up new mirrors with encrypted file systems, and copy over file system data, repartion the other disk, add those partitions to the new mirrors.
That's good info for anyone considering mdadm.
What if the underlying bus is 32 bit pci-e? would than not help with the throughput so that "twice" the data output does not slow your down that much? Of course it would still be considerably slower than having a 32-bit pci-e raid controller.
2011/9/28 Bruno Wolff III bruno@wolff.to:
On Wed, Sep 28, 2011 at 21:25:56 +0200, "Joshua C." joshuacov@googlemail.com wrote:
That's the whole idea behind it. It's on a intel-p67 chipset with the build-in intel-raid1. I tend to use an mdadm array but I'm not sure which will be simpler to set and manage afterwards. I have to say I've not worked with arrays before this.
mdadm is pretty simple to use.
I've found quite a lot of information in the internet about setting an mdadm array. All the time it concerns copying the info from one hdd to the other and setting the system to "see" the hdds as one. Have anyone of you come across a useful all-in-one guide?
On Wed, Sep 28, 2011 at 23:01:39 +0200, "Joshua C." joshuacov@googlemail.com wrote:
I've found quite a lot of information in the internet about setting an mdadm array. All the time it concerns copying the info from one hdd to the other and setting the system to "see" the hdds as one. Have anyone of you come across a useful all-in-one guide?
If you do it at install time in Fedora it's easy. You can use the custom disk setup in the install process to do it.
If you are trying to convert an existing machine over, than it's going to depend on particulars. I'd suggest doing a backup (which you'd want to do anyway), reinstall and reload. If you were planning on doing an upgrade (say to F16), you could combine it with that.
On Wed, 2011-09-28 at 15:03 -0500, Bruno Wolff III wrote:
On Wed, Sep 28, 2011 at 11:41:22 -0600, Pete Travis me@petetravis.com wrote:
Bash will expand $(inane -r) for you - you can pass it any kernel you have headers installed for.
I wanted to jump in to suggest you reconsider motherboard driven fakeraid. The mainboard becomes a single point of failure, and replacing it or migrating the array can be problematic, especially with different chipset revisions or BIOS versions.
I recommend you set up a mdadm array. Drivers are in the kernel, documentation is profuse, and management is fairly simple once you get the hang of it. The graphical installer can even do it for you. Use the array for /home and possibly /etc and /var, and keep your root filesystem separate from your important data.
There is a downside to using mdadm over fake raid and that is that you can hit a bottleneck with the PCI bus as the data needs to be sent to each disk drive that needs a copy of the data (or parity info) instead of just once to the controller. Typically this will be twice as much data.
That said, I use mdadm. I have done such things as drop one side of my raid 1 mirrors, repartition that drive, set up new mirrors with encrypted file systems, and copy over file system data, repartion the other disk, add those partitions to the new mirrors.
---- doesn't fake raid do the same thing? If there isn't an intelligent controller, the same type of data still has to travel through the exact same bus. Neither have write-back cache that would actually improve peformance.
Additionally, fakeraid requires proprietary kernel modules, dies with the motherboard and typically is slower performance than mdadm.
Craig
2011/9/29 Craig White craigwhite@azapple.com:
On Wed, 2011-09-28 at 15:03 -0500, Bruno Wolff III wrote:
On Wed, Sep 28, 2011 at 11:41:22 -0600, Pete Travis me@petetravis.com wrote:
Bash will expand $(inane -r) for you - you can pass it any kernel you have headers installed for.
I wanted to jump in to suggest you reconsider motherboard driven fakeraid. The mainboard becomes a single point of failure, and replacing it or migrating the array can be problematic, especially with different chipset revisions or BIOS versions.
I recommend you set up a mdadm array. Drivers are in the kernel, documentation is profuse, and management is fairly simple once you get the hang of it. The graphical installer can even do it for you. Use the array for /home and possibly /etc and /var, and keep your root filesystem separate from your important data.
There is a downside to using mdadm over fake raid and that is that you can hit a bottleneck with the PCI bus as the data needs to be sent to each disk drive that needs a copy of the data (or parity info) instead of just once to the controller. Typically this will be twice as much data.
That said, I use mdadm. I have done such things as drop one side of my raid 1 mirrors, repartition that drive, set up new mirrors with encrypted file systems, and copy over file system data, repartion the other disk, add those partitions to the new mirrors.
doesn't fake raid do the same thing? If there isn't an intelligent controller, the same type of data still has to travel through the exact same bus. Neither have write-back cache that would actually improve peformance.
Additionally, fakeraid requires proprietary kernel modules, dies with the motherboard and typically is slower performance than mdadm.
Craig
-- This message has been scanned for viruses and dangerous content by MailScanner, and is believed to be clean.
-- users mailing list users@lists.fedoraproject.org To unsubscribe or change subscription options: https://admin.fedoraproject.org/mailman/listinfo/users Guidelines: http://fedoraproject.org/wiki/Mailing_list_guidelines
Do I need to set any corn jobs to monitor the raid? This is recommended in most of the guides I read. If so, any suggestions why and how to do this?
On Thu, 2011-09-29 at 10:35 +0200, Joshua C. wrote:
Do I need to set any corn jobs to monitor the raid? This is recommended in most of the guides I read. If so, any suggestions why and how to do this?
---- I generally just set my e-mail address in /etc/mdadm.conf and leave it at that. You do get notified if the array goes into rebuild mode. Also it's good to set root's mail to come to your regular e-mail channels if possible... /etc/aliases but that sort of requires you to set up smtp on your system.
Craig
On Wed, 2011-09-28 at 10:57 +0200, Joshua C. wrote:
As the title says, I'd like to reinstall fedora 15 with the netinstall image because it's about 100mb (kernel and initrd) instead of the install dvds. My problem is that those files located in http://download.fedora.redhat.com/pub/fedora/linux/releases/15/Fedora/x86_64... have long been outdated. As you can see the kernel is only 3.7mb and the initrd almost 94mb. How to rebuild them from the latest kernel-2.6.40.4-6.fc15?
Does your hardware require the newer kernel? If not, just do the install with the provided media and then run 'yum update' once you've booted into your new system. No need to respin install media.
Dave
--joshua
2011/9/30 David Lehman dlehman@redhat.com:
On Wed, 2011-09-28 at 10:57 +0200, Joshua C. wrote:
As the title says, I'd like to reinstall fedora 15 with the netinstall image because it's about 100mb (kernel and initrd) instead of the install dvds. My problem is that those files located in http://download.fedora.redhat.com/pub/fedora/linux/releases/15/Fedora/x86_64... have long been outdated. As you can see the kernel is only 3.7mb and the initrd almost 94mb. How to rebuild them from the latest kernel-2.6.40.4-6.fc15?
Does your hardware require the newer kernel? If not, just do the install with the provided media and then run 'yum update' once you've booted into your new system. No need to respin install media.
Dave
--joshua
-- users mailing list users@lists.fedoraproject.org To unsubscribe or change subscription options: https://admin.fedoraproject.org/mailman/listinfo/users Guidelines: http://fedoraproject.org/wiki/Mailing_list_guidelines
It's a p67 chipset and I'd like to rebuild the install media. I tried dracut initrd.img `uname -r` but it produced a 26mb image. This falls far behind the almost 100mb in the original install media. What did I miss?
How to really rebuild it?
-
Bruno Wolff III -
Craig White -
David Lehman -
JD -
Joe Zeff -
Joshua C. -
Pete Travis -
Phil Meyer