I was having the same problem as Can no longer save or delete a pedalboard or switch pedalboards so I tried to install the 1.1RC2 release. The install seemed to complete fine but when it rebooted it just stays on the logo screens and never gets to knob 1 etc.
The networking is not working. Neither the browser or ssh can connect.
After letting it sit on the logo screen for about 10 min I unplugged it and plugged it in again but it still stays on the logo screen.
How to reproduce
see description
Expected/suggested solution
Replace this text with how you would expect this to work.
Additional information
Open the controller menu (hold left knob down), navigate to Info > Versions and write down here the versions.
release: 1.1 RC2
controller:???
Also provide some information about your system if possible.
I tried manually installing 1.1RC3 by holding down the left knob and footswitch during power on and it installed but still hung at the logo screen afterwards. I have just manually installed 1.0.6 using the same method and now it has booted to the knob #1 screens.
Unfortunately, now I’m back to the Bug! Couldn’t save pedalboard problem. I am also unable to install any plugins.
This may have started when I tried to Update All from the plugins page. I had a pedal board that used gxtubescreamer loaded and the Update All seemed to hang when installing the newer version.
Now when I try to load a pedalboard with a gxtubescreamer, the ui for that plugin is blank:
I have switched to the default pedalboard and tried removing the gxtubescreamer plugin but it pops up a Failed to uninstall plugin message. Trying to Upgrade it just results in it hanging on the installing plugin popup:
For situations like this It would be nice to have a “complete factory reset” feature for the MOD (reset all plugins, clear all user-data etc). One can backup important pedalboards to the cloud by sharing them before wiping the MOD.
PS. I suppose it’s already possible using the command-line via ssh (also backup the /root/ directory which holds user-data), but I highly recommend to wait for official support to chime in before going that way.
Since ssh allows password again in 1.1, it should be easy to script a backup solution.
Pedalboards and banks are just text files, plus the screenshots.
Plugins can be installable at any time, just by loading the pedalboard that contains them.
@jalbrecht You most likely have a read-only user partition now, and that’s why managing plugins and saving pedalboards does not work.
Please install 1.1.0-RC3, which should fix that. Sadly the install fails sometimes, and you need to retry.
We need to make this more robust, sorry for the issues.
user ‘root’, pw ‘mod’.
note that you can only log in using pw in 1.1.
also btw…
plugins are in /root/.lv2 (not really important unless you deployed your own custom versions)
pedalboards are in /root/.pedalboards
the rest of the data is in /root/data (banks and last used pedalboard)
the user data is never modified during updates and reinstalls.
@falkTX can onepossible to clear all data? [quote=“falkTX, post:7, topic:712”]
the user data is never modified during updates and reinstalls.
[/quote]
How can one reset the /root/ folder (or all user-data) to be exactly like a new MOD shipped from the factory? ie a complete factory reset?
Sorry for hijacking this thread somewhat. While fixing things and keeping all data intact is definitely the better option, a “quick & reliable” way to reset the whole device would be cool.
In any case it’s easy to get the (updated) plugins again and pedalboards can be backed-up in the cloud simply by sharing them (no ssh backups are just icing on the cake)
1 Unplug the mod
2 hold down the left knob and switch.
3 plug in the mid while holding down the knob and switch
4 wait 5 seconds before releasing the knob and switch
5 plug in the usb port to computer when asked and mod connects as a mass storage device
6 copy the release tar file to the mod
7 eject the mod (I’m using the file manager in ubuntu for copying and ejecting the device)
8 mod lights go red and update messages go by
9 mod lights go green and mod screens show the logo then lights go off
10 mod stays on the logo screen instead of getting to the knob #1 screen
The 1.0.6 release is making it to the knob #1 screen (normal boot) using the steps above.
There is no major difference between 1.1 and 1.0 that would make this fail for 1.1.
If you power off first, then hold down the buttons before turning on, the 1.1 will install correctly.
Well I’ll try again tonight but as you can see from my last post, I do hold the buttons down before turning on. So far since starting this topic, I’ve tried to install 1.1-rc3 six times and 1.1-rc2 once with no success but I have installed 1.0.6 twice with no problems booting up.
Finally had time today to try again but no luck. This time I downloaded the 1.1 final release and tried installing it four times with no success. Just to check my ability to perform the install, I installed 1.0.6 and it booted successfully.
So since the start of this thread I have tried to install the 1.1 series release (rc2, rc3, final) ten times with zero success and the 1.0.6 release three times with 100% success. All of the installs were done using the “hold down left knob and switch” while powering on method (see Mod won’t boot after manual install for details)
I appreciate that there’s nothing in the 1.1 series releases that should prevent boot up but I think you’ll agree the install stats I’ve had suggest that’s not the case. Any thoughts on a plan B would be greatly appreciated as I don’t think there is any use in my trying to install 1.1 any more.
Would it be possible to get a 1.0.6 custom build with ssh password auth enabled? I’m more that happy to do any debugging on my end.
I just went through the same thing. I installed 1.1.1 via the gui and it worked fine, then I powered down and loaded up for the gig. At the gig it never got past the logos screen. Got home, read this thread, and then installed 1.0.6. It’s rebooted and seems to be fine. I’m going to wait a while and check the forums and see if anyone else has experienced anything similar.
Sorry to hear you’re seeing the same thing I am. I haven’t had time to try 1.1.1 yet but given your experience I don’t think it will solve my problem.
If 1.0.6 is working for you then I guess you haven’t run into the read-only user partition problem. It might be that the 1.1 booting issue is actually separate from the read-only user partition problem.
Good news, I was able to reproduce a similar issue with 1.1.
Apparently the automatic recovery of data partition (being there just in case something goes wrong) is not working correctly.
I was able to manually fix a bad partition, but the automatic system failed.
Investigating…
