@Seth hey Seth, I found a thread you made talking about your Technogym bike - did you ever figure out how to fix that error with the init script?

@Carl hm, don't think that was me. I've never had any kind of computerized exercise equipment, as much as I'd like a bike or a treadmill.

Do you have a link to the thread?

let me see if I can find it, sec

askubuntu.com/questions/662334/…

looks like it wasn't you who asked the question, you just tried to help

that's the quoted link in question

ahhh. Wow I don't even remember that haha.

Yeah, not my question. I did leave a comment, but there isn't/wasn't much we could do there. That's a very specific piece of equipment.

@Carl I'm curious, what lead you to that message?

extensive googling, hahaha

I've found so little information on these bikes

I was gonna say, you'd probably have to go pretty far down google to find an SE chat link. Are you experiencing a similar problem?

yeah I have the exact same issue, same bike too as far as i can tell

I'm able to get a shell on the bike, can connect my keyboard and throw commands at it, but beyond that I have little idea what I would need to do

No init found. Try passing init=bootarg Busy box v1.13.3 (Ubuntu 1:1.1.13.3-1ubuntu7) - I'm not even sure where I'd pass that flag to

> No init found. Try passing init=bootarg

I'd try googling that (if you haven't already), and see if any of the answers for other machines makes sense for your situation.

It's hard to give any specific advice since so much would depend on how exactly technogym set everything up, what hardware there is, etc.

You might be able to use blkid to find a filesystem (if there is one) and could then maybe try repairing with with fsck. Assuming it's a repairable filesystem error. I can't really help more, but that might offer a jumping off point :)

Here's a list of commands you should have access to: boxmatrix.info/wiki/BusyBox-Commands

@Seth thanks for the advice Seth, sorry for the delay