Failed to prepare archive media for use - Connect IT Community

/* * These styles apply ONLY to the header and footer assets. */ * { padding: 0; margin: 0; box-sizing: border-box; } .super-nav { display: flex; justify-content: flex-end; align-items: center; margin: 0 auto; max-width: 1264px; padding-left: 40px; padding-right: 40px; height: 40px; text-align: right; } .super-nav a { color: #34427c; margin-right: 20px; padding: 10px; text-decoration: none; } .super-nav a:hover, .super-nav a:focus { background-color: #f7f9fa; } .footer { background: #f5f5f6; color: #555a62; font-size: 14px; line-height: 1.5; padding: 0; } .footer-image { background-image: url("/themes/kaseya/assets/images/footerImage.png"); height: 500px; background-repeat: no-repeat; background-size: cover; margin-top: -100px; } .footer-wrap { padding-left: 18px; padding-right: 18px; max-width: 1236px; margin: 0 auto; } .footer-main-content { background-color: #000; padding: 100px 0; } .footer .footer-col-title { color: #ffffff; font-weight: 700; font-size: 13px; padding-bottom: 10px; text-transform: uppercase; } .footer .footer-link { color: #9b9ca0; text-decoration: none; } .footer .footer-link:hover, .footer .footer-link:focus, .footer .footer-link:active { text-decoration: underline; } .footer-main-content .footer-link { padding-top: 10px; } .footer-row { display: flex; flex-wrap: wrap; justify-content: space-between; align-items: center; margin: -3px; } .footer-main-content-row { align-items: flex-start; } .footer-bottom-content { padding: 10px; align-items: center; } .footer-col { padding: 0 3px; display: flex; flex-direction: column; } .footer-col-copyRight { justify-content: flex-start; color: #9b9ca0; flex: 1; display: flex; } .footer-last-col { flex-direction: row; } .footer-last-col .footer-link { padding-right: 10px; text-transform: uppercase; } @media screen and (max-width: 768px) { .super-nav { padding-right: 0; } .footer-image { height: 250px; } .footer-main-content { padding: 40px 0; } .footer .footer-col-title { padding-top: 10px; } .footer-row:not(.footer-main-content-row) { display: block; } .footer-col:not(.footer-main-content-col) { width: 100%; text-align: center; padding: 10px 0; } .footer-main-content-col { width: 50%; } .footer-last-col { flex-direction: column; } .footer-last-col .footer-link { padding-bottom: 10px; } } /*# sourceMappingURL=styles.css.map */ Ask the Community Groups

Failed to prepare archive media for use - Connect IT Community | Kaseya

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 torubleshooting
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 above mdadm --detail /dev/md99 command

# mkfs.xfs -f /dev/sdx

mkfs.xfs -f /dev/sdg
meta-data=/dev/sdg isize=256 agcount=4, agsize=244188662 blks
= sectsz=512 attr=2, projid32bit=0
data = bsize=4096 blocks=976754646, imaxpct=5
= sunit=0 swidth=0 blks
naming =version 2 bsize=4096 ascii-ci=0
log =internal log bsize=4096 blocks=476930, version=2
= sectsz=512 sunit=0 blks, lazy-count=1
realtime =none extsz=4096 blocks=0, rtextents=0
mkfs.xfs: pwrite64 failed: Input/output error

Replace the drive or drives that you can not write a filesystem to.