search for: raidtab

Hi There, I re-installed Centos 4 on a box previously running x86 Solaris 10. After a reboot a got a BAD PBR SIG so I used rescue mode and grub to install a boot loader on each of my software-raided disks. Which works fine and allows me to boot ok. My question is, what happened to /etc/raidtab the machine boots ok and lists all the raid-1 devices I set up in the install (including the /boot partition) but there is no raidtab file. I tried using dmraid to take a look at the software RAID setup but it reports "No Software Raid" So my question is "what happened to mkraid...

...on I don't know. I partitioned it to the same specs as the 2 ide drives as per the bottom of fdisk -l. Now, trying to go by: http://www.redhat.com/docs/manuals/enterprise/RHEL-4-Manual/admin-guide/ 5.9.8.2 Creating RAID Arrays they state the following: Next, it is necessary to create the /etc/raidtab file. This file is responsible for the proper configuration of all RAID arrays on your system. The file format (which is documented in the raidtab(5) man page) is relatively straightforward. Here is an example /etc/raidtab entry for a RAID 1 array: ummm...1.)I think this is part of the old raidtoo...

...ving some trouble with unlinked inodes and I/O errors on certain files. I took it down to single-user mode, and ran fsck on it. That operation mixed up files like /etc/hosts with /etc/rc.sysinit, and vice versa. I straightened those out, and ran fsck again. That happened to trash such files as /etc/raidtab and /etc/passwd and caused I/O errors so that I could not straighten it out. Running fsck again made the problem worse by making /etc/rc.sysinit unaccessible, and preventing me from booting up at all. I don't have helpful snippets from the error log since I was on a serial terminal and was inc...

...he older mkraid utils at the time but has been in production for over a year. This node and the array unfortunately had a power outage and the resulting problem faced by us is the following. The raid start up fails with as it cannot find a device /dev/sdai1 . This device is not part of the /etc/raidtab but is a normal device defined in the /dev directory. There are no references to the /dev/sdai1 device in /proc/partitions at all . All devices expected as /dev/sdd1 and /dev/sdx1 are listed and show the expected sizes. so I presume these are the only devices that the Linux box would be able to wo...

...71 138 546210 5 Extended /dev/hdd4 139 21781 173844468 83 Linux /dev/hdd5 71 104 273104+ 83 Linux /dev/hdd6 105 138 273104+ 83 Linux I can mount hdX1 and hdX2 (hdx2 is xfs) on all disks. Now /etc/raidtab (from one of the hdx2 partions) has the following entry which I'd like to re-create on the CentOS box raiddev /dev/md0 raid-level 5 nr-raid-disks 4 nr-spare-disks 0 persistent-superblock 1 chunk-size 64 device /dev/hda4 raid...

.../dev/sdo dc 00 06 CL1G 04:1b OPEN-9 00040898 /dev/sdh c6 00 07 CL2G 04:1c OPEN-9 00040898 /dev/sdp dc 00 07 CL1G 04:1c OPEN-9 00040898 from here: would I fdisk the devices, then create the raidtab file, then mkraid, then add them to create the ocfs filesystem, then mount then, then add them to the fstab and it's done? Is this even supported? The main reason for all of this is that I see a couple of conflicting comments on this: don't use raid or lvm on RAC? or yes you can? Any insi...

When a new system CentOS-4.4 is built the swap partition is always reversed... Note md3 below, the raidtab is OK, I have tried various raid commands to correct. swapoff -a raidstop /dev/md3 mkraid /dev/md3 --really-force swapon -a And then I get a proper ourput for /proc/mdstat, but when I reboot /proc/mdstat again reads as below, with md3 [0] [1] reversed. [root]# cat /proc/mdstat Personalitie...

So I have been playing with a RAID 10 f2 ( 2 disks far layout) setup...thanks for all of the advice..Now I am playing with the format and want to make sure I have it setup the best that I can, my raid was built using the raid 10 option with 2 disks with the layout=far, chunk size 512....now I read all of the docs I could find about format and stride and stripe size and this is what i came up

Hello all, I've got CentOS 5.2 installed on an old Pentium III server. The server is used by a club at my school, and they are rapidly running out of room on the internal IDE drives that are configured in software RAID 1. I have a Silicon Image SATA controller in the server, and I was planning on adding two more SATA hard drives to the computer. Is there a GUI like Disk Druid for

...hat kind of overhead is involved after the filesystem is ext3? - What journalling mode is suggested for this type of application/system configuration? - What size journal would be appropriate give data=ordered vs. data=journal? - And any other suggestions/insights/comments. Below is our /etc/raidtab. Let me know if you need any more information. Thank you in advance for all your assistance. Regards, Andrew Rechenberg Network Team, Sherman Financial Group arechenberg@shermanfinancialgroup.com raiddev /dev/md0 raid-level 0 persistent-superblock...

...restoring from backup) is simple: # sfdisk /dev/sdb < ~/partitions.sda That''s it. The two drives are now identically partitioned. Now we need to initialise the RAID on the second disk without destroying the data on the first. # apt-get install mdadm raidtools2 Begin by creating the raidtab. My one looks like this: raiddev /dev/md0 raid-level 1 nr-raid-disks 2 persistent-superblock 1 chunk-size 8 device /dev/sda1 failed-disk 0 device /dev/sdb1 raid-disk 1 ... repeated for each partition. Marking the partitions...

...now when I put everything back into the head node, and reboot, the BIOS sees all four drives, and from what I can tell, recognizes the first raid (of drives 3 and 4), but says it can only find one disk for the second raid (drives 1 and 2). I can't find any way around this. Looking at my /etc/raidtab file: raiddev /dev/md0 raid-level 1 nr-raid-disks 2 nr-spare-disks 0 persistent-superblock 1 device /dev/sdc1 raid-disk 0 device /dev/sdd1 raid-disk 1 raiddev /dev/md1 raid-level 0...

Conclusion: DO NOT USE SOFTWARE RAID-1 WITH EXT3 I've started with this conclusion cause i am positive that raid-1 and ext3 are causing data corruption. I've upgraded from 7.1 to 7.2 and from the first date i run into data corruption problems @ least once per day (i was monitoring once per day only) after 7 days we bought a brand new server cause the previous was very old and i thought