Ask the Community
Groups
Archive disk does not appear on rescan - Connect IT Community | Kaseya
<main> <article class="userContent"> <h2 data-id="summary"><strong>SUMMARY</strong></h2> <p>An archive drive may no longer be recognized after rescanning due to potential conflicts with other jobs running.</p> <h2 data-id="issue"><strong>ISSUE</strong></h2> <p></p> <ul><li>Archive drive is not recognized after rescaning</li> <li>uarchive log complains about drive not responding and running 'hotplug scan' shows that the drive is not responding</li> </ul><pre class="code codeBlock" spellcheck="false" tabindex="0"> 0 (3750): Apr 01 15:03:49 : [LOG2] rpcutil.c:154: Executing command: /usr/bp/bin/uarchive-scripts/scan.sh 0 (3750): Apr 01 15:03:58 : [LOG2] Command exit code: 0 0 (3750): Apr 01 15:03:58 : [LOG2] Command stderr (diagnostic output): 0 (3750): Scanning for hotplug devices... 0 (3750): device "sdb" not removable 0 (3750): <b>device "sdc" not responding</b> 0 (3750): device "sda" not removable # hotplug scan <b>device "sdc" not responding</b> device "sdb" not removable device "sda" not removable current removable devices: kernel: __ratelimit: 19 callbacks suppressed kernel: sd 3:0:0:0: [sdc] Unhandled error code kernel: sd 3:0:0:0: [sdc] Result: hostbyte=DID_BAD_TARGET driverbyte=DRIVER_OK kernel: sd 3:0:0:0: [sdc] CDB: Read(10): 28 00 00 00 00 00 00 00 20 00 kernel: __ratelimit: 19 callbacks suppressed kernel: Buffer I/O error on device sdc, logical block 0 kernel: Buffer I/O error on device sdc, logical block 1 kernel: Buffer I/O error on device sdc, logical block 2 kernel: Buffer I/O error on device sdc, logical block 3 kernel: sd 3:0:0:0: [sdc] Unhandled error code</pre> <h2 data-id="resolution"><strong>RESOLUTION</strong></h2> <p>Check when "disk_mon" is running in cron. If "disk_mon" is attempting to read the drive at the same time we are scanning or removing it, the time when "disk_mon" is running should be changed to a less problematic time.<br><br>Note: Y<i>ou must restart the cron service after making any changes.</i> </p> <pre class="code codeBlock" spellcheck="false" tabindex="0"> # crontab -l 0 12 * * * /usr/bp/bin/disk_cleanup.sh * * * * * /usr/bp/bin/cmc_host_statistics -1 >> /usr/bp/logs.dir/cmc_host_statistics.log 2>&1 0,15,30,45 * * * * /usr/bp/bin/cleanupHungBpsyncProcesses 0 15 * * * /usr/bp/bin/adaptiveDedupRatios -i >/dev/null 2>&1 0 * * * * /usr/bp/bin/failure_report.php >/dev/null 2>&1 30 6 * * * /usr/bp/bin/processSpaceAlert.php >/dev/null 2>&1 0 9 * * * php /var/www/html/recoveryconsole/bpl/reports/replication_report.php -f >/dev/null 2>&1 <b>0,30 * * * * /bin/cp /var/tmp/disk_mon.out /var/tmp/disk_mon.out.bak; /usr/bp/bin/disk_monitoring.py -s -c >/var/tmp/disk_mon.out 2>&1 </b>0 0 * * 0 /usr/bp/bin/ana_snmptrap_sender.py -a -c >/var/tmp/ana_snmptrap_sender.out 2>&1 0 20 * * * /usr/bp/bin/inventory_sync >/dev/null 2>&1 45 * * * * /usr/bp/bin/summary_counts 7 >/dev/null 2>&1 */15 * * * * /usr/bp/bin/sync_summary.php -r >/dev/null 2>&1 0 12 * * * php /var/www/html/recoveryconsole/bpl/gfslite.php >/dev/null 2>&1 */5 * * * * /etc/init.d/bp_rcscript start</pre> In the above crontab, there are various other jobs set to run at the top of the hour. By changing "disk_mon" to run at 15 and 45 minutes after the hour, we avoid possible conflicts with other jobs: <pre class="code codeBlock" spellcheck="false" tabindex="0"> 15,45 * * * * /bin/cp /var/tmp/disk_mon.out /var/tmp/disk_mon.out.bak; /usr/bp/bin/disk_monitoring.py -s -c >/var/tmp/disk_mon.out 2>&1</pre> Once you have made the change, restart cron: <pre class="code codeBlock" spellcheck="false" tabindex="0"> service crond restart</pre> </article> </main>