Raspberry PI as NAS

[outlawal2]

Greetings!

I am running several Amiga models with network capabilities on my network and would like to use an RPI 4 as a simple NAS.  I am using Veeam as a backup solution so my intent is to copy all Amiga related files to the RPI as a NAS and then I can copy the entire PI in Veeam and save backups regularly.  Then I wil backup my Amigas to folders on the PI and backup the PI ensuring everything is safe at all times.

In theory anyway.

Issue I am having is I can't seem to write to the PI from my Amiga.  I am able to see the PI share and open it and I can see files on it but I can't write to it.
To make thngs as easy as possible with this initial experiment I am logging into the PI as root and as far as I know I have all permissions set for the root account. and root is the owner of the share as well.
I am wondering if it is because I am using the filesystem EXT4 on the PI?  (But my Synology NAS is also EXT4 and I can read and write to it with no issues.)

Amiga is an 060 3000 running Roadshow and as stated Roadshow with EZ SMB Mounter software and SMBFS.  These are configured and I can read and write to my Synology NAS but not the RPI.
Any suggestions?

[Tygre]

Hi OutlawAL2!

Nice I have a similar setup here although I'm less dilligent in backing up my RPI!

I assume that you are using Samba to make some folders of your RPI visible and SMBFS on your Amigas to access them? If so, could you show us the smb.conf sections in which you declare the "shares"? It could be that they are "read-only". Also, do you have a specific user on your RPI for Samba-related stuff? In SMBFS, ddi you put the corresponding username and password?

Take care!

[kolla]

I am guessing here that the problem is that samba on pi is configured for modern cifs/smb3 only, while smbfs only supports up smb2 if I recall correctly, or perhaps only smb1... so you need to configure samba to support “legacy” versions of smb. Don’t ask me how, I go to great lengths to avoid smb alltogether

[outlawal2]

TYGRE
Thanks for the response guys appreciate it
Sorry I haven't been able to get back to you but my job got in the way and continues to..

With that in mind I am using SMB Mounter with SMBFS so short answer is yes I am using the correct account and password (I have it prompt me for those each time)
And the shares are accessible with those accounts/passwords from Windows PCs so I am thinking Kolla may be correct regarding the version of SMB as my NAS can be used all the way back to SMB1 so I am betting the PI won't support that out of the box.

Sorry can't get to the PI at the moment but am wondering what is the process to turn on SMB1 on the PI?  Pretty sure that is what is causing my pain.

KOLLA:

Thanks  for the suggestion as I think you are probably correct. I am curious though,  What do you use to connect your Amigas if you don't use SMB?

[Tygre]

Hi OutlawAl2

You're welcome

Poking around the Internet, it seems that you can specify the minimum accepted protocol version in the [global] section of /etc/samba/smb.conf with:

Code: [Select]

min protocol = SMB1
but actually, looking at my own configuration file, here is the option that you must add/change into [global], I even had added a comment

Code: [Select]

   # Same as "ntlmv1-permitted", for Amiga SMBFS clients
   ntlm auth    = yes

Let's know!

[kolla]

@outlawal2

I use good old nfs2 and the chnfs package...

http://aminet.net/package/comm/net/chnfsc102-30b2

[outlawal2]

Nice job Tygre... 
  # Same as "ntlmv1-permitted", for Amiga SMBFS clients
   ntlm auth    = yes
was the ticket. 

Interestingly enough, trying SMB1 errored out but the other suggestion was gold.
Thank you sir!

[Tygre]

Happy that it's working for you

I think that we have pretty much the same setup! Be aware that some Amiga files cannot be copied to the PI because of the filesystems over there, for example StormC project files with the extension ".¶"

Cheers!

[outlawal2]

Interesting..  I would have thought that cross dos would take care of that issue..
Well nothing is ever perfect especially when working with 30 year old tech.

I am just pleased I was able to get the Amiga to see my Linux box.   Now I am going to install Manjaro as a VM and configure as the NAS and then I can keep the entire thing virtualised and backed up that way.  Then I can use my PI4 for something else!

More to come
(And again thank you for the assistance!)

[chris]

I use Duplicati for backup, works great on the Pi. Use B2 Cloud as the backing store and it costs barely anything.

[outlawal2]

Yeah backing up the PI is no issue, I am wondering what you folks use to backup your Amiga that can utilize a network drive?

[golem]

Because the Amiga has so many smaller sized files, I find the easiest way to back up is create an lha archive of each individual top level directory on the Amiga drive and then copy these to my NAS.
That way if you have a directory that does not change you don't need to create the lha or copy it to the NAS each time. It also makes sure all Amiga file attributes are preserved.
Syntax to backup Libs folder, for example, (that I have copied from other members here I'm sure, is);
lha -aerzx a Backup:Libs.lha Libs/#?
Assigning Backup: to a folder on your Amiga drive is faster than running it over the network, and then copy to NAS after all the lha have been created.

[outlawal2]

I may just do that

One of the things I intend to do is to build up a configuration that has everything on it I want including Rapid Road config, Mui etc and copy it to my network drive.
Then create a CD that has the networking files and config along with SMB Mounter

So the next time I have to build from scratch I can simply install 3.1.4 and connect a CD drive.
Copy the network files with SMB Mounter and mount my NAS
Copy all of the backed up files from my config created earlier and reboot.

Makeshift Amiga Imaging!

And I intend to include all of the different drivers for my networking along with entries for all of them in the config files REMd out and just select the ones I need depending on the network card I am using.
That is the thought anyway.

[chris]

FolderSync works well for keeping the Amiga in sync with the NAS, where it can be backed up.  This is fine if the character set and Amiga filesystem attributes being lost isn't going to cause any problems.
The other thing I like to do is create an ISO with the files on.  If you ensure it is created with all the Amiga extensions then you won't lose anything, and it can be mounted and files read easily on any system.  This is similar to the LhA solution but it's less hassle to get to individual files.

[Tygre]

Hi Chris!

I used FolderSynch, very cool!

And I like you idea of using an ISO (or HDF) file, maybe with ImageMount?

Cheers!