Etherdfs and Dos Fat about retronas HOT 5 CLOSED

No, as it says it has ignored the invalid entry, it is something we should probably address to stop confusion though.

umask should be controlling file creation perms etc, so if you cant even get to the drive i don' t think you're there yet

@danmons you've used this one, I haven't care to chime in.

from retronas.

Can you verify /storage/dos is FAT? The output of df -hT /storage/dos in Linux will confirm. Similarly, mount will show all mounted volumes, and should list /storage/dos specifically.

8TB is also very large for FAT. Maybe retry the process with 1TB as well, just to see what the effect is. (2TB is the upper bounds for FAT32 with default cluster size, although I'm not sure if that matters to EtherDFS).

I'll attempt to rebuild and re-test some time this week on latest versions with an 8TB volume.

from retronas.

Ok @danmons , I've reset the previous one virtual hd and created a new virtual hd of 1TB.

 etherdfs.service - EtherDFS lightweight file server for MS-DOS
     Loaded: loaded (/lib/systemd/system/etherdfs.service; enabled; vendor preset: enabled)
     Active: active (running) since Mon 2023-10-16 22:15:24 BST; 1min 36s ago
   Main PID: 557 (ethersrv-linux)
      Tasks: 1 (limit: 1599)
        CPU: 18ms
     CGroup: /system.slice/etherdfs.service
             └─557 /opt/retronas/bin/ethersrv-linux -f eth0 /storage/dos

Oct 16 22:15:24 raspberrypi4retronas systemd[1]: Started EtherDFS lightweight file server for MS-DOS.

Press [Enter] to continue...

df -hT /storage/dos
Filesystem     Type   Size  Used Avail Use% Mounted on
/dev/loop0     msdos  1.0T  320K  1.0T   1% /storage/dos

sudo fsck.fat -v -n /dev/loop0
fsck.fat 4.2 (2021-01-31)
Checking we can access the last sector of the filesystem
There are differences between boot sector and its backup.
This is mostly harmless. Differences: (offset:original/backup)
  65:01/00
  Not automatically fixing this.
Boot sector contents:
System ID "mkfs.fat"
Media byte 0xf8 (hard disk)
       512 bytes per logical sector
     32768 bytes per cluster
        64 reserved sectors
First FAT starts at byte 32768 (sector 64)
         2 FATs, 32 bit entries
 134217728 bytes per FAT (= 262144 sectors)
Root directory start at cluster 2 (arbitrary size)
Data area starts at byte 268468224 (sector 524352)
  33546238 data clusters (1099243126784 bytes)
63 sectors/track, 255 heads
         0 hidden sectors
2147483646 sectors total
Checking for unused clusters.
Dirty bit is set. Fs was not properly unmounted and some data may be corrupt.
 Automatically removing dirty bit.
Checking free cluster summary.

Leaving filesystem unchanged.
/dev/loop0: 4 files, 10/33546238 clusters

from retronas.

Ok, this is the answer I've got from a member of MiSTer Fpga Forum, it seems sensible:

I'm not familiar with this particular software, but I'd guess from the programmer's description of EtherDFS that it won't work on anything other than real hardware with a real Ethernet card connected directly to a real, wired, Ethernet network.

Per the EtherDFS Read Me, EtherDFS works directly with Ethernet packets and doesn't use any higher level protocol.

AO486 doesn't emulate a network card. Instead, it uses PPP to transport higher-level protocols (IP, IPX, etc.) via an emulated serial link. Then, the MiSTer hard processor system at the other end of the PPP link places that traffic on the attached Ethernet or WiFi network.

So, from the EtherDFS client's perspective on AO486, there's no Ethernet card with which to interface. You'll need to use a different protocol. FTP would be the usual way to send files, but for a drive mount, your best option is going to be either SMB (LanMan/SAMBA) or IPX/SPX (Netware). I'm not sure if either of these play well with PPP.

Again, I'm not an expert, and I'd love to be proved wrong, but that's how I see it.

from retronas.

As this is not a retronas issue i am closing this, if you find success in this down the line it would be great if you could let the project know in the discussions area

from retronas.