Hello All,

 

A few days ago, I experienced a power outage at my home. I do have a UPS, which does not last that long, but usually my server is able to shutdown gracefully. However, when my server restarted, a couple of my shares were not reachable. This happened to me before. As before, I started the array in Maintenance mode and checked the disk file systems. After reviewing the logs, I determined that Disk 2 was having a problem.

 

After the reiserfsck check was completed on Disk 2 and recommendations given, I ran reiserfsck again with the --rebuild tree option. This seemed to work fine, based on completion of all three passes. The only odd thing is that my parity check started running while that was happening.

 

Now when I start the array, after taking a while to mount the drives, it shows that Disk 2 is unmounted and does not have a filesystem. The only option available is to format, which I am leary of doing without some advice. It is also interesting that  when I click on those previously unreachable shares now, they show all of the data, when before the system said they were empty reflecting the problem.

 

Please see my logs attached. What course of action do you recommend?

 

Thanks in advance for your help.

 

bhingi

arcadia-diagnostics-20170802-0823.zip

DO NOT FORMAT. Wait for the file system experts to chime in here

Sent from my LG-D852 using Tapatalk

You are having a lot of errors on both disk2 (sdh) and disk1 (sde):

 

Aug  1 06:58:54 Arcadia kernel: sd 4:0:0:0: [sdh] tag#0 CDB: opcode=0x88 88 00 00 00 00 00 c1 f0 36 30 00 00 01 00 00 00
Aug  1 06:58:54 Arcadia kernel: scsi target4:0:0: handle(0x0009), sas_address(0x4433221100000000), phy(0)
Aug  1 06:58:54 Arcadia kernel: scsi target4:0:0: enclosure_logical_id(0x500605b004794670), slot(3)
Aug  1 06:58:54 Arcadia kernel: sd 4:0:0:0: task abort: SUCCESS scmd(ffff8800ab16c480)
Aug  1 06:59:00 Arcadia kernel: mpt2sas_cm0: log_info(0x31110d01): originator(PL), code(0x11), sub_code(0x0d01)
Aug  1 06:59:27 Arcadia kernel: sd 4:0:0:0: attempting task abort! scmd(ffff8800ab16c180)
Aug  1 06:59:27 Arcadia kernel: sd 4:0:0:0: [sdh] tag#0 CDB: opcode=0x88 88 00 00 00 00 00 c1 f2 ab 30 00 00 01 00 00 00
Aug  1 06:59:27 Arcadia kernel: scsi target4:0:0: handle(0x0009), sas_address(0x4433221100000000), phy(0)
Aug  1 06:59:27 Arcadia kernel: scsi target4:0:0: enclosure_logical_id(0x500605b004794670), slot(3)
Aug  1 06:59:27 Arcadia kernel: sd 4:0:0:0: task abort: SUCCESS scmd(ffff8800ab16c180)
Aug  1 07:00:00 Arcadia kernel: sd 4:0:0:0: attempting task abort! scmd(ffff8800ab16c480)
Aug  1 07:00:00 Arcadia kernel: sd 4:0:0:0: [sdh] tag#0 CDB: opcode=0x88 88 00 00 00 00 00 c1 f5 2f 30 00 00 02 00 00 00
Aug  1 07:00:00 Arcadia kernel: scsi target4:0:0: handle(0x0009), sas_address(0x4433221100000000), phy(0)
Aug  1 07:00:00 Arcadia kernel: scsi target4:0:0: enclosure_logical_id(0x500605b004794670), slot(3)
Aug  1 07:00:00 Arcadia kernel: sd 4:0:0:0: task abort: SUCCESS scmd(ffff8800ab16c480)
Aug  1 07:00:06 Arcadia kernel: mpt2sas_cm0: log_info(0x31110d01): originator(PL), code(0x11), sub_code(0x0d01)
Aug  1 07:00:06 Arcadia kernel: mpt2sas_cm1: log_info(0x31110d01): originator(PL), code(0x11), sub_code(0x0d01)
Aug  1 07:00:15 Arcadia kernel: mpt2sas_cm1: log_info(0x31110d01): originator(PL), code(0x11), sub_code(0x0d01)
Aug  1 07:00:23 Arcadia kernel: mpt2sas_cm0: log_info(0x31110d01): originator(PL), code(0x11), sub_code(0x0d01)
Aug  1 07:00:31 Arcadia kernel: mpt2sas_cm1: log_info(0x31110d01): originator(PL), code(0x11), sub_code(0x0d01)
Aug  1 07:01:06 Arcadia kernel: sd 1:0:3:0: attempting task abort! scmd(ffff8800975dd500)
Aug  1 07:01:06 Arcadia kernel: sd 1:0:3:0: [sde] tag#3 CDB: opcode=0x88 88 00 00 00 00 00 02 94 1d 68 00 00 04 00 00 00
Aug  1 07:01:06 Arcadia kernel: scsi target1:0:3: handle(0x000c), sas_address(0x4433221104000000), phy(4)
Aug  1 07:01:06 Arcadia kernel: scsi target1:0:3: enclosure_logical_id(0x500605b0046a1790), slot(7)
Aug  1 07:01:06 Arcadia kernel: sd 1:0:3:0: task abort: SUCCESS scmd(ffff8800975dd500)

 

SMART looks fine for both so check/replace cables or connect the on a different controller.

 

Only after these errors are gone should you attempt to run reiserfsck again.