IP address 0.0.0.0 - Unable to connect

  • if you have ssh access run

    omv-salt deploy run avahi halt hosts issue systemd-networkd

    Same result with and without sudo:

    • Official Post

    Read-only file system:

    Your OS filesystem is mounted read only. This usually happens when there is a problem. I would: sudo mount -o remount,rw / but you need to look at the logs (like kern.log and sylog in /var/log/) to see why it is doing that.

    omv 8.0-12 synchrony | 6.17 proxmox kernel

    plugins :: omvextrasorg 8.0.2 | kvm 8.0.2 | compose 8.0.5 | cterm 8.0 | borgbackup 8.0.2 | cputemp 8.0 | mergerfs 8.0 | scripts 8.0.1 | writecache 8.0.6


    omv-extras.org plugins source code and issue tracker - github - changelogs


    Please try ctrl-shift-R and read this before posting a question.

    Please put your OMV system details in your signature.
    Please don't PM for support... Too many PMs!

  • Your OS filesystem is mounted read only. This usually happens when there is a problem. I would: sudo mount -o remount,rw / but you need to look at the logs (like kern.log and sylog in /var/log/) to see why it is doing that

    I went to take a look at the logs, but even if I could find the error, I'd have no idea what it means or how to repair. For example, in the kern.log, the only thing my un-trained eyes could find was this warning in red at the bottom of the page:


    [ File kern.log is unwritable ]


    Here's what I got when I tried sudo mount -o remount,rw /:

    Code
    root@wdmch:~# sudo mount -o remount,rw /
    mount: /: cannot remount /dev/sda19 read-write, is write-protected.

    I know this may be a long shot, but could something strange have happened when I temporarily mounted my OMV's Linux HDD in my Windows 10 machine?


    There was an option to 'Set default ownership and permissions of the mounted volume' (which I did not enable), when I mounted the HDD within the third party app 'Linux File Systems for Windows by Paragon Software'. Perhaps this was the culprit?


    I also mounted the volume as 'Read-Write' in order to edit the files with Notepad++

    • Official Post

    could something strange have happened when I temporarily mounted my OMV's Linux HDD in my Windows 10 machine?

    Sure. That is a terrible idea so lots of bad things could happen.

    I also mounted the volume as 'Read-Write' in order to edit the files with Notepad++

    Also not a good idea. I hope you at least used Unix line endings.

    /dev/sda19

    19??? Please tell me you don't have 19 partitions on that disk and this is just a typo...

    omv 8.0-12 synchrony | 6.17 proxmox kernel

    plugins :: omvextrasorg 8.0.2 | kvm 8.0.2 | compose 8.0.5 | cterm 8.0 | borgbackup 8.0.2 | cputemp 8.0 | mergerfs 8.0 | scripts 8.0.1 | writecache 8.0.6


    omv-extras.org plugins source code and issue tracker - github - changelogs


    Please try ctrl-shift-R and read this before posting a question.

    Please put your OMV system details in your signature.
    Please don't PM for support... Too many PMs!

  • Sure. That is a terrible idea so lots of bad things could happen

    OK, I'll have another crack at mounting and experimenting with settings.

    I hope you at least used Unix line endings.

    Unix what nows?

    Please tell me you don't have 19 partitions on that disk and this is just a typo...

    Hold my beer:

    Is this bad?

    • Official Post

    Unix what nows?

    Look at the Edit -> EOL Conversions menu. Windows uses a CR LF for the end of each line. Linux uses just a LF. If you edit system config files and use CR LF, you will break things.


    Is this bad?

    wtf... Why??? I also wouldn't use a 4TB disk for the OS.

    omv 8.0-12 synchrony | 6.17 proxmox kernel

    plugins :: omvextrasorg 8.0.2 | kvm 8.0.2 | compose 8.0.5 | cterm 8.0 | borgbackup 8.0.2 | cputemp 8.0 | mergerfs 8.0 | scripts 8.0.1 | writecache 8.0.6


    omv-extras.org plugins source code and issue tracker - github - changelogs


    Please try ctrl-shift-R and read this before posting a question.

    Please put your OMV system details in your signature.
    Please don't PM for support... Too many PMs!

  • Look at the Edit -> EOL Conversions menu. Windows uses a CR LF for the end of each line. Linux uses just a LF. If you edit system config files and use CR LF, you will break things.

    You guessed it. I was on CR LF. I'll change and try again.

    wtf... Why??? I also wouldn't use a 4TB disk for the OS.

    I believe the OS stuff is on a smaller 30 something GB partition, while the Data Volume is the 3.6TB partition. I just copy and paste things off the internet. Don't judge! :)

    • Official Post

    essed it. I was on CR LF. I'll change and try again.

    Please don't. If you are going to edit files on the OS drive, boot your system in Linux and use a Linux editor.


    I believe the OS stuff is on a smaller 30 something GB partition, while the Data Volume is the 3.6TB partition. I just copy and paste things off the internet. Don't judge!

    I will judge whatever you copy and pasted because it is terrible. Does making that many tiny partitions make sense to you?

    omv 8.0-12 synchrony | 6.17 proxmox kernel

    plugins :: omvextrasorg 8.0.2 | kvm 8.0.2 | compose 8.0.5 | cterm 8.0 | borgbackup 8.0.2 | cputemp 8.0 | mergerfs 8.0 | scripts 8.0.1 | writecache 8.0.6


    omv-extras.org plugins source code and issue tracker - github - changelogs


    Please try ctrl-shift-R and read this before posting a question.

    Please put your OMV system details in your signature.
    Please don't PM for support... Too many PMs!

  • I changed the IP config files to DCHP.


    While the router DID give the device a new IP address and the login page rendered (even with a Ctrl + Shift + R refresh), it is still rocking the '502 - Bad Gateway error'.


    Let's rule out the IP stuff for now, as I feel it's working in it's current form.


    As ryecoaaron has discovered, my issue appears to now be read/write focussed.


    Are there any commands I can issue to force all my mounts/partitions to be read/write? (I know, this is becoming less OMV and more Linux related). I understand if we're moving too far away from this forum's purpose.

    • Official Post

    Are there any commands I can issue to force all my mounts/partitions to be read/write?

    No. Linux is doing that on each boot to protect your system because there is a problem. That problem needs to be fixed. I don't know what that problem is though.

    omv 8.0-12 synchrony | 6.17 proxmox kernel

    plugins :: omvextrasorg 8.0.2 | kvm 8.0.2 | compose 8.0.5 | cterm 8.0 | borgbackup 8.0.2 | cputemp 8.0 | mergerfs 8.0 | scripts 8.0.1 | writecache 8.0.6


    omv-extras.org plugins source code and issue tracker - github - changelogs


    Please try ctrl-shift-R and read this before posting a question.

    Please put your OMV system details in your signature.
    Please don't PM for support... Too many PMs!

  • I've abandoned trying to sort out the write access issue.


    I'm satisfied my original issue (re-establishing IP access to the device) was rectified with all your help. Thankyou dearly.


    I'm fairly certain the mounting of the Linux HDD in my Windows 10 PC caused the read/write issue.


    I've since unmounted the culprit (sda19), ran a FS checker and let it fix about 150 errors and rebooted.


    The device no longer boots up. I'm admitting defeat and starting again. Thankfully nothing on the NAS worth saving.


    Thanks again for all your help! :)

Participate now!

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