Difference between revisions of "Troubleshooting Reinstall"

From MOD Wiki
Jump to navigation Jump to search
 
(71 intermediate revisions by 4 users not shown)
Line 1: Line 1:
−
[[File:Duo-fel-button.jpg|450px|thumb|Location of the FEL button on the MOD Duo]]
+
General Troubleshooting section, divided by possible issues.
  
−
== MOD boots into restore mode by default ==
+
== MOD boots the main system, but screens do not work ==
  
−
If the main MOD OS becomes unbootable for some reason, the MOD will automatically boot into restore mode (used for performing OS updates).<br>
+
If the MOD is able to boot (verified by still providing USB Ethernet device) but the screens do not seem to work properly, we can try to re-flash the "top-board"/screen controller unit.<br/>
−
You know the MOD is in restore mode if the inputs and output leds are blue and the display says "plugin USB cable to PC" or "copy file, eject and unplug".
+
This can happen, for example, if the MOD lost power during the last step of the update process.
  
−
When this happens we need to force a new installation of the MOD OS.<br>
+
This is fixable by reflashing the controller firmware, which can be done through the web interface or SSH.
−
We do this by starting the restore mode with a special "force install" flag.
 
  
−
The method for starting this special mode is:
+
=== reflashing controller via web interface ===
  
−
# Turn off your MOD
+
Open the [http://192.168.51.1/settings.html|web interface advanced settings] (accessible in the bottom-right corner of the regular web interface), then navigate to the "DANGEROUS" area.<br/>
−
# Hold the left knob and footswitch down
+
Simply follow the instructions for the "Reflash controller" section of the page.
−
# Turn on the MOD (while still holding the knob and footswitch down)
 
−
# Wait 5 seconds and let go of the knob and footswitch <br/> The MOD is now booting into restore mode, but will allow the installation of any valid MOD release (including the same as already installed or downgrades).
 
−
# Connect the MOD to your PC (if not done yet) and wait for a new mass storage drive to appear
 
−
# Download the latest release from [[Releases]]
 
−
# Copy the modduo*.tar file onto the new drive and use your OS option to safely remove the drive
 
−
# Disconnect the USB cable
 
  
−
On some rare cases the MOD might boot again in restore mode after this.<br>
+
[[File:Screenshot-advanced-settings-dangerous.png|thumb|Web interface advanced settings]]
−
If that happens please start over from step 1.
 
  
−
== MOD does not boot at all, not even restore mode ==
+
=== reflashing controller via SSH ===
  
−
If for some reason your MOD device does not boot at all - not even in forced-restore mode - we need to reinstall the OS inside.<br/>
+
Connect to 192.168.51.1 via SSH (user 'root' and password 'mod') and then run the following command:
−
You can perform a factory reset (which will erase all your data) or keep your data by reinstalling the system over USB.<br/>
 
−
The method for keeping user data only works on Linux at the moment.
 
  
−
=== Factory Reset ===
+
<code language="console">hmi-update /usr/share/mod/controller/mod*controller.bin</code>
  
−
Requirements: Linux or macOS, basic command-line knowledge
+
Wait until you get confirmation of the flashing process being complete, and then turn off and on the unit.
  
−
To begin:
+
== MOD does not boot ==
−
# Click and hold down the FEL button on the back of the MOD Duo (in tiny hole), while you power it on.
 
−
# Hold it for 2 seconds, then release
 
−
# Download this file: http://download.moddevices.com/releases/modduo/reset/modduo-v1.3.1.351-reset-image.raw
 
−
# Download https://github.com/moddevices/CT_NandBoot/archive/master.zip and extract it
 
−
# Open a terminal and 'cd' to the directory where master.zip was extracted, ie:
 
−
<code language="console">cd ~/Downloads/CT_NandBoot-master/</code>
 
  
−
If you're running '''macOS''', run:<br/>
+
If your unit seems unable to boot properly, we can force the unit to start in restore mode.<br>
−
<code language="console">./bootfix.osx -w ~/Downloads/modduo-v1.3.1.351-reset-image.raw</code><br/>
+
You know the MOD is in restore mode if the inputs and output leds are blue and the display says "plugin USB cable to PC" or "copy file, eject and unplug".
−
(adjust the path to 'modduo-v1.3.1.351-reset-image.raw' as needed)
 
  
−
If you're running '''Linux''' 64bit, run:<br/>
+
The method for manually starting recovery mode is:
−
<code language="console">./bootfix -w ~/Downloads/modduo-v1.3.1.351-reset-image.raw</code><br/>
 
−
(adjust the path to 'modduo-v1.3.1.351-reset-image.raw' as needed)
 
  
−
For non-64bit Linux systems, run 'make clean' and 'make' beforehand.
+
# Turn off your MOD
 +
# Hold the left knob and footswitch down (on the Dwarf and Duo X you can use the left endless-knob and the 1st button from the bottom-left)
 +
# Turn on the MOD (while still holding the knob and footswitch down)
 +
# Wait 5 seconds and let go of the knob and footswitch - the MOD is now booting into restore mode
 +
# Connect the MOD to your PC (if not done yet) and wait for a new mass storage drive to appear
 +
# Download the latest release from [[Releases]]
 +
# Copy the mod*.tar file you just downloaded onto the new drive and use your OS option to safely remove the drive
 +
# Disconnect the USB cable
 +
# Wait while the unit updates itself, it will reboot automatically when done
  
−
Continuing:
+
Note: On some rare cases a MOD Duo might boot again in restore mode after this. If that happens please start over from step 1.
−
# Wait until the 'bootfix' process finishes
 
−
# Power off and on the MOD Duo (by replugging the power cable)
 
−
# Wait until its LEDs turn blue, after around 30 seconds. If the LEDs don't light up after one minute, replug the power cable once again
 
−
# Wait until the LEDs turn red, then green. This should take around 10 minutes.
 
  
−
Once the LEDs are green, the MOD Duo has finished its factory reset.<br/>
+
== MOD boots into recovery mode automatically ==
−
Power it off and on again one last time, and it will be good as new :)
 
  
−
----
+
If the main MOD OS kernel becomes unbootable, the MOD will automatically boot into restore mode (used for performing OS updates).<br>
 +
You know the MOD is in restore mode if the inputs and output leds are blue and the display says "plugin USB cable to PC" or "copy file, eject and unplug".
  
−
=== Reinstall via USB boot ===
+
If this happens, we need to reinstall the latest release, which will allow the unit to boot normally again.<br>
 +
Simply allow the unit to boot into recovery mode, and then:
  
−
Requirements: Linux, basic command-line usage
+
# Connect the MOD to your PC (if not done yet) and wait for a new mass storage drive to appear
−
 
+
# Download the latest release from [[Releases]]
−
To begin:
+
# Copy the mod*.tar file you just downloaded onto the new drive and use your OS option to safely remove the drive
−
# Click and hold down the FEL button on the back of the MOD Duo (in tiny hole), while you power it on.
+
# Disconnect the USB cable
−
# Hold it for 2 seconds, then release
+
# Wait while the unit updates itself, it will reboot automatically when done
−
# Connect the MOD Duo to your computer via USB cable
 
−
# Download http://download.moddevices.com/releases/modduo/reset/mod-boot-fel-restore.tar.gz and extract it
 
−
# Open a terminal and 'cd' to the directory where mod-boot-fel-restore.zip was extracted, ie:
 
−
<code language="console">cd ~/Downloads/mod-boot-fel-restore/</code>
 
  
−
If not you're running 64bit, install sunxi-tools from your Linux distribution, and copy /usr/bin/sunxi-fel to the current directory, overriding the existing file there.<br/>
+
== MOD does not boot at all, not even in restore mode ==
  
−
Continuing:
+
If for some reason your MOD device does not boot at all - not even in forced-restore mode - we need to reinstall the bootloader or perhaps the entire OS inside.
−
# Run: <code language="console">./boot-fel-restore.sh</code>
 
−
# Wait for around 2 minutes, and the MOD Duo will boot into recovery mode.
 
−
# Install a MOD OS release as usual.
 
  
−
Note: You can find all MOD OS software releases in the [[Releases]] section.
+
See the [[Troubleshooting Reinstall Dwarf]] page for how to reinstall the MOD OS in the Dwarf.<br/>
 +
See the [[Troubleshooting Reinstall Duo X]] page for how to reinstall the MOD OS in the Duo X.<br/>
 +
See the [[Troubleshooting Reinstall Duo]] page for how to reinstall the MOD OS in the Duo.

Latest revision as of 18:48, 26 February 2024

General Troubleshooting section, divided by possible issues.

MOD boots the main system, but screens do not work

If the MOD is able to boot (verified by still providing USB Ethernet device) but the screens do not seem to work properly, we can try to re-flash the "top-board"/screen controller unit.
This can happen, for example, if the MOD lost power during the last step of the update process.

This is fixable by reflashing the controller firmware, which can be done through the web interface or SSH.

reflashing controller via web interface

Open the interface advanced settings (accessible in the bottom-right corner of the regular web interface), then navigate to the "DANGEROUS" area.
Simply follow the instructions for the "Reflash controller" section of the page.

Web interface advanced settings

reflashing controller via SSH

Connect to 192.168.51.1 via SSH (user 'root' and password 'mod') and then run the following command:

hmi-update /usr/share/mod/controller/mod*controller.bin

Wait until you get confirmation of the flashing process being complete, and then turn off and on the unit.

MOD does not boot

If your unit seems unable to boot properly, we can force the unit to start in restore mode.
You know the MOD is in restore mode if the inputs and output leds are blue and the display says "plugin USB cable to PC" or "copy file, eject and unplug".

The method for manually starting recovery mode is:

  1. Turn off your MOD
  2. Hold the left knob and footswitch down (on the Dwarf and Duo X you can use the left endless-knob and the 1st button from the bottom-left)
  3. Turn on the MOD (while still holding the knob and footswitch down)
  4. Wait 5 seconds and let go of the knob and footswitch - the MOD is now booting into restore mode
  5. Connect the MOD to your PC (if not done yet) and wait for a new mass storage drive to appear
  6. Download the latest release from Releases
  7. Copy the mod*.tar file you just downloaded onto the new drive and use your OS option to safely remove the drive
  8. Disconnect the USB cable
  9. Wait while the unit updates itself, it will reboot automatically when done

Note: On some rare cases a MOD Duo might boot again in restore mode after this. If that happens please start over from step 1.

MOD boots into recovery mode automatically

If the main MOD OS kernel becomes unbootable, the MOD will automatically boot into restore mode (used for performing OS updates).
You know the MOD is in restore mode if the inputs and output leds are blue and the display says "plugin USB cable to PC" or "copy file, eject and unplug".

If this happens, we need to reinstall the latest release, which will allow the unit to boot normally again.
Simply allow the unit to boot into recovery mode, and then:

  1. Connect the MOD to your PC (if not done yet) and wait for a new mass storage drive to appear
  2. Download the latest release from Releases
  3. Copy the mod*.tar file you just downloaded onto the new drive and use your OS option to safely remove the drive
  4. Disconnect the USB cable
  5. Wait while the unit updates itself, it will reboot automatically when done

MOD does not boot at all, not even in restore mode

If for some reason your MOD device does not boot at all - not even in forced-restore mode - we need to reinstall the bootloader or perhaps the entire OS inside.

See the Troubleshooting Reinstall Dwarf page for how to reinstall the MOD OS in the Dwarf.
See the Troubleshooting Reinstall Duo X page for how to reinstall the MOD OS in the Duo X.
See the Troubleshooting Reinstall Duo page for how to reinstall the MOD OS in the Duo.

Retrieved from "http://wiki.mod.audio/index.php?title=Troubleshooting_Reinstall&oldid=13811"