Hi I have a SuSE 8.2 server with two 40GB drives in a RAID1 config and everything has been working ok until now. It is set up with persistent superblocks and the partition type to 0xFD as instructed in the how-to. On it reside two partitions; boot and root. I did not think of saving the partition table data... Some time ago I heard alarming sounds from the server and swapped one of the drives (secondary) with a new one. After this the sounds disappeared and the rebuild went well (as verification showed). Now it seems that the primary drive is broken and the system won't boot no matter what. I am using the SuSE YaST online update function regularly, but now I wonder if the recent kernel update didn't in fact screw up my lilo.conf. At least, the update procedure asked me to issue /sbin/lilo after the update, which I did, but thought no more of it. Could it be that I hereby lost my persistent superblock setting or something even worse? Anybody aware of similar issues? I must now make my non-broken secondary drive bootable and this includes finding the partitions again... Partition Magic 7 reports an error saying something about non-existing or faulty partition data. Being a newbie in this field I must ask for advice on what to do. Thanks in advance /Niclas _________________________________________________________________ STOP MORE SPAM with the new MSN 8 and get 2 months FREE* http://join.msn.com/?page=features/junkmail