I think I'm in a world-of-hurt: I was "running out" of room on the partition that held the pages served by my webserver [running on SuSE 7.x, meaning they were "hosted" under /usr/local/httpd] so I decided to copy the "tree" to another partition where I would then alter the .conf file to point to the new partition [which I was intending to call "/srv/www", since that seems to be the way 8.x/9.x does it] HOWEVER, at some point in the copy process "things went bad", and the system locked up. [we're talking flashing caps/scroll lock lights] During the reboot and subsequent transaction replay [reiser], I got a null pointer exception and the system hung again -- rebooting THIS time returned "cannot find a valid reiserfs partition on 09:00" OK, "rescue CD" time -- took a while to "remember" exactly how I had this system set up, but in a nutshell it's like this: two identical hard drives [10gb apiece -- IBM deskstars as I recall] partitioned the same down the line. /dev/hd[ab]5 is joined together as a "raid" device and is known as /dev/md0 -- this is my "root" directory. The rest of the partitions: /dev/hd[ab][6-8], are joined together as "volume groups" -- vg00/system is "/var", vg01/data is "/home", and vg02/backup is "/ snapshot", which is where I was moving my webpages to [largest free space...] reiserfsck reported it couldn't find a superblock, so I tried to "force" the creation of a new one with parameter "--rebuild-sb" -- here is where I might have shot myself in the foot: rebuild-sb suggested a block size of 4096, however I recalled that during the boot sequence when it couldn't find anything on device 09:00 that there were references to a 1024-byte block size, so I overrode "4096" with "1024". I then found out/realized/whatever that I also had to perform a "--rebuild-tree" operation, and this is the scary part: the program reported THOUSANDS of "size (...) should be (...)" error messages where the first and second elipses seemed to toggle between 0 and 1000. NOW reiserfsck reports "FATAL corruption found" -- worse still, the "--rebuild-tree" operation fails with "no reister metadata found whatsovever, have you repartitioned?" [or words to similar effect] and goes on to suggest a "quick fix" on how to find/identify the actual original superblock [the presumption being that you've re-partitioned and "moved" things around] So, "am I hosed"? Where do I go from here? I know I haven't "repartitioned" the drive, so the hinted-at help in the reiserfsck program won't help. -- Yet another Blog: http://osnut.homelinux.net