I'm doing exactly this on a trial basis with production servers. So far,
it's working great. Some tips:
1) Flash drives are less reliable than HDDs. Software RAID1 is the way
to go.
A) Use two different makes of USB drives so that you have
different failure characteristics. If either
On 01/24/2014 11:09 PM, Emmanuel Noobadmin wrote:
However, note that there might be an issue with anaconda and big USB
storage. The boot partition anaconda creates will not boot past grub.
I needed to manually create the partition to start on sector 63 for
grub to see it. Happens on my 16GB
Is it possible to install CentOS on a USB Flash Drive. Have boot
sector, / and /boot on USB drive then put /home, etc on a software
raid array of the physical drives.
Thought there used to be motherboards with SDHC slots that you could
use to boot off.
On 1/25/14, Matt matt.mailingli...@gmail.com wrote:
Is it possible to install CentOS on a USB Flash Drive. Have boot
sector, / and /boot on USB drive then put /home, etc on a software
raid array of the physical drives.
Thought there used to be motherboards with SDHC slots that you could
use
JohnS wrote:
For others that are saying it want update the boot config then you may
have something wrong somewhere because it should plain out update it.
We know that it should update the boot config. And under most
circumstances, it does. The problem is that under some conditions,
while
I successfully created an install media on a USB flash drive, but now I
have a minor problem installing from it. Whenever I run the installer,
it insists on installing grub on /dev/sdb (the flash drive) rather than
/dev/sda (the hard drive where I'm installing everything).
Is there a way to
Bowie Bailey wrote, On 05/26/2010 10:59 AM:
I successfully created an install media on a USB flash drive, but now I
have a minor problem installing from it. Whenever I run the installer,
it insists on installing grub on /dev/sdb (the flash drive) rather than
/dev/sda (the hard drive where I'm
Bowie Bailey wrote, On 05/26/2010 10:59 AM:
I successfully created an install media on a USB flash drive, but now I
have a minor problem installing from it. Whenever I run the installer,
it insists on installing grub on /dev/sdb (the flash drive) rather than
/dev/sda (the hard drive where
m.r...@5-cent.us wrote:
Bowie Bailey wrote, On 05/26/2010 10:59 AM:
I successfully created an install media on a USB flash drive, but now I
have a minor problem installing from it. Whenever I run the installer,
it insists on installing grub on /dev/sdb (the flash drive) rather than
Bowie wrote:
m.r...@5-cent.us wrote:
Bowie Bailey wrote, On 05/26/2010 10:59 AM:
I successfully created an install media on a USB flash drive, but now
I have a minor problem installing from it. Whenever I run the
installer, it insists on installing grub on /dev/sdb (the flash drive)
rather
m.r...@5-cent.us wrote:
Bowie wrote:
Agreed. It's truly obnoxious that we can specify which drive to install
the OS onto, but we can't specify where to put the boot loader.
What I did was skip the grub install and then install it from the rescue
prompt. Unfortunately, this left me
Bowie wrote:
m.r...@5-cent.us wrote:
Bowie wrote:
snip
Once it's on, it's fairly stable... though the update of the kernel does
*not* always work correctly. With nearly 200 machines that I'm rolling
out
updates to, not infrequently, I'll see that the default= line in
/etc/grub.conf is
On Wed, 2010-05-26 at 14:57 -0400, m.r...@5-cent.us wrote:
Bowie wrote:
m.r...@5-cent.us wrote:
Bowie wrote:
snip
Once it's on, it's fairly stable... though the update of the kernel does
*not* always work correctly. With nearly 200 machines that I'm rolling
out
updates to, not
JohnS wrote:
On Wed, 2010-05-26 at 14:57 -0400, m.r...@5-cent.us wrote:
Bowie wrote:
m.r...@5-cent.us wrote:
Bowie wrote:
snip
Once it's on, it's fairly stable... though the update of the kernel does
*not* always work correctly. With nearly 200 machines
On Wed, 2010-05-26 at 14:57 -0400, m.r...@5-cent.us wrote:
Bowie wrote:
m.r...@5-cent.us wrote:
Bowie wrote:
snip
Once it's on, it's fairly stable... though the update of the kernel
does *not* always work correctly. With nearly 200 machines that I'm
rolling out
updates to, not
On 5/26/2010 2:37 PM, JohnS wrote:
And, in fact, that is exactly what happened. The default= line was set
to 1, so it booted the old kernel instead of the new one. Other than
that, it seems to be fine. I wonder what causes that? I've never
noticed that behavior in my other systems. (But
On Wed, 2010-05-26 at 15:07 -0500, Les Mikesell wrote:
On 5/26/2010 2:37 PM, JohnS wrote:
And, in fact, that is exactly what happened. The default= line was set
to 1, so it booted the old kernel instead of the new one. Other than
that, it seems to be fine. I wonder what causes that?
On 5/26/2010 3:17 PM, JohnS wrote:
And, in fact, that is exactly what happened. The default= line was set
to 1, so it booted the old kernel instead of the new one. Other than
that, it seems to be fine. I wonder what causes that? I've never
noticed that behavior in my other systems. (But
On Wed, 2010-05-26 at 15:29 -0500, Les Mikesell wrote:
It's not the stick of RAM - it's the fact the the grub conf editing is
set up to match your initial kernel type and isn't triggered by the
install of the PAE kernel or it's subsequent updates. Look in
/etc/sysconfig/kernel.
---
On 05/26/2010 11:57 AM, m.r...@5-cent.us wrote:
Bowie wrote:
m.r...@5-cent.us wrote:
Bowie wrote:
And, in fact, that is exactly what happened. The default= line was set
to 1, so it booted the old kernel instead of the new one. Other than
that, it seems to be fine. I wonder
20 matches
Mail list logo
