Unexpected power outage in 3PAR storage, one of the volumes cannot be remounted

[Finally_]

Storage: 3par 7000

Host: redhat 6. x Kernel: 2.6

Storage configuration:

12 virtual volumes assigned to 4 hosts (host1, honst2, host3, host4)

Fault symptom:

The storage unexpectedly lost power. After restarting, it was discovered that a controller was malfunctioning and was subsequently replaced. After all storage faults were resolved, the host began to remount the disk. At this point, it was found that the volume in host2 could be mounted and read normally, but could not be written. Subsequently, a restart operation was performed on the host. After restarting, one of the four virtual disks of the host could not be mounted, with the following prompt:

notes：Note: dm-18 is the partition of dm-8

~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~

[root@host2 /]# mount -t ext3 /dev/dm-8 /test11

mount: /dev/dm-8 already mounted or /test11 busy

[root@host2 /]# mount -t ext3 /dev/dm-18 /test11

mount: wrong fs type, bad option , bad superblock on /dev/dm-18missing codepage or other errorIn some cases useful info is found in syslog - trydmesg tailor so

~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~·~~~

Name:                    mpath4
State:                     ACTIVE
Read Ahead:         256
Tablespresent:      LIVE
Open count:          1
vent number:        1
Major，minor:      253，8
Number of targets: 1

UUID:                       mpath-360002ac00000000000000014000040f7

~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~

Name:                    mpath4P1
State:                     ACTIVE
Read Ahead:         256

Tablespresent:      LIVE
Open count:          0
vent number:        0
Major，minor:      253，18
Number of targets: 1 

UUID:                       part1-mpath-360002ac00000000000000014000040f7

~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~

[Mahesh202 · Accepted solution]

Hi

The error message indicates there may be a problem with the file system or superblock on the /dev/dm-18 partition.
Here are some steps you can take to try and resolve the issue:

Check the file system: You can run the fsck command on the partition to check for errors and repair any file system issues. For example, you can run the following command:

fsck /dev/dm-18
This command will scan the file system on the /dev/dm-18 partition and attempt to repair any errors.

Check the superblock: If the file system appears to be intact, but the superblock is corrupted, you can try to restore it from a backup. You can use the e2fsck command with the -b option to specify a backup superblock. For example, you can run the following command:

e2fsck -b 32768 /dev/dm-18
This command will attempt to restore the superblock using the backup superblock located at block 32768.

Check the disk for errors: If the file system and superblock appear to be intact, but you are still having issues mounting the partition, you may want to check the disk for errors. You can use the badblocks command to check the disk for bad sectors. For example, you can run the following command:

badblocks -v /dev/dm-18
This command will scan the disk for bad blocks and report any errors it finds.

Restore from backup: If none of the above steps are successful, you may need to restore the data from a backup. You should ensure that you have a recent backup of the data before proceeding with any data restoration.

Hope this helps.!!

Regards
Mahesh.

[Finally_]

Hi Mahesh

Thank you for your reply. The problem has been resolved. After investigation, there was an error in the customer's record information. The dm-18 in the previous phenomenon has been suspended from use

[Mahesh202]

Hi

I'm glad to hear that the problem has been resolved. It's important to thoroughly investigate and identify any errors or discrepancies in the configuration or records to ensure the smooth functioning of the system.
If you have any further queries, we will be happy to assist you.

Regards
Mahesh.

If you feel this was helpful please click the KUDOS! thumb below!
Note: All of my comments are my own and are not any official representation of HPE.