NFS - 500 Internal Server Error

  • Hi All,

    I wonder if anyone can decipher the error below or give advice.

    Also, I cannot type command line entries in as I cannot SSH into the pi even though I have tried to enable SSH in services.

    I cannot log in with root either like some posts suggest -only admin works.


    Thanks for any help.


    Below is what I did:



    Hardware: Raspberry Pi 3A+

    External 2TB Drive.



    I used the official Raspberry Pi Imager app on mac to image the Pi and supply wifi credentials and enable SSH.


    Username: lf


    image: selected for hardware 3A+ >Other > Legacy 64 bit Lite.


    Used router to find pi on network: 192.168.1.101



    Opened Terminal


    Code
    ssh 192.168.1.101
    
    sudo apt update
    
    sudo apt upgrade
    y
    
    wget -O - https://raw.githubusercontent.com/OpenMediaVault-Plugin-Developers/installScript/master/install | sudo bash

    That takes 30 or so minutes

    The ssh connection is dropped and I get permission denied when I try to ssh in again.


    I access the Open Media Vault Config page via a web browser.


    Plugged in a 2B drive and it reset the pi,


    Logged back into web interface

    Checked notifications and logs in web interface but couldn't see and power problems.


    Changed password


    Mounted Drive


    Added share folder


    Services > Enabled NFS > Shares


    added the HDD share created earlier


    client: 192.168.1.53. 500 Internal server error

    tried 192.168.53/24 500 Internal server error

    tried 192.168.0/24 500 Internal server error


    I cannot decipher this error message:


    There's more to the error message - but the forum wouldn't let me post it because it was too long...

  • chente

    Approved the thread.
  • I wiped the SD card and tried again with a different SD card and a different power supply in case these were causing issues.


    The same problem occurred upon applying changes after a share was added to the NFS.



    Summary for NAS


    ------------


    Succeeded: 5


    Failed: 1


    ------------


    Total states run: 6


    Total run time: 3.480 s


    [ERROR ] Command '/bin/systemd-run' failed with return code: 1


    [ERROR ] stderr: Running scope as unit: run-r87f2eb555af74923924bb1c724b61aa6.scope


    Job for nfs-server.service canceled.


    [ERROR ] retcode: 1


    [ERROR ] Job for nfs-server.service canceled. in /usr/share/php/openmediavault/system/process.inc:242


    Stack trace:


    #0 /usr/share/php/openmediavault/engine/module/serviceabstract.inc(62): OMV\System\Process->execute()


    #1 /usr/share/openmediavault/engined/rpc/config.inc(178): OMV\Engine\Module\ServiceAbstract->deploy()


    #2 [internal function]: Engined\Rpc\Config->applyChanges(Array, Array)


    #3 /usr/share/php/openmediavault/rpc/serviceabstract.inc(123): call_user_func_array(Array, Array)


    #4 /usr/share/php/openmediavault/rpc/serviceabstract.inc(149): OMV\Rpc\ServiceAbstract->callMethod('applyChanges', Array, Array)


    #5 /usr/share/php/openmediavault/rpc/serviceabstract.inc(620): OMV\Rpc\ServiceAbstract->OMV\Rpc\{closure}('/tmp/bgstatusF5...', '/tmp/bgoutputTj...')


    #6 /usr/share/php/openmediavault/rpc/serviceabstract.inc(159): OMV\Rpc\ServiceAbstract->execBgProc(Object(Closure))


    #7 /usr/share/openmediavault/engined/rpc/config.inc(199): OMV\Rpc\ServiceAbstract->callMethodBg('applyChanges', Array, Array)


    #8 [internal function]: Engined\Rpc\Config->applyChangesBg(Array, Array)


    #9 /usr/share/php/openmediavault/rpc/serviceabstract.inc(123): call_user_func_array(Array, Array)


    #10 /usr/share/php/openmediavault/rpc/rpc.inc(86): OMV\Rpc\ServiceAbstract->callMethod('applyChangesBg', Array, Array)


    #11 /usr/sbin/omv-engined(537): OMV\Rpc\Rpc::call('Config', 'applyChangesBg', Array, Array, 1)


    #12 {main}

    • Official Post

    Please go to the notification sidebar (the bell icon at the top right), copy the compete error message to clipboard and paste it here.


    Please also let us know which OMV version you are using. We have 3 versions (5,6 and 7) to maintain ATM. You can specify the version via tags at the top of the post here.

  • Hardware: Raspberry Pi 3A+

    External 2TB Drive.

    You are running a Pi3 which only has USB2.0

    That port can only provide 480mA of power to a drive. If it's portable type, it's not enough.


    So, questions that need answer are:

    What drive are you using?

    Is it self-powered or its a portable one?

  • Thanks Soma,


    Yeah I thought it might be an issue, but nothing came up in the logs.


    It is a portable 2TB Western Digital and it does not have an external power supply, it's trying to take power from the P3A+'s USB port. Surely half an amp is plenty?

  • Yeah I thought it might be an issue, but nothing came up in the logs.

    Which logs you searched?


    The one you should inspect is dmesg.


    sudo dmesg | grep fail

    OR

    sudo dmesg | grep err

    OR

    sudo dmesg | grep voltage

    ALSO

    I don't know if Pi3 has this but you can try

    sudo vcgencmd get_throttled


    Surely half an amp is plenty?

    Depends on the portable drive.

    But I wouldn't trust my DATA on an unreliable power source.

    You'll be better off having it connected to an external power supply OR just use a proper self-powered box or drives.

    • Official Post

    There's more to the error message - but the forum wouldn't let me post it because it was too long...

    Paste it in a text file and post the file (after you checked the power)

  • Thanks everyone,

    Much appreciated,


    Well, I did it all again and got it working with a USB stick formatted to EXT4, so it must have been something about that drive,, either the current draw or something else.


    I only looked at the logs I could access via the web page interface - I have not been able to SSH into the pi since I installed OpenMediaVault. It just says permission denied.


    I will see about getting another drive


    I include the rest of the error message for completeness.

    Thanks again

  • I can't provide the current output of the journalctl -u nfs-server command on your system.

    If you're encountering issues with your NFS server, running the journalctl -u nfs-server command in your terminal will display the logs related to the NFS server service. This can help you identify any errors or issues that might be occurring.

    If you have specific error messages or issues from the output that you'd like assistance with, feel free to share them here, and I'll do my best to provide guidance based on the information provided.

Participate now!

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