UNSOLVED

Docleroux

updated

7 years ago

D

Docleroux

1 Message

0

2308

May 6th, 2019 14:00

VNX e3150 VMFS Datastore critical failure (25)

Hello,

I am troubleshooting a vnxe with a performance storage pool.  On this single storage pool there are 2 VMFS datastores.  One data store is working fine and the other is showing a critical failure (25) in the health state.  Is there anything that can be done to recover or fix the data on the datastore?  If I run svc_storage_integritycheck  I get below.  I am confused because this datastore resides on the same storage pool as another good datastore.

 

service@(none) spa:~> svc_storage_integritycheck 
=================================================
List of unmounted/corrupt storage elements found:
=================================================
1 -> vol_1_1406805509(corrupted)
=================================================
Please enter the item you would like to fix from the list, or enter "q" to quit: 1

###########################################################################
WARNING: Attempting to fix this corruption may take a long time to complete
###########################################################################
Enter "yes" if want to proceed with this action: yes
Running check on: 1 -> vol_1_1406805509
-- Please wait for status to say "Done..Done" before proceeding --
Error 5: Input/output error
Failed to run fsck on vol_1_1406805509
service@(none) spa:~>

1: ID = app_2
LUN ID = 1
Name = Per-Data-01
Description =
Health state = OK (5)
Node = iscsi_node_0
iSCSI target = iqn.1992-05.com.emc:apm001432067460000-1-vnxe
Storage pool = performance
Size = 2089072721920 (1.9T)
Protection size = 0
Protection size used = 0

2: ID = app_3
LUN ID = 2
Name = Cap-Data-01
Description =
Health state = OK (5)
Node = iscsi_node_0
iSCSI target = iqn.1992-05.com.emc:apm001432067460000-1-vnxe
Storage pool = capacity
Size = 2188028936192 (2.0T)
Protection size = 0
Protection size used = 0

3: ID = app_1
LUN ID = 0
Name = Per-Data-02
Description =
Health state = Critical failure (25)
Node = iscsi_node_0
iSCSI target = iqn.1992-05.com.emc:apm001432067460000-1-vnxe
Storage pool = performance
Size = 2089072721920 (1.9T)
Protection size = 0
Protection size used = 0

  • DELL-Sam L

    Community Manager

    8058 Posts

    34386 Points

    1828

    0

    Posted May 13th, 2019 13:00

    Hello Docleroux,

    Have you tried to run the following command to see if the host can see the partition?

    partedUtil getptbl /vmfs/devices/disks/

    If you can see the partition, then I would run the following command to try & fix it.

    partedUtil fix /vmfs/devoces/disks/ - try to fix it

    Here is also a link to some other steps that you can use to try to recover the partition.

    https://vmwaremine.com/2014/06/23/use-partedutil-recover-damaged-vmfs5-gpt-partition/#sthash.F4Dyl1pE.dpbs

    Please let us know if you have any other questions.

  • DELL-Sam L

    Community Manager

    8058 Posts

    34386 Points

    1170

    0

    Posted September 28th, 2020 13:00

    Hello Docleroux,

    Here is a link to a KB that maybe of assistance. https://dell.to/3cL4QMz

  • DELL-Sam L

    Community Manager

    8058 Posts

    34386 Points

    591

    0

    Posted May 18th, 2022 08:00

    Hello mitjax,

    What is your current OE of your vnxe system?  Did you run out of space on your datastore?

  • DELL-Sam L

    Community Manager

    8058 Posts

    34386 Points

    577

    0

    Posted May 18th, 2022 14:00

    Hello mitjax,

    Here is a link to a kb that maybe of assistance. https://dell.to/3Pt3ity

  • DELL-Sam L

    Community Manager

    8058 Posts

    34386 Points

    133

    0

    Posted May 19th, 2022 11:00

    Hello mitjax,

    You can’t repair a lun as a service user, as in most cases that can only be done as administrator or via support. You can try the steps listed in these 2 kb’s to see if they help. 

    https://dell.to/3FZgWjU

    https://dell.to/3My3N3x

  • 1180

    0

    Posted September 26th, 2020 10:00

    for me occur same problem

     

    service@(none) spb:~> svc_storage_integritycheck
    =================================================
    List of unmounted/corrupt storage elements found:
    =================================================
    1 -> vol_15_1404129159(corrupted)
    =================================================
    Please enter the item you would like to fix from the list, or enter "q" to quit: 1

    ###########################################################################
    WARNING: Attempting to fix this corruption may take a long time to complete
    ###########################################################################
    Enter "yes" if want to proceed with this action: yes
    Running check on: 1 -> vol_15_1404129159
    -- Please wait for status to say "Done..Done" before proceeding --
    Error 5: Input/output error
    Failed to run fsck on vol_15_1404129159
    service@(none) spb:~>

     

     

    its not in vmware but on storage. how i can solve this ?

     

     

  • mitjax

    6 Posts

    605

    0

    Posted May 18th, 2022 02:00

    I am in the same situation. But I can't access the article you posted. Any suggestions?

  • mitjax

    6 Posts

    413

    0

    Posted May 18th, 2022 05:00

    Have you managed to solve your issue?

  • mitjax

    6 Posts

    595

    0

    Posted May 18th, 2022 06:00

    I've managed to get access to the article, but that info are a bit scarce.Could you please elaborate a little bit more? Should I first check the type using /nas/bin/nas_server -l? If this is correct, I get permission denied running that command.

    Help appreciated.

    Br,
    Mitja

  • mitjax

    6 Posts

    579

    0

    Posted May 18th, 2022 11:00

    Storage system: VNXe3150
    Software version: 2.4.4.22638

    The storage pool has 114 GB of free space. On this pool there are 7 generic iSCSI storage "drives" all working except one. It could be that it run out of space, as users are heavy on it. But there was also en event: Storage Servers configured for SPA have stopped and will be restarted. After the restart of SPA the storage elements associated with storage resource started operating normally except one.

    If you need me to diagnose something, please let me know what should I do.

    Thanks.

    Mitja