Hi all! Whooo! Now that seemed to be a huge thread I kicked off! Too bad I was swaeting over my suse-box with no e-mail trying to save everything. Well it looks like I made it! Thanks to all your tips! Well, to start off, reiserfsck seemed to have made things worse. I was not able to boot at all. Safe settings would hang at some point as would normal boot. I then tried rescue on the DVD and while it (naturally) started up the thing would not see the disk. Some rescue, I thought. Then I grabbed my Knoppix (3.4) and that was not able to see the disks either (It might be that Knoppix uses an older LVM version, but I didn't dig into that). Then I noticed that the thing would boot when I gave option 1 (into init 1) and would see the disks ok. However I could not access the network. As I wanted to take a backup anyway though I got me a spanking new 160 GB disk and installed a clean 9.1. After installing LVM packages the new system was able to mount and read the disks ok! The rest is of course hours of copying. Neato, all my .kde settings are working too! Including my bunch of kmail filters to keep the mailing lists in order... There was one interesting thing though: after I inserted the new (SATA) disk I could not boot beyond BIOS. I had to (after a colleague tipped me off) put the two LVM (IDE) disks on different chains - rather than the same as they were before - in order to boot correctly. Mind you that before the crash the disks were running on the same chain for a year or so. A quick answer to the "heat" thread. The computer as a whole was definitely not overheated as I dismantled the side panels a long time ago. However, I had put the HDs one above and one below the floppy, so maybe that aged them or something. BTW, How do I now check the old disks if they are ok? Any suggestions for tools? So now that I had a new system I wanted to upgrade to 9.2 (as it was a fresh 9.1 install anyway) but I get stuck in yast. but that's definitely for another thread... Cheers and a big thanks again folks, Kostas