Thanks, I did run reiserfsck using whole partition. It recovered a lot more files....but.... I know have this problem.

 

mount /dev/sdj1 disktemp/

mount: /dev/sdj1: can't read superblock

 

It won't  mount the disk....when I try fdisk /dev/sdj I get these results:

 

 

The device presents a logical sector size that is smaller than

the physical sector size. Aligning to a physical sector (or optimal

I/O) size boundary is recommended, or performance may be impacted.

 

Command (m for help): p

 

Disk /dev/sdj: 4000.8 GB, 4000787030016 bytes

256 heads, 63 sectors/track, 484501 cylinders, total 7814037168 sectors

Units = sectors of 1 * 512 = 512 bytes

Sector size (logical/physical): 512 bytes / 4096 bytes

I/O size (minimum/optimal): 4096 bytes / 4096 bytes

Disk identifier: 0x00000000

 

  Device Boot      Start        End      Blocks  Id  System

/dev/sdj1              1  4294967295  2147483647+  ee  GPT

Partition 1 does not start on physical sector boundary.

 

Command (m for help): ^C

 

 

run reiserfsck -check.

 

Post the command and output from the terminal session.

root@Tower:/mnt# reiserfsck --check /dev/sdb
reiserfsck 3.6.24

Will read-only check consistency of the filesystem on /dev/sdb
Will put log info to 'stdout'

Do you want to run this program?[N/Yes] (note need to type Yes if you do):Yes
###########
reiserfsck --check started at Wed Apr 15 22:05:38 2015
###########
Replaying journal: Done.
Reiserfs journal '/dev/sdb' in blocks [18..8211]: 0 transactions replayed
Checking internal tree.. finished                                
Comparing bitmaps..finished
Checking Semantic tree:
finished                                                                       
No corruptions found
There are on the filesystem:
Leaves 899927
Internal nodes 5470
Directories 45359
Other files 111251
Data block pointers 890881028 (1690601 of them are zero)
Safe links 0
###########
reiserfsck finished at Thu Apr 16 00:51:01 2015
###########
root@Tower:/mnt# 

So, at this point, I am just trying to save the data. I have already replace the disk. I am just trying to find a way to mount the disk and extract what I can from the drive. Any ideas how to get this to mount?

So, the below is what I get when I try and mount the disk:

 

root@Tower:/mnt# mount /dev/sdb1 disktemp/
mount: /dev/sdb1: can't read superblock
root@Tower:/mnt# reiserfsck --rebuild-sb /dev/sdb
reiserfsck 3.6.24

Will check superblock and rebuild it if needed
Will put log info to 'stdout'

Do you want to run this program?[N/Yes] (note need to type Yes if you do):Yes
Reiserfs super block in block 16 on 0x810 of format 3.6 with standard journal
Count of blocks on the device: 976754640
Number of bitmaps: 29809
Blocksize: 4096
Free blocks (count of blocks - used [journal, bitmaps, data, reserved] blocks): 86620797
Root block: 23644
Filesystem is clean
Tree height: 5
Hash function used to sort names: "r5"
Objectid map size 972, max 972
Journal parameters:
Device [0x0]
Magic [0x0]
Size 8193 blocks (including 1 for journal header) (first block 18)
Max transaction length 1024 blocks
Max batch size 900 blocks
Max commit age 30
Blocks reserved by journal: 0
Fs state field: 0x0:
sb_version: 2
inode generation number: 0
UUID: d5cae947-8342-4fce-b9b9-ad2af5e04215
LABEL: 
Set flags in SB:
Mount count: 1
Maximum mount count: 30
Last fsck run: Thu Apr 16 00:51:01 2015
Check interval in days: 180

Super block seems to be correct

root@Tower:/mnt# 

 

root@Tower:/mnt# mount /dev/sdb1 disktemp/
mount: /dev/sdb1: can't read superblock
root@Tower:/mnt# reiserfsck --rebuild-sb /dev/sdb

 

And there is your problem .... You tried to mount /dev/sdb1, which is correct, but then ran reiserfsck on /dev/sdb, which is incorrect ... reiserfsck should have been run on /dev/sdb1.

 

I'm not sure if this is recoverable or not.

That is the expected result

 

You should be specifying /dev/sdb1 as the device (i.e. you need to also mention the partition) when using raw devices.

Thanks, that fixed it.

So just to give you an update on how it all worked out and for future reference.

 

When the disk showed unformatted (originaly a reiserfs), I ran a reiserfsck on the correct partition (/dev/sdb1). When I tried the whole disk option i used:

 

reiserfsck --rebuild-tree -S  /dev/sdb

 

Anyway, this made the drive unmountable (plus whatever else I screwed up). 

 

I thought I messed up the drive so I ran reiserfsck without the whole disk option ( reiserfsck --rebuild-tree  /dev/sdb)...this recovered about 1.5 TBs of ~4 TBs of files.  I copied off what I could just to make sure I got a little back. I made sure only to copy of the drive to prevent any writes.  I then ran reiserfsck with the whole disk option, and I believe I recovered almost all of the files. (will never know)  Luckily, that partition held the Apple Time Machine backup files, so I can just redo that on my Mac.

 

So, even if you accidentally run reiserfsck on the whole disk, vice that partition, you can still go back and get your files. (at least a subset of them).

 

Thanks for all the help.

 

I am still a bit confused - you should never have run reiserfsck against /dev/sdb - it should always have been against /dev/sdb1 even when using the --rebuild-tree option.  That may be why you lost some files I suspect.

Sorry to confuse you. I understand I should not have done that. The purpose of the post to explain what happens when it has been done. I just wanted to provide some feedback to the forum on what happens. 

 

A little more info.. I think I did get back almost all files, but they all ended up in weird directories like 4_1716 , 34557_25345, etc. But the files are there.