Clean Install of OMV7 Hangs - Multiple attempts

  • I have attempted 5 or 6 times to update to OMV7 / bookworm. The upgrade path has not been successful for me and i switched to clean installation. Use a clean download of Rasbperry PI OS Lite and set up SD Card with it. It boots, I get OS set up including fan and expanding FS, I run OMV Script, everything installs and comes up great.


    If I make a change -

    add a plugin
    authorize myself for SSH
    set up shared folders


    And reboot - it bricks. I have sat 15 minutes hoping it will start up - but it never does. I can power off, watch the drive boot for 45 seconds or less, then no drive activity - sometimes a flash here or there every 5 seconds or so. I can't SSH in. and website is not up.

    I have tried eliminating plugins, i have tried only configuring SMB/CIFS to try and eliminate if it is a specific plugin - but regardless of my attempts. every time I get OMV set up and credentials created - if I reboot it, it bricks.

    jimmy

    simplicity is the ultimate sophistication.

  • KM0201

    Approved the thread.
    • Official Post

    Connect a monitor and see what happens during boot.


    Does it reboot if you only install the OS?


    Did you follow this guide?

    omv6:raspberry_pi_install [omv-extras.org]

  • I understand them like this... after installing OMV and a reboot, the Raspi does not start. including fan and expanding FS... What does that mean? Expanding Filesystem takes place after installing RasberryPiOS and rebooting. Including fan, I interpret that they install or configure a fan controller. To do this, you will certainly edit the config.txt. After that, they install OMV and when rebooting, the Raspi does not start.

    I would proceed like this: Install RaspiOS lite (64Bit), restart, configure sensibly using raspi-config, restart and then reinstall OMV. Leave any other things (fan control) out, do not tinker with the config.txt and see if the Raspi reboots and OMV runs.

  • For clarity - what you are describing is what i have done. OMV comes up fine the first boot. But if you configure it and reboot it, like adding a user to OMV or turning on SMB/CFS and tell the system to reboot - it hangs on reboot. Bricked.

    jimmy

    simplicity is the ultimate sophistication.

  • macom yes I followed the guide step by step. There aren't error messages and everything seems to be working, you just get a hang. The RASPI is headless, but I can haul it up and hook to monitor to see what's onscreen during hang.

    jimmy

    simplicity is the ultimate sophistication.

    • Official Post

    I would proceed like this: Install RaspiOS lite (64Bit), restart, configure sensibly using raspi-config, restart and then reinstall OMV. Leave any other things (fan control) out, do not tinker with the config.txt and see if the Raspi reboots and OMV runs.

    No. You're not following -> the guide. There's no "raspi-config" in the guide. Follow the guide to the end. Once OMV is installed and running, if you configure something else and things go south, you'll know what happened.

    That that said, I haven't configured OMV7/Bookwork, on an R-PI, using the existing OMV6 guide. To use the OMV6 guide, start with RaspiPS lite (64Bit) "Bookworm". That should be the only difference.

    If you have trouble with the install, while actually following the guide, post again and I'll do a test run.

  • No. You're not following -> the guide. There's no "raspi-config" in the guide. Follow the guide to the end. Once OMV is installed and running, if you configure something else and things go south, you'll know what happened.

    That that said, I haven't configured OMV7/Bookwork, on an R-PI, using the existing OMV6 guide. To use the OMV6 guide, start with RaspiPS lite (64Bit) "Bookworm". That should be the only difference.

    If you have trouble with the install, while actually following the guide, post again and I'll do a test run.

    I have been building systems since you were in diapers I expect. I can follow an install - I can also follow when your install Bricks a device. Just trying to help here, man.

    jimmy

    simplicity is the ultimate sophistication.

  • No. You're not following -> the guide. There's no "raspi-config" in the guide. Follow the guide to the end. Once OMV is installed and running, if you configure something else and things go south, you'll know what happened.

    That that said, I haven't configured OMV7/Bookwork, on an R-PI, using the existing OMV6 guide. To use the OMV6 guide, start with RaspiPS lite (64Bit) "Bookworm". That should be the only difference.

    If you have trouble with the install, while actually following the guide, post again and I'll do a test run.

    oddly enough - my inability to follow a guide has OMV6 working like a top as it has for a year. But i digress.

    As stated, OMV7 comes up just fine, the trouble comes when you configure it. In my testing of now 7 times deep, I can consistently cause a brick by enabling the SMB/CIFS service. I did try the install script that does not include networking with similar results.

    I have also tried the in-place upgrade twice unsuccessfully..

    If I were to leave the install running without rebooting it - it will run for hours and I can even transfer a Time Machine backup to the external SSD. However - a reboot, and I'm a brick. I have tried this with 3 different RPI boards before you go there, and also 3 different SD-Cards.

    As close as I can come to determining the variable - it appears to be the configuration of SMB/CIFS - or setting up a shared folder on an attached SSD which is using EXT4. I can mount the storage drive, and re-share the shared folders. I can browse the contents. But if i reboot - history.

    jimmy

    simplicity is the ultimate sophistication.

  • I understand them like this... after installing OMV and a reboot, the Raspi does not start. including fan and expanding FS... What does that mean? Expanding Filesystem takes place after installing RasberryPiOS and rebooting. Including fan, I interpret that they install or configure a fan controller. To do this, you will certainly edit the config.txt. After that, they install OMV and when rebooting, the Raspi does not start.

    I would proceed like this: Install RaspiOS lite (64Bit), restart, configure sensibly using raspi-config, restart and then reinstall OMV. Leave any other things (fan control) out, do not tinker with the config.txt and see if the Raspi reboots and OMV runs.

    some clarity here as I was summarizing the install process. My PI is mounted in an ARGON40 case which uses the I2C header to control an onboard fan based on temperature. ARGON40 has their script posted on GITHub and it is part of my standard build process of an RPI using the argon 40 to perform the following steps after initial install of SD Card.

    sudo apt update
    sudo apt upgrade -y
    reboot
    sudo raspi-config (expand filesystem). Standard step on Raspbi Builds
    Enable I2C
    reboot
    Install Argon 40 via GITHub
    sudo argon-config (or whatever their command is) set fan to come on at 50C
    reboot
    Run OMV Install Script from https://github.com/OpenMediaVa…-Developers/installScript


    For testing purposes I have eliminated the Argon 40 installation as well as skipping the raspi-config sequences during initial setup of PI - same results. OMV7 is fine and can be rebooted until you configure it with SMB or Shared Folders then it bricks.




    jimmy

    simplicity is the ultimate sophistication.

  • For those who are interesting in testing OMV7
    _______________________________________________________
    On the R-PI4:

    I've found that it's possible to build OMV7 using the latest Raspberry Pi Imager (1.8.4)
    - Select the R-PI4
    - OS is under "Other" Select Raspberry PI OS Lite (64bit) Bookworm
    - Under General Preset the user and name (To be used for SSH logon)
    - Under Services, enable SSH with a password
    (I didn't change anything else.)

    When logged in by SSH:

    sudo apt-get update

    sudo apt-get upgrade -y

    sudo reboot

    Login with SSH again and run the script:

    wget -O - https://github.com/OpenMediaVa…Script/raw/master/install | sudo bash

    After the reboot, check your DHCP server for the assigned IP and login.


    The issue seems to be with systemd networking.  Don't change network settings or attempt to activate the wireless interface. That results in the R-PI dropping off the network. Rebooting does not change anything.

    That's not to say that there may be other issues. At this point I don't know. but realize that OMV7 is still "testing in an RC1 phase".

  • not meaning to be difficult here - seriously! But that is roughly the process I have already followed. To be clear, I'm not making any changes to networking other than what OMV does itself. I'm simply going under services and enabling them.

    jimmy

    simplicity is the ultimate sophistication.

  • I will follow this process again this morning and note the steps . I'll note where we hang. Hopefully we don't!

    jimmy

    simplicity is the ultimate sophistication.

  • My PI is mounted in an ARGON40 case which uses the I2C header to control an onboard fan based on temperature

    This mean it's a Pi4 with a Argon40 ONE v2, correct?

    I can try it once I get home in 2 weeks time and see how it goes.


    Until now, I only tested the NEO for Pi5 and it worked flawless, although the fan is now controlled by the RaspiOS PWM.


    I'm waiting for the ONE for Pi5 that is on transit to my house and I hope I also have it there once I go back.
    Strange is that I don't see any script yet for it. Since the FAN is PWM and there's a power button on the Pi5, there's no need for an I2C controlled function.


    I have been building systems since you were in diapers I expect.

    :/ :/ :/

    "This is NOT the way..."

  • PI Imager v1.8.4 MacOS
    Choose - Raspberry PI OS Lite (64-Bit) Release 2023-12-11
    256GB Sandisk Ultra 190Mb/s SD Card (target)

    SSH Service Enabled.
    set hostname "mystorage.local"
    Locale Settings America/New_York, us Keyboard
    SSH User Created with password and SSH (my standard options)
    (wifi not enabled)

    Install SD Card into PI4B 8GB.
    Connected gigabit Ethernet (headless) in argon40 case
    with USB3.0 SSD option and 2TB M.2 SSD.


    ssh user@mystorage.local
    sudo apt update && sudo apt upgrade -y
    sudo reboot

    ssh user@mystorage.local
    wget -O - https://github.com/OpenMediaVa…Script/raw/master/install | sudo bash

    "ERROR 404 not found"
    (tried twice)

    sudo wget -O - https://github.com/OpenMediaVa…Script/raw/master/install | sudo bash

    (install runs and completes in approximately 12 minutes and notifies of reboot.)
    (no failures reported)


    login to http://mystorage.local using default Admin and openmediavault.
    Change admin password , logout, login

    Reboot
    Comes back up less than 1 min.

    login
    users - (myaccount) set password.

    confirm pending changes


    Services

    SMB/CIFS

    Settings

    (check enabled)
    apply pending changes.

    (takes about 45 seconds)


    reboot (power, reboot, confirm)

    it's been 5 minutes now - still no website.

    jimmy

    simplicity is the ultimate sophistication.

  • correct on V2 - just went thru process again and it bricks as soon as you enable SMB/CIFS as far as I can tell.

    sorry about the snark.. X/

    jimmy

    simplicity is the ultimate sophistication.

  • It's now been 20 minutes - this is the behavior i expected. I run the PI headless inside of an alarm box in my basement, no other electronics in there other than a 2.5gb Switch. I can pull the PI and hook to my monitor to see if it has onscreen messages but unfortunately I don't have a monitor near a LAN port in my home, so I can't run with a monitor and keyboard "in production"


    for now I'm popping the card with OMV6 back in.

    jimmy

    simplicity is the ultimate sophistication.

  • reboot (power, reboot, confirm)

    it's been 5 minutes now - still no website

    Can you check if the IP changed either on the router or with a IP scanner tool?

    Or just ping the IP to see if it's still the same.


    On a side note, I had an issue on pi5 with the network.

    All it took was to disable the predictable network names on raspi-config.


    There's already several threads with successfull updates/installs of OMV7 on Pi4.

    Curious if it's some issue with the ONE itself.


    argon40 case
    with USB3.0 SSD option and 2TB M.2 SSD.

    Is your case the v2 (no bottom addons)or the M2 (m.2 addon bottom board)?

  • It's now been 20 minutes - this is the behavior i expected. I run the PI headless inside of an alarm box in my basement, no other electronics in there other than a 2.5gb Switch. I can pull the PI and hook to my monitor to see if it has onscreen messages but unfortunately I don't have a monitor near a LAN port in my home, so I can't run with a monitor and keyboard "in production"


    for now I'm popping the card with OMV6 back in.

    I believe i have uncovered the issue. I hooked the PI up to my monitor and noticed it was booting just fine and querying for a network. Dug in the basement and found a long long cat5 and hooked it up. Saw that the PI is getting the proper reserved IP address - it seems to just be dropping the hostname.

    Logging into IP address directly system works at website.
    also works for SSH.

    my clients are going to look for hostname of "mystorage.local". any idea why the hostname is getting dropped?

    jimmy

    simplicity is the ultimate sophistication.

Participate now!

Don’t have an account yet? Register yourself now and be a part of our community!