These dd commands may take an hour or more. You sure your system was hung? Anyway, try this dd command on your working disks: dd if=/dev/<good disk> of=/dev/null bs=64k example: dd if=/dev/hda of=/dev/null bs=64k or this if you want to know how long it takes: time dd if=/dev/hda of=/dev/null bs=64k The above is a read test. It will not overwrite any data. Once you know your good disks work, try a bad disk. Maybe you will be able to determine a common hardware component, like a disk controller. Guy -----Original Message----- From: linux-raid-owner@xxxxxxxxxxxxxxx [mailto:linux-raid-owner@xxxxxxxxxxxxxxx] On Behalf Of Arnab Chowdry Sent: Wednesday, May 12, 2004 6:27 PM To: linux-raid@xxxxxxxxxxxxxxx Subject: RE: mkraid hangs system >you could dd if=/dev/zero of=/dev/your/disk, Oddly enough, dd hangs as well. I guess that means it's not a RAID problem. Very strange though, and I don't have a good intuition about why it's happening. dd if=/dev/zero of=/dev/hde dd if=/dev/zero of=/dev/hdg dd if=/dev/zero of=/dev/hdi dd if=/dev/zero of=/dev/hdk All of the above hang the system after a few seconds. I'm sorry is this is now off-topic, but maybe some of you experts have some intuition about why this might happen? All four of the drives can't have "gone bad" or something. -Arnab - To unsubscribe from this list: send the line "unsubscribe linux-raid" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html - To unsubscribe from this list: send the line "unsubscribe linux-raid" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
