You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I haven't been able to boot my Pi for two weeks. Everytime I boot it gets stuck in
end kernel panic - not syncing: VFS: Unable to mount root fs on unknown-blick(179,2)
I tried using a keyboard to enter recovery mode using shift but the keyboard doesn't get recognized.
I tried to edit the file cmdline.txt in the boot fs from my linux desktop and changing the line
root=/dev/mmcblk0p2
What did you expect to happen instead?
na
How to reproduce this bug?
na
Additional information:
No response
The text was updated successfully, but these errors were encountered:
Is MainsailOS not maintained directly by the Mainsail team? I cannot get past this issue. I didn't install anything externally. All that I have to do to get here is Install MainsailOS using Raspberry Pi Imager. Run all updates using Mainsail Update Manager. Then, if I restart my pi it will boot into this issue.
@Trevo525 same team, but this is the wrong repo for MainsailOS issues. but in general we do not use the github issue tracker for support, but only to manage the project (bugreports & feature requests). for support please use our discord.
PS: but the error looks to me as if your SD card/filesystem has a defect.
Thanks, I have tried three microSD cards that were all brand new and this happens everytime. I have it working now using KIAUH instead. You can close this now though.
Browser:
Chrome
Device:
Desktop PC
Operating System:
Windows
What happened?
I haven't been able to boot my Pi for two weeks. Everytime I boot it gets stuck in
end kernel panic - not syncing: VFS: Unable to mount root fs on unknown-blick(179,2)
I tried using a keyboard to enter recovery mode using shift but the keyboard doesn't get recognized.
I tried to edit the file cmdline.txt in the boot fs from my linux desktop and changing the line
root=/dev/mmcblk0p2
What did you expect to happen instead?
na
How to reproduce this bug?
na
Additional information:
No response
The text was updated successfully, but these errors were encountered: