Sorry -- it's a USB device so the drive letter has changed as I've moved the drive around.
My friend threw a theory out there -- maybe the beginning of the partition is incorrect on the drive? The drive originally had an NTFS partition. By blowing away the beginning of the drive and then rewriting the partition table, maybe the kernel was using the original "beginning" location of the NTFS partition which *may* be incorrect for the beginning of the reiserfs /dev/sdX1 partition. I did *NOT* reboot after making changes to the partition table (nor did I disconnect / reconnect the drive). Is this possible? I'm 99.99999% sure this drive is not defective. There has to be some way to mount this partition as it was cleanly unmounted and the data copied over with no issues when I was originally doing it. Isn't there a way to search for a superblock on the drive and then use that when attempting to mount the partition? -james On Tue, Aug 24, 2010 at 12:31 PM, Mick <michaelkintz...@gmail.com> wrote: > On 24 August 2010 15:46, James <j...@nc.rr.com> wrote: >> Yep, positive. Just checked through my history: >> >> mkreiserfs -f /dev/sdd1 >> mount /dev/sdd1 /mnt/backup > > Hmm ... if you have made a fs on sdd1, why are you trying to mount > sdf1 in your first post? > > ... or is sdd1 now being recognised by udev as sdf1? > > I am not sure I can suggest anything better than what you have already > tried. I have recovered umpteen reiserfs corruptions with no loss of > data so far, by running reiserfsck --fix-fixable, or --rebuild-tree. > However, none of these problems were due to a problematic drive or USB > cable - your case may be different and recovery less successful. > > Of course, if you have storage space somewhere else it is always a > good idea to use dd to image the partition first before you start your > recovery attempts. > -- > Regards, > Mick > >
