similar to: help with rebuilding md0 (Raid5)

I decided to start using ext3. My kernel 2.4.15p9. I downloaded and build util-linux-2.11m and e2fsprogs 1.25. I compiled ext3 in the kernel. I started converting my filesystems and thing went ok for the first few. I then started getting the following on each additional filesystem. [root@joker /root]# tune2fs -j /dev/hdc4 tune2fs 1.25 (20-Sep-2001) Creating journal inode: done This filesystem

I''m getting a VFS kernel panic when trying to booting to FC3 from Xen. Its the one that says I must supply a valid "root=" option. (sorry I don''t have it verbatim.) I''m using the xen-2.0 binary installer, kernel 2.6.9. I am using ext3fs, but I am fairly certain that I have compiled support into the kernel. (I''ve tired compile xen from the 2.0

Hi All I just installed a 2 node ,10 r2 rac on centos Linux 4.6 My rac install was done by following Jeff Hunters document (excellent work!) http://www.idevelopment.info/ For storage I used openfiler with the iscsi protocol http://www.openfiler.com/ everything went perfect... to the letter, I gracefully shutdown the 2 nodes , then the openfiler appliance, when I went to start it back up,

Hello all. I am using plain 2.4.7 with ext3-2.4-0.9.4-247, compiled with gcc-2.96-85 on a RH7.1 distribution with the relevant changes, i.e. e2fsprogs-1.22-1, mount-2.11g-4 and util-linux-2.11f-3 taken from rawhide. I am using sometimes my /usr/local partition for ext3 testing: /dev/hdc2 3842408 738176 2909044 21% /usr/local For my DIY testing, I am timing this trivial

Hi, Yesterday I nuked an old fat32 partition on my hard drive using fdisk. I just destroyed the partition and then created a new linux partition. Then I created an ext3 filesystem with the following command mkfs.ext3 -j /dev/hdc1 Everything seemed fine so I went ahead and moved all my music (MP3s and FLACS) onto that partition. This morning when I turn on my computer I can't mount that

it seems like I keep running into a wall. The present raid array...well let me do an fdisk -l: ---------------------------------------- Disk /dev/hda: 250.0 GB, 250059350016 bytes 255 heads, 63 sectors/track, 30401 cylinders Units = cylinders of 16065 * 512 = 8225280 bytes Device Boot Start End Blocks Id System /dev/hda1 * 1 13 104391 fd Linux

Dear R helpers, I have two input files as 'quantity.csv' and 'equity_price.csv' as (for example) given below. 'quantity.csv' GOOG     YHOO 1000         100 'equity_price.csv' sr_no   GOOG_price           YHOO_price 1            15.22                 536.40 2            15.07                 532.97 3            15.19                 534.05  4           

Hello, I had a scientific linux 3.0.4 system (rhel compatible), with 3 ide disks, one for / and two others in linear raid (250 gb and 300 gb each). This system was obsoleted so i move the raid disks to a new scientific linux 3.0.7 installation. However, the raid array was not detected ( I put the disks on the same channels and same master/lsave setup as in the previous setup). In fact

Hello. I have several systems (CentOS 3 and CentOS 4) with software raid and I've observed a difference in the raid state: In CentOS 3 systems we find that mdadm --detail /dev/md* show: .............. Version : 00.90.00 Creation Time : Fri Apr 16 14:59:43 2004 Raid Level : raid1 Array Size : 20289984 (19.35 GiB 20.78 GB) Device Size : 20289984 (19.35 GiB 20.78 GB)

I wanted to boot gentoo on xen, but it doesn''t work. What can I do? Booting ''Xen 3.0.0 / Linux 2.6.12.5'' root (hd0,0) Filesystem type is ext2fs, partition type 0x83 kernel /xen.gz dom0_mem=131072 com1=115200,8n1 [Multiboot-elf, <0x100000:0x641cc:0x27e34>, shtab=0x18c078, entry=0x100000] module /vmlinuz-2.6.12.5-xen-0 root=/dev/md0

OK, I have managed to get software RAID 1 running on my wonderful Proliant server but now have two challenges: 1) Fresh after an OS install and reboot, the RAID array starts to do its stuff but straight away (as part of the boot messages) I am told that the second disk is 'not ready for command' and the system hangs as soon as resyncing starts. I think this is fixed by adding an hdparm