search for: clueby4

http://wiki.centos.org/HowTos/SoftwareRAIDonCentOS5 has: dd if=/dev/zero of=/dev/sda bs=512 count=64 dd if=/dev/zero of=/dev/sdb bs=512 count=64 Will the joker who put in this particular gem without any warnings or a clear explanation for those who need a clueby4 with regards to file systems please either remove the instructions or add a very clear warning that damage to file systems that is not recoverable will result if run on the wrong disk(s). My successor at my previous job has gleefully followed those instructions (he seriously needs a clueby4 wh...

http://wiki.centos.org/HowTos/SoftwareRAIDonCentOS5 has: dd if=/dev/zero of=/dev/sda bs=512 count=64 dd if=/dev/zero of=/dev/sdb bs=512 count=64 Will the joker who put in this particular gem without any warnings or a clear explanation for those who need a clueby4 with regards to file systems please either remove the instructions or add a very clear warning that damage to file systems that is not recoverable will result if run on the wrong disk(s). My successor at my previous job has gleefully followed those instructions (he seriously needs a clueby4 wh...

Looks like the chum did not have to lose any data. Wiping out the MBR and the next 63 blocks apparently only wiped out grub stage1, partition table, and part of the lvm config data. I get to try to do a lvm 'recovery' at his expense now but this is my first time...has anybody ever tried restoring lvm config data back to the md/pv device? Cheers, Christopher

Hello Everyone, First time CentOS poster :) I have CentOS 4 installed on the head node of a Sun Gridengine cluster set up in a RAID. The head node has four hard drives, and I assume that drives 1 and 2 are in a raid and then drives 3 and 4 are in another raid. I was trying to expand the OS partition on drive 1 because it was full. I took drive 1 out, put it in my Fedora 8 box as a secondary