Error Boot

1st Official Post

    Hello everyone.

    I am a new member of the forum, I am 69 years old and I live in Italy.

    Unfortunately I do not know the English language, and for translations I use Google Translate, so I apologize if the translation is not correct.

    This is my problem.

    About two weeks ago I switched from OMV5 to OMV7, I managed to recover all the folders and everything works regularly.

    The only reason why I ask for help in this Forum is that when I turn on the NAS I get an error which at the moment does not affect its operation. This error did not appear in OMV5.

    The NAS has these components:

    ASUS M5A78L-M/USB3 motherboard

    SSD Samsung 128Gb (Which contains only the Operating System)

    32Gb memory

    5 HDD Seagate 4Tb in RAID 5, file system EXT4

    The network card is integrated into the motherboard.

    The error that I get after installing OMV7 is the following:


    /dev/sda1: clean, 52357/7757824 files, 1328972/31008256 blocks

    [ 4.363746] sp5100-tco sp5100-tco: Failed to reverse MMIO or alternate MMIO region

    [ 4.363787] sp5100-tco sp5100-tco: probe with driver sp5100-tco failed with error -16


    If you need further explanation, let me know.

    Thanks.

  • macom

    Approved the thread.

    Hello. I noticed that at every start the sequence of numbers changes.


    I don't know the cause.


    Can someone please give me a solution?


    Thanks.


    Start Date 2025.04.19 Hours 17:11


    /dev/sda1: clean, 52357/7757824 files, 1328972/31008256 blocks

    [ 4.363746] sp5100-tco sp5100-tco: Failed to reverse MMIO or alternate MMIO region

    [ 4.363787] sp5100-tco sp5100-tco: probe with driver sp5100-tco failed with error -16


    Start Date 2025.05.11 Hours 11:30


    /dev/sda1: clean, 47156/7757824 files, 1212852/31008256 blocks

    [ 4.212912] sp5100-tco sp5100-tco: Failed to reverse MMIO or alternate MMIO region

    [ 4.212949] sp5100-tco sp5100-tco: probe with driver sp5100-tco failed with error -16


    Start Date 2025.05.11 Hours 11:46


    /dev/sda1: clean, 47161/7757824 files, 1212851/31008256 blocks

    [ 4.337337] sp5100-tco sp5100-tco: Failed to reverse MMIO or alternate MMIO region

    [ 4.337374] sp5100-tco sp5100-tco: probe with driver sp5100-tco failed with error -16


    Start Date 2025.05.11 Hours 11:59


    /dev/sda1: clean, 47162/7757824 files, 1212857/31008256 blocks

    [ 4.146850] sp5100-tco sp5100-tco: Failed to reverse MMIO or alternate MMIO region

    [ 4.146889] sp5100-tco sp5100-tco: probe with driver sp5100-tco failed with error -16

    The numbers are time stamps so that’s why they are changing slightly.


    I googled the errors and I don’t think you need to worry about them.


    If your system is working fine I would just ignore them.

    OMV 7 (latest) on N100 Minipc (16GB) and RPI5 (8GB). OS on SD card. System ext4 on SSD. Data BTRFS on HDDs

    Hello there,

    If you really want to get rid of that message, just blacklist the module. From what I read on the internet it is a watchdog driver.

    If you wish to blacklist it, you can do this:

    Code
    echo "blacklist sp5100_tco" > /etc/modprobe.d/sp5100-tco-blacklist.conf

    If you get an error, because you not logged in as root, use sudo -i before you execute the command and exit after.

    Thanks to Jatal and Bermuda for the help.

    About Bermuda, I wanted to tell you that I don't know the procedures you indicated, and I don't know how to insert them because I don't know Debian.


    But this question arises: Why then on OMV5 everything worked regularly without any kind of error?

    Having saved the image of the OMV5 Operating System with Acronis True Image before deleting and then installing OMV7, restoring the OMV5 image the error does not exist, and everything works regularly.

    How do you explain this thing?


    Anyway, THANK YOU infinite guys for the help.

    Hello,

    this is not really an "error". It's just a kernel-module that is not working with your wachtdog. It probably happened because OMV7 has a newer kernel. I wouldn't worry about that. If your can't follow my suggestion, because you not that experienced with Unix/Linux, just leave it like that.

    I agree. I think you would have had the same situation with omv5 but the message was not being shown in the startup output.

    OMV 7 (latest) on N100 Minipc (16GB) and RPI5 (8GB). OS on SD card. System ext4 on SSD. Data BTRFS on HDDs

    And… I run omv on many different systems. Most have one or two messages like you are seeing.


    I run these systems without a monitor so never see them and ignore them

    OMV 7 (latest) on N100 Minipc (16GB) and RPI5 (8GB). OS on SD card. System ext4 on SSD. Data BTRFS on HDDs

    Good morning everyone.

    I thank you so much for the suggestions.

    Then I will definitely leave everything as it is.

    I hope to find a way or get help from someone who knows how to insert the code that Bermuda suggested to me. Thank you.

    Thanks also to the Forum for this opportunity to receive help.

    Good work everyone.

    • Official Post
    Quote from GbGiandu

    I hope to find a way or get help from someone who knows how to insert the code that Bermuda suggested to me. Thank you.

    Simply log into the server with ssh and run that line of code. https://wiki.omv-extras.org/do…lities_maint_backup#putty

    • New
    Quote from chente

    Simply log into the server with ssh and run that line of code. https://wiki.omv-extras.org/do…lities_maint_backup#putty

    As far as I understand his case, he has already a monitor and probably keyboard hooked up to his OMV host. He's issue is, that he can actually see the error message when the host boots up. So he only needs to log in as "root" and type that line of code to the letter. But given his Linux skill deficit, he's probably better off to have someone do/show it to him. But other than that, ssh would be the common approach.

    • New

    Good afternoon everyone.

    Mainly I thank you for the help you have given me, but I would like to know just one thing, this error that appears at startup, is it due to:

    1. the motherboard

    2. the processor (in my case it is an AMD FX8350)

    3. or another component of the NAS?

    Thanks everyone.

    Note for 'chente': I have a monitor and a keyboard connected to the host, but since I am not an expert in Linux, I prefer not to cause damage by tinkering with the code. Anyway, thanks chente for the suggestion.

    • New

    The error-message is due to a hardware-watchdog which your motherboard has. It is a nice feature to have and use. A watchdog reboots your host when the operating system hangs. Usually a process sends a signal to the watchdog every few seconds that everything is ok. When there is no signal the watchdog assumes the operating system is not ok and reboots the host.


    The message is about the driver module which has a problem loading the driver. But since you don't really need the watchdog, you can blacklist the driver-module (my solution) or simply ignore the message. Really, just IGNORE it :) Is has ZERO influence. Don't get obsessed by it. Is just something all people have. My HP notebook has also errors while booting. Some features don't work. But everything else works, so it is OK.

    • New
    • Official Post
    Quote from GbGiandu

    Note for 'chente': I have a monitor and a keyboard connected to the host, but since I am not an expert in Linux, I prefer not to cause damage by tinkering with the code.

    I only responded to your request for help running a command line.

    If you request help in this forum, you'll often receive instructions asking you to run commands in the CLI. Often, these will be simple commands requesting information about your system and its status. Other times, they will be commands that actually execute some change to your configuration to resolve a problem.

    You should familiarize yourself a bit with the command line, for example, so you can Google the suggested command and know what you're doing before doing it.

    • New

    Hello everyone.

    In the afternoon while I was copying files from the NAS to an external HDD, I realized late that the NAS monitor located behind me was showing this screen,

    with a sequence of errors.


    Can you please help me understand what is happening?

    Does OMV have an error check on the disks?

    If so, how should I check them?


    When I installed OMV7 I activated the S.M.A.R.T. check on all disks.

    However, I noticed that on the OMV7 WEB interface the S.M.A.R.T. section is green on all disks.

    Even the temperatures of all disks are (after two hours of operation) between 25 and 29 degrees.

    I can't understand what's happening. For now, as a precaution, I have turned everything off.


    Thanks to everyone for any advice and help.

    • New

    Well ... that doesn't look good. Since you have trouble operating a shell lets try some practical things first.


    It seems one drive has I/O errors. This could also be a faulty cable.

    Please shut down your host and switch SATA6 port with SATA1 port.

    -> disconnect STAT6 from HDD_6

    -> disconnect SATA1 from HDD_1

    -> connect SATA6 to HDD_1

    -> connect SATA1 to HDD_6

    -> power up your host

    -> wait for errors to show up


    OMV uses UUID to identify the disks. So things should be logically ok.

    Let's see if the error switches to another disk or if it stays on SATA6.

    • New

    Thanks Bermuda for the suggestion. :thumbup:

    Today I won't have time to make these changes you indicated, I'll do it all on Monday and let you know.

Participate now!

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

Register Yourself Login