Page 7 of 9 FirstFirst ... 56789 LastLast
Results 61 to 70 of 88

Thread: Time to build a server with old hardware.

  1. #61
    Join Date
    Jul 2019
    Location
    Beauvais France
    Beans
    109
    Distro
    Ubuntu 20.04 Focal Fossa

    Re: Time to build a server with old hardware.

    Thanks all for this very informative topic.
    Happy user of Ubuntu-20.04 on a Beelink BT3pro mini PC

  2. #62
    Join Date
    Feb 2008
    Location
    Lincolnshire
    Beans
    210
    Distro
    Ubuntu 11.04 Natty Narwhal

    Re: Time to build a server with old hardware.

    Hello again

    I seem to have gone a long way to get back to where I was a week ago. Basically, I failed to get control of bigbin-xubuntu, so I rebuilt it as a work station. That is what it was always destined to be anyway.

    I built a new machine to be the server. This is still an XUbuntu machine. It is called serverbot, and it now contains the disk with the partition Vol10. On serverbot I:

    ran "sudo apt install nfs-kernel-server"
    ran "sudo systemctl start nfs-kernel-server"
    edited fstab with the line "UUID=cf560714-4c5b-47d9-9765-08638b617ff4 /Vol10 ext4 noatime,errors=remount-ro 0 2"
    edited exports with the line "/Vol10 bigbin-xubuntu(rw,root_squash,async)"

    Following this I went to the client. There I:

    ran "sudo apt install nfs-common"
    edited fstab with the line "192.168.1.91:/Vol10 Vol10 nfs defaults 0 2"

    Again, Vol10 exists in the File System browser, but it is empty. Browsing the network makes Serverbot visible, but the only thing in it is the print share.

    Should I being doing something to start nfs-common, I tried

    sudo systemctl start nfs-common

    but this command failed.

  3. #63
    Join Date
    Nov 2008
    Location
    Metro Boston
    Beans
    15,486
    Distro
    Kubuntu 20.04 Focal Fossa

    Re: Time to build a server with old hardware.

    nfs-common just provides the infrastructure needed to run NFS.

    What do you see with
    Code:
    sudo mount -v 192.168.1.91:/Vol10 /Vol10
    If you ask for help, do not abandon your request. Please have the courtesy to check for responses and thank the people who helped you.

    Blog · Linode System Administration Guides · Android Apps for Ubuntu Users

  4. #64
    Join Date
    Mar 2010
    Location
    Squidbilly-Land
    Beans
    22,137
    Distro
    Ubuntu Mate 16.04 Xenial Xerus

    Re: Time to build a server with old hardware.

    On the client ....
    edited fstab with the line
    Code:
    192.168.1.91:/Vol10 Vol10 nfs defaults 0 2
    is incorrect. A /Vol10 is missing. Details matter. Computers do what we tell them.

    If you insist on staying with what you have AND , 192.168.1.91 is the correct NFS-server static IP,
    Code:
    192.168.1.91:/Vol10   /Vol10    nfs     defaults 0 2
    would be the client-side fstab.

    In post #7 above, I provided a number of correct lines, and attempted to be clear as to where those lines and commands needed to happen.

    Also, if you did a fresh install, the UUID could have changed, so you'll need to check that. There are commands above, which try to explain what they are for and how they check stuff, you can/should run. When you build a car engine, do you wait until after the final wash+wax job to try the key and turn the engine over? I hope not. That makes for confusion and lots of rework. It makes troubleshooting 1 tiny issue into troubleshooting every step, hoping nobody missed anything else along the way.

    Do a little, check it.
    Do a little more, check it.
    Do a little more, check that.

    SeijiSensei's command:
    Code:
    sudo mount -v 192.168.1.91:/Vol10 /Vol10
    will validate everything upto the client-side fstab line.

  5. #65
    Join Date
    Feb 2008
    Location
    Lincolnshire
    Beans
    210
    Distro
    Ubuntu 11.04 Natty Narwhal

    Re: Time to build a server with old hardware.

    Thank you for persisting. I missed out a "/" in my post, but I checked fstab and the "/" is there in the real thing. I'm sorry if I'm misinterpreting instructions, but three forms were given originally and that is the one which seemed nearest. I'll try the others again tomorrow. Unfortunately the journal file I was keeping on the first version was one of the things I lost. That was strange, because I copied it into Vol10 using the cp command, and then checked the driectory of Vol10 before physically moving the disk to the new machine, but the file was not there after re-mount.

    192.168.1.91 is the fixed address of the server.

    I did check the UUID for the new server.

    sudo mount -v 192.168.1.91:/Vol10 /Vol10 returns

    mount.nfs: timeout set for Tue Dec 8 22:20:10 2020
    mount.nfs: trying text-based options 'vers=4.2,addr=192.168.1.91,clientaddr=192.168.1.1 68'
    mount.nfs: mount(2): Permission denied
    mount.nfs: access denied by server while mounting 192.168.1.91:/Vol10

  6. #66
    Join Date
    Mar 2010
    Location
    Squidbilly-Land
    Beans
    22,137
    Distro
    Ubuntu Mate 16.04 Xenial Xerus

    Re: Time to build a server with old hardware.

    Whenever posting configs, aren't you just copy/pasting everything?

    Did the client IP address change?
    Does your LAN DNS know about that change?
    If not, then inside the /etc/exports file, don't use the hostname, use the static IP for the client.

    There are lots of moving parts in this setup. Because the first thing I do with any new install is force a specific, static, IP and update the LAN DNS, those things don't enter my mind, but they are necessary to have a "well-managed" network. IMHO.

    It would be helpful if you used 'code tags', like we've been using.

  7. #67
    Join Date
    Feb 2008
    Location
    Lincolnshire
    Beans
    210
    Distro
    Ubuntu 11.04 Natty Narwhal

    Re: Time to build a server with old hardware.

    I usually copy and paste, but I'm switching between machines on 3 different desks. I set the server to a fixed IP - 192.168.1.91. This is what it had been allocated; I just set it to fixed. The client is not fixed, but I checked the name. One of tomorrows tasks could be to fix the client's IP and use that.

    I'm not familiar with "code tags". I just looked them up and was presented with information on ctags and etags commands. But as usual, no conceptual context to make sense of it, just that thay are a kind of text editor accross "Unix like systems". If it is simple and you can explain a little more I will try to use them.

    Did the output from "sudo mount -v 192.168.1.91:/Vol10 /Vol10" help at all.

  8. #68
    Join Date
    Nov 2008
    Location
    Metro Boston
    Beans
    15,486
    Distro
    Kubuntu 20.04 Focal Fossa

    Re: Time to build a server with old hardware.

    Quote Originally Posted by Phil Binner View Post
    Did the output from "sudo mount -v 192.168.1.91:/Vol10 /Vol10" help at all.
    Let's see the /etc/exports file from the server.

    "Code tags" are a feature of most forum software. If you embed text within [code][/code] tags, it will display like this
    Code:
    Text inside code tags
    For instance entering the text

    [code]sudo mount -v 192.168.1.91:/Vol10 /Vol10[/code]

    displays as
    Code:
    sudo mount -v 192.168.1.91:/Vol10 /Vol10
    If you ask for help, do not abandon your request. Please have the courtesy to check for responses and thank the people who helped you.

    Blog · Linode System Administration Guides · Android Apps for Ubuntu Users

  9. #69
    Join Date
    Mar 2010
    Location
    Squidbilly-Land
    Beans
    22,137
    Distro
    Ubuntu Mate 16.04 Xenial Xerus

    Re: Time to build a server with old hardware.

    There are 2 reasons for code tags n these forums:
    * to show terminal commands + output clearly; fixed width fonts are used.
    * to retain spacing from the terminal - columns line up - makes output readable for us who are used to seeing it that way.

    I'm sorry I wasn't clear.

    If you want to use machine names in NFS, then each machine needs to be able to ping the other using the name. If in doubt, use the IP address instead. These are network protocols.

  10. #70
    Join Date
    Feb 2008
    Location
    Lincolnshire
    Beans
    210
    Distro
    Ubuntu 11.04 Natty Narwhal

    Re: Time to build a server with old hardware.

    Positive progress today. I now have a server, serverbot, with Vol10 mounted and shared, and I have two clients, firstmedion and bigbin-xubuntu, that have read write access.

    Lines in /etc/exports was

    Code:
    /Vol10  192.168.1.168(rw,root_squash,async)
    /Vol10  192.168.1.83(rw,root_squash,async)
    I need to save this as a test to see if I understood about code tags.
    Last edited by QIII; December 9th, 2020 at 06:55 PM. Reason: Fixed code tags.

Page 7 of 9 FirstFirst ... 56789 LastLast

Bookmarks

Posting Permissions

  • You may not post new threads
  • You may not post replies
  • You may not post attachments
  • You may not edit your posts
  •