Ask the Community
Groups
System won't boot after applying updates - Connect IT Community | Kaseya
<main> <article class="userContent"> <h2 data-id="summary"><strong>SUMMARY</strong></h2> <p>System won't boot after applying updates</p> <h2 data-id="issue"><strong>ISSUE</strong></h2> <p><strong>Purpose</strong><br>System updated the OS won't load.<br><br><strong>Cause</strong><br>The most likely cause is a new kernel and unitrends-drivers packages did not get installed properly.<br><br><strong>Resolution</strong></p> <p>There are two primary symptoms that have been seen and three methods we can clear this issue without having to reimage the appliance:</p> <p> </p> <p>Option A: <a rel="nofollow" href="#h_01ENX9Z936TDYTBQS23QEEZBXB">The DPU fails to boot with “Error 15: unable to find file” or similar.</a></p> <p>Option B: <a rel="nofollow" href="#h_01ENX9ZT68R80JBB5WHZ420TVH">The DPU fails to boot with a kernel panic</a></p> <p>Option C: <a rel="nofollow" href="#h_01ENXA24J8Q9Y4EN927RG6T4F3">Rescue current Installation from image media:</a></p> <h2 id="h_01ENX9Z936TDYTBQS23QEEZBXB" data-id="the-dpu-fails-to-boot-with-error-15-unable-to-find-file-or-similar"> <br>The DPU fails to boot with “Error 15: unable to find file” or similar.</h2> <p> This has been seen on DPU 2000 and 3000. The reason is that the supplied grub.conf points to the kernel at /kernel-2.6.18…. and the initrd at /initrd-2.6.18…. when those are in the /boot directory. This can be remedied as follows:</p> <p>1. Let the system try to boot, and fail. Hit a key to continue once “Error 15” is seen.</p> <p>2. Hit “e” to edit the boot options.</p> <p>3. Select the kernel line and hit “e”, scroll back with the arrow keys and change</p> <p>kernel /vmlinuz-2.6.18-….</p> <p> To</p> <p>kernel /boot/vmlinuz-2.6.18-…</p> <p>Then, hit enter to commit</p> <p>4. Select the initrd line and hit “e”, scroll back with the arrow keys and change</p> <p>initrd /initrd-2.6.18-….</p> <p> To</p> <p> Initrd /boot/initrd-2.6.18-…</p> <p>Then, hit enter to commit</p> <p> </p> <p>5. Then “b” to boot</p> <p>6. Once booted, edit /boot/grub/grub.conf to have the same changes, and save that file.</p> <p> </p> <h2 id="h_01ENX9ZT68R80JBB5WHZ420TVH" data-id="the-dpu-fails-to-boot-with-a-kernel-panic">The DPU fails to boot with a kernel panic</h2> <p> This has been seen on many newer (x86_64) platforms. Multiple unitrends-config packages may have been installed as part of the update. This can be remedied as follows:</p> <p>1. Hit “e” to edit the boot options at boot time</p> <p>2. Select the kernel line and hit “e”, scroll back with the arrow keys and change</p> <p>root=/dev/sdaX</p> <p> to</p> <p>root=/dev/md0</p> <p>(This is for an 822 and most similar platforms – other platforms may need a different root device.)</p> <p>3. Hit “b” to boot</p> <p>4. Once booted, edit /boot/grub/grub.conf to have the same changes and save that file.</p> <p> </p> <h2 id="h_01ENXA24J8Q9Y4EN927RG6T4F3" data-id="rescue-current-installation-from-image-media">Rescue current Installation from image media:</h2> <ol><li>Create reimage media and set to boot from USB via <a href="https://kaseya.vanillacommunities.com/kb/articles/aliases/unitrends/hc/en-us/articles/360013198897" rel="noopener nofollow">How to reimage a Unitrends appliance</a> </li> <li>Boot from the RecoveryOS Factory Image DVD. </li> <li>Go to the option for '<strong>Rescue Installed System</strong>'.</li> <li>When the system starts to boot select boot with networking.</li> <li>You will be prompted that the system will try to locate the installed system, select or </li> <li>The system should be found and mounted to /mnt/sysimage.</li> <li>Type 'chroot /mnt/sysimage'. This makes the mounted disk the system root filesystem.</li> <li>Type 'service sshd start'. This will start the SSH daemon and will allow remote access via SSH to the system.</li> <li>Type 'yum reinstall unitrends-drivers'.</li> <li> <p id="list-the-installed-kernels">List the installed kernels</p> <pre class="code codeBlock" spellcheck="false" tabindex="0"># rpm -qa | grep kernel | sort dracut-kernel-004-411.el6.noarch<br>kernel-2.6.32-754.28.1.el6.x86_64<br>kernel-firmware-2.6.32-754.28.1.el6.noarch</pre> </li> <li>Now the kernel needs to be reinstalled.</li> <li>Type 'yum reinstall kernel-2.6.32-754.28.1.el6.x86_64'. <ol><li>You may have to remove it before you can reinstall it. If this is the case run this:</li> </ol></li> <li>'rpm -e --nodeps --justdb kernel-2.6.32-754.28.1.el6.x86_64' <ol><li>and then </li> </ol></li> <li>'yum install kernel-2.6.32-754.28.1.el6.x86_64'.</li> <li> Reboot</li> </ol><p><br>If you are unsure of <strong>ANY</strong> of these steps please call Unitrends for assistance. </p> </article> </main>