> 2) in an earlier message you indicated that there was some kind of > RAID on this system, I think it is safe to say that it is a BIOS-assisted > software RAID, which COULD be causing you problems if it is still > configured in the BIOS. And even if it isn't causing this problem, > it WILL bite you in the future when the BIOS decides top copy something > from one drive to the other...
Sorry about my previous post but there is no RAID. > So, start by disabling the BIOS "RAID" do-hickey thing and unplug > the second drive. I suspect you will have no problems then. I have tried pulling the plug on the second disk (wd1) with no luck. > Once you convince yourself the size of the drive is not directly > an issue, I'd suggest starting over with a more sane partitioning > plan. Just because you have a cheap 500G disk doesn't mean you > need to allocate all or most of it. For one, the bigger the disk, > the longer it takes to fsck after you trip over the power cord. I actually have two "cheap" 500GB; so that makes it 1 terabyte. I don't mind fsck doing its thing when I trip over the cable. But I really do need a large /data1 partition to rsync stuff over from other places. Here's the last disk partition I tried (and it didn't work): / 10g, swap 3g, /tmp 20g, /home 100g, /var/ 50g, /usr/ 50g. It was sitting there for 30 minutes after the last file set was installed (xserv44.tgz) and then I turned it off. Thanks for any further help.
