Closed illmaren closed 2 years ago
The script changes networking to using netplan. Some routers are bad and don't hand out the same address or even a new address. Rebooting the router usually fixes this. The script can't change bad routers. Please read the install guide because this is covered - https://forum.openmediavault.org/index.php?thread/28789-installing-omv5-on-raspberry-pi-s-armbian-sbc-s-i386-32-bit-platforms/
This issue is for the bootloop caused by the watchdog only. This has been fixed on the RPi family.
The bootloop issue on all arm boards should be fixed now.
You should have no problem installing on Armbian Buster though.
I`ve tested yesterday with Armbian Buster and the script and it worked fine indeed. Thx.
I'm still having an issue with watchdog and the current script (I'm using a RPI 3B+). It took me a while track down this was this issue, since I had fresh-installed (raspbian bullseye -> install script) onto a HDD perfectly fine earlier this week. When I switched to an SSD yesterday, I thought the new hardware was the case... but it's definitely watchdog.
Either way... after using the current script (commit "ca7da1b")... openmediavault-watchdog.conf
is still reporting that it's set to 5 mins.
RuntimeWatchdogSec=5min
I'm going try jae-hyup's pre-configuration steps and see if that'll get me past this snag. Ideally, I'd like this to work without too much customization... but I may end up attempting to disable watchdog as much as I can if this keeps up.
I really shouldn't have nuked that HDD, and waited a bit (so much for green-blue testing), haha.
There is a thread on the forum about this. If you are using the 32bit Raspberry Pi OS, it is still broken in a different way. None of this is caused by the script though. So, we have to wait for an OMV fix again. https://forum.openmediavault.org/index.php?thread/41699-stuck-in-part-of-the-installation/
Hm, good thing this is being tracked fast. Too bad I stepped in at the wrong time to test this out, though.
What's reported there are pretty much the same issues I'm having (except the networking, I don't think I've gotten to a point where I can test it's disabled after getting to a live session... only that it doesn't come online due to rebooting).
I'll try out some of these workarounds and see if I get a system going (watchdog still seems like the culprit at the moment)... I haven't tried the 64-bit version of a distro for this, cause I wanted to keep things stock... but if I get down the line and I'm still hitting a snag, I'll try it.
I don't have forum membership, might need to make one to chime in. Thanks.
edit : looks like you've tracked down the offending issue... it's always a typo, hah!
I haven't created an account on the forums yet, but since you replied here I thought I'd do the same just to wrap up.
After the 42fe730
commit, I am able to reach a usable install with the RPI 3b+ following the intended instructions while using the install script. The base OS is Raspbian lite with the "default" 32-bit kernel.
Everything appears to be working as it should without customization to any salt or bash scripting, so I'd call this successful. Thank you for the quick response and hammering out those commits!
Hardware: Fresh and new Raspberry 4b 8gb 32gb SD Card from Sandisk
Software: https://downloads.raspberrypi.org/raspios_lite_arm64/images/raspios_lite_arm64-2021-11-08/ Flashed with Rufus 3.8.1580
What happens? After
the Raspberry is stuck in a bootloop and Raspbian needs to be newly flashed to the SDCard