UD Mount Options

[thefly]

Trying to mount a failed drive that used to be in my array in an attempt to copy out data.  Is this completely dead or is there a potential to get it going?

Mar 24 10:56:31 Tower kernel: sd 1:0:1:0: [sdi] 2930277168 512-byte logical blocks: (1.50 TB/1.36 TiB)
Mar 24 10:56:31 Tower kernel: sd 1:0:1:0: [sdi] Write Protect is off
Mar 24 10:56:31 Tower kernel: sd 1:0:1:0: [sdi] Mode Sense: 00 3a 00 00
Mar 24 10:56:31 Tower kernel: sd 1:0:1:0: [sdi] Write cache: enabled, read cache: enabled, doesn't support DPO or FUA
Mar 24 10:56:31 Tower kernel: sdi: sdi1
Mar 24 10:56:31 Tower kernel: sd 1:0:1:0: [sdi] Attached SCSI disk
Mar 24 10:56:37 Tower emhttp: ST31500341AS_9VS1GLK5 (sdi) 1465138584
Mar 24 10:56:39 Tower emhttp: ST31500341AS_9VS1GLK5 (sdi) 1465138584
Mar 24 10:59:43 Tower emhttp: ST31500341AS_9VS1GLK5 (sdi) 1465138584
Mar 24 10:59:59 Tower unassigned.devices: Adding disk '/dev/sdi1'...
Mar 24 10:59:59 Tower unassigned.devices: Mount drive command: /sbin/mount -t reiserfs -o auto,async,noatime,nodiratime '/dev/sdi1' '/mnt/disks/ST31500341AS_9VS1GLK5'
Mar 24 10:59:59 Tower kernel: REISERFS (device sdi1): found reiserfs format "3.6" with standard journal
Mar 24 10:59:59 Tower kernel: REISERFS (device sdi1): using ordered data mode
Mar 24 10:59:59 Tower kernel: REISERFS (device sdi1): journal params: device sdi1, size 8192, journal first block 18, max trans len 1024, max batch 900, max commit age 30, max trans age 30
Mar 24 10:59:59 Tower kernel: REISERFS (device sdi1): checking transaction log (sdi1)
Mar 24 11:00:42 Tower kernel: sd 1:0:1:0: [sdi] tag#0 UNKNOWN(0x2003) Result: hostbyte=0x04 driverbyte=0x00
Mar 24 11:00:42 Tower kernel: sd 1:0:1:0: [sdi] tag#0 CDB: opcode=0x28 28 00 ad f2 a0 a8 00 00 08 00
Mar 24 11:00:42 Tower kernel: blk_update_request: I/O error, dev sdi, sector 2918359208
Mar 24 11:00:42 Tower kernel: REISERFS error (device sdi1): vs-13070 reiserfs_read_locked_inode: i/o failure occurred trying to find stat data of [1 2 0x0 SD]
Mar 24 11:00:42 Tower kernel: REISERFS (device sdi1): Remounting filesystem read-only
Mar 24 11:00:42 Tower kernel: REISERFS (device sdi1): Using r5 hash to sort names
Mar 24 11:00:42 Tower kernel: sd 1:0:1:0: [sdi] Read Capacity(16) failed: Result: hostbyte=0x04 driverbyte=0x00
Mar 24 11:00:42 Tower kernel: sd 1:0:1:0: [sdi] Sense not available.
Mar 24 11:00:42 Tower kernel: sd 1:0:1:0: [sdi] Read Capacity(10) failed: Result: hostbyte=0x04 driverbyte=0x00
Mar 24 11:00:42 Tower kernel: sd 1:0:1:0: [sdi] Sense not available.
Mar 24 11:00:42 Tower kernel: sdi: detected capacity change from 1500301910016 to 0
Mar 24 11:00:42 Tower unassigned.devices: Mount of '/dev/sdi1' failed. Error message: mount: /dev/sdi1: can't read superblock
Mar 24 11:02:35 Tower emhttp: device /dev/sdi zero-size
Mar 24 11:02:38 Tower emhttp: device /dev/sdi zero-size
Mar 24 11:02:52 Tower emhttp: device /dev/sdi zero-size
Mar 24 11:04:21 Tower emhttp: device /dev/sdi zero-size
Mar 24 11:04:57 Tower emhttp: device /dev/sdi zero-size
Mar 24 11:04:58 Tower emhttp: device /dev/sdi zero-size
Mar 24 11:04:59 Tower emhttp: device /dev/sdi zero-size
Mar 24 11:05:29 Tower emhttp: device /dev/sdi zero-size
 

[Squid]

doesn't look like a failed drive based on the error messages.  Simply a case of a corrupted ReiserFS filesystem

 

You should be able to run reiserfsck against the drive and get your stuff back.  Probably as a start,

reiserfsck --check /dev/sdi1

 

[thefly]

Next?

 

Do you want to run this program?[N/Yes] (note need to type Yes if you do):Yes

 

The problem has occurred looks like a hardware problem. If you have
bad blocks, we advise you to get a new hard drive, because once you
get one bad block  that the disk  drive internals  cannot hide from
your sight,the chances of getting more are generally said to become
much higher  (precise statistics are unknown to us), and  this disk
drive is probably not expensive enough  for you to you to risk your
time and  data on it.  If you don't want to follow that follow that
advice then  if you have just a few bad blocks,  try writing to the
bad blocks  and see if the drive remaps  the bad blocks (that means
it takes a block  it has  in reserve  and allocates  it for use for
of that block number).  If it cannot remap the block,  use badblock
option (-B) with  reiserfs utils to handle this block correctly.

bread: Cannot read the block (2): (Input/output error).

Aborted

[Squid]

Calling in the master @johnnie.black, before I get out of my comfort zone

[JorgeB]

That's a bad disk, reiserfsck will stop if it finds an unreadable sector, you can use ddrescue to clone the disk to a new one then run reiserfsck.