IcerJo

  • Posts

    19
  • Joined

Profile Information

  • Gender
    Male

Recent Profile Visitors

The recent visitors block is disabled and is not being shown to other users.

IcerJo's Achievements

  1. Thank you @Igor, my apologies and thank you for all you and the team do. I plan to donate to Armbian when some of my remodeling projects are done. and That would be swell @Heisath, I did see in the FAQ's that we may not be "supported" Officially but we are in a Community type of support, so if you were able to acquire and run Edge/Nightly that would definitely help out in the long run
  2. I wonder if someone could buy it and donate it to Armbian for testing so that we could be Supported again? If anyone does buy and donate I will donate to them
  3. I see you updated your Device, there is a known issue with the kernel in question, there is another thread that details how you can revert back to the old .43 kernel to regain access. If you look the following post/instructions you should be good to go. I'm curious as to why no one referred you to that post. I know the title of the Thread is about upgrading to Bullseye but it also got sidetracked to troubleshooting Armbian 21.08.1 and the EMMC read only error/problem.
  4. Just after 24hours system randomly rebooted while i was out of the house, so back to the old trick of setting the max to 1.4ghz and min to 408mhz
  5. I opted to just setup an SD Card with the latest, and redo my OMV install on it, since that's technically all I use it for at this time, I was able to get the old system booted with no problems by pushing re-pushing the bootloader but wasn't able to install the Deb files, and I am not that confident in my linux skill set, though i learned a few new tips and tricks during the troubleshooting! I'll repush to EMMC once issues have eventually been resolved, or i may downgrade the kernel and push, i'll see later. Thank you @ebin-dev for your advice and assistance and thank you @TDCroPower for the RSync article!
  6. Thank you for the Rsync guide, I'm going to give this a try real quick, I had to modify the parameters since i had my usb SD card reader mounted as /media/USB, the rsync just finished. I'm going to shutdown, and pop the SD Card in and see what happens
  7. If you can SSH in or possibly boot off of an SD card with the latest image, you can reinstall the bootloader, it at least gets it up and running, least for me that means I can get in and see my drives and wrote to the, but I fear the emmc is still somewhat locked down but yet it lete turn ash back on. Sent from my Pixel 4a (5G) using Tapatalk
  8. Seems like it doesn't make it fully writeable, but it does let the system boot and I'm able to access all of my files and save some changes in the system, like turn some services on and off. But I couldnt write the 3 files to the emmc to do a downgrade so unless I messed up I am at a loss but would gladly try the above mentioned. Sent from my Pixel 4a (5G) using Tapatalk
  9. In Essence I did what you stated but by using armbian-config to re-push the bootloader. How would one go about making the emmc Write-able in order to install the 3 packages to downgrade the kernel? Or would I need to re-setup OpenMediavault and everything, and run it from the SDcard or copy it over to the emmc from the SD Card with the old kernel, and then do a kernel freeze for time being till issue is resolved?
  10. Ahh, so it's essentially a ticking time bomb? I pushed the bootloader from an SD card and got my system back up yesterday.
  11. I don't know much when it comes to armbian, but from the temp fix I did, it seems like the bootloader was the culprit/issue, I installed/pushed a new bootloader via the latest image on an sd card and my system is back up and running with the latest kernel with no problems. Or rather i think it might be a combination of issues, I am not sure how the bootloader being pushed would work if the kernel is the culprit but at least my system is back up and stable till they have a proper fix implemented. I read another Post where its a Kernel Panic that Occurs at 150372 seconds = 41.7 hours..
  12. Thanks, I guess I'll stick with what works/caused me to be stable for this long [emoji16] Edit: I opted to start fresh and am testing the stability of the new kernel's Govenor and cpu frequencies via SD Card till they fix the EMMC issue's which then at that time i will push Armbian back to the EMMC. So far 22 hours with no problems. Sent from my Pixel 4a (5G) using Tapatalk
  13. Any update? I know I set my Max and Minimum cpu frequencies to the same for both the 4 cores and 2 upper cores. and never looked back lol If ondemand and cpu frequencies have been fixed that would probably add some robustness.
  14. Howdy Igor! A workaround I found that seems to work for me, was to boot from the latest release from an SD card, and update the bootloader. It seemed to let me back in and stopped giving me the login loop i was experiencing. I am running Buster.