Failed to prepare archive media for use, archive superblock failure

ISSUE

Failed to prepare device 'Recovery Archive' for use: Failed to create archive filesystem
Failed to prepare archive media for use

 

RESOLUTION


# dmesg | grep I/O

end_request: I/O error, dev sdg, sector 493720592
end_request: I/O error, dev sdg, sector 3907019792
end_request: I/O error, dev sdg, sector 3907018768

This is indicating there is an issue with sdg

Some additional troubleshooting
Attempt to prepare the storage from the command line.

# mdadm --detail /dev/md99

/dev/md99:
        Version : 1.2
  Creation Time : Tue Oct 10 15:32:37 2017
     Raid Level : raid0
     Array Size : 15628070912 (14904.09 GiB 16003.14 GB)
   Raid Devices : 4
  Total Devices : 4
    Persistence : Superblock is persistent

    Update Time : Tue Oct 10 15:32:37 2017
          State : clean
 Active Devices : 4
Working Devices : 4
 Failed Devices : 0
  Spare Devices : 0

     Chunk Size : 1024K

           Name : SJCRecovery:99  (local to host SJCRecovery)
           UUID : 9ad95abd:f78031b5:4075a7e8:57c6eb73
         Events : 0

    Number   Major   Minor   RaidDevice State
       0       8       48        0      active sync   /dev/sdd
       1       8       64        1      active sync   /dev/sde
       2       8       80        2      active sync   /dev/sdf
       3       8       96        3      active sync   /dev/sdg


# mdadm --examine /dev/md99
mdadm: No md superblock detected on /dev/md99. (This is bad)


# mkfs.xfs -f /dev/md99

Error:
mkfs.xfs: pwrite64 failed: Input/output error (This is also bad)

Next you can attempt to write a filesystem to the other device to verify if they need to be replaced.


First stop md99

# mdadm --stop /dev/md99

Next try to write a filesystem to each device

(CAUTION: Incorrect naming of /dev/sdx can direct to a storage drive instead of archive device. This should only be handled by those comfortable with linux bash shell, if unsure or concerned contact Support for process.)

Make sure to only run against drives listed in the above mdadm --detail /dev/md99 command. We can find archive disks using the command: # disk_monitoring_logger.py


E represents External Drive (Archive) in the above output

# mkfs.xfs -f /dev/sdX -- where X is the drive letter assigned

Note: This will format the data on the drive and allow us to re-use



Navigate to Configure > Backup Copy Targets section > select cold backup copy target > click "enable" and "Scan for media" to ensure no mount or communication errors.

If the issue persists, power cycle the appliance to ensure there are no communication errors between Appliance and the Recovery Archive device.

1. Shutdown the appliance.
2. Disconnect the cable(s) connecting the archives to the appliance.
3. Disconnect the power cable from the appliance.
4. Hold the power button down on the appliance for 15 seconds with the power cable disconnected.
5. Reconnect the power cable to the appliance and boot it up.
6. After it has been up for 1 minute, re-attach the archive unit.
7. Power on the Archive RXDA or Dock, navigate to configure > backup copy targets, and select archive device > "Erase" > and then click "Scan for media" to ensure no errors. Afterward, trigger cold backup copy job

null

Have more questions?

Contact us

Was this article helpful?
0 out of 0 found this helpful

Provide feedback for the Documentation team!

Browse this section