Ask the Community
Groups
Failed to prepare archive media for use - Connect IT Community | Kaseya
<main> <article class="userContent"> <h2 data-id="issue"><strong>ISSUE</strong></h2> <p>Failed to prepare device 'Recovery Archive' for use: Failed to create archive filesystem<br>Failed to prepare archive media for use</p> <h2 data-id="resolution"><strong>RESOLUTION</strong></h2> <p><br><br><br><br><br># dmesg | grep I/O<br><br>end_request: I/O error, dev sdg, sector 493720592<br>end_request: I/O error, dev sdg, sector 3907019792<br>end_request: I/O error, dev sdg, sector 3907018768<br><br>This is indicating there is an issue with sdg<br><br>Some additional torubleshooting<br>Attempt to prepare the storage from the command line.<br><br># mdadm --detail /dev/md99<br><br>/dev/md99:<br> Version : 1.2<br> Creation Time : Tue Oct 10 15:32:37 2017<br> Raid Level : raid0<br> Array Size : 15628070912 (14904.09 GiB 16003.14 GB)<br> Raid Devices : 4<br> Total Devices : 4<br> Persistence : Superblock is persistent<br><br> Update Time : Tue Oct 10 15:32:37 2017<br> State : clean<br> Active Devices : 4<br>Working Devices : 4<br> Failed Devices : 0<br> Spare Devices : 0<br><br> Chunk Size : 1024K<br><br> Name : SJCRecovery:99 (local to host SJCRecovery)<br> UUID : 9ad95abd:f78031b5:4075a7e8:57c6eb73<br> Events : 0<br><br> Number Major Minor RaidDevice State<br> 0 8 48 0 active sync /dev/sdd<br> 1 8 64 1 active sync /dev/sde<br> 2 8 80 2 active sync /dev/sdf<br> 3 8 96 3 active sync /dev/sdg<br><br><br># mdadm --examine /dev/md99<br>mdadm: No md superblock detected on /dev/md99. (This is bad)<br><br><br># mkfs.xfs -f /dev/md99<br><br>Error:<br>mkfs.xfs: pwrite64 failed: Input/output error (This is also bad)<br><br>Next you can attempt to write a filesystem to the other device to verify if they need to be replaced.<br><br><br>First stop md99<br><br># mdadm --stop /dev/md99<br><br>Next try to write a filesystem to each device<br><br><strong>(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.)</strong><br><br>Make sure to only run against drives listed in above mdadm --detail /dev/md99 command<br><br># mkfs.xfs -f /dev/sdx<br><br>mkfs.xfs -f /dev/sdg<br>meta-data=/dev/sdg isize=256 agcount=4, agsize=244188662 blks<br> = sectsz=512 attr=2, projid32bit=0<br>data = bsize=4096 blocks=976754646, imaxpct=5<br> = sunit=0 swidth=0 blks<br>naming =version 2 bsize=4096 ascii-ci=0<br>log =internal log bsize=4096 blocks=476930, version=2<br> = sectsz=512 sunit=0 blks, lazy-count=1<br>realtime =none extsz=4096 blocks=0, rtextents=0<br>mkfs.xfs: pwrite64 failed: Input/output error<br><br><br>Replace the drive or drives that you can not write a filesystem to.</p> </article> </main>