Displaying 20 results from an estimated 5000 matches similar to: "Software RAID on CentOS 5 ... ideas ..."
2011 Sep 07
1
boot problem after disk change on raid1
Hello,
I have two disks sda and sdb. One of the was broken so I have changed the
broken disk with a working one. I started the server in rescue mode, and
created the partional table, and added all the partitions to the software
raid.
*I have added the partitions to the RAID, and reboot.*
# mdadm /dev/md0 --add /dev/sdb1
# mdadm /dev/md1 --add /dev/sdb2
# mdadm /dev/md2 --add /dev/sdb3
# mdadm
2010 Aug 24
0
Booting CentOS 5.5 (KVM) from a second disk
Hi all!
Doing some tests with CentOS 5.5 on a KVM virtual machine, after doing
the installation, I added a second disk. But when trying to boot from
it, I get the following error:
---------------------------------------------------------------------
root (hd1,0)
Error 21: Selected disk does not exist
---------------------------------------------------------------------
The two disks are
2010 Aug 24
1
Booting CentOS 5.5 (KVM) from a second disk
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
Hi all!
Doing some tests with CentOS 5.5 on a KVM virtual machine, after doing
the installation, I added a second disk. But when trying to boot from
it, I get the following error:
- ---------------------------------------------------------------------
root (hd1,0)
Error 21: Selected disk does not exist
-
2015 Aug 05
2
CentOS 5 grub boot problem
On 8/5/2015 12:34 PM, Chris Murphy wrote:
> On Wed, Aug 5, 2015 at 9:12 AM, Bowie Bailey <Bowie_Bailey at buc.com> wrote:
>> I am trying to upgrade my system from 500GB drives to 1TB.
> I'm going to guess that there are no IDE drives that have 4096 byte
> physical sectors, but it's worth confirming you don't have such a
> drive because the current partition
2005 Dec 02
1
FIXED Re: Re: MD Raid 1 software device not booting not even reaching grub
doing that grub-install /dev/sda will give me the "corresponding BIOS
device" error.
But now I fixed it by doing a manual grub install.
first boot with cd1 and type linux rescue at the prompt
when you're at the linux prompt after detecting and mounting the
partitions, do a "chroot /mnt/sysimage"
then
# grub --batch
#grub> root (hd0,0)
Filesystem type is ext2fs,
2005 Nov 27
0
centos4.2 -raid 1 and grub
I had this little shell script.
Use at your own risk...
Jerry
---------
# To load a blank drive with the old partition information use the command:
# sfdisk /dev/hda < /etc/silentm/raidinfo.partitions.hda
# The following command will setup the passed argument to boot in case
the main disk is faulty
# $1 is either /dev/hdb or /dev/sdb
grub_setup_scsi()
{
grub << EOF
find
2015 Aug 05
0
CentOS 5 grub boot problem
On Wed, Aug 5, 2015 at 11:11 AM, Bowie Bailey <Bowie_Bailey at buc.com> wrote:
> On 8/5/2015 1:00 PM, Chris Murphy wrote:
>>
>> On Wed, Aug 5, 2015 at 10:52 AM, Bowie Bailey <Bowie_Bailey at buc.com>
>> wrote:
>>>
>>> How would I go about pointing it at the partition?
>>>
>>> What I am currently doing is this:
>>> device
2005 Jul 21
1
Install Problems Centos 4.1
Dear All,
I have a K8S-MX Asus Athlon 64 Motherboard with a 754 pin 3000+ CPU,
which I cam trying to install 4.1 Centos 64 bit.
The problem seems to arise when installing onto Mirrored disks, I have
noticed that from Centos 4 onwards it tries to rebuild the arrays as it
installs which slows the whole process right down across all platforms I
have tried it on.
In addition, the install
2015 Aug 05
0
CentOS 5 grub boot problem
On Wed, Aug 5, 2015 at 9:12 AM, Bowie Bailey <Bowie_Bailey at buc.com> wrote:
> I am trying to upgrade my system from 500GB drives to 1TB.
I'm going to guess that there are no IDE drives that have 4096 byte
physical sectors, but it's worth confirming you don't have such a
drive because the current partition scheme you've posted would be
sub-optimal if it does have 4096
2015 Aug 05
0
CentOS 5 grub boot problem
On Wed, Aug 5, 2015 at 10:52 AM, Bowie Bailey <Bowie_Bailey at buc.com> wrote:
>
> On 8/5/2015 12:34 PM, Chris Murphy wrote:
>>
>> On Wed, Aug 5, 2015 at 9:12 AM, Bowie Bailey <Bowie_Bailey at buc.com> wrote:
>>>
>>> I am trying to upgrade my system from 500GB drives to 1TB.
>>
>> I'm going to guess that there are no IDE drives that
2015 Aug 05
5
CentOS 5 grub boot problem
On 8/5/2015 1:00 PM, Chris Murphy wrote:
> On Wed, Aug 5, 2015 at 10:52 AM, Bowie Bailey <Bowie_Bailey at buc.com> wrote:
>> How would I go about pointing it at the partition?
>>
>> What I am currently doing is this:
>> device (hd0) /dev/hdg
>> root (hd0,0)
>> setup (hd0)
>
> setup (hd1,0)
>
> It's hd1 if your device map is correct and
2016 Aug 11
5
Software RAID and GRUB on CentOS 7
Hi,
When I perform a software RAID 1 or RAID 5 installation on a LAN server
with several hard disks, I wonder if GRUB already gets installed on each
individual MBR, or if I have to do that manually. On CentOS 5.x and 6.x,
this had to be done like this:
# grub
grub> device (hd0) /dev/sda
grub> device (hd1) /dev/sdb
grub> root (hd0,0)
grub> setup (hd0)
grub> root (hd1,0)
grub>
2015 Mar 29
1
RAID1 bootloader configuration on CentOS 6.x and 7
Hi,
The CentOS wiki sports a page about setting up software RAID1 on CentOS
5.x. There's a section about making both members of the RAID1 bootable
by setting up GRUB on both disks.
Now I wonder how this should be done on CentOS 6.x and 7. I have two
sandbox machines in my office, one running a minimal CentOS 6.6, the
other one with a CentOS 7 installation.
Correct me if I'm wrong,
2016 Aug 11
0
Software RAID and GRUB on CentOS 7
On 08/11/16 02:33, Nicolas Kovacs wrote:
> Hi,
>
> When I perform a software RAID 1 or RAID 5 installation on a LAN server
> with several hard disks, I wonder if GRUB already gets installed on each
> individual MBR, or if I have to do that manually. On CentOS 5.x and 6.x,
> this had to be done like this:
>
> # grub
> grub> device (hd0) /dev/sda
> grub> device
2015 Aug 05
2
CentOS 5 grub boot problem
I never thought I'd say this, but I think it's easier to do this with
GRUB 2. Anyway I did an installation to raid1's in CentOS 6's
installer, which still uses GRUB legacy. I tested removing each of the
two devices and it still boots. These are the commands in its log:
: Running... ['/sbin/grub-install', '--just-copy']
: Running... ['/sbin/grub',
2007 Sep 25
2
mdadm problem.
So I'm trying to RAID-1 this system which has two identical disks
installed in it, and it isn't working for some reason.
I started by doing a CentOS-4 install on /dev/sda1 as root, and with
/dev/sda2 as my swap.
I finish the install, yum update, and then I want to make the mirrors.
I copy the partition table from one disk to the other:
# sfdisk -d /dev/sda | sfdisk /dev/sdb
I create
2008 Oct 01
0
AW: Increase size of file-based diskimage (with MBR, partitions + fs)
Hey
I had the same problem some time ago. But here is a solution how to do that, but it''s a bit tricky!
REQUIREMENT: THE SYSTEM PARTITION ON THE IMAGE MUST BE THE FIRST PARTITION, AFTER THAT THERE MUST BE ONLY SWAP PARTITIONS!!!!
This setup would work, there should be no risk at all:
Partition 1 on the image: /
Partition 2 on the image: swap space
This setup WONT''T WORK, YOU
2009 Apr 28
3
Updated How to Setup a Software RAID on CentOS 5
I have attempted to address all comments:
http://wiki.centos.org/HowTos/SoftwareRAIDonCentOS5
Give me your best shot! :-D
Phil
2007 Aug 29
1
chain.c32 question
I'd like to use chain.c32 to allow the computer boot from HARDDISK if
needed.
If I use isolinux and boot from CD, the following works OK:
chain.c32 hd0
But if I boot from USB Flash Key, it sometimes work and sometimes it
doesn't and I have to use
chain.c32 hd1
(it seems BIOS assigns hd0 to the flash key sometimes, so the real
harddisk is hd1 in that case).
Is there any way to tell
2017 Jan 05
1
Strange (?) device.map in CentOS 7 VM installations
On Thu, Jan 5, 2017 at 4:04 AM, Nikolaos Milas <nmilas at noa.gr> wrote:
> On 4/1/2017 7:37 ??, Gordon Messmer wrote:
>
> I don't see that on VMs that I manage. Some of the physical machines that
>> I manage do have duplicates in the device.map.
>>
>
> Thank you Gordon for your feedback!
>
> Can others please report the content of /boot/grub2/device.map